Related
Hey friends.
I've got a little Problem.
At first I've some wifi issues of my one s.
Today I got the message, that there is an Ota update. I hoped, that it fixes the wifi issues (disconnect in standby and doesn't reconnect after wake up).
I've the official shipped Rom with opened hboot and root. I rooted it for apps like addblocker.
So after I downloaded my update the phone turned of to install it. Started in recovery where it aborted.
I think it is why I installed Cwm for root.
Is there a way how to install the update? Maybe to reinstall the original recovery?
I don't really want to install a custom rom.
Thanks a lot
sk1786 said:
Hey friends.
I've got a little Problem.
At first I've some wifi issues of my one s.
Today I got the message, that there is an Ota update. I hoped, that it fixes the wifi issues (disconnect in standby and doesn't reconnect after wake up).
I've the official shipped Rom with opened hboot and root. I rooted it for apps like addblocker.
So after I downloaded my update the phone turned of to install it. Started in recovery where it aborted.
I think it is why I installed Cwm for root.
Is there a way how to install the update? Maybe to reinstall the original recovery?
I don't really want to install a custom rom.
Thanks a lot
Click to expand...
Click to collapse
If the bootloader is unlocked, relock it through the HTC One S Toolkit. Also, I might just be able to find a .img file of the stock recovery for you. I will look now.
EDIT: I have attached the stock recovery file. Rename it to "recovery.img" (without the quotes) and flash it in fastboot (replace the obviously fake names with the actual directories):
Code:
cd /sdk/platform-tools (or whatever you keep fastboot and adb in)
adb reboot bootloader (or boot into it manually and skip this)
fastboot devices (just to verify)
fastboot flash recovery recovery.img (it'll say a lot of crap and then tell you when it's copied)
fastboot reboot (or you can go back to the bootloader and get into recovery from there and skip this step)
Also, I have included a picture of a lion. Why? Because I can.
EDIT2: The recovery was to big to upload so I put it on mediafire: http://www.mediafire.com/?unfu1p66545xu7z
sk1786 said:
So after I downloaded my update the phone turned of to install it. Started in recovery where it aborted.
I think it is why I installed Cwm for root.
Is there a way how to install the update? Maybe to reinstall the original recovery?
I don't really want to install a custom rom.
Thanks a lot
Click to expand...
Click to collapse
Yes you need to install stock recovery for OTA update to work.
Use OTA Rootkeeper to save your root file or you will loose root after the update.
Thank you auf lot I'll try it today.
Edit: Didn't had to relock my bootloader. Only did your Fastboot-Instructions and run the Voodoo OTA Rootkeeper. Now everything works fine.
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
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...
So I bought my pixel back in Dec, unlocked bootloader and rooted. All was well. Then a few weeks ago I somehow got the OTA update. Not entirely sure how...it must have forced it. Regardless, I lost root now.
I used the skipsoft tool prior and it worked great. I ran the tool again, but my build is 7.1.1 NOF26V. Bought from the google play store BTW.
That build isnt an option that I can select when I run the tool, so I dont know if I can reroot or what.
Anyone experience this yet and can shed some light? Thanks!!!
chugger93 said:
So I bought my pixel back in Dec, unlocked bootloader and rooted. All was well. Then a few weeks ago I somehow got the OTA update. Not entirely sure how...it must have forced it. Regardless, I lost root now.
I used the skipsoft tool prior and it worked great. I ran the tool again, but my build is 7.1.1 NOF26V. Bought from the google play store BTW.
That build isnt an option that I can select when I run the tool, so I dont know if I can reroot or what.
Anyone experience this yet and can shed some light? Thanks!!!
Click to expand...
Click to collapse
Can't help yoy with the toolkit, dont use it. In that thread would be the place to ask. I can help you with the non-toolkit method.
Get fastboot and adb from google and unzip it to a folder.
https://developer.android.com/studio/releases/platform-tools.html
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC3 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Turn it off then hold power and vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
that worked sir...thank you!!!
For anyone else wondering about this, I had this same version and used the toolkit with the option to root any variant (something a long these lines) and it worked no problem.