Database Info

Question about Rooting FP5

Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?

jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
*sigh* look around...
Sent from my SCH-I510 using xda premium

jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
Here you gotaken from my thread)
5. How to root a pure stock FP1 and make CWM stick after reboot - Turn off your phone, use ODIN to flash CWM (0302 blue latest version - http://imnuts.net/zU2jkn) with "reboot" option unchecked,
After completed, disconnect the usb cable, pull the battery, reinstall battery, hold down volume up+home+power to boot into cwm,
(if you failed to boot into cwm and your phone boot up you have to redo the process). Now flash Super user package zip (Superuser-3.0.7-efgh-signed.zip - and su-bin-3.0.3.2-efghi-signed.zip (both can be download from here (look for Gingerbread) : http://androidsu.com/superuser/
Reboot phone. Use Root explore (or Root browser lite or ES file explorer) go to /system/ect/install-recovery.sh script, tab on mount R/W button (upper top). Long press on the script and in the popup menu, select permission, unchecked all permission then save the file.
Shutdown phone, re-Odin cwm again, once done reboot, now cwm should stick. Once phone came up, to verify root on your phone, you can download "root checker basic" from the Market. If you have issue, download "superuser update fixer" app from the market and run it.(no reboot required). That's it.

Wow great help with links and everything thanks a lot
Sent from my SCH-I510 using xda premium

Just to add to this very helpfull Post, this are the problems I run into and how I fixed them so that if anyone comes up with the same issues, you have the solution:
1. Flashing CWM with odin was failing, I changed usb port, I rebooted the computer, and the problem was that I was doing it without the battery, as soon as I put the battery in the phone and tried odin, it was succesfull, so, what I think is that there is not enough power to the phone just using the usb cable and that is why it was failing to flash.
2. after I flashed superuser and su-bin files, rebooted the phone, but as soon as my phone was on, and connected to the internet, for some reason, the phone automatically downloaded and updated this two files, so I could not change the recovery sh script, my solution, disabled data, reflash cwm, and the root files, then I was able to change the permissions of the file.
I AM NOW ROOTED!!!! thanks buhohitr

ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?

jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Again, please look around...
Sent from my SCH-I510 using xda premium

jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.

buhohitr said:
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
Click to expand...
Click to collapse
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!

jorge3687 said:
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
Click to expand...
Click to collapse
Nice! glad you got it working.

I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
Click to expand...
Click to collapse
I see all the replies with answers now. Don't know why they weren't there before.

yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
I see all the replies with answers now. Don't know why they weren't there before.
Click to expand...
Click to collapse
well, since I could not get help from the experts, I just did it myself and wrote the process for other people to make it easier.

Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.

Sigh... http://forum.xda-developers.com/showthread.php?t=1832040
Sent from my SCH-I510 using xda premium

read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.[/QUOTE]

jorge3687 said:
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Click to expand...
Click to collapse
[/QUOTE]
I had already tried the above without success. CWM was overwritten each time. There was another file to delete as well somewhere in system/ect which was also supposed to prevent recovery overwriting,mbut that solution proved just as fruitless.
I got itt working through trial and error, though. As it turns out, recovery actually UNmounts system after you flash a single file, so you must REmount after each if you are flashing multiple files. I do not see this "feature" explained anywhere. Maybe this is something fundamental about Linux which has escaped me over the years of android phone ownership.
Thank you for trying to help me even though.

It unmounts for safety reasons, and it's done by the package itself, not the recovery by default. You don't want power to be pulled from a filesystem in unix when it's mounted. The real issue isn't the unmount, but the mount itself seems wonky on this phone, so depending on how the CWM package is written, there's a good chance it won't be successful when it tries to mount the filesystems. It's better to mount them yourself if you're working with a package that wasn't specifically written with this phone in mind, and you even need to mount on some that are.

how to update to 4.4.x after this... New to android

First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.

To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.

cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers

shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)

finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?

cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.

shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!

cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076

shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.

No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.

RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.

cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..

RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?

cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.

RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost

cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905

RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!

cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:

RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?

RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?

Update fails to install

I tried to install the new update but on the install screen it says failed to verify and asks if i want to install anyways.
I choose yes and it errors out saying the update is for device "roth" and i have device "thor"
Does ayone know a workaround for this?

Have you messed with any system files or changed out the recovery or anything like that? I assume the Shield is going to look to make sure the system is all intact before allowing the update. Though the fact it says Roth which is a spelling error of Thor seems weird. Mine updated fine...
If you can find the update using root explorer you could delete it and redownload it.

I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk

csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
OTAs will commonly fail if you install custom recovery. You'll have to wait for someone to make it into a zip that you can run through CWM.

csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.

CDeviant said:
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.
Click to expand...
Click to collapse
I tried this but it wouldn't download the ota again an I couldn't find where it was. So, I tried going back to stock to update but now it is stuck on the boot screen. I tried downloading a newer factory image from the nvidia website but now all of the windows links are locked behind some developer program that I have to make an account, submit an application, and wait for approval. Do you have any links to a recent factory restore image?
EDIT: I ended up just downloading mint and the linux .sh file to get the factory images.

You can use the root toolbox on this forum to reflash stock and relock and fix it

eric4shay said:
You can use the root toolbox on this forum to reflash stock and relock and fix it
Click to expand...
Click to collapse
That's what I tried before but it didn't work

If some updates please capture the OTA zip that downloads and upload it for us to tear apart.

What steps are you doing on there also email me [email protected] I will be able to respond more quickly

you dont have to
you can just use kwonggers toolkit, and just revert to stock kernel, stock system image, and stock recovery, you don't need to relock bootloader, but you must download the ota's separately, if you don't automatically see them under about shield> updates, then go to application manager>all> and force stop google services framework, then check for the update(it should now show up and download). this is what I have been doing, everytime I want to revert to the stock, most up to date ota, after this, you can reflash cwm recovery, flash the super su.zip and root again!

The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk

Mechcondrid said:
The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk
Click to expand...
Click to collapse
That could be more than one reason. But off the top of my head, maybe it's because the OTA folder is userspace, and there might not be enough Storage left on the internal. Cache is a separate partition, Things can even be deleted while running. So basically it insures enough space to download, and the user would never need to delete his own data to make room.
It might be awkward when you're looking for the OTA, but I think it's designed that way with the user in mind. :good:

Well regardless here's the ota file https://drive.google.com/file/d/0B2khjpo7TDP0Y3c0SjNNRWNXT28/edit?usp=sharing
Sent from my SCH-I545 using Tapatalk

SuperSU needs to update binary

Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.

What if you upgrade it using the "normal" method?

If I do a normal install i get the following:
Installation failed!
Please reboot and try again.

brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?

rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.

brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.

rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?

brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards

rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app

brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.

Cannot root

Got my replacement shield today. Went ahead and did the OTA update to 5.1.1 but am unable to root using either towelroot or kingroot. anyone else have a working method. Don't have an sd card yet so that is out as well

cmccarter said:
Got my replacement shield today. Went ahead and did the OTA update to 5.1.1 but am unable to root using either towelroot or kingroot. anyone else have a working method. Don't have an sd card yet so that is out as well
Click to expand...
Click to collapse
Using USB copy SuperSU to your tablet, unlock the bootloader, flash the TWRP custom recovery and then use TWRP to install SuperSU. If you want follow this guide, but skip flashing BlissPop and the GAPPS package.

Strange! I used Kingroot on the replacement tablet, just two days ago. It was on 5.0.1 when I received it but I went ahead & upgraded to 5.1.1. Kingroot only took 20 seconds to reach 100% on 5.1.1.
Long story short, I wiped the device in TWRP because I don't know what Kingroot also installs besides just rooting the device, & flashed the full 5.1.1. OTA ROM along with the latest superSU. Rebooted & had to setup the device as a new device. No big deal because it was a brand new tablet anyways so no data lost.
By the way, I don't have an SD card in my tablet either. I borrowed the SD card from my Note 3 to make this work. Then deleted the files before placing it back in the phone.
So I'm rooted, TWRP recovery AND using 5.1.1 clean install. No trace of Kingroot found through ES file explorer.

Kingo *

bull1295 said:
Using USB copy SuperSU to your tablet, unlock the bootloader, flash the TWRP custom recovery and then use TWRP to install SuperSU. If you want follow this guide, but skip flashing BlissPop and the GAPPS package.
Click to expand...
Click to collapse
Still having trouble. I unlocked the bootloader, installed TWRP and installed supersu but rootchecker still says no su. Do I have to do a sideload of supersu from an sd card?

bull1295 said:
Using USB copy SuperSU to your tablet, unlock the bootloader, flash the TWRP custom recovery and then use TWRP to install SuperSU. If you want follow this guide, but skip flashing BlissPop and the GAPPS package.
Click to expand...
Click to collapse
Still having trouble. I unlocked the bootloader, installed TWRP and installed supersu but rootchecker still says no su. Do I have to do a sideload of supersu from an sd card?

What I'd like to do is root my new device, install twrp and blisspop without connecting it to the internet. Is this possible?
Kingroot requires internet.

present Status
did a full wipe
verified bootloader is unlocked
twrp is in stalled
loaded supersu 2.46 thru twrp
rebooted
after login i get a messgae that supersu is outdated but cannot get a successful update
at this point i am open to all suggestions.
have.tried both towelroot(says.phone not supported)
kingsroot just tries to load a bunch of garbage ware
next?
Sent from my LG-E980 using Tapatalk

but cannot get a successful update
Click to expand...
Click to collapse
have you tried both the Normal and TWRP options when updating SuperSU?

Bogdacutu said:
have you tried both the Normal and TWRP options when updating SuperSU?
Click to expand...
Click to collapse
yep, twrp never reboots and normal always fails
Sent from my LG-E980 using Tapatalk

I'd suggest downloading the recovery image for your current version of Android (or full OTA and wipe system beforehand) and flashing just the system.img from there, to make sure that you're starting from a clean state, then try flashing SuperSU through TWRP again (it should work without issues)

will try that will the.ota image need to be . on the sdcard?
Sent from my LG-E980 using Tapatalk

cmccarter said:
will try that will the.ota image need to be . on the sdcard?
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
if you're downloading the OTA (not the recovery image), you can either put it on the SD card, or you can flash it directly from your computer using ADB sideload from the Advanced menu in TWRP (on the PC side, do "adb sideload path/to/ota.zip")

My thanks to all who helped. I finally put everything on a 1gb sdcard that I found. Installed everything and now (I think) I have full root access. Will let you know later

Tnx to all who helped. I finally put everything on a 1gb card I found in my junk pieces an it appears that I have full root access.