Ok I know I'm late in the day;
I bought my Asus transformer very early on and rooted it via the App Backup exploit. I've never unlocked my tablet. I've done a couple of OTA and am now on build 9.4.3.30. When JB came out I didn't update because of problems to start off with and losing Flash. Things have obviously changed now and I'm contemplating the idea of updating to the latest JB version from ASUS via OTA. When I look at the forums there's a lot of posts about problems with people flashing custom ROM's, but I can't find much on how people are getting on with the old rootkeeper method. How are you guys getting on with this method? Is JB worth updating to? Or should I stick to ICS?
My biggest problem with ICS is I'll get random crashes with the Launcher and the desktop shows only the wallpaper, and Google Maps constantly crashes.
Thank you!!!
psjw12 said:
Ok I know I'm late in the day;
I bought my Asus transformer very early on and rooted it via the App Backup exploit. I've never unlocked my tablet. I've done a couple of OTA and am now on build 9.4.3.30. When JB came out I didn't update because of problems to start off with and losing Flash. Things have obviously changed now and I'm contemplating the idea of updating to the latest JB version from ASUS via OTA. When I look at the forums there's a lot of posts about problems with people flashing custom ROM's, but I can't find much on how people are getting on with the old rootkeeper method. How are you guys getting on with this method? Is JB worth updating to? Or should I stick to ICS?
My biggest problem with ICS is I'll get random crashes with the Launcher and the desktop shows only the wallpaper, and Google Maps constantly crashes.
Thank you!!!
Click to expand...
Click to collapse
Do you plan on installing a custom ROM? If so, I would suggest unlocking while on ICS and get your NVFlash files created. I just updated last week from ICS and I would say it's worth it. I have no idea about rooting JB with a stock bootloader or if it's even possible. When the first OTA for JB dropped, it was hit or miss keeping root if you had VooDoo OTA root keeper and used supersu.
Good luck with your choice.
As for your launcher crashes, have you tried an alternate launcher such as apex launcher?
Organized_Chaos said:
As for your launcher crashes, have you tried an alternate launcher such as apex launcher?
Click to expand...
Click to collapse
I've not tried any other launcher. I think there's problem coming from the graphics because after some time of the tablet being on (about 24-48 hours), all 3D applications will crash and the home screen will not draw correctly.
Dredz said:
Do you plan on installing a custom ROM? If so, I would suggest unlocking while on ICS and get your NVFlash files created. I just updated last week from ICS and I would say it's worth it. I have no idea about rooting JB with a stock bootloader or if it's even possible. When the first OTA for JB dropped, it was hit or miss keeping root if you had VooDoo OTA root keeper and used supersu.
Good luck with your choice.
Click to expand...
Click to collapse
I'm planning on sticking to the stock room on JB. So plan is I won't unlock it. I think warranty runs out in May so I'm waiting till then to unlock.
Related
I am rooted using the Universal Xoom Root method. I am still running stock, only with SU and apps which require SU. Why can I not accept an OTA update? It seems like the worse that could happen is it overwrite the SU.apk and I need to re-root.
Thanks in advance.
I was wondering about this as well. I am rooted and am running Rogue kernel. I guess I'll just update and see what happens. Worse comes to worse, I will have to re-root.
Seems like the Xoom forums are quiet...did a lot of people abandon the device for the Galaxy Tab 10.1...When previous OTAs happened, the forums were chock full of chatter about to or not to accept the update.
Yeah, I just tried an OTA update and it wouldn't work. Got the Droid with exclamation point. Up + power put me back where I was.
Sent from my Xoom using XDA App
same here. No dice on the update, just stuck at the install screen. On a positive note, the update notifications are gone. Damn those were annoying.
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
place your unrooted backup on, take update and reroot.
if you don't have one, their are some around.
I keep a backup that isn't rooted with all my apps installed, then when update comes, it is real quick to restore, update and reroot ....
jerrycycle said:
If you root, even without any additional custom ROM/kernel mods, you may receive notification of an OTA update but you should not accept it and try to install it. It will probably put you into a bootloop or worse.
If you wish to root, don't worry. Our wonderful developers are hard at work right now, configuring an update for the device...we'll more then likely get it before the official release comes out OTA.
Anyway, you can always revert back to stock if you really want the OTA update, but stock is boring.
Click to expand...
Click to collapse
Yeah, diddo here with it not bothering me about OTA updates anymore after trying. It didn't put me in a boot loop, just the pretty droid screaming (exclamation point)
I have a backup from before I rooted, but what the heck, it didn't hurt anything, and I was just playing around.
Thanks for everyone's input.
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
flippingout said:
Spoke too soon. The update is back to nagging me again. Errrrrrrr
Why can't they just push out ICS for the Xoom. Hell, they showed ICS on the Verizon Xoom at LeWeb this week.
Click to expand...
Click to collapse
Yeah, diddo. Mine started again about three days after I tried to install. I too am looking forward to ICS.
Sent from my Xoom using XDA App
Hi All,
I've got a blue TF300 + dock that I was very happy with (almost) when I was on ICS, with plain stock ROM and root, and browser2ram and ezoverclock.
I stupidly did the OTA update to JB, not realising that ezoverlcock and browser2ram would not work anymore.
I preserved root using OTA rootkeeper, did a wipe from recovery menu, then booted back up, installed my apps using TB and restored root.
I have been trying to persevere with the tablet for a couple of weeks now since the update, but I just cant put up with the laggyness anymore. I am sick of not being able to smoothly browse a website that has rich content, like youtube, without the browser freezing up (yes, I have tried pretty much every browser there is).
What I am wondering (since I dont really want to have to loose the warranty - the device should be usable as it is out of the box) is that if I download and flash the WW update from the Asus site, will it wipe all my system permissions too, and would it possibly make my tablet any less buggy? (Feels like maybe I got a dodgy OTA update, some people are saying it works great on theirs).
I understand that if I flash this update I will loose root.
So my last question is, that if I do that will it loose root, and if so is there any way of getting root on JB yet without unlocking the bootloader?
Cheers in advance guys.
PS. I will unlock and custom ROM if it really is necessary, I am comforable enough doing it, I have unlocked pretty much every smartphone I had, but the tablet does not come with a carrier warranty unfortunately
Can't really answer your main question, but browser2ram still works on JB. Ezoverclock doesn't work because of the new kernel, b2r doesn't tweak the kernel.
jgaf said:
Can't really answer your main question, but browser2ram still works on JB. Ezoverclock doesn't work because of the new kernel, b2r doesn't tweak the kernel.
Click to expand...
Click to collapse
Thanks for that Is there a new version or the old one still works?
I'm using the same I used on ICS.
mcall_r said:
Hi All,
I've got a blue TF300 + dock that I was very happy with (almost) when I was on ICS, with plain stock ROM and root, and browser2ram and ezoverclock.
I stupidly did the OTA update to JB, not realising that ezoverlcock and browser2ram would not work anymore.
I preserved root using OTA rootkeeper, did a wipe from recovery menu, then booted back up, installed my apps using TB and restored root.
I have been trying to persevere with the tablet for a couple of weeks now since the update, but I just cant put up with the laggyness anymore. I am sick of not being able to smoothly browse a website that has rich content, like youtube, without the browser freezing up (yes, I have tried pretty much every browser there is).
What I am wondering (since I dont really want to have to loose the warranty - the device should be usable as it is out of the box) is that if I download and flash the WW update from the Asus site, will it wipe all my system permissions too, and would it possibly make my tablet any less buggy? (Feels like maybe I got a dodgy OTA update, some people are saying it works great on theirs).
I understand that if I flash this update I will loose root.
So my last question is, that if I do that will it loose root, and if so is there any way of getting root on JB yet without unlocking the bootloader?
Cheers in advance guys.
PS. I will unlock and custom ROM if it really is necessary, I am comforable enough doing it, I have unlocked pretty much every smartphone I had, but the tablet does not come with a carrier warranty unfortunately
Click to expand...
Click to collapse
I have same laggyness.
Hi all, Soon to be joining the ranks of happy tf300t owners but I have a couple of questions.
I bought my tf second hand and only afterwards I noticed that It comes rooted and unlocked.
Will this affect my ability to get OTA updates? And will I be okay to use factory restore when I get it to be sure its securely wiped (I softbricked my hannspad once by performing a factory reset after applying a honeycomb ROM, still don't understand why but just want to be sure theres no chance of that happening here.)
If it does affect me is there an easy way I can set the device to a way that I can get OTA? And do factory resets if thats even an issue (I do have some limited flashing experience with my Hannspad).
And lastly are there any must have apps? (Willing to pay) Or even just tweaks etc to make my transforming experience more pleasant?
Running JB 4.1.1
Well if it already unlocked then doing a factory reset will be fine and will not brick anything. But before you do that i would boot into recovery and make sure its twrp 2.2.2.0 and not another twrp version or clockworks.
No you can't get OTA updates since its unlocked but that is not a big deal, just wait for a Dev to add it to there ROM or just get the stock firmware from asus site and flash it yourself.
flashing the updates your self is only slighty more work the the ota ones mate but as its already roote thats makes up for it and the first few apps that come to mind are adaway, titanium back up, bsplayer (for movies) and dolphin browser (with the jet pack add on)
Just so you know, if you are running jb, do not attempt to flash anything ICS, either ROM or recovery. Make sure what you're flashing is designed for jb, otherwise you might brick your tablet.
You can't get ota when unlocked, but Asus is good for posting their Roms on their website shortly after an ota update is released. There are several guides here which tell you different ways you can install them. Its not hard at all.
Finally, if unlocked, you cannot relock.
Hope this helps a little.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I've gone through the root process on a dozen phones and tablets, but this is the first time I've gone through the process on a new device (to me) so long after its release, and therefore I'm finding the information I need to be a little... hard to pin down. I'm really just trying to be extra cautious with this one since I need it next week.
What I have: Android 4.0.3 ICS, ASUS Build v9.4.3.26
What I want: Android 4.1.? JB, ASUS Build v10.4.2.?? w/ Root/Recovery/Etc
With the above outdated firmware, I'm not sure if I should upgrade to Jellybean using ASUS OTA updates and then root/flash, or if I should use an older root method and upgrade to Jellybean by flashing a custom ROM, etc, etc, etc, etc, etc.
Edit: I should note that I was planning to follow this thread, but it was written under the assumption your tablet is already rooted with a custom recovery.
brennen.exe said:
I've gone through the root process on a dozen phones and tablets, but this is the first time I've gone through the process on a new device (to me) so long after its release, and therefore I'm finding the information I need to be a little... hard to pin down. I'm really just trying to be extra cautious with this one since I need it next week.
What I have: Android 4.0.3 ICS, ASUS Build v9.4.3.26
What I want: Android 4.1.? JB, ASUS Build v10.4.2.?? w/ Root/Recovery/Etc
With the above outdated firmware, I'm not sure if I should upgrade to Jellybean using ASUS OTA updates and then root/flash, or if I should use an older root method and upgrade to Jellybean by flashing a custom ROM, etc, etc, etc, etc, etc.
Edit: I should note that I was planning to follow this thread, but it was written under the assumption your tablet is already rooted with a custom recovery.
Click to expand...
Click to collapse
This is how I did it this afternoon on my new TF300T:
Rooted ICS with this: http://forum.xda-developers.com/showthread.php?t=1704209
Installed supersu: https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Updated su binary using supersu
Installed OTA rootkeeper: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Backed up su with OTA rootkeeper
Installed ES File Explorer(you really don't have to do this but I wanted to make sure some other app had root access before I upgraded to JB)
Made sure supersu authorized all these root apps by running them at least once.
Upgraded to Jelly Bean
Restored root access with OTA rootkeeper
Wiped the sweat from my brow afterwards!
I am staying with stock JB locked to keep getting OTA updates. If you want a custom rom, you need to unlock:
http://forum.xda-developers.com/showthread.php?t=2055886&highlight=unlock
Unlock APK is here: http://forum.xda-developers.com/showthread.php?t=1949758
NOTE: If you upgrade to Jelly Bean without OTA rootkeeper in place, you will not be able to root it without unlocking it first. There is no root exploit yet for the TF300 Locked Jelly Bean.
Yep. This will do the trick.
Still Charged Up
bads3ctor said:
This is how I did it this afternoon on my new TF300T.
Click to expand...
Click to collapse
Thanks badsector, I'll give it a go today and report back how it went.
Alright, thanks for the help in getting started, but I forgot to mention I had unlocked the tablet beforehand as a first step to another guide, so OTA updates were a no-go for me with this approach. What I ended up doing was, after performing 1-7 from your list, install TWRP using fastboot, manually install the JB update from ASUS, install TWRP for JB (again w/ fastboot), and then load a custom ROM. I'm all up to date and running fine, and had I intended to stay on the stock ROM I could have just left it at that when I flashed the ASUS firmware.
Thanks again!
I unfroze all the apps I had frozen and tried the OTA and it still failed.
I am rooted with just the stock ROM.
Anything I am missing here?
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
No OTA updates will work on a rooted phone. If it somehow does work it will likely break your root privileges
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Plunkyxda said:
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
Click to expand...
Click to collapse
You can do a OTA with root but you will just lose it. If you altered some system files it will fail or if you run a custom recovery it will fail.
I've had similar issues, on other devices, with ota updates not working because of root, and more specifically I believe, cwm recovery. Unfortunately I've had to use kies to update.
Sent from my SCH-I535 using xda premium
kendive said:
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Click to expand...
Click to collapse
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Yea I agree... I did not really need the OTA and I plan on installing CleanROM 5.6 tmr.
I just froze all that bloat back. I can't stand all that S***T running in the back ground.
Plunkyxda said:
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Click to expand...
Click to collapse