Greetings, all!
A friend of mine has a VZW GS3, which I rooted for him a few months ago using this method: http://forum.xda-developers.com/showthread.php?t=2046439
Last week he got the 4.1.2 OTA. When he allows it to install, this what he gets:
Install Untrusted Package? THIS CANNOT BE UNDONE.
-No
-Yes - Install untrusted zip
_ +++++Go Back+++++
ClockworkMod Recover v6.0.2.3
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed.
Click to expand...
Click to collapse
I've looked through that thread a bit, but I can't seem to find anyone having the same issue. So my question is can he just install the update this way and be alright? Also, will it need to be rooted again?
Thank you so much for any help!
evergamer said:
So my question is can he just install the update this way and be alright? Also, will it need to be rooted again?
Click to expand...
Click to collapse
After reading about people having problems losing root after the OTA update, I decided to not to take it, and instead flashed a stock rooted 4.1.2 image, per this thread: http://forum.xda-developers.com/showthread.php?t=2178482
Since I had no plans to do any theme mods, I used the Odex version. Scroll down to post #3 and grab the 4.1.2 modem and rpm as well (which are part of the OTA). These can be flashed in the same recovery session as the update.
Also, since I was only going from 4.1.1 to 4.1.2, I dirty flashed without wiping anything, and had no problems.
SempaiMatt said:
After reading about people having problems losing root after the OTA update, I decided to not to take it, and instead flashed a stock rooted 4.1.2 image, per this thread: http://forum.xda-developers.com/showthread.php?t=2178482
Since I had no plans to do any theme mods, I used the Odex version. Scroll down to post #3 and grab the 4.1.2 modem and rpm as well (which are part of the OTA). These can be flashed in the same recovery session as the update.
Also, since I was only going from 4.1.1 to 4.1.2, I dirty flashed without wiping anything, and had no problems.
Click to expand...
Click to collapse
Thanks for the info. I haven't dirty flashed my phone in ages. Do you have to clear the cache or anything? Also, will settings/appdata be lost?
evergamer said:
Thanks for the info. I haven't dirty flashed my phone in ages. Do you have to clear the cache or anything? Also, will settings/appdata be lost?
Click to expand...
Click to collapse
Dirty flash is just clear cache and dalvik cache, you will not loose app/system settings.
evergamer said:
Do you have to clear the cache or anything? Also, will settings/appdata be lost?
Click to expand...
Click to collapse
I cleared absolutely nothing, and all settings and app data were unchanged. (Actually, some bloatware that I had previously uninstalled was returned.) My thinking was that the OTA was only a small update that wouldn't screw up settings and data. Of course, I did a full nandroid backup in case things didn't work.
Also, the stock rooted 4.1.2 thread says that the vzw installer is removed. However, after flashing it, I noticed there was still an "SDM 1.0" service still on my phone, which I think has something to do with updates, and I froze it with Titanium Backup. (Since then, I've flashed CleanROM 6 R2, and the SDM 1.0 is gone.)
buhohitr said:
Dirty flash is just clear cache and dalvik cache, you will not loose app/system settings.
Click to expand...
Click to collapse
K, cool. I don't remember the last time I flashed like that. I always flash clean with AOKP.
And 724mb for a ROM? Seems huge.
evergamer said:
K, cool. I don't remember the last time I flashed like that. I always flash clean with AOKP.
And 724mb for a ROM? Seems huge.
Click to expand...
Click to collapse
Full bloated rom is about 1gb, if you debloated you should have smaller rom size, so 724mb is about OK.
Related
Hi,
I have a i9020a on 4.0.4 rooted. Got the OTA for JB update and after downloaded the file and restart, I got the "signature verification failed" in CWM recovery. Wonder what I need to do to be able to work around this. Do I have to revert back to stock recovery and if yes is there a guide on how to do that ?
Thanks
d960 said:
Hi,
I have a i9020a on 4.0.4 rooted. Got the OTA for JB update and after downloaded the file and restart, I got the "signature verification failed" in CWM recovery. Wonder what I need to do to be able to work around this. Do I have to revert back to stock recovery and if yes is there a guide on how to do that ?
Thanks
Click to expand...
Click to collapse
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1. I logged everything in got the 4.0.4 1mb first then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
I chose to get the OTAs this way instead, but I'm sure just flashing is fine.
Hope this helps.
You can't actually receive and install the ota with a custom recovery.
You can flash it manually with a custom recovery.
You can get it ota and have it install automatically with stock.
Can't install a ota when its pushed to your phone over the air with custom and you can't manually flash it with stock recovery.
jayjay3333 said:
I went to stock by doing this. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
I didn't flash the updates in the second part #1. I logged everything in got the 4.0.4 1mb first then did this to get the 4.1.1 http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
Go into airplane with a strong wifi signal on for this to work.
I then rerooted (2nd part #2 on)
I chose to get the OTAs this way instead, but I'm sure just flashing is fine.
Hope this helps.
Click to expand...
Click to collapse
Thanks, did you do the wipe as well? I was wondering how to properly wipe, e.g., go to setting and storage and erase everything, is that considered wipe?
albundy2010 said:
You can't actually receive and install the ota with a custom recovery.
You can flash it manually with a custom recovery.
You can get it ota and have it install automatically with stock.
Can't install a ota when its pushed to your phone over the air with custom and you can't manually flash it with stock recovery.
Click to expand...
Click to collapse
Thanks for education. Still pretty new on this...
d960 said:
Thanks, did you do the wipe as well? I was wondering how to properly wipe, e.g., go to setting and storage and erase everything, is that considered wipe?
Click to expand...
Click to collapse
This is a "clean" wipe:
full wipe / changing roms:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with a "virgin" phone, only bootloader, recovery and radio are left. dalvik-cache resides on /data, so it's gone already.
You could also format SD in recovery as well. I moved everthing I wanted out and wiped for a nice fresh start, but that's just me :good:
jayjay3333 said:
This is a "clean" wipe:
full wipe / changing roms:
1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)
2. format /system, /boot
this leaves you with a "virgin" phone, only bootloader, recovery and radio are left. dalvik-cache resides on /data, so it's gone already.
You could also format SD in recovery as well. I moved everthing I wanted out and wiped for a nice fresh start, but that's just me :good:
Click to expand...
Click to collapse
Thanks. I managed to update to JB following the guide you are refering to and also the steps you took (i.e., doing OTA update). In general it went smooth but I do encounter some issues that I want to ask the OP of that thread.
Hello, this is probably a stupid question but I have custom kernel and some other tweaks to my 4.4.2 N5 so OTA will fail.
Since I don't want to wipe my device (nor wait for the OTA) could I just download 4.4.3 images and flash 4.4.3 /system and /boot to my device without wiping it?
Or do I have to flash 4.4.2 image and then flash the OTA via recovery?
DarknessWarrior said:
Hello, this is probably a stupid question but I have custom kernel and some other tweaks to my 4.4.2 N5 so OTA will fail.
Since I don't want to wipe my device (nor wait for the OTA) could I just download 4.4.3 images and flash 4.4.3 /system and /boot to my device without wiping it?
Or do I have to flash 4.4.2 image and then flash the OTA via recovery?
Click to expand...
Click to collapse
You can (i did as well) but any tweaks to system files etc will be overwritten and it will go to stock kernel.
to do this. follow the directions at the below link. the step about changing the flash-all file is crucial as if you don't do that then it will wipe your data as well.
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
y2whisper said:
You can (i did as well) but any tweaks to system files etc will be overwritten and it will go to stock kernel.
to do this. follow the directions at the below link. the step about changing the flash-all file is crucial as if you don't do that then it will wipe your data as well.
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
Click to expand...
Click to collapse
Thank you. I don't really care about the tweaks and the kernel I'll flash later, I just don't want to wipe and have to reinstall/reconfigure everything.
DarknessWarrior said:
Hello, this is probably a stupid question but I have custom kernel and some other tweaks to my 4.4.2 N5 so OTA will fail.
Since I don't want to wipe my device (nor wait for the OTA) could I just download 4.4.3 images and flash 4.4.3 /system and /boot to my device without wiping it?
Or do I have to flash 4.4.2 image and then flash the OTA via recovery?
Click to expand...
Click to collapse
Because I've also modified too many system files I usually open up the factory image and pull the images I need and flash those, or you could flash the boot and system images from 4.4.2 and do the OTA. For the update to 4.4.3 you would need the boot, radio and system images. The bootloader image stayed the same. Scenario 2 in this link will show what I'm talking about. Really only takes a few minutes. ; )
Wanted to add that at the end instead of doing fastboot reboot I would unplug your phone and use your volume and power button to get into recovery and flash the supersu zip.
Updated my N5 and N7 Monday night and everything is working well!
Not a great idea
Most likely you'll wind up with issues from the dirty flash and have to reset the device anyway in my experience.
I tried flashing 4.4.3 I'm on stock rooted but it won't install when trying to flash gives me a error status 7. Anyone please help!
Dirty flashing a new android version is a bad idea. In my opinion.
Clean flash.
---------- Post added at 07:54 PM ---------- Previous post was at 07:51 PM ----------
Maybe they tweaked location services to not suck so much juice.
I always toggle it off. Will have to try it on after I update.
Clean flash only for a new version has always been the golden rule!
Lol, what? Clean flash only if you're switching ROMs. If you're on the factory rom, flashing a factory image is perfectly fine. I've upgraded 4 different devices through many versions of Android with out a single issue.
galaxys said:
Clean flash only for a new version has always been the golden rule!
Click to expand...
Click to collapse
Completely agree. Regardless of how many problems other people haven't had. The exact same principles apply as custom ROMs. Legacy data and settings can interfere between versions so I would always recommend a wipe, at least before reporting any "bugs"
Sent from my Nexus 5 using Tapatalk
GldRush98 said:
Lol, what? Clean flash only if you're switching ROMs. If you're on the factory rom, flashing a factory image is perfectly fine. I've upgraded 4 different devices through many versions of Android with out a single issue.
Click to expand...
Click to collapse
Many can't say the same. Clean flashing the firmware is always better than dirty flashing or updating by OTA.
Yup
Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
UPDATE: I was able to make it work, see comment #12
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
timmaaa said:
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
rhaces said:
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
Click to expand...
Click to collapse
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
timmaaa said:
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
Click to expand...
Click to collapse
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
rhaces said:
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
Click to expand...
Click to collapse
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
timmaaa said:
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
Click to expand...
Click to collapse
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
Follow vomer's guide here. It just bring your rom back to stock and leaves user data untouched. http://forum.xda-developers.com/showpost.php?p=55882576&postcount=229
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
There's nothing wrong with Titanium if you know how to use it. Unless you're restoring system data (which you shouldn't be) it's perfectly solid. And the thing is, you're not stock, those modifications you've made mean that you're not stock, so it's completely normal that you'd have issues with updating. You can moan about it all you like but it doesn't change the fact that you need to wipe.
Transmitted via Bacon
What he said.
You can't apply an OTA update if u have a custom kernel installed.
Just go back stock and apply updates until the latest version. If u use titanium properly you will not have any issue, just backup user apps without system settings.
Any other turnaround can cause havoc.
rhaces said:
Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
Click to expand...
Click to collapse
Please check http://forum.xda-developers.com/showpost.php?p=55948892&postcount=16
@rhaces, just curious, could you PM me your /data/system/packages.xml file?
Well, It looks like you really don't need to wipe data (see, I told you it was ludicrous), I tried following both this and this, but did not helped (however both gave me ideas), here's what I did:
Fastboot flash boot system and recovery from 33R, boot into system, apply the OTA from the system (I'm now in an unrooted-unmodified stock 33R) and now that worked. Booted into newly installed 38R and everything worked ok, so went back to fastboot, flashed TWRP, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
Just don't complain when you start getting problems. Which you most likely will.
Transmitted via Bacon
Rooted with CWM as recovery. Shield Tablet has OTA update but obviously can't install with CWM. What is the simplest way to stay up to date and keep root?
Sent from my SHIELD Tablet using xda premium
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Scoobydumb said:
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Click to expand...
Click to collapse
That's not the way to go at all.
Whenever there's an update, flash the incremental OTA file HERE.
Flashing the stock recovery will not allow taking OTA's.
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Scoobydumb said:
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Click to expand...
Click to collapse
Um, just flash it in TWRP or CWM, only need to flash cache and dalvik cache, but that's optional.
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Singularity_iOS said:
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Click to expand...
Click to collapse
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
FoxyDrew said:
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
Click to expand...
Click to collapse
Ok thanks. One more question. How would I go about checking the rom version? Unless I'm missing it I can only see the Android version, which is 5.0.
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Singularity_iOS said:
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Click to expand...
Click to collapse
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Wouldn't the tablet be wiped then? And if this is the case everytime can't I just keep the stock recovery and sideboard a custom one?
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
NaminatoR1254jaime.sier said:
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
Click to expand...
Click to collapse
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
perky nerky said:
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
Click to expand...
Click to collapse
On my previous instructions I pointed out to (after flashing ota) to reflash custom rec and supersu.
NaminatoR1254jaime.sier said:
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Click to expand...
Click to collapse
With twrp I do it literally after flashing full ota. I leave recovery to reboot to system right when Im done flashing everything.
Hey guys!
I have the US 16GB WiFi only model of the SHIELD tablet, it's rooted, bootloader is unlocked, and I'm running 5.0.1 with a custom recovery.
I'm just a little confused as to how to updated to the 2.2.1 software that was recently released. I'm still on 2.1, and when I try to update it asks to update to 2.2 rather than the current, 2.2.1.
However it's been awhile since the last time I installed an update and I forgot the process in order to flash updates and make sure SuperSU is installed, etc.
Can anybody help me out and give me the few steps I need to take in order to make sure I still have root and my custom recovery installed as well as the 2.2.1 update? Thanks.
If you need anymore info just ask.
*UPDATE*
I downloaded the Incremental OTA update for my model from here, and used the 2.1 - 2.2 MEGA file.
I put it on my /sdcard/0/, and tried flashing it via CWM and I got this error:
Code:
Package expects build fingerprint of nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29082_493.9700:user/release-keys or nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29979_512.4856:user/release-keys; this device has nvidia/wx_na_wf/shieldtablet:4.4.2/KOT49H/22229_
Code:
E:Error in /data/media/0/productionBL-droid-signed-wx_na_wf-incremental_ota-from-29082_493.9700-to-29979_512.4856.zip
Any ideas?
rogvid700 said:
*UPDATE*
I downloaded the Incremental OTA update for my model from here, and used the 2.1 - 2.2 MEGA file.
I put it on my /sdcard/0/, and tried flashing it via CWM and I got this error:
Code:
Package expects build fingerprint of nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29082_493.9700:user/release-keys or nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29979_512.4856:user/release-keys; this device has nvidia/wx_na_wf/shieldtablet:4.4.2/KOT49H/22229_
Code:
E:Error in /data/media/0/productionBL-droid-signed-wx_na_wf-incremental_ota-from-29082_493.9700-to-29979_512.4856.zip
Any ideas?
Click to expand...
Click to collapse
Seems like your trying to upgrade from 1.2, to 2.2....
Are you currently on Android 4.4.4?
I can confirm that I am running Lollipop 5.0.1
But yeah I noticed that too. It thinks I'm running 4.4.2?
Anyone? Any ideas?
rogvid700 said:
Anyone? Any ideas?
Click to expand...
Click to collapse
Maybe there's just a glitch, or a ghost line of code preventing it from flashing.
My only advice would be to do a full wipe and just flash the full OTA instead of the incremental one.
What's the safest way of doing this?
I have Titanium Backup, and do I just use CWM to do a full wipe? Or something else?
And I'm sure it'll lose root if I do a full wipe. Would I just flash SuperSU after flashing the full OTA in order to get it back?
Sorry for all the questions. I'm not a total amateur, just not an expert.
rogvid700 said:
What's the safest way of doing this?
I have Titanium Backup, and do I just use CWM to do a full wipe? Or something else?
And I'm sure it'll lose root if I do a full wipe. Would I just flash SuperSU after flashing the full OTA in order to get it back?
Sorry for all the questions. I'm not a total amateur, just not an expert.
Click to expand...
Click to collapse
Exactly what you said. Full wipe, then reflash SuperSU.
You'll also have to reflash CWM, as flashing the full OTA in CWM, flashes the stock recovery.
Okay so, I need to put the full OTA on my device, and then wipe? Or vice versa?
Because won't the full wipe remove the full OTA if it's on my device?
So, full wipe, flash OTA, flash CWM, flash SuperSU? (Please correct me if this order is wrong)
rogvid700 said:
*UPDATE*
I downloaded the Incremental OTA update for my model from here, and used the 2.1 - 2.2 MEGA file.
I put it on my /sdcard/0/, and tried flashing it via CWM and I got this error:
Code:
Package expects build fingerprint of nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29082_493.9700:user/release-keys or nvidia/wx_na_wf/shieldtablet:5.0.1/LRX22C/29979_512.4856:user/release-keys; this device has nvidia/wx_na_wf/shieldtablet:4.4.2/KOT49H/22229_
Code:
E:Error in /data/media/0/productionBL-droid-signed-wx_na_wf-incremental_ota-from-29082_493.9700-to-29979_512.4856.zip
Any ideas?
Click to expand...
Click to collapse
Because u cant do that. You cant flash an incremental OTA via custom rec.
If u are rooted you need to flash latest FULL OTA vía custom recovery, reflash supersu andnyou should be ready
There is no need to full wipe everything. Just "dirty flash" it. Make a nandroid just in case.
1- Make nandroid
2- Flash full ota
3- Wipe cache & dalvik
4- Flash custom rec
5- Flash supersu
That should do it.
So the nandroid backup just won't work through CWM, it fails when trying to backup /data.
I've tried wiping the cache and still nothing. If I just want to go ahead and do a full wipe, where would that be in the steps you gave me?
Thanks!
rogvid700 said:
Okay so, I need to put the full OTA on my device, and then wipe? Or vice versa?
Because won't the full wipe remove the full OTA if it's on my device?
So, full wipe, flash OTA, flash CWM, flash SuperSU? (Please correct me if this order is wrong)
Click to expand...
Click to collapse
Yes this is correct. And when I say full wipe, if it's not obious, DON'T wipe internal storage, or External SD card.
FoxyDrew said:
Yes this is correct. And when I say full wipe, if it's not obious, DON'T wipe internal storage, or External SD card.
Click to expand...
Click to collapse
Thanks you guys! Followed the steps, flashed the full OTA, then CWM, then SuperSU and i am now on 2.2.1 with root!