Voodoo OTA says rooted but is fake. This happened after jb update - Transformer TF300T Q&A, Help & Troubleshooting

I updated to jb. Use voodoo to unroot and restore root back. And it shows that i am rooted but is not.
Anyone else with this issue?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Yes, and I'm not 100% sure it's resolved. Most likely, if you access your tablet via adb you can su - root, and get a # prompt meaning root access, but it seems root access has been cut off at an application level.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

carlosraf20 said:
I updated to jb. Use voodoo to unroot and restore root back. And it shows that i am rooted but is not.
Anyone else with this issue?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
there's a ongoing discussion here, i'm one of the people who lost root like you, but looks like they found something...

nooktablet said:
there's a ongoing discussion here, i'm one of the people who lost root like you, but looks like they found something...
Click to expand...
Click to collapse
Hey nooktablet... before we were in the same boat, but calisro found a working solution!
STEP BY STEP
NOTE: After Step 7, go back to original CMD Window where you SU;d.
If you don't want to go back to Windows #1, you can open a new shell session in CMD Windows #2 with SU privileges.
7a) adb shell
7b) su -
Then continue on to the remaining steps.

Related

[Q] Trying to nachoroot, but...

In nachoroot stage2, I get:
Code:
cannot create /data/local.prop: permission denied
What's wrong? someone says nachoroot works on transformer classic
Couple of members got that same message in the NachoRoot thread.
Here's what one had to say
http://forum.xda-developers.com/showpost.php?p=21152218&postcount=70
You could down grade firmware and use RazorClaw
Sent from my Transformer TF101 using Tapatalk
I just used vipermood root tool... Found it in the Asus prime development section... It's pretty much a 1 click root tool that works for our tablets (tf101) as well... I was rooted with super user in the time it takes to reboot twice... And vipermood root tool uses nacho root to gain root
Sent from my Transformer TF101 using Tapatalk
jimbo1qaz said:
In nachoroot stage2, I get:
Code:
cannot create /data/local.prop: permission denied
What's wrong? someone says nachoroot works on transformer classic
Click to expand...
Click to collapse
I had the same problem with mine. I read somewhere that it was something to do with it being a B40 model. What model is yours? I have recently got mine back from Asus through RMA, they replaced the motherboard, so not sure if that is anything to do with it.
Seg

Took the update to JB, but can't get my root back

OK, need someone to tell me what I'm missing please.
Yesterday I was on stock .30 and rooted. This morning I took the JB update. My first boot was OK and I still had root, but when I rebooted, I got stuck in a loop. It kept rebooting after getting to the desktop. I assumed at least one of my apps was causing it, so I used the wipe data function with the power + vol down thing. that wiped everything, including root.
I tried to re-do the debugfs method, but that seems to fail. Strange thing is, if I use adb shell from the computer, I can su - root and get root access. That's how I was able to give read/write access to the data folder where debugfs does its' work. It's just that root check says I'm not rooted. Voodoo OTA has all boxes checked on my root check, except the one that says granted root permissions. The SU file does exist inside /system/xbin
So it's as if the tablet's user just doesn't have permission to do root. I loaded a terminal emulator on the tablet, and tried to su - root that way, and got permission denied. I would normally get the "superuser" popup when doing something like that -
So there's definitely a piece I'm missing. Can someone point me in the right direction please?
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Sorry, should have mentioned that I tried that. Attaching a screenshot as to what it looks like. Notice the center checkmark stating "root permission granted" is not checked, and there's no option to restore, only to remove or temp unroot, so it's like, everything is good, except for the actual root permission
Root checker shows red (no access) and root programs like root explorer do not prompt for superuser permission before running as I would expect them to the first time.
Did you run superuser? Did you reboot after running su for the first time?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Absolutely, more times than I can count. Here's another shot showing I can't execute such but it seems to have global execute...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
pakure said:
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, uninstalled superuser, and installed superSU as you suggested and rebooted the tablet for good measure.
Ran it, and it prompted me, saying su needed updating, said yes do it, came back to me "installation failed", which I honestly expected because for whatever reason, current tablet user cannot get to su, even though it appears permissions said it should.
One other note, earlier I tried to refollow these directions: http://forum.xda-developers.com/showthread.php?t=1704209
That is how I rooted when under build .30, no issues at all. This time I hit a snag when trying to push files to /data/local - said I had no permission. now I got around it via ADB by simply typing su - root....root seems to work when I'm in ADB, but it doesn't work via tablet interface. I don't know what I'm missing here....
Just a thought.. I was considering flashing back to .30 using fastboot but I wasn't sure if that would even work. I tried loading the .30 zip into the root of storage and it detected it, as a downgrade even and asked to proceed. When done I was still on 4.1.1 not the older build.
BTW, thank you for taking the time. I really don't mean to be a pain here. I've not had this much trouble before...
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I was able to restore my root. See this post.
http://forum.xda-developers.com/showthread.php?p=30481502#post30481502
I've really messed up now. Set perms wrong for the such that was on the tablet so now can't get root using adb either so unless there is a way to downgrade without root I'm screwed.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
thesuzukimethod said:
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
Click to expand...
Click to collapse
Yes it's the /data folder where the exploit was and is causing the issue. I saw one of the commands was flash all, but I was too scared to try that. I tried the update.zip approach, but it came back with needed files weren't present in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
calisro said:
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
Click to expand...
Click to collapse
Oops. This is the whole link. Sorry about that. directions are in there.
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
If you have a check mark unchecked, you likely have root issues. Which check box?
calisro said:
If you have a check mark unchecked, you likely have root issues. Which check box?
Click to expand...
Click to collapse
Sorry - imprecise language on my part.
When I opened up OTA rootkeeper, it showed the same unchecked box (in rootkeeper) as others have mentioned, but I had "restore root" as an option. I did, and had no problems keeping root after updating to JB 4.1.1. OTA. I was using superuser but had checked "OTA survival" in Superuser's options, so I think that's how i kept root (seems like this "survival" option is baked in to Super Su, but a (non-default) option in Superuser).

New TF700T - rooting doesn't work

Just got a new TF700T (today), performed the OTA firmware update.
Tried the rooting procedure but it doesn't work - the procedure finishes off nicely, installs superuser.apk on the end as well but the device is not rooted.
No errors during the installation procedure, this is not my first tablet/phone I'm rooting. Simply, doesn't work - superuser is denying the root request from programs.
Is this b/c of the OTA update or?
Install SuperSU from Playstore
Did you reboot after?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
And when you do get it rooted, download Voodoo OTA Rootkeeper. It will, hopefully, let us keep root after the nearing JB release...
I had the same issue when I rooted. I started SuperSU itself, granted it root, and then rebooted. Worked fine after that.
Sent from my Galaxy Nexus using xda premium
VivianC said:
I had the same issue when I rooted. I started SuperSU itself, granted it root, and then rebooted. Worked fine after that.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
X2

Superuser

Hi, I got the device with root. But every thing which need su permission, su directly denies them, even it self while updating ! I changed option in su to auto accept root permissions. It didnt worked. I tried re rooting according to guide in thedroiddemos and after it batchfile said my device is succesfully rooted. Aaaand it was same result su denies everything. Help please cant do without root
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
muhsino said:
Hi, I got the device with root. But every thing which need su permission, su directly denies them, even it self while updating ! I changed option in su to auto accept root permissions. It didnt worked. I tried re rooting according to guide in thedroiddemos and after it batchfile said my device is succesfully rooted. Aaaand it was same result su denies everything. Help please cant do without root
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
What worked for me was installing SuperSU (updated binaries), installing Superuser Update Fixer (forcing fix if need be) and installing BusyBox and running it. I don't know which of these was the most essential to do, but it made the difference.
I was trying to fix it about 2 hours after 5min I post this thread I got it working lol. Sorry for spam ignore please
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

[Q] How to reset update check to re get update notification after failure

so ya.. topic says it pretty much..
bunch of us i see on the other threads are rooted had a failure and would like to attempt again, but nobody saved the ww update patch so we need to re download it..
dmclient and cmclient have been force stopped and wiped clean
/data/ files associated with updating have been removed..
rebooted and nope no new update available..
what are we missing here?
I am afraid we may have to try a factory reset although I am holding out for a better alternative.
EDIT: Do not factory reset if you are rooted! On JB factory reset will delete root.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
How to restart failed 4.2.1 OTA(root required)
OTA file is here: http://www.mediafire.com/?3f13caikjfxoxpv
Copy dlpkgfile_4.2.1_Init to /cache, renaming it to dlpkgfile. Make a file in /cache/recovery named "command" with this in it:
Code:
--update_package=/cache/dlpkgfile
Boot into recovery by holding volume down and power button....then when you see text....hit the volume up button....and the update will go.
If the update fails, look at the logs in /cache/recovery to see what caused the failure.
bads3ctor said:
OTA file is here: http://www.mediafire.com/?3f13caikjfxoxpv
Copy dlpkgfile_4.2.1_Init to /cache, renaming it to dlpkgfile. Make a file in /cache/recovery named "command" with this in it:
Code:
--update_package=/cache/dlpkgfile
Boot into recovery by holding volume down and power button....then when you see text....hit the volume up button....and the update will go.
If the update fails, look at the logs in /cache/recovery to see what caused the failure.
Click to expand...
Click to collapse
that looks to be the same URL you posted for the US update or is it different?
Ashcunak said:
that looks to be the same URL you posted for the US update or is it different?
Click to expand...
Click to collapse
I didn't post it but it worked on my US TF300T. I had a failed update because I had deleted CMClient.apk and CMClient.odex and after fixing this problem, the above method got me to 4.2.1.
bads3ctor said:
I didn't post it but it worked on my US TF300T. I had a failed update because I had deleted CMClient.apk and CMClient.odex and after fixing this problem, the above method got me to 4.2.1.
Click to expand...
Click to collapse
Oh sorry, i shoulda capitalized it up in the first post of the thread or something.. were looking for WW not US :\
bads3ctor said:
I didn't post it but it worked on my US TF300T. I had a failed update because I had deleted CMClient.apk and CMClient.odex and after fixing this problem, the above method got me to 4.2.1.
Click to expand...
Click to collapse
Thank you for trying to help.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
As far as I can tell the new 4.2.1 ota update has not been released for WW yet only US.
Should hopefully be out by end of the month but have no confirmation on that.
pjc21 said:
As far as I can tell the new 4.2.1 ota update has not been released for WW yet only US.
Should hopefully be out by end of the month but have no confirmation on that.
Click to expand...
Click to collapse
It has been rolling out for the last two days, check this thread: http://forum.xda-developers.com/showthread.php?t=2181235
We got the OTA for WW, but it failed and therefore are trying to get the OTA to reset.
So far there have been alot of issues trying to root after the 4.2.1 ota which I'm on now. Was thinking of rooting as I've done all my other devices in the passed and just recently got this one but as of now there's an issues with the new bootloader encrypting the file system so recoveries can't mount the system. I was about to root before read that and unlocked my bootloader but i guess my question is is there any way to reflash the stock bootloader to lock it again as i also read that you can lose future otas after unlocking it. Any help appreciated thanks.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
The answer is still no. There is no going back once unlocked.
Sent from my SCH-I510 using xda app-developers app
Reilly1812 said:
The answer is still no. There is no going back once unlocked.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Yea you can ignore the post was just hoping for a fix for the unlocked bootloader if were to effect future ota. Ill just monitor the threads for possible fix in future thanks anyway. Delete posts if need be.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
The topic of this thread is related to those on WW firmware with locked bootloaders that had a failed update, and are seeking a method to get the ota notification again.
Sent from my SGH-I747M using XDA Premium HD app
Still cannot reset ota check. Also, do not try a factory reset to get the ota if you are rooted, you will lose root. This sucks!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
David Dee said:
Still cannot reset ota check. Also, do not try a factory reset to get the ota if you are rooted, you will lose root. This sucks!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
ya its odd this time, i swore before we were able to reset this to try again...
Ashcunak said:
ya its odd this time, i swore before we were able to reset this to try again...
Click to expand...
Click to collapse
I had problems with the JB update back in August, but I was able to reset constantly by the CM / DM cache delete. This time something is definitely different. We need to the find the ota file. Alternative is to unlock.
no luck yet anyone?
Nothing on my end.
Sent from my SGH-I747M using XDA Premium HD app

Categories

Resources