Related
I got the 2.3.5 Update OTA on my One-click-root Nexus and applied the update, but now I'm stuck on the android/exclamation point screen.
What do I do??
gnuf99 said:
I got the 2.3.5 Update OTA on my One-click-root Nexus and applied the update, but now I'm stuck on the android/exclamation point screen.
What do I do??
Click to expand...
Click to collapse
That's the stock recovery - hold power and hit vol up to get the menu.
I've been doing that, but nothing happens.
I did a battery pull, and it rebooted in 2.3.4
So what am I doing wrong? Do I need to change something before trying the update again?
Hold power and slide from volume down to volume up. But that wont do u any good you need to flash a custom recovery and reflash super user.
Sent from my Nexus S 4G using Tapatalk
So I goofed something up on my phone?
Is there a way to do this without losing all my app info/game saves?
I was going to run a TItanium backup.
And sorry, I'm a total noob with this.
ROM Manager, would I flash an older ROM or the ClockworkMod Recovery?
At that point could i just install the update and re root with Shabby Penguin's one click and then get all my app data back from Titanium backup?
gnuf99 said:
So I goofed something up on my phone?
Is there a way to do this without losing all my app info/game saves?
I was going to run a TItanium backup.
And sorry, I'm a total noob with this.
ROM Manager, would I flash an older ROM or the ClockworkMod Recovery?
At that point could i just install the update and re root with Shabby Penguin's one click and then get all my app data back from Titanium backup?
Click to expand...
Click to collapse
Nothing is goofed up if you rebooted into 2.3.4.
The update did not apply. Did you receive the OTA or download it manually?
If you are unlocked just flash CWM via fastboot and apply it from there.
If you are locked then you can go back into the stock recovery, hold power down and hit vol up (in that order) to get the menu and apply the update. You may want to ensure it is in the root of the sdcard and named update.zip.
The OTA does not wipe nor is a wipe necessary, so you shouldn't be losing any data/apps.
I got the update OTA, but not it's not asking me if I want to apply it.
I'm sorry I'm such a noob here, but step wise.
If I boot up with Vol UP, I can then go to Recovery and get to ClockWork Recovery.
From there do I just hit update from SD card?
gnuf99 said:
I got the update OTA, but not it's not asking me if I want to apply it.
I'm sorry I'm such a noob here, but step wise.
If I boot up with Vol UP, I can then go to Recovery and get to ClockWork Recovery.
From there do I just hit update from SD card?
Click to expand...
Click to collapse
Yeah, choose apply update. Choose your zip from the SD card and apply.
It will go through a series of asserts and then apply if it passes. If you've modified any of the checked system files, boot image or kernel it's likely going to fail.
Well, I didn't alter any of them on purpose
I used Shabby Penguin's one click root so I could use Titanium Backup only. (Although now I'll probably add tethering to the list) So I don't think I changed any kernel files.
It's saying it can't find the file. Whatever downloaded must have gotten deleted somehow. I may just download the update and do it myself like everyone else.
Just to clarify. I place the update.zip in the root and select apply update on the ClockWorkMod Recovery, and that's it?
I was waiting to just get the update OTA organically hoping it would avoid these problems, lol.
gnuf99 said:
Well, I didn't alter any of them on purpose
I used Shabby Penguin's one click root so I could use Titanium Backup only. (Although now I'll probably add tethering to the list) So I don't think I changed any kernel files.
It's saying it can't find the file. Whatever downloaded must have gotten deleted somehow. I may just download the update and do it myself like everyone else.
Just to clarify. I place the update.zip in the root and select apply update on the ClockWorkMod Recovery, and that's it?
I was waiting to just get the update OTA organically hoping it would avoid these problems, lol.
Click to expand...
Click to collapse
In CWM use the choose zip file from SD card option, then you can pick the file regardless of it's name.
That's it - if you are stock (other than rooting) it should apply without any issues.
You may need to reflash CWM and delete /etc/install-recovery.sh to keep CWM installed. I haven't looked at the update itself to see if it is installing the script to reflash the stock recovery.
I had this problem too. I rebooted and its back to 2.3.4. I will attempt to go to 2.3.5 today once I have more time and post my findings here. If anyone has any success please keep updating this thread.
It looks like I have to reflash CWM in order to restore Super User.
My bootloader is still unlocked, but it won't let me run/install CWM. How do I do this?
Jagar, I did finally figure this out after reading through the code in the rooting .bat that Shabby Penguin put together.
basically his file has the Clockwork Recovery image that you need.
Boot up in bootloader.
then type
fastboot flash recovery ______.img whatever image you have.
Then select RECOVERY on the bootloader menu and now you can install the superuser.zip file to re-root.
you might wanna just run the new one click again, make sure its version 2.0.. it will do teh dirty work for ya
Seriously Shabby, big props to you for automating that process. I learned much more from your code than reading through all those other posts
@gnuf99 although you succeeded in getting root , please do read the guides abt adb and fastboot. This will be always handy for you, indifferent of the device you'll use later.
Sent from my Transformer TF101 using Tapatalk
this forum is here to help people and spread knowledge, not so we can talk down to those less experienced then us. everyone starts somewhere...
removed. unnecessary comment by me .
shabbypenguin said:
you might wanna just run the new one click again, make sure its version 2.0.. it will do teh dirty work for ya
Click to expand...
Click to collapse
*REMOVED* Looking on another thread.
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?
Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link
If all else fails flash the google stock images
Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...
I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.
Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.
Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.
Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.
If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095
Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5
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