Hello everyone! I was hoping to root my Nexus 6 with Android 6.0 on board but I can't seem to find any info on the topic, can anyone help me out??
Thanks!
ichigo663 said:
Hello everyone! I was hoping to root my Nexus 6 with Android 6.0 on board but I can't seem to find any info on the topic, can anyone help me out??
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059493
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Anything that can be done on a Linux system?
Don't use toolkits on marshmallow.
Download TWRP, fastboot flash it, flash custom kernel, and SuperSu 2.52
Sent from my Nexus 6 running cyosp using Tapatalk
Can any of these be done without a computer. I only have my phone
pitbullmommy45245 said:
Can any of these be done without a computer. I only have my phone
Click to expand...
Click to collapse
No you will need a computer to do this. I would not advise modding your device at all if you do not have access to a PC.
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
khw1959 said:
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
Click to expand...
Click to collapse
Dont even get me started on using a kit.
As to why. If something goes wrong you will need a PC to fix it.
khw1959 said:
That root kit worked for me on MM and was easy. Why?
Found this http://forum.xda-developers.com/nexus-6/help/root-computer-t3218176
Click to expand...
Click to collapse
Because if something goes sideways, and eventually it will, youl'll have no clue what it did, and how to fix it.
Nexus phones have open source tools, adb and fastboot, to manipulate them, they are very easy and straightforward to use.
I understand that coming from different phones, that only have hacks and tricks to unlock the bootloader and change the recovery, using tools seems obvious, but with a Nexus it's counterproductive, and makes fixing things so much harder.
Sent from my Nexus 6 running cyosp using Tapatalk
Thank for that insight. I wanted and took the easy/prepared route for unlocking and root of this phone. I was once familiar with manual way when the N2 was unlocked. I got to re-learn again. My last job made me very anal retentive about following instructions, and I think that made the rootkit easy to use. In 3 days I used it when I got with 5.1.1 and yesterday for 6.0. Today I flash Roms to find the one I like.
ichigo663 said:
Anything that can be done on a Linux system?
Click to expand...
Click to collapse
Adb and fastboot work on linux.
Any easy way to root 58r ??
Exqctly like K and N. Flash modified boot.ing, and flash SuperSu.zip in TWRP.
Sent from my Nexus 6 running cyosp using Tapatalk
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
ghost010 said:
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
Click to expand...
Click to collapse
Because at one time it did require a kernel change to get root.
ghost010 said:
Why do people keep saying you need a custom kernel??? BTW, used nexus root toolkit on the K build without problems, no luck on R(never had N) but the tool got updated.... However... I would not be using any thing chainfire Su related sinds it got sold out.
Click to expand...
Click to collapse
Because you needed a custom boot.img to root 58K too. It will either contain a modified kernel with SELinux set to permissive (I've patched mine by hand, so I know what I'm talking about), or contain an updated sepolicy binary to allow su to work. Also since you said you didn't have red triangle, it means your fstab.shamu was also replaced with one with disabled verity.
So. Don't use rootkits. If you do use rootkits and discover you don't know what's happening, at least please don't keep correcting those who try to help you.
scryan said:
Adb and fastboot work on linux.
Click to expand...
Click to collapse
I was hoping that someone would answer this. Flashing files and rooting on Linux is MUUUUCH easier than Windows. Why? No need for special drivers to recognize your device.
Even better, if you try to run a adb/fastboot command without having them installed, Linux will tell you the actual command for you to type and download/install them...all within the command window.
This might sound confusing, but it is really easy and seamless, in my opinion.
AarSyl said:
I was hoping that someone would answer this. Flashing files and rooting on Linux is MUUUUCH easier than Windows. Why? No need for special drivers to recognize your device.
Even better, if you try to run a adb/fastboot command without having them installed, Linux will tell you the actual command for you to type and download/install them...all within the command window.
This might sound confusing, but it is really easy and seamless, in my opinion.
Click to expand...
Click to collapse
Most of what you said depends on your distro.
On Arch you definitely need to add u-dev rules for the phone to be noticed, and if you dont have them installed and you try to run it, it won't tell you how to download.
But.... If you install via a package manager it will be automatically added to your path
Also, I have NEVER downloaded drivers for my phone in windows, and never needed to.
That's good to know. I should've added that I use Ubuntu as my distro, and I love it.
Related
I update to FRG83D and I guess i lost root. I attempted to restore flash clock world mod again but .nothing happens when i confirm I tried to do a backup from Titanium backup and of course it says i'm not rooted. Then I tried to go into Superuser app and it asked me to update. I attempted to and I got an error the su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Sorry for the long winded explanation, but i'm totally frustrated. I've been trying to fix this for 2hrs. Oh yeah I originally got root using universal androot and it still says im rooted. I clicked unroot but it doesn't work. I'm confused cuz androot says i'm rooted, but Superuser and Titanium backup says i'm not.
PLEASE HELP MEEE!!! I would like to get back cmod 6.1
was this:
cmod 6.1 rc1-n1
clockmod 2.5.1
kernel: 2.6.35.7
Build num: frg83
Now i'm this:
Android ver: 2.2.1
Kernel ver: 2.6.32.9-27240
Baseband ver: 32.36.00.28U4.06.00.12_7
Build num: FRG83D
fastboot oem unlock
Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
crachel said:
fastboot oem unlock
Click to expand...
Click to collapse
lol damn you evil bastards
Have some pity for the newbs
Newbs should start reading Wiki instead of wasting hours on irrelevant stuff
danger-rat said:
Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thank you danger-rat. I'm back to stock frg83. It only took about 10mins. Now I'm trying figure out how to get back to root. None of the one click methods seem to be working. Superoneclick, z4root, androot. Once again Thank YOU
Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.
dls5375 said:
Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.
Click to expand...
Click to collapse
Is it the case for a Nexus One replacement unit that has never been rooted or altered in any way? I got it with FRG83 and installed FRG83D as soon as I received it. I tried SOC method but it was stuck on 'waiting for device' message. Not sure if it is because of an old XP machine or HTC Evo cable I was using.
Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.
Jack_R1 said:
Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.
Click to expand...
Click to collapse
I tried both SOC 1.5.1 and 1.5.5 with .net 2.0.5x in the XP machine. I just used the files included in the zip, isn't it that it has latest Nexus One drivers too? Sorry, I am a Mac,Linux guy and not much experience with ADB stuff on Windows.
It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.
Jack_R1 said:
It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.
Click to expand...
Click to collapse
Thank you! I guess I have no other option but to install Windows on my Mac. I was feeling lucky and I thought Linux or Mac can use SOC but it is proving difficult and I haven;t come across a single reply who stated success on Linux/Mac!
Uh, why SOC? Use any of the others you just run directly on the phone..
khaytsus said:
Uh, why SOC? Use any of the others you just run directly on the phone..
Click to expand...
Click to collapse
They don't exist for FRG83D just yet and I am not sure if we can downgrade to FRF91 or some other firmware without unlocking bootloader.
You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.
Jack_R1 said:
You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.
Click to expand...
Click to collapse
Is it true for Mac too? My previous attempts with VMWare and Parallels failed while trying to use USB at low level. I guess it is worth a shot, thank you!
when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.
dls5375 said:
when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.
Click to expand...
Click to collapse
Tried that already, no go..
kkiran said:
Tried that already, no go..
Click to expand...
Click to collapse
With all the time wasted searching for other methods, you would have had root on your device already if you just did it manually. It is so simple, takes like 20 mins, and it doesn't require a Windows PC.
I really don't understand why people search for so long for a "1-click" when doing it manually doesn't take that much more effort.
Rooting so is simple with the binaries available:
1) Put rageagainstthecage on your device, change permissions to allow it to run, run it, and presto, it gives you a root shell.
2) Now that you have a root shell, all you have to do is put su in the /system/bin directory, change the permissions so that it can run, and presto, you have root.
And given that rageagainstthecage exploits a vulnerability in the way adb works, this method will work for all devices without a NAND lock.
Rageagainstthecage so easy a caveman can do it.
Sent from my Nexus One
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Nexus 7 toolkit auto update v4.3.4
NinjaMogglet said:
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Click to expand...
Click to collapse
Can anybody help please?,
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Confirmation
Logan_M said:
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Click to expand...
Click to collapse
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
NinjaMogglet said:
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
Click to expand...
Click to collapse
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Unfortunately having the SDK does not mean I can actually use it
I got in over my head, hence trying to learn/read about it it on XDA
I found the thread that appeared to offer what I want,
a toolkit that I should be able to use to unlock/root with.
Thanks
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
you dont have to know how to use the entire SDK, all you need to do is be able to follow directions. every nexus is rooted the exact same way. the only thing the toolkit does is hide the commands. you could take the few minutes to learn these commands
fastboot oem unlock
fastboot flash recovery nameofrecoveryfile.img
reboot to recovery
adb push SuperSU.zip /sdcard/ (or /data/media, whatever)
flash supersu.zip with your custom recovery....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pirateghost said:
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
NinjaMogglet said:
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
Click to expand...
Click to collapse
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
All Understould
Pirateghost said:
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
Click to expand...
Click to collapse
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
not sure why you need to go anywhere other than right here on XDA....
theres a freakin sticky for it even...
http://forum.xda-developers.com/showthread.php?t=2150661
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Still not clear??
smt8544 said:
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Click to expand...
Click to collapse
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
NinjaMogglet said:
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
Click to expand...
Click to collapse
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Thanks
Pirateghost said:
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Click to expand...
Click to collapse
Thanks...
I did not ignore your link, I read all the pages.
Especially the one's that pointed out the ommisions, like un-lock first, and some of the key presses.
I will get back to this when I'm bright eyed, not 01:25 in the morning.... Just in case.
Thanks again
Like the title says im after the system dump for this device, it has already been leaked as a few sites are reporting having it so if anyone has it or knows where to find it please share so i can extract wallpapers sounds apps etc to share
Any advice on how to do a system dump? I should have my First in a few days.
fungflex said:
Any advice on how to do a system dump? I should have my First in a few days.
Click to expand...
Click to collapse
I have mine right now but I don't know how to go about dumping the system.
rooobbbbb said:
I have mine right now but I don't know how to go about dumping the system.
Click to expand...
Click to collapse
Do you have the Android SDK installed and are familiar with using adb?
dstaley said:
Do you have the Android SDK installed and are familiar with using adb?
Click to expand...
Click to collapse
Absolutely to both.
rooobbbbb said:
I have mine right now but I don't know how to go about dumping the system.
Click to expand...
Click to collapse
Could you check to see if it's possible to disable LTE? or did AT&T do something to prevent that as it does on every phone but the iPhone?
Sent from my SAMSUNG-SGH-I747
rooobbbbb said:
Absolutely to both.
Click to expand...
Click to collapse
IIRC, you should just be able to `adb pull /system` to get the important bits. It's not a full dump, but I think you need root level access for that. And the only way I know how to get root access is to flash a zip through recovery, and TWRP/CWM hasn't yet been released for the First.
I couldn't disable LTE but I don't see why I would, the battery is awesome. Can't dump anything right now I'm out. Am I the only person with this phone already?
Sent from my HTC first using xda premium
rooobbbbb said:
I couldn't disable LTE but I don't see why I would, the battery is awesome. Can't dump anything right now I'm out. Am I the only person with this phone already?
Sent from my HTC first using xda premium
Click to expand...
Click to collapse
Well, considering that it doesn't come out until tomorrow, I'd be willing to say yes.
I was wondering why no one was posting anything about it. Lol
Sent from my HTC first using xda premium
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
nuclear_eclipse said:
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
Click to expand...
Click to collapse
Do you have a retail AT&T First? Can you confirm that retail AT&T First is unlockable via htcdev?
Sent from my SAMSUNG-SGH-I747
Yes, this is a retail model, and yes, the bootloader was unlocked via htcdev.com.
nuclear_eclipse said:
So in all seriousness, I have the First, I have the bootloader unlocked via htcdev.com, I'm rather familiar with adb and fastboot, and I would love to upload a system dump if someone can tell me what commands to run.
I'm trying `adb pull /system` right now, but it's getting "permission denied" on some files, so I don't know how useful that will be. I've also tried looking around online, but just about everything I find is assuming that you already have a custom recovery or a rooted system; nothing wants to tell me how to get myself to that state from scratch, and I'm very hesitant to just start flashing stuff at random without a proper image dump to fall back to.
Anyone have a good idea where to start?
Click to expand...
Click to collapse
Humor me for a moment, if you will. Connect your device to your computer and run `adb root`. You should get a permission denied error of some sorts. I'm curious to see if Facebook is shipping with root enabled.
dstaley said:
Humor me for a moment, if you will. Connect your device to your computer and run `adb root`. You should get a permission denied error of some sorts. I'm curious to see if Facebook is shipping with root enabled.
Click to expand...
Click to collapse
Code:
[email protected] ~/first » adb root
adbd cannot run as root in production builds
^C
nuclear_eclipse said:
Code:
[email protected] ~/first » adb root
adbd cannot run as root in production builds
^C
Click to expand...
Click to collapse
That's what I figured would happen! It looks like this may be an option to root the 4.1.2 build. It worked on the One S and the Nexus 7, which gives me hope.
dstaley said:
That's what I figured would happen! It looks like this may be an option to root the 4.1.2 build. It worked on the One S and the Nexus 7, which gives me hope.
Click to expand...
Click to collapse
No good, but thanks for providing the link. The only shot we have left is waiting for the RUU to be leaked so we can pull recovery out of it, and get a CWM/TWRP made from it.
What is RUU and how does that help us? Sorry, just coming from a Nexus-only world, so I'm not familiar with modern HTC/Samsung devices.
Sent from my HTC first using xda premium
RUU stands for ROM Update Utility and is a Windows executable file that can flash and restore a HTC device. There are ways to extract binaries from this file, and if there are no root exploits that will work on this phone, we will need to extract the original recovery.img from that RUU to build a custom recovery, in which at that point allows us to flash SuperUser.apk to get root.
TRF-Inferno said:
RUU stands for ROM Update Utility and is a Windows executable file that can flash and restore a HTC device. There are ways to extract binaries from this file, and if there are no root exploits that will work on this phone, we will need to extract the original recovery.img from that RUU to build a custom recovery, in which at that point allows us to flash SuperUser.apk to get root.
Click to expand...
Click to collapse
RUUs for the HTC One were first available on March 26, just about a month after its announcement (and, oddly, a few weeks before it's general release). Since these have to be leaked by HTC, there's no telling when we will see those. Is there any chance another root exploit exists in stock Android 4.1.2 that we could exploit in order to get root?
so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing
Bfitz26 said:
so i am trying to root using this io method i believe it is called i thought i had adb installed but it seems as though it is not. i have tried using a few methods here on xda none seem to work restarted pc several times as well as phone run adb devices and my devices isn't there in fact i got invalid command or whatever. ran the root tool same thing happend yes i am usb debugging enabled, ethernet mode. does anyone have a good guide to get adb to install correctly on windows 8.1 nothing
Click to expand...
Click to collapse
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?
Bfitz26 said:
ok well i got adb working showed device but when i run root script it says push any key to continue i click it and it says not a valid command or something and exits? not sure what the deal is here a little frustrating i am a bit confused why i haven't seen this talked about any where?
Click to expand...
Click to collapse
What exactly did it say?
TheOriginalKyle said:
What exactly did it say?
Click to expand...
Click to collapse
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.
Bfitz26 said:
thanks anyway i got it so my questions at this point are: our bootloader is locked on 12b right and is that just stopping us from kernels? last time i remember a locked bootloader you needed a safestrap to flash anything so i am a bit baffled. 2 best way to get custom recovcery what is the best least issues and most compatiable, i have seen some failed efs partitions causing bricks and can we flash any rom placed here in the developement section on any softwasre version with any recovery.thanks for any and all help anyone can give. i have searched the forums just keep getting mixed awnsers to my questions just want to make sure i am doing the right thing.
Click to expand...
Click to collapse
1. I believe our bootloader is locked, I don't think safe strap is necessary just make a backup before you flash anything too risky
2. For the custom recovery this method seems to work the best http://forum.xda-developers.com/showthread.php?t=2449670 it also explains #1 better. You can also flash Clockwork Recovery the difference is mainly personal preference. To get the latest TWRP on you'll need to flash the .img then when it's all set up flash the .zip.
3. For the failed efs partitions here's a link to back that up (I had no idea that was a problem). http://forum.xda-developers.com/showthread.php?t=2451390 I only used this when I flashed a different radio, also the only brick that I know of is with FreeGee on 12b but that's the lazy way and who knows maybe he fixed it.
4. ROM's will usually tell you what is compatible and what isn't, if you have the latest TWRP or CRP you should be fine on 12b just read the instructions and scan the comments for issues.
Glad I could help
Thanks!
Sent from my VS980 4G using Tapatalk
Got my new nexus 6 today
updated to android 5.1.1
am from touchwiz most of my life
any apps i sud be using
and how to root this thing?
i mostly used odin all my life guess no use of that here anymore
so any guidance is highly appreciated....
advance thanks
MD0038 said:
Got my new nexus 6 today
updated to android 5.1.1
am from touchwiz most of my life
any apps i sud be using
and how to root this thing?
i mostly used odin all my life guess no use of that here anymore
so any guidance is highly appreciated....
advance thanks
Click to expand...
Click to collapse
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
http://forum.xda-developers.com/showthread.php?t=2948481
Face_Plant said:
http://forum.xda-developers.com/showthread.php?t=2948481
Click to expand...
Click to collapse
will go through thee whole thing and understand if not hope you al help me a bit
XxCyberHackerxX said:
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
Click to expand...
Click to collapse
ok, or you can root your device the right way, within 3-4 minutes. where is the guidance in using a tool kit? considering you learn absolutely zero from it, and toolkits occasionally mess things up as well.
simms22 said:
ok, or you can root your device the right way, within 3-4 minutes. where is the guidance in using a tool kit? cinsidering you learn absolutely zero from it, and toolkits occasionally mess things up as well.
Click to expand...
Click to collapse
Very true. But he indicated he was a novice so the toolkit would guide him through the process
XxCyberHackerxX said:
Very true. But he indicated he was a novice so the toolkit would guide him through the process
Click to expand...
Click to collapse
Toolkit is good but i want to learn all things
XxCyberHackerxX said:
Very true. But he indicated he was a novice so the toolkit would guide him through the process
Click to expand...
Click to collapse
tool kits are not for novices, at all. they do not guide you through anything. toolkits are fine to use, when you know whats going on. but when you dont, you arent taught a single thing.
XxCyberHackerxX said:
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
Click to expand...
Click to collapse
DO NOT use the toolkit till unlocked and know how to use manual fastboot. Will not know why toolkit failed and will not know how to recover as it will take fastboot to recover. I did Odin also. It was a dependable tool. Fastboot is the old tried and true Nexus, HTC tool. Virtually unbrickable. The toolkit can brick you and will require fastboot knowledge to fix. Fastboot update only takes 2-3 minutes once set up and know what you are doing.
Just to echo what everyone else is saying, toolkits are great but only use them if you understand what they're doing. Using fastboot the first time.round is essential for learning.
All.threads are in nexus 6 general > sticky roll-up
Including my adb and fastboot thread,. Which is good for noobs.
HaHaa. I actually had more problems and failed flashes with Odin and "the toolkit". Never had a fail with fastboot.
Toolkits.... Not. Do it manually with all the proven guides posted!
MD0038 said:
and how to root this thing?
Click to expand...
Click to collapse
There are already advices given by real experts.
I humble add some " why's " not to start rooting for the first time with a toolkit.
A. There are so many options; it easy to make a mistake.
B. Toolkits use scripts and once started you are not fast enough to stop the process when you do something wrong.
C. When you know how to use command lines
with adb and fastboot, you will be prepared for toolkits.
D. You will find here complete rooting guidelines in sticky threads. Read them.
Nice rooting!
Thanks everyone for overwhelming support read half of the thread will do rest of the work tomorrow some assignments to do
Sent from my Nexus 6 using Tapatalk