Related
Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?
thinkhope said:
Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?
Click to expand...
Click to collapse
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.
absolutelygrim said:
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.
Click to expand...
Click to collapse
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.
thinkhope said:
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.
Click to expand...
Click to collapse
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know
absolutelygrim said:
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know
Click to expand...
Click to collapse
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.
thinkhope said:
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.
Click to expand...
Click to collapse
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot
absolutelygrim said:
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot
Click to expand...
Click to collapse
Thank you very much!!
Sent from my One X using xda app-developers app
I accidentally pushed the wrong framework-res.apk file in adb and now im stuck in a bootloop
I have stock recovery and am rooted
I can enter download mode but I don't want to lose all my data.
What can I do?
If you didn't make a nandroid backup... You will have to re-flash your rom over again
Edited:
Just noticed your on stock... Yikes. Looks like you'll have to Odin that thing. When pushing apks. Set the permissions to rw-r-r before rebooting
And definitely watch what your pushing
Annex1 said:
If you didn't make a nandroid backup... You will have to re-flash your rom over again
Edited:
Just noticed your on stock... Yikes. Looks like you'll have to Odin that thing. When pushing apks. Set the permissions to rw-r-r before rebooting
And definitely watch what your pushing
Click to expand...
Click to collapse
I'd prefer people use the heimdall oneclick (check 'Projects' out my sig).
Odin always makes things complicated, and it's closed source.
Heimdall is open source, documented, and actively maintained.
Just a suggestion
Or try using Heimdal One-Click to flash a custom kernel only. Then find a kernel you can flash in CWM that has TWRP. Then you can copy over your original framework-res.apk in the TWRP file manager and see if it will boot.
None of that will mess with your files except framework-res.
It's been a long time since I've been on stock recovery but does ADB pick up the phone when its in recovery?
hechoen said:
It's been a long time since I've been on stock recovery but does ADB pick up the phone when its in recovery?
Click to expand...
Click to collapse
It does on the blastoff kernel in eollies oneclick
bhundven said:
It does on the blastoff kernel in eollies oneclick
Click to expand...
Click to collapse
I know it does with custom recoveries but if he can get it picked up in the stock recovery he can just push the original .apk back. Easy. If it picks it up.
hechoen said:
I know it does with custom recoveries but if he can get it picked up in the stock recovery he can just push the original .apk back. Easy. If it picks it up.
Click to expand...
Click to collapse
what does it matter? Push the apk with custom recovery. I don't know of anything you can flash with stock recovery.
bhundven said:
what does it matter? Push the apk with custom recovery. I don't know of anything you can flash with stock recovery.
Click to expand...
Click to collapse
F. I'm off topic.
You're rooted on stock recovery. Install root explorer, over write the framework-res.apk, reboot.
Thank you so much guys.
I was able to flash a custom kernal with Heimdall and I pushed the right framework-res and now everythings back to normal
I'm truly grateful for all your speedy and helpful replies.
I would advise you to flash a simple zip (take any simple mod or gapps) valid for your Android version and edit its updater script to just flash the system folder. Then add the zip a system folder with framework folder and put your right framework-res.apk,
This way you just flash, fix permissions and good to go... no Heimdall, kernel or any other change, and you're back in business.
Another even simpler way is to use our device's Aroma File Manager and simply copy the right file and fix permissions...
First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?
I just got the OTA Update to Lollipop
and after i download the files, i press the install and reboot,then my nexus goes to recovery mode (CWM 6)
and then there appears :
. . . (theres still some description)
E:signature verification failed
then i just reboot and get my nexus still on 4.4
im actually forget which ROM im using right now
but in settings , it is KTU84P
FYI : I just unrooted this devices and this happened too when i was trying to upgrade with Nexus Update Checker.
Please help me guys
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
jasonftfw said:
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
Click to expand...
Click to collapse
how to make it sure/check it , that im using stock ROM or not
and how to uninstall CWM ?
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
jasonftfw said:
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
Click to expand...
Click to collapse
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
---------- Post added at 03:01 AM ---------- Previous post was at 02:56 AM ----------
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
just got the OTA notification again, so I'll give it another shot (yeah, i just quoted myself)
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
jasonftfw said:
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
Click to expand...
Click to collapse
thanks but I got the OTA notification again and is now installing without problems
DarknessWarrior said:
thanks but I got the OTA notification again and is now installing without problems
Click to expand...
Click to collapse
Never hurts to know how to sideload for future.
jasonftfw said:
Never hurts to know how to sideload for future.
Click to expand...
Click to collapse
agreed.
I just installed Android Sdk and downloaded the ota from google and im having problems it doesnt side load
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Falconite said:
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Click to expand...
Click to collapse
check out the toolkit from wugfresh, that might be the easiest way for you if you don't know what you're doing... maybe take some notes so that you do remember what you're doing for future.
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...