I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778975696 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Cheetah1024 said:
I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Click to expand...
Click to collapse
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Evolution_Tech said:
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Click to expand...
Click to collapse
Oh, so it's normal that flash-all doesn't work?
Cheetah1024 said:
Oh, so it's normal that flash-all doesn't work?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Cheetah1024 said:
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Click to expand...
Click to collapse
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Evolution_Tech said:
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Click to expand...
Click to collapse
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Cheetah1024 said:
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, you helped me big time mate! Thank You! :laugh:
Related
Hi all,
I've unlocked the bootloader on my Nexus One.
I got the message that there was a new froyo update. When I try to install I got this error: "Verficiation failed".
Is there a way to install this new update, like a force on the verficition check or installing the official bootloader again?
Thanks in advance.
Regards,
Dirk
Do you have a custom recovery?
?
From what I've read you may not want to update, being the main fix is to disable/make it more difficult to root. You may want to for your own reasons, idk. Just putting it out there.
First, thanks for the reply's.
Do you have a custom recovery?
Click to expand...
Click to collapse
It could be that I have a custom recovery (I've followed a manual, and there was a step to choose for Nexus bootloader or Cyonogenmod bootloader. I've choosed Nexus.
Is there a way to get the official custom recovery back?
I don't have a custom rom.
From what I've read you may not want to update, being the main fix is to disable/make it more difficult to root. You may want to for your own reasons, idk. Just putting it out there.
Click to expand...
Click to collapse
This update does'nt make sense, but I like to have gingerbread when it comes out.
Thanks!
dirkjanneman said:
Is there a way to get the official custom recovery back?
I don't have a custom rom.
Click to expand...
Click to collapse
Yeah grab one from the FRF91 image on http://developer.htc.com and flash it via fastboot.
Rusty! said:
Yeah grab one from the FRF91 image on http://developer.htc.com and flash it via fastboot.
Click to expand...
Click to collapse
Thanks again.
I think I have to unzip that file and then :
fastboot flash boot boot.img
?
fastboot flash recovery recovery.img
Rusty! said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Yeah! It Works. Thank you!!!
Hey guys, I just got the 4.4.3 to 4.4.4 update notification on my XT1058 (Movistar, Chile). The thing is, I have TWRP so I know I can't take it right now. The device is not rooted nor it has xposed installed. My question is, how do I safely go back to stock recovery? Thanks in advance
Extract the recovery.img from your carriers 4.4.3 sbf and flash just the recovery image via fastboot. Commands should look like this.
fastboot flash recovery recovery.img
Travisdroidx2 said:
Extract the recovery.img from your carriers 4.4.3 sbf and flash just the recovery image via fastboot. Commands should look like this.
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
There's only 4.4.2 available on the sbf list to download. Is it ok or should I take another step?
chalocesped said:
There's only 4.4.2 available on the sbf list to download. Is it ok or should I take another step?
Click to expand...
Click to collapse
They are the same (the 4.4.2 / 4.4.3 recoveries).
Hit the THANKS button under the posts of those who have helped you...
samwathegreat said:
They are the same (the 4.4.2 / 4.4.3 recoveries).
Hit the THANKS button under the posts of those who have helped you...
Click to expand...
Click to collapse
I see! Thank you
I managed to flash the stock recovery, but now I'm unable to turn on wifi. Any thoughts?
chalocesped said:
I managed to flash the stock recovery, but now I'm unable to turn on wifi. Any thoughts?
Click to expand...
Click to collapse
Did you take the OTA? How did you flash stock recovery? It sounds like you borked your /persist partition...
samwathegreat said:
Did you take the OTA? How did you flash stock recovery? It sounds like you borked your /persist partition...
Click to expand...
Click to collapse
No I haven't, as I can't download it via mobile network. I downloaded the 4.4.2 stock firmware, took the recovery file from the zip and did fastboot recovery recovery.img. After booting and realizing I couldn't turn on the wifi (slides immediately to off) I did a factory reset but it didn't solve it
chalocesped said:
No I haven't, as I can't download it via mobile network. I downloaded the 4.4.2 stock firmware, took the recovery file from the zip and did fastboot recovery recovery.img. After booting and realizing I couldn't turn on the wifi (slides immediately to off) I did a factory reset but it didn't solve it
Click to expand...
Click to collapse
Have you tried wiping cache and dalvik, then rebooting? That used to solve a similar problem on another phone.
gokart2 said:
Have you tried wiping cache and dalvik, then rebooting? That used to solve a similar problem on another phone.
Click to expand...
Click to collapse
Unsuccesful, sadly. Will try to restore a previous backup made with twrp
OTA 4.4
Do you have to go back to stock recovery if you're using TWRP recovery? Or is there a way to apply the update while using TWRP? I downloaded the update, told it to install and it rebooted to TWRP. The only zip I found was the old update under cache. Is there a way to do this or where do I find the newly downloaded file to install?
When I couldn't find the file I just rebooted. After booting up the phone attempted to reboot and install about 3 or 4 times before saying unsuccessful and operating normally.
TKil9 said:
Do you have to go back to stock recovery if you're using TWRP recovery? Or is there a way to apply the update while using TWRP? I downloaded the update, told it to install and it rebooted to TWRP. The only zip I found was the old update under cache. Is there a way to do this or where do I find the newly downloaded file to install?
When I couldn't find the file I just rebooted. After booting up the phone attempted to reboot and install about 3 or 4 times before saying unsuccessful and operating normally.
Click to expand...
Click to collapse
You have to use stock recovery.... Just flash TWRP back on afterwards.
Sent from my XT1058 using Tapatalk
superp32 said:
Could it be because he downgraded from 4.4.3
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Who downgraded? The OP doesn't appear to have downgraded - he only flashed the stock recovery from 4.4.2 (which is the same as the 4.4.3 stock recovery). I'm confused.
samwathegreat said:
Who downgraded? The OP doesn't appear to have downgraded - he only flashed the stock recovery from 4.4.2 (which is the same as the 4.4.3 stock recovery). I'm confused.
Click to expand...
Click to collapse
I am in the process of deleting it I didn't see your post about them being the same. He has to have an unlocked bootloader to have twrp correct?
Sent from my XT1058 using Tapatalk
superp32 said:
I am in the process of deleting it I didn't see your post about them being the same. He has to have an unlocked bootloader to have twrp correct?
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Yup, although safestrap recovery (for locked bootloaders) is based on TWRP, it isn't the same. So at least he will be able to root again afterwards. Being unlocked doesn't affect the ability to take an OTA though. I've seen some people confused about that and tell people that they need to re-lock before taking an OTA. This is NOT the case. Stock recovery is required though.
Don't want to confuse anybody though. Just ignore the above. All that really matters is you must have stock recovery and no significant modifications to /system (no Xposed, etc.).
I'm on 4.4.2 for Sprint, i got the update to install 4.4.4, after reading this thread and the guide to flash OTA i see I have to return to stock recovery. My question is in the guide it says '' if you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO''...... my bootloader says 30.B4 , so should i take the OTA?
reds28heem said:
I'm on 4.4.2 for Sprint, i got the update to install 4.4.4, after reading this thread and the guide to flash OTA i see I have to return to stock recovery. My question is in the guide it says '' if you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO''...... my bootloader says 30.B4 , so should i take the OTA?
Click to expand...
Click to collapse
Hmm I'm thinking that what you read might have been for another variant....I'm not familiar with the bootloader version.
Regardless, if you are concerned, you are completely safe to flash the ENTIRE stock 4.4.2 SBF, then you can SAFELY take the 4.4.4 OTA with no risk. And if you take the OTA immediately after flashing the entire SBF, you'll already have stock recovery and you can just flash TWRP and re-root AFTER you are on 4.4.4.
:good:
(The above instructions ONLY apply to the Sprint variant. Not any of the variants that received 4.4.3.)
samwathegreat said:
Hmm I'm thinking that what you read might have been for another variant....I'm not familiar with the bootloader version.
Regardless, if you are concerned, you are completely safe to flash the ENTIRE stock 4.4.2 SBF, then you can SAFELY take the 4.4.4 OTA with no risk. And if you take the OTA immediately after flashing the entire SBF, you'll already have stock recovery and you can just flash TWRP and re-root AFTER you are on 4.4.4.
:good:
(The above instructions ONLY apply to the Sprint variant. Not any of the variants that received 4.4.3.)
Click to expand...
Click to collapse
Yeah that's what i was planning on doing completely flashing to stock then taking the OTA, just wanted to make sure I dont brick my phone
Problem, im trying flash stock but i keep getting this.
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 907079228 bytes
error: cannot load 'system.img': Not enough space
reds28heem said:
Yeah that's what i was planning on doing completely flashing to stock then taking the OTA, just wanted to make sure I dont brick my phone
Problem, im trying flash stock but i keep getting this.
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 907079228 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
System.img is too big for the standard Fastboot.exe included in the Android SDK/PlatformTools. You must use the Moto tweaked fastboot (aka mfastboot) -> http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
So I've read a couple threads on this, but I'm still confused.
I want to update through OTA, but not encrypt my phone, ultimately.
Is this how it's done?
Flash Stock system, boot, bootloader, recovery (5.0.1)
Boot to stock recovery, adb sideload OTA
Reboot to bootloader
Flash custom boot w/o forced encryption
Reboot?
I think when I unencrypted back then, I had to make a full wipe? I want to avoid this.
George_Mn said:
So I've read a couple threads on this, but I'm still confused.
I want to update through OTA, but not encrypt my phone, ultimately.
Is this how it's done?
Flash Stock system, boot, bootloader, recovery (5.0.1)
Boot to stock recovery, adb sideload OTA
Reboot to bootloader
Flash custom boot w/o forced encryption
Reboot?
I think when I unencrypted back then, I had to make a full wipe? I want to avoid this.
Click to expand...
Click to collapse
It would be best to wait for a 5.1 no-force boot.img to be released first. And also, wait until the 5.1 systemn.img is available. Then flash 5.1 system.img and the nboot.img of your choice.
rootSU said:
It would be best to wait for a 5.1 no-force boot.img to be released first. And also, wait until the 5.1 systemn.img is available. Then flash 5.1 system.img and the nboot.img of your choice.
Click to expand...
Click to collapse
Didn't Google want to ditch force encryption with 5.1?
George_Mn said:
Didn't Google want to ditch force encryption with 5.1?
Click to expand...
Click to collapse
The only change we're expecting is that they may move from software to hardware encryption.
Though you could test it if you believe that to be the case.
rootSU said:
The only change we're expecting is that they may move from software to hardware encryption.
Though you could test it if you believe that to be the case.
Click to expand...
Click to collapse
I just read a post of someone saying 5.1 does not add an option to unencrypt.
rootSU said:
It would be best to wait for a 5.1 no-force boot.img to be released first. And also, wait until the 5.1 systemn.img is available. Then flash 5.1 system.img and the nboot.img of your choice.
Click to expand...
Click to collapse
is there no way to create a 5.1 no force boot.img from the 5.1 OTA or from the system files on the phone after the 5.1 OTA was applied?
thafngame24 said:
is there no way to create a 5.1 no force boot.img from the 5.1 OTA or from the system files on the phone after the 5.1 OTA was applied?
Click to expand...
Click to collapse
I don't know enough about unpacking boot,imgs to answer that.
I am also looking for the same thing. Sideload the OTA zip file and keep it unencrypted.
I am currently on FK and I was thinking to do this:
Flash stock 5.0.1 boot.img
Sideload the OTA
Flash unencrypted 5.1 boot.img
Of course no reboots in between to avoid the encryption.
Any thoughts?
Ladduro said:
I am also looking for the same thing. Sideload the OTA zip file and keep it unencrypted.
I am currently on FK and I was thinking to do this:
Flash stock 5.0.1 boot.img
Sideload the OTA
Flash unencrypted 5.1 boot.img
Of course no reboots in between to avoid the encryption.
Any thoughts?
Click to expand...
Click to collapse
We got the factory images now, so you don't have to flash 5.0.1 first.
5.1.0 Shamu
Is there an unencrypted 5.1 boot yet?
George_Mn said:
We got the factory images now, so you don't have to flash 5.0.1 first.
5.1.0 Shamu
Is there an unencrypted 5.1 boot yet?
Click to expand...
Click to collapse
Yes, here http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Ladduro said:
Yes, here http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Click to expand...
Click to collapse
I messed it up. Flashed everything (but the custom boot.img) and then tried to root (Cause I wanted to flash a mod through twrp) which lead into a boot which I didn't interupt quick enough.
It now just says "Encryption unsuccessful" and that I have to reset it. I even tried flashing everything again (including new unencrypted boot.img) Oh well.. Most stuff was backed up so whatever..
George_Mn said:
I messed it up. Flashed everything (but the custom boot.img) and then tried to root (Cause I wanted to flash a mod through twrp) which lead into a boot which I didn't interupt quick enough.
It now just says "Encryption unsuccessful" and that I have to reset it. I even tried flashing everything again (including new unencrypted boot.img) Oh well.. Most stuff was backed up so whatever..
Click to expand...
Click to collapse
Sorry about that...
Ladduro said:
Sorry about that...
Click to expand...
Click to collapse
Happens! I literally got everything backed up but Whatsapp so at least I got a fresh phone now lol. And it's unencrypted!
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Evolution_Tech said:
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Click to expand...
Click to collapse
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
greycobalt said:
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
Click to expand...
Click to collapse
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi hi. Made me smile. Thanks for that.
Evolution_Tech said:
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
Click to expand...
Click to collapse
I will definitely do this! Thanks. They haven't posted the Verizon 5.1.1 to the image site yet, so I'll have to wait a bit I guess. :-/ Thanks!
Didgeridoohan said:
Hi hi. Made me smile. Thanks for that.
Click to expand...
Click to collapse
Can someone explain this to me as to why https://android.googleapis.com/pack...amu-ota-LMY48I-from-LMY47Z-superblock-fix.zip gives me the following error shown in the attach picture?
Looks like it should match correctly but sideload is errorring out saying otherwise
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>adb shell getprop ro.build.fingerprint
google/shamu/shamu:5.1.1/LMY47Z/1860966:user/release-keys
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
david279 said:
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
Install the stock recovery in fastboot, you can download it from the factory images or just search for it
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
danarama said:
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
Click to expand...
Click to collapse
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
JimSmith94 said:
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
Click to expand...
Click to collapse
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
danarama said:
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
Click to expand...
Click to collapse
There is an LYZ28J factory image available, here > https://developers.google.com/android/nexus/images
danarama said:
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
Click to expand...
Click to collapse
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
JimSmith94 said:
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
Click to expand...
Click to collapse
It will lose root, but you just flash supersu from recovery
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
doublejz said:
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
Click to expand...
Click to collapse
Just flash the system.img then