Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
pandacookie said:
Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
Click to expand...
Click to collapse
nice.
That is real good news
Well I've been rooting and un rooting and going into the bootloader on Windows 8.0 since the beginning. But happy it's working for you now.
Sent from my HTCONE using XDA Premium 4 mobile app
BrianBaker said:
Well I've been rooting and un rooting and going into the bootloader on Windows 8.0 since the beginning. But happy it's working for you now.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh, I know it worked in 8.0. But it didn't work in 8.1 for a lot of people, myself included. This wasn't just an HTC One issue, either. This was an issue for quite a few phones. But yeah, it works now. Either it's one crazy coincidence that this triggered 8.1 to recognize my HTC One in fastboot, or this update really makes a difference.
Just re-read what you wrote and realized what you were saying.. My bad... Waiting for official 8.1 to roll out myself so I'm happy to know I won't have an issue.
Sent from my HTCONE using XDA Premium 4 mobile app
Oh it's all good! I hope what I discovered here helps a few people.
Yea, I had to reinstall 8.1 to 8.0 at work because no matter what I did it would not work..
pandacookie said:
Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
Click to expand...
Click to collapse
Yep can confirm! Fastboot finally works on 8.1!
It always worked with 8 and 8.1 if you used the clockworkmod universal adb drivers
orthonovum said:
It always worked with 8 and 8.1 if you used the clockworkmod universal adb drivers
Click to expand...
Click to collapse
They didn't work for me, though.
pandacookie said:
They didn't work for me, though.
Click to expand...
Click to collapse
strange, works for me and friends on windows 7, 8, 8.1 no problems.. anyway sounds like things are no longer an issue with 4.3 tho so good to hear
Perhaps it works for only people that updated to the newer hboot. I flashed the firmware without the new hboot and mine is still borked.
I think it does have something to do with the new hboot, I have the new firmware minus the hboot and it still isn't working for me.
Sent from my HTCONE using Tapatalk 4
pandacookie said:
Some of you may have felt the frustration of trying to root using a computer running Windows 8.1. (I have Windows 8.1 RTM) I actually tried to root last night. Windows 8.1 would not recognize my HTC One while in fastboot, no matter what I tried. I Googled and tried EVERYTHING out there! I tried various drivers. I tried uninstalling and reinstalling the device. I tried uninstalling and reinstalling the usb root hub through Device Manager. I even tried a virtual machine, which also didn't work. I also have a crappy netbook that dual boots Windows 7 and Ubuntu 12.04, but I was stubborn and was determined to try to figure it out.
Then the update came today. Since the update included a new HBoot, I was curious if that would make a difference. So I went into fastboot and hoped for the best. Lo and behold, the computer began installing the correct drivers! That was enough. And now I am happily rooted. Not S-Off yet, but that will come!
I am a happy Panda!
Click to expand...
Click to collapse
Oh man you are the best! Sorry to quote you again, but you safed my from doing my head in on the next wall as I couldn't get fastboot to be recognised either.
I have the HTC One Int'l though, but upgrading my Hboot 1.54 to Hboot 1.55 finally got my computer running W8.1 to download the correct drivers and fastboot is working now! What an easy fix LOL
However, latest HTC Sync drivers are necessary and best to upgrade them before upgrading to W8.1 which definetely needs the latest Hboot
I am also a very happpy Panda now!
An issue arises for me when you begin to run an RUU and then it boots you into FastbootRUU mode after root and recovery installed, then it will not work properly.
as I expected, upgrading to the newer hboot from 1.44 to 1.55 does allow windows 8.1 to install fastboot driver.
does updating the hboot to 1.55 effect being s-off at all? i would like my windows 8 to work with my htc one but not if itll take away my s-off.
Still don't work for me
liljthatbol said:
Still don't work for me
Click to expand...
Click to collapse
Update to latest HBOOT and install HTC sync.
Related
Hey guys, I'm trying to get S-OFF for my device where I am running 1.31. I am able to do the ADB command when my phone is turned on, but when I am in recovery my computer can't get it to recognize my device.
I had just upgraded my TWRP from 2.5.0.0 to the newest version which I believe it is 2.6.3.0.
EmSeeMAC said:
Hey guys, I'm trying to get S-OFF for my device where I am running 1.31. I am able to do the ADB command when my phone is turned on, but when I am in recovery my computer can't get it to recognize my device.
I had just upgraded my TWRP from 2.5.0.0 to the newest version which I believe it is 2.6.3.0.
Click to expand...
Click to collapse
Same here. I went back to 2500...again. It seems like every time I try a newer version, something doesn't work with it.
erikivy said:
Same here. I went back to 2500...again. It seems like every time I try a newer version, something doesn't work with it.
Click to expand...
Click to collapse
can you point me where to get the older versions?
EmSeeMAC said:
Hey guys, I'm trying to get S-OFF for my device where I am running 1.31. I am able to do the ADB command when my phone is turned on, but when I am in recovery my computer can't get it to recognize my device.
I had just upgraded my TWRP from 2.5.0.0 to the newest version which I believe it is 2.6.3.0.
Click to expand...
Click to collapse
Had this problem when I updated my Nexus 7 from 4.2 to 4.3. The problem was needing to update the Android SDK. The adb exe wasn't at a high enough API to recognize the new drivers.
gk1984 said:
Had this problem when I updated my Nexus 7 from 4.2 to 4.3. The problem was needing to update the Android SDK. The adb exe wasn't at a high enough API to recognize the new drivers.
Click to expand...
Click to collapse
I had just installed the android sdk yesterday, I would assume they would have been updated to the most recent release? Anyways, I just downgraded to 2.5.0.0 and ran the RUU and now everything is okay!:good:
I had that problem yesterday, tried for a couple hours trying different drivers and stuff then decided to restart my computer and it worked without a hitch
Sent from my HTCONE using Tapatalk now Free
Hi,
I'm having problems connecting my phone to my computer (MacBookPro). I tried downloading Motorola Device Manager, but it won't work (since I'm using OS X Yosemite). I rebooted in to Win 7, and tried downloading MDM there, but it doesn't install drivers for the phone.
The reason I want to connect the phone to the computer is I'm looking to update the phone to Lollipop (can't stand waiting for the OTA).
//nejo01
nejo01 said:
Hi,
I'm having problems connecting my phone to my computer (MacBookPro). I tried downloading Motorola Device Manager, but it won't work (since I'm using OS X Yosemite). I rebooted in to Win 7, and tried downloading MDM there, but it doesn't install drivers for the phone.
The reason I want to connect the phone to the computer is I'm looking to update the phone to Lollipop (can't stand waiting for the OTA).
//nejo01
Click to expand...
Click to collapse
Have you tried Android File Transfer? https://www.android.com/filetransfer/
_MetalHead_ said:
Have you tried Android File Transfer? CANT QOUTE THIS
Click to expand...
Click to collapse
No, I thought that was just for file transfers (I was looking to try to update my phone, which doesn't seem possible)?
same problem here.
In yosemite (mac osx) doesnt work and dont detect the device.
I think the problem is the compatibility between MDM and Yosemite...
nejo01 said:
No, I thought that was just for file transfers (I was looking to try to update my phone, which doesn't seem possible)?
Click to expand...
Click to collapse
How are you trying to update? ADB/fastboot? You need the Android SDK for that.
_MetalHead_ said:
How are you trying to update? ADB/fastboot? You need the Android SDK for that.
Click to expand...
Click to collapse
No, I was simply trying to check for updates via the computer (as I read somewhere that Lollipop was released - but it didn't show up in my phone)
I've been skimming some threads on updating the phone, but from what I could tell the phone needs to an XT1095 and not the 92 that I have?
nejo01 said:
No, I was simply trying to check for updates via the computer (as I read somewhere that Lollipop was released - but it didn't show up in my phone)
I've been skimming some threads on updating the phone, but from what I could tell the phone needs to an XT1095 and not the 92 that I have?
Click to expand...
Click to collapse
I think you know something I don't here... exactly how do you plan on updating through your computer? I'm lost.
_MetalHead_ said:
I think you know something I don't here... exactly how do you plan on updating through your computer? I'm lost.
Click to expand...
Click to collapse
I thought that maybe the OTA update-function on the phone wasn't a hundred percent, so figured I'd check out updating via Motorola computer software.
nejo01 said:
I thought that maybe the OTA update-function on the phone wasn't a hundred percent, so figured I'd check out updating via Motorola computer software.
Click to expand...
Click to collapse
Ahhh, through Motorola Device Manager? I didn't even know it existed prior to this thread.
And it's not that it's not 100%, it's that the OTA rolls out in stages. Not every phone gets it at the same time. Not quite sure how it'll work through that software though.
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
ryan4a said:
Hello,
Maybe this has already been answered, but does anyone know if it's possible to flash an updated radio.img, system.img, bootoader.img and boot.img? I'm a bit of a noob, and I want to upgrade my Nexus 6 to 5.1 once the factory images are released (and the modified boot.img to remove encryption). However, I'd like to do this without the use of a computer. I would use the Nexus Root Toolkit, but for some reason my PC no longer recognizes my device (even though I've tried EVERYTHING to fix, including different cables, ports, drivers, restarts etc.). Maybe the 5.1 update will fix, but I think I have a faulty micro usb port on the device.
I don't want to wipe my data or lose root, which is why I would only update the above images. I thought it could be done through Flashify, but the dev said I'd have to flash an entire .zip through TRWP, but I need the files along with the correct commands. I would lose root, but would use the Towelroot apk to get it back.
Please let me know if this is correct or if I'm missing something. Or if there is an easier way (like maybe Nexus Update Checker).
Thanks
Click to expand...
Click to collapse
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
simms22 said:
first off, towelroot doesnt work in android 5.0+. 2ndly, if you are planning on flashing the official 5.1, you need a computer. if you are planning on updating a custom rom, and you have twrp recovery, download the rom and flash it via twrp.
Click to expand...
Click to collapse
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
ryan4a said:
Thanks. I don't have a custom ROM. So I guess I'll wait for one to get updated, then install it. Like I said, using a computer is not an option
Click to expand...
Click to collapse
thats the easiest way. i dont own a computer nor laptop, so i try to do everything from the phone. but its easier to update via recovery anyways. one thing though, since you are on the stock rom, you will have to wipe your data before flashing a custom rom, since the majority are aosp based, and wont flash over stock.
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
doitright said:
Before you give up, try a different computer (preferably running Linux), or booting the one you have on a livecd/usb.
If the USB plug on the phone is, in fact, broken, try calling motorola. The phone is still under warranty....
Click to expand...
Click to collapse
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
ryan4a said:
Thanks. I've tried on multiple computers (PC & Mac, but not Linux). Nothing works. I originally thought it was one of the modifications I made to the device, like root, unlock, custom boot.img, custom recovery, modified build.prop, etc. The more I search, the more I think it's hardware. I'd like to not have to warranty it because I'd have to wipe everything, restore to factory settings, unroot, etc. It's just a big hassle. Plus I'd be without a phone until the replacement arrives. I may end up just living with staying on lollipop 5.0.1 forever. It's just super frustrating.
Click to expand...
Click to collapse
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
For a driver, it isn't a question of seeing it. Its a question of knowing how to talk to it. Further, one of the reasons I suggest he use something that runs linux, is because it avoids this whole driver problem altogether. The other reason is that it is actually consistent, and trivial to determine whether the devices itself actually made a connection, i.e. "dmesg -w", plug it, and see if it says anything.
simms22 said:
update your nexus 6 driver, or install the adb driver. your computer cant see your phone until it has one of the drivers installed. if you had it installed, uninstall it and reinstall.
Click to expand...
Click to collapse
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
ryan4a said:
I've deleted and reinstalled the google driver, and installed the ADB driver. No dice. I'm telling you...I've tried everything. That's why I think it's hardware, however unlikely.
Click to expand...
Click to collapse
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
simms22 said:
when getting adb to work, thats the #1 issue, installing and getting the driver to work. so, i can tell you, many people dont get the driver working without help in manually installing it. it seems those with older windows have less issues then those with newer windows. i really doubt that its a hardware issue.
Click to expand...
Click to collapse
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
ryan4a said:
Man I hope you're right. But my PC doesn't even recognize my device. Like it's not even showing up in the device manager. At best, I can sometimes get the PC to recognize it as an "unknown device". When I try to automatically update the driver, it says complete. But nothing changes. What do I do at that point? I haven't been successful in manually updating the driver.
Click to expand...
Click to collapse
i wouldnt be able to help you there, as i dont own a computer. but there are many that can help out. maybe someone else will see this thread..
ryan4a said:
As a matter of fact, I thought my new Turbo charger was broken because it stopped charging my phone. But when I unchecked USB debugging AND unchecked the MTP connection, the charger started working again. Very strange!
Click to expand...
Click to collapse
Like I said, TRY LINUX.
No drivers required. Everything is built into the kernel.
Fedora even has an "android-tools" package that includes adb. You just install it with "yum install android-tools" -- even on the livecd (it will install to ramdisk).
Quit screwing around with wondoze and TRY IT.
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
killall said:
Linux is a mega pita. Nothing is intuitive or easy. All these commands that have to be typed in, yuk. Give me good ol' Windows any day. Lol.
To the OP. Are you on windows 8.1? Have you disabled 'driver signature verification'?
Click to expand...
Click to collapse
I'm using Windows 7. Don't think I'll be using Linux either. I'm running out of options for upgrading android versions without a PC. I'm highly considering installing CM12. I'd rather not because it's seems unnecessary on a Nexus device, but don't know what else to do.
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Definitely sounding more and more like hardware
ryan4a said:
There is also about a 5 second delay from the time I plug my device into any charger, to when it actually begins charging. I'm thinking these two issues are related, which leads to believe it's hardware.
Click to expand...
Click to collapse
I have the same delay when plugging in a charger. But my PC recognizes my N6 without any problems.
On my Droid Maxx I had driver issues. I asked on XDA and got it figured out. I can't check now but have a look at my posts and you may find your answer.
Back to V-Day.
Brand new nexus 6, build #LMY47E, running Android 5.1
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
a.demarco said:
Brand new nexus 6, build #LMY47E
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
Click to expand...
Click to collapse
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Evolution_Freak said:
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Click to expand...
Click to collapse
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Yeah, I knew there were a couple other SDK components needed but I couldn't think of them off the top of my head and also get my kids ready for bed at the same time. Lol!! Glad you're on the right track! :good:
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
slimc84 said:
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
a.demarco said:
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
Click to expand...
Click to collapse
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
slimc84 said:
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
Click to expand...
Click to collapse
Ah, gotcha... Had no idea the drivers were in the toolkits!
a.demarco said:
Ah, gotcha... Had no idea the drivers were in the toolkits!
Click to expand...
Click to collapse
Are you still having driver issues or did you get it sorted out? Just curious.
Evolution_Freak said:
Are you still having driver issues or did you get it sorted out? Just curious.
Click to expand...
Click to collapse
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
a.demarco said:
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
Click to expand...
Click to collapse
Yes, priorities. If you have any questions later, don't hesitate to ask.
Download the nexus toolkit and follow the instructions given in it to install the drivers, you don't even need the android sdk,
a.demarco said:
OS Windows 7 Home Premium 64-bit SP1
...
What do I do?
Click to expand...
Click to collapse
Delete that crap and install a real operating system.
doitright said:
Delete that crap and install a real operating system.
Click to expand...
Click to collapse
And what in your opinion is a real operating system?
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