Database Info

[Q] I535VRUCNC1 update

does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?

esjames said:
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
Click to expand...
Click to collapse
Literally one thing: http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3-4.30.14.pdf

Well, then. Thats a worthy update lol

esjames said:
Well, then. Thats a worthy update lol
Click to expand...
Click to collapse
by all means, if you're traveling to Canada then update away haha

Lmao wow. That's the most pitiful update ever. Seriously, couldn't they have waited until there was something more substantial and then included Canadian roaming in THAT update. As always though, Verizon is dumber than a bag of hammers...
Sent from my iPhone using Tapatalk

Might be worthwhile to extract the modem package and see if the SMS bug is rectified.

wow
i was so sure this was a KK upgrade. been looking around for how to retain root if you take it. thanks for the info!

Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.

EddieK23 said:
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
Click to expand...
Click to collapse
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.

landshark68 said:
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
Click to expand...
Click to collapse
Ah, I see, next time I'm around her I'll re-root it and backup all her stuff with titanium backup, flash the VRUCML1 and factory reset, then restore everything and see if it works.
Strangely enough, when the same update for my Verizon Note 2 came out, I was able to update while rooted even though I unsinatalled theexact same system apps I did on her phone. How strange.
Nonetheless, thank you so much.

I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks

Joe R said:
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Click to expand...
Click to collapse
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk

Ok thanks. I will try to find an ML1 download.
Sent from my Samsung Galaxy S III using Tapatalk

Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?

pnuker said:
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4

Maintained root
twistedillutions said:
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I was able to maintain root on the OTA update by having OTA Survival Mode checked on SuperSU.

SlimSnoopOS said:
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?

smalco44 said:
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
Click to expand...
Click to collapse
Apparently I need a refresher on how to properly copy and paste Here's the link again: http://forum.xda-developers.com/showthread.php?p=52515244#post52515244

I have not yet updated to this new patch yet, am I still able to install saferoot as directed on the thread for it or do I need to do something special first?

D800-20u Update (Knock Code update)

Here's the files from the update... not much we can do with them though...
http://www.androidfilehost.com/?fid=23501681358545806
Edit: I was on 800-20k with a custom recovery (autorec) installed. Taking the update will put you in a "recovery" bootloop. I was able to get out of the bootloop by nulling out the fota partition.
I reflashed the 800-20c TOT file using LGFlashtool and then went and did a software update. It downloads both 20k and 20u updates and applies them both. Afterwards I rooted using autoprime's ioroot25r1 tool (adb sideload method).
Because there is a new kernel to support knock-code, do NOT flash a recovery using autorec or anything that will affect the kernel until a developer gets their hands on it and inserts the older bootloader.
-Daryel

Just got this notification. Anybody know if there's anything important or significant with this?
Sent from my LG-D800 using Tapatalk 4

RS7JR said:
Just got this notification. Anybody know if there's anything important or significant with this?
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
The only difference I see is knock-code.
Good news is that ioroot25 still works on it.
-Daryel

so, do you lose root after this update? i'm rooted with no custom recovery

xbxjunkie said:
so, do you lose root after this update? i'm rooted with no custom recovery
Click to expand...
Click to collapse
ota should error out, mine did, i tried twice.

spdwiz18 said:
ota should error out, mine did, i tried twice.
Click to expand...
Click to collapse
hmm, then i'm not gonna do it. anyone know where it's downloaded to and what to freeze to prevent the DL again
i'm coming from a tmobile G2 and the update app is different
Nvm.....found and froze it.....problem solved

spdwiz18 said:
ota should error out, mine did, i tried twice.
Click to expand...
Click to collapse
After it errors out, do the notifications stop? I've "postponed" mine atm and have no interest in actually updating. I'm not wanting to be pestered daily by the update request. (I'm stock recovery rooted too)
Edit: It detected that I'm rooted and has stopped notifications.

daryelv said:
The only difference I see is knock-code.
Good news is that ioroot25 still works on it.
-Daryel
Click to expand...
Click to collapse
Here's AT&T's update page that has some info: http://www.att.com/esupport/article.jsp?sid=KB423381&cv=820#fbid=9EhTGDbrWCI
Software update includes:
Knock Code" security feature
Calendar/ Exchange Active Sync (EAS) enhancements
I've also noticed that Album Art for music playing in Google Music now takes up the entire lock screen; the previous release only displayed in a little box at the top.

spdwiz18 said:
ota should error out, mine did, i tried twice.
Click to expand...
Click to collapse
I was able to take the update and did not lose root. however I do not have a recovery installed.
D800 model

skullymullins said:
I was able to take the update and did not lose root. however I do not have a recovery installed.
D800 model
Click to expand...
Click to collapse
I was able to root last week with IOroot, d/l the update yesterday, and keep root.

newb here. mine just automatically updated to 20u. I saw the update when I recieved my g2 yesterday but didn't think it was going to update by its self. can I still follow the pinned newbie guide and use ioroot25 and AutoRec?
edit: re-read the first post, so can't use autorec till its updated? do you think it will take long? I wanted to put cm on

Gabe3 said:
newb here. mine just automatically updated to 20u. I saw the update when I recieved my g2 yesterday but didn't think it was going to update by its self. can I still follow the pinned newbie guide and use ioroot25 and AutoRec?
edit: re-read the first post, so can't use autorec till its updated? do you think it will take long? I wanted to put cm on
Click to expand...
Click to collapse
Autorec will work, but you'll lose the "knock code" which I doubt you would care about if you're going with CM. Autorec will be updated sometime after LG releases the source code for the kernel. The latest they still have posted is the code for D800-20c.
-Daryel

daryelv said:
Autorec will work, but you'll lose the "knock code" which I doubt you would care about if you're going with CM. Autorec will be updated sometime after LG releases the source code for the kernel. The latest they still have posted is the code for D800-20c.
-Daryel
Click to expand...
Click to collapse
thats great, thanks. and ioroot still works as well? i'll have to do some googling what the knock code is.

I'm bone stock, unrooted and just got the latest update. Only difference i see is Knock Code (which is very cool BTW), other than that it's still the same old awesome G2. Glad to see they are still paying attention to it now that they are focusing on the G3. Wonder if we'll get the new G3 UI on the (stock) G2

ItsDon said:
I'm bone stock, unrooted and just got the latest update. Only difference i see is Knock Code (which is very cool BTW), other than that it's still the same old awesome G2. Glad to see they are still paying attention to it now that they are focusing on the G3. Wonder if we'll get the new G3 UI on the (stock) G2
Click to expand...
Click to collapse
This! :thumbup:
Scribe'd on my awesome OG2

daryelv said:
Autorec will work, but you'll lose the "knock code" which I doubt you would care about if you're going with CM. Autorec will be updated sometime after LG releases the source code for the kernel. The latest they still have posted is the code for D800-20c.
-Daryel
Click to expand...
Click to collapse
"IF and WHEN" LG decides to update it seeing as they never released source for 10q or 20k(and now 20u but it just started going public so who knows)

daryelv said:
Edit: I was on 800-20k with a custom recovery (autorec) installed. Taking the update will put you in a "recovery" bootloop. I was able to get out of the bootloop by nulling out the fota partition.
-Daryel
Click to expand...
Click to collapse
How can I do that? Nulling out the fota partition
I have the same problem
Thanks
Sent from my KFTHWI using Tapatalk

Sj12345 said:
How can I do that? Nulling out the fota partition
I have the same problem
Thanks
Click to expand...
Click to collapse
Like this...
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
-Daryel

I tried ioroot25r1 on the 20u update but when it says press any key to continue the window just closes.

Gabe3 said:
I tried ioroot25r1 on the 20u update but when it says press any key to continue the window just closes.
Click to expand...
Click to collapse
have you tried the manual method:
1)open cmd window inside ioroot25 folder
2)place phone in airplane mode and enable usb debugging then plug into pc
3)type adb devices in cmd to make sure device is visible
4)after you see your device type adb reboot recovery
5)when the phone reboots into stock recovery using volume keys scroll to adb sideload update option and use power button to confirm
6)in cmd window type adb sideload kk_root.zip
7)you should see dat root on phone screen
8)enjoy root
Click to expand...
Click to collapse
Sent from my Potato powered G2 D800

Could someone make a flashable zip for the new update D80120e June 30, 2014.

Could someone make a flashable zip for the new update D80120e June 30, 2014 please?!

demoncamber said:
Could someone make a flashable zip for the new update D80120e June 30, 2014 please?!
Click to expand...
Click to collapse
I just noticed that being posted. Do you know the Android OS version (i.e. v4.4.x... what is x?)?

Still 4.4.2 http://support.t-mobile.com/docs/DOC-7591#update_download_computer

demoncamber said:
Still 4.4.2 http://support.t-mobile.com/docs/DOC-7591#update_download_computer
Click to expand...
Click to collapse
BLAH!

Has anyone found a link to download the kdz yet?

demoncamber said:
Has anyone found a link to download the kdz yet?
Click to expand...
Click to collapse
Just updated the thread here with the link. I didn't want to start a whole new thread or have it get lost in another thread.

I just bought my phone from Swappa. It's currently rooted,TWRP and running D80120a.
I received OTA update notification last night.
Will I loose root if I allow it to install?
If so, how can I ignore it and disable the notification?

Howie Dub said:
Just updated the thread here with the link. I didn't want to start a whole new thread or have it get lost in another thread.
Click to expand...
Click to collapse
Awesome. thank you
Hope someone has time to put up a flashable zip [emoji4]

sixcoronas said:
I just bought my phone from Swappa. It's currently rooted,TWRP and running D80120a.
I received OTA update notification last night.
Will I loose root if I allow it to install?
If so, how can I ignore it and disable the notification?
Click to expand...
Click to collapse
If you're rooted with TWRP, the OTA won't install, at least it didn't for me. I clicked on the OTA and it rebooted into TWRP, but nothing installed. Rebooted the system, the OTA was gone, and I was still on 20a. You will lose root if you install the 20e, but you can re-root with TowelRoot and I believe you can get TWRP back with AutoRec (I used TowelRoot, but not AutoRec). From my understanding, if you use AutoRec, you will lose Knock Code.

So I tried to update and it went through the process. Even seen the little green android saying installing update . phone rebooted still had root access and about phone is showing the "a" version. Checked for update again and it said phone up to date. This doesn't seem right
Sent from my LG-D801 using XDA Free mobile app

hippiesky said:
So I tried to update and it went through the process. Even seen the little green android saying installing update . phone rebooted still had root access and about phone is showing the "a" version. Checked for update again and it said phone up to date. This doesn't seem right
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
I'm guessing you don't have a custom recovery? I had TWRP and the green android was on for a split second before TWRP started and it didn't update. I think if you're rooted, you have to update via the support tool or the pc suite. To get root back, use towelroot. Backup your data, but you should be able to keep everything on your phone if you don't wipe/reset.

Cool thanks!
Sent from my LG-D801 using XDA Free mobile app

Has anyone come across a flashable 20e radio yet?
Sent from my LG-D801

Has anyone made a zip from the newest updates kdz yet?

Not that I've found yet, seems like a lot of people ditched this phone unfortunately
Sent from my LG-D801

[Q] Root D85010f

Hey guys,
So I just got the G3 last week, and an update rolled out from AT&T. Me being the idiot I am thought it was the Lollipop update so I updated it. Turns out, it was just 10f.
Then when I looked for ways to root the G3, all the methods required the software to be on 10d, not f.
What should I do?
Any help is much appreciated.

Use the bruteforce method in Stump root.
see: http://forum.xda-developers.com/lg-g3/help/att-d85010f-update-stump-root-t2953063

You are certain it'll work for 10f?

sympathizer said:
You are certain it'll work for 10f?
Click to expand...
Click to collapse
100%. I rooted on 10f using stump.
In addition, if you plan on rooting a device and you know there is an update, please wait to install the update until you know a root method is found.

aybarrap1 said:
100%. I rooted on 10f using stump.
In addition, if you plan on rooting a device and you know there is an update, please wait to install the update until you know a root method is found.
Click to expand...
Click to collapse
Will do.
Thanks a lot!

Not rooting
sympathizer said:
Will do.
Thanks a lot!
Click to expand...
Click to collapse
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.

esanger22 said:
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
Click to expand...
Click to collapse
You can always flash back to the older version 10d in the return to stock thread.
Sent from my LG-D850 using XDA Premium HD app

Intub8 said:
You can always flash back to the older version 10d in the return to stock thread.
Sent from my LG-D850 using XDA Premium HD app
Click to expand...
Click to collapse
This is what I would do. It is possible you got a bad OTA as well. Did you factory reset after the OTA? I have seen many cases on forums where a factory reset takes care of many issues after an OTA.
Sent from my LG-D850 using Tapatalk

esanger22 said:
I too am trying to root d850 10f with bruteforce on stumproot...mine will not do it though, keeps saying device is not supported after about 7 minutes of trying. Any ideas? (Yes, i know, shouldnt have installed the darn update), but i keep seeing people rooting 10f no problem with stump, although mine wont.
Click to expand...
Click to collapse
I don't know man, do you have the correct app installed? Mine went through smoothly in less than 5 minutes.

I just did this - now i am trying to bump the device. So my memory is relatively fresh
Reboot for fresh start - Run Stump - it will say device not supported - try brute force - let it run - takes 5 - 7 and maybe 10 min after which it says "reboot" device - then go ahead and reboot device. Run stump again - it should say device is rooted. Next download "root checker" it will say rooted. Ofcourse if this all does not go thru - you can downgrade to a previous firmware and it'll go easier - however that's more labor intensive and you'll not be able to back up the current ROM with all your apps and setup.

Well, I ended up having to flash back to 10d as mentioned by many of you. This fixed the problem!

esanger22 said:
Well, I ended up having to flash back to 10d as mentioned by many of you. This fixed the problem!
Click to expand...
Click to collapse
Good to hear and I do not think you are missing much going back. At least I have found no difference. Just freeze "Software Update" to prevent nagging OTA update notifications.

aybarrap1 said:
Good to hear and I do not think you are missing much going back. At least I have found no difference. Just freeze "Software Update" to prevent nagging OTA update notifications.
Click to expand...
Click to collapse
I actually installed CM12...its friggin awesome.

I can report no issues here with Stumproot on 10f and I've restored back to stock multiple times.

Sounds like something was just messed up on my phone, everyone else was able to use it!

perhaps this
http://forum.xda-developers.com/att-lg-g3/development/rom-stock-rooted-att-odexed-d85010f-t2945873
works nicely, no muss, no fuss

If i revert to 10D do i have to use the BUMP method after root? Or just get TWRP/CWM Recovery like good ole days? I just don't care to have the BUMP bypass that is why I am asking.
I have the ATT G3 10F.

Latest OTA update unable to install - produced "Error" screen on reboot

A few days ago, I received a notification on my N5 for a new system update of size 10.1 MB. When I choose to install the update, the phone reboots as expected, shows the "Google" startup logo, shows a screen that indicates that it is installing the update for a few seconds, and then finally ends at an "Error" screen (please see the attached image).
The phone stays on this screen for quite a while (more than a minute), then finally the device restarts and the system update notification is still present.
I've tried rebooting the phone manually and installing the update again, both when charging and when off the charger, but this has not helped. I've also searched to see if others have been having this problem, but I haven't been able to find anything. Has anyone else been experiencing this issue with the latest update, or are there any suggestions for how I can go about getting the update to install properly?

I would suggest you flash the system.img and boot.img using fastboot. The latest factory image ends in 48i, Google nexus factory image and download that image, extract it and inside is another zip file, in there you'll find the system and boot images.
Sent from my Nexus 9 using XDA Free mobile app

Thank you for your speedy reply! I will do as you've suggested and respond with my results.

I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?

Why don't you just do what jd1639 suggested?
Sent from my Nexus 5 using Tapatalk

So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
cj182 said:
I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?
Click to expand...
Click to collapse
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.

TomCatullo said:
So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.
Click to expand...
Click to collapse
If your bootloader is unlocked just flashing the system and boot images does not wipe your device. If everything goes right there will be no re-setting up required, you will have to re-root if you're rooted but that's just a matter of flashing supersu in a custom recovery.
Sent from my Nexus 5 using XDA Free mobile app

Or try recovery (stock) and find the flash update from cache (might work)
Sent from my LG-D722 using XDA Free mobile app

That doesn't work. The update checks for changes to the system (root, etc.) and needs stock recovery to install.

I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?

It doesn't wipe your data... many of us have done it.

jrosado said:
I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?
Click to expand...
Click to collapse
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app

Telyx said:
It doesn't wipe your data... many of us have done it.
Click to expand...
Click to collapse
jd1639 said:
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.

jrosado said:
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.
Click to expand...
Click to collapse
Sorry about that, I meant it DOES NOT wipe the device.
Sent from my Nexus 9 using XDA Free mobile app

I'm sorry to say that it wipes all data and applications

jrosado said:
I'm sorry to say that it wipes all data and applications
Click to expand...
Click to collapse
Did you flash just the system.img and boot.img? Just doing that will not wipe your data. I do that with every update. If you flashed other images, userdata.img, then you device will be wiped
Sent from my Nexus 9 using XDA Free mobile app

Only system and boot..don't know why, but it wiped all

jrosado said:
Only system and boot..don't know why, but it wiped all
Click to expand...
Click to collapse
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, i had to do it..otherwise it would not write the firmware..is there any way to do it without unlock the bootloader?

This is why the first thing you should do when you get a nexus is unlock the bootloader...