Related
What an absolute cluster. I am trying to use motochopper, right now I am installing USB drivers.
When I select "browse for software on your computer" it only lets me pick folders, not allowing me to pick the actual file that I need. I can't find a way around this, even placing the file in the folder doesn't help. I attached a picture to help.
Thank you in advance for assisting me with this headache. I have unlocked the device already, need to root it and then have a customer recovery, and eventually get on kitkat because the stock rom on this TF300 is almost unusable.
awmiscool said:
What an absolute cluster. I am trying to use motochopper, right now I am installing USB drivers.
When I select "browse for software on your computer" it only lets me pick folders, not allowing me to pick the actual file that I need. I can't find a way around this, even placing the file in the folder doesn't help. I attached a picture to help.
Thank you in advance for assisting me with this headache. I have unlocked the device already, need to root it and then have a customer recovery, and eventually get on kitkat because the stock rom on this TF300 is almost unusable.
Click to expand...
Click to collapse
If you can't find another solution, you can using Framaroot. It runs only on the tablet (no ADB needed) and works on some Android versions.
You can always try Kingo. It worked like a champ on my TF300T and my Note 3.
Sent from my SM-N900V using XDA Premium 4 mobile app
awmiscool said:
What an absolute cluster. I am trying to use motochopper, right now I am installing USB drivers.
When I select "browse for software on your computer" it only lets me pick folders, not allowing me to pick the actual file that I need. I can't find a way around this, even placing the file in the folder doesn't help. I attached a picture to help.
Thank you in advance for assisting me with this headache. I have unlocked the device already, need to root it and then have a customer recovery, and eventually get on kitkat because the stock rom on this TF300 is almost unusable.
Click to expand...
Click to collapse
I think the best option is to use fastboot to install a custom recovery such as TWRP then root it from the recovery. If you are planning on flashing a custom ROM you will have to do this eventually anyway.
Are you up to date with the latest stock ASUS ROM? Which custom ROM are you going to use if that is your plan?
All questions that will determine the best way to move forward AND which custom recovery to install.
Best of luck.
pastorbob62 said:
I think the best option is to use fastboot to install a custom recovery such as TWRP then root it from the recovery. If you are planning on flashing a custom ROM you will have to do this eventually anyway.
Are you up to date with the latest stock ASUS ROM? Which custom ROM are you going to use if that is your plan?
All questions that will determine the best way to move forward AND which custom recovery to install.
Best of luck.
Click to expand...
Click to collapse
For some reason it won't do any OTA updates. I haven't looked too much into roms, sounds like cromni-x or something is what I want. I don't want bleeding edge, I want reliability and smoothness. This is my first tablet I've done this process to, my S3 was easy and my other older phones were even easier. I will look into the methods posted, as well as posting my current tablet info shortly. Thank you very much guys!
Framaroot app says my device won't take the exploit. Kingo says device not connected with both usb debugging enabled and disabled, even though I can see it on my pc and am able to transfer files.
Running 4.1.1 with build number 10.4.2.20, will be on this project all day so by all means please give more advice!
EDIT: I am doing a fresh install of windows 7 in case some of these issues are related to it not being detected correctly. I have had issues with microsd cards and other usb devices before.
Just use kingo root
awmiscool said:
For some reason it won't do any OTA updates. I haven't looked too much into roms, sounds like cromni-x or something is what I want. I don't want bleeding edge, I want reliability and smoothness. This is my first tablet I've done this process to, my S3 was easy and my other older phones were even easier. I will look into the methods posted, as well as posting my current tablet info shortly. Thank you very much guys!
Framaroot app says my device won't take the exploit. Kingo says device not connected with both usb debugging enabled and disabled, even though I can see it on my pc and am able to transfer files.
Running 4.1.1 with build number 10.4.2.20, will be on this project all day so by all means please give more advice!
EDIT: I am doing a fresh install of windows 7 in case some of these issues are related to it not being detected correctly. I have had issues with microsd cards and other usb devices before.
Click to expand...
Click to collapse
Once you've unlocked it, it will not do updates via the standard method. You will have to flash via fastboot. Before you flash CROMi-X you will need to flash the stock Asus JB 4.2.1. If I understand correctly, you are not able to connect to your PC in fastboot mode? Are you in the bootloader when you attempt to use fastboot? If that is the case then you probably don't have the correct drivers installed. It has been over a year since I installed everything on my PC so I am a little foggy on where to get all of the correct drivers and software.If I remember correctly I downloaded them from Asus. I believe I downloaded and installed ASUS Pad PC Suite which installed the correct drivers. Then you need fastboot which can be found on several threads including the one I first provided to you.
Just because you are connected as a media device and can transfer files back and forth does not mean you have the right drivers installed and can use fastboot. You are connecting at a totally different level.
What ever you do, be sure you are matching versions of bootloader/recovery/ROM. Don't flash a 4.2.x version recovery onto a 4.1.x version bootloader. This goes double for 4.4.x version ROM's. If you do , you will brick your tablet. Also, I suggest doing an NVflash backup once you have fastboot up and running BEFORE you flash anything custom. It is a long process with many steps but in the long run you will be thankful you did if you should make a mistake and brick your tablet.
If you have questions, ask but do a lot of research first. All of the info you need is on this forum but you need to spend the time reading and becoming familiar before going forward. We have all been where you are at one time and had to do the research. It is time well spent. Having bricked one smart phone because I got in a hurry I am speaking from experience.
---------- Post added at 08:18 AM ---------- Previous post was at 07:35 AM ----------
spider623 said:
Just use kingo root
Click to expand...
Click to collapse
Did you even read what he wrote???
pastorbob62 said:
Once you've unlocked it, it will not do updates via the standard method. You will have to flash via fastboot. Before you flash CROMi-X you will need to flash the stock Asus JB 4.2.1. If I understand correctly, you are not able to connect to your PC in fastboot mode? Are you in the bootloader when you attempt to use fastboot? If that is the case then you probably don't have the correct drivers installed. It has been over a year since I installed everything on my PC so I am a little foggy on where to get all of the correct drivers and software.If I remember correctly I downloaded them from Asus. I believe I downloaded and installed ASUS Pad PC Suite which installed the correct drivers. Then you need fastboot which can be found on several threads including the one I first provided to you.
Just because you are connected as a media device and can transfer files back and forth does not mean you have the right drivers installed and can use fastboot. You are connecting at a totally different level.
What ever you do, be sure you are matching versions of bootloader/recovery/ROM. Don't flash a 4.2.x version recovery onto a 4.1.x version bootloader. This goes double for 4.4.x version ROM's. If you do , you will brick your tablet. Also, I suggest doing an NVflash backup once you have fastboot up and running BEFORE you flash anything custom. It is a long process with many steps but in the long run you will be thankful you did if you should make a mistake and brick your tablet.
If you have questions, ask but do a lot of research first. All of the info you need is on this forum but you need to spend the time reading and becoming familiar before going forward. We have all been where you are at one time and had to do the research. It is time well spent. Having bricked one smart phone because I got in a hurry I am speaking from experience.
---------- Post added at 08:18 AM ---------- Previous post was at 07:35 AM ----------
Did you even read what he wrote???
Click to expand...
Click to collapse
yes the problem is windows drivers, many TF can't be even unlocked and the latest kingo downloads the drivers and installs them for him, also starting the asus sync app tricks the pc to see the tablet during the root, that is actually an asus problem
spider623 said:
yes the problem is windows drivers, many TF can't be even unlocked and the latest kingo downloads the drivers and installs them for him, also starting the asus sync app tricks the pc to see the tablet during the root, that is actually an asus problem
Click to expand...
Click to collapse
I agree it does appear to be a driver issue. But he stated the following, "Kingo says device not connected with both usb debugging enabled and disabled, even though I can see it on my pc and am able to transfer files." That tells me Kingo didn't install any drivers.
Not sure about the PC being tricked since after I installed the Asus PC sync app the drivers were installed and I was able to uninstall the sync app without losing the drivers. I did a complete nvflash backup, and have installed numerous custom ROM's, from ICS to JB to KK without ever touching Kingo. I've since upgraded to Windows 8 then 8.1 and still am able to do whatever I desire from flashboot and adb, all with the same drivers I originally installed from the Asus PC sync app.
Also, being unlocked and being rooted are two different things entirely. You must be unlocked before you can be rooted but you don't have to be rooted to be unlocked. You can also install a custom recovery or ROM that will take care of rooting once the proper drivers are installed without ever using Kingo, Motochopper or any such app.
Not saying Kingo wouldn't work, but it does seem he has tried that without success.
One clarification to the above post. You do NOT have to be unlocked to root.
Sent from my SM-N900V using XDA Premium 4 mobile app
Reilly1812 said:
One clarification to the above post. You do NOT have to be unlocked to root.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmmmm...not sure about that since I unlocked before I even attempted to get root access. But you can't install custom recoveries, or ROM's without being unlocked. In fact you don't have access to fastboot mode without being unlocked.
I am not even sure what the point of rooting is if you don't want to install a custom recovery and ROM. Sure, you can uninstall system apps and free up some space but only to a point. And the performance is still going to be sluggish. Customization for my tablet has kept it fresh and like new, negating the need to buy a new tablet. Performance is on par with anything I would be interested in buying.
pastorbob62 said:
Hmmmm...not sure about that since I unlocked before I even attempted to get root access. But you can't install custom recoveries, or ROM's without being unlocked. In fact you don't have access to fastboot mode without being unlocked.
I am not even sure what the point of rooting is if you don't want to install a custom recovery and ROM. Sure, you can uninstall system apps and free up some space but only to a point. And the performance is still going to be sluggish. Customization for my tablet has kept it fresh and like new, negating the need to buy a new tablet. Performance is on par with anything I would be interested in buying.
Click to expand...
Click to collapse
100% sure since I have never unlocked and rooted it with Kingo.
Agree that unlocking required for most everything else.
Sent from my SM-N900V using XDA Premium 4 mobile app
Reilly1812 said:
100% sure since I have never unlocked and rooted it with Kingo.
Agree that unlocking required for most everything else.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info! :good:
pastorbob62 said:
Thanks for the info! :good:
Click to expand...
Click to collapse
To answer your earlier question about only rooting...
30+ years in IT, dealing with family, customers and coworkers is more than enough.
Just being able to install ad blockers, apps like Titanium BU and completely debloating the device can be more than enough. This is key when you don't need the hassle of screwing up or bricking your daily driver device(s).
Sent from my SM-N900V using XDA Premium 4 mobile app
Reilly1812 said:
To answer your earlier question about only rooting...
30+ years in IT, dealing with family, customers and coworkers is more than enough.
Just being able to install ad blockers, apps like Titanium BU and completely debloating the device can be more than enough. This is key when you don't need the hassle of screwing up or bricking your daily driver device(s).
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I suppose. But if all you do is root and install ad blockers and Titanium BU Root the odds of bricking your device are slim to none, though as sbdags has pointed out, removing the wrong system files with Titanium BU or any root uninstaller can soft brick the device.
Reilly1812 said:
To answer your earlier question about only rooting...
30+ years in IT, dealing with family, customers and coworkers is more than enough.
Just being able to install ad blockers, apps like Titanium BU and completely debloating the device can be more than enough. This is key when you don't need the hassle of screwing up or bricking your daily driver device(s).
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can softbrick it with TiBu by removing the wrong /system files so do be careful. You would either then have to flash back to stock to repair or unlock it to flash a custom rom. But yes you can achieve some enhancements just by rooting but you can't do much tweaking safely as you have no backup system.
Hello, everyone. A few days ago, I hard-bricked my Galaxy S3 running 4.4.2. I finally got the class 10 SD card and got it working after many tries. My question now is, what is my phone restricted to? Should I be paranoid about it running out of battery or turning it off? Is it safe to restore the device (I don't really want to, but if I must...). The problem obviously started because ex-unlock screwed up my bootloader. Is there any damage left that needs fixing? Thanks, guys!
trevonator126 said:
Hello, everyone. A few days ago, I hard-bricked my Galaxy S3 running 4.4.2. I finally got the class 10 SD card and got it working after many tries. My question now is, what is my phone restricted to? Should I be paranoid about it running out of battery or turning it off? Is it safe to restore the device (I don't really want to, but if I must...). The problem obviously started because ex-unlock screwed up my bootloader. Is there any damage left that needs fixing? Thanks, guys!
Click to expand...
Click to collapse
First of all, nice job un-bricking your phone! You should, if you haven't already, Odin the stock OTA 4.4.2 update MD5. After you've done that, you don't need to worry about rebooting your phone or running out of battery. You can then use your SD card normally, or keep it as a backup in case you hard brick your phone again. With a locked bootloader, you cannot install custom roms or recoveries. You also cannot use any current tool to try and unlock the bootloader. Every tool as of July 29, 2014, will fail and probably hard brick your device. You can still root your phone with Towelroot, that's how I got my phone rooted and it's right as rain. You can also remove carrier bloatware/system apps, use Xposed modules, and do all the other cool things you can do with a rooted device other than installing a custom ROM/Recovery.
redusk said:
First of all, nice job un-bricking your phone! You should, if you haven't already, Odin the stock OTA 4.4.2 update MD5. After you've done that, you don't need to worry about rebooting your phone or running out of battery. You can then use your SD card normally, or keep it as a backup in case you hard brick your phone again. With a locked bootloader, you cannot install custom roms or recoveries. You also cannot use any current tool to try and unlock the bootloader. Every tool as of July 29, 2014, will fail and probably hard brick your device. You can still root your phone with Towelroot, that's how I got my phone rooted and it's right as rain. You can also remove carrier bloatware/system apps, use Xposed modules, and do all the other cool things you can do with a rooted device other than installing a custom ROM/Recovery.
Click to expand...
Click to collapse
Thanks! Do I have to worry about it running out of battery/turning off right now? I have a mac, so if necessary, I'll use Odin in Virtualbox. Thanks again!
trevonator126 said:
Thanks! Do I have to worry about it running out of battery/turning off right now? I have a mac, so if necessary, I'll use Odin in Virtualbox. Thanks again!
Click to expand...
Click to collapse
If you haven't removed your recovery MicroSD from your phone, you should be fine to reboot/run out of juice.
redusk said:
First of all, nice job un-bricking your phone! You should, if you haven't already, Odin the stock OTA 4.4.2 update MD5. After you've done that, you don't need to worry about rebooting your phone or running out of battery. You can then use your SD card normally, or keep it as a backup in case you hard brick your phone again. With a locked bootloader, you cannot install custom roms or recoveries. You also cannot use any current tool to try and unlock the bootloader. Every tool as of July 29, 2014, will fail and probably hard brick your device. You can still root your phone with Towelroot, that's how I got my phone rooted and it's right as rain. You can also remove carrier bloatware/system apps, use Xposed modules, and do all the other cool things you can do with a rooted device other than installing a custom ROM/Recovery.
Click to expand...
Click to collapse
Alright, so I turned off my phone to test and it booted up normally, so I don't think I need to worry about that. I'm borrowing a friend's PC and getting Odin set up.
All right! I'm backing up all my apps to an OTG drive and am about to go for Odin. Pretty nervous haha.
trevonator126 said:
Alright, so I turned off my phone to test and it booted up normally, so I don't think I need to worry about that. I'm borrowing a friend's PC and getting Odin set up.
Click to expand...
Click to collapse
Best of luck!
redusk said:
Best of luck!
Click to expand...
Click to collapse
Thanks! Anything I should know before hand? Do I have to unroot first?
trevonator126 said:
Thanks! Anything I should know before hand? Do I have to unroot first?
Click to expand...
Click to collapse
I don't believe so. It will probably remove your root though, so you'll probably need to re-root after you Odin the stock OTA.
redusk said:
I don't believe so. It will probably remove your root though, so you'll probably need to re-root after you Odin the stock OTA.
Click to expand...
Click to collapse
Good to know! One more thing. My phone will only enter download mode briefly and then restart immediately after into regular mode. So it won't let me go into download mode. If I just reset my phone using the factory reset, will it have the same effect as flashing the exact same rom with Odin?
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
So im out and about ATM and decided to root my S5 again. But i do not have a computer handy and toweleoot doesnt work anymore. Any other options for root without computer? I have attached my phone info. Any information would be helpful.
Since you're on OG1 your only option is a recovery-based root installer like CF auto root. Unless you've already got a custom recovery, you're SOL and will need a PC.
Thanks for the frankness.... figured i was SOL home know though
sephirothkadaj said:
Thanks for the frankness.... figured i was SOL home know though
Click to expand...
Click to collapse
Yeah... it sucks. My S5 went in for service and came back with OG1... so I had not choice but to void knox and root with CF. I did some extensive searching but who knows how long it would take for another method like towel to be found.
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
bump
I don't think this will work unless we get our Bootloader unlocked (which hasn't been done yet as far as i know)
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
this is kind of lame.... why chainfire release a auto root if the thevice have bootloader locked down? and onlockable?
Confused myself
I want to say root is possible, there are tons of sites with instructions: https://www.google.com/search?q=SM-...i57j0j69i60.9343j0j4&sourceid=chrome&ie=UTF-8
Of course, XDA doesn't seem to have a specific G930T thread for rooting with instructions, then see threads like this today. I was all set to give it a try, but unsure if should proceed...
Did find this: http://forum.xda-developers.com/tmobile-galaxy-s7/help/sm-g930t-root-doesnt-void-warranty-t3415936
EDIT: so the one linked in original comment was the bleeding edge root process and seems like had a really high failure rate. Most current I've seen is: http://lifeatsamsung.com/root-t-mobile-galaxy-s7-sm-g930t-2/
Seems a little more clean cut and easy. I'll edit again if I find a newer solution or at least commentary on success/fail
In comments OP posts:
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
Click to expand...
Click to collapse
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse
So the solution and all the fixes, etc is right here: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Worked for me, no problem. Even installed the debloated, deox'd ROM. Unfortunately after root you will need to follow rest of guide, otherwise you will see some lag issues.
On the other side of it, phone is great, fast, if not faster than before, and got root. Let me know if you would like some screenshots proving a TMO phone is rootable or if can answer any questions
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse
I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks
Mordred said:
I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks
Click to expand...
Click to collapse
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root
TH3B0SS said:
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root
Click to expand...
Click to collapse
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...
Mordred said:
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...
Click to expand...
Click to collapse
This means that the only rooting method right now isn't as stable as it would be if it had a unlocked bootloader the root right now will cause some issues but they can easily be fix from some of the steps after rooting guides that are in the xda forums and yes it using a Qualcomm processor Witch is pretty much the snapdragon and there hasn't been any luck this past year of getting the bootloader unlocked for full and smooth rooting I'm really ****ty at explaining sorry if your still lost
The Chainfire method he released does NOT work. I'm not sure why he released it...maybe he knows of a future bootloader unlock that we don't know about.
@troby86 I see you have yours rooted. How did you accomplish this?
Mordred said:
@troby86 I see you have yours rooted. How did you accomplish this?
Click to expand...
Click to collapse
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.
Thank you. Lots to look through.
troby86 said:
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.
Click to expand...
Click to collapse
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?
Mordred said:
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?
Click to expand...
Click to collapse
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...
KillerClaw321 said:
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...
Click to expand...
Click to collapse
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK
Mordred said:
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK
Click to expand...
Click to collapse
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!
KillerClaw321 said:
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!
Click to expand...
Click to collapse
Sorry for being daft... I don't see a driver link and how do I remove the previous version?