Database Info

Added line to build.prop....now bricked?

So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running

S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?

Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?

Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things

S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need

Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?

S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?

Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.

Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.

XDA Avengers I need help! (Stuck on logo)

Hi XDA.
This was a thread I started last night ( http://forum.xda-developers.com/oneplus-one/help/one-chinese-import-flash-to-bacon-issue-t2923211) and where it ends is where I realised my device wasn't unlocked. "yeah I know"
So I downloaded and followed these steps shown on this great tutorial https://www.youtube.com/watch?v=5O2e_R_TbVg
But now my phone appears to have no OS. It wont show up as a USB device to allow me to put a zip across to install.
I have learnt alot this evening and am enjoying the process and this is the last step....
If I haven't bricked my phone!
Any help much appreciated.

That's the video that gets you to use a toolkit, right? My first piece of advice: ditch the toolkit and never use one again. They're more trouble than they're worth and clearly cause problems. Plus doing things manually allows you to actually learn a great deal of crucial stuff that you really need to know. Anyway, please provide some more information on your device, is the bootloader unlocked now? Do you have TWRP recovery installed?
Transmitted via Bacon

Hi and thanks for replying. I followed the guide and unlocked and installed TWRP and can access it easily but when tring to re boot the device it just stays on the +1 logo.
I have subsequently tried unlocking again if that was the problem.

Boot the phone into TWRP, go into the wipe menu and perform a factory reset, then reboot the phone.
Transmitted via Bacon

Ok just tried a factory reset and it failed stating among many things.
E:Unable to mount '/data
E:Unable to mount storage
Also the first line was E:could not mount / data and unable to find cry pto folder.

It might be time to start fresh, you're gonna have to try flashing the fastboot images I think.
Transmitted via Bacon

Ok thanks again for your support.
With this in mind can you please give me a nod in the right direction on how to do this please. I appreciate im a little out of my depth here. Swimmimg in deep android.

http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Follow step 8.

Yep, that's the one. Keep in mind though that I haven't yet updated that to suit the latest version (38R), so you can download the latest version from here:
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip
And then modify the last command to suit.
Transmitted via Bacon

Ok I'm going in! Will follow those 8 steps however the phone doesn't show as a USB device any more so will this work?

Really sorry guys but step two is a no-go as the device wont boot to enable me to get into dev options.

jnapier10 said:
Really sorry guys but step two is a no-go as the device wont boot to enable me to get into dev options.
Click to expand...
Click to collapse
All you need to worry about is section 8. They're not steps that need to be followed in sequence, they're separate sections.
Transmitted via Bacon

Ok that's a relief. I have completed step one and it says its unlocked.
Ok so im downloading the OS you suggested but cannot get the phone to come up as a USB device to put the new OS onto the internal memory.

jnapier10 said:
Ok that's a relief. I have completed step one and it says its unlocked.
Ok so im downloading the OS you suggested but cannot get the phone to come up as a USB device to put the new OS onto the internal memory.
Click to expand...
Click to collapse
You don't put it on the phone, you need to put it in your adb/fastboot directory on your PC as per the directions in section 8.
Transmitted via Bacon

Yip my bad. Sorry morning eyes and nerves dont mix.
Right installed fast-boot to my desktop and unzipped all files into fast-boot folder.
Ok lets see what happens

Hmmm

jnapier10 said:
Hmmm
Click to expand...
Click to collapse
If you follow the correct instructions you'll see that it doesn't even mention this command...
ONLY follow the instructions in section 8.

Ok everything was going great but on the final step I received this. Thanks again so much for your help, I really appreciate it. I think its close to being sorted.

Gamm86 said:
If you follow the correct instructions you'll see that it doesn't even mention this command...
ONLY follow the instructions in section 8.
Click to expand...
Click to collapse
Yip im again being a chief idiot. I realised just after I had posted.

jnapier10 said:
Ok everything was going great but on the final step I received this. Thanks again so much for your help, I really appreciate it. I think its close to being sorted.
Click to expand...
Click to collapse
Make sure the zip file is in the fastboot folder aswell and make sure the name of the file you use in the command is identical to the name of the zip file.
After the final step your phone should boot again.

[Q] How to root this device without deleting any data?

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.

[Q] Total Noob, trying to brick my phone

Hi everyone,
I am new to android mods. I just bought a used vzw M8 running 4.4.4. I unlocked and got S off using sunshine. Rooted with WS2, and verified. Installed SuperSU. Stock otherwise. I have installed the SDK on my laptop. I can't get any devices to show up when i use the adb devices command.
I am trying to figure out how to disable the OTA for Lollipop. Does anyone know if the OTA will re-lock or bypass my root? Can you help me disable if it is an issue?
Eventually, I'd like to go to a different (cleaned up) ROM and 5.X, but i need to make sure the evil red monster doesn't mess up my work first. I have spent several hours searching the forums, and have made some progress. If there are any detailed posts to point me to, I'd appreciate any and all help.
Thank you,
Dustin

Did you install the HTC drivers? If not install HTC sync manager (I think that's the name) and it'll install them for u then u can uninstall HTC sync manager and you should get adb to recognize your device. Ota will not relock your device. It will take off root tho. But you can just flash custom recovery and flash su in there. I'd suggest since your s off to flash dottats s off 5.0.1 ruu over in the development section once you get adb working. It is also pre rooted and will get up and running on lollipop.
Save the Manuals!!!

dustinoob said:
Hi everyone,
I am new to android mods. I just bought a used vzw M8 running 4.4.4. I unlocked and got S off using sunshine. Rooted with WS2, and verified. Installed SuperSU. Stock otherwise. I have installed the SDK on my laptop. I can't get any devices to show up when i use the adb devices command.
I am trying to figure out how to disable the OTA for Lollipop. Does anyone know if the OTA will re-lock or bypass my root? Can you help me disable if it is an issue?
Eventually, I'd like to go to a different (cleaned up) ROM and 5.X, but i need to make sure the evil red monster doesn't mess up my work first. I have spent several hours searching the forums, and have made some progress. If there are any detailed posts to point me to, I'd appreciate any and all help.
Thank you,
Dustin
Click to expand...
Click to collapse
Check this thread out for blocking the OTA http://forum.xda-developers.com/verizon-htc-one-m8/help/block-ota-updates-t2871520 It is also my understanding that just being rooted will cause the OTA to fail. I may be wrong about that, however.

MotoTurbo said:
Did you install the HTC drivers? If not install HTC sync manager (I think that's the name) and it'll install them for u then u can uninstall HTC sync manager and you should get adb to recognize your device. Ota will not relock your device. It will take off root tho. But you can just flash custom recovery and flash su in there. I'd suggest since your s off to flash dottats s off 5.0.1 ruu over in the development section once you get adb working. It is also pre rooted and will get up and running on lollipop.
Save the Manuals!!!
Click to expand...
Click to collapse
I did install the drivers exactly the way you suggest. My computer recognizes the phone as a drive. I just can't get it to show up on ADB. Thank you for the suggestion on the ruu. I may just let the OTA come though today to get rid of the message. Then, run the ruu when I figure this out more.

BladeRunner said:
Check this thread out for blocking the OTA http://forum.xda-developers.com/verizon-htc-one-m8/help/block-ota-updates-t2871520 It is also my understanding that just being rooted will cause the OTA to fail. I may be wrong about that, however.
Click to expand...
Click to collapse
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.

dustinoob said:
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.
Click to expand...
Click to collapse
Maybe try dottats HTC fastboot exe. Its in the main ruu thread in general section. Its in 2nd or 3rd post I believe And check adb there, might be the sdk
Save the Manuals!!!
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
Here's the link to post
http://forum.xda-developers.com/showthread.php?p=56890497
Save the Manuals!!!

Makes me want to brick mine too sometimes.
dustinoob said:
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.
Click to expand...
Click to collapse
Somethings just can't be explained. Check this out. I have to use my 6 year old laptop with AMD Phenom II x4 because my desktop Intel i5-3570 cant send sh1t to my phone. It's always something. After trying to figure it out for hours, I gave into the PC Gods. I'm sure Dottat could solve it in 2 mins or less.
I only post to let you know others share your frustration. Honestly, if I didn't have an unlimited data plan, I might not even bother with modding anymore. I will follow your post, waiting for a solution too.

dustinoob said:
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.
Click to expand...
Click to collapse
To use adb/htc_fastboot with the copy i have on the thread you were already linked all you need to do is unzip the file. You don't install adb/htc_fastboot... You just unzip and use. So long as your drivers are installed correctly.

Help with root, new to HTC
Hi,
I have been on Samsung since ....well forever...lol. Can someone point me to the noob thread to unlock and root? I heard of this Sunshine thing...does that do it all?
Thanks...and sorry for the noobness.

handymanxda said:
Hi,
I have been on Samsung since ....well forever...lol. Can someone point me to the noob thread to unlock and root? I heard of this Sunshine thing...does that do it all?
Thanks...and sorry for the noobness.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=51395737
Save the Manuals!!!

dottat said:
To use adb/htc_fastboot with the copy i have on the thread you were already linked all you need to do is unzip the file. You don't install adb/htc_fastboot... You just unzip and use. So long as your drivers are installed correctly.
Click to expand...
Click to collapse
Thank you, dottat. I have installed and re-installed the driver. My computer can see my phone, and pull it up as a disk drive. I can open the SDK and ADB. In the CMD window, when I type "adb devices", it starts the daemon successfully. Then, under list of devices, it is blank. Any ideas? Could i have downloaded the wrong SDK/ADB package and need to get yours? I'm really green with this software and Linux in general, so I may be missing something. I'm hoping I can get comms worked out and load your RUU file soon. Can I go ahead and take the 5.0 OTA without worry? I have root, s off, and BL unlock. SuperSU fails to update.
THANK YOU!!!

Do you have Android Debugging checked under developer settings?
Save the Manuals!!!

MotoTurbo said:
Do you have Android Debugging checked under developer settings?
Save the Manuals!!!
Click to expand...
Click to collapse
That was it!! Thank you!

dustinoob said:
That was it!! Thank you!
Click to expand...
Click to collapse
Yes! Yeah just remembered that this morning haha. Glad you got it working
Save the Manuals!!!

MotoTurbo said:
http://forum.xda-developers.com/showthread.php?p=51395737
Save the Manuals!!!
Click to expand...
Click to collapse
Thanks! Looks like a lot of work...it's because Verizon locked things down? So am I right in saying I need to use Sunshine to get S-Off then do that Bootloader Unlock? Or do I need to unlock the bootloader?

handymanxda said:
Thanks! Looks like a lot of work...it's because Verizon locked things down? So am I right in saying I need to use Sunshine to get S-Off then do that Bootloader Unlock? Or do I need to unlock the bootloader?
Click to expand...
Click to collapse
What Android version you running?
On 4.4.3 and over sunshine will s off and unlock bootloader together, but its a 50/50 chance. I personally used firewater and weaksauce but I was on 4.4.2 when I did it but VZW closed that exploit in 4.4.3.
Save the Manuals!!!

MotoTurbo said:
What Android version you running?
On 4.4.3 and over sunshine will s off and unlock bootloader together, but its a 50/50 chance. I personally used firewater and weaksauce but I was on 4.4.2 when I did it but VZW closed that exploit in 4.4.3.
Save the Manuals!!!
Click to expand...
Click to collapse
It is 4.4.3. Firewater chugged and spit...LOL...will try Sunshine and see if that unlocks the bootloader as well. Thanks!

Does This CF-Auto Root Trully Works ON G930T

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?