Related
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
*sigh* look around...
Sent from my SCH-I510 using xda premium
jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
Here you gotaken from my thread)
5. How to root a pure stock FP1 and make CWM stick after reboot - Turn off your phone, use ODIN to flash CWM (0302 blue latest version - http://imnuts.net/zU2jkn) with "reboot" option unchecked,
After completed, disconnect the usb cable, pull the battery, reinstall battery, hold down volume up+home+power to boot into cwm,
(if you failed to boot into cwm and your phone boot up you have to redo the process). Now flash Super user package zip (Superuser-3.0.7-efgh-signed.zip - and su-bin-3.0.3.2-efghi-signed.zip (both can be download from here (look for Gingerbread) : http://androidsu.com/superuser/
Reboot phone. Use Root explore (or Root browser lite or ES file explorer) go to /system/ect/install-recovery.sh script, tab on mount R/W button (upper top). Long press on the script and in the popup menu, select permission, unchecked all permission then save the file.
Shutdown phone, re-Odin cwm again, once done reboot, now cwm should stick. Once phone came up, to verify root on your phone, you can download "root checker basic" from the Market. If you have issue, download "superuser update fixer" app from the market and run it.(no reboot required). That's it.
Wow great help with links and everything thanks a lot
Sent from my SCH-I510 using xda premium
Just to add to this very helpfull Post, this are the problems I run into and how I fixed them so that if anyone comes up with the same issues, you have the solution:
1. Flashing CWM with odin was failing, I changed usb port, I rebooted the computer, and the problem was that I was doing it without the battery, as soon as I put the battery in the phone and tried odin, it was succesfull, so, what I think is that there is not enough power to the phone just using the usb cable and that is why it was failing to flash.
2. after I flashed superuser and su-bin files, rebooted the phone, but as soon as my phone was on, and connected to the internet, for some reason, the phone automatically downloaded and updated this two files, so I could not change the recovery sh script, my solution, disabled data, reflash cwm, and the root files, then I was able to change the permissions of the file.
I AM NOW ROOTED!!!! thanks buhohitr
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Again, please look around...
Sent from my SCH-I510 using xda premium
jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
buhohitr said:
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
Click to expand...
Click to collapse
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
jorge3687 said:
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
Click to expand...
Click to collapse
Nice! glad you got it working.
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
Click to expand...
Click to collapse
I see all the replies with answers now. Don't know why they weren't there before.
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
I see all the replies with answers now. Don't know why they weren't there before.
Click to expand...
Click to collapse
well, since I could not get help from the experts, I just did it myself and wrote the process for other people to make it easier.
Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Sigh... http://forum.xda-developers.com/showthread.php?t=1832040
Sent from my SCH-I510 using xda premium
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.[/QUOTE]
jorge3687 said:
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Click to expand...
Click to collapse
[/QUOTE]
I had already tried the above without success. CWM was overwritten each time. There was another file to delete as well somewhere in system/ect which was also supposed to prevent recovery overwriting,mbut that solution proved just as fruitless.
I got itt working through trial and error, though. As it turns out, recovery actually UNmounts system after you flash a single file, so you must REmount after each if you are flashing multiple files. I do not see this "feature" explained anywhere. Maybe this is something fundamental about Linux which has escaped me over the years of android phone ownership.
Thank you for trying to help me even though.
It unmounts for safety reasons, and it's done by the package itself, not the recovery by default. You don't want power to be pulled from a filesystem in unix when it's mounted. The real issue isn't the unmount, but the mount itself seems wonky on this phone, so depending on how the CWM package is written, there's a good chance it won't be successful when it tries to mount the filesystems. It's better to mount them yourself if you're working with a package that wasn't specifically written with this phone in mind, and you even need to mount on some that are.
Hey,
I just did the 2.20 root method posted about a week ago, and I got to the white screen without a problem. I did the htc-dev stuff, and that worked too. I pressed Yes and unlocked my bootloader (or so I thought). I flashed TWRP recovery. However, I couldn't do anything else. My phone runs normally, but I checked and it is not rooted. I realize that the new 2.20 method is a temporary root, and I checked in its thread, and was pointed to this thread: http://forum.xda-developers.com/showthread.php?t=1952426. That isn't for Mac, and I wasn't able to find any way to root a 2.20 HOX, install SU, install a ROM, etc.
I installed a rom and all that on my old phone, a Motorola Atrix, without too many problems, so I'm not completely illiterate. Any help on this would be much appreciated. Thanks!
ilovesports said:
Hey,
I just did the 2.20 root method posted about a week ago, and I got to the white screen without a problem. I did the htc-dev stuff, and that worked too. I pressed Yes and unlocked my bootloader (or so I thought). I flashed TWRP recovery. However, I couldn't do anything else. My phone runs normally, but I checked and it is not rooted. I realize that the new 2.20 method is a temporary root, and I checked in its thread, and was pointed to this thread: http://forum.xda-developers.com/showthread.php?t=1952426. That isn't for Mac, and I wasn't able to find any way to root a 2.20 HOX, install SU, install a ROM, etc.
I installed a rom and all that on my old phone, a Motorola Atrix, without too many problems, so I'm not completely illiterate. Any help on this would be much appreciated. Thanks!
Click to expand...
Click to collapse
ok. first thing 1st: Did you ever install SU after flashing the recovery (twrp) ?
Crappyvate said:
ok. first thing 1st: Did you ever install SU after flashing the recovery (twrp) ?
Click to expand...
Click to collapse
no, because i don't know how to do it. should i flash it using fastboot (while the phone is in white screen)? if so, what file do I flash? I got a SU zip, but I'm not sure what to do with it. But I can confirm that I've installed twrp correctly, because I can go to twrp from the white screen by using the volume up/volume down buttons and the power button and going to Recovery.
Thanks for your help
ilovesports said:
no, because i don't know how to do it. should i flash it using fastboot (while the phone is in white screen)? if so, what file do I flash? I got a SU zip, but I'm not sure what to do with it. But I can confirm that I've installed twrp correctly, because I can go to twrp from the white screen by using the volume up/volume down buttons and the power button and going to Recovery.
Thanks for your help
Click to expand...
Click to collapse
reboot in recovery/twrp. install your su.zip (don't know where you got your su.zip and what it contains whether it has both the su binaries and Superuser apk ). Reboot. if you don't have Superuser apk download it from the market (chainfire version). Voila.
Crappyvate said:
reboot in recovery/twrp. install your su.zip (don't know where you got your su.zip and what it contains whether it has both the su binaries and Superuser apk ). Reboot. if you don't have Superuser apk download it from the market (chainfire version). Voila.
Click to expand...
Click to collapse
Okay, a couple more questions. Where should I get the su zip? I googled it and found a directory of a bunch of different versions of SU, but it hadnt been updated since like July. Also, what command do I use to install the su.zip?
./fastboot.OSX flash recovery su.zip doesn't work. I'm just now realizing that I should download it to phone memory and install in recovery from there.
Sent from my HTC One X using xda app-developers app
ilovesports said:
Okay, a couple more questions. Where should I get the su zip? I googled it and found a directory of a bunch of different versions of SU, but it hadnt been updated since like July. Also, what command do I use to install the su.zip?
./fastboot.OSX flash recovery su.zip doesn't work. I'm just now realizing that I should download it to phone memory and install in recovery from there.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
You flash the su.zip from inside twrp
http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
ilovesports said:
Okay, a couple more questions. Where should I get the su zip? I googled it and found a directory of a bunch of different versions of SU, but it hadnt been updated since like July. Also, what command do I use to install the su.zip?
./fastboot.OSX flash recovery su.zip doesn't work. I'm just now realizing that I should download it to phone memory and install in recovery from there.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
1. you told me you had an su.zip !! anyway: http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
2. I said reboot in twrp/recovery (do not flash su.zip in fastboot) and hit the install menu, select the su.zip and swipe to flash
3. go back to main menu and hit reboot and then system
4. download SuperSu.apk from chainfire in the Market
5. open it, it'll probably ask you if you want to update the binaries, go ahead and do so.
You should be good to go.
Crappyvate said:
1. you told me you had an su.zip !! anyway:
2. I said reboot in twrp/recovery (do not flash su.zip in fastboot) and hit the install menu, select the su.zip and swipe to flash
3. go back to main menu and hit reboot and then system
4. download SuperSu.apk from chainfire in the Market
5. open it, it'll probably ask you if you want to update the binaries, go ahead and do so.
You should be good to go.
Click to expand...
Click to collapse
Yeah, I had it, but I wasn't sure if I had the right one. I did and its all straight now. I was able to install su via twrp and everything worked. I now have root access. One last question (and I realize I've asked a lot of you guys, and I do really appreciate all your help), do I need to take any special steps or precautions when installing custom roms? On my atrix I just saved them to memory and then installed via cwm
Sent from my HTC One X using xda app-developers app
ilovesports said:
Yeah, I had it, but I wasn't sure if I had the right one. I did and its all straight now. I was able to install su via twrp and everything worked. I now have root access. One last question (and I realize I've asked a lot of you guys, and I do really appreciate all your help), do I need to take any special steps or precautions when installing custom roms? On my atrix I just saved them to memory and then installed via cwm
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes. dont fu**ing flash icecoldjelly.. or any international ROM
and always ALWAYS flash the boot.img from the rom you want to flash, then flash the rom
ilovesports said:
Yeah, I had it, but I wasn't sure if I had the right one. I did and its all straight now. I was able to install su via twrp and everything worked. I now have root access. One last question (and I realize I've asked a lot of you guys, and I do really appreciate all your help), do I need to take any special steps or precautions when installing custom roms? On my atrix I just saved them to memory and then installed via cwm
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
there is even an app for that now http://forum.xda-developers.com/showthread.php?t=1963896
Crappyvate said:
there is even an app for that now http://forum.xda-developers.com/showthread.php?t=1963896
Click to expand...
Click to collapse
Thanks, I used that. I installed a ROM. It took a long time (especially in splash screen/boot animation) so i thought i bricked my phone. i didn't. it works great. thanks!
ilovesports said:
Thanks, I used that. I installed a ROM. It took a long time (especially in splash screen/boot animation) so i thought i bricked my phone. i didn't. it works great. thanks!
Click to expand...
Click to collapse
no problem and for thanks there is a button, use it
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?
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...
Ran into problems with my phone the other day and had to do a wipe, upon reboot, it says I am not rooted (with root checker). Upon checking I am still Unlocked/S-off, but am unable to gain root. SuperSU says there is no SU binary, and when I try to push SU.img all I get is "error: device '(null)' not found". But, if I do a device check it shows that it is connected.
I have tried everything I can think of, starting from the very beginning and trying to reroot all over again, but it won't let me push the SU.img file. Any help would be greatly appreciated.
ShiftyBob said:
Ran into problems with my phone the other day and had to do a wipe, upon reboot, it says I am not rooted (with root checker). Upon checking I am still Unlocked/S-off, but am unable to gain root. SuperSU says there is no SU binary, and when I try to push SU.img all I get is "error: device '(null)' not found". But, if I do a device check it shows that it is connected.
I have tried everything I can think of, starting from the very beginning and trying to reroot all over again, but it won't let me push the SU.img file. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using TWRP to install SuperSU flash able?
The_scam said:
Have you tried using TWRP to install SuperSU flash able?
Click to expand...
Click to collapse
Every link I have found is dead. Do you have one you could send me, or point me to an active link?
ShiftyBob said:
Every link I have found is dead. Do you have one you could send me, or point me to an active link?
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/
The_scam said:
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
Flashed it using TRWP, still no luck. Other than adding/deleting apps, I literally haven't changed anything since I rooted it a year ago (I'm still running 6.0).
I'm out of ideas...
ShiftyBob said:
Flashed it using TRWP, still no luck. Other than adding/deleting apps, I literally haven't changed anything since I rooted it a year ago (I'm still running 6.0).
I'm out of ideas...
Click to expand...
Click to collapse
Just wipe all your data and run an Ruu
The_scam said:
Just wipe all your data and run an Ruu
Click to expand...
Click to collapse
I'll give it a shot. Also worth noting is that when I rooted a year ago, I immediately made a Nandroid backup (as I always do). When restoring from the backup, it puts my phone back in the same state it was at the time I made the backup... except for having root.
ShiftyBob said:
I'll give it a shot. Also worth noting is that when I rooted a year ago, I immediately made a Nandroid backup (as I always do). When restoring from the backup, it puts my phone back in the same state it was at the time I made the backup... except for having root.
Click to expand...
Click to collapse
The root functionality lives (AFAIK) with the kernel in the boot partition. Restoring your backup would only affect your system and data partitions. Somehow when you did the original wipe it must've given you the stock kernel/boot partition. I agree that starting over with an RUU and going from there is probably your best option. You can probably restore a data backup when you're done though.