Question how worried should I be about bricking my pixel 6 by not flashing Android 13 to both slots
I read that you can brick your device if you only flash 13 to one slot
Can someone post directions to flash 13 to slot b without messing up slot b
AS far as I know, when you do a system update it installs on the slot that is not currently in use. If you have installed the original A13 update, and then later installed the September update you have A13 in both slots.
If you've only upgraded to the original A13 update it would be hightly unlikely but technically possible to force your phone to try and boot on the older A12 slot, which could brick your phone.
Please someone correct me if I'm wrong.
poit said:
AS far as I know, when you do a system update it installs on the slot that is not currently in use. If you have installed the original A13 update, and then later installed the September update you have A13 in both slots.
If you've only upgraded to the original A13 update it would be hightly unlikely but technically possible to force your phone to try and boot on the older A12 slot, which could brick your phone.
Please someone correct me if I'm wrong.
Click to expand...
Click to collapse
From my understanding of the situation, you're not wrong.
This is why we put a sticky at the top of the forum.
poit said:
AS far as I know, when you do a system update it installs on the slot that is not currently in use. If you have installed the original A13 update, and then later installed the September update you have A13 in both slots.
Click to expand...
Click to collapse
More context needed: Factory system updates install to the currently active slot. OTA updates install to the currently inactive slot, then switch to that slot during reboot.
poit said:
If you've only upgraded to the original A13 update it would be hightly unlikely but technically possible to force your phone to try and boot on the older A12 slot, which could brick your phone.
Please someone correct me if I'm wrong.
Click to expand...
Click to collapse
Again...sticky. If the device bootloops for any reason, it will attempt to switch to the old slot.
All you have to do is sideload the A13 OTA again; the OTA always installs to whatever is the "other" slot.
Related
UPDATED TOPIC! 02.08.2017
ASUS has released the NEWEST Nougat Update for ZF3U:
Newest Release: Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
Previous Version: Version WW_14.1010.1705.49 Release Date: 21.06.2017
Here is the official Update for Manual Install. DIRECT from ASUS Servers. Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/UL-ASUS_A001-WW-14.1010.1706.50-user.zip
Via:
http://https://www.asus.com/Phone/ZenFone-3-Ultra-ZU680KL/HelpDesk_Download/
If the link is expired Get it from the Asus ZenFone 3 Ultra Support and Firmware Website under Drivers and Tools-ANDROID Section. It is for the WW Version:
UPDATE! :OTA Update Working ONLY with phones with LOCKED Bootloaders. The Manual Update will work with both LOCKED and UNLOCKED Bootloaders. I have tested the OTA Update and after I unlocked my ZF3U's bootloader, I can no longer get update notification (on my previous ZF3U-I am on my 2nd one). From what I have read, ASUS servers block any devices with unlocked bootloaders from accessing automatic system updates. My only option is to find a way to RELOCK the bootloader or use the Manual Update file.
Enjoy!
Changelog:
Android 7.0 Nougat comes with handful of features such as App Shortcuts, Multi Window support, restart setting to power menu, Launch the camera by pressing the power button twice, Image Keyboard support, 100 emoji added, GIF Support, Quick Reply via Notification, Notification Redesigned panel, Notifications prioritization, Enhanced Doze Mode, System UI Tuner, Customizable Quick Settings, Don Not Disturb, New Settings Panel Redesigned, Data Saver per App, seamless updates and New Emoji Support.
-----------------------------------------
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
ctorbaoglu said:
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
It may be because your Bootloader is unlocked. If it is you will not receive the update. My ZF3U's bootloader was locked when I received the update. However, when I unlocked the bootloader, rooted and then decided to wipe everything through TWRP to do a fresh install of everything to reinstall Android 7.0 the trouble started. Now, I cannot do firmware update using the system Update menu (notification of update availability is not there). This is because the bootloader is now unlocked and I don't know if it is possible to relock it. I guess I have to wait for the full manual package of Android 7 to become available or see if anyone can help me to relock the bootloader and then update from Android 6.0 original firmware. I was excited to be finally getting Android 7.0 but only managed to use it for 1 day. Oh well, you live and learn.:crying:
Click to expand...
Click to collapse
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
AWFRONT said:
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
Click to expand...
Click to collapse
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
doctahjeph said:
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
Click to expand...
Click to collapse
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
doctahjeph said:
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
Click to expand...
Click to collapse
I have tried your suggestion numerous times and;
-it appears that when I boot to Android M, I don't have any sound in calls, fingerprint and other issues fully remain.
-when I upgrade to Android N, then Iam able to hear call sounds but fingerprint scanner still does not register and other issues still remain.
I have a feeling that somewhere along the process my device has enabled some sort of encryption and this is preventing the device from enabling all the features. No matter how many times I install/reinstall/wipe using stock or TWRP no change.
Does anyome know how I could disable encryption either using some sort of google service or through root etc... In settings device reports that it is encrypted. Also when I first booted the device after firmware update encrypting device message was shown. Not sure whats going on with my device. Hope to find out/fix soon though.
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
AWFRONT said:
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Click to expand...
Click to collapse
???? Thank you!!!
ASUS has released the NEWEST Nougat Update for ZF3U.
Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, .
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
Once again, I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Never mind.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
Hey @AWFRONT How did u manage to go back from android 7 to 6 ...i recently updated my phone to nougat and want to go back to mm. Could u help me out I have unlocked bootloader
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
AWFRONT said:
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
Click to expand...
Click to collapse
all of this from twrp or stock recovery
If you have TWRP installed then apply from it, if not you can use the stock recovery of Android 6.0 as posted in one of the topics of ZF3U forum sections and flash it using custom recovery and then flash the appropriate firmware file of Android MM version 6.0 and on completion wipe cache, factory data and reboot.
Due to lack of developer support for this device, I do not recommend that you rollback the firmware. When my 1st device failed I realised that ASUS devices don't have the software fixability ease of Samsung devices so I am using my 2nd ZF3U in its original factory state. I love the device as it is and don't want to mess with it and root is no longer important to me.
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
gubbilo144 said:
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
Click to expand...
Click to collapse
mine is
Malam
anybody updated to WW-14.1010.1711.62 is it still 7.0 or 7.1.1
I have an Indian Unit Running 11.0.11.0.QFQMIXM
I recieved a new update around 34 mb which I cant install for some reason.
Sashi Sharma said:
I have an Indian Unit Running 11.0.11.0.QFQMIXM
I recieved a new update around 34 mb which I cant install for some reason.
Click to expand...
Click to collapse
Are you rooted or do you have twrp? If so it's normal.
Follow this guide and try to update https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
Phil_gloves said:
Are you rooted or do you have twrp? If so it's normal.
Follow this guide and try to update https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
Click to expand...
Click to collapse
I have not rooted my device, I did unlock the bootloader and flash twrp in slot A. I didnt understand the so lot system well and decided against rooting. Then I just set slot B as default and booted in the normal os and locked the bootloader once again.
I think the device is not updating because one of the slots has been tampered with. Do I have to flash the stock recovery on that slot to restore normal operation?
Hi.
I've bought a new Nord2 and I'm studying to have it rooted. A, maybe numb, question. On my OP 6 to update I download the whole packet (OP itself says root detected so the entire packet will be downloaded) then I update and installing Magisk on inactive slot I have the phone updated and rooted. Is this possible on Nord2? Frow what I've read it seems that only incremental update are released. Any tip before starting root? On my OP6 I don't have TWRP and I don't need it if it's not mandatory.
Thanks a lot
The oneplus nord 2 does not have a stock OS released officially by Oneplus yet, so as of right now, it is not possible to flash a stock OS. The only things we have access to are the incremental update.zips, and whatever images people are pulling right out of their own phones and uploading to others in the community. There's been a few rumours that Oneplus should be releasing full stock os soon, but I've seen no official newso n that front yet so I wouldn't hold your breath.
Secondly, the Oneplus Nord 2 does not have A/B partitions, so there is no inactive slot, so other methods of updating whilst rooted, that works on other AB partition devices does not work on the nord 2.
Thanks for your answer. I thought that A/B partition was standard from Android 9+. If not yes it's a problem... In this way every update requires to root the phone again...
Hey, I'm trying to downgrade my phone so I can use Lineage. I only have access to Linux and can't get Virtualbox to work, so I'm pretty sure MSM tool is out of the question. I've updated my phone to Oxygen 12, but Oxygen 11 is still in the other slot. I did try switching slots to get on Android 11, but it wouldn't boot, even after I cleared the userdata partition. Now that I think about it, would I even need to boot the device to install Lineage, or would I just need to have Android 11 installed and be able to use the bootloader with fastboot commands? Or if I would need to boot, how would I get Oxygen 11 fully working?
(Also, it's T-Mobile firmware, so I also can't downgrade with their official app)
You don't have A11 firmware anymore, which I guess is also why you can't boot stock A11 now. Updates can update more than what the A/B slots cover.
AndyYan said:
You don't have A11 firmware anymore, which I guess is also why you can't boot stock A11 now. Updates can update more than what the A/B slots cover.
Click to expand...
Click to collapse
you mean a11 just disappeared from the other slot? i could reflash it but i'm scared, i guess if everything is in separate slots then i can't mess up alot tho
androidloyal said:
you mean a11 just disappeared from the other slot? i could reflash it but i'm scared, i guess if everything is in separate slots then i can't mess up alot tho
Click to expand...
Click to collapse
Only some partitions remain, not enough to cover the "firmware" part. Just find a Windows PC to MSM with.
androidloyal said:
Hey, I'm trying to downgrade my phone so I can use Lineage. I only have access to Linux and can't get Virtualbox to work, so I'm pretty sure MSM tool is out of the question. I've updated my phone to Oxygen 12, but Oxygen 11 is still in the other slot. I did try switching slots to get on Android 11, but it wouldn't boot, even after I cleared the userdata partition. Now that I think about it, would I even need to boot the device to install Lineage, or would I just need to have Android 11 installed and be able to use the bootloader with fastboot commands? Or if I would need to boot, how would I get Oxygen 11 fully working?
(Also, it's T-Mobile firmware, so I also can't downgrade with their official app)
Click to expand...
Click to collapse
you should downgrade with the T-Mobile MSM tools. Note that your data will be wiped, so make sure you have a backup if you want one!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.