Related
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?
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
Have a rooted Verizon HTC One M8. Didn't have a custom rom on it. I was just happy with not having ads, and being able to have access to files on the phone. The one problem that I kept having was it constantly telling me that I needed to do an update. I tried freezing Update files in Titanium Backup, but I would still see the notifications. Followed advice elsewhere on the internet, and tried to Force Close Download Manager. I then went into TWRP and wiped Cache and Dalvic Cache. Now, it's completely stuck on the white HTC screen on bootup. I can boot into Recovery, but I'm not sure what to do to get the phone back to working condition.
Please help! This is not the Sunday afternoon that I was envisioning today. I just wanted the update notifications to stop.
SmoovySmoov said:
Have a rooted Verizon HTC One M8. Didn't have a custom rom on it. I was just happy with not having ads, and being able to have access to files on the phone. The one problem that I kept having was it constantly telling me that I needed to do an update. I tried freezing Update files in Titanium Backup, but I would still see the notifications. Followed advice elsewhere on the internet, and tried to Force Close Download Manager. I then went into TWRP and wiped Cache and Dalvic Cache. Now, it's completely stuck on the white HTC screen on bootup. I can boot into Recovery, but I'm not sure what to do to get the phone back to working condition.
Please help! This is not the Sunday afternoon that I was envisioning today. I just wanted the update notifications to stop.
Click to expand...
Click to collapse
Were You temp rooted or did you s off?
dottat said:
Were You temp rooted or did you s off?
Click to expand...
Click to collapse
I am S-Off'd.
SmoovySmoov said:
I am S-Off'd.
Click to expand...
Click to collapse
I have two solutions. One that wipes and one that doesn't. The one that doesn't you will need to reflash twrp and a su.zip when done but it's easy. Sound ok?
Run the exe on the first post here. Make sure your phone is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2883845
Official RUU 3.28.605.4 EXE/ZIP
dottat said:
I have two solutions. One that wipes and one that doesn't. The one that doesn't you will need to reflash twrp and a su.zip when done but it's easy. Sound ok?
Run the exe on the first post here. Make sure your phone is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2883845
Official RUU 3.28.605.4 EXE/ZIP
Click to expand...
Click to collapse
So this would take me back to not rooted, or am I reading that incorrectly? If so, is there no way to stay rooted, just to reflash stock rom?
Yes. But you will still get nagged to update too. If you want to simply flash stock then flash this one via recovery. http://forum.xda-developers.com/showthread.php?t=2914922
[ROM][10/22/14] - Stock Rooted 4.4.4 - OTA 3.28.605.4 - W/P - BusyBox and Root - UP!
Rerooting the phone after updating using the exe is easy to do though
SmoovySmoov said:
So this would take me back to not rooted, or am I reading that incorrectly? If so, is there no way to stay rooted, just to reflash stock rom?
Click to expand...
Click to collapse
dottat said:
Yes. But you will still get nagged to update too. If you want to simply flash stock then flash this one via recovery. http://forum.xda-developers.com/showthread.php?t=2914922
[ROM][10/22/14] - Stock Rooted 4.4.4 - OTA 3.28.605.4 - W/P - BusyBox and Root - UP!
Rerooting the phone after updating using the exe is easy to do though
Click to expand...
Click to collapse
So, I have your original method downloading. Are you saying that after I flash that, and then reroot it (which I will need help with as well, since I used Sunshine before), I won't get nagged to do an update all the time?
SmoovySmoov said:
So, I have your original method downloading. Are you saying that after I flash that, and then reroot it (which I will need help with as well, since I used Sunshine before), I won't get nagged to do an update all the time?
Click to expand...
Click to collapse
You will be up to date. When you flash twrp You can grab the latest su.zip from here http://download.chainfire.eu/supersu
Wipe cache when flashing su.
Sunshine was an exploit to gain s off. Not root. S off means you can flash whatever you want. In this case, root is just an app you flash.
dottat said:
You will be up to date. When you flash twrp You can grab the latest su.zip from here http://download.chainfire.eu/supersu
Wipe cache when flashing su.
Sunshine was an exploit to gain s off. Not root. S off means you can flash whatever you want. In this case, root is just an app you flash.
Click to expand...
Click to collapse
Still have about 15 minutes on the download. Sorry for all the questions, but I want to make sure I get what all you are saying.
1) Once the download finishes, I run the program and follow the prompts. This will return me to stock, not rooted.
2) I then need to flash SuperSU using TWRP. This will get me rooted again? Where do I place the .zip on my external SD card? I've had problems with TWRP in that I never see anything that I can install when I go to the Install screen there. It just says TWRP. No files. I try to navigate to the external SD, but there's never anything there that I can install.
SmoovySmoov said:
Still have about 15 minutes on the download. Sorry for all the questions, but I want to make sure I get what all you are saying.
1) Once the download finishes, I run the program and follow the prompts. This will return me to stock, not rooted.
2) I then need to flash SuperSU using TWRP. This will get me rooted again? Where do I place the .zip on my external SD card? I've had problems with TWRP in that I never see anything that I can install when I go to the Install screen there. It just says TWRP. No files. I try to navigate to the external SD, but there's never anything there that I can install.
Click to expand...
Click to collapse
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
---------- Post added at 03:19 PM ---------- Previous post was at 03:09 PM ----------
Here's a quick how to..for after you run that exe.
Take the su.zip to your internal storage.
Download twrp 2.8.1.0 here
http://techerrata.com/browse/twrp2/m8_wlv
Download fastboot/adb here
https://www.androidfilehost.com/?fid=23501681358559711
Extract the fastboot/adb zip. Copy the new twrp image into this new folder. Open the newly extracted folder and while holding the shift button right click on your mouse. Select open command prompt here.
Put phone in fastboot mode and connect to your pc. Run the following command to flash twrp.
Fastboot flash recovery openrecovery-twrp-2.8.1.0-m8_wlv.img
After this completes select boot loader on the phone screen. Then select recovery. Choose wipe and select advanced. Only select cache and wipe. When done hit the home button icon at the bottom. Then click install. Scroll down and find your su.zip and flash it. Reboot when done
dottat said:
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
Click to expand...
Click to collapse
Not 100% on that one. Are you meaning having adb set up on my computer? If so, no. I tried once before, and couldn't figure out what I was doing. I achieved root by using Sunshine to S-Off, and then Klingo One Click Root Method.
SmoovySmoov said:
Not 100% on that one. Are you meaning having adb set up on my computer? If so, no. I tried once before, and couldn't figure out what I was doing. I achieved root by using Sunshine to S-Off, and then Klingo One Click Root Method.
Click to expand...
Click to collapse
Edited my last post
dottat said:
Edited my last post
Click to expand...
Click to collapse
It keeps saying that the Update Utility cannot see my phone.
SmoovySmoov said:
It keeps saying that the Update Utility cannot see my phone.
Click to expand...
Click to collapse
Can you install team viewer and pm me the details to screen share.
dottat said:
Can you install team viewer and pm me the details to screen share.
Click to expand...
Click to collapse
I wasn't in fastboot. It's updating now.
SmoovySmoov said:
I wasn't in fastboot. It's updating now.
Click to expand...
Click to collapse
? good
dottat said:
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
---------- Post added at 03:19 PM ---------- Previous post was at 03:09 PM ----------
Here's a quick how to..for after you run that exe.
Take the su.zip to your internal storage.
Download twrp 2.8.1.0 here
http://techerrata.com/browse/twrp2/m8_wlv
Download fastboot/adb here
https://www.androidfilehost.com/?fid=23501681358559711
Extract the fastboot/adb zip. Copy the new twrp image into this new folder. Open the newly extracted folder and while holding the shift button right click on your mouse. Select open command prompt here.
Put phone in fastboot mode and connect to your pc. Run the following command to flash twrp.
Fastboot flash recovery openrecovery-twrp-2.8.1.0-m8_wlv.img
After this completes select boot loader on the phone screen. Then select recovery. Choose wipe and select advanced. Only select cache and wipe. When done hit the home button icon at the bottom. Then click install. Scroll down and find your su.zip and flash it. Reboot when done
Click to expand...
Click to collapse
Okay, so I completed the first part, and am back to not rooted. Not completely following your instructions above, though. I extracted the fastboot/adb file to my Desktop. It's just those files. There's no folder. Are you saying I just need to create a folder with them in it, and then add the twrp file to it?
SmoovySmoov said:
Okay, so I completed the first part, and am back to not rooted. Not completely following your instructions above, though. I extracted the fastboot/adb file to my Desktop. It's just those files. There's no folder. Are you saying I just need to create a folder with them in it, and then add the twrp file to it?
Click to expand...
Click to collapse
Unzip the rar file and then continue
Edit...You should have extracted to a folder not current directory. You want those files within a folder and then yes place the twrp in there too
Once you run through this all it will make better sense going forward.
dottat said:
Unzip the rar file and then continue
Edit...You should have extracted to a folder not current directory. You want those files within a folder and then yes place the twrp in there too
Once you run through this all it will make better sense going forward.
Click to expand...
Click to collapse
Feel like I'm close, but it's not 100% yet.
Got the phone back to operational. Went looking in apps, and SuperSU was not listed. Everything says that I'm rooted, but it was not there. Googled SuperSU apk, and followed a link to download it via Google Play. Redownloaded it, and when opened, it says "There is no SU binary installed, and SuperSU cannot install it." Also, the damn update that started this whole mess just popped up on the screen again.
SmoovySmoov said:
Feel like I'm close, but it's not 100% yet.
Got the phone back to operational. Went looking in apps, and SuperSU was not listed. Everything says that I'm rooted, but it was not there. Googled SuperSU apk, and followed a link to download it via Google Play. Redownloaded it, and when opened, it says "There is no SU binary installed, and SuperSU cannot install it." Also, the damn update that started this whole mess just popped up on the screen again.
Click to expand...
Click to collapse
Did you flash the su.zip in recovery?
Also, since you wiped cache the ota should be gone. Go to settings and chose app manager. Slide over to the right until you see all at the top. Hit the magnifying glass and search for htcdm. When it finds it click on it. Force stop and clear data for it.
Also, since you are running stock with just a few tweaks of your own, you may want to flash santods ota killer zip. It would prevent what started this off in the first place and remove the leftover prompt in the same shot.
https://www.androidfilehost.com/?fid=23329332407587434
This afternoon I applied OTA 3.1 to my Shield Tablet, and reinstalled CWM and flashed supersu. My tablet booted correctly but I don't have root. If I open the SuperSU app, I get "there is no SU binary installed and SuperSU cannot install it. This is a problem!" anyone know how to fix this?
Thanks
I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.
Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk
sixstringedmatt said:
Reflash recovery via fastboot, boot into CWM then reflash latest SuperSU in CWM.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.
Aventura5 said:
That's what I did, same as when I first rooted, but the SuperSU app says there's no SU binary and CWM is there but disappears after a reboot.
Click to expand...
Click to collapse
I'm having the same problem.
Im also with the same problem, on 3.0 i used kingroot, but with 3.1 doesnt work also.
Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.
King root 4.5 works to root easily
Got it rooted again
I finally got it rooted again.
1) Put supersu.zip on to sd card.
2) Flashed TWRP with ADB fastboot.
3) Rebooted into recovery.
4) Flashed supersu.zip from the sd card.
5) Rebooted
After that it was finally rooted again. Hope this helps anybody else who has this problem.
Unfortunately though since I got my tablet when it first came out I have a recalled one. This will be my 4th RMA. LOL
danjull said:
Not sure how it works with cwm, not sure if there's a fine manager. But in twrp try mounting system, go in to advanced>file manager and go to the folder 'system' and rename the file 'recovery-from-boot.p' to 'recovery-from-boot.bak' or something else, and flash cwm or twrp again. Then flash your super user again.
Click to expand...
Click to collapse
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
EDIT: This worked and now CWM sticks, but i still get the SU binary not installed error.
Aventura5 said:
Thanks I'll try that as soon as I can. In CWM there's no file manager but you can use an adb shell. I'm just a little nervous disabling a file named recover from bootloop. After i root do i re-enable it?
Click to expand...
Click to collapse
No. It restores stock recovery on first reboot.
Kingroot worked for me guys
What I don't understand is how the zip can install the SuperSU app as a system app, but not install the SU binary. Is it possible to manually copy the Su binary to my device? I have root access in recovery mode.
Dose anyone have any idea why this happens?
It works now with the new version of supersu
Is there a guide for rooting the shield from 3.0 and up? Thanks.
tecnoworld said:
Is there a guide for rooting the shield from 3.0 and up? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.
tecnoworld said:
That's for 2.0...am I wrong? I'd like a similar guide for newer versions, namely 3.0 and on. Thanks.
Click to expand...
Click to collapse
It dose say for 2.0, but it should work on everything. This is the "real" way, other methods are hacks that work only on certain versions. I prefer this method, it gives you the most insurance against damage, but you could always just use kingo root. Also, versions 2.x and 3.x are both lollipop.
Aventura5 said:
I also just noticed that CWM is not there now. It was there when I flashed it with fast boot, but now it disappeared from which I don't understand. Also just to clarify, SuperSU installed as a system app from the zip, I didn't download it from the play store.
Click to expand...
Click to collapse
Just out of curiosity, doesn't fastboot boot (image of recovery) just boot into the recovery and not flash it?
From previous experience, to reflash recovery you need something like flash_image or a way to write the image on the recovery partition... Correct me if I'm wrong...
Just learned of this method from a Reddit user - https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Sharing here.
Neffy27 said:
Just learned of this method from a Reddit user - https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Sharing here.
Click to expand...
Click to collapse
I also followed this guide a couple days ago. Running OPW28.2 with Magisk 16.0 Still working on getting Xposed to work without bootloop.
Neffy27 said:
Just learned of this method from a Reddit user - https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Sharing here.
Click to expand...
Click to collapse
Will modifiying build.prop will make error
Did you follow the option for Devices that have A/B partitions?
So basically, all I need to do is go into magisk, uninstall, restore images. Then apply OTA update. Once the update displays "step 2", go back into Magisk and Install to second slot?
I tried this method, but when I hit "Restore Images" it says "Stock backup does not exist!". Is there a way of putting a stock boot.img for my current FW in the proper location for it to recognize it as a backup? I tried looking this up but got no helpful solution.
I think if you installed Magisk via Recovery like I did it won't keep a backup of the boot.img. I think it does that only if you install Magisk outside of Recovery, which requires that you have a copy of the original boot.img.
Just get a copy of the firmware for your version, extract and write back the original boot.img via Fastboot and then update the OTAs (assuming you made.no changes to your system partition). Then reinstall the custom Recovery if you want and then Magisk again.
I have tried flashing just boot.img, but it didn't work. Could be adaway changing hosts file? Anyhow I just end up flashing back to stock
(minus clearing userdata) taking a few OTA's then re-reooting. Have been able to keep my data no issues. Takes a while but it's what it takes.
I could not get this to work either.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
OTA could not be applied..
I tried to uninstall Magisk completely, and I boot-looped.