Hey guys,
after reverting to OOS11 from a custom Rom using msmtool, my camera and flashlight refuse to work.
To fix it, I tried manually flashing the stock boot.img (to remove any changes that a prior installation of magisk could have made).
When that didn't fix the issue, I tried installing LineageOS to see if the camera and flashlight would work there.
Surprisingly, both of them worked as expected, which led me to try and install stock oos11 again.
Unfortunately the problem came back as soon as I used msmtool to revert back.
Could anyone suggest a fix or point me in the right direction?
opose said:
Hey guys,
after reverting to OOS11 from a custom Rom using msmtool, my camera and flashlight refuse to work.
To fix it, I tried manually flashing the stock boot.img (to remove any changes that a prior installation of magisk could have made).
When that didn't fix the issue, I tried installing LineageOS to see if the camera and flashlight would work there.
Surprisingly, both of them worked as expected, which led me to try and install stock oos11 again.
Unfortunately the problem came back as soon as I used msmtool to revert back.
Could anyone suggest a fix or point me in the right direction?
Click to expand...
Click to collapse
Msm to oos10 then ota to latest
HueyT said:
Msm to oos10 then ota to latest
Click to expand...
Click to collapse
They are still not working after installing OOS 10.0.4 with msmtool and updating to 11.0.7.1 via ota
opose said:
They are still not working after installing OOS 10.0.4 with msmtool and updating to 11.0.7.1 via ota
Click to expand...
Click to collapse
Did it work on oos10 (before ota to 11)?
HueyT said:
Did it work on oos10 (before ota to 11)?
Click to expand...
Click to collapse
no, it didn't work with oos10.
I tried leezaal's fix for the issue, though that didn't work for me either.
What I found out:
- When on any custom rom, camera and flash work, but other sensors (gyroscope, compass, etc.) are not recognized
- On any OOS version, camera and flashlight don't work, but the other sensors do.
I think that maybe my persist partition has been corrupted by the downgrade (Android 12 to 11), which is the reason that msmtool doesn't fix the issue?
On the other hand, as far as I know, custom roms don't change the persist partition, so why do they fix my camera ?
I have the same problem after revert from ColorOS 12.1 beta1 . Do you find a solution?
apsolem said:
I have the same problem after revert from ColorOS 12.1 beta1 . Do you find a solution?
Click to expand...
Click to collapse
Didn't find one yet, but I think this thread may help you
Related
Hi all. New OP5T user here. Currently running on android 8.1 on PixelExperience ROM but planning on updating when the stable version of Pie gets released. Have a few questions:
- I've searched in the forum that updating to an open beta version of pie is as simple as wipe and flash for those on twrp when coming from previous android versions (such as 8.1). Does this mean I can do the same with the stable version and just flash Pie based ROMs afterwards?
- when I flashed a custom ROM which failed to boot, I tried to restore the nandroid backup of the stock rom but unfortunately, i was greeted with a black screen. Now Im scared to freely test out roms because of that failed nandroid backup. Did anything change in what specific partitions one has to back up? Ive always just backed up whatever partitions were checked by default in my Nexus 6p days and it always worked.
Did you already have 5.1.4 and 5.1.5? Check for project Treble. What I did to get the latest open beta without screwing up my phone is that I flashed through TWRP the latest stable release, then I flashed stock recovery so I can flash the latest Pie beta. After that you can choose to stay stock or flash twrp and magisk. Everything works fine. If you end up with a bricked phone and even recovery doesn't show there is a tool uploaded from 1+ customer service on this forum that can help you recover your phone! I tried and it worked!
Tehbro said:
Hi all. New OP5T user here. Currently running on android 8.1 on PixelExperience ROM but planning on updating when the stable version of Pie gets released. Have a few questions:
- I've searched in the forum that updating to an open beta version of pie is as simple as wipe and flash for those on twrp when coming from previous android versions (such as 8.1). Does this mean I can do the same with the stable version and just flash Pie based ROMs afterwards?
- when I flashed a custom ROM which failed to boot, I tried to restore the nandroid backup of the stock rom but unfortunately, i was greeted with a black screen. Now Im scared to freely test out roms because of that failed nandroid backup. Did anything change in what specific partitions one has to back up? Ive always just backed up whatever partitions were checked by default in my Nexus 6p days and it always worked.
Click to expand...
Click to collapse
To ensure no problems when updating, you must backup your apps and data with titanium backup or any other app that you like and do a complete wipe.
To ensure that all will work flawless, you must be sure that the last OOS that were installed in your phone was up to 5.1.4, flash de OOS 5.1.7 on TWRP after a factory reset, and then just update to 9.0.0 without any issues.
If your last OOS version was 5.1.4 or lower, you must flash the 5.1.4 in twrp and then the 5.1.7.
Or just use this, with this to flash 5.1.7
libnijunior said:
To ensure no problems when updating, you must backup your apps and data with titanium backup or any other app that you like and do a complete wipe.
To ensure that all will work flawless, you must be sure that the last OOS that were installed in your phone was up to 5.1.4, flash de OOS 5.1.7 on TWRP after a factory reset, and then just update to 9.0.0 without any issues.
If your last OOS version was 5.1.4 or lower, you must flash the 5.1.4 in twrp and then the 5.1.7.
Or just use this, with this to flash 5.1.7
Click to expand...
Click to collapse
Thanks. I was able to update OOS to 5.1.7 through OTA then flashed my current ROM. I was told i could just flash a custom PIE rom right away as I'm on the latest FW, yes?
Tehbro said:
Thanks. I was able to update OOS to 5.1.7 through OTA then flashed my current ROM. I was told i could just flash a custom PIE rom right away as I'm on the latest FW, yes?
Click to expand...
Click to collapse
For sure, now you can flash any pie ROM you want. (OOS Based)
For those that aren't based in OOS, depends from one to another, and now, as the official pie is recent, some are using old blobs ( from 5.1.7 and maybe have some incompatibilities with the new blobs)
libnijunior said:
For sure, now you can flash any pie ROM you want. (OOS Based)
For those that aren't based in OOS, depends from one to another, and now, as the official pie is recent, some are using old blobs ( from 5.1.7 and maybe have some incompatibilities with the new blobs)
Click to expand...
Click to collapse
Ah right. Does that mean its better to wait for non-OOS pie roms to be based on the latest official build? Sorry, but what are blobs?
Tehbro said:
Ah right. Does that mean its better to wait for non-OOS pie roms to be based on the latest official build? Sorry, but what are blobs?
Click to expand...
Click to collapse
Blobs are the things that ROMs are in the scratch, the device specific things. For now I think that all the mainstream ROMs already are based on the new OOS, but always is better to read all ROM specific thread to be sure.
Anyone can help me how to Rollback from BETA 3 to STABLE 10.0.9?
Obviously return error that stable is older than beta.
Thanks
Maybe flashing Fastboot rom will work without issues. But I didn't test it.
Of course you can't local update to 10.0.9 since it's old dated than OB3. You have to wait for a roll back zip.
Rolling back from a beta to a lower stable on the OP5 was just a case of booting into recovery and choosing the lower stable zip.
Have you tried from recovery ?
Basically the same procedure except your performing the rollback from recovery directly instead of the software system menu method.
Subscribing to thread. I find the actual phone service and signal strength is poor on Beta 3 and am anxious to get off of it.
Use msm tool
You can install the rollback package found on OB1 thread on OnePlus forums..it takes you back to 10.0.8 and can install update on top of that...
Anyone tried it yet with the ob1 rollback package? I just want to be sure before doing it. Thank!
Udzi said:
Anyone tried it yet with the ob1 rollback package? I just want to be sure before doing it. Thank!
Click to expand...
Click to collapse
I did and it worked fine...Install Rollback package from OB1 thread and install 10.0.9...Your data will be wiped though..
ram4ufriends said:
I did and it worked fine...Install Rollback package from OB1 thread and install 10.0.9...Your data will be wiped though..
Click to expand...
Click to collapse
Yes, I am aware of that, thank you for the clarification!
ram4ufriends said:
I did and it worked fine...Install Rollback package from OB1 thread and install 10.0.9...Your data will be wiped though..
Click to expand...
Click to collapse
That's why I said try it with Fastboot rom. You can easily edit the flash.bat file and flash without wipe. But I can't say if that works without issues.
can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
freddienuxx said:
can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
Click to expand...
Click to collapse
I'm also curious about this. My current method is to just use the MSM tool whenever I want to go back to stock but it is definitely time consuming. As far as I know TWRP is still early in development and a lot of things that should normally work dont work perfectly
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Haunt3r said:
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Click to expand...
Click to collapse
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
thirtythr33 said:
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
Click to expand...
Click to collapse
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Haunt3r said:
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Click to expand...
Click to collapse
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
thirtythr33 said:
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
Click to expand...
Click to collapse
there is no "full" update for 7.7aa it's solely an OTA
Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
yeah man there is, came out June 28th, check oxygen updater or oneplus software download.
lol either way I can't flash it so fml
Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
Yes there is, it came out a few days ago about 3gb's on OnePlus website...
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Haunt3r said:
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Click to expand...
Click to collapse
yeah man we have to wait insane long for AA full updates. yeah my issue is very frustrating and I've tried everything short of msm, I just don't see how it is possible that twrp reports I am missing those partitions yet my phone boots, but slot B is f'd, and I can't flash full AA update either through twrp or local upgrade.
Okay so if we do flash the full ota through recovery what's the correct process on this to keep twrp and magisk without needing a PC to push the recovery and root back onto the device?
Just downloaded full zip update for the OP9P Global vLE2125_11.C.44_1440_2022201182114
I have a question... I have 2123 not 2125. Previous i have c38 eu but now I just update to c40 global and next c44 thought the updater. I need to re root I need to install install the boot.img from global? In the info my device is still 2123
Nope. You are good
Poloasis said:
Just downloaded full zip update for the OP9P Global vLE2125_11.C.44_1440_2022201182114
Click to expand...
Click to collapse
I got that update as well. Is it Android 12 or still 11?
Thank you
netgar said:
I got that update as well. Is it Android 12 or still 11?
Thank you
Click to expand...
Click to collapse
12
Just installed it. Looks like gcam access to all cameras is restored.
Poloasis said:
12
Click to expand...
Click to collapse
Thank you. So I guess I can't just root as always.
Have you been able to root it?
I downloaded the update from oxygen updater.
OnePlus9ProOxygen_22.E.44_OTA_1440_all_2201182111_30de568cd.zip
I got the EU ver. When i update i wont stick. Still the same. What am i doing wrong?
alpadie said:
I downloaded the update from oxygen updater.
OnePlus9ProOxygen_22.E.44_OTA_1440_all_2201182111_30de568cd.zip
I got the EU ver. When i update i wont stick. Still the same. What am i doing wrong?
Click to expand...
Click to collapse
Have u download the full zip? Your devices is rooted? If yes u need to restore stock boot.img and next install the update
davyleggend said:
Have u download the full zip? Your devices is rooted? If yes u need to restore stock boot.img and next install the update
Click to expand...
Click to collapse
Yes the full zip. I have root. How do i restore boot.img? And I guess that means no more root. Do We have root for the new one?
alpadie said:
Yes the full zip. I have root. How do i restore boot.img? And I guess that means no more root. Do We have root for the new one?
Click to expand...
Click to collapse
Open magisk and uninstall next local upgrade. For re root i'm waiting because I don't know what boot.img i need to flash. Probably i make it by my self.
davyleggend said:
Open magisk and uninstall next local upgrade. For re root i'm waiting because I don't know what boot.img i need to flash. Probably i make it by my self.
Click to expand...
Click to collapse
Okej thanks for the info. I'l will wait for when we have root
Installed C.44 EU over C.38 EU using local update app, latest Magisk Alpha, and keep root using the Magisk OTA option before rebooting after the update.
No need to unroot to upgrade
i went from c.39 to c.40 the day before yesterday. i used mlgmxyysd's tool to flash c39's stock images to the device then updated through the updater.
found the flashed boot image, flashed it (just like the old way, fastboot flash boot.img).
i then installed c.44 ota, went to magisk, installed it to the inactive slot, rebooted, and it ran fine.
with magisk alpha, you don't need the toolbox anymore (i believe)
Anyone have problem with haptics on c44? Haptics feedback is just missing on some menu actions.
Looks like an issue with work profile. Work apps such as MS Teams forces closed and an 'IT doesn't allow multiple users' toast notification pops up. Dang!
Damn... I better stay with A11
I have notification of update to le2123 have not updated yet
Any users any issues with certain apps android auto, Spotify etc
Use phone for work and don't want to feck it up
funkyirishman said:
I have notification of update to le2123 have not updated yet
Any users any issues with certain apps android auto, Spotify etc
Use phone for work and don't want to feck it up
Click to expand...
Click to collapse
If you're using a work profile you're more than likely going to run into bother. I do and intune won't install company policy certificate in the work profile rendering it useless
hallo dare said:
If you're using a work profile you're more than likely going to run into bother. I do and intune won't install company policy certificate in the work profile rendering it useless
Click to expand...
Click to collapse
I don't have a work profile but use certain apps like ms authentication and rsa secure I'd to log in
Hello all!
I am an user of OnePlus 9 pro (T-mobile). I don't want the pink startup screen, and I found a lot of resources here can help me on it.
I have backup all my personal data. I have unlocked the sim and bootloader (using the official unlock_token.bin). What is the next step?
I am lost here since there are some different posts (and some posted last year, I am not sure if this still work or not).
Thank you all!
Flash a rom or custom oos
First off do not update to A12, make sure USB debug is enabled, auto updates disabled....do that and I hope you are on A11...if so, I have exactly what you need
FizzyAps said:
Flash a rom or custom oos
Click to expand...
Click to collapse
Any link for the rom?
TheGhost1951 said:
First off do not update to A12, make sure USB debug is enabled, auto updates disabled....do that and I hope you are on A11...if so, I have exactly what you need
Click to expand...
Click to collapse
I just unlocked the bootloader. It is now Android 11 with 05/01/2021 safety update. (11.2.4.4.LE5ACB). Could you please give the next step instruction?
run93 said:
I just unlocked the bootloader. It is now Android 11 with 05/01/2021 safety update. (11.2.4.4.LE5ACB). Could you please give the next step instruction?
Click to expand...
Click to collapse
Turned off auto updates? Yes? You can update to 11.2.9.9 then stop there, but make sure auto updates are turned off!!!!! Next step will to get root!
TheGhost1951 said:
Turned off auto updates? Yes? You can update to 11.2.9.9 then stop there, but make sure auto updates are turned off!!!!! Next step will to get root!
Click to expand...
Click to collapse
I would stay away from custom roms, I have seen too many people having problems. Secondly as of right now, A12 is buggy so that is why I stay with stock A11 from T-Mobile. With the setup I can give you, you can have any custom bootanimation and custom systemwide font you want.....
First off, download and install Magisk v25.2 app from GitHub website and install it to your phone. Next download the attached file to the folder with your platform files.....
Download Magisk from this link to your phone and install it.
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Then download this link to your platform tools folder on PC...
Download twrp-3.6.2_11-0-lemonadep.img
Download page for twrp-3.6.2_11-0-lemonadep.img
dl.twrp.me
Then download this link to your phone storage...
17.63 MB file on MEGA
mega.nz
Let me know when you are down with these three steps!!!!! And are you updated to 11.2.9.9
TheGhost1951 said:
Let me know when you are down with these three steps!!!!! And are you updated to 11.2.9.9
Click to expand...
Click to collapse
Yes. I have successfuly updated 11.2.9.9 now.
I have a question that would this work? https://forum.xda-developers.com/t/le2127-oneplus-9-pro-custom-rom-t-mobile.4490195/
I am interested in Android 12 or even 13 if possible.
run93 said:
Yes. I have successfuly updated 11.2.9.9 now.
I have a question that would this work? https://forum.xda-developers.com/t/le2127-oneplus-9-pro-custom-rom-t-mobile.4490195/
I am interested in Android 12 or even 13 if possible.
Click to expand...
Click to collapse
If you are focused on upgrading to A12 or A12 then what I have will not work. As for the custom ROM, possible it may work, but you need to follow the steps to the letter. Any OP9P custom ROM will work from the XDA forums, the question is, will there be issues? Very possible. Good luck on your journey.....
TheGhost1951 said:
I would stay away from custom roms, I have seen too many people having problems. Secondly as of right now, A12 is buggy so that is why I stay with stock A11 from T-Mobile. With the setup I can give you, you can have any custom bootanimation and custom systemwide font you want.....
Click to expand...
Click to collapse
Been running nameless for over a month and a half now and haven't had a single out-of-the-ordinary problem that can't be fixed with a simple reboot. I have the T-Mobile variant here. Data works fine.
TheGhost1951 said:
If you are focused on upgrading to A12 or A12 then what I have will not work. As for the custom ROM, possible it may work, but you need to follow the steps to the letter. Any OP9P custom ROM will work from the XDA forums, the question is, will there be issues? Very possible. Good luck on your journey.....
Click to expand...
Click to collapse
I understand about the concerns about custom ROM. I am confused that is there any official Global or EU ROM available ?
run93 said:
I understand about the concerns about custom ROM. I am confused that is there any official Global or EU ROM available ?
Click to expand...
Click to collapse
Stock.....but you need to be rooted, TWRP installed and then install the stock ROM zip in twrp.
TheGhost1951 said:
Stock.....but you need to be rooted, TWRP installed and then install the stock ROM zip in twrp.
Click to expand...
Click to collapse
Thank you for all the help today! I think I did something wrong. I successfully get TWRP (directly boot, not recovery since it is failed), and then get my phone bricked flashing the rom lineageos... Now I am trying to unbrick it...
run93 said:
Thank you for all the help today! I think I did something wrong. I successfully get TWRP (directly boot, not recovery since it is failed), and then get my phone bricked flashing the rom lineageos... Now I am trying to unbrick it...
Click to expand...
Click to collapse
Bricked as in black screen? Or does it boot to fastboot? What version of lineage are you trying to run? And what OOS were you on? You need to be on OOS 12 to run lineage 19. And twrp is not the recovery to use for that.
Look before you leap.....read read read and make sure to follow ALL steps 1step at a time.....