Database Info

Stock but rooted - Avoiding OTA Push?

As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?

recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
well, renaming files at least works for boot animations & such, so i don't see why it wouldn't work for that ota file. normally, if it's something i don't want/need, i'll either freeze it or remove it entirely. try 'Anttek App Manager'(it's free).
additionally, i wouldn't wait around on an "official" CM7 for the Thunderbolt as that may never happen. i find at least that the latest 'SHIFTAO5P" roms that dhacker is now working on are the most stable ones and seem to have everything working ok.

recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
Has anyone actually tried the method I mentioned
Did it work

Now that an ota IS being pushed I guess i'll find out the hard way unless someone can help me out?

I got a OTA request right before I updated from Stock Rooted Gingerbread to the current stock rooted.
Now I'm on the current version same as OTA but rooted, renamed otacert.zip.bak but still had in the software update "deferred update pending".
Not sure how to stop this. Any help appreciated.

Can't u accept the OTA n just reinstall Superuser as long as ur S-Off? Been awhile so I can't remember.
Sent from my ADR6400L using xda premium

I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.

Tantalin said:
I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.
Click to expand...
Click to collapse
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button

Could you just restore a nandroid?
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.

recDNA said:
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.
Click to expand...
Click to collapse
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button

You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.

recDNA said:
You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.
Click to expand...
Click to collapse
I was answering your file question while telling him why his OTA didn't work cause of the hboot problem
If I helped you in any way please use the thank you button

Grnlantern79 said:
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I'm in the same pickle as tantalin. Let me ask some dumb questions:
- I can get to the CWM recovery screen. Are you saying I could do a factory re-set, then restore the ROM pre-update? Would I have to have backed up before the OTA (which I didn't, as I only rooted yesterday...argh).
Thanks for your help.

Keep in mind Im a beginner too so you may want to wait for someone with more experience.
CHECK WITH AN EXPERIENCED USER BEFORE FOLLOWING MY DIRECTIONSDIRECTIONS
Yes, you would have had to have a rom to restore to. You could try wiping data, cache, and dalvik cache but I don't know whether phone would boot.
Another alternative would be to shut off phone, take out flash card, copy a custom rom like bamf forever 1.0.8 or the rooted version of the update on the sdcard. Put sdcard back in phone, turn on phone whole holding volume key down. Go to recovery. Wipe data, wipe cache, wipe dalvik cache (under advanced choices)Choose instal from sdcard. Browse to custom rom you put on sdcard. Choose it and install.
Keep in mind Im a beginner too so you may want to wait for someone with more experience.

TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!

If you have a rooted stock phone, and then you accept an OTA or load an RUU, you WILL lose root and the custom recovery program. But you SHOULD still be S-Off. If you are in that position right now, you need to re-flash the custom recovery to be able reload the SU app to regain root.
If you are actually back in S-on, you need to restart the root process from the beginning.
THEN BACK UP IMMEDIATELY BEFORE YOU DO ANYTHING ELSE....
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
Click to expand...
Click to collapse
Good job.

Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!
Click to expand...
Click to collapse
Excellent! I know that phew feeling all to well!
Now please, PLEASE READ THIS THREAD (You'll be glad you did!)
http://forums.androidcentral.com/showthread.php?p=829066

Grnlantern79 said:
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I was able to get to HBOOT & I followed the steps in the 3rd post of this thread starting at step 5.
I didn't wipe anything (Wipe data, cache, and dalvik), so I don't know what the short term or long term effects are.
I used TiBup & My Backup Pro to restore my SMS/MMS...I don't really want to go any further until I know if I should go back & wipe those things & then do it over...anyone?

I ended up in the exact situation as the op. I went back to stock rooted with perm S-Off and the update got pushed to my phone.
When I noticed the phone trying to update but stuck at the screen you are describing I pulled the battery and went into recovery from hboot. In recovery under mounts there is an option to turn on sd storage or something like that. I've used it before so I knew it would allow me to access the sd card from pc. I then downloaded the rooted rom of the ota. Then I unmounted the phone from pc, rebooted recovery, and went through the normal rom installation.
Sent from my ADR6400L using xda premium

The only issue to me seems if you have something on the phone not backed up you want to keep. Even if the update installs and it updates the bootloader back to s-on, revolutionary root still works so you cam just re-root.
Edit: I recommend you head over to thunderboltforums to at least restore the bootloader to stock s-off if you want to accept the update and re-root.
Sent from my ADR6400L using Tapatalk

[Q] ICS Update Problems

Help! I have downloaded and was in the process of installing the OTA update for ICS on my Transformer TF101. The installation got to the end of the progress bar and a triangle with an "!" appeared. The tablet would not do anything. I rebooted the tablet and now it is just stuck at the Eee Pad screen. when I hold down the power button, it just continuously reboots. I contacted Asus and they say I have to send it back in. I just got it back a few weeks ago from a service repair. Is there anything I can do to get this working again or am I stuck with sending it back to Asus?
Thanks

I am getting the Triangle, but I'm able to restart the unit with a long press on the power button. So, no ICS for me yet, but I'm still able to get back to the old setup. I'm sorry for your loss.

Follow the instructions here: http://forum.xda-developers.com/showpost.php?p=22905630&postcount=3

That worked...thanks! So is there any way to root it again now that I have ICS installed? or do I need to wait?

aamon17 said:
Follow the instructions here: http://forum.xda-developers.com/showpost.php?p=22905630&postcount=3
Click to expand...
Click to collapse
Does this still apply to someone without cwm
Sent from my Transformer TF101 using XDA Premium HD app

Same Issue
I too am having this issue but now I am stuck at work with no WIFI to try this above. But I am running stock ROM, Recovery and no Root. I had root but the last OTA I got removed it. I downloaded it this morning and ran it failed with the Triangle and then re-downloaded it by tethering to my phone at work and it still didn't work. Is it saved on the device anywhere? Or will you have to downloaded it every time? This is pretty frustrating that I waited to ROM or anything due to waiting on ICS and now that it is here I can't get it.
P.S. What the Guy above me asked.

My update issue is due to the SRS_config file that I modified to fix the speaker volume balance. I discovered this after trying the CWM update method.

adude007 said:
My update issue is due to the SRS_config file that I modified to fix the speaker volume balance. I discovered this after trying the CWM update method.
Click to expand...
Click to collapse
I figured this would happen if someone got CWM to work, which I cant even figure out how to properly install CWM to begin with. ntm I left my usb cable at home.

vectorized said:
I figured this would happen if someone got CWM to work, which I cant even figure out how to properly install CWM to begin with. ntm I left my usb cable at home.
Click to expand...
Click to collapse
vectorized:
I had trouble getting CWM to install via the Recovery installer.apk method that is available in the dev section. The trick was to COPY, REPEAT COPY, SU from system/bin to system/xbin and then that program recognized root. I used root explorer. Seriously copy don't move.
You can get that APK one click method here:
http://forum.xda-developers.com/showpost.php?p=22359727&postcount=218
Edit: On review it looks like you probably want the second link. That will install the newer CWM which allows for internal & SD Card ZIP files to be flashed
Then I had to use the full install CWM version of our OTA update:
http://forum.xda-developers.com/showthread.php?t=1514658
Edit: Option B to be clear.
I hope this helps.

I ended up going to the original transformer rom and flashing every firmware update from that. It took a while. now I've got ice cream sandwich. Now I just need root
Sent from my Transformer TF101 using XDA Premium HD app

UCLE2 - Can't get root access

I'm just starting to learn how to do all this...
I have CWM 5.8.4.0 installed, UCLD2 and Superuser 3.0.7
I've lost root access and can't figure out how to get it back. I've been searching the forum but can't quite seem to find what I need. I went through the process for rooting and no good result. I thought maybe I should just do a recovery back to 2.3.6 in CWM and it says the MD5 mismatch. I thought I had a solid backup for my original phone all this time. I restored it once through ROM manager and it worked great. I did a factory reset and went through the rooting process again and still nothing.
What my goal is, is to flash to a ROM that people are liking and that performs well. Was going to try SKYICS 4.2E, but I don't think I should attempt anything until I figure out how to go to a backup consistently. I could back up what I have now, which gives me a working phone, but I don't really like it. Most of my apps don't work correctly on it. What I really don't want to do is go forward again and really have it jacked up and not be able to go to a previous backup.
Where should I start? I'm guessing getting root access again. I'm assuming I won't be able to flash another ROM until I get this.
Thanks for the help!

I was having that problem too, I used this script "su_ics_v3.1_updated_wraithdu_installer" also install and run busybox if you haven't already or just flash an insecure kernel (make sure its right for your rom)

jordan9812 said:
Just go read the faxes then after hours of that restore to stock and read the rooting guide good luck
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Okay funny guy... What was my first line again??? lol
I don't even know how to get back to stock. I can do that even if I don't have root access? I'm just trying to learn the mechanics of all this. Learn what does what... CWM is a means to write to the phone from boot. Can install different ROMs and parts of ROMS, ie. lock screens... Then there's kernels that operate the hardware that have to be compatible with the ROM. People talk about way more than I can comprehend at this point; it's one step at a time for learning.
So---first step is what? Read for hours? I don't understand what I'm reading. haha

32dave said:
I was having that problem too, I used this script "su_ics_v3.1_updated_wraithdu_installer" also install and run busybox if you haven't already or just flash an insecure kernel (make sure its right for your rom)
Click to expand...
Click to collapse
What was the very first line in my post? lol
I'm not a programmer, but have taken some Java classes.
I don't know how to use scripts at all. In my mind, I can't do anything until I get root access. I'm not sure what the MD5 mismatch means either. I'm definitely reading things, but it seems that either I'm not understanding or that it's a tangent and not really related to what I'm trying to do...

You don't need root access. All you need is cwm to flash roms, kernels and radios
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I'm starting to figure that out. This stuff isn't very simple. It seems like it is, but for some reason it's just not. It's like a tractor pull. The more I learn the harder it gets to learn more because the crap gets too deep!

CodeRedDewd said:
I'm starting to figure that out. This stuff isn't very simple. It seems like it is, but for some reason it's just not. It's like a tractor pull. The more I learn the harder it gets to learn more because the crap gets too deep!
Click to expand...
Click to collapse
read the n00b posts and stickies, its really not that hard, all roms r rooted..meaning u dont have to root, u can do root ur self for stock firmware, the hard part(not really hard) is flashing cwm(clockworkmod recovery) via odin, once u do that flash a rom according to the rom u want to use, read this on howto root and flash cwm using odin http://forum.xda-developers.com/showthread.php?t=1340526
to go back to stock is very easy also via odin, read this link on howto http://forum.xda-developers.com/showthread.php?t=1652398
once u find a rom read all about that rom on how to flash it and any trouble shooting
clockworkmod recovery replaces the stock recovery so u can do wonderful things to our phones, it's this application that installs(flashes) the roms

Thanks for the info... I installed another ROM that I liked better, SKYICS without the root. I wanted to tweek something else and I cannot do it unless I get root access. Using Odin is pretty easy like you said and CW recovery. The first link you posted is the one I originally followed and it was rooted. I went through the process again and no root. Titanium just says sorry I don't have permission. I did a factory reset and tried to root again and nothing. I'm not sure where to go from here to get the root back....

If you flash a custom ROM they are already rooted
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I don't have root access. I did have it, but lost it when I installed ICS 4.0.4.
Titanium is saying it can't do anything... I just checked and now it's working. I didn't change anything. That's weird. It asked me for permission and is now in the superuser list. I couldn't get anything to do that for a few days. I'll just have to say Okay and move on. lol

CodeRedDewd said:
I don't have root access. I did have it, but lost it when I installed ICS 4.0.4.
Titanium is saying it can't do anything... I just checked and now it's working. I didn't change anything. That's weird. It asked me for permission and is now in the superuser list. I couldn't get anything to do that for a few days. I'll just have to say Okay and move on. lol
Click to expand...
Click to collapse
thats why i said when u use a rom "once u find a rom read all about that rom on how to flash it and any trouble shooting", its usually a bad flash, if reflashing doesnt work then redownload the rom and again and flash
u could of flashed superuser, but the problem was the rom didnt install properly......good u got it solved

32dave said:
I was having that problem too, I used this script "su_ics_v3.1_updated_wraithdu_installer" also install and run busybox if you haven't already or just flash an insecure kernel (make sure its right for your rom)
Click to expand...
Click to collapse
Can you be more specific on rooting 4.0.4? I didn't like SKY ICS and installed Embryo. It's much faster than the other, but now I don't have root again. I don't know how I got root access to SKY ICS, because when I asked I didn't have root, but 2 days later I suddenly had the access and did nothing.
I'm browsing around trying to find how people root 4.0.4...

CodeRedDewd said:
I'm browsing around trying to find how people root 4.0.4...
Click to expand...
Click to collapse
I used the 1st 3 steps for my ULCE2 [GUIDE]{ROOT}How To Root The ICS Leak

pc103 said:
I used the 1st 3 steps for my ULCE2 [GUIDE]{ROOT}How To Root The ICS Leak
Click to expand...
Click to collapse
That's exactly what I did and it's not working. I'm using CWM touch and tried 2 different superuser files I've found and nothing. BusyBox won't install because it says it doesn't have permission and I can't mount the drive in the phone with a file explorer because it's not rooted.
I read somewhere that I may need to install an "insecure kernel", or maybe a ROM that is already rooted? I can't figure those things out....
I've even started all over and flashed the UCLE2 again, cleared all data. then installed Embryo, CWM then superuser. No luck. I'm at a loss here.
Update: I have tried these superuser files.
Superuser, Superuser-3.0.7-d-signed and Superuser-3.0.7-efghi-signed. The last one gave me root access for 4.0.4. I'll attach the file for others.

CodeRedDewd said:
That's exactly what I did and it's not working. I'm using CWM touch and tried 2 different superuser files I've found and nothing. BusyBox won't install because it says it doesn't have permission and I can't mount the drive in the phone with a file explorer because it's not rooted.
I read somewhere that I may need to install an "insecure kernel", or maybe a ROM that is already rooted? I can't figure those things out....
I've even started all over and flashed the UCLE2 again, cleared all data. then installed Embryo, CWM then superuser. No luck. I'm at a loss here.
Update: I have tried these superuser files.
Superuser, Superuser-3.0.7-d-signed and Superuser-3.0.7-efghi-signed. The last one gave me root access for 4.0.4. I'll attach the file for others.
Click to expand...
Click to collapse
This superuser zip gave root access where other versions did not for 4.0.4.

CodeRedDewd said:
That's exactly what I did and it's not working. ...
I read somewhere that I may need to install an "insecure kernel", or maybe a ROM that is already rooted?....
I've even started all over and ...I'm at a loss here..
Click to expand...
Click to collapse
(See below)
CodeRedDewd said:
This superuser zip gave root access where other versions did not for 4.0.4.
Click to expand...
Click to collapse
...which is why we're focused on the one method with its 3 or 4 steps we linked. [Confession] My bad, I forgot to mention as is often covered in the threads - CWM flashing the zip took me a few (4) retries. I only backed up as far as 'select update from sdcard' for each retry, all within the same recovery session. Maybe this will help?

pc103 said:
(See below)
...which is why we're focused on the one method with its 3 or 4 steps we linked. [Confession] My bad, I forgot to mention as is often covered in the threads - CWM flashing the zip took me a few (4) retries. I only backed up as far as 'select update from sdcard' for each retry, all within the same recovery session. Maybe this will help?
Click to expand...
Click to collapse
It wasn't the steps ther were wrong. It was superuser that was wrong. I tried and tried with 2 different ones and nothing. Then I found another version that worked on the first attempt. The versions I tried first worked on 2.3.5, but not on 4.0.4.
I'm attaching the one I found that worked the first time. I tried the others about 20 times each and nothing, but they worked before. I haven't read anywhere that there are different versions of superuser that only root certain builds. I found it out the hard way.

If i can remember "SOME" superuser zips need to be flashed a few times before they flash successfully.
Sent from my SAMSUNG-SGH-I727 using XDA

jyazzie110 said:
If i can remember "SOME" superuser zips need to be flashed a few times before they flash successfully.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Thanks. I have read that, and that it works sometimes when it says it fails. The problem was that there are a few versions of superuser. I had two that worked on previous versions of android, like 2.3.6, but they won't work on 4.0.4. I found a different one named. "Superuser-3.0.7-efghi-signed" that worked first time. I tried the others more than enough. They don't work on 4.0.4. It's funny no one has mentioned this before.

Let's be clear.
I am glad you reached this goal CodeRed. Enjoy!
CodeRedDewd said:
...It wasn't the steps that were wrong....The problem was that there are a few versions of superuser.
Click to expand...
Click to collapse
Yes, but there was only one version in the [GUIDE]{ROOT}How To Root The ICS Leak.
CodeRedDewd said:
I had two that worked on previous versions of android, like 2.3.6, but they won't work on 4.0.4. I found a different one named. "Superuser-3.0.7-efghi-signed" that worked first time. I tried the others more than enough. They don't work on 4.0.4. It's funny no one has mentioned this before.
Click to expand...
Click to collapse
I had the older zip too, but it was all properly instructed in our [Dev] thread. Copperhed posted 'This will root 2.3.5 or 2.3.6' for an earlier Superuser.zip last November, linked in InSaiyanone's excellent all-in-one guide.
Needing to root 4.0.4 would lead us to the next stickie, where projeqht linked
Starskyrob's 'Step 2: Flash Attached zip from recovery.' in his [GUIDE]{ROOT}How To Root The ICS Leak, posted March 28th, referring to the zip you and I succeeded with. I think anyone reading the stickies should find the same guidance.

(SOLVED)[Q] how to tell if phone is already rooted.....

So I just picked up a skyrocket and I went to update OTA and it downloaded the update and when it went to restart to install the update the phone booted into clockwork. I wasnt able to find a thread for this specific device about it so I am asking here now. MOD if there is one please point me in the right direction. I did notice that there is no att bloatware on the device. Thanks.

Terminal editor, type su, press enter, see what happens.
Other clues: presence of Superuser app.
You have a custom recovery also which will need to be ODINed away.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yes, it does have superuser. As far as Terminal editor/ODINed i'll be honest I have no idea what you are talking about. First sammy device that I have had long enough to keep and want to keep. Use to HTC branded devices. But thank you I think it is rooted because of the superuser app.

Questions should be posted in Q&A. Moved.
Side note: I recommend you read a lot before you mess with it. Although this device seems to be very difficult to hardbrick misusing ODIN can lead to one.
Cheers

Go to market download root checker. Run it. If a super user prompt appears, that's a good sign.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

occupational_hazard said:
Go to market download root checker. Run it. If a super user prompt appears, that's a good sign.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yes it does, superuser prompt comes up. I really would just rather have this back to completly stock running 2.3.6 until the 4.0 update rolls out. Not sure which is better. Rooted or unrooted????? Also am not sure if it has ODIN....I tried to boot into recovery to run ODIN3 and upgrade to 4.0.4 but when trying to power on into bootloader it just vibrates and will not boot until I release the volume up rocker. Other than curiosity the phone works and performs flawlessly. With superuser being installed and after installing titanium I am sure it is rooted. Still not sure what ODIN is (like I said used to the HTC branded phones and never cared about root) Thanks for all the information. Also I am not sure if I will be able to update to 4.0 when the OTA update rolls out, im not concerned about it being rooted or not (have not found a reason to have rooted yet). Anyone know if it can be updated OTA even though it has root?

didozer said:
Yes it does, superuser prompt comes up. I really would just rather have this back to completly stock running 2.3.6 until the 4.0 update rolls out. Not sure which is better. Rooted or unrooted????? Also am not sure if it has ODIN....I tried to boot into recovery to run ODIN3 and upgrade to 4.0.4 but when trying to power on into bootloader it just vibrates and will not boot until I release the volume up rocker. Other than curiosity the phone works and performs flawlessly. With superuser being installed and after installing titanium I am sure it is rooted. Still not sure what ODIN is (like I said used to the HTC branded phones and never cared about root) Thanks for all the information. Also I am not sure if I will be able to update to 4.0 when the OTA update rolls out, im not concerned about it being rooted or not (have not found a reason to have rooted yet). Anyone know if it can be updated OTA even though it has root?
Click to expand...
Click to collapse
Ota will not work with cwm...you need the stock recovery to do an ota......rooted I don't believe matters
Sent from my A500 using Tapatalk

StolenVW said:
Ota will not work with cwm...you need the stock recovery to do an ota......rooted I don't believe matters
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Can I download and install via sd card when the update is available. Only time I have used cwm is on my wifes old eris.

didozer said:
Can I download and install via sd card when the update is available. Only time I have used cwm is on my wifes old eris.
Click to expand...
Click to collapse
You need stock recovery. You need to read the stickies for a few days before you do anything.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Or just keep your phone as is, and wait when ics officially drops, just wait a day and someone will have a flashable zip of it for cwm. Might as well learn the perks of being rooted now and learn your way around the phone
Sent from my SAMSUNG-SGH-I727 using xda premium

Its all set now. Had to figure out the whole Odin thing. Ended up just redoing to software using my computer with a one click method. Can't remember who made it but it was from android central but mad by member on here. So thank you to that mamber Kenny something?? Any was have it flashed to 4.0.4 with no bugs. Everything works perfect and so far battery life is great. I must say that so far I am loving this phone. At first I wasn't sure about going away from my vivid but I can't find any reason to have any regrets. Thanks guys I appriciate your help and input.

can u put solved in ur title

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).