Related
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind
***For US LTE Tablet***
Here is a .zip you can flash to update to 5.0.1 from 5.0. The OTA was pulled from my device which I factory reset to 4.4.4. It will remove root and it will reflash the stock recovery, but it will NOT relock your bootloader. Make backups! Flash at your own risk! I am not responsible for any damage that occurs.
The reason why the new 5.0.1 OTA does not flash for rooted users is a sha1 hash is generated from the system partition. If it doesn't match what the hash should be from the factory, it fails out. Removing these checks will break your device because of the new differential update method employed, which is why these sha1 hashes are so important. The .zip I have is a standard update (not differential) and can be flashed with any recovery you want
Here is a link:
https://drive.google.com/file/d/0B_iRndxSfhpXRjBXY3FXUG1tNDA/view?usp=sharing
Thanks for your explanation! Any chance for providing the same zip for eu lte?
So is this a modified zip or is it just the full version from nvidia's server?
The rest of the world - LTE - version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.
any zip for wifi only tablet?
Adrixan said:
The rest of the world version of the 5.0.1 update is here:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_un_do-full_ota-29082_493.9700.zip
Flashed fine with ClockworkMod Recovery.
If you were rooted, you need to re-root afterwards.
Click to expand...
Click to collapse
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0
What do you have to do to root after installing this?
RollWii said:
I need a little help how to flash via CWM and if i flash it will my data be erased? Plus how to reroot once i update? I have root and unlocked bootloader running 5.0
Click to expand...
Click to collapse
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
TheCrowing said:
What do you have to do to root after installing this?
Click to expand...
Click to collapse
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.
Adrixan said:
It did not reset my tablet, just like an OTA update should.
You will lose root and the custom recovery though.
To get it back, just follow the fine guide in the forum again: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
You just have to reinstall the custom recovery as detailed in the forum thread: http://forum.xda-developers.com/shield-tablet/development/recovery-cwm-recovery-nvidia-shield-t2848064 and from there flash SuperSU again.
Click to expand...
Click to collapse
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?
RollWii said:
So basically all i need to do is
1) install cwm again since i updated to lollipop and have root
2) downlaod the update and install via cwm
3) reroot using the root.img etc etc and flash super su etc etc
4) reinstall cwm
Am i going the right path?
Click to expand...
Click to collapse
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?
RollWii said:
Ok so its the same process like when i updated from kitkat to lollipop. One last question do i need to use the boot.img again?
Click to expand...
Click to collapse
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)
Adrixan said:
I never came into a situation, where i had to use some extra boot.img.
When I got my shield recently, I directly updated to 5.0 before rooting and only did the update to 5.0.1 with a previously rooted device.
So, I'd assume, if you are on 5.0 rooted, my instructions should work for you.
And careful, as mentioned above, my link is for the Rest of the world LTE version! (not us!)
Click to expand...
Click to collapse
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?
RollWii said:
Oh good that you mentionedim using US Unlocked LTE so your file wont work on mine?
Click to expand...
Click to collapse
No, but the File from the guy, who started this thread should work for the U.S. LTE version following the same instructions as I just gave.
How long should it be sitting at the NVIDIA screen after flashing the update?
It went after a couple minutes.
Adrixan said:
What I did:
I WAS on 5.0 already! I don't know, if you can go directly from a KitKat release to 5.0.1!
1) Reboot recovery and flash zip like any other
2) Reboot normally, root will be lost. Don't restore root, when CWM asks you to.
3) reboot into fastboot mode
4) fastboot flash recovery recovery.img with the recovery.img from the thread, mentioned above
5) boot into recovery mode
6) flash the SuperSU update zip
7) reboot again, when cwm asks to fix root access, select yes this time
8) have a rooted shield on 5.0.1
Click to expand...
Click to collapse
sorry but i forgot how to flash the SUperSU update.zip how and where can i find it again?
Hi,
I have a rooted Nexus 4 with android 5.0 lollipop build LRX21T.
I have TWRP recovery installed version : v2.8.0.1
The device id rooted via placing the zip file in the device and flashng it via TWRP recovery.
But i am not able to update to android 5.0.1 via google OTA update.
Everytime i try to install the 5.0.1 OTA it goes to TWRP recovery.
I found that the downloaded OTA update file is placed in /cache folder , so i try to update it manually but failed as it shows some update partition error.
"E: error executing updater binary in zip '/cache/e93b********************.signed-occam-LRX22c-from-LRX21T.e93b****.zip"
update partition details.....
I think i am getting this error because the device is rooted.
Can someone guide me how to update my device..and if this because of the rooted device how to unroot without going back to stock.
Thanks in advance....
You can't flash the ota in twrp. You have to be 100% stock recovery, system, kernel, and radio. Flash the stock recovery with fastboot then try the ota.
Sent from my Nexus 9 using XDA Free mobile app
I flashed the stock recovery the OTA update continued in the stock recovery , then it showed a error....and i had to restart the phone ...now the ota update has disappeared with the phone still in android 5.0 ...Can you tell me how to get the OTA update back...?
1)Does the error came because the phone is still rooted ?
2) If so how do i remove the root with returning stock .?
3) also if i root and return to stock will it wipe my phone apps and their data...
Now i got the OTA update downloaded manually on my laptop and and booted into stock recovery to try to sideload the zip it gave me the error
"package expects build fingerprint of google /occam/mako:5.0/LRX21T or google /occam/mako:5.0/LRX22C user release keys; this device has google/occam/mako:4.4/KRT160 user release keys .....
This is weird as i am running android android lollipop 5.0 LRX21T and not android kitkat....
Did you flash mods while rooted?
Sent from my Nexus 4
arkangel72 said:
Did you flash mods while rooted?
Sent from my Nexus 4
Click to expand...
Click to collapse
Tried both...with and without Root....same error....
Try flashing factory image.
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
sachin.parmar100 said:
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
Click to expand...
Click to collapse
Actually i dont want to flash stock as i will lose all the data in the process....
Any other way....?
If there is no other way could you please suggest any tool kit which will backup all data including sms ,contact, call logs and all app data and /data/media folder. in one go ...?
use advanced backup from twrp backup menu and select data only to create a nandroid backup of data only
you can also use titanium backup to backup to choose what to backup and restore it afterwards but it will need root again.
sync your contacts with google server
Flah rom in fastboot
Download factory image, flash system, bootloader and recovery manually. You won't lose your data.
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
sachin.parmar100 said:
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
Click to expand...
Click to collapse
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Yaz75 said:
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Click to expand...
Click to collapse
thanks for pointing out i was so wrong
Hello,
Is it possible to update from 5.0 to 5.1 if i have unlocked the bootloader? I also have TWRP. I downloaded the 5.1 update, but when i want to install it the phone reboots and i get into TWRP menu. Is there any way to flash the OTA update without losing my current data on the phone?
Thank you!
Dealing with the same problem here.
IIRC TWRP automatically handled OTA updates in the past but it doesn't seem to be working anymore.
What was the procedure you were using before? You just installed as a normal zip from TWRP ?
For the ota to work you have to be 100% stock system, recovery, and kernel. I'd just flash the system and boot images from 5.1 in fastboot to update.
Sent from my Nexus 5 using XDA Free mobile app
So sad. I will lose all the stuff I have on the device.
tzeus said:
So sad. I will lose all the stuff I have on the device.
Click to expand...
Click to collapse
Not if you just flash the System and Boot images and remove -w from the Flashall.bat command to prevent the wipe instead of using the OTA. If you use the OTA, you will have to be stock as the previous posted stated, which since you are rooted with a custom recovery, would require you to flash the stock image, wiping your device, before you could run the OTA. This is the result of a change in the way Android 5.+ authenticates, which is why it worked previously. It now checks the whole partition, and one byte out of place will abort it.
That said, you can always backup your phone (which is a good thing to do anyway before flashing/upgrading) to prevent data loss.
Edit: Actually, thinking about it, I think Wugs added a No Wipe option to his toolkit, just flash System and Boot images from there is likely easiest for you.
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
tzeus said:
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
Click to expand...
Click to collapse
To be clear, you do not need to relock your bootloader. You can just flash 5.1 and then root and install a custom recovery like TWRP again, yes. If you are not familiar, Wug's NRT make this a breeze. Once you get 5.1 installed, just hit root. It will install the latest TWRP version and root/install SuperSU and Busybox for you.
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
tzeus said:
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
Click to expand...
Click to collapse
No, download the image and extract it. See this, http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
I figured out how to update after flashing twrp. Maybe obvious to some but I've seen questions about it.
The zip in the "Convert CA to WW" thread has the stock rom in a zip file. Open it and inside is a recovery.img file in it, extract it to your adb folder on your PC.
Download the firmware update from ASUS official site and save to the root of your sd card or internal storage (it will recognize both.)
Reboot into fastboot on your device.
fastboot flash recovery recovery.img
When that finishes reboot and your phone should find the update and ask if you want to install. Do so. You may need to power cycle first.
When you're done you can reflash TWRP.
Once you have TWRP you can flash Magisk or SuperSU as you see fit.
It's painless.
An old post from you, but thank you. This was really easy. I've spent 2 days trying to figure out how to upgrade without restore stock rom, boot etc. and lose all data. I was about to give up when I saw this post, I didn't expect it to work - to easy. But I could give it a try.
This was painless.
Then it took me 3 hours to figure out how to reinstall twrp again, it wasn't just to flash and reboot I had to boot directly into recovery after flash. But that is another story.
Thanks, you just saved me some time!
Kasdarack said:
I figured out how to update after flashing twrp. Maybe obvious to some but I've seen questions about it.
The zip in the "Convert CA to WW" thread has the stock rom in a zip file. Open it and inside is a recovery.img file in it, extract it to your adb folder on your PC.
Download the firmware update from ASUS official site and save to the root of your sd card or internal storage (it will recognize both.)
Reboot into fastboot on your device.
fastboot flash recovery recovery.img
When that finishes reboot and your phone should find the update and ask if you want to install. Do so. You may need to power cycle first.
When you're done you can reflash TWRP.
Once you have TWRP you can flash Magisk or SuperSU as you see fit.
It's painless.
Click to expand...
Click to collapse
Will this recovery work for upgrading nougat to oreo?
Em Kay said:
Will this recovery work for upgrading nougat to oreo?
Click to expand...
Click to collapse
You need to upgrade to latest N - ...14.2020.1712.85, once you do that you should get Oreo as FOTA after reboot
DanFreed said:
You need to upgrade to latest N - ...14.2020.1712.85, once you do that you should get Oreo as FOTA after reboot
Click to expand...
Click to collapse
Thanks, man.
Can I manually update with the recovery by downloading the rom?
I think, the FOTA won't arrive as I've rooted my phone.
Em Kay said:
Thanks, man.
Can I manually update with the recovery by downloading the rom?
I think, the FOTA won't arrive as I've rooted my phone.
Click to expand...
Click to collapse
When you flash stock recovery and update you unroot, so you will get FOTA. Just update to Oreo and then flash twrp and Magisk (or whatever you use) again.
I am rooted and updated to Oreo then chose updates involving battery improvement and/or system stability (downloaded to external sd), after installed the last update I flashed twrp and rooted again.
You need to flash stock recovery before update. The phone will find the updated with custom recovery but update will fail.
The site I downloaded stock recovery from is down so you have to search for it, or download RAW stock rom and extract the recovery from it
DanFreed said:
You need to flash stock recovery before update. The phone will find the updated with custom recovery but update will fail.
The site I downloaded stock recovery from is down so you have to search for it, or download RAW stock rom and extract the recovery from it
Click to expand...
Click to collapse
Anyone know where I can get stock recovery or how to extract from stock image from the ASUS site?
derbend said:
Anyone know where I can get stock recovery or how to extract from stock image from the ASUS site?
Click to expand...
Click to collapse
Seems like Mega is up again. You should find stock recovery here
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB
DanFreed said:
Seems like Mega is up again. You should find stock recovery here
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB
Click to expand...
Click to collapse
Thanks! I ended up having to use the 11.41.87.2 recovery in order to flash a Nougat update - it wouldn't work with the older recoveries.