Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
I you have backup of efs partation of just restore that via twrp
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try?
characterdivide said:
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try
Click to expand...
Click to collapse
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
Try to flash this
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
characterdivide said:
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
Click to expand...
Click to collapse
Yes
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
Can you tell me what happened actually while updating? Did you successfully flashed new update in twrp or some else
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
So
characterdivide said:
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
Click to expand...
Click to collapse
Someone told me that after downloading incremental update package ROM Boots to twrp but failed to flash update and nothing happened he booted to old OS
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
characterdivide said:
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
Click to expand...
Click to collapse
So you have to flash old roms boot.img it will. Help to back everything
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Give me V10 stock image FOR DN 2101
And after flashing this will our TWRP avilable or Not agian?
Done
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Im having same issues as you could help me out what image did you use and how. Thanks in advance.
Related
As the heading says, I need help installing lollipop using TWRP, sideloading the .zip fails every time. Any suggestions, it would be nice to install this update as it doesn't seem to be coming as an OTA any time soon for me. Thanks.
Well, the OTA came in this morning and saved the day. I reflashed stock recovery just in case, so it wouldn't brick like my G3 did when I tried to install an OTA. I then rebooted after flahing stock and installed the update. All is well.
rjzmanz said:
Well, the OTA came in this morning and saved the day. I reflashed stock recovery just in case, so it wouldn't brick like my G3 did when I tried to install an OTA. I then rebooted after flahing stock and installed the update. All is well.
Click to expand...
Click to collapse
Glad you got it working, it would seem that you need stock recovery to flash the OTA as the TWRP recovery causes the ZIP's version check asserts to fail. So you wouldn't have bricked, it just wouldn't have installed for you.
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Is it rooted? Which recovery r u using? Twrp or stock?
Not rooted
itsmelutfor said:
Is it rooted? Which recovery r u using? Twrp or stock?
Click to expand...
Click to collapse
What have you already modded in the original installation? If your system was stock the update wouldn't fail. Please be more specific so people can help you. If you've kingrooted or flashed twrp, the update will fail...
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
prabhat.singh.836 said:
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
Click to expand...
Click to collapse
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
swatidixit710 said:
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Click to expand...
Click to collapse
deathaddder said:
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
Click to expand...
Click to collapse
I have tried wipe cache method and doesn't works at all if you have rooted your phone and unrooted back.
And the OTA should work even with unlocked bootloader, if you have not rooted your phone before.
If you want to lock your bootloader again, just follow these steps,
1. Goto Settings -> Developer options
2. OEM unlocking -> turn it off
Error in installation of OxygenOS2.2.1
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Ankit_Lal said:
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Click to expand...
Click to collapse
Did you try to flash the full rom zip here?
http://downloads.oneplus.net/2016-04-20/opx/OnePlus_X_OxygenOS_2.2.1-X/
Cannot update to Oxygen OS 2.2.1
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Ankit_Lal said:
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Click to expand...
Click to collapse
I have the same problem. Brand new phone, out of box, Oxygen version 2.1.0.
Hi, I saw about the quad rooter issue, and today I checked the ota update. (I never had an ota update because I always been rooted, s3, s5 and g5)
But now it purpose the 10d update. (450mo)
I'm 10c h850 rooted.
Should I make this update?
Will I lose root? (Rooted via twrp super su)
If I have to re install everything (apps, datas, root), maybe should I wait for 7 nougat don't you think?
Thanks.
trotirider said:
Hi, I saw about the quad rooter issue, and today I checked the ota update. (I never had an ota update because I always been rooted, s3, s5 and g5)
But now it purpose the 10d update. (450mo)
I'm 10c h850 rooted.
Should I make this update?
Will I lose root? (Rooted via twrp super su)
If I have to re install everything (apps, datas, root), maybe should I wait for 7 nougat don't you think?
Thanks.
Click to expand...
Click to collapse
It won't install the update anyway with twrp installed. It'll just fail and reboot. Wait until your ROM devs rebase your ROM on the new base.
Thanks, it was stock rom. But yeah I don't think it's worth if I make a fresh install with android 7.
As you said I'm affraid about the bootloop issue.
trotirider said:
Thanks, it was stock rom. But yeah I don't think it's worth if I make a fresh install with android 7.
As you said I'm affraid about the bootloop issue.
Click to expand...
Click to collapse
Not bootloop, just because you have custom recovery installed the stock update process will not complete even on stock Rom, you'd need to wait for a flashable version of the update or you'd have to flash stock recovery back to your device first.
I just used LGUP without any issues. Pretty painless.
Then flashed TWRP again, and flashed my ROM of choice.
The only tricky part was quickly getting into TWRP after you flash TWRP. It reboots and if you're not quick enough, TWRP will be overridden by the stock recovery. Then you just need to repeat (flash TWRP again, get into TWRP and flash ROM).
Hello everyone,
I'm trying to flash TWRP because I want to make a backup of my phone, because I need to do a factory reset. And I need to do a factory reset because Wifi and Bluetooth aren't working...
So I installed the necessary driver for Windows 10, downloaded TWRP and when I flash it with Flash Tool, I actually get the message saying "Download OK"...but in reality, my phone doesn't boot at all. So I have to do this thing where you unplug your battery and flash it again (I don't flash a full ROM, just click on Download again while the Scatter file for TWRP is still selected). This is what happens every time I tried to install TWRP. On top of that, it seems like I have no recovery whatsoever now!
What am I doing wrong? I've already read from somebody in the thread for TWRP that he/she got it to work with CM13, so the issue can't be that I'm using CM13.
Do you really use TWRP for P9000 Lite or do you use TWRP for P9000 normal Version??
Nono, it's the Lite version.
This one https://forum.xda-developers.com/el...ent/recovery-twrp-3-0-2-1-p9000-lite-t3366126
The only other Version I can find is this:
http://www.needrom.com/download/p9000-lite-twrp-3-0-0/
I don't know if this helps you
Nope, that didn't work either.
Oh well...I've just flashed a Stock-ROM with a recovery that lets me flash CM13 again. I used Titanium to make backups of my apps. Wifi and Bluetooth still don't work but that doesn't belong in this thread.
Thank you though.
Fallout23 said:
Nope, that didn't work either.
Oh well...I've just flashed a Stock-ROM with a recovery that lets me flash CM13 again. I used Titanium to make backups of my apps. Wifi and Bluetooth still don't work but that doesn't belong in this thread.
Thank you though.
Click to expand...
Click to collapse
Flash twrp 3.0.2.6 for the p9000 lite it worked for me
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
The usual way can mean a lot, but most important, did you use Magisk 25.1?
Cheers
Tom
ne0ns4l4m4nder said:
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
Click to expand...
Click to collapse
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Lughnasadh said:
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Click to expand...
Click to collapse
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
AlkaDragos said:
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
Click to expand...
Click to collapse
In the past it has worked for some but not others. The key is to make sure you haven't made any modifications to any of the partitions. For example, if you are using a custom kernel it won't work unless you flash all the modified images back to stock beforehand.
Also make sure you patch your own boot image so there is a stock boot image backup Magisk can restore.