Related
I just wanted to put this out for people looking for a root method with the Design. The Super Tool hasn't worked for me when using the design. I have figured out a way that has work more than a few times now. Here is exactly what I've done to get Unlock Bootloader and able to flash a recovery.
1. Use HTC Unlocker at htcdev.com to unlock bootloader. Must have all files instaled. They will have all the files at htcdev. Follow instructions to the end and you have unlocked your bootloader.
2.http://forum.xda-developers.com/showthread.php?t=1239821 Download the su file and the recovery file that are below the YouTube video.
3. Put the two file into your sdk tool folder where you adb and fastboot.
4. Open a command prompt at that folder. Shift right click on folder and you can open a command prompt right where you need it.
5. in command prompt type "adb push recovery.img /sdcard/"
"adb push su-2.3.6.3.zip /sdcard/" with out quotes.
6. Get to fastboot using "adb reboot bootloader" in command prompt or do a battery pull, hold power and down volume then have your phone connected at fastboot where it should say fastboot usb.
7. Type "fastboot flash recovery recovery.img"
8. Once its finished unplug and hit power button while fastboot is highlighted.
9. Now you see you can use the volume down button to navigate down to recovery. When you are on it hit power button and it will boot into recovery.
9.5 I suggest selecting backup restore and making a back up of your system at this point. I have seen that in using this method if you ever let the phone completely die you can get a problem or two and it is nice to have a backup that is fresh and clean that you can start over with. If this ever does happen to you just navigated yourself to recovery like you are now and when you click backup/restore you can restore your system.
10. Using volume key navigate to instal from zip. "install zip" and then pick the "su-2.3.6.3.zip" Now superuser is installed
11. Navigate back and and reboot to system.
YEA.
This is pretty simpled down explanation but if you get stuck it usually can get worked out. I haven't seen much for ROMs for this phone yet but at least you get superuser and all the goodies that come from having that, Tether anyone, not to mention all the bloat ware you can remover with rootuninstaller from the market. Just dont use rootuninstaller to remove critical like sprintzone and so on.
Ive had good luck using this method and if anyone is developing a rom for it that would be awesome. You dont have S-off so you must do all your flashing using the skilled know how that TWRP offers using command prompts to flash img. and so on but it is not bad and it gets easier and easier to do the more you get hooked on flashing but like I said there isnt much out yet for this phone.
Hope this helps some of you.
Much Love and Many shout outs to TWRP and everyone over there who are just killing it.
Does this method work if your phone was previously updated? I have my bootloader unlocked but it still has 's-on'. I just wanted to make sure it will still work on my phone or not.
This might be a little old but it seems as this work with the exception of the Recovery.Img which apparently needs to be different than the one given on the other post. Everything else has worked perfectly.
Jorke550 said:
This might be a little old but it seems as this work with the exception of the Recovery.Img which apparently needs to be different than the one given on the other post. Everything else has worked perfectly.
Click to expand...
Click to collapse
thanks
Help
Hey man,
I need help, I followed step by step, but the recovery doesn't work, wait 15 minutes but did not enter, what do you think happens?
No help anymore
Ivan0907 said:
Hey man,
I need help, I followed step by step, but the recovery doesn't work, wait 15 minutes but did not enter, what do you think happens?
Click to expand...
Click to collapse
Forget about, i did it
Introducing.... Superboot!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
You will need to htcdev bootloader unlock your device to use this root solution.
APPLY THIS AT YOUR OWN RISK!
Superboot - DOWNLOAD
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then pressing the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Enjoy!
P
PS If you find this useful, details on how to donate should you wish to do so are in the download topic at MoDaCo.
Hi @All,
I got a problem, cause I rootet my One X with pauls great stuff...
So I wanted to do the same thing with my One S and didnt change superboot with the file r3 superbootandroot, so something happened with my OneS.....it doesnt start and shows me Warning "this is only for blabla" in red....so I went to bootloader, did it right with the right file, and goes till now, cause doing a restart, it shows me only this warning again....I always have to go to bootloader, to start my device right..what can I do?
And in Bootloadermode, the first word is tampered...I know what that means and is there a chance to change it?
So what did you do exactly? You flashed One X to One S? Whoops!
If you can confirm this is what you've done i'll upload what you need to fix it..
P
Hi Paul, yes, i did a mistake....booting r3 to OneS, not teh right superboot-file...
after that, i bootet it right with superboot, but now "tampered", and everytime i must go to bootloader and boot your file to use my device^^
big thx for Answer!!
I also have this **tampered** line before the **unlocked** line, but no issues with booting - everything fine.
You didnt do my mistake, of course, sure? to boot with a file of an One X to One S, did you?
jammysunny said:
You didnt do my mistake, of course, sure? to boot with a file of an One X to One S, did you?
Click to expand...
Click to collapse
Nope, just wanted to say that the **tampered** has nothing todo with your fault and current problem..
good to hear...but it wouldnt be normal, to boot this superboot-file everytime I restart my S^^
jammysunny said:
good to hear...but it wouldnt be normal, to boot this superboot-file everytime I restart my S^^
Click to expand...
Click to collapse
True
Hi Paul, what or how can I do myself, cause tomorrow i leave Home to Vacance, and there I am not able to do such like this^^
jammysunny said:
Hi Paul, what or how can I do myself, cause tomorrow i leave Home to Vacance, and there I am not able to do such like this^^
Click to expand...
Click to collapse
once you booted with the superboot image, it does the necessary changes on your /system partition for the phone to stay rooted even when you reboot it...
--
Hi is this method safe etc, anyone tried running apps with root access etc?
only asking as mine is coming next week..
it's as safe as rooting can be and works like described...
Hi
I would like to ask what's the difference between this rooting method compared to the htc official one, especially concerning the warranty part. Is the official htc method a fastboot flash or fastboot boot?
Thanks for this a hundred times.
There is no official rooting method, just official bootloader unlock.
Rooting is what you do afterwards.
And it just refers to being able to su to root. For this 'fastboot flash' is not necessary if the needed files are copied by a 'fastboot boot'ed image.
You could alter the ramdisk in order to create an insecure boot.img though and that needs to be flashed...
Sent from my HTC One S
Will this work on the T-Mo US version?
It should yes..
Good afternoon...I was wondering if it is or will it be possible to root without using HTCDEV ? The reason I'm asking is I'm not sure that I want HTC to know, what if I have to send my phone back for say, a cracked screen or something, will my warranty be voided because I rooted using HTCDEV, they would obviously be aware that I'm rooted...HTC pretty much states that if you root your phone your warranty would be invalid...i've been a long time follower/fan since my G1 days, thanks again Modaco
Thanks in advance for your help and any suggestions that you may have...
Found a great tutorial by Torxx in One S Android development, may be helpful to some...
Thanks again XDA
Hello,
I have also **Tempered** in the top of the bootloader. (HTC One S)
after that I tried to do a factory reset but the only thing it does, the phone reboot and there is no new installation. Clear Storage is the same...
How can I get my phone in the state before flashing with "install-superboot-windows.bat"
Is there an original boot.img that I can flash to restore my phone... ?
touchhdsteo said:
Hello,
I have also **Tempered** in the top of the bootloader. (HTC One S)
after that I tried to do a factory reset but the only thing it does, the phone reboot and there is no new installation. Clear Storage is the same...
How can I get my phone in the state before flashing with "install-superboot-windows.bat"
Is there an original boot.img that I can flash to restore my phone... ?
Click to expand...
Click to collapse
whats the problem here? it does not boot?
you cant get rid of the ** TEMPERED ** message for now...
Been a while so i tried read up a bit. Thank you for taking the time to read this and/or dropping a little knowledge on me.
I Install Weaksauce. Run.
Install SuperSu.
Run firewater
can someone tell me where to get adb tools? have never really messed around with adb.
Install CWM or TWRP (which is more stable?)
nandroid
install custom rom
Correct order? and some help with the adb would be appreciated. Thanks again
If nobody else helps with adb stuff, I'll link in a little when I get on the computer. Try firewater first. If it fails and says it will never work with your device in the error, you will need to DL and use sunshine. It will cost you 25 dollars but worth it if you ever want to have control of your device.
After you use firewater or sunshine, whatever you have to use. reboot, uninstall weak sauce and SuperSU.
Then back into fastboot.
Definitely use twrp
After installing twrp with fastboot,
After you have twrp, flash SuperSU zip found here on xda in chainfires thread. This will give you your permanent root.
Then you can nandroid, and rom all you want.
silver04v said:
If nobody else helps with adb stuff, I'll link in a little when I get on the computer. Try firewater first. If it fails and says it will never work with your device in the error, you will need to DL and use sunshine. It will cost you 25 dollars but worth it if you ever want to have control of your device.
After you use firewater or sunshine, whatever you have to use. reboot, uninstall weak sauce and SuperSU.
Then back into fastboot.
Definitely use twrp
After installing twrp with fastboot,
After you have twrp, flash SuperSU zip found here on xda in chainfires thread. This will give you your permanent root.
Then you can nandroid, and rom all you want.
Click to expand...
Click to collapse
where do i put twrp.img
camf3xu said:
where do i put twrp.img
Click to expand...
Click to collapse
Youbplace the image in your adb folder in.....sdk/platform-tools.
camf3xu said:
where do i put twrp.img
Click to expand...
Click to collapse
Into the same folder where your adb.exe and fastboot.exe are.
To get adb/fastboot try this great little tool: http://forum.xda-developers.com/showthread.php?t=2317790
Make sure USB debugging is enabled in Developer Options.
Then open Device Manager on your PC, connect your phone booted to Android via USB cable and note any changes. You should see an entry for adb interface. If it doesn't have a yellow exclamation mark next to it, you probably have the correct driver installed. If it does, right click the entry and update the driver.
Check the connection with the command:
Code:
adb devices
from a command prompt opened from the adb folder.
If it returns a string of letters and numbers: Congrats, your adb is working.
Next boot the phone to hboot.
Connect it via USB and you should see a new entry for the fastboot interface.
Proceed as above.
To test the connection issue
Code:
fastboot devices
If you get the connection, the command to flash TWRP is
Code:
fastboot flash recovery twrp.img
Check out the 2 other posts many get firewater to work using superuser with weaksauce app instead of supersu. Check out the two other posts below first is the main one.
http://forum.xda-developers.com/showthread.php?t=2787587
http://forum.xda-developers.com/ver...firewater-s-off-fail-bottle-chugging-t2821691
work in progress any help would be great. anything you do is at your own risk and possible may brick your phone or OS.
Ok this is a start of rooting this phone just like other carriers phone cricket z987 grand x max plus you need to install king root4.5 worked for me to get temp root. now this is not permenent and will cause phone to get buggy forcing a restart. what has worked with zte max, zte grand x max plus worked was after getting temp root you could install twrp 2.8.6.0 and installing superuser.zip from there gave gave perm root access but not full w/r access. now that does not work with this phone. phone boots into factory bootloader when trying to install twrp.
im looking into more option but as of right now I on a slow stand still till i can figure something out or someone else. feal free to help.
cgrimm9 said:
work in progress any help would be great. anything you do is at your own risk and possible may brick your phone or OS.
Ok this is a start of rooting this phone just like other carriers phone cricket z987 grand x max plus you need to install king root4.5 worked for me to get temp root. now this is not permenent and will cause phone to get buggy forcing a restart. what has worked with zte max, zte grand x max plus worked was after getting temp root you could install twrp 2.8.6.0 and installing superuser.zip from there gave gave perm root access but not full w/r access. now that does not work with this phone. phone boots into factory bootloader when trying to install twrp.
im looking into more option but as of right now I on a slow stand still till i can figure something out or someone else. feal free to help.
Click to expand...
Click to collapse
Please do I have people asking me if it's possible to root this phone and I said it could happen so fingers crossed
I tried and pretty much gave up. I can only gain temp root but its would be useful in small things like installing a recovery but there is non that works that I know of. I got titanium backup to back up my system but don't know if it will write if I format. Again any help from would be appreciated
Has any progress been made? I've been tinkering with this for days. Been pulling my hair out trying to dump the rom. If I can get the rom dumped I can attempt to port cwm over.
jimbog92 said:
Has any progress been made? I've been tinkering with this for days. Been pulling my hair out trying to dump the rom. If I can get the rom dumped I can attempt to port cwm over.
Click to expand...
Click to collapse
try this
stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot 4.5 and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""
"su"
"cd /dev/block/platform/7824900.sdhci/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"
You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB I did this and I got all three files saved to the root of my sd card. it would be easier for you do do this your self I am over my data cap so I cant upload the file
Last edited by cgrimm9; Today at 02:06 AM.
cgrimm9 said:
try this
stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot 4.5 and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""
"su"
"cd /dev/block/platform/7824900.sdhci/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"
You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB I did this and I got all three files saved to the root of my sd card. it would be easier for you do do this your self I am over my data cap so I cant upload the file
Last edited by cgrimm9; Today at 02:06 AM.
Click to expand...
Click to collapse
Ok, i got the first 2 to dump, now im guessing the system dump takes a while. where do they dump to exactly? and thanks for the help.
Ok, got all 3 to dump and found the files.. Now, have you made any progress in attempting to port a custom rom?
I'm to scared to brick my phone gf will kill me if I spend more money on a new phone. There is possibly a way to gain perm root but its risky you can look here
You do this at your own risk you brick your phone I will not beable to help restore.
jimbog92 said:
Ok, i got the first 2 to dump, now im guessing the system dump takes a while. where do they dump to exactly? and thanks for the help.
Ok, got all 3 to dump and found the files.. Now, have you made any progress in attempting to port a custom rom?
Click to expand...
Click to collapse
I may attempt that this weekend. But honestly, I am more worried about getting custom recovery and a custom rom installed.
Had there many any follow up on this phone? I would love to get cm12 or cm13 up and running.
I know its possible I don't think its gonna happen it only needs twrp to be tweaked to install in a different location but I don't see no support for this phone
dude, this phone is so easy to root. you dont need kingroot or any of that crap. you just need to know what your doing with adb. which you should know before you ever get into rooting. email zte support and request your boot loader unlock code. be sure to include you will need to provide them your phones serial number and imei. you willrecieve it in less than 24 hrs. open adb in comand terminal and type "adb devices". adb should return showing your devices serial number and device name. if it does you are good, if not make sure you have usb debugging enabled on your device. if your device does show up then type "adb reboot bootloader". your phone should reboot to the bootloader screen. to make sure this worked type "fastboot devices". Again your devices serial number and device should populate. Then type "fastboot oem unlock and the code you recieved from zte". adb will say "daemon started... time elapsed... write successful. i would download twrp 2.8.7.0. once you have that downloded move it to the same folder your adb is installed at and in adb type "fastboot flash recovery (recoveryname.img)".here again adb will say daemon started... time elapsed... write successful. now move supersu.apk (your super user app) to the root of your sd card. in adb type "fastboot reboot recovery" and your device will reboot into recovery. unplug your phone. on your phone in recovery select install zip. select your sd card. select your superuser apk. the swipe to install. once its done select reboot. bam your device is rooted with super user installed. a lot of times when you unlock your bootloader your device will factory reset so dont be surprised. do this all at your own risk
Hello
I would like to help out with this if ppl are still trying. I have experience with kernel building and etc etc but I need to know how to root my phone otherwise I can't dump boot imgs. To port over twrp or cwm. Also the source does not seem to be available so I would have to write a ton of code to do so. And also I noticed this post dates back to when the phone ran 4.4.4. I'm running 5.1.1 and that's another issue once rooted I can do it but we need more support.
Have any of you uploaded your boot, recovery and system image. Also have any of you managed root yet. I will be attempting to do so this weekend.
niisan518 said:
Have any of you uploaded your boot, recovery and system image. Also have any of you managed root yet. I will be attempting to do so this weekend.
Click to expand...
Click to collapse
Hello, I was wondering if you had any luck rooting. I also have the ZTE Lever running kit kat 4.4
kxhan15 said:
dude, this phone is so easy to root. you dont need kingroot or any of that crap. you just need to know what your doing with adb. which you should know before you ever get into rooting. email zte support and request your boot loader unlock code. be sure to include you will need to provide them your phones serial number and imei. you willrecieve it in less than 24 hrs. open adb in comand terminal and type "adb devices". adb should return showing your devices serial number and device name. if it does you are good, if not make sure you have usb debugging enabled on your device. if your device does show up then type "adb reboot bootloader". your phone should reboot to the bootloader screen. to make sure this worked type "fastboot devices". Again your devices serial number and device should populate. Then type "fastboot oem unlock and the code you recieved from zte". adb will say "daemon started... time elapsed... write successful. i would download twrp 2.8.7.0. once you have that downloded move it to the same folder your adb is installed at and in adb type "fastboot flash recovery (recoveryname.img)".here again adb will say daemon started... time elapsed... write successful. now move supersu.apk (your super user app) to the root of your sd card. in adb type "fastboot reboot recovery" and your device will reboot into recovery. unplug your phone. on your phone in recovery select install zip. select your sd card. select your superuser apk. the swipe to install. once its done select reboot. bam your device is rooted with super user installed. a lot of times when you unlock your bootloader your device will factory reset so dont be surprised. do this all at your own risk
Click to expand...
Click to collapse
Hello, I tried booting into bootloader but it didn't work, just does a normal reboot. It does recognize my phone though when I type adb devices. I contacted zte through email and by phone and they said they don't give those codes. Is the bootloader suppose to be unlocked already? Thank you.
Have you tried just typing "fastboot oem unlock" , or "fastboot oem bootloader unlock" without the unlock code? A lot of devices don't even need a code. Or if your bootloader is already factory unlocked, you could just skip to "fastboot flash recovery".
kxhan15 said:
Have you tried just typing "fastboot oem unlock" , or "fastboot oem bootloader unlock" without the unlock code? A lot of devices don't even need a code. Or if your bootloader is already factory unlocked, you could just skip to "fastboot flash recovery".
Click to expand...
Click to collapse
Hello again. Well I tried everything you mentioned. When I type adb devices it shows my device but when I type reboot bootloader it just does a normal reboot. Also when I type fastboot flash recovery with my img. file it just says waiting for device. Any suggestions. I really appreciate the help and your time.
dhplap said:
Hello again. Well I tried everything you mentioned. When I type adb devices it shows my device but when I type reboot bootloader it just does a normal reboot. Also when I type fastboot flash recovery with my img. file it just says waiting for device. Any suggestions. I really appreciate the help and your time.
Click to expand...
Click to collapse
Plug your device in and type adb devices once that is done type ADB reboot fastboot
kxhan15 said:
Plug your device in and type adb devices once that is done type ADB reboot fastboot
Click to expand...
Click to collapse
Thanks again. I tried that and it still just does a normal reboot.
dhplap said:
Thanks again. I tried that and it still just does a normal reboot.
Click to expand...
Click to collapse
from what I've researched the bootloader is locked and it's impossible to enter fastboot mode. Thank you very much for your help though.
Android 6.0.1, build number MOB30H
I have a brand new nexus 5 that I want to root. Using ota, I accepted the system updates to 6.0.1 with the Android security patch of May 1, 2016. (not sure if that was a good idea or not but it's done now....). Now I want to root it with a twrp recovery.
Like most run of the mill users I've only rooted a device 2-3 times in my life, so my memory is rusty on how exactly to do it. I searched this forum and found many threads about this or that rooting problem which just confused me further. I know I need to unlock the bootloader and then flash a twrp recovery but I am not sure of the exact sequence of steps.
1. When I connect the nexus 5 to my windows pc using adb, it appears in Windows but the nexus 5 folder is empty. I have developer options available and usb debugging is on but I can't find where the mtp switch is.
2. Adb.
I have adb installed in Windows. The command "adb devices" returns the nexus 5 number unauthorized.
Don't know what "unauthorized" means or what to do about it.
I've done nothing further because I don't want to mess things up. Please help me resolve questions 1 and 2. Then, I presume I need to
A. unlock the bootloader
Fastboot command?
B. What's next?
Thanks for any help.
Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Click to expand...
Click to collapse
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs
You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.
Yes I already had developer options working and also usb debug on.
Discovered that mtp is a problem in marshmallow. I finally got file transfer working.
audit13 said:
You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.
Click to expand...
Click to collapse
Thank you very much. That is very helpful.
I didn't know you could "install TWRP and root without using ADB commands". How do you do that?
BTW, I updated the new nexus 5 to marshmallow inadvertently. When I root I'll probably use a 5.1.1 image. Good idea?
Stevica Smederevac said:
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs
Click to expand...
Click to collapse
Yep, my bad. Sorry about that. My 5 crapped out and have the 5x now. Amazing how fast you forget things, lol.
Sent from my Nexus 9 using XDA Free mobile app
Download and flash twrp in fastboot mode: https://dl.twrp.me/hammerhead/twrp-3.0.2-0-hammerhead.img.html
Download supersu.zip and save it to the phone's internal memory: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Boot the phone into fasboot mode, open a command prompt, type fastboot devices and press enter. If the device is recognized, you'll see the device's serial number. Unlock the bootloader by typing "fastboot oem unlock" and use the volume/power button to accept the agreement and unlock the bootloader. Unlocking the bootloader will wipe the phone's data and cache.
To install TWRP, boot the phone into fastboot mode, connect it to the computer, open a command prompt, and type "fastboot flash recovery name-of-TWRP-file,img" and press enter. After flashing, immediately boot into recovery using the power and volume buttons, and then flash supersu.zip.
Thank you so much audit13. I really appreciate your help.
One question if I may. Reading on the web about rooting the nexus 5 running marshmallow I came across a couple of sites that said I should download and flash "ElementalX kernel and SuperSU 2.52" in addition to supersu.
I've never had to install a separate kernel when I rooted in the past. I notice you don't add flashing a kernel either. Can I ignore flashing a special kernel?
Thank you so very much for your clear instructions.
Some root methods require a rootable kernel. The latest supersu should root mm.
Thank you. Ran into a problem. That's why people like me are afraid of rooting.
Bootloader is now unlocked. Thanks.
With the N5 in fastboot mode, I connected it again with the laptop.
From the laptop command prompt I ussued "fastboot devices" and it found the phone.
Problem:
1. Fastboot flash recovery.img
(I had renamed the twrp 3.0.2 img file to recovery. Img)
Result:
unknown partition 'recovery.img'
error: cannot determine image filename for' recovery.img'
Tried by downloading a fresh copy and using its original filename.
Same result.
What am I doing wrong?
Thank you.
Found my error. I forgot the word recovery.
I now flashed twrp successfully!
When I went to flash supersu I discovered that the supersu I had downloaded was no longer in download folder. Guess it got wiped. So I rebooted into system and will download it again. Hope that does not mess up things.
Edit:
All went well. Re-downloaded SuperSU, installed fine and I'm home free.
Thank you all, especially audit13. This is a nerve-wracking process for people who only do it rarely. Glad it is over. The rest is easy!
I spoke too soon. I believe I now have a boot loop? What I have is that the horizontal turning balls of marshmallow go around forever and never finish booting.
How do I exit from this?
So close, but not there!
Edit
I rebooted into twrp, deleted cache, davlik. Still in bootloop.
Deleted data. Still in bootloop.
Help.
Reflash the entire stock rom and start over.
Try the latest beta of supersu: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Great you are still here.
Need more details.
You say reflash stock rom. Where do I get it? How do I get it into the phone? Do I flash it through twrp?
How to flash factory image: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Factory images are here: https://developers.google.com/android/nexus/ota#hammerhead
Thank you again. Will do.
I think I know what went wrong. After I flashed twrp the phone rebooted into system before I could stop it and I think I interrupted it somewhere to return to twrp to flash Supersu. Anyway, glad I didn't brick it. Thanks again for being there.
It's morning now and after a good night's sleep I'm less rattled. Will get breakfast and start again.
I'm going out with my wife for breakfast.
I haven't followed the marshmallow threads but I recall reading about lingering problems with marshmallow. I also like to use xprivacy and gravitybox. So I'm thinking of flashing the latest 5.1.1 instead of 6. Any thoughts?
I like both ROMs but my battery life seems a bit better on MM. I'm sticking with unrooted stock ROMs on all of my phones for now.
Being a "flashaholic" is tiring!
audit13, I know you know this but it was so simple to do (once you know how.....!). It took me the whole of 20 minutes, if that, to download the files, flash 5.1.1, flash twrp and install SuperSU. Makes you wonder why I had so much trouble before!
Well when you don't know the command syntax (forget to write which partition to flash to) and are frozen with fear that you will brick the phone, it is a scary process. Once I knew how, I breezed through it. Problem is that by the next time I need to do this, I will have forgotten how or will worry that the process has changed.
I just want to thank you more than I can say for helping and hanging in while I made my mistakes. I wish there was a way I could thank you with more than words. You were great!
P.S. This time I used the beta SuperSU. Don't know if it made any difference.