Hey all, so I bought a nexus 5 about a week ago(loving it!) and it came with boot loader unlocked. Basically I'm tryna install twrp through fastboot so I can flash SuperSU and root. Andriod version is 5.1 lollipop and I'm trying to install 2.8.5.2 twrp. I can get cmd to recognize the andriod SDK platform and is recognizes the fastboot recovery command but it says waiting for device. Do I press start on my phone or should it do this itself?
KentuckyGuy447 said:
Hey all, so I bought a nexus 5 about a week ago(loving it!) and it came with boot loader unlocked. Basically I'm tryna install twrp through fastboot so I can flash SuperSU and root. Andriod version is 5.1 lollipop and I'm trying to install 2.8.5.2 twrp. I can get cmd to recognize the andriod SDK platform and is recognizes the fastboot recovery command but it says waiting for device. Do I press start on my phone or should it do this itself?
Click to expand...
Click to collapse
You have to install drivers from here first: http://developer.android.com/sdk/win-usb.html
Is your phone booted to fastboot?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
Is your phone booted to fastboot?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
Fastboot is waiting on device if there isn't wright driver installed.
Enable use debugging
Install drivers and adb using adbinstaller.exe. Google it.
Then try "adb devices" in cmd
Yes my device was booted to fastboot. I already installed the android SDK, and the PC already installed driver. I'm gonna enable USB debugging as I forgot though. Will look into all of this and let you guys know. Just curious as to what is the start option in the fastboot menu on my phone?
Turns out I do need the drivers for adb. Thanks zagorteney! I'm gonna install them and see what happens.
Adb is irrelevant in fastboot mode
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
KentuckyGuy447 said:
Turns out I do need the drivers for adb. Thanks zagorteney! I'm gonna install them and see what happens.
Click to expand...
Click to collapse
Ben36 said:
Adb is irrelevant in fastboot mode
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
That's true. Adb and fastboot are two different things. In fastboot you don't need USB debugging enabled. You need to install drivers, when you are allready in fastboot mode (booted in bootloader).
zagorteney said:
That's true. Adb and fastboot are two different things. In fastboot you don't need USB debugging enabled. You need to install drivers, when you are allready in fastboot mode (booted in bootloader).
Click to expand...
Click to collapse
OK so when I use the adb devices command it doesn't pick up my device? Do I have to press the start option on my phone in bootloader? Also as I said when I use the fastboot recovery command it just keeps saying waiting for device. Should I press start on my device in the bootloader mode?
Try fastboot devices and see what it says
Sent from my Nexus 5 using Tapatalk
KentuckyGuy447 said:
OK so when I use the adb devices command it doesn't pick up my device? Do I have to press the start option on my phone in bootloader? Also as I said when I use the fastboot recovery command it just keeps saying waiting for device. Should I press start on my device in the bootloader mode?
Click to expand...
Click to collapse
If the phone is running normally, try the "adb devices" command and see if your device is recognized. Or if booted in to the bootloader, do "fastboot devices". Either way you should see your device as an alphanumeric string. If either recognizes your device, you have the correct drivers installed.
You will fastboot flash a custom recovery in bootloader mode.
Lots on good info in these threads:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
upndwn4par said:
If the phone is running normally, try the "adb devices" command and see if your device is recognized. Or if booted in to the bootloader, do "fastboot devices". Either way you should see your device as an alphanumeric string. If either recognizes your device, you have the correct drivers installed.
You will fastboot flash a custom recovery in bootloader mode.
Lots on good info in these threads:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Away from a working PC for a couple of days but when I get access to one, will try it and let you guys know what happens.
Alright guys thanks! Got the custom recovery installed and phone is rooted! Solution was installing the Naked (United?) Drivers for nexus 4(yes they work for nexus 5 too!) Fastboot recognized the device and installed recovery susscessfully! Now it seems I have another question,I installed elementalx kernel and reverted back to stock as stock is way easier on my battery. Just wondering when changing the settings in the elementalx installer and then reverted to stock did the config stick or revert? I noticed my phones running hotter than usual which leads me to be leave the thermel throttling didn't revert. Thanks!
EDIT: It seems battery is draining faster too!
KentuckyGuy447 said:
Alright guys thanks! Got the custom recovery installed and phone is rooted! Solution was installing the Naked (United?) Drivers for nexus 4(yes they work for nexus 5 too!) Fastboot recognized the device and installed recovery susscessfully! Now it seems I have another question,I installed elementalx kernel and reverted back to stock as stock is way easier on my battery. Just wondering when changing the settings in the elementalx installer and then reverted to stock did the config stick or revert? I noticed my phones running hotter than usual which leads me to be leave the thermel throttling didn't revert. Thanks!
EDIT: It seems battery is draining faster too!
Click to expand...
Click to collapse
Probably best if you opened a new thread for separate issues.
EDIT: Yep, so nice to be ignored.
There's no way elementalx is worse on battery than stock. It's far better.
Use options for custom hotplugging
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
There's no way elementalx is worse on battery than stock. It's far better.
Use options for custom hotplugging
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
I reinstalled to test thoughly. I see where I can disable mpdecision and use custom hotplugging in the elementalx config, is that it or is there other steps I need to take besides that? Any advice or threads on this?
EDIT: I'm guessing the overheating is causing the battery drain. Stock didn't heat my device like this. Its not bad overheating but it does get significant and the battery seems to plummet when it happens. Usually happens after playing games, although stock didn't heat up this bad or drain battery that bad while playing games. It may also be the new charger I got, will charge with stock charger to see what happens.
beekay201 said:
Probably best if you opened a new thread for separate issues.
Click to expand...
Click to collapse
True but I don't want mods thinking I'm trying to spam or troll.
Thanks guys, I've done all I needed to do. As suggested by Ben using custom hotplugging and adjusting thermal throttling, device settled back down and is running smooth and heatfree(besides heavy gaming which is usual.) Thanks everyone! Guess it'll hold me over till official Cyanogenmod 12.1 nightlies start rolling out.
Related
Hi, I've got a Nexus S 4g. I recently tried to flash it with the stock Jelly Bean image from Google's developer page - developers.google.com/android/nexus/images. While I was running flash-all.sh, the flash appeared to finish, and my terminal just said <waiting for device>. The device does boot up, and is functional, however, I can't get this thing to connect to any of my PCs via USB.
I've plugged it into my 12.10 Ubuntu laptop, and run lsusb. The device isn't listed at all, so adb doesn't work. I've also booted the phone into fastboot, and lsusb still doesn't list it (so fastboot devices doesn't list anything either). I've also plugged it into my Arch box, and tried the same steps with the same results. Before I flashed the phone, I was able to debug just fine on both machines.
Has anyone seen this behavior before? Is there any way to fix it? I've spent a bunch of time searching around for this problem, and haven't seen much. Thanks.
Well, crap. It looks like I flashed the wrong image to my phone. I've got a Nexus S 4G (d720), and it appears I flashed the i9020 image. That's what has probably caused my issue. Does anyone know if there's any way to recover from this?
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
kwibis said:
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
no need to have debbuging mode on
kwibis said:
Rephrase: Do you have unlocked bootloader?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have adb and fastboot drivers installed?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
Yes
The problem is that I flashed the wrong image to my device. I'm pretty sure it's hosed. The phone works fine - it boots up, I can get on wifi, but I just can't connect via USB. The image I flashed must have different USB drivers than what my device has. It looks like I'm stuck with it, or I will see if someone can "unbrick" it, and flash the proper image to it.
Well since you have unlocked bootloader I guess you have custom recovery and are rooted as well. You can download a custom rom, safe your app data with titanium backup, factory reset and wipe cache in recovery and flash proper rom. Then the drivers should work again and you can flash the correct image if wanted.
Sent from my Nexus S
I've tried to unlock the bootloader and root this phone for the past 5 hours with no success. Is the 4.4.4 not supported by the current tools? I don't suppose any of the drivers have changed from the 4.4.3 to this. Running windows 8.1. Also have Ubuntu 14.10
Ahmed_iAM said:
I've tried to unlock the bootloader and root this phone for the past 5 hours with no success. Is the 4.4.4 not supported by the current tools? I don't suppose any of the drivers have changed from the 4.4.3 to this. Running windows 8.1. Also have Ubuntu 14.10
Click to expand...
Click to collapse
Why don't you just do it manually? Its good learning experience and extremely easy/straightforward to do on Nexus devices. Plenty of guides.
EDIT: I assume you meant you were using scripts given you said tools. I guess I should clarify. You do mean those toolkits are what you are using? Or are you saying that fastboot isn't working?
Ahmed_iAM said:
I've tried to unlock the bootloader and root this phone for the past 5 hours with no success. Is the 4.4.4 not supported by the current tools? I don't suppose any of the drivers have changed from the 4.4.3 to this. Running windows 8.1. Also have Ubuntu 14.10
Click to expand...
Click to collapse
What about unlocking it manually (fastboot oem unlock) & flashing recovery + SuperSU?
Beter than the tools (assuming you mean toolkits) anywayz.
Sent from my Nexus 10 using Tapatalk
I'll try it manually. If that doesn't work I'll come back. I usually unlock the bootloader then root. That is the best way right or does it not matter?
Ahmed_iAM said:
I'll try it manually. If that doesn't work I'll come back. I usually unlock the bootloader then root. That is the best way right or does it not matter?
Click to expand...
Click to collapse
Unlocking the bootloader wipes the device, so yes, do that first.
Worked. But Android L erased the root like I thought I would and also removed the custom recovery. I do like the features. Buggy with sum apps but it's good for the most part.
Ahmed_iAM said:
Worked. But Android L erased the root like I thought I would and also removed the custom recovery. I do like the features. Buggy with sum apps but it's good for the most part.
Click to expand...
Click to collapse
Glad you did it the manual way. Flashing the entire factory image will always remove root and put on the stock recovery. Extract the zip file in the factory image and see what's in there. You can flash all those individually.
Sent from my Nexus 5 using XDA Free mobile app
The issue came up again. I Dont know which driver it is. I did the recovery, rooting and flashing from a windows 7 VM and it worked perfectly. It just happens when I use 8.1 it does not work at all. I installed LG's drivers, googles, the SDK, the slimes SDK and a couple others. Seems to make no difference. Any ideas? I'd prefer not having to use a VM to do this root and flashing process.
Main issue is when I do the adb or fastboot devices command, the nexus 5 is not recognized but the system does see it as an android boot loader.
I seem to be having the same issue, I can get the phone to reboot into fastboot through ADB, but "fastboot oem unlock" does not work, states "waiting for device", even tried CF auto root and it displays the same thing, "waiting for device". any suggestions?
gfaughn said:
I seem to be having the same issue, I can get the phone to reboot into fastboot through ADB, but "fastboot oem unlock" does not work, states "waiting for device", even tried CF auto root and it displays the same thing, "waiting for device". any suggestions?
Click to expand...
Click to collapse
Reboot your computer. Boot your phone into bootloader using volume down and power. Then connect the USB and see if "fastboot devices" reports anything
gfaughn said:
I seem to be having the same issue, I can get the phone to reboot into fastboot through ADB, but "fastboot oem unlock" does not work, states "waiting for device", even tried CF auto root and it displays the same thing, "waiting for device". any suggestions?
Click to expand...
Click to collapse
If it's windows 8/8.1 it needs some driver verification. To turn it off go to charms>setting>advance start up> restart now>trouble shoot> adv options>windows start up options>restart>press F7 or "disable driver signature enforcement">reboot
Should work
Ahmed_iAM said:
If it's windows 8/8.1 it needs some driver verification. To turn it off go to charms>setting>advance start up> restart now>trouble shoot> adv options>windows start up options>restart>press F7 or "disable driver signature enforcement">reboot
Should work
Click to expand...
Click to collapse
I never had to disable driver signature enforcement to get it to work on 8/8.1/8.1U1 :/
rootSU said:
Reboot your computer. Boot your phone into bootloader using volume down and power. Then connect the USB and see if "fastboot devices" reports anything
Click to expand...
Click to collapse
unfortunately "fastboot devices" did not list any devices, running windows 7.
EDIT: I got it working, wanted to post this if anyone else sees issues like i did - i flashed Koush's universal adb/fastboot driver:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
Worked perfect. Thanks all for your help!
Hey,
I accidentally wiped my operating system using TeamWin recovery, and every time I try to click boot it says, "no operating system are you sure you want to reboot?" Suddenly, though, when I tried to boot into TWRP to use adb sideload to install the system images, the TeamWin home screen just started to blink. I cannot access TeamWin or access my phone's operating system, not being installed.
If you're on the latest 2.8.2.0 TWRP, flash to the previous version.
Computer doesn't recognize
rootSU said:
If you're on the latest 2.8.2.0 TWRP, flash to the previous version.
Click to expand...
Click to collapse
Since I cannot access the TeamWin recovery, I cannot connect the phone to a computer at all to flash TWRP.
drabestdart said:
Since I cannot access the TeamWin recovery, I cannot connect the phone to a computer at all to flash TWRP.
Click to expand...
Click to collapse
no idea what you're talking about.
You dont use fastboot flash from recovery. Fastboot works only in bootloader
No USB debugging
rootSU said:
no idea what you're talking about.
You dont use fastboot flash from recovery. Fastboot works only in bootloader
Click to expand...
Click to collapse
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
If you have any precious data on sd card try first to flash fresh, but with "no wipe" option. Using Wugfresh toolkit is good choise. You can put the phone in bootloader manually and tick the option "phone in bootloop" before starting.
Regards, Zagor
drabestdart said:
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
Click to expand...
Click to collapse
Have you even tried to boot into the bootloader and connect it to your computer?
USB debugging is an android setting and has absolutely nothing to do with fastboot which is used in the bootloader.
If you don't understand fastboot, please go to the sticky thread in general then read "adb and fastboot. What is it?" Thread.
To clarify, you don't need USB debugging except for when you are using adb when booted into android. It has no relevance when using Adb in recovery or fastboot in the bootloader.
If you're having trouble connecting in bootloader you have maybe an issue with your drivers which again, my thread will help you with.
drabestdart said:
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
Click to expand...
Click to collapse
Flash the factory image with fastboot. Boot into the bootloader and run the flash-all.bat from your pc. It will wipe your device so be forewarned
Sent from my Nexus 5 using XDA Free mobile app
drabestdart said:
Well I did not have USB debugging turned on at the point when I deleted my OS so I cannot connect my phone to a computer, which I'm pretty sure you need to flash TWRP?
Click to expand...
Click to collapse
I think you already know this to be untrue since you were attempting to adb sideload a rom. Please don't be argumentative with knowledgeable people trying to help you.
Wakamatsu said:
I think you already know this to be untrue since you were attempting to adb sideload a rom. Please don't be argumentative with knowledgeable people trying to help you.
Click to expand...
Click to collapse
I don't think he is intentionally being argumentative. I think he just lacks some basic knowledge. Hopefully my thread will help with that
Worked!
jd1639 said:
Flash the factory image with fastboot. Boot into the bootloader and run the flash-all.bat from your pc. It will wipe your device so be forewarned
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks very much to all of you that helped me.
This response worked, though I had to use the flash-all.sh since I'm a mac user. All in all, you guys were a great help and I realize that I were lacking some knowledge about the topic I was talking about. Again, thanks, not only to jd1639, but also superSU, and various other people.
Worked!
jd1639 said:
Flash the factory image with fastboot. Boot into the bootloader and run the flash-all.bat from your pc. It will wipe your device so be forewarned
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks this worked! Thank you all who have helped me, including rootSU and this user to whom I am replying. I realize that I lacked some knowledge of the topic I was talking about, and apologize if I may have frustrated you. Since I am a mac user, however, I had to use the flash-all.sh instead of the .bat file.
Hi everyone.
So here is my problem.. I wanted to change rom, was on Cataclysm and wanted to flash the latest Dirty unicorn rom but I kinda ****ed up.
I did a full wipe like asked (system etc) and I wanted to flash the new rom and gapps from TWRP, using adb and fastboot. I downloaded latest drivers for the nexus 5 on my pc, and they are working, I assume.
My problem is that, since I don't have USB Debugging enabled, my device is not listed when I open a command prompt Window in adb folder and type fastboot devices.
So now I'm stuck with my nexus 5 with no os on it, and I was wondering if I could enable usb debugging via TWRP or..?
Thanks in advance !
Note : My device is rooted BUT Unlocked, if that can help.
Your problem is either your memory if you've done this before or your reading if you haven't. Tell twrp to reboot to bootloader and try again there
Sent from my Nexus 5 using Tapatalk
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.