I did the Nvflash where it installed CWM at the same time. When I try and update to the 3588 update, it just shows the android guy with a triangle and exclamation point and it wont update. How can I update the tablet to the 3588 firmware?
bumppppppppp
I usually wait until after the ota update to install cwm. Not sure if that's your problem however. Roebeet has a post somewhere on how to nvflash straight to 3588.
As far as I know, clockworkmod and over-the-air updates have always been incompatible.
As suggested above, you could nvflash and do the OTA update before installing cwm. Alternatively, you could simply download and flash the 3588 update manually.
Related
Dear friends,
I just rooted and installed the cw recovery in my newly bought ASUS TF. The current version is 8.4.4.11, 3.1. Then how can I update my machine to V8.6.5.9, 3.2 without wipe?
Thank you very much!
Depending on which rooting method you used, if you read the root thread, it will advise you to update to the latest firmware for your model before rooting. You won't be able to update to the latest firmware after rooting and installing cwm recovery because the update will fail. You will need to return back to full unrooted stock with no cwm recovery, then update to the latest firmware, then reroot. PM me for instructions on how to return to stock.
smslike123 said:
Dear friends,
I just rooted and installed the cw recovery in my newly bought ASUS TF. The current version is 8.4.4.11, 3.1. Then how can I update my machine to V8.6.5.9, 3.2 without wipe?
Thank you very much!
Click to expand...
Click to collapse
cavsoldier19d said:
Depending on which rooting method you used, if you read the root thread, it will advise you to update to the latest firmware for your model before rooting. You won't be able to update to the latest firmware after rooting and installing cwm recovery because the update will fail. You will need to return back to full unrooted stock with no cwm recovery, then update to the latest firmware, then reroot. PM me for instructions on how to return to stock.
Click to expand...
Click to collapse
I have seen this a few times, you do not have to return to stock to update your firmware. A couple of nice people have made the update compatible with CWM and you just have to put the zip on your SD card and install it from CWM. Here's the links to go to .9 and .13 Cheers.
http://forum.xda-developers.com/showthread.php?t=1234734
http://forum.xda-developers.com/showthread.php?t=1281161
After looking at what firmware you are at, I'm not sure if there are zip updates that go back that far, but you can certainly search to see...Cheers.
ckuke4 said:
I have seen this a few times, you do not have to return to stock to update your firmware. A couple of nice people have made the update compatible with CWM and you just have to put the zip on your SD card and install it from CWM. Here's the links to go to .9 and .13 Cheers.
http://forum.xda-developers.com/showthread.php?t=1234734
http://forum.xda-developers.com/showthread.php?t=1281161
After looking at what firmware you are at, I'm not sure if there are zip updates that go back that far, but you can certainly search to see...Cheers.
Click to expand...
Click to collapse
But mine is 8.4.4.11, 3.1 rather than 8.6.5.9, 3.2....
Install a new custom rom
I have a rooted stock Sensation. I have heard that to update to the latest firmware, I need to flash the stock recovery P58img file (or whatever it is called) and then revert back to the clockwork mod recovery. As we all know, trying to apply the firmware update with the clockwork mod recovery prevents the update from even attempting to install.
I downloaded the stock p58 file someone kindly provided me and tried the update, but it always freezes 1/3 of the way through the update and I have to pull the battery to restore it to normal.
Does anybody have an idea why this is happening? I read most of the update thread, but I didn't see the solution unless I missed it.
Listerine said:
I have a rooted stock Sensation. I have heard that to update to the latest firmware, I need to flash the stock recovery P58img file (or whatever it is called) and then revert back to the clockwork mod recovery. As we all know, trying to apply the firmware update with the clockwork mod recovery prevents the update from even attempting to install.
I downloaded the stock p58 file someone kindly provided me and tried the update, but it always freezes 1/3 of the way through the update and I have to pull the battery to restore it to normal.
Does anybody have an idea why this is happening? I read most of the update thread, but I didn't see the solution unless I missed it.
Click to expand...
Click to collapse
You haven't provided any real details.
PG58IMG.zip can be used to update a multitude of things on the phone, Recovery, Radio, Firmware.
Can I ask why you want to update the Firmware and what you expect to get out of the update ?
There is a thread on a cut down update (no HBOOT Update) from the latest RUU, is that what you're referring to ? http://forum.xda-developers.com/showthread.php?t=1385439
I have also read that installing the latest RUU (with the firmware update) changes the HBOOT which can affect how it's then used.
You need to ask for more in details
gol_n_dal said:
You haven't provided any real details.
PG58IMG.zip can be used to update a multitude of things on the phone, Recovery, Radio, Firmware.
Can I ask why you want to update the Firmware and what you expect to get out of the update ?
There is a thread on a cut down update (no HBOOT Update) from the latest RUU, is that what you're referring to ? http://forum.xda-developers.com/showthread.php?t=1385439
I have also read that installing the latest RUU (with the firmware update) changes the HBOOT which can affect how it's then used.
Click to expand...
Click to collapse
Sorry. so the pg58img I used was a stock recovery file. I had heard using that would allow me to install the update, but after flashing it during the installation of the update it failed.
I wanted to install the firmware because I had read that it improved system performance and reduced bugs.
I saw the update that you were referring to, but the thread mentioned how after updating there would be no visual changes or any indicators to let me know that the firmware had actually updated, and I didn't like that aspect of it.
here is a probolem
root lost after flashing the ota updates as LI1, LI2 or LI3.
I've tried many ways,but still have no root.
Anyone got an idea?
You managed to flash the LI2 JB OTA update? The LI3 is an ICS OTA update it says on Sammobile, you flashed that as well?
You have to flash CWM recovery with ODIN, but uncheck auto reboot. When Odin is done you reboot staight to recovery with out first booting the device, or else you will loose CWM. And there you can flash SU zip and you have root.
If you want CWM to stick you should before reboot mount system and connect to computer, start adb and run adb shell, su, rm /system/etc/install-recovery.sh and reboot. And your done
well thanks
i'll try it later.
LI2 is an ICS OTA update. I flashed it coming from LH2 with Mobile Odin Pro and that flashed SuperSU.apk while flashing LI2.
So I assume that flashing the normale SuperSU.zip will work, too.
Btw. I did never loose CWM when leaving it.
akxak said:
LI2 is an ICS OTA update. I flashed it coming from LH2 with Mobile Odin Pro and that flashed SuperSU.apk while flashing LI2.
So I assume that flashing the normale SuperSU.zip will work, too.
Btw. I did never loose CWM when leaving it.
Click to expand...
Click to collapse
maybe theres an LI2 for ICS also but the one posted today is JB for Philipines.
Firmware Pda name N8000XXBLI2 jellyBean OTA update.
Hello all. I seem to have hit a snag while trying to achieve rooted JB. I used Matt's Utility to flash back to 4.0.4 and rooted the device before installing SafeStrap and Voodoo. After all this though, I am unable to upgrade my phone via the Verizon OTA updates as it fails on reboot and takes me to the recovery screen with the red triangle. I can't do a manual update either of the update as SafeStrap gives me an error whenever I try to flash the file (Status 4: e-signature verification failed). Even roms that I have successfully used in the past are now producing this error when attempting to flash.
Does anyone know what this is a symptom of?
Do you have any other recovery besides the stock recovery installed?
You cannot do the OTA update with a non-stock recovery.
Phone but be completely stock (except Root) to do OTA.
rockstarr001 said:
Hello all. I seem to have hit a snag while trying to achieve rooted JB. I used Matt's Utility to flash back to 4.0.4 and rooted the device before installing SafeStrap and Voodoo. After all this though, I am unable to upgrade my phone via the Verizon OTA updates as it fails on reboot and takes me to the recovery screen with the red triangle. I can't do a manual update either of the update as SafeStrap gives me an error whenever I try to flash the file (Status 4: e-signature verification failed). Even roms that I have successfully used in the past are now producing this error when attempting to flash.
Does anyone know what this is a symptom of?
Click to expand...
Click to collapse
Get rid of safestrap, and reinstall it AFTER the JB upgrade. Safestrap always causes problems with OTA updates.
Resolved. Thanks for the answers, you were absolutely right. Reran steps 1 through 3 on the utility, installed all OTA updates after protecting root in order to achieve rooted JB. Installed safest rap afterwards. I wish this was clearer in the utility or on the instructions online. Enjoying batakang right now, cheers!
Sent from my DROID RAZR HD using xda app-developers app
Hi xda,
Can anybody help me in updating my shield to the latest update 72? I have a rooted NVIDIA Shield on (I believe) update 68, Android 4.3 Jelly Bean. I have clockworkmod recovery installed as the bootloader. Upon downloading the update and hitting restart, it brings up CWM and asks if I want to flash the update zip it downloaded, click yes, says root may have been lost - fix? click yes/no, doesn't matter I've tried both and then it boots right back up and says the system update is still available. SO it's obviously not installing correctly.
Can anybody help me out? Is it possible to install the OTA update with CWM, or do I have to restore the default android bootloader? And if so, do I also have to unroot? Factory reset? What would be the easiest way of updating?
Thanks in advance, I'm loving my Shield!
You will need to revert to the stock recovery before you perform the update, as CWM cannot do it for some reason.
If you are not using CWM features outside of rooting, you might prefer this rooting method which does not require installing it so you can just do OTA upgrades without worrying:
https://github.com/linux-shield/shield-root
Failed OTA with a twist...
I also tried the OTA with a rooted/CWM Shield and failed. However, I found this thread and reverted to stock recovery as instructed. But now, it says there are no updates available, and still reports I'm running 4.3. So how do I get it to update?
rpalmer919 said:
I also tried the OTA with a rooted/CWM Shield and failed. However, I found this thread and reverted to stock recovery as instructed. But now, it says there are no updates available, and still reports I'm running 4.3. So how do I get it to update?
Click to expand...
Click to collapse
I actually had the same problem as you after reverting back to stock recovery. The only solution I could find was to 1) Backup everything on my Shield and 2) Factory reset. After factory resetting, the OTA update was detected, and installed flawlessly. I'm now on 4.4 Kit Kat, stock recovery, and am in the process of restoring all my apps and then re-rooting.
525 45863523
Gnurou said:
You will need to revert to the stock recovery before you perform the update, as CWM cannot do it for some reason.
If you are not using CWM features outside of rooting, you might prefer this rooting method which does not require installing it so you can just do OTA upgrades without worrying:
Click to expand...
Click to collapse
Just an update:
After going back to stock recovery, factory resetting for the OTA update to detect, installing it, restoring all my apps, and re-rooting using the method above, everything is running great. Future OTA updates with ease as well as being able to have root access!