Develop Bugs

[Q] Easy Root

Does anyone know is there a one click root app out there for the GN yet? Will Unrevoked be doing a program for this? If not is there an word of one being done? It was made so easy for my DINC I would love to get my free tethering back.

here lets look at a pinned topic from the Gnex General board
http://forum.xda-developers.com/showthread.php?t=1338442
and one from the dev board
http://forum.xda-developers.com/showthread.php?t=1360413

Goat_For_Sale said:
here lets look at a pinned topic from the Gnex General board
http://forum.xda-developers.com/showthread.php?t=1338442
and one from the dev board
http://forum.xda-developers.com/showthread.php?t=1360413
Click to expand...
Click to collapse
Not really what Im talking about since its "it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash". I dont want to do this everytime I reboot plus it doesnt unlock the bootloader. Im wanting to know about a simple one step app that is permanent.

I think this is another case for a split forum. Unfortunatly the verizon nexus is different than the non-verizon.
I too am looking to root to get back my 3rd party wifi tether. as of now, I have found nothing that makes me think it is possible "today". Verizon has somehow locked the 3rd party apps. I am not a programer, or claim to be one; but I follow instructions well.
People need to say, I have verizon and I need this....XDA is world wide and people assume that when you are asking a question about a GN you are asking about the version they have and this forum is loaded with non-LTE information, with some LTE info hear and there.
If I find a LTE easy root I will gladly post it here

the insecure doesnt really matter. For what youre talking about it is a permanent flash you will not neet to re root everytime you turn on your phone. I superbooted yesterday. Im currently rooted and my phone has probably been restarted 15 times

It's pretty easy to manually root the LTE GN. The follow steps are for Windows.
Download this zipped package. It contains adb, fastboot, and Paul's unsecured boot.img that will install su and Superuser.apk for you.
Download ADB USB Drivers.
Step 1.) Unlock your bootloader. Put your phone into fastboot mode and install the ADB USB Drivers. Run fastboot-windows from the zipped package
Code:
fastboot-windows oem unlock
Step 2.) Put your phone back into fastboot mode if it reboots after unlocking. Then boot Paul's boot.img
Code:
fastboot-windows boot boot.img
Step 3.) Voila you're rooted... easy as pie.

ac7822 said:
the insecure doesnt really matter. For what youre talking about it is a permanent flash you will not neet to re root everytime you turn on your phone. I superbooted yesterday. Im currently rooted and my phone has probably been restarted 15 times
Click to expand...
Click to collapse
mayor bloom said:
I think this is another case for a split forum. Unfortunatly the verizon nexus is different than the non-verizon.
I too am looking to root to get back my 3rd party wifi tether. as of now, I have found nothing that makes me think it is possible "today". Verizon has somehow locked the 3rd party apps. I am not a programer, or claim to be one; but I follow instructions well.
People need to say, I have verizon and I need this....XDA is world wide and people assume that when you are asking a question about a GN you are asking about the version they have and this forum is loaded with non-LTE information, with some LTE info hear and there.
If I find a LTE easy root I will gladly post it here
Click to expand...
Click to collapse
That would be great if you find anything. As for saying that the superboot I guess ill give it a try. The post says that it will unroot (not sure how that works) on every reboot. Maybe im just not understanding it correctly

silow said:
It's pretty easy to manually root the LTE GN. The follow steps are for Windows.
Download this zipped package. It contains adb, fastboot, and Paul's unsecured boot.img that will install su and Superuser.apk for you.
Download ADB USB Drivers.
Step 1.) Unlock your bootloader. Put your phone into fastboot mode and install the ADB USB Drivers. Run fastboot-windows from the zipped package
Code:
fastboot-windows oem unlock
Step 2.) Put your phone back into fastboot mode if it reboots after unlocking. Then boot Paul's boot.img
Code:
fastboot-windows boot boot.img
Step 3.) Voila you're rooted... easy as pie.
Click to expand...
Click to collapse
Do you happen to have anything for us MAC users?? I'm really surprised I can't seem to find anything concrete for it.....

AlpineM3 said:
Do you happen to have anything for us MAC users?? I'm really surprised I can't seem to find anything concrete for it.....
Click to expand...
Click to collapse
I followed this tutorial to set up fastboot and adb on my mac:
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
Then you just need the boot.img linked above and use the same commands(except use the mac fastboot that you set up earlier)
There were no drivers needed to be installed.

jhuynh said:
I followed this tutorial to set up fastboot and adb on my mac:
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
Then you just need the boot.img linked above and use the same commands(except use the mac fastboot that you set up earlier)
There were no drivers needed to be installed.
Click to expand...
Click to collapse
What about to unlock the boot loader? Thanks btw
Sent from my Galaxy Nexus using xda premium

AlpineM3 said:
What about to unlock the boot loader? Thanks btw
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The commands are the exact same as the commands for windows except your fastboot probably isn't called fastboot-windows.

I found this guys and it seems to be the best and most straight forward guide to rooting the GN Ive found. Take a look http://forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/141563-guide-how-unlock-bootloader-root-verizon-galaxy-nexus.html
Also has a mac version along with video and other information.

AlpineM3 said:
What about to unlock the boot loader? Thanks btw
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Once you have fastboot loaded and the drivers, it's just a matter of booting to the bootloader and doing a fastboot OEM unlock. It should be no different.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
Kipphh said:
Does anyone know is there a one click root app out there for the GN yet? Will Unrevoked be doing a program for this? If not is there an word of one being done? It was made so easy for my DINC I would love to get my free tethering back.
Click to expand...
Click to collapse
OP:
No one will likely be doing a one-click system since this is a Nexus. Manual root is superior, and it is incredibly easy with some light knowledge of fastboot and adb. Honestly, I feel like if you cannot find your way around rooting a Nexus, perhaps you should not root it. An understanding of the system really comes in handy if you face issues.
Just unlock the bootloader using fastboot (there are instructions for this everywhere), then boot to an insecure boot.img of some sort (superboot is an option, I used koush's ClockworkMod image). Once you have this, you can use adb to push superuser to the system partition. If you overwrite the recovery, don't worry, because there is a script that will overwrite with the stock recovery after each boot.
If you want ClockworkMod permanently installed (as on your DINC, I presume) you will have to rename/remove the script. I have not done this, as I just re-flash ClockworkMod every time I alter something.
Hope that helps.

kekspernikai said:
Once you have fastboot loaded and the drivers, it's just a matter of booting to the bootloader and doing a fastboot OEM unlock. It should be no different.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
OP:
No one will likely be doing a one-click system since this is a Nexus. Manual root is superior, and it is incredibly easy with some light knowledge of fastboot and adb. Honestly, I feel like if you cannot find your way around rooting a Nexus, perhaps you should not root it. An understanding of the system really comes in handy if you face issues.
Just unlock the bootloader using fastboot (there are instructions for this everywhere), then boot to an insecure boot.img of some sort (superboot is an option, I used koush's ClockworkMod image). Once you have this, you can use adb to push superuser to the system partition. If you overwrite the recovery, don't worry, because there is a script that will overwrite with the stock recovery after each boot.
If you want ClockworkMod permanently installed (as on your DINC, I presume) you will have to rename/remove the script. I have not done this, as I just re-flash ClockworkMod every time I alter something.
Hope that helps.
Click to expand...
Click to collapse
Well Im happy to say your wrong. Here is a link to a one step root.
http://forums.androidcentral.com/ve...ks/147177-wugs-galaxy-nexus-root-toolkit.html

Very weird root issue

When I first bought my ZL, I rooted the phone using binary4 V27 on superuser mode and that was very fast and simple. I could modify system files and do everything.
One day using my ultimate stupidness, I updated the firmware to 10.1.1.....253 then I did factory reset without doing a backup for my root.
Right now, when I go to settings -----> about ----> I get Kernal version 3.4.0 with android version 4.1.2 but unfortunately It seems like I don't have a rooted phone + I am unable to do any function of a rooted phone like modifying system files or ....etc .
I've tried million ways such as:
1- rooting the phone using the same method --------> the result is stucking at the wight screen and nothing happened.
2- Using motochopper method --------> doesn't work
3- Using the method of installing Android SDK and using the command prompt window to push (Su-busybox-superuser.apk) files to data/local/tmp/ --------> when reach sysrw step (sysrw not found)
tried to type SU (su not found)
tried to use one of the alternative commands like cd /system/usr/we-need-root or ./su-backup -----> file not found
or mount -o remount,rw '' /systemmount ---------> Operation not permitted
I will be following your instructions directly and give u the feed back
I am not gonna move anywhere until solving this issue BC I am getting crazy
I would highly appreciate your help guys , ... Thank you so much in advance

mahmoud.kunbaz said:
When I first bought my ZL, I rooted the phone using binary4 V27 on superuser mode and that was very fast and simple. I could modify system files and do everything.
One day using my ultimate stupidness, I did factory reset without doing a backup for my root.
Right now, when I go to settings -----> about ----> I get Kernal version 3.4.0 with android version 4.1.2 but unfortunately It seems like I don't have a rooted phone + I am unable to do any function of a rooted phone like modifying system files or ....etc .
I've tried million ways such as:
1- rooting the phone using the same method --------> the result is stucking at the wight screen and nothing happened.
2- Using motochopper method --------> doesn't work
3- Using the method of installing Android SDK and using the command prompt window to push (Su-busybox-superuser.apk) files to data/local/tmp/ --------> when reach sysrw step (sysrw not found)
tried to type SU (su not found)
tried to use one of the alternative commands like cd /system/usr/we-need-root or ./su-backup -----> file not found
or mount -o remount,rw '' /systemmount ---------> Operation not permitted
I will be following your instructions directly and give u the feed back
I am not gonna move anywhere until solving this issue BC I am getting crazy
I would highly appreciate your help guys , ... Thank you so much in advance
Click to expand...
Click to collapse
u already posted in Q & A the same thing

demonicjas said:
u already posted in Q & A the same thing
Click to expand...
Click to collapse
Yeah, I am so sorry for that but as you know some people only go for a certain section so I might be missing someone who has the
solution of my issue :crying:
I am sorry again

mahmoud.kunbaz said:
Yeah, I am so sorry for that but as you know some people only go for a certain section so I might be missing someone who has the
solution of my issue :crying:
I am sorry again
Click to expand...
Click to collapse
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2

butatx said:
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2
Click to expand...
Click to collapse
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Thanks again

mahmoud.kunbaz said:
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Click to expand...
Click to collapse
Some aspects of modifying this phone can leave you a seriously broken phone, notably the TA partition. You would benefit greatly from doing a lot (like hours and hours) of reading in the "Z" section. All the activity is there, not in the ZL section. 99.9% of all the information there applies to the ZL (but practically NONE of the download files, so do not use software there unless clearly labeled for the ZL). The sections on backing up TA (look for DRM and TA), on using flashtool.
Note that all the information on root that does not specifically mention 253 is obsolete.

Linwood.Ferguson said:
Some aspects of modifying this phone can leave you a seriously broken phone, notably the TA partition. You would benefit greatly from doing a lot (like hours and hours) of reading in the "Z" section. All the activity is there, not in the ZL section. 99.9% of all the information there applies to the ZL (but practically NONE of the download files, so do not use software there unless clearly labeled for the ZL). The sections on backing up TA (look for DRM and TA), on using flashtool.
Note that all the information on root that does not specifically mention 253 is obsolete.
Click to expand...
Click to collapse
Thanks alot for your reply but I really don't understand why this device (ZL) is being ignored like that
I have opened a thread here about that http://forum.xda-developers.com/showthread.php?t=2293512
so many ZL users are complaining and unfortunately things are not going well

mahmoud.kunbaz said:
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Thanks again
Click to expand...
Click to collapse
Yup, please read a lot and read the feedback. It will help you to gain ur confident.
Sent from my BlackBerry 9900 using Tapatalk

butatx said:
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2
Click to expand...
Click to collapse
tried rootkeeper - doesn't work. (currently on 434 with locked BL)

Thread closed, use the post linked by the op three posts above

All In One Razr M Guide (Root, Recovery, ROM) w/ CyanogenMod Official

Hello All!
This is my guide to rooting, recovering, and "romming" the Motorola Droid Razr M!
ROM: CyanogenMod 10.1 Official
DISCLAIMER: All software that I will provide links to is AS-IS. I will NOT be responsible for anything that happens to your phone as a result of this guide
Lets Begin!
Pre-Reqs:
- All download links are in the text document below. I am not allowed to post outside links because this is my first post
-Razr M
-OEM Cable
-Software Version must be < 98.18.78.XT907.Verizon.en.US (If software is 98.18.78 and you haven't unlocked your bootloader follow this guide (link in text document below) to only root your device )
-Android Jelly Bean 4.1 (I did mine with 4.1.2. Not sure it will work on ICS)
-Battery % > than 90 %
-Patience
-MAKE SURE TO BACK EVERYTHING UP (CONTACTS, DATA, TXTS, ETC)!!
Part 1 (Rooting):
Step 1: Obtain the "motochopper.zip" file (Credit to Dan Rosenberg)
Step 2: Extract the zip
Step 3: Make sure to have the latest windows drivers for phone (If not on windows skip this step):
Step 4: Connect M to computer and make sure usb debugging is enabled (allows computer to "talk" to phone)
Step 5: Navigate to motochopper folder and click "run.bat"
Step 6: Follow on-screen instructions
Step 7: Jump for joy because you now have root!
Step 8: Proceed to Part 2
Part 2 (Bootloader):
Step 1: Obtain the "motopocalypse.zip" file (Credit to Dan Rosenberg)
Step 2: Extract the zip
Step 3: Connect M to computer
Step 4: MAKE SURE that you have root!!!!!
Step 5: Click "run.bat"
Step 6: Follow on-screen instructions
Step 7: Confirm that the bootloader is unlocked (Status code 3 or "Warning Bootloader Unlocked!" Screen on boot up)
Step 8: Proceed to Part 3 if confirmation is successful
Part 3 (Recovery/ROM):
Before you proceed you must be sure that you actually want to install a ROM on your device. My choice was CyanogenMod 10.1 Official for the Razr M.
If you find some other guide that has a safer way of doing this the use that one.
Step 1: Obtain a recovery image. I chose ClockworkMod 6.0.3.2
Step 2: Put this file inside of the "motopocalypse" folder
Step 2.1: Grab the CyanogenMod 10.1 Official Zip and the gapps package
Step 2.2: Put these files on the root of your Android phone (/sdcard) or on a microSD and put it into your phone
Step 3: From the command window type: "adb reboot-bootloader" and hit enter. You should be greeted with a familiar screen;
Ok, here is where the guides on the internet failed me. On the official cyanogenmod blog for the Razr M, it says to issue: "fastboot flash recovery your-recovery.img" and then "fastboot boot your-recovery.img". This first command worked but the second one didn't and I was unable to ever boot into CWM. That's when I had to turn to this command: "fastboot flash boot recovery.img". What this command does is replace your boot sequence (correct me if i am wrong) with CWM. So when you reboot, it will only boot into CWM. This is why your have to be serious about putting a ROM on your device. Installing a ROM fixes the boot sequence.
Step 4: If you want to continue issue the command: "fastboot flash boot your_recovery_filename.img" If you want to turn back now issue the command: "fastboot continue"
Step 5: If it installed the recovery correctly then issue "fastboot reboot"
Step 6: You will now hopefully boot into CWM.
Step 7: Use volume keys to scoll and power to select
Step 8: Choose wipe_data/factory_reset and confirm the choice
Step 9: Choose "install zip from sd" and select the CyanogenMod package. Confirm and you will see it install
Step 10: Choose "install zip from sd" and select the Gapps package. Confirm and you will see it install
Step 11: On the main menu select "reboot phone now"
Step 12: If everything was successful you will boot into CyanogenMod 10.1 Official!
Step 13: Set everything up.
Step 14: Proceed to Part 4
Part 4 (Recovery again/ Finishing up):
Step 1: Everything may seem ok, but you don't have a recovery partition anymore
Step 2: Connect M to computer if it isn't anymore
Step 3: Hold down vol+, vol-, and power at the same time to get to boot menu. Select bootloader with vol- and select it with vol+
Remember my big spiel earlier about how these commands didnt work. Well now they do! I suspect that the didn't work before because Verizon's OEM Android kept overwriting your custom recovery
Step 4: Go to "motopocalypse" folder and Issue "fastboot flash recovery the-same-file-you-flashed-earlier.img"
Step 5: It will succeed and then issue "fastboot continue"
Step 6: Now you have your recovery partition back! You can now boot into it from the boot menu or from the cyanogenmod menu
Step 7: Not over yet! Boot back into CyanogenMod and go to settings
Step 8: In Android 4.2+ the developer settings are disabled. To fix this tap on the build number in the "about phone" section 10 times
Step 9: From now on to use adb your will need to get the updated adb files for Android 4.2+ :
Step 10: You may notice that the screen has some kind of weird refresh bug when you scoll. To fix this, check the Developer Setting item that says "Disable HW overlays"
Step 11: Enjoy
Thank you guys so much for reading this guide and I hope you found it very helpful!
If you have any questions or problems leave a comment or just PM me. I will do my best to help you out.
Cheers,
Ryan (carb0nrain)

it works
it works on the Razr M 201M softBank.

Will this work with the latest OTA?
I know the latest OTA was supposed to have removed the unlock exploit. If I follow all the intructions will I still be able to root AND unlock?

Root with the latest OTA update
Forveralon said:
I know the latest OTA was supposed to have removed the unlock exploit. If I follow all the intructions will I still be able to root AND unlock?
Click to expand...
Click to collapse
This guide is only meant for people how don't have the latest OTA update. The latest OTA update removed the bootloader unlock exploit which means that you can't install a custom recovery or ROM. However, there is still a way to root your M with the latest OTA update. Look at the first link in the text document above (I can't post links directly in replies because i am a fairly new member). Hope this helps!
Cheers,
Ryan

I am the op of the other method in the dev forum.
Seems we approach it from opposite ends. Do we get the same results?
I need to check yours out....

Different Ends
aviwdoowks said:
I am the op of the other method in the dev forum.
Seems we approach it from opposite ends. Do we get the same results?
I need to check yours out....
Click to expand...
Click to collapse
This is how it worked for me. (See attached pic) Which part did we do differently. If anything is wrong, please feel free to correct me.
Cheers,
Ryan

Do you want to be on the old radio-...81p? The new is in my goodies...78p.

Radio
aviwdoowks said:
Do you want to be on the old radio-...81p? The new is in my goodies...78p.
Click to expand...
Click to collapse
Could you explain to me what the radio file is? And what is the difference between the 81p and the 78p radios. This is one of the subjects that i still dont know much about.
Thanks

Just flash it from recovery. It is from 981878.

Radio
aviwdoowks said:
Just flash it from recovery. It is from 981878.
Click to expand...
Click to collapse
Thanks

Could one of you in the know, please give the system versions that allow root? I just bought a Razr M, that came with 98.16.1.XT907 and the one click root worked fine. There is a nag wanting to do a OTA for version 98.16.3 but I keep telling it "later" as I do not know if that version is rootable. Is it?
Thank you, and I hope this helps someone else.

Rumblur said:
Could one of you in the know, please give the system versions that allow root? I just bought a Razr M, that came with 98.16.1.XT907 and the one click root worked fine. There is a nag wanting to do a OTA for version 98.16.3 but I keep telling it "later" as I do not know if that version is rootable. Is it?
Thank you, and I hope this helps someone else.
Click to expand...
Click to collapse
The new version is rootable but you can't unlock the bootloader. If you are still on the older version, you're lucky. Unlock the bootloader and don't take the update until afterwards. Even if you don't use it, you might regret not unlocking the bootloader because the update blocked the bootloader unlock exploit. Look for the RazrM Utility 1.20. It has the root method, bootloader unlock, recovery flash tool, and recovery tool all in one package.

RikRong said:
The new version is rootable but you can't unlock the bootloader. If you are still on the older version, you're lucky. Unlock the bootloader and don't take the update until afterwards. Even if you don't use it, you might regret not unlocking the bootloader because the update blocked the bootloader unlock exploit. Look for the RazrM Utility 1.20. It has the root method, bootloader unlock, recovery flash tool, and recovery tool all in one package.
Click to expand...
Click to collapse
So if I read you right, you're saying go ahead and unlock the bootloader, root it, take the OTA (just the one I mentioned or all of them? I think there's one even newer than that if not two) and then using the tool you mentioned, root it again?

Rumblur said:
So if I read you right, you're saying go ahead and unlock the bootloader, root it, take the OTA (just the one I mentioned or all of them? I think there's one even newer than that if not two) and then using the tool you mentioned, root it again?
Click to expand...
Click to collapse
Yeah, pretty much, but you'll need to root first, then unlock the bootloader (use utility 1.20 for this). After that, you can take the OTA and reroot by using Motochopper 1.3 or by just flashing a SU zip in recovery. The utility can be used on the previous update only, not the newest one. Another option for you after you unlock the bootloader and install a custom recovery, is using one of the stock based ROMs on this forum or Batakang. There are a couple of stock based, pre-rooted ROMs running around here.

RikRong said:
Yeah, pretty much, but you'll need to root first, then unlock the bootloader (use utility 1.20 for this). After that, you can take the OTA and reroot by using Motochopper 1.3 or by just flashing a SU zip in recovery. The utility can be used on the previous update only, not the newest one. Another option for you after you unlock the bootloader and install a custom recovery, is using one of the stock based ROMs on this forum or Batakang. There are a couple of stock based, pre-rooted ROMs running around here.
Click to expand...
Click to collapse
OK, I took the 3.1.6 update and the bootloader is still unlocked. I tried using the utility 1.20 afterwards and the root (option 5) failed. It said "SU already exists". If I uninstall SU would that help and then it take root? Or, is there another version of motochopper that I need to find and download?

Rumblur said:
OK, I took the 3.1.6 update and the bootloader is still unlocked. I tried using the utility 1.20 afterwards and the root (option 5) failed. It said "SU already exists". If I uninstall SU would that help and then it take root? Or, is there another version of motochopper that I need to find and download?
Click to expand...
Click to collapse
If your bootloader is unlocked and you have an aftermarket recovery installed, all you need to do is flash a SU zip in recovery.

RikRong said:
If your bootloader is unlocked and you have an aftermarket recovery installed, all you need to do is flash a SU zip in recovery.
Click to expand...
Click to collapse
No aftermarket (that I know of, but I'm rusty on this stuff as this is the first thing I've done since the HTC Inc2). I just found a DL for motochopper 1.1.2 and used it. I downloaded a root checker from the store and it says "this device has root access". So I guess I'm good!
While I have your help and attention here, I've looked at the ROMs listed on this site but there is not much information about why one is better than another etc. I'm perfectly fine with the stock phone "IF" it has root (which it does now) and IF the weird shutdown/lockup thing goes away. My other #1 main concern is anything that will increase reception.... I am leaving the Inc2 behind for that very reason... horrible reception.

Rumblur said:
No aftermarket (that I know of, but I'm rusty on this stuff as this is the first thing I've done since the HTC Inc2). I just found a DL for motochopper 1.1.2 and used it. I downloaded a root checker from the store and it says "this device has root access". So I guess I'm good!
While I have your help and attention here, I've looked at the ROMs listed on this site but there is not much information about why one is better than another etc. I'm perfectly fine with the stock phone "IF" it has root (which it does now) and IF the weird shutdown/lockup thing goes away. My other #1 main concern is anything that will increase reception.... I am leaving the Inc2 behind for that very reason... horrible reception.
Click to expand...
Click to collapse
If you want to run a custom ROM, you'll need to install TWRP or CWM. If you want to get the best reception, stick to stock and just tweak it, or find one of the customized/deodexed/tweaked stock ROMs running around here. I've had no issues with aftermarket ROMs and signal, but many people have complained about weaker reception on the aftermarket ROMs.

many thanks. I will check out the deodexed stuff. Is there any preference or reason to pick TWRP over CWM or vice versa? One last question after that.... when I had a Droid X, when I was ready to sell it I used a SBF CD to put it back to bone stock OEM. Is there something like that for the M?

Rumblur said:
many thanks. I will check out the deodexed stuff. Is there any preference or reason to pick TWRP over CWM or vice versa? One last question after that.... when I had a Droid X, when I was ready to sell it I used a SBF CD to put it back to bone stock OEM. Is there something like that for the M?
Click to expand...
Click to collapse
I prefer TWRP because it's easier use. Also, it seems to work better than CWM for the 4.3 ROMs that are out now. Yeah, you can run a XML in RSD and restore to stock. Here's a complete listing of Moto firmware.
http://sbf.droid-developers.org/

[Nexus 5] CF-Auto-Root

CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 17.5 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.

Download
CF-Auto-Root-hammerhead-hammerhead-nexus5.zip

Great to see this ready to go!

*hits thanks*

Well done sir!

Superb, mine's due to arrive in the morning, so hopefully this means I'll be good to go with Titanium from my S3?
Sent from my GT-I9300 using Tapatalk

Thanks for this Chainfire!
Sent from my Nexus 4

Amazing developer you are chainfire.... many thanks for all your hard work
Sent from my LG-E970 using Xparent BlueTapatalk 2

Amazing and very fast work ! Thank's for this Chainfire !

Nice Mister Chainfire.
You alwaysa do a great job.
Although I'm dissapointed now because I wanted to be the first to root this phone and post a tutorial .
ADB with insecure boot method . We all love it.

Great work, you rock Chainfire :good:

Works exactly as promised!
Great work Chainfire.

Works a treat Mr Chainfire - but then again we already knew it would. Damn I love the Devs!

It´s my first nexus, so can i ask if the phone comes with unlocked bootloader? or i have to unlock it? Thanks

jlmcr87 said:
It´s my first nexus, so can i ask if the phone comes with unlocked bootloader? or i have to unlock it? Thanks
Click to expand...
Click to collapse
You need to unlock it but after analyzing this tool I can tell that it will do it for you, you just need to enter fastboot (vol down+power)
Sent from my Nexus 5 using Tapatalk

sewer56lol said:
You need to unlock it but after analyzing this tool I can tell that it will do it for you, you just need to enter fastboot (vol down+power)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My last phone was an xperia arc, and after unlock it i lost functionalities like bravia engine etc. With nexus i will lost functionalities, warranty?

jlmcr87 said:
My last phone was an xperia arc, and after unlock it i lost functionalities like bravia engine etc. With nexus i will lost functionalities, warranty?
Click to expand...
Click to collapse
Warranty will be lost, but you can always re-lock it later

Ngo93 said:
Warranty will be lost, but you can always re-lock it later
Click to expand...
Click to collapse
So if i relock it.....google don´t know that if ihave to use the warranty?

jlmcr87 said:
My last phone was an xperia arc, and after unlock it i lost functionalities like bravia engine etc. With nexus i will lost functionalities, warranty?
Click to expand...
Click to collapse
It is made for people who unlock the Bootloader, so you won't loose functionalities, about warrenty - I don't know.

i only need this root ... no one more when TWRP can be run on the nexus 5 ?

Root Issue -- won't reboot into recovery mode

Hi --
Old Galaxy Tab Pro 10.1 running kitkat. I am using CF Auto Root to root it via Odin and I get the "pass" in Odin but then it just reboots into the existing OS and Supersu is not on the device. The instructions I have been following say that you should try again but switching off the "auto reboot" in odin. I did that, but it just remains in download mode. The instructions said to take out the battery...which, not really an option for the tablet.
I believe I followed all other instructions: I have the correct CF Auto Root file for my build; I have the drivers from Samsung ...
Any advice is appreciated.

tojotojo said:
Hi --
Old Galaxy Tab Pro 10.1
Click to expand...
Click to collapse
Which one?
tojotojo said:
running kitkat......
Click to expand...
Click to collapse
So you want to keep that?
If not why don't you flash TWRP and Lineage?

bmwdroid said:
Which one?
So you want to keep that?
If not why don't you flash TWRP and Lineage?
Click to expand...
Click to collapse
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.

tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.

tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
I see.
Imo it's necessary 1st of all to make sure it's on latest stock to have latest bootloader.
Flashing TWRP with Odin is extremly easy.
Here is a post/thread although written for S4 valid for most others as well.
Written a how-to myself as well but the english part is not as up-to-date as the german is.

tojotojo said:
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
Click to expand...
Click to collapse
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.

bmwdroid said:
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
Click to expand...
Click to collapse
Great, will give this a shot later today. Appreciate the help!

Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options. Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.

tojotojo said:
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options.
Click to expand...
Click to collapse
As I said: not on this old device
tojotojo said:
Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
Click to expand...
Click to collapse
Just use Odin to flash latest TWRP,
Reboot to that TWRP,
Wipe everything plus "Format Data"
Flash suiting ROM and test if it works
reboot to TWRP and flash Gapps fitting this ROM version (I prefer Bitgapps ARM)
Be happy

@tojotojo remember that Odin can only flash .tar and .tar.md5 files
TWRP.....img are to flash later in an old TWRP to get a newer one.

you need check off auto-reboot. it still in dload-mode, then press power to reboot and just as you see it starts boot press recovery-mode key combination to enter recovery. if you are slow, tab will load default system without ur root and recovery. i hope this help you.