So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.
Describe more.
The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.
Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!
Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.
Related
Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.
buckoman said:
Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.
Click to expand...
Click to collapse
Maybe just root(; lol and flash clean Rom stock 4.1.2
Sent from my SCH-I535 using Tapatalk 4 Beta
I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?
buckoman said:
I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?
Click to expand...
Click to collapse
Not unless you can remove the update and try again. Verizon soft bricked you. Don't know if you can remove the update file from memory and try to download again without root. Get a file explorer and look for the file. Not sure of name as I have only taken one OTA over all the years and it worked. If want to Odin the full MB1 update image is on SamMobile. If Odin that don't have to worry about OTA and will have same thing.
prdog1 said:
Not unless you can remove the update and try again. Verizon soft bricked you.
Click to expand...
Click to collapse
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?
buckoman said:
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?
Click to expand...
Click to collapse
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe
prdog1 said:
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe
Click to expand...
Click to collapse
And just making sure, using Odin will completely wipe the phone, yes?
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?
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.
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...
So I was away from my computer when the January Security update came out so Im on the December update.
I would like to know can I just jump straight to the Feb update when its available or do I need to do Jan first then Feb?
im unlocked, rooted, ex kernel, google store phone. thanks.
You can just jump.
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
kidhudi said:
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
Click to expand...
Click to collapse
I think downgrading via OTA it's quite impossible.
You have to wipe and flash the full factory image.
damn it thats what i was afraid of.
thanks
kidhudi said:
damn it thats what i was afraid of.
thanks
Click to expand...
Click to collapse
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
TonikJDK said:
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
Click to expand...
Click to collapse
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
kidhudi said:
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
Click to expand...
Click to collapse
Time to start clearing data on the dialer related apps, or reset the phone. I am hopeful that will help you. If it was soley update related the forum would be blowing up with complaints.
Now did something go wrong with your update... I'll buy that.
i just assumed it was the april security update it started acting up around the same time. i thought maybe a crappy download
i already did a few factory resets. tried third party dialers. everything i could think of.
what really sucks is i am 3 months out of the 1 year google warranty. so i am pretty much screwed.
thanks for your help bro
i will try to sideload the latest ota.. if it is still jacked up then it is probably hardware related
what sucks is i am still paying it off and it is virtually unusable lol.. at least i can text