Related
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Same problem here
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.
A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.
A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.
A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least
Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.
Hey all,
Has anyone tried rooting the new OTA firmware B560? If so, can you post which versions of TWRP and SuperSU were used? And if you happen to have the links to the downloads that would be great too!
T.I.A.
Hi, for twrp I've used the version from this thread http://forum.xda-developers.com/showthread.php?t=3156779 for supersu used the version 2.62 from chainfire website. Installed twrp through fastboot, then in twrp installed supersu. I believe newer versions of supersu works too.
Stuck on Huawei Logo
Bonnie1977 said:
Hey all,
Has anyone tried rooting the new OTA firmware B560? If so, can you post which versions of TWRP and SuperSU were used? And if you happen to have the links to the downloads that would be great too!
T.I.A.
Click to expand...
Click to collapse
Okay so I flashed TWRP with no problem, then rebooted normally. Powered off and entered TWRP recovery to flash SuperSU. It installs fine but then when I reboot it just stays stuck on Huawei Logo.
Please help!
Bonnie1977 said:
Okay so I flashed TWRP with no problem, then rebooted normally. Powered off and entered TWRP recovery to flash SuperSU. It installs fine but then when I reboot it just stays stuck on Huawei Logo.
Please help!
Click to expand...
Click to collapse
i am quoting myself here
qkrusty said:
does anybody know which supersu root is working with this latest B560?
Click to expand...
Click to collapse
SuperSU_v2.64_Pro and BETA-SuperSU-v2.52
what i did after upgrading to B560 ( from rooted B522)and loosing root is, flash twrp ,boot into twrp then flash superSu 2.64 pro zip in twrp , rebooted the phone but there was no superSu icon , i then went and install superSu 2.52 beta apk , rebooted the phone , then i opened superSu , it automatically updated the binaries and voila
ps: i reflashed the B522 stock recovery before upating to B560 with a full rom zip from http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
edit : i used twrp from @somboons app ,it is twrp 2.8.7.0 here's the link http://forum.xda-developers.com/mate-7/development/tool-srk-tool-huawei-beta-02-20160501-t3369990
touns_j said:
i am quoting myself here
SuperSU_v2.64_Pro and BETA-SuperSU-v2.52
what i did after upgrading to B560 ( from rooted B522)and loosing root is, flash twrp ,boot into twrp then flash superSu 2.64 pro zip in twrp , rebooted the phone but there was no superSu icon , i then went and install superSu 2.52 beta apk , rebooted the phone , then i opened superSu , it automatically updated the binaries and voila
ps: i reflashed the B522 stock recovery before upating to B560 with a full rom zip from http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
Click to expand...
Click to collapse
My problem is I never make it past the Huawei Logo. So I have no idea if SuperSU actually installs. I have reflashed stock recovery for B560, but that still doesn't seem to help. The next step I'm going to take now is to reinstall the update package for B560 and then if I'm able to boot up I'll try your method. Wish me luck!
Bonnie1977 said:
My problem is I never make it past the Huawei Logo. So I have no idea if SuperSU actually installs. I have reflashed stock recovery for B560, but that still doesn't seem to help. The next step I'm going to take now is to reinstall the update package for B560 and then if I'm able to boot up I'll try your method. Wish me luck!
Click to expand...
Click to collapse
good luck mate , you will sort it out
ps: once you've manually flashed SuperSu , and click on reboot , Twrp will throw a message saying " you don't have root bla bla bla " , and offer to " root " , never accept that , ignore the request
touns_j said:
good luck mate , you will sort it out
ps: once you've manually flashed SuperSu , and click on reboot , Twrp will throw a message saying " you don't have root bla bla bla " , and offer to " root " , never accept that , ignore the request
Click to expand...
Click to collapse
actually I never got that message when I clicked on reboot. Can you tell me which TWRP version you used?
Bonnie1977 said:
actually I never got that message when I clicked on reboot. Can you tell me which TWRP version you used?
Click to expand...
Click to collapse
i used twrp from @somboons app ,it is twrp 2.8.7.0 here's the link http://forum.xda-developers.com/mate...60501-t3369990
I used TWRP 3.0.2.0 from the package that Churdy linked in the main thread with all the different versions of software.
mega:///#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ
I just had bricks from using genuine Chainfire SuperSU until I used the forum SuperSU Pro 2.64 which also comes with an unroot file.
mega:///#!0wITxJLR!S2iIVNjveSDMdne5QMNqd6so41vbTEK9tSJXJkOJJnw
I have not got Xposed to run properly yet though.
I'm freaking out!!! I can't get any USB debugging recognition, so I have no way of reinstalling the B560 firmware update. I have stock recovery now and my phone just keeps staying on the Huawei logo. Please somebody HELP!!!!
RobboW said:
I used TWRP 3.0.2.0 from the package that Churdy linked in the main thread with all the different versions of software.
mega:///#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ
I just had bricks from using genuine Chainfire SuperSU until I used the forum SuperSU Pro 2.64 which also comes with an unroot file.
mega:///#!0wITxJLR!S2iIVNjveSDMdne5QMNqd6so41vbTEK9tSJXJkOJJnw
I have not got Xposed to run properly yet though.
Click to expand...
Click to collapse
i use the above and it doesnt work. still no root eventhough it manage to install
i noticed during installation
it says
remounting system r/w
is this mean it fail to mount??
ok now this work.
before install supersu
go to mount menu and enable system mount
then only install supersu
--------------------
sorry to say i still cannot get full root. cannot go copy paste to system. it still read only. supersu not responding at all!!!?
i disable supersu ( the uncheck button) and exit. then launch again supersu, it update the binary successfully, and reboot. after reboot, i launch and re-enable supersu ( check button) then try to cut/past to system ...unfortunately unsuccessful
ahhl said:
i use the above and it doesnt work. still no root eventhough it manage to install
i noticed during installation
it says
remounting system r/w
is this mean it fail to mount??
ok now this work.
before install supersu
go to mount menu and enable system mount
then only install supersu
--------------------
sorry to say i still cannot get full root. cannot go copy paste to system. it still read only. supersu not responding at all!!!?
Click to expand...
Click to collapse
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
RobboW said:
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
Click to expand...
Click to collapse
i did try to wipe dalvik/cache but it freeze. luckily i able to reboot successfully
---------- Post added at 10:24 AM ---------- Previous post was at 10:12 AM ----------
RobboW said:
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
Click to expand...
Click to collapse
ok i go to phone manager and allow supersu to autolunch
now supersu works.
I just used the unroot zip and it worked. This is good as I can root, make changes then unroot.
Edit:
It seems removing root has allowed my file manager to still do root operations, possibly as it was already allowed root access prior to uninstalling SU. Other user apps cannot access root. I just put the Huawei Notepad app back into system/priv-app from backups folder in Storage. Permissions were ok without altering. All I needed was a wipe dalvik/cache in TWRP and reboot.
Unfortunately I reflashed the Stock Recovery and now I'm not able to do anything. I've tried adding the dload folder with the B560 update to reinstall the firmware, but it fails at 5%, with both the OTA update and the Full versions. I'm soooo scared that I have bricked my device. When I reboot into the stock recovery I get 3 options, Reboot System, Wipe data/factory reset and Wipe cache partition. And when I manually force it into fastboot/rescue mode the computer doesn't recognize the phone.
Please someone tell me that my device can be saved somehow! I don't know what else to do :*(
Bonnie1977 said:
Unfortunately I reflashed the Stock Recovery and now I'm not able to do anything. I've tried adding the dload folder with the B560 update to reinstall the firmware, but it fails at 5%, with both the OTA update and the Full versions. I'm soooo scared that I have bricked my device. When I reboot into the stock recovery I get 3 options, Reboot System, Wipe data/factory reset and Wipe cache partition. And when I manually force it into fastboot/rescue mode the computer doesn't recognize the phone.
Please someone tell me that my device can be saved somehow! I don't know what else to do :*(
Click to expand...
Click to collapse
Which stock recovery did you use though? It must be the right one to work.
I found a flash fail at 5% was when there is no update in the /System/dload folder if you're trying to force it to do OTA. I did that by accident. Thought I bricked it but it re-booted ok.
If you use the dload folder in SD card, Marshmallow prefers to kick off the update from the dialler app.
If you used the wrong recovery, maybe it will flash from SD ok with a different ROM but we need to know exactly what recovery you flashed to it. That controls partitioning which you probably messed up.
See if you can re-install a driver and see it with ADB somehow.
RobboW said:
Which stock recovery did you use though? It must be the right one to work.
I found a flash fail at 5% was when there is no update in the /System/dload folder if you're trying to force it to do OTA. I did that by accident. Thought I bricked it but it re-booted ok.
If you use the dload folder in SD card, Marshmallow prefers to kick off the update from the dialler app.
If you used the wrong recovery, maybe it will flash from SD ok with a different ROM.
Click to expand...
Click to collapse
I used this one... So it should have worked properly. How can I flash it from the SD card? I'm willing to try anything right now. Because I'm about to go crazy!
Bonnie1977 said:
I used this one... So it should have worked properly. How can I flash it from the SD card? I'm willing to try anything right now. Because I'm about to go crazy!
Click to expand...
Click to collapse
this recovery works fine from me , i extracted it from B560 update.app.. hmm try and give B522 recovery a try then , put the update.app file in the dload folder and put it on your sd card root folder, then flash the stock recovery using recovery mate7 mobopx v2.1 http://depositfiles.com/files/dkok9h43y then use the 3 buttons trick to force install the firmware
edit : when updating with the full update , you only put the update.app file in the dload folder, nothing else
touns_j said:
this recovery works fine from me , i extracted it from B560 update.app.. hmm try and give B522 recovery a try then , put the update.app file in the dload folder and put it on your sd card root folder, then flash the stock recovery using recovery mate7 mobopx v2.1 http://depositfiles.com/files/dkok9h43y then use the 3 buttons trick to force install the firmware
edit : when updating with the full update , you only put the update.app file in the dload folder, nothing else
Click to expand...
Click to collapse
Yesssss!!! I finally got it fixed... I added the full B522 update to my sd and forced the update and it WORKED!!! The B560's wouldn't but that one did... I don't understand why seeing that I had B560 when I tried rooting my device. I'm just glad that I have my phone back!! :good::laugh:
Bonnie1977 said:
Yesssss!!! I finally got it fixed... I added the full B522 update to my sd and forced the update and it WORKED!!! The B560's wouldn't but that one did... I don't understand why seeing that I had B560 when I tried rooting my device. I'm just glad that I have my phone back!! :good::laugh:
Click to expand...
Click to collapse
i'm glad it worked (i should probably remove that recovery though , maybe the file got corrupted while i was uploading it who knows , but it works fine for me )
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review
You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
memocatcher said:
You can install it via the update manager. But yes, you are going to lose twrp and root, which is not a problem at all since it took me only like 5 minutes to get it all working again.
I followed this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Thanks
dgunn said:
Don't do it. 5.1.8 will be released end of next week and you will be doing this all over again. I was going to myself but I'm waiting until the next release until someone pushes full writeup and review
Click to expand...
Click to collapse
Lol... And after that there will be a new build in another week...
The more updates, the better. We won't complain, do we? I'm glad, we don't suffer for updates like SAMEsung-users do.
Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Updating via twrp and then (before reboot) re flashing twrp.zip and magisk will grant you to maintain twrp and root
Manivannan9444 said:
hi guys i am on 5.1.6 oos rooted twrp installed now i want to update to 5.1.7 so can i update just like that in updater app or should i have to do any prerequisites
Click to expand...
Click to collapse
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either
Bradl79 said:
if u update through the OS like updater app or anything, u will have to re-flash twrp using the fastboot method, if you already have twrp installed then just update via twrp with full zip, install twrp installer zip, and then magisk (i usually reboot back to recovery after i install twrp installer then flash magisk). Then you are done, u do not lose anything and do no wipe anything either
Click to expand...
Click to collapse
Should i have to change slot after twrp flash of full rom
The easiest way is to download and install the update through the settings app then BEFORE you reboot open Magisk, click install then install to second slot.
No flash or worrying
sarthak kumar said:
Did you successfully do it? If yes please tell what procedure you followed.
Do I need to backup internal? Or my apps?
Thanks.
Click to expand...
Click to collapse
Download the ota.zip, reboot to TWRP, flash ota, flash TWRP.zip, reboot to OS, reboot to recovery again if you want magisk and install magisk zip. Done. No data loss or changing settings.
Hello, I'm still a noob trying to learn, so far with help of this forum I've learned to unlock and root my first android phone, now I'm trying to learn how to properly keep my device updated!
Can someone please give a little rundown to what are the correct steps to update OTA on a rooted twrp device?
I've been browsing the forums a lot but I seem to find a lot of different approaches, or too vague instructions.
It would be greatly appreciated if someone could help me out, step by step, and explain the steps with the commands I need to put in, if there are any.
Thank you
download the ota from here
place it on your phone
go to update on you phone then hit the cog and hit local update
let it up date
reboot to boot loader
fastboot twrp img again
then flash the installer
reboot recovery
then it will boot back in to recovery again
flash root
job done
Hello,
To save you having to fastboot boot TWRP, do the following:
Save the following files to your SDCard:
OTA.zip
Magisk.zip
TWRP.zip
Boot into TWRP
Flash OTA.zip first, then TWRP.zip straight after, then Magisk.zip straight after that, reboot.
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
Sorry yes, put the installer zip on the sdcard
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
audinak2 said:
@Swatto86 By twrp do you mean TWRP recovery or TWRP installer? I assume that you mean the installer
Click to expand...
Click to collapse
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
i just download and install the OTA through system updates. Then boot to Trwp recovery and flash magisk . Profit
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide
to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You can flash the installer zip for TWRP through TWRP itself.
Doesn't installing OTA through system settings wipe TWRP? That's why I perform all my updates from TWRP directly.
DampDeceiver said:
Thank you everyone for the quick replies,
What exactly is it to 'flash' the installer? Is it something I can do from the TWRP screen, just tap on it? Or will I have to put in command prompts?
I have followed this guide https://www.youtube.com/watch?v=Es80k627kTc to unlock/twrp/root, I have a TWRP recovery as far as I know, I'm not sure about 'installer'.
Thanks!
Click to expand...
Click to collapse
You have to do twrp/root again after updates. Unlock sticks, but twrp and root don't.
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Ajaykumar21066 said:
there must be something strange with me then , OTA update doesnt wipe my twrp , i just flash magisk after OTA
Click to expand...
Click to collapse
It prob doesn't overwrite until u reboot so twrp may not have been overwritten on that partition yet, so would make sense, I need to try it out sometime
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Swatto is correct. The risk when using twrp is that you must reboot to recovery immediately after flashing the twrp installer zip, or you will boot to the old slot and things will be broken. Rebooting to recovery gets you onto the active, updated slot.
When you reboot to recovery and flash an OTA, you are flashing it to the other slot. The current slot is untouched, while the new active one is completely stock. The twrp installer zip flashes twrp to both slots.
This is the procedure to follow if you want to update via twrp. Personally, I prefer taking the OTA and reinstalling via fastboot just to make sure everything is clean.
lollyjay said:
I have personally tested the following with TWRP already installed and twrp-installer-enchilada-3.2.1-0.zip on your phone:
Download full (not incremental) OOS ROM to your phone and check MD5
Reboot to your installed TWRP
Install the OOS ROM
Do not reboot instead stay in TWRP
Install twrp-installer-enchilada-3.2.1-0.zip
Reboot Recovery
Wipe cache
Reboot System
Click to expand...
Click to collapse
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Thank you
DampDeceiver said:
Alright everyone, thanks for all the replies. I have to say even with all your help things were still really confusing for me. I went ahead and ditched TWRP (since I don't really need it anyway), updated OTA through the system, reinstalled magisk before reboot on 2nd slot (the OTA option), and rebooted. And so far all seems fine, I'm on the latest OOS version and I'm still rooted, everything seems to work. Can I do this again in the future and completely overwrite my TWRP installation on my A slot?
I kinda went with TWRP as it's supposed to be more safe for noobs but it ended up making things a lot more difficult to manage.
Click to expand...
Click to collapse
I have not tried that method as I want twrp, but that is the recommended approach.
I know things have changed with twrp, but it's not that hard once you get used to it. You just have to remember that your phone will switch active slots every time it gets an update or you flash an ota (for example, to go back to stock), so twrp, etc, have to be installed on the other slot before you boot to it. Once you get comfortable with that idea, the rest of it is pretty easy.
Well, I am glad to read this post. Its always interesting how things can be slightly different in every phone manufacturer's setup.
After my lady Huawei device (Honor 6x), I did not want to have to deal with their style of... Control over their devices.
And things seem much easier here, while also being a little confusing right now. I don't fully get the slot a/b stuff yet but it sounds like it's a system to ensure stability on the phone in cases where the newest update could install incorrectly the alternative slot has a backup to ensure the device will function.
Sorta sounds like the dual bios setup on some motherboards. It's good!
Right, so to summarise to ensure I got it right:
1) Downloaded large (1gb+) ota zip from one of these threads, official twrp recovery installing zip, new version of magisk recovery installing zip
2) in recovery install all 3 of those zips in that listed order
3) reboot to recovery again to ensure twrp is still installed
4) profit
Which twrp thread should I take the zip from? There are a few different threads. I shouldn't care about the fastboot version when I already have twrp installed, right?
Either way, it can be much easier than what I had to do on Huawei phones. (currently the easiest phone I used for customisation like this was Nexus 4, but gladly OP6 is getting pretty close to that same level).
Sent from my OnePlus 6 using XDA Labs
You're best off downloading from the official twrp site. If you already have it installed, no need to use the fastboot boot method. You should to reboot to recovery in between flashing twrp and magisk to be sure magisk gets installed on the active slot.
Swatto86 said:
When you install OTA via system settings and reboot, the slot switches to the inactive one (where the OTA installed to) and boots. This means the previous slot (prior to reboot) still has TWRP installed.
You are probably going direct to recovery after the OTA install without doing a full reboot first.
Click to expand...
Click to collapse
Question, more of a scenario really. So if I'm on slot A and have TWRP and Magisk installed, would it be alright to just do a local update and reboot, giving me a perfectly clean install in slot B? Does it work that way? Thanks!
I'm actually using a 6t, but worst case scenario I just use the MSM Download tool, still I wanna get the hang of these confusing A/B devices.
I'm trying to update from 11.0.11.11 to 11.0.12.12 incremental update from oxygen updater and having this error:
"Fail on install system update" on 1% progress bar.
Try from system OTA and same error occur.
Somebody try and it work?
Thanks
just installed the same firmware without issue
jushhh said:
I'm trying to update from 11.0.11.11 to 11.0.12.12 incremental update from oxygen updater and having this error:
"Fail on install system update" on 1% progress bar.
Try from system OTA and same error occur.
Somebody try and it work?
Thanks
Click to expand...
Click to collapse
If you are rooted and/or have TWRP installed, then you need to restore the stock boot and/or recovery images before starting the update.
Then I will lose root access?
Not if you do it properly.
If you're using TWRP, then you'll have to restore the stock recovery.
If you're rooted then you can restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root.
Then download and install the incremental update manually. Then install Magisk to the inactive slot and reboot.
See https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-30#post-85801253
jushhh said:
Then I will lose root access?
Click to expand...
Click to collapse
1) Update software but DO NOT REBOOT
2) Open Magisk > tap install > tap Install to inactive slot > NOW reboot.
Make sure you disable any and all modules first. No need to uninstall, just disable them. Mainly just a precaution. Possibly remove security from the lockscreen too for good measure.
I lost root the other day actually forgetting to properly install Magisk before rebooting and now I have to buy a laptop just to root again.
BillGoss said:
Not if you do it properly.
If you're using TWRP, then you'll have to restore the stock recovery.
If you're rooted then you can restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root.
Then download and install the incremental update manually. Then install Magisk to the inactive slot and reboot.
See https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-30#post-85801253
Click to expand...
Click to collapse
Thanks @BillGoss, your instructions are perfect. Work like a charm.
Anyone have the stock firmware or stock image for 11.0.12.12.KB05AA? Trying to root it.
ClassickWORLD said:
Anyone have the stock firmware or stock image for 11.0.12.12.KB05AA? Trying to root it.
Click to expand...
Click to collapse
Use TWRP: https://forum.xda-developers.com/t/guide-rooting-oos-with-twrp.4327417/
since i did it manually and ended up with no boot.img backup from magisk, i had to manually extract boot.img from my last ota 11.0.11.11.KB05AA and reflash it through fastboot. then it let me update and i rerooted.
I get the notification but can't even try it because when i tap on it, it does nothing.
dazoe said:
I get the notification but can't even try it because when i tap on it, it does nothing.
Click to expand...
Click to collapse
I managed to install the update, I used oxygen updater to download the update, used restore images option in magisk, installed update (DID NOT REBOOT), used install to inactive slot in magisk, then rebooted.
Seems like it all went well.
BillGoss said:
If you are rooted and/or have TWRP installed, then you need to restore the stock boot and/or recovery images before starting the update.
Click to expand...
Click to collapse
Do I have root and twrp, what should I restore? Only recovery? If so, you have maybe some stock for 11.0.11.11 kb05ba? I don't know why, but I only have a copy of the boot.
e1thx said:
Do I have root and twrp, what should I restore? Only recovery? If so, you have maybe some stock for 11.0.11.11 kb05ba? I don't know why, but I only have a copy of the boot.
Click to expand...
Click to collapse
Use payload dumper to get a copy of the .11 recovery.
BillGoss said:
Use payload dumper to get a copy of the .11 recovery.
Click to expand...
Click to collapse
I have root and twrp, what should I restore? Only recovery? And then magic restore?
e1thx said:
I have root and twrp, what should I restore? Only recovery? And then magic restore?
Click to expand...
Click to collapse
Read Post #5.
BillGoss said:
Read Post #5.
Click to expand...
Click to collapse
I have read it, that's why I am asking.I need to recover two partitions? Or one
e1thx said:
I have read it, that's why I am asking.I need to recover two partitions? Or one
Click to expand...
Click to collapse
What don't you understand in post #5? You said you're rooted. So post #5 tells you what to do.
BillGoss said:
What don't you understand in post #5? You said you're rooted. So post #5 tells you what to do.
Click to expand...
Click to collapse
Sorry Bill, I get it all now. I just have to do as You wrote:
1) restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root
2) install update manually, System update>Gear icon (local upgrade)
3) install Magisk to the inactive slot and reboot
Last question, where or how to download update manually?
e1thx said:
Sorry Bill, I get it all now. I just have to do as You wrote:
1) restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root
2) install update manually, System update>Gear icon (local upgrade)
3) install Magisk to the inactive slot and reboot
Last question, where or how to download update manually?
Click to expand...
Click to collapse
Ah, well that's tricky if it's not available from OnePlus or the XDA rom thread. I believe Oxygen updater app will give you the rom also, but I've never used it.
Edit: just read your post again and I'm confused: what rom exactly are you looking for?
This thread is about ending up on 11.0.12.12.KB05AA
And if you're looking for that one you'll find it in https://forum.xda-developers.com/t/updates-thread.4188149/post-86165983