[How-To] Root and unlock the bootloader of the Nexus 4/5 without wiping data - Nexus 4 General

This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Devices you can root using this app:
- Nexus 4: 4.4.3, 4.4.4
- Nexus 5, 4.4.3
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done

noob clarifications
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding

salxtai said:
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding
Click to expand...
Click to collapse
1. To flash a kernel you have to unlock your bootloader, that's right. You just flash it using your PC and fastboot, there are many guides on how to do that
2. If your phone is rooted and you have SuperSU installed there'll be a popup and it'll tell you to update the binary before using the app. You are able to select the "normal" way then without a recovery
3. You can install CWM/TWRP using your PC in fastboot mode!
No problem, just ask :good:

Can the usual commandline methods for other things be used after this?

PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
If you mean fastboot commands for example to flash another kernel/recovery/etc, yes! There's no difference between unlocking using this method or another "old" one, but this one doesn't wipe data

PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
yes. can also be used flashify to flash recovery.img without PC

I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?

PGvossman said:
I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?
Click to expand...
Click to collapse
Check the OP, there are already the steps given to unroot and relock

mihahn said:
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Click to expand...
Click to collapse
I tested this on Android 4.4.4... it works fine!
Note: with TowelRoot v3 it isn't necessary reboot, but when I've tried to update SuperSu it fails so reboot and that's all
Thanks so much!

I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?

PGvossman said:
I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?
Click to expand...
Click to collapse
It updates the superuser binary that got installed by Towelroot I guess

will this method work on the nexus 5?

mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
F
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done
Click to expand...
Click to collapse
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks

anees167 said:
will this method work on the nexus 5?
Click to expand...
Click to collapse
Yes, it should work fine. Try it
dodgebizkit said:
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks
Click to expand...
Click to collapse
These two are basically the same, as they are apps to manage the superuser permissions of other apps. You may use the one you like

That was easy
Of course I don't see this thread unitl after I spent the last hour setting everything up in Ubuntu to root the old fashioned way! Used this and was rooted in no time.

ota updates affected or not?
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...

ashutoshchauhan211 said:
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...
Click to expand...
Click to collapse
see towelroot only roots your device.
You can get OTA PROVIDED - You dont change any of the stock files.. Nothing should be changed.

mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
Click to expand...
Click to collapse
Hi, I have rooted Nexus 4 4.4.4 with towelroot app (and I have SuperSu app).
Now, If I install custom recovery, I will lost data? With custom recovery, I will get OTA update?
Thank you

blank nexus 4 without ROM
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......

nexusfans said:
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

Related

[Q] Can I unroot without wiping / back to stock?

Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)
GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.
Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now

[GUIDE] How to root without tripping knox - Kitkat and Lollipop, Locked bootloader

I take no responsibility for what happens to your device if you follow this guide. Rooting or modifying carries risks, however I have tested this procedure many times with 100% success on my SM-t805. It should work for any device, but I can't confirm, so feedback please if it works for your device.
1. Firstly you need to downgrade your device to a XXU1ANF8 or earlier firmware suitable for your particular model. This is available at http://samsung-updates.com/ or you can use this one XSG-T805XXU1ANF8-20140625 which is for the T805 model only.
https://www.androidfilehost.com/?fid=23501681358555496 T800 only
Download and then install the firmware on your device with ODIN.
If you are still on Kitkat then there is no need to wipe the data partition. However if you are running Lollipop after successful installation you will need to boot into recovery POWER + HOME + VOL UP then select WIPE DATA/RESET -
YOU WILL LOSE ALL YOUR USER DATA SO BACK UP ANYTHING YOU NEED TO THE SD CARD FIRST!
NOTE: IF THE INSTALL FAILS AT HIDDEN.IMG OR CACHE.IMG SIMPLY BOOT INTO RECOVERY AFTERWARDS AND WIPE CACHE THEN CARRY ON WITH THE REST OF THE PROCEDURE.
2. Once booted into Android, set up your wifi and google account and skip everything else (this wont be needed if you didn't wipe the data partition)
3. Next we need to install a Few apps, so go ahead and install these apps from Play Store:
System app remover(root)
Root Validator
Terminal Emulator For Android
KINGROOT 4.1
Kingroot updates and earlier versions if posted version doesn't work:
http://androidxda.com/download-kingroot-application
Kingroot 4.5 (latest version)
We also need to download the package from this LINK
4. Using the built in File Manager extract the zip package to your internal SD card. Once extracted, inside the extracted folder is another folder called MRW.
THIS FOLDER NEEDS TO BE MOVED TO THE ROOT OF YOUR INTERNAL SD CARD OR THIS WON'T WORK.
5. Next go to Settings set your display timeout to 10 mins.
Now Run KINGROOT then wait for it to do it's thing. If it reboots part way through the process then after rebooting unlock your device, but don't touch anything for a couple of mins. The app should restart and continue. If you are successful you can move to the next step. If not, exit the app and run it again, it may take several attempts before you eventually achieve root.
6. After success uninstall the KINGROOT app (NOT KINGUSER) (not required with v4.5) and the other blue app with Chinese writing.
Now reboot - DO NOT RUN THE KINGUSER APP
7. Let your device fully boot then run the Terminal Emulator and wait for the command prompt
NOTE: IF AT ANY POINT YOU SEE A POP UP BOX WITH CHINESE WRITING ASKING YOU TO UPDATE THE KINGUSER APP SELECT CANCEL.
Now type or copy and paste the following command into the Terminal window:
su
It will ask for root permission, so select ALLOW.
Without closing the terminal emulator window, hit the HOME button and run the SYSTEM APP REMOVER app. (The app is red and simply called UNINSTALL)
The app will ask for root permission, hit ALLOW.
Look for the KINGUSER app then select it and uninstall it. Exit from the app.
Re-open the terminal emulator window and type the following:
sh /sdcard/mrw/root.sh
This will run a script, you will see a bunch of warnings, just ignore them .At then end of the script the SUPERSU app will run.
8. Hit CONTINUE then NORMAL.
Next you may see another message that 'Samsung knox has been detected'. When you see this message select CANCEL.
Once completed you should see a message saying that installation has been successful. Hit OK.
If you see the message again 'Samsung knox has been detected' select CANCEL then exit the SUPERSU app.
9 . Now check with ROOT VALIDATOR that you have root and everything looks ok.
DO NOT REBOOT.
The root is only temporary, if you reboot you will lose root.
10. The next step is to install our ROM of choice with Flashfire.
For more info on FLASHFIRE see here: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
11. Run FLASHFIRE and grant it root.
12. Agree to the disclaimer and then hit the Red circle with a white +.
Next select 'Flash firmware package' and then navigate to the firmware you want to install (in this case the stock tar package) and select it.
Wait until it finishes scanning the archive.
Next you will see the list of partitions to be flashed, all that is really required is BOOT, RECOVERY and SYSTEM. You can flash the others if you wish.
When you're happy hit the TICK and then you will see a list of what will be flashed. If you tap any one of them you will be able to change the options. Tap the REBOOT option then select DOWNLOAD from the list. This is so we can boot into download mode after the flashing process to flash the Lollipop BOOTLOADER. If not upgrading to lollipop just select REBOOT
I'd advise to leave the rest as is and then hit FLASH
NOW WATCH CHAINFIRES MAGIC!
13. After reboot it should boot directly into DOWNLOAD mode or REBOOT if not updating to Lollipop.
If updating to Lollipop we need to flash a Lollipop BOOTLOADER. I have provided a link below for the T800 and T805. If you have a T700/705/T807/T707 or if the ones provided don't work then you will have to extract it from the Lollipop stock ROM and then TAR it up.
T800XXU1BOCC_BOOTLOADER.tar
T805XXU1BOCC_BOOTLOADER.tar
Latest T800 boot loader thanks DUHasian skillz.
T800XXU1BOE3 bootloader
Flash the BOOTLOADER with ODIN.
If successful then after reboot you should have a rooted version of Lollipop or whatever rom you decided to install and an untripped Knox counter(hopefully)
Good luck and please give feed back.
If you wish you can give feedback to Chainfire at the link posted at the beginning of this post.
NOTE: If you wish to change roms or update and wish to keep root you will have to use the same procedure with Flashfire.
Also note that if you flash a custom KERNEL or BOOTLOADER then it may trip KNOX. Custom ROMs with stock KERNEL and BOOTLOADER should be OK(but don't hold me to that)
CREDITS TO CHAINFIRE FOR FLASHFIRE AND SUPERSU, KINGTEAM FOR ROOT AND WOLFDROID FOR THE KINGROOT REMOVAL SCRIPT.
My god I've been waiting for a thread like this one for a long time.
I don't have time to try it today but I'll give you feedback in a day or two.
Feedback here http://forum.xda-developers.com/showpost.php?p=61296003&postcount=12
Moderators, this thread should be sticked
Just so that I understand the limits of this method I need to ask. Is this method specific to achieve rooted (SuperSU) Lollipop 5.0.2 without tripping Knox or can further changes be made? For example:
1) Remove system apps (removing bloat).
2) Adding system apps such as Viper4Android, busybox, which must be installed in /system/priv-app
3) The Lollipop/Samsung compatible XPosed framework and modules
4) Installing a Tab S model compatible recovery (e.g. TWRP) as I would really like nandroid backups.
I only ask as in the Tab S Kingroot thread there was a post which mentioning that despite Kingroot having successfully achieved root without tripping Knox if you messed with the /system partition files there was the possibility of tripping Knox.
The comment in step 12 "... then navigate to the firmware you want to install ..." suggests that you could install one of the model compatible custom ROMs (e.g. CM). Is that a correct assumption or right now are you restricted to Lollipop stock? Some of those ROMs are from Lollipop 5.1.1 AOSP source (e.g. CM 12.1) which may be going too far with this method and still not trip Knox.
One last question, if I did implemented this could I go back to a pure unrooted stock kitkat/lollipop using Odin or Flashfire without tripping Knox? Odin would be fine.
I greatly appreciate the effort and quality of your post. I had hoped that a "Knox off" SuperSU lollipop root would be found for my month old Tab S 10.5 as I'm used to the low risk flashing on the Nexus devices and have had a mean itch to root without obvious risk to my warranty.
Thanks again
This method can be used to root any Rom.
Once you have root you can practically do what you please.
As for tripping Knox if you mess with the system partition, that's the whole point of root it already messes with the system partition. It shouldn't trip Knox, but never say never.
Just ensure once you have root you remove everything Knox related.
I can't confirm if a custom Rom will trip Knox, but as already stated as long as the bootloader and kernel are stock I believe it won't trip Knox.
Custom recovery may trip Knox.
You can go back to stock any time you wish.
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
3DSammy said:
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
Click to expand...
Click to collapse
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
shayind4 said:
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
Click to expand...
Click to collapse
Firstly, nowhere does it state to flash the kitkat bootloader on a lollipop Rom in step 12 or 13.
By step 13 you should be running a lollipop Rom.
Secondly Knox should not trip when flashing a stock bootloader. The bootloader can be flashed independently in Odin.
Lastly Flashfire does NOT flash bootloaders.
If you don't flash the bootloader your Rom won't boot.
I suggest you digest the guide again.
3DSammy said:
In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
Click to expand...
Click to collapse
It doesn't state to flash the boot loader in step 12? :what:
Your boot loader will be replaced when you downgrade to kitkat via Odin.
You need to reflash the lollipop boot loader after using Flashfire to install your Lollipop Rom or it won't boot.
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Paddiii said:
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Click to expand...
Click to collapse
No, this is the whole point of the post. Flashfire will root for you.
ashyx said:
It doesn't state to flash the boot loader in step 12? :what: ...
Click to expand...
Click to collapse
My bad, I saw the word "Boot" in step 12 and incorrectly assumed that was referring to a bootloader image.
Thanks for correcting me and your patience.
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
bibihub said:
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
Click to expand...
Click to collapse
The hidden.img failure is because its carrier/region related.For some it will flash ok, for others it will fail. It isn't actually required at all. Even if it fails to flash the rest of the Rom will.
All that needs to be done after that failure is to wipe cache in recovery.
As regards flashing custom roms. Remember your Rom is already custom as you have modified it.
I would say a good chance custom stock roms won't trip Knox as long as it's build properties reflect its a stock Rom.
However something like Cyanogen probably would trip Knox as its not based on stock.
I won't say this is for sure, but I think it's the general consensus.
Over one thousand views and literally only one person has bothered posting feed back.
ashyx said:
Over one thousand views and literally only one person has bothered posting feed back.
Click to expand...
Click to collapse
OK now two. I successfully applied your instructions yesterday. I really appreciate your guide.
What I did, differently is flashed with Odin using a Virtualbox Windows guest VM from my Ubuntu 14.04 host PC. It took a few days of false starts to get that working. Here is a "[How-To] Linux, Virtualbox and ODIN for your Samsung device", that I just posted to help others who do not have access to Windows machines.
Of the whole procedure the scariest moment was after flashing 4.4.2 stock with Odin over my devices 5.0.2 install. The reboot was too fast for me to get into recovery to wipe user data. I could not power off the SM-T800 and holding POWER + VOL DOWN just rebooted where it would hang displaying "SAMSUNG".
Booting into recovery ( POWER + VOL UP + HOME) had no effect what so ever. Finally I found that if I was fast enough I could reboot (POWER + VOL DOWN) and as soon as the screen went blank hold down the "POWER + VOL UP + HOME" buttons, then the tablet booted into recovery where wiping user data worked as described in your guide.
After completing your guide I am on stock Android 5.0.2 with Knox 0x0000.
My root apps so far:
Busybox
Titanium backup
GMD Gestures.
ES File Explorer with RW access to all partitions
System Uninstall Pro
Universal init.d
See Update below: "Unfortunately so far Viper4Android is not working as I cannot get SELinux permissive enabled either by the SELinux app or an init.d shell script using the "setenforce 0" command. From what I've read that is due to the Samsung stock bootloader."
V4A now works, see: "[HOW-TO] Installing Viper4Android (V4A) Audio on a Lollipop Tab S"
I took the high road and only froze the following KNOX related apps using titanium backup:
com.sec.enterprise.knox.attestation
KLMS Agent
KNOX
KNOX
KNOX II
KNOX SetUpWizardClient
So far I debloated 117Mgs of other apps using System Uninstall Pro. I bought the pro version of Flashfire just to show respect for Chainfire's development efforts. I have not tried to see if Flashfire's backups can be successfully restored yet.
Thanks again for your guide.:good:
Thanks for the feedback, it's constructive and encouraging for others to know It's successful.
For future reference you can disable auto reboot in Odin then manually reboot with POWER + VOL DOWN + HOME then as soon as it restarts switch to VOL UP while continuing to hold the other buttons.
The above procedure can be used at any point and will restart the device and get you into recovery every time.
just registered to suport OP, it works
I thought I did not need to run the su script as I could use kinguser w/o problems. But the flashfire is not compatible with other kinguser. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
vancities said:
I thought I did not need to run the su script as I could use kinguser w/o problems. But the fireflash is not compatible with other root authorization app. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
ashyx said:
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
Click to expand...
Click to collapse
I had success. What I mean is the step 6 7 8 9 are not necessary if flashfire could work with kinguser.
Also kingroot only works on XXU1ANF8 and maybe lower. I mentioned this because in other thread about kingroot, someone got success but most did not.
So my feedback . everything was great , was a little confused about Odin at first but like you said everything can be found on xda. Need to be on the most recent Odin which I believe is 3.10. Kingroot took forever to root but I believe it has something to do with connectivity to the servers. So my tab s is rooted no Knox counter. I'm hoping the custom tw rom doesn't revert all the hard work ? thanks again op.

Is there a root method that doesn't require unlocking the bootloader? (LRX22C)

I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
There is a way, I believe, by running TWRP on your PC and flashing SuperSU from your PC. However, it's not a recommended method as you will have no way of backing up. Also, if you get caught in a bootloop, you won't be able to recover without a custom recovery.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
and you don't have to "hack" a nexus as well, as google provided an easy way to unlock your bootloader and to obtain root. if you just got your nexus a few days ago, just unlock the bootloader and root it. loosing a few days of information is more than worth it for root. don't waste your time worrying over a few days of data.
Can be done but not recommended.
adb backup/restore can save a little bit of information for you, but I wouldn't go in expecting it to save everything
Sent from my Nexus 6
What did you set up? You can back up your messages, and your apps will re-download. Your photos are already syncing to Google. If it's not rooted, I can't imagine you've done that much customization.
Lesson learned: unlock should ALWAYS be the very first step you do on a new phone.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
danr93 said:
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
Click to expand...
Click to collapse
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
danarama said:
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
Click to expand...
Click to collapse
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
danr93 said:
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
Click to expand...
Click to collapse
Good stuff. Once rooted, Flashify is a great tool to flash TWRP. With the nexus 5, you could unlock the bootloader with an app that didnt wipe everything, which was great, but Nexus 6 doesn't allow that, but always do go to settings > developer options > OEM Unlock (Set to enable). Without this set, you cannot unlock the bootloader from fastboot. Also, side note, developer options doesn't show up until you go into Settings > About phone then tap "Build number" several times to make the option visible. Think its 7 times.
It's interesting saying that you need kingroot to remain on the device. Thats a bit of a pain. Does it install SuperSU or not? If not, might be interesting to see what happens if you install the SuperSU app from Play - whether it allows it to be removed then.
My preferred method however is definitely unlock the BL, fastboot flash TWRP, From TWRP flash SuperSU zip (or rooted ROM).
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
arcooke said:
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
Click to expand...
Click to collapse
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
danarama said:
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
Click to expand...
Click to collapse
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
arcooke said:
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
Click to expand...
Click to collapse
That's lollipop for you. It changed everything.
It's still really simple.
Good to know. Thanks for the info!

Nexus 5 root with kingoroot apk

Ive uploaded a fully working root method of kingoroot that roots the nexus 5 on 5.1.1 LMY48B firmware
I have used it myself with uk stock nexus 5 and all works just thought i would upload so other people can benefit from this instead of using a pc enjoy
anyone tested this yet? i am to scared to try xD
thankyoumr said:
anyone tested this yet? i am to scared to try xD
Click to expand...
Click to collapse
working fine.. tested by me
Yes, this can also root from COMPLETE stock without the need of a computer of any kind. May want to add that to thread title if possible to let others know it can be used to root LMY48B(At Least) without the need of a computer to unlock bootloader first and without the need of a custom recovery first. Just install Kingroot then use KingUser(I Believe That Is The Super User App It Installs, Do NOT Install Another SuperUser App Yet Until After Custom Recovery Installed) and use KingUser to allow custom recovery App permissions to install recovery then use that recovery to install SuperUser binaries properly.
Sent from my Nexus 5 using Tapatalk
Why? It's a Nexus.
fastboot oem unlock
flash supersu zip file.
GldRush98 said:
Why? It's a Nexus.
fastboot oem unlock
flash supersu zip file.
Click to expand...
Click to collapse
He just said why on the first post...lol
So you dont need a pc
Its just an easier method if you ask me and for unlocking bootloader you just need to download the nexus 5 unlock bootloader app from google play to unlock bootloader then just install twrp manager from google play and theres your root bootloader unlock and custom recovery but thats upto the user as other people do it there way
It's remarkable what I'm willing to download and install from XDA sometimes.
Anyway, it certainly rooted my device without needing to hook it up to a PC. Threw two "this is bypassing android security" messages. Hope it didn't do anything else :/
---------- Post added at 09:57 PM ---------- Previous post was at 09:37 PM ----------
This also leaves you with an app called Kinguser, which is used to grant root permission to other apps, which can't be removed.
I think I'll feel better if I wipe and start over...
---------- Post added at 09:57 PM ---------- Previous post was at 09:57 PM ----------
This also leaves you with an app called Kinguser, which is used to grant root permission to other apps, which can't be removed.
I think I'll feel better if I wipe and start over...
All you do is use KingUser to grant permission to TWRP Manager to install TWRP and then use SuperSU to install SU through recovery THEN you can easily use SuperSU to grant permissions to any app that'll allow you to remove KingUser. That way you always have an app that can grant SU at all times without going ANY time at all without a SuoerUser app
EPayne123 said:
All you do is use KingUser to grant permission to TWRP Manager to install TWRP and then use SuperSU to install SU through recovery THEN you can easily use SuperSU to grant permissions to any app that'll allow you to remove KingUser. That way you always have an app that can grant SU at all times without going ANY time at all without a SuoerUser app
Click to expand...
Click to collapse
Tried that but SuperSU kept failing to install. Ended up just wiping and going from scratch. The whole Kingroot sending data home to a server just didn't sit well with me. I know they've addressed that they do it to keep track of success rates and don't collect any personal data.
rbrenart said:
Tried that but SuperSU kept failing to install. Ended up just wiping and going from scratch. The whole Kingroot sending data home to a server just didn't sit well with me. I know they've addressed that they do it to keep track of success rates and don't collect any personal data.
Click to expand...
Click to collapse
Failed to install returning SuperSU?
Will this wipe all data the way unlocking the bootloader does?
Sent from my Nexus 5 using Tapatalk 2
ddimple4 said:
Will this wipe all data the way unlocking the bootloader does?
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
No, wiping data only happens when you unlock bootloader through the bootloader. . . not through the OS. I believe only of you use the Farnborough method instead of manually doing so inside of OS
Sent from my Nexus 5
My friend has nexus 5 tmobile. Will this work? If so any additional steps?
Hi. I'm a newbie in root matter. My nexus 5 is already in LMY48b 5.1.1. Hong Kong stock ROM. So far there's only one reason I want to root it, it is to let some call recorder apps to record incoming voice clearly. So at this stage I don't need to flash any custom ROM. I dug for a certain time of course I can find many teaching how to root, but most of them look like it involves many procedures, many terms or apps, unlock bootloader, android SDK, twrp, custom recovery, etc... it makes me so scared even to give it a try. Until I saw this thread and I think the kingroot app probably the simplest one for my case! In fact I can get it done with a Chinese root way, it's also very simple but I also heard that most likely there's spyware inside so I leave it.
So what I want to make sure is my thought above is it correct? I try not to annoy you guys, any answer simply either yes or no is appreciated. Of course if you guys want to tell me more it is most welcome.
我從使用 Tapatalk 的 SM-T700 發送
lookgod88 said:
Hi. I'm a newbie in root matter. My nexus 5 is already in LMY48b 5.1.1. Hong Kong stock ROM. So far there's only one reason I want to root it, it is to let some call recorder apps to record incoming voice clearly. So at this stage I don't need to flash any custom ROM. I dug for a certain time of course I can find many teaching how to root, but most of them look like it involves many procedures, many terms or apps, unlock bootloader, android SDK, twrp, custom recovery, etc... it makes me so scared even to give it a try. Until I saw this thread and I think the kingroot app probably the simplest one for my case! In fact I can get it done with a Chinese root way, it's also very simple but I also heard that most likely there's spyware inside so I leave it.
So what I want to make sure is my thought above is it correct? I try not to annoy you guys, any answer simply either yes or no is appreciated. Of course if you guys want to tell me more it is most welcome.
我從使用 Tapatalk 的 SM-T700 發送
Click to expand...
Click to collapse
may be you can try the nexus toolkit, http://www.wugfresh.com/nrt/
beware that when unlock the bootloader all data will lost (factory reset), you can use something like helium to make a backup first (for back app data)
DummyPLUG said:
may be you can try the nexus toolkit, http://www.wugfresh.com/nrt/
beware that when unlock the bootloader all data will lost (factory reset), you can use something like helium to make a backup first (for back app data)
Click to expand...
Click to collapse
Hi dummyplug, thank you for your reply and your referring. But I actually don't need to flash ROM, that's why I thought that I don't need to unlock the bootloader either. Do I?
lookgod88 said:
Hi dummyplug, thank you for your reply and your referring. But I actually don't need to flash ROM, that's why I thought that I don't need to unlock the bootloader either. Do I?
Click to expand...
Click to collapse
The reason to unlock the bootloader is because if it is locked you can't run custom recovery (not flash, just a temp boot up with custom recovery), which is need for the root process, in short, you need to unlock the boot loader before you can do anything.
something like kingroot can bypass the need of an unlocked bootloader, so you actually can use kingroot to root your nexus first, then use those bootloader unlocker from play store to unlock the bootloader, but I will stay away from those tools because I don't trust them.
the toolkit can help you to unlock the bootloader and root, and do something else.
p.s. that means you need an unlocked bootloader to root, meanwhile can keep all other things (recovery, firmware) as stock.
DummyPLUG said:
The reason to unlock the bootloader is because if it is locked you can't run custom recovery (not flash, just a temp boot up with custom recovery), which is need for the root process, in short, you need to unlock the boot loader before you can do anything.
something like kingroot can bypass the need of an unlocked bootloader, so you actually can use kingroot to root your nexus first, then use those bootloader unlocker from play store to unlock the bootloader, but I will stay away from those tools because I don't trust them.
the toolkit can help you to unlock the bootloader and root, and do something else.
Click to expand...
Click to collapse
Oh I see. Now I understand! Thank you very much. I got what I want to know.

How to Root my N6 w/o PC?

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk
shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?
I can recommend the NTRT, the Nexus Telepathic Rooting Tools.
OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.
we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk
shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>
simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.
Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.
Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!
1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.
I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period

Categories

Resources