Related
Has anyone else had an issue where the Samsung Camera App won't focus on Stock (Samsung) Roms? I don't have the problem with AOSP Roms...which is sooooooooooooo weird. Doesn't make any sense to me. I have tried NSeven Rom, Stock Rooted Rom (no mods), MODest Rom...they all have the same issue. However, the issue doesn't exist on LineageOS, EmotionOS, and I am sure it wont be a problem in Resurrection Rom either (haven't tried yet). I have tried to install a 3rd party Camera app and it does the same thing. Blurry and Wont Focus.
Balian67 said:
Has anyone else had an issue where the Samsung Camera App won't focus on Stock (Samsung) Roms? I don't have the problem with AOSP Roms...which is sooooooooooooo weird. Doesn't make any sense to me. I have tried NSeven Rom, Stock Rooted Rom (no mods), MODest Rom...they all have the same issue. However, the issue doesn't exist on LineageOS, EmotionOS, and I am sure it wont be a problem in Resurrection Rom either (haven't tried yet). I have tried to install a 3rd party Camera app and it does the same thing. Blurry and Wont Focus.
Click to expand...
Click to collapse
I've heard of kernels effecting camera before. What stock ROM are you on? And did you flash a custom kernel with it? If so, that might have something to do with it.
dhplap said:
I've heard of kernels effecting camera before. What stock ROM are you on? And did you flash a custom kernel with it? If so, that might have something to do with it.
Click to expand...
Click to collapse
I will just say that I started unmodded on the newest version released by Verizon (locked bootloader..etc). i did the rollback and unlocked the bootloader. Camera worked. EVERY TouchWiz Rom I flash has this issue. WITH the kernels included with the roms. I haven't flashed custom kernels yet. That is why I think this issue is weird. I just flashed Resurrection Rom which is AOSP and Camera focuses and works. I've never experienced this kind of weirdness before.
Balian67 said:
I will just say that I started unmodded on the newest version released by Verizon (locked bootloader..etc). i did the rollback and unlocked the bootloader. Camera worked. EVERY TouchWiz Rom I flash has this issue. WITH the kernels included with the roms. I haven't flashed custom kernels yet. That is why I think this issue is weird. I just flashed Resurrection Rom which is AOSP and Camera focuses and works. I've never experienced this kind of weirdness before.
Click to expand...
Click to collapse
So you're on the CPD1 bootloader?
dhplap said:
So you're on the CPD1 bootloader?
Click to expand...
Click to collapse
quite possible. When I boot into download mode it doesn't say. In settings/about phone it only shows baseband. Im sure there is a command but I am not sure what it is.
**EDIT** I found phone info on the playstore. I am on bootloader Version: N910VVRU2BPA1 PDA Version: N910VVRS2CQB2 Baseband Version: N910VVRS2CQC1
Balian67 said:
quite possible. When I boot into download mode it doesn't say. In settings/about phone it only shows baseband. Im sure there is a command but I am not sure what it is.
**EDIT** I found phone info on the playstore. I am on bootloader Version: N910VVRU2BPA1 PDA Version: N910VVRS2CQB2 Baseband Version: N910VVRS2CQC1
Click to expand...
Click to collapse
That's probably the problem, you're still on the lollipop bootloader. You need to upgrade to the CPD1 bootloader and unlock it again from this page https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144 that hsbadr supplied for us. Since you're already unlocked on BPA1 you'll only need to do it one more time. In the instruction section you can start at the second step though. Just remember, after you flash the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 You're wifi won't work so you'll need to use data for rooting. After you complete all of the steps successfully you should be good to go and do another clean flash of the marshmallow ROM of your choice.
Just want to say I'm on PD1 with a stock rom and kernel and have had this same problem since I've gotten to Marshmellow last year. I've just kinda accepted it at this point.
dhplap said:
That's probably the problem, you're still on the lollipop bootloader. You need to upgrade to the CPD1 bootloader and unlock it again from this page https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144 that hsbadr supplied for us. Since you're already unlocked on BPA1 you'll only need to do it one more time. In the instruction section you can start at the second step though. Just remember, after you flash the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 You're wifi won't work so you'll need to use data for rooting. After you complete all of the steps successfully you should be good to go and do another clean flash of the marshmallow ROM of your choice.
Click to expand...
Click to collapse
I will keep this in mind. I am currently on Resurrection Rom and I have ZERO issues. I don't want to mess with it. When I start to mess with stuff is when I spend 12 hours fixing something that should have only taken an hour to do to begin with. As the comment below you said...he has the same camera issue on CPD1
bagery77 said:
Just want to say I'm on PD1 with a stock rom and kernel and have had this same problem since I've gotten to Marshmellow last year. I've just kinda accepted it at this point.
Click to expand...
Click to collapse
It is literally the most weird issue I have had....It's usually the AOSP camera that is crashing...or crappy pictures...but ever since unlocking the bootloader the camera got blurry. I don't get it. Resurrection Rom has been killin it for me though. I love it. I might stay on it forever.
Balian67 said:
It is literally the most weird issue I have had....It's usually the AOSP camera that is crashing...or crappy pictures...but ever since unlocking the bootloader the camera got blurry. I don't get it. Resurrection Rom has been killin it for me though. I love it. I might stay on it forever.
Click to expand...
Click to collapse
I don't like shopping around too much these days. But the focus problem does clear up after several seconds. Always. So that's made it tolerable for me.
bagery77 said:
I don't like shopping around too much these days. But the focus problem does clear up after several seconds. Always. So that's made it tolerable for me.
Click to expand...
Click to collapse
It never cleared for me. I have sat on the camera for a minute tapping to focus...waiting...etc
Balian67 said:
It never cleared for me. I have sat on the camera for a minute tapping to focus...waiting...etc
Click to expand...
Click to collapse
Hmm, maybe Redemption/AOSP is your best bet. I just know it sucks to not have options still. Perhaps someone will pipe in with the magical fix. Good luck
I do agree with dhplap, you need to be on the Marshmellow bootloader if you're flashing stock Marshmellow roms. I can't remember all the stuff it breaks not having it, but I recall quite a few posts stating issues that were fixed by rerooting and updating the bootloader. Until they did that, they remained limited. AOSP Marshmellow seemed to work for them for some reason, however stock/Touchwiz "Marshmellow" broke stuff. Since you're on Lollipop bootloader, a stock Lollipop rom may remedy the camera issue for you.
bagery77 said:
Hmm, maybe Redemption/AOSP is your best bet. I just know it sucks to not have options still. Perhaps someone will pipe in with the magical fix. Good luck
I do agree with dhplap, you need to be on the Marshmellow bootloader if you're flashing stock Marshmellow roms. I can't remember all the stuff it breaks not having it, but I recall quite a few posts stating issues that were fixed by rerooting and updating the bootloader. Until they did that, they remained limited. AOSP Marshmellow seemed to work for them for some reason, however stock/Touchwiz "Marshmellow" broke stuff. Since you're on Lollipop bootloader, a stock Lollipop rom may remedy the camera issue for you.
Click to expand...
Click to collapse
I am so busy lol. I have 2 Sprint Note 4's that I am trying to root and I ran into ODIN/USB Driver issues. MAYBE I will worry about this next weekend haha. I will keep all this in mind. I will keep this post till then.
Thanks everyone.
I wanted to report that after I did all that stuff yall said, I restored my MODest Rom backup and the camera is now focusing. Maybe that will fix all the other issues with the other roms I tried using. I appreciate it Gents.
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
I have the same problem. I can't even downgrade
New version 22.0.0.0 and no signal bug. Omfg
Having trouble since open beta 1 in receiving and placing calls, crazy what 1+ is releasing
12 sounds is shaky at best
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
I'm still hoping they will release 12.0.0.1 this night
Jomsha said:
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
Click to expand...
Click to collapse
Same issues here
Indian version
Eslam.hanafy said:
Same issues here
Indian version
Click to expand...
Click to collapse
Ob2 did that already. No sim if 5g is turned on..Gonna root later, no big deal
Jomsha said:
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
Click to expand...
Click to collapse
try this method i posted in a thread, and let me know..
OOS 12.0.0 Stable Update Cellular Network Fix
Hi, As you may know most of us is having this issue after the OOS 12.0.0 Stable Update, Cellular Network lost, No Signal, Outgoing call, and SMS. The below method worked at least for me, let me know if worked with anyone of you please. Please...
forum.xda-developers.com
h8Aramex said:
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
Click to expand...
Click to collapse
How did you get into edl mode running A12?
My network doesn't work on OOS12 stable for some reason. I spent 2 days flashing different oos12 builds (eu, global, indian) to try to see if the network comes back, tried literally everything but no luck
Very disappointed. Had to come back to OOS11. Everything works perfectly, except the fact that I'm not running the latest android version on my flagship 9 Pro.
Read my post here. And back through a few others.
jruizdesign said:
I was getting the same issue, but flashing a different variant of your current c.44 should do the trick.
Ex: I have a LE2127 (TMO), I converted with a11 to use LE2123(EU) software updates. When android 12 hit my phone wouldn't give me data on the 2123 update, so I had to download the LE2125(global/NA) update and flash using the the system update app that was so generously given in the following post:
Post in thread '[TMO] 9 PRO MODEM RETENTION' https://forum.xda-developers.com/t/tmo-9-pro-modem-retention.4292445/post-86328243
I don't know what software or model your phone is now, so I am NOT suggesting you switch if you are not already on 2123 or 2125. Those two are interchangeable without problem so it should be fine
Click to expand...
Click to collapse
I don't know anything about the Indian variant so I'm not sure if the same fixed will work.
But I can tell you I have tried every msm tool and almost every possible variant an no matter what goes wrong there has been a fix here in the these forums already.
Currently running lastest c.44 global LE2125 A12 on my TMo LE2127 model device with ZERO bugs so far. Data works flawlessly
khanboy619 said:
My network doesn't work on OOS12 stable for some reason. I spent 2 days flashing different oos12 builds (eu, global, indian) to try to see if the network comes back, tried literally everything but no luck
Very disappointed. Had to come back to OOS11. Everything works perfectly, except the fact that I'm not running the latest android version on my flagship 9 Pro.
Click to expand...
Click to collapse
Did you read the data retention thread and msm using the given tool in that thread ONLY? If you use that msm tool, the take the local update to 11.2.9.9 then update the your variant of C44 you should have no issues.
jruizdesign said:
Did you read the data retention thread and msm using the given tool in that thread ONLY? If you use that msm tool, the take the local update to 11.2.9.9 then update the your variant of C44 you should have no issues.
Click to expand...
Click to collapse
Are you sure about this?? Because I flashed OOS12 by first flashing OS 11.2.8.8 through MSM tool and then updating to android 12.
Do you think flashing 11.2.9.9 will actually work, because I'll have to through the hastle of downgrading and then updating again. (As I'm running 11.2.10.10 atm)
The help is much appreciated.
h8Aramex said:
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
Click to expand...
Click to collapse
The easiest way to crashdump after this update is trying to flash your modem files like you would of you of on a11.
jruizdesign said:
The easiest way to crashdump after this update is trying to flash your modem files like you would of you of on a11. Easy fix with msm to stock and try again
Click to expand...
Click to collapse
khanboy619 said:
Are you sure about this?? Because I flashed OOS12 by first flashing OS 11.2.8.8 through MSM tool and then updating to android 12.
Do you think flashing 11.2.9.9 will actually work, because I'll have to through the hastle of downgrading and then updating again. (As I'm running 11.2.10.10 atm)
The help is much appreciated.
Click to expand...
Click to collapse
No 11.2.10.10 you get the same result no need to downgrade.
Amd4life said:
How did you get into edl mode running A12?
Click to expand...
Click to collapse
Same way you would in android 11.
Make sure the phone is completely off. Hold volume up and volume down buttons, and plug it in.
Make sure you already have the msm tool fully opened and ready to click enum.
As soon as you plug it in it should say ok ok in the tool, click enum then start.
I stress that point to do it quickly because it will fail with different errors if it's not done quick enough after the device is plugged in.
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Fatmonk8 said:
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Click to expand...
Click to collapse
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
TheKnux said:
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
Click to expand...
Click to collapse
To de-bloat.
But if that's the only positive this go around then it's probably not worth me doing since I have been de-bloating more with ADB lately. But if others have any input on other benefits then I may do it again.
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
TheKnux said:
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
Click to expand...
Click to collapse
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Fatmonk8 said:
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Click to expand...
Click to collapse
So I spent a week figuring this out. I realized a few days ago that I mistakenly flashed the Indian firmware for the OnePlus 9 PRO. I have the regular 9. I tried to flash every other msm I could find and download. Nothing seems to work except the Indian OnePlus 9 PRO msm... Problem is, the camera, flash and fingerprint scanner didn't work. I was able to toggle the unlock oem button by running an adb command line then I did oem unlock in fastboot. After that, I followed the instructions for installing StagOs 12.1, which involves installing lineage recovery then flashed the rom. Everything works flawlessly! Love this rom.
Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.
Which phone version do you have?
luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.
skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing
I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!
TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,
I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.
Just checked Asus website of Rog6 support. I'll be downloading it but before I have to back up my data, in case anything goes wrong. Anyone already on 13?
fux1976 said:
Just checked Asus website of Rog6 support. I'll be downloading it but before I have to back up my data, in case anything goes wrong. Anyone already on 13?
Click to expand...
Click to collapse
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13
mind if you share how you downgraded your phone to .197?
Thanos88 said:
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13
Click to expand...
Click to collapse
I also updated to Android 13 Version: 33.0610.2810.72.
Thanos88 said:
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13
Click to expand...
Click to collapse
To be honest with Rog2 was much easier. I can't figure out what's the problem with Android Auto (crashes) but voice typing started working magically on its own. Never had problems with hardware luckily.
Today I'll upgrade and let you know the result. Fingers crossed!
amit.akm said:
I also updated to Android 13 Version: 33.0610.2810.72.
Click to expand...
Click to collapse
Is everything working fine? Did you update on top or factory reset?
Redlith said:
mind if you share how you downgraded your phone to .197?
Click to expand...
Click to collapse
You need to flash raw firmware via fastboot
Thanos88 said:
You need to flash raw firmware
Click to expand...
Click to collapse
did the bootloader unlocked and be able to receive firmware update?
Redlith said:
did the bootloader unlocked and be able to receive firmware update?
Click to expand...
Click to collapse
Hi, I updated to android 13. It's very very good !!! I didn't even have to do factory reset, everything works great. Phone feels more smoother. Very good update.
No you don't need bootloader unlocked for raw flash
Thanos88 said:
Hi, I updated to android 13. It's very very good !!! I didn't even have to do factory reset, everything works great. Phone feels more smoother. Very good update.
No you don't need bootloader unlocked for raw flle
Click to expand...
Click to collapse
any new features you've noticed?
i mean, does flashing raw file unlocked the bootloader?
Redlith said:
any new features you've noticed?
i mean, does flashing raw file unlocked the bootloader?
Click to expand...
Click to collapse
Just some UI changes, nothing visually changed but phone feels more snappy & Overall much better. All the bugs I had on .197 have been fixed. It's a excellent update.
No it doesn't unlock bootloader
Thanos88 said:
Just some UI changes, nothing visually changed but phone feels more snappy & Overall much better. All the bugs I had on .197 have been fixed. It's a excellent update.
No it doesn't unlock bootloader
Click to expand...
Click to collapse
Just updated: wow! It seems like a new phone! Snappier, visual and settings improvement. Updated on top, no factory reset. For one time it went flawlessly. I applied Magisk before rebooting ("after OTA"). Perfect!
Thanos88 said:
Hi, I updated to android 13. It's very very good !!! I didn't even have to do factory reset, everything works great. Phone feels more smoother. Very good update.
No you don't need bootloader unlocked for raw flash
Click to expand...
Click to collapse
Thanks for providing your feedback, I'll update in a bit...
Pete450 said:
Thanks for providing your feedback, I'll update tonight.
Click to expand...
Click to collapse
Sorry for double-posting, but just following up - I updated from WW-32.2810.2210.220 (skipping WW-32.2810.2212.241) to WW-33.0610.2810.72, and can confirm it to be working without data wipe.
Also, it resolved the sound issue, where after placing/receiving a call, the bottom speaker would be much louder than the top speaker during any media audio.
Hello
I have a rog 6d ultimate i just download Android 13 update from asus
UL-ASUS_AI2203-ASUS-33.0404.1203.63-1.1.1-2301-user.zip
I put it on root restart my phone ,update showed up but fail to update.what should i do ?!
My phon not rooted but bootloader is unlocked is that matter ?!
My phone is ww
havard20009 said:
Hello
I have a rog 6d ultimate i just download Android 13 update from asus
UL-ASUS_AI2203-ASUS-33.0404.1203.63-1.1.1-2301-user.zip
I put it on root restart my phone ,update showed up but fail to update.what should i do ?!
My phon not rooted but bootloader is unlocked is that matter ?!
My phone is ww
Click to expand...
Click to collapse
Possibly bootlader, not sure. My bootloader has always been locked
Thanos88 said:
Possibly bootlader, not sure. My bootloader has always been locked
Click to expand...
Click to collapse
What should i do ?!
Can i lock it again?!
After update can i unlock it again ?!
How about update raw file ?!
havard20009 said:
What should i do ?!
Can i lock it again?!
After update can i unlock it again ?!
How about update raw file ?!
Click to expand...
Click to collapse
You should lock it and try the update again. I don't know if you can unlock it after updating, haven't tried myself
hi every one i need help about update to a13 wthout ota and how to creat backup
and how to check if bootloader are locked or no
Thanos88 said:
Better late than never. I'm still on the .197 update, the updates after that ruined my top speaker, it stopped working, so I downgraded back to .197. no idea what A13 will do, it's just so much hassle downgrading and having to set the phone up again. Would be good to get your feedback on A13
Click to expand...
Click to collapse
Hey bro, I just bought a ROG 6, I'm gonna manually update the phone, my cuestion is, wich firmware version is the best? (Already on 134) I don´t mind if isn't the lastest version, I just want to know wich is the most stable/recommendable version, you said the 197 is a stable one, I think the 241 should work great because is the last android 12 update, can you confirm? Do you recomend the lastest android 13 version? (WW-33.0610.2810.81) Or, in your experience wich is the most recommendable one?
Sorry for so many cuestions
Thanks