I have been anxiously waiting for asus to post the jb firmware (us tf300t). I found it today, but now realize if i flash it manually i lose my root, backed up with voodoo and superSU or not. I then was reading about this dlpkgfile thing. Am i understanding this correctly?
It is the file that gets downloaded from asus when you check for an OTA, or when an OTA is pushed to your device
It then reboots, and uses the file to update the device.
It does not make u lose root?
So theoretically, I should be able to put it in /cache/directory and then`reboot my tab and it should start updating right? I know i need to make sure i get US version, backup root, etc. But will this work how I am thinking it will?
Oh and, I am not sure why my ota failed in the first place, i think i might have uninstalled a system app by accident without thinking. I am just plain rooted stock, NOT unlocked. I had also run the firmware for ics from asus website yesterday to get all the stock stuff back on my tab, then rerooted, and am waiting for JB update now
Related
I rooted my asus transformer pad tf300t two months ago. Lately my tablet has been promting me about an available update from Asus. I have my doubt about updating my rooted tablet using an official update, so I did a bit of research. And it seems that normally we are adviced to NEVER update directly from a rooted tablet...
Is that true? Do we need to reflash to get rid of the root first before we update?
Thanks in advance for any advice.
1. Remember to get your /system/apps and /system/lib back to stock state before any OTA update.
2. Make sure apps (especially those that came with the stock, however irrelevant e.g. Netflix) have not been frozen / uninstalled with Titanium Backup or other applications. Sometimes some stock apps (even after factory reset) don't match SHA1 sums. Replace modified apks in /system/app to those that originally come with your stock version of tablet as found in About Tablet.
3. You will need a build.prop that hasn't been modified too! Look around to see if you can find one for your SKU.
4. If you have Chainfire 3D installed, you'll have to uninstall the 3D driver, wipe data and cache for the Chainfire 3D app, and uninstall it before update.
In any case, just go for it.
I did that naively. Update failed miserably (worry not, boots back into your pre-update state!). Looked for a way to put the update file manually into /cache partition, update still failed cause of modified/frozen apks.
Added default apks from some dropbox shared link somewhere on these forums, update still failed due to the Chainfire OpenGL driver issue.
On correcting that problem though, update booted to Jelly Bean!
Oh, and if you wish to keep root after update, remember to change Superuser app to SuperSu, then install OTA Rootkeeper from Google Play, save root. Temporary unroot just to be safe (possibly not essential). Then update!
Hi,
I deleted some apps with Root Uninstaller, and now cannot do OTA update.
Is there a way to download stock apps? Om still on 9.4.3.26 firmware back from April, but it is very buggy - crushes all the time - really need to update it. Please let me know were I can find stock Apps
Thanks
I tried to do some digging, but the firmware just looks a bit dated for any meaningful results to show up. A few build.prop dropbox links have been taken down now that it isn't much used. Even the Asus support site doesn't have a US SKU image of the .26.
I guess your best shot may be to try one of the manual upgrades to .29 and then to V10.4.2.9, or to unlock your bootloader. However, I have not done a manual upgrade yet so I wouldn't know the troubleshooting bit. These instructions seem simple though.
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
I am on stock 4.1.2, VRBMB1. I am rooted, unlocked and with TWRP recovery. I have used Titanium to freeze SDM 1.0.
I am considering going to VRBMF1. I don't know how to safely get there. I also don't know what improvements might come with the OTA to MF1. Should I just hang out with VRBMB1 until the rumored update to 4.3 arrives? I would like to be in the position to return to what I have now (just in case), or be able to move to 4.3 if, and when, it come out. How do I proceed? Thanks
I have the same question... subscribed!
Is there a rooted/unlocked update file, or do I just run the VZ update and use Voodoo rootkeeper to restore root (or Casual unlock again, if needed)? Or dirty-flash one of the rooted/unlocked stock ROMs (and then the firmwares)?
So many ways to get there, just looking for the safest... I figure the VZ update might be best.
So, I finally bit the bullet. I backed up all kinds of things before running, but it seems I didn't need to. I unfroze SDM, and then checked for updates. It downloaded and then rebooted to install. Since CWM was installed, it tried to perform the update, gave a few errors, but I let it go anyway. After the main install was done, CWM asked me if I want to let the updater install a new (stock) recovery - I said no. Then it said that I may have lost root, so do I want CWM to fix it - I said yes. Then I cleared the cache (just in case) and rebooted. The phone booted up, said it completed the upgrade, and then dropped me back into the rooted OS. Pretty cool.
SDM did complain to say that the updated "didn't happen" but the phone shows the new MF1 version, and a few new apps as well. So, obviously, the update happened... and I didn't lose root or recovery. Damn nice...
I wonder if TWRP does the same things (disable the stock recovery and restoring root)...?
EDIT: Reading the TWRP page says that they don't support nor recommend applying a stock ROM update.
Secondly, I found that while my phone was working fine, when I tried to get into recovery, it popped up the unauthorized software error. Meh. I used the Casual rooting tool to reroot, apply the insecure aboot, and then reapply CWM... and I'm back to normal now. Not a big deal, but still more steps than I thought I needed above!
So i eventually received my lollipop OTA this morning (UK, EE).............
But what exactly do i do with it
I'm rooted (Locked BL). I obviously can't install the OTA the normal way, can i ?
I was waiting for some custom ROMS to be made available but don't seem to see any. Will these follow soon since the Lollipop update has went global?
I'm kinda torn tbh.... i have my phone set up perfectly on KitKat and it looks amazing and some of my favourite xposed tweaks aren't available on Lollipop e.g. Blurred System UI.
Anyway...If i should decide to install Lollipop (i probably will) what would be the best method?
(Are we talking going back to stock, installing OTA, then re-rooting, or is there a more simple method?)
I believe u only lose root. Install and re-root is my fiddy cent...
Download your respective firmware and make a pre-rooted rom based on it.
And flash it via recovery.
Stick with KitKat.
Sorry to hijack the thread but if I root without unlocking bootloader, will I get to update normally via ota or companion app? I don't mind losing root access if only to reboot later. And does it affect drm keys etc?
I'm rooted with kitkat and received the prompt for lollipop OTA. The point is it downloads but won't install, so to upgrade you'd need to use flashtool, PC companion or boot into recovery and flash an appropriate zip. None of those should have any effect on your DRM, but you'll lose root unless you're flashing a pre-rooted version of lollipop. If you do opt for a rooted version of lollipop it's still a bit unclear whether recovery is fully available to you, and xposed installer has a rack of issues either way...... you might want to hold for now?
Thanks for that I'll wait it out for now. The only real reason I was really updating was for the move to sd feature. Do anyone know of any alternatives?
The point is, I just wanted root until the ota. So it will update normally via sony PC companion?
OTA Can't Verify on Rooted Device
I noticed the update this morning. Phone rebooted like it was going to work but didn't. Now it allows me to download it over and over and each time it says "could not verify". Is there any good reason to want this update? I'm rooted on the 77fw and my phone works fine as is. I do not want to update and find out I lost root. Unless there is a very good reason to, I'll just wait and see if a rooted zip becomes available.
Stickin with kitkat. I will not run without root.