I'm currently on MTC20F rooted with TWRP and was wondering if there's anything different to upgrading to Nougat? I usually download the stock image from https://developers.google.com/android/nexus/images and remove the '-w' in the flashall.sh and run it. But since i'm going from 6 to 7 i'm wondering if there's anything special I need to do? Has anyone had any major issues with it and should I wait to upgrade or anything? Thanks!
jkingaround said:
I'm currently on MTC20F rooted with TWRP and was wondering if there's anything different to upgrading to Nougat? I usually download the stock image from https://developers.google.com/android/nexus/images and remove the '-w' in the flashall.sh and run it. But since i'm going from 6 to 7 i'm wondering if there's anything special I need to do? Has anyone had any major issues with it and should I wait to upgrade or anything? Thanks!
Click to expand...
Click to collapse
just use this HowTo and go through section 9, thats it. of course, it also works for upgrading from MM to N.
ulxerker said:
just use this HowTo and go through section 9, thats it. of course, it also works for upgrading from MM to N.
Click to expand...
Click to collapse
alright thats the way i'm doing it right now. so no different than a security update. any reason not to upgrade now?
jkingaround said:
alright thats the way i'm doing it right now. so no different than a security update. any reason not to upgrade now?
Click to expand...
Click to collapse
no, attack!
Related
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Here is what I did from stock 5.1.1 on a rooted verizon Note 4 (Using PaulPizz MMB29M.N910VVRS2CQB2):
Using Oden I installed:
VRS2CQB2_modems.tar.md5
VRS2CQB2_Bootloaders_NoAboot.tar.md5 and
VRS2CQB2_NoAboot.tar.md5
The phone boots into 6.0.1 (Kernel 3.10.40) and I have access to TWRP, ADB, ODIN, and root.
Paul suggested "You need to update your aboot partition to 6.0.1. the wifi driver is in the new aboot"
I am a noob and I don't understand what this means. Can anybody give me a list of steps to follow? I think I might be in over my head and returning to stock 6.0.1 might be acceptable.
Old Dude said:
Here is what I did from stock 5.1.1 on a rooted verizon Note 4 (Using PaulPizz MMB29M.N910VVRS2CQB2):
Using Oden I installed:
VRS2CQB2_modems.tar.md5
VRS2CQB2_Bootloaders_NoAboot.tar.md5 and
VRS2CQB2_NoAboot.tar.md5
The phone boots into 6.0.1 (Kernel 3.10.40) and I have access to TWRP, ADB, ODIN, and root.
Paul suggested "You need to update your aboot partition to 6.0.1. the wifi driver is in the new aboot"
I am a noob and I don't understand what this means. Can anybody give me a list of steps to follow? I think I might be in over my head and returning to stock 6.0.1 might be acceptable.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
dhplap, I appreciate the link to a different process but there seems to be too much assumed knowledge for me to try again (like what am I supposed to do with a .7z file). I am afraid I'm gonna brick the phone. I have flashed back to stock 5.1.1 (BPA1), verified the WiFi was working again and then flashed the stock CQC1 ROM from SamMobile. I really just wanted to get the latest security patches and have found a way to do that. My CID is still 150100523231384d4100657e54fc1200 which may be helpful in the future.
I am done for now with custom ROMs. I may take another swing at it when I have more time to educate myself. You may close this thread. My sincere thanks for your help.
Old Dude said:
dhplap, I appreciate the link to a different process but there seems to be too much assumed knowledge for me to try again (like what am I supposed to do with a .7z file). I am afraid I'm gonna brick the phone. I have flashed back to stock 5.1.1 (BPA1), verified the WiFi was working again and then flashed the stock CQC1 ROM from SamMobile. I really just wanted to get the latest security patches and have found a way to do that. My CID is still 150100523231384d4100657e54fc1200 which may be helpful in the future.
I am done for now with custom ROMs. I may take another swing at it when I have more time to educate myself. You may close this thread. My sincere thanks for your help.
Click to expand...
Click to collapse
You need to either flash the stock mm or lp rom you lost your WiFi do to the fact that your device while I'm certain it says 6.0.1 is in all reality 5.1.1 with the toolchain updated to mm . If you want a stock system with working radio Odin the stock firmware either api works
mojoswagger1980 said:
You need to either flash the stock mm or lp rom you lost your WiFi do to the fact that your device while I'm certain it says 6.0.1 is in all reality 5.1.1 with the toolchain updated to mm . If you want a stock system with working radio Odin the stock firmware either api works
Click to expand...
Click to collapse
He did flash stock mm. It was the last thing he flashed according to his list. He needs to upgrade his bootloader to mm.
dhplap said:
He did flash stock mm. It was the last thing he flashed according to his list. He needs to upgrade his bootloader to mm.
Click to expand...
Click to collapse
What ? Your High champ he said he flashed w/o aboot. That's the safe upgrade if he had flashed stock the bl would have updated itself
mojoswagger1980 said:
What ? Your High champ he said he flashed w/o aboot. That's the safe upgrade if he had flashed stock the bl would have updated itself
Click to expand...
Click to collapse
First of all your wasted. If he flashes stock mm he will lose root and lock his bootloader again and have to go back to bpa1 and start all over. Hence upgrade bootloader. Or he could stay on lollipop.
dhplap said:
First of all your wasted. If he flashes stock mm he will lose root and lock his bootloader again and have to go back to bpa1 and start all over. Hence upgrade bootloader. Or he could stay on lollipop.
Click to expand...
Click to collapse
He did lose root bud he wants to. If u followed the thread to this point u would know that. You read the first and last post and your responses show that .
mojoswagger1980 said:
He did lose root bud he wants to. If u followed the thread to this point u would know that. You read the first and last post and your responses show that .
Click to expand...
Click to collapse
I guess we both missed that he already flashed the stock bpa1 already. I just went off of you telling him to flash stock after he said he already did it. Have a good day bud!
dhplap said:
I guess we both missed that he already flashed the stock bpa1 already. I just went off of you telling him to flash stock after he said he already did it. Have a good day bud!
Click to expand...
Click to collapse
No u missed it . I was telling him the radio is in the bl he didn't flash . IDK what u we're suggest but at least don't actlike this is mutual in any way . We Aren't disagreeing on Minor details.
mojoswagger1980 said:
No u missed it . I was telling him the radio is in the bl he didn't flash . IDK what u we're suggest but at least don't actlike this is mutual in any way . We Aren't disagreeing on Minor details.
Click to expand...
Click to collapse
That's for sure. Read the second post buddy. That's what he needed to do to update his bootloader and keep root if he wanted too, or he could have just flashed a lollipop rom. Understand or no? Sorry, can't play with you anymore right now, gotta go to work. I'll be back later though if you have any questions.
I am on 8.1 DP2 which is OPP6.171019.012, tried to install the official 8.1 OTA which is OPM1.171019.011 : obviously the latter is older that DP2, so now I am still on DP2.
Maybe I need to wait for the OTA for those that are on beta program?
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
skw5115 said:
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
Click to expand...
Click to collapse
I can confirm this, I have updated this way.
anyone has the OTA for those on DP2?
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Mikulec said:
I can confirm this, I have updated this way.
Click to expand...
Click to collapse
I'm assuming you already had an unlocked bootloader?
Mr Patchy Patch said:
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
Click to expand...
Click to collapse
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
oxman said:
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Click to expand...
Click to collapse
go to the website and unenroll.
imnuts said:
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Usually an OTA is made to go from one specific build to another. Which would make sense on why you can't do it that way. If you have the unlocked bootloader flashing the factory image for 8.1 can be done.
thegios said:
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Click to expand...
Click to collapse
If you have an unlocked bootloader, you can update now with the factory image. Otherwise wait until the OTA rolls or for beta users.
Sent from my Pixel 2 XL using Tapatalk
I just got the small ota to bump me from DP2 to final. So it's in the wild now. You can probably force the update at this point.
Like he said, I just got the official OTA bump yesterday to final. If you can't force it, it should come soon regardless.. This shows the December 5th patch.
hrkahn said:
I'm assuming you already had an unlocked bootloader?
Click to expand...
Click to collapse
yes
I have same problem with Nexus 5X.
Adb sideload breaks at 47%.
Now i can only wait, because i have the no-rpmb-bug.
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it
Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?
Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This
Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk
Sorry if this has been asked before (I couldn't find anything) but is it possible to upgrade a rooted 3aXL to Android 11? Or do I need to un-root, upgrade and try a fresh root on A11? Thanks.
boominski said:
Sorry if this has been asked before (I couldn't find anything) but is it possible to upgrade a rooted 3aXL to Android 11? Or do I need to un-root, upgrade and try a fresh root on A11? Thanks.
Click to expand...
Click to collapse
Download the full image for Android 11 then use either the flash-all.bat file (will do a factory format so beware) or adb sideload it.
Going to a new version of Android it's always recommended to factory format.
Either way you will need to re-root after using magisk canary
This is pretty much what I thought. So there's no way to keep root then :crying:
boominski said:
This is pretty much what I thought. So there's no way to keep root then :crying:
Click to expand...
Click to collapse
Cheer up @boominsko you act like you loose root permanently. After updating just do the patch boot.img thing. Make sure to use the latest Magisk Canary. Also make sure to switch to canary channel.
Haha! Yeah, it's not so bad. Just a bit of a pain in the backside to fiddle around with files and ADB etc. Oh well. Thanks for the advice though!
boominski said:
This is pretty much what I thought. So there's no way to keep root then :crying:
Click to expand...
Click to collapse
You have to redo root even after security patches every month. This is no different