Related
Hi guys, I'm on the international beta rom but it's quite outdated now and I'd like to get up to speed with the OTA's.
I download the full version for flashing in TWRP as i'm rooted but it asks for a password everytime.
Apparently I need to format the internal storage to get past this, but I don't want to lose all my apps and setup etc. Is there anyway to update without losing root and files etc?
Thank you in advance,
Andy
The beta is based on Android 7 Nougat, right? And the stable is currently still based on 6.0.1. If you mean you'd like to get back to the stable channel I think a clean flash is the only option. You might be able to restore your data via TWRP but I'm not sure if that's OK when downgrading from 7 to 6. Maybe someone else can confirm this.
I'd say the best option would be a fastboot clean flash of the full ROM and go from there. Then you can reflash TWRP.
thank you for your reply, but I'm not on nougat at the moment, I'm happy sticking to the beta channel but as I'm rooted I can't OTA update to newer beta version which would be nougat.
Cheers,
Andy
andypa1 said:
thank you for your reply, but I'm not on nougat at the moment, I'm happy sticking to the beta channel but as I'm rooted I can't OTA update to newer beta version which would be nougat.
Cheers,
Andy
Click to expand...
Click to collapse
In that case, follow the steps I mentioned but using the Beta Fastboot ROM using the Mi Flash tool. Make sure you select "flash_all_except_storage.bat" and you'll keep your data and apps during the process. Once the device is booted, just make sure not to root and you'll be able to OTA to new beta roms when they are released.
Here's a link to the full list of Fastboot flashable ROMs. You didn't mention whether you're on Helium or Hydrogen, so make sure to pick the correct ROM for your device.
Good luck!
1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ
nima0003 said:
1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ
Click to expand...
Click to collapse
Do you have update to 10.5.5.IN11AA ?
gaww said:
Do you have update to 10.5.5.IN11AA ?
Click to expand...
Click to collapse
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.
spotmark said:
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.
Click to expand...
Click to collapse
Just got the phone and it updated to .5, and late at night, .6 showed up. It installed without all the trouble with TMo 7.
It unrooted, and I used the .5 magisk patched.img above without any problems, but will use .6 when available.
Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.
dladz said:
Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.
Click to expand...
Click to collapse
Thanks. I didn't wipe and I don't use fingerprint.
gaww said:
Thanks. I didn't wipe and I don't use fingerprint.
Click to expand...
Click to collapse
Right ok, might want to check it if you ever do. Just in case
Will this work on the Verizon compatible phone?
skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
If you're using an unlocked 8 Pro, sure. If you're using an 8, purchased directly from Verizon, no.
skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
Check your pms if you want to tinker with the Verizon model with
I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?
Ecna said:
I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?
Click to expand...
Click to collapse
No - don't use old one. If you search, you should find 10.5.10 boot image.
Thanks, I couldn't find a new one so I downgraded to 5.9.
Ecna said:
Thanks, I couldn't find a new one so I downgraded to 5.9.
Click to expand...
Click to collapse
Now you can upgrade back to 5.10 and reinstall magisk before booting up the update. Works real easy.
^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!
Deckardmac said:
^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!
Click to expand...
Click to collapse
Don't make things complicated, update to 10.5.10, boot twrp, install magisk from the zip
^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.
Deckardmac said:
^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.
Click to expand...
Click to collapse
Use 20.4
^ Thanks guys. It worked flawlessly.
how to fix cts profile false on 10.5.10
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.....