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!
Related
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
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
So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
filmfanatic09 said:
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
Click to expand...
Click to collapse
You cannot be rooted or you must hide root w/ voodoo or super su. Also you must use stock recovery.
the update will not actually fail if you are rooted, although it may report failing.
if it actually fails, you can obviously see it doesnt go through the process, then there is some other factor causing it to fail.
some things that would cause it to fail all together are: non stock recovery, freezing any bloat, removing any bloat, pretty much any modifications to the stock software other than rooting will cause it to fail.
once you have any system deficiencies fixed, use voodoo from the market to protect root and temp unroot before taking the update.
if you cant figure out what you did to the system to fix it, you may want to re-flash using the proper utility for your current system, re-root, protect and temp unroot through voodoo, then try the update again.
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
filmfanatic09 said:
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
Click to expand...
Click to collapse
you can flash the hole system using this http://forum.xda-developers.com/showthread.php?t=2474393 get the 1.33 version to match what you are on or the 1.34 to go right to the version you are trying to upgrade to. either is fine.
I own a Verizon SCH-I535 that had version 4.1.2 and after months of avoiding the Verizon update I stupidly pressed install now instead of later. I did have enough mind to take the battery out before it could reboot but my question is can I still root? And can I still use the 4.1.2 method? I don't want to install any roms just wish to uninstall any bloat apps.
I had a very similar issue some time ago. Check out my thread at http://forum.xda-developers.com/showthread.php?t=2607252
I went in a few circles, soft bricked my phone, but was able to recover. I think the important thing is to verify if your bootloader has been locked or not; boot into odin/recovery mode and checkout the messages posted in my thread. If the bootloader is not locked yet then you have options. If it is locked, you should probably just reboot the phone and let it do it's thing as the locked bootloader cannot be reverted.
Depends on how important this is to you. My wife got the 4.3 update and loves it, but she is not the type to do any customization. I now have a CM 10 d2vzw and am happy. It I were to do this again, I would probably verify you have an unlocked bootloader and re-flash the complete stock 4.1.2 image as I did. Issue is, you will probably lose a lot of data & settings, but things like pictures, etc. should sitll be there. Once the stock 4.1.2 is there you will want to root and disable updates, or else flash a new rom.
The 4.3 update (and anything after it) locks the bootloader. If that's a big deal to you, then you need to push some custom roms. If not, towelroot works on everything so far, so you'd be able to reroot (pretty hassle free) and do what you want.