Hey guys,
Even after reading tons of threads, I cant seem to manually sideload an update for 5.0.1.
I just got this Nexus 6, but have been a long time user since Nexus 4.
What is the easiest way to upgrade to 5.0.1 without loosing all my data? Thanks again!
So you're stock unrooted? What happens when you sideload? Please give more info
Ive already tried to download the patch but cant seem to apply, even following a few guides.....
Reply
rootSU said:
So you're stock unrooted? What happens when you sideload? Please give more info
Click to expand...
Click to collapse
I am stock, rooted, unlocked. I tried to manually sideload with no success. I also tried the nexus toolbox. I get all the way to the end, and it looses ADB connection
@RoysGTI
If you are rooted, you will not be able to side load the update. And "unroot" will still leave some files which will prevent it from installing.
You need to extract the system.img from 5.0.0 and fastboot flash it. This will leave your user data intact. Then after flashing the update, you will have to reroot.
I assume you are still encrypted?
cam30era said:
@RoysGTI
If you are rooted, you will not be able to side load the update. And "unroot" will still leave some files which will prevent it from installing.
You need to extract the system.img from 5.0.0 and fastboot flash it. This will leave your user data intact. Then after flashing the update, you will have to reroot.
I assume you are still encrypted?
Click to expand...
Click to collapse
Could you assist me in the flashing of the system.img? How will that get me to 5.0.1?
I am not sure if I am encrypted or not.....
RoysGTI said:
Could you assist me in the flashing of the system.img? How will that get me to 5.0.1?
I am not sure if I am encrypted or not.....
Click to expand...
Click to collapse
You need to take a step back and do some reading and studying before doing anything else with your phone. You don't want to risk doing something wrong and bricking your device. Read and study these tutorials before proceeding further. Make sure you thoroughly understand everything, before proceeding. And don't hesitate to ask questions in those respective threads.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
cam30era said:
You need to take a step back and do some reading and studying before doing anything else with your phone. You don't want to risk doing something wrong and bricking your device. Read and study these tutorials before proceeding further. Make sure you thoroughly understand everything, before proceeding. And don't hesitate to ask questions in those respective threads.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Ok, I followed the first steps again, and restored back to original stock factory image. Going to check my version and then reroot.
Once I root again, will I have to do this same process for every OTA update?
RoysGTI said:
Ok, I followed the first steps again, and restored back to original stock factory image. Going to check my version and then reroot.
Once I root again, will I have to do this same process for every OTA update?
Click to expand...
Click to collapse
OTA will not install if you are rooted.
cam30era said:
OTA will not install if you are rooted.
Click to expand...
Click to collapse
Got updated to 5.0.1 with root access now. Thanks again for your help! It def. helps starting from scratch.
RoysGTI said:
Got updated to 5.0.1 with root access now. Thanks again for your help! It def. helps starting from scratch.
Click to expand...
Click to collapse
There's a button for that.
Related
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Scoopta said:
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Click to expand...
Click to collapse
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
jayboyyyy said:
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
Click to expand...
Click to collapse
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Scoopta said:
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Click to expand...
Click to collapse
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
jayboyyyy said:
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
Click to expand...
Click to collapse
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Scoopta said:
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Click to expand...
Click to collapse
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
jayboyyyy said:
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
Click to expand...
Click to collapse
ok...thanks for the info. I'll see if I can find a thread on it.
So I will have my new phone from T mobile on Wednesday and want to unlock and root it right away. I have read how to do it and it looks easy enough.
If I keep stock Rom and don't flash a custom kernel, can i still get updates or once you root can you no longer update?
thanks
nixie2121 said:
So I will have my new phone from T mobile on Wednesday and want to unlock and root it right away. I have read how to do it and it looks easy enough.
If I keep stock Rom and don't flash a custom kernel, can i still get updates or once you root can you no longer update?
thanks
Click to expand...
Click to collapse
Once you root lollipop you can't accept OTAs, however you can flash the update via fastboot.
nixie2121 said:
So I will have my new phone from T mobile on Wednesday and want to unlock and root it right away. I have read how to do it and it looks easy enough.
If I keep stock Rom and don't flash a custom kernel, can i still get updates or once you root can you no longer update?
thanks
Click to expand...
Click to collapse
Hi! Welcome to the Nexus 6 community.
First, keep doing what you have been doing. Reading! That's the best way to learn the how to's.
As far as OTA's, lollipop requires that NO system modifications are present for OTA to flash. However, there are many ways around this "feature". Keep searching and reading here, as all of these topics have been addressed. Always remember, Google is your friend too.
Pilz said:
Once you root lollipop you can't accept OTAs, however you can flash the update via fastboot.
Click to expand...
Click to collapse
I have been reading around, mostly on tapatalk (hard to find things!)
Anyway, could you answer this question (I will learn about flashing updates via fastboot soon, maybe you can point me to a good thread to learn this?)
When I flash an update, is it like flashing a new rom meaning all apps, settings and such are wiped?
Thanks so much!!!
nixie2121 said:
I have been reading around, mostly on tapatalk (hard to find things!)
Anyway, could you answer this question (I will learn about flashing updates via fastboot soon, maybe you can point me to a good thread to learn this?)
When I flash an update, is it like flashing a new rom meaning all apps, settings and such are wiped?
Thanks so much!!!
Click to expand...
Click to collapse
This OP is a good start
http://forum.xda-developers.com/showthread.php?t=2948481
When you flash a update via fastboot don't use the flash-all.bat file because it will encrypt your phone ( if you decrypted) and wipe the user data. Flash each image manually (I always do this) and you will be fine. If you want a break down of the order I'll post it and or link a post for updating while rooted.
Pilz said:
This OP is a good start
http://forum.xda-developers.com/showthread.php?t=2948481
When you flash a update via fastboot don't use the flash-all.bat file because it will encrypt your phone ( if you decrypted) and wipe the user data. Flash each image manually (I always do this) and you will be fine. If you want a break down of the order I'll post it and or link a post for updating while rooted.
Click to expand...
Click to collapse
Did you decrypt? I see the thread on how to do that as well.
nixie2121 said:
Did you decrypt? I see the thread on how to do that as well.
Click to expand...
Click to collapse
Yes I did (Its one of the first things I did) if you wait then you will lose your user data. When you encrypt or decrypt and or unlock/re-lock the BL it will wipe your phone.
All,
I just got prompted by AT&T to install the 5.1 update and while I want it right now my phone is working near perfectly and I use a number of root needed applications. Before I do the upgrade I want to know if this will cause me to lose root and if so how easy it is to get it back? Right now I'd definitely pick root over 5.1
Searched but couldn't find an answer so sorry if I missed a thread on it already...
-Ross
rosscarlson said:
All,
I just got prompted by AT&T to install the 5.1 update and while I want it right now my phone is working near perfectly and I use a number of root needed applications. Before I do the upgrade I want to know if this will cause me to lose root and if so how easy it is to get it back? Right now I'd definitely pick root over 5.1
Searched but couldn't find an answer so sorry if I missed a thread on it already...
-Ross
Click to expand...
Click to collapse
you have root, you wont be able to update via ota. any kind of system file changes prevents you upating via ota.
simms22 said:
you have root, you wont be able to update via ota. any kind of system file changes prevents you upating via ota.
Click to expand...
Click to collapse
Ah, ok - so even if I'm being prompted you're saying that it will fail? I'm not running a custom ROM or anything just rooted. Just clarifying as it is prompting me to update.
So to update would I then need to go through the process manually? I'm sure there's a thread somewhere so I can find that, just making sure I understand...
-Ross
rosscarlson said:
Ah, ok - so even if I'm being prompted you're saying that it will fail? I'm not running a custom ROM or anything just rooted. Just clarifying as it is prompting me to update.
So to update would I then need to go through the process manually? I'm sure there's a thread somewhere so I can find that, just making sure I understand...
-Ross
Click to expand...
Click to collapse
yup, itll fail. and yes, manually. theres ways of doing it without losing data as well. yes, theres a thread for that
simms22 said:
yup, itll fail. and yes, manually. theres ways of doing it without losing data as well. yes, theres a thread for that
Click to expand...
Click to collapse
I can't find that thread
PunishedSnake said:
I can't find that thread
Click to expand...
Click to collapse
Loads of threads. Search "update losing data" or something.
But in short, just fastboot flash system.img and boot.img and not userdata.img
rootSU said:
Loads of threads. Search "update losing data" or something.
But in short, just fastboot flash system.img and boot.img and not userdata.img
Click to expand...
Click to collapse
Thats what I figured
And I went from D build to E back down to 5.0.1 then ota to M lol
I hope the release the wifi calling update as a system image
PunishedSnake said:
Thats what I figured
And I went from D build to E back down to 5.0.1 then ota to M lol
I hope the release the wifi calling update as a system image
Click to expand...
Click to collapse
If its m that's already out, I don't see a factory image coming
Will installing the stock update kill root, or worse yet brick my phone?
http://forum.xda-developers.com/showthread.php?t=3076803
Can I let the phone do the update on its own with no problems?
If you take the ota you won't be able to root. If you want to root use the thread i posted
dirtydodge said:
If you take the ota you won't be able to root. If you want to root use the thread i posted
Click to expand...
Click to collapse
.....and you won't be able to downgrade either!
Sent from my SAMSUNG-SM-G900A
Not having any luck taking the ota, keeps telling me" device storage to full please move or delete stuff......."
bigslimoid said:
Not having any luck taking the ota, keeps telling me" device storage to full please move or delete stuff......."
Click to expand...
Click to collapse
Go to the thread i posted and read in the notes section. Download the nce file and flash in odin. This will put you phone back to factory settings. Then you should be able to take the ota. If you take the ota you won't be able to root. If you want root on lollipop then follow the instructions in that same op and it'll tell you how to get to rooted Lollipop.
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
FireMedic1234 said:
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
Click to expand...
Click to collapse
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
simms22 said:
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
Click to expand...
Click to collapse
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
FireMedic1234 said:
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
Click to expand...
Click to collapse
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
simms22 said:
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
Click to expand...
Click to collapse
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
FireMedic1234 said:
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
Click to expand...
Click to collapse
ok, boot into the bootloader, connwct via usb to your computer, the type fastboot devices. at that point, it should list your phone via a number. if it does, then its all connected right. then you can flash the factory image, but do not use the flash-all script, flash them all individually.
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
FireMedic1234 said:
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
Click to expand...
Click to collapse
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
I concur. I have used "the" toolkit to see what happens. Have had multiple failures using toolkit and always had to revert to fastboot to fix. Might as well use fastboot up front. Saves a lot of time and headaches.
simms22 said:
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
Click to expand...
Click to collapse
Gotcha thanks again!
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You can drag and drop or copy/paste the image into the command line.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
are you flashing with flash-all or are you flashing each image individually. dont use flash-all, flash them individually.
Share a screen print of the command prompt, with the command you executed, and the error message?
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
FireMedic1234 said:
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
Click to expand...
Click to collapse
Yes.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You don't need to put the system.img there. Please do read general > sticky roll-up thread > adb and fastboot...
...some time.
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
FireMedic1234 said:
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
Click to expand...
Click to collapse
Yes the flash-all.bat can't break up the image. Has something to do with how it sees the partition. Have heard that fastboot in SDK 23+ has fixed this problem. Have not confirmed as I do each individually anyway depending on what I want to do.
---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------
Only way you're gonna possibly brick is flash wrong image to wrong partition. Not sure that even that can be corrected with fastboot as long as the one you bork isn't the bootloader.