Related
Hi,
I am sadly no mobile expert and need your kind support. Since over half a year I have 2 problems
very frequent phone call interruptions
much lower battery life time
My phone/sim provider in Germany are Vodafone and Congstar. But I do not think its related to them.
All the trouble started after a certain upgrade to newer versions of Android OS, but can't remember when this exactly started. Then the battery life went down significantly and I get those annoying interruptions in phone calls up to 3-4 times in a ~15 minute call. Its so bad .. What could you recommend to me ?
Is there a better image downloadable, maybe fallback to older version ?
Or is it possible to fallback to the version in ROM ? I fear side effects and unfixed system holes by this.
Thanks for any help !
BR
Moin,
I highly recommend you to switch to CyanogenMod. I took the switch to CM right after i bought my GT-I9195 and all I can say I've never expirenced such problems either on Vodafone nor O2. ATM I'm still at CM11 as this is rock stable and battery life is quite good, ~2-3 days depending on usage
Just follow this steps and you've got nothing to worry about.
1. install custom recovery
2. take a full backup of your current system + SD Card just for the case...
3. install CM11 for your phone + pico OpenGAPPS
4. flash the latest Modem EUR region for your phone right after
5. use it for a few days without any Custom kernel and a minimum of installed apps
6. if your not satisfied restore the backup from step 2.
Sounds simple...it is indeed.
Regards / Grüße
DonQ
DonQuichotte said:
Moin,
I highly recommend you to switch to CyanogenMod. I took the switch to CM right after i bought my GT-I9195 and all I can say I've never expirenced such problems either on Vodafone nor O2. ATM I'm still at CM11 as this is rock stable and battery life is quite good, ~2-3 days depending on usage
Just follow this steps and you've got nothing to worry about.
1. install custom recovery
2. take a full backup of your current system + SD Card just for the case...
3. install CM11 for your phone + pico OpenGAPPS
4. flash the latest Modem EUR region for your phone right after
5. use it for a few days without any Custom kernel and a minimum of installed apps
6. if your not satisfied restore the backup from step 2.
Sounds simple...it is indeed.
Regards / Grüße
DonQ
Click to expand...
Click to collapse
1st of all you talk about your GT-I9195 model which is a normal S4 mini, but I have the DUAL SIM version.
Thanks but I want to stay with the normal SW train, I installed CM on a S3 1y ago and I didn't like the look and feel. So CM is not an option for me.
Besides my preferences, if I look at this article its nice to see, that there is progress for the DUAL SIM version but there are still known issues like stuttering problems and of you look down further the auther doesn't intend to create a CM official version out of it, so it looks more like a "hack" than something which is further supported by CM. Looks like an ALPHA SW and a one way road to me. http://forum.xda-developers.com/showthread.php?t=2790789
So .. other ideas ?!
Hello,
One point before flashing: your knox is 0x0 ? 1st flash result 0x1 and warranty lost.
Choice is to flash and try to solve this problem by yourself but lost the warranty or see with samsung support what they can do, but after 1st flash there is no coming back.
Kralisec said:
Hello,
One point before flashing: your knox is 0x0 ? 1st flash result 0x1 and warranty lost.
Choice is to flash and try to solve this problem by yourself but lost the warranty or see with samsung support what they can do, but after 1st flash there is no coming back.
Click to expand...
Click to collapse
I have no clue about knox. I am using the smartphone with a private and a company SIM.
But there are is company deployed SW on the smartphone. Also e-mail is pure private.
I only use DUAL SIM for the purpose of being able to make company phone calls with the company SIM.
Is there no way to get rid of 4.4.2 ? I remember the phone has been sold with 4.2.x.
Is there no 4.2 stored somewhere on the phone which can be reactivated ? At least then I could check, wheter it runs more stable and whether battery life is then better. But in fact I have no Kies backup, as I hate this bloated software.
Knox information : https://en.wikipedia.org/wiki/Samsung_Knox
more important: at the end, e-fuse part: "This information may be used by Samsung to deny warranty service"
Kralisec said:
Knox information : https://en.wikipedia.org/wiki/Samsung_Knox
more important: at the end, e-fuse part: "This information may be used by Samsung to deny warranty service"
Click to expand...
Click to collapse
Is somebody able to explain to me in easy words, what this all now means to me ?
Does this mean, I can't do a downgrade without loosing any kind of warranty ?
Should this be the case, I assume I am stuck n the 4.4.2 path and can only hope for vendor support (Samsung).
So shall I open a case with Samsung and hope that they fix the issue should it be a SW related issue ?
In short: if you flash using odin or heimdall for the 1st time you will loose your warranty.
Samsung update is merged inside rom, it's not something you can just uninstall.
I don't know if usual samsung tool let you downgrade to a previous version
(this time without knox issue since it's pure samsung way to update)
Hi, I've got this one Note 4 that's had loads of trouble presumably since the last security update.
Baseband Version: N910AUCS2EQD1
Android: 6.0.1
Have seen the instructions and all as to how to go about downgrading BUT one site I came across with the original stock firmware downloads outright state how:
""DO not ever try to downgrade from any newest Android 6.0.1 Marshmallow updates back to an older 6.0.1 build version""
'and so I'm lost. Should trying to then reinstall the same Baseband version atop what's already there a good first alternative? ...that is, just in case it was never upgraded properly in the first place? Or is that not even possible?
Is trying to downgrade at all a futile pursuit?
Would truly appreciate any suggestions, help, direction...heck, anything! Thanks in advance.
I downgraded from 6.0.1 epk5 to 5.1.1 with no problem.
Not sure about qd1.
As long as you have the odin firmware, I see no problem.
Can i downgrade note 4 n910a from marshmallow to lollilop,please help me i am in great trouble because marsmallow update is very bad with a lot of reboot issue ,battery drain.
Once you are on QD1 you will not be able to go back to anything lower than that firmware. The bootloader is now at the latest version and has blown one of those imaginary "e-fuses" so that you can not go back in time to any other vulnerable OS. I just tried today to go from EQD1 to EPK5 and It would not flash and would fail every time whilst using the latest Odin. So good luck on finding anything on getting you back to another firmware version but at this time I do not believe there is anything that will move you back to the firmware you want. If you do happen to find something or make your own exploit do tell @sanaullahkhan371 If you are on QD1 you are not going to be able to downgrade if you are on PK5 you can try the Odin downgrade method that will5 presumably used but if you are not in this firmware use case you are SOL.
will5 said:
I downgraded from 6.0.1 epk5 to 5.1.1 with no problem.
Not sure about qd1.
As long as you have the odin firmware, I see no problem.
Click to expand...
Click to collapse
Hi,
Can you please let me know how did you downgrade? Is it straight away flash to 5.1.1 or did you follow any steps?
I am also planning to downgrade. Anyways, I stopped using Note 4 after update to 6.0.1 as it was switching off every now and then due to update. Might as well make this phone usable to take photos and as a video player for my kid
Thanks
roxster said:
Hi,
Can you please let me know how did you downgrade? Is it straight away flash to 5.1.1 or did you follow any steps?
I am also planning to downgrade. Anyways, I stopped using Note 4 after update to 6.0.1 as it was switching off every now and then due to update. Might as well make this phone usable to take photos and as a video player for my kid
Thanks
Click to expand...
Click to collapse
I just odin to this firmware N910AUCU2DOI2-5.1.1 It s available somewhere on this forum.
Read how to odin if you never used it. In this case you need to unzip the file and load AP, BL, CP and CSC files on odin and flash.
Was running 6.0.1 epk5 previously.
will5 said:
I just odin to this firmware N910AUCU2DOI2-5.1.1 It s available somewhere on this forum.
Read how to odin if you never used it. In this case you need to unzip the file and load AP, BL, CP and CSC files on odin and flash.
Was running 6.0.1 epk5 previously.
Click to expand...
Click to collapse
Thanks a lot buddy! :good:
My note 4 was also running on 6.0.1 EPK5. Found the 5.1.1 firmware and followed your instructions to downgrade. My phone came back to life and is usable now.:victory:
No more switching off abruptly! I wont update anymore since all the apps which I use are working fine with current version of Android.
braindead444 said:
Once you are on QD1 you will not be able to go back to anything lower than that firmware. The bootloader is now at the latest version and has blown one of those imaginary "e-fuses" so that you can not go back in time to any other vulnerable OS. I just tried today to go from EQD1 to EPK5 and It would not flash and would fail every time whilst using the latest Odin.
Click to expand...
Click to collapse
Were you ever able to flash back to an older version from QD1? Others have said that the bootloader was not incremented in QD1.
spocko said:
Were you ever able to flash back to an older version from QD1? Others have said that the bootloader was not incremented in QD1.
Click to expand...
Click to collapse
Were you able to downgrade from EQD1 to 5.1.1? I am on EQH1 and I am not able to downgrade
somani09 said:
Were you able to downgrade from EQD1 to 5.1.1? I am on EQH1 and I am not able to downgrade
Click to expand...
Click to collapse
I'm also on EQH1. I have never tried to downgrade. I was just curious if it was possible, in case a root method was discovered that only worked on older versions. But I've just learned to live without root. EQH1 works fine for me.
I had the infamous freeze/reboot/shutdown issue with 6.0.1 and I wasn't sure if that was the issue but I downgraded to 5.1 and have fewer issues now. The phone runs just fine, except it does not reboot. You have to do a soft reset every time. But with the Wakelock app, at least it runs.
roxster said:
Thanks a lot buddy! :good:
My note 4 was also running on 6.0.1 EPK5. Found the 5.1.1 firmware and followed your instructions to downgrade. My phone came back to life and is usable now.:victory:
No more switching off abruptly! I wont update anymore since all the apps which I use are working fine with current version of Android.
Click to expand...
Click to collapse
Hi can i ask if u still have that firmware file
Looks like Verizon and AT&T users won't get the Android 10 beta.
Dougau said:
Looks like Verizon and AT&T users won't get the Android 10 beta.
Click to expand...
Click to collapse
Not officially but as usual people will share the update files on here so anyone can unofficially be part of the beta with any carrier supported by the multi csc.
Sent from my SM-G975U using XDA Labs
jwarrior319 said:
Not officially but as usual people will share the update files on here so anyone can unofficially be part of the beta with any carrier supported by the multi csc.
Click to expand...
Click to collapse
What is the multi csc?
jhs39 said:
What is the multi csc?
Click to expand...
Click to collapse
For U model: OYN
ATT, BSC, CCT, CHA, GCF, SPR, TMB, TMK, USC, VMU, VZW, XAA, XAS
For U1 model: OYM
ACG,AIO,ATT, BSC, CCT, CHA, GCF,LRA, SPR, TFN, TMB, TMK, USC, VMU, VZW, XAA, XAG, XAR, XAS
The firmware packages are released with the csc's (carrier specific software) included so switching carriers is as simple as swapping the sim and rebooting.
Sent from my SM-G975U using XDA Labs
basically wat hes saying is the devices are almost identical n use the same keys so once beta is out someone can pull the update and others could flash it.. like its always been lol
elliwigy said:
basically wat hes saying is the devices are almost identical n use the same keys so once beta is out someone can pull the update and others could flash it.. like its always been lol
Click to expand...
Click to collapse
Thanks for helping clear that up a little. I guess thats the short version. Just trying to show the why part. Lol
There's probably a slight chance there would be signal issues but there shouldn't be that many changes between 9 and 10 with the new setup.
Sent from my SM-G975U using XDA Labs
For anyone concerned on Verizon about the beta, I can confirm that the tmobile beta found at this thread works. No CSC headache needed. All I did was put the update on an SD card and run it through recovery. Personally, I did not clear data but, with anything beta it is suggested to clear possible bugs. As far as service, my phone booted up fine and the phone ran as if it were on a regular verizon pie firmware.
*IF* you are receiving the notorious adb sideload issue that I ran into as well (I didn't root my phone but, I have a feeling when I granted xda navbar permissions, it may have triggered something), simply move the update to a micro sd and update that way. I don't know if it'll require it in the future as well (I'm assuming the update would destroy modified system files) but, for now it works.
If any of you have any questions regarding the update, I'd be more than happy to answer them and please give a special thanks to goofwear on his thread for providing us with the beta!
megaghostgamer said:
For anyone concerned on Verizon about the beta, I can confirm that the tmobile beta found at this thread works. No CSC headache needed. All I did was put the update on an SD card and run it through recovery. Personally, I did not clear data but, with anything beta it is suggested to clear possible bugs. As far as service, my phone booted up fine and the phone ran as if it were on a regular verizon pie firmware.
*IF* you are receiving the notorious adb sideload issue that I ran into as well (I didn't root my phone but, I have a feeling when I granted xda navbar permissions, it may have triggered something), simply move the update to a micro sd and update that way. I don't know if it'll require it in the future as well (I'm assuming the update would destroy modified system files) but, for now it works.
If any of you have any questions regarding the update, I'd be more than happy to answer them and please give a special thanks to goofwear on his thread for providing us with the beta!
Click to expand...
Click to collapse
Can i update to beta via that update zip.I'm currently on G975USQS2ASGK
Zixi said:
Can i update to beta via that update zip.I'm currently on G975USQS2ASGK
Click to expand...
Click to collapse
Is that the latest update on your carrier? I can't remember what mine was before I did the beta but, I was on the latest verizon firmware before the beta.
I think yes it is.
Zixi said:
Can i update to beta via that update zip.I'm currently on G975USQS2ASGK
Click to expand...
Click to collapse
megaghostgamer said:
Is that the latest update on your carrier? I can't remember what mine was before I did the beta but, I was on the latest verizon firmware before the beta.
Click to expand...
Click to collapse
Zixi said:
I think yes it is.
Click to expand...
Click to collapse
Latest for U model is BSI4 or BSIA depending on carrier. BSI4 is required if using update zip from on here.
Edit: corrected BSIE to BSIA
Sent from my SM-G975U1 using XDA Labs
So i need to update to BSI4 and then update zip?
Quote:
Originally Posted by HolyHog
The only way you can install this update is from an external SD card. You can find the correct file here
https://forum.xda-developers.com/s10...3908657/page82 . Post 815.
Download either the U or the U1 version.
For a U phone
You must be on U BSI4 to update to the ZSJ8 Android 10 Beta. This is the Verizon version.
For a U1 phone
You must be on U1 BSIC to update to the ZSJA Android 10 Beta. This is the AT&T version.
Note : You can load via Odin any S10+ rom you like since all the S10+ are the same now. It will set up properly by the SIM card you have in it.
Once you have downloaded the respective file, rename it to update.zip. Then copy the update.zip file to your external SD card.
Once you have it on your SD card, restart your phone to the stock recovery. You do this by hitting restart twice and then hold down the bixby button and volume up. Don't let go until you see the recovery menu.
Once in recovery use the volume down button to highlight "Apply update from SDcard". Use the power button to select it. Next you will shown the files on your SD card. If you you put Update.zip on the root of your card, it will be the first file listed. Highlight the update.zip by moving to it with the volume down button.
Then select the update.zip withe the power button.
It will go through the installation and reboot.
You do not have to factory reset to do an update like this. The ROM will reset your apps to the new version number. That doesn't mean they will all work properly. For more info on what doesn't work go here.. https://forum.xda-developers.com/s10...-beta-t3983463
Don't forget this is a beta ROM and you are testing it out.
HolyHog said:
Quote:
Originally Posted by HolyHog
The only way you can install this update is from an external SD card. You can find the correct file here
https://forum.xda-developers.com/s10...3908657/page82 . Post 815.
Download either the U or the U1 version.
For a U phone
You must be on U BSI4 to update to the ZSJ8 Android 10 Beta. This is the Verizon version.
For a U1 phone
You must be on U1 BSIC to update to the ZSJA Android 10 Beta. This is the AT&T version.
Note : You can load via Odin any S10+ rom you like since all the S10+ are the same now. It will set up properly by the SIM card you have in it.
Once you have downloaded the respective file, rename it to update.zip. Then copy the update.zip file to your external SD card.
Once you have it on your SD card, restart your phone to the stock recovery. You do this by hitting restart twice and then hold down the bixby button and volume up. Don't let go until you see the recovery menu.
Once in recovery use the volume down button to highlight "Apply update from SDcard". Use the power button to select it. Next you will shown the files on your SD card. If you you put Update.zip on the root of your card, it will be the first file listed. Highlight the update.zip by moving to it with the volume down button.
Then select the update.zip withe the power button.
It will go through the installation and reboot.
You do not have to factory reset to do an update like this. The ROM will reset your apps to the new version number. That doesn't mean they will all work properly. For more info on what doesn't work go here.. https://forum.xda-developers.com/s10...-beta-t3983463
Don't forget this is a beta ROM and you are testing it out.
Click to expand...
Click to collapse
I have the verizon s10 plus and I am on BSIV, that is the most recent, Can I still update?
jhr5474 said:
I have the verizon s10 plus and I am on BSIV, that is the most recent, Can I still update?
Click to expand...
Click to collapse
You will get the stable Android 10 update as and when it comes like a regular monthly firmware update.
WhoIsJohnGalt1979 said:
You will get the stable Android 10 update as and when it comes like a regular monthly firmware update.
Click to expand...
Click to collapse
So there is NO way to flash any of the betas on the verizon model with this firmware?
jhr5474 said:
So there is NO way to flash any of the betas on the verizon model with this firmware?
Click to expand...
Click to collapse
No. Only way is to go back to BSI4 and flash the betas in chronological fashion.
WhoIsJohnGalt1979 said:
No. Only way is to go back to BSI4 and flash the betas in chronological fashion.
Click to expand...
Click to collapse
is it possible to revert and do that?
jhr5474 said:
is it possible to revert and do that?
Click to expand...
Click to collapse
Yes it is. Both BSI4 and BSIV are on the same boot loader. You can go back to BSI4 by downloading the firmware using Frija etc and Odin.
elliwigy said:
basically wat hes saying is the devices are almost identical n use the same keys so once beta is out someone can pull the update and others could flash it.. like its always been lol
Click to expand...
Click to collapse
Do you know if it's possible to pull a regular OTA update to be flashed with ODIN?
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Andrew8578 said:
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Click to expand...
Click to collapse
Same here, was literally just googling for help.
vibrantliker said:
Same here, was literally just googling for help.
Click to expand...
Click to collapse
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
You may not want to hold your breath on that one. For whatever reason, oneplus does not release full OTA zips for AA half the time. (WTF ONEPLUS). Because of this, I long since started flashing BA over my global phone. As the gentleman said up above, it works absolutely perfectly.
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
can I just flash the BA version on top of my current rom (AA) and not lose anything? I just got done reinstalling everything, and it was a pain. I don't want to do this a 3rd time, if I can avoid it.
I never had any issues with rooting/being unlocked and updating on my previous OnePlus phones... this is a new one for me.
On 8t I had to use EU..google is who releases OTAs for all variants except EU, which is still directly from oneplus. Rooting broke OTAs for me as well on any other rom besides EU...also I have 9pro, which I local updated to EU zip b4 flashing magisk_boot.img and I already received new update since rooting and all is good.
I just flashed BA on top on my current rom via system update (you have to click the cog wheel top right and put the OTA zip on your root directory)
Nothing changed and the navigation bar in split screen is indeed fixed, meaning this is the latest version.
Thanks again for letting me know about this!
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
zoman7663 said:
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Click to expand...
Click to collapse
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
bulletbling said:
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
Click to expand...
Click to collapse
Noted, thanks for the info.
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
What I want to know too!
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
bulletbling said:
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
Click to expand...
Click to collapse
geez, I hope we don't have to relock and unlock for every update. I guess for the time being, there's no reason to be unlocked, but when custom ROM's start rolling out, that's going to be a major headache. I wonder if/when the updates are posted on One Plus website, will the updates work, or will root/unlock still prevent it?
I really want that update as I'm reading it made the battery much better. What to do!
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
TPXX said:
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
Click to expand...
Click to collapse
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
vibrantliker said:
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
Click to expand...
Click to collapse
My last rooting experience was on an S7. Afraid I can't help you with this one.
Hi there,
Just like the title says.
Xprivacylua won't' work on Android 13 for me. what I was wondering is whether I can downgrade without flashing the bootloader.
I am going to follow the following guide but am afraid to get a bricked phone
How to Bypass Anti Rollback Mechanism in Pixel 6A/6/6 Pro
This guide will show you how to bypass Anti Rollback Mechanism while doing a downgrade from Android 13 to Android 12 on Pixel 6A/6/6 Pro.
www.droidwin.com
Thank you all
------------------------add---
finally managed to downgrade to Android 12, just add --force before update:
fastboot --force update image-oriole-sq3a.220705.001.b2.zip (m phone is pixel6)
then reboot, then choose factory reset.
credits @Bunnehbunn
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
smokejumper76 said:
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
Click to expand...
Click to collapse
You've made my day
I am going to wait and see for several days before proceeding as I just know how to flash-all, I have never flashed step by step or flashed to the specific slots.
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
roirraW edor ehT said:
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine.
Click to expand...
Click to collapse
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
roirraW edor ehT said:
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
Click to expand...
Click to collapse
Is downgrading on both slots a must? I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
bush911 said:
Is downgrading on both slots a must?
Click to expand...
Click to collapse
If you want to run Android 12 instead of 13, and you've already flashed 13 to both slots, or at least 13's bootloader to both slots (which you should definitely do if you haven't), then yes, you should downgrade both slots and wipe to start fresh.
You can't expect both Android 12 and Android 13 to operate with the same app data, so having a different version of Android on the other slot isn't going to do you any favors.
bush911 said:
I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
Click to expand...
Click to collapse
Try a factory reset?
Lughnasadh said:
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
Click to expand...
Click to collapse
Here my friend. Also in the OP.
Partial quote:
I tried this as soon as I upgraded to 13 and yes you can downgrade down to Android 12 after upgrading with no noticable issues. The radio and every other image but the bootloader can be downgraded. But I only tried 003, 004 July images for oriole so I don't know about anything lower personally.
Click to expand...
Click to collapse
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Lughnasadh said:
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Click to expand...
Click to collapse
You can join the ranks of such like my boss at work (where we use Google officially for everything including company mail). They chat me to ask me for a link to a particular file that's in Google Drive, or to find a particular email for them.
Just kidding about joining the ranks! You're welcome!
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Lughnasadh said:
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Click to expand...
Click to collapse
Absolutely, I agree on both parts.
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
enderdzz said:
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
Click to expand...
Click to collapse
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April. Also I'm surprised you weren't bricked after booting Android 13 because it does increment the anti-rollback counter.
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
drivers/soc/google/boot_control/boot_control_sysfs.c - kernel/gs - Git at Google
I'm guessing your bootloader version is old enough to not have the bits implemented so it just doesn't care, but that's weird because the July Android 12 bootloaders do have the bits and will not load if the counter is incremented by Android 13.
I wouldn't recommend continuing to run like this and would update to the August Android 13 bootloader because there's no telling what might be happening wrong under the hood. Example is that the August Android 13 bootloader it is able to boot Android 12 but because of interface differences it is a broken experience.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
So yeah if you're correct then it's possible you did get away with it as your firmware is too old to have implemented it. However this is not a supported firmware-software configuration.
Thank you for your reply!
Namelesswonder said:
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April.
Click to expand...
Click to collapse
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
Namelesswonder said:
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
Click to expand...
Click to collapse
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
enderdzz said:
Thank you for your reply!
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
Click to expand...
Click to collapse
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Namelesswonder said:
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much! I'm much more clear now.
enderdzz said:
Thank you very much! I'm much more clear now.
Click to expand...
Click to collapse
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Namelesswonder said:
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Click to expand...
Click to collapse
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
enderdzz said:
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
Click to expand...
Click to collapse
If WebView applications didn't crash within minutes of launching them then that means the DRM library should either be working or just not segfaulting like it does with Android 12 on 13 bootloader.
The fingerprint scanner HAL not working is completely understandable, part of the bootloader flash also carries the fingerprint scanner's firmware, and we know that one of the big things with Android 13 is that the fingerprint scanner is somewhat more reliable, so it definitely has changed between Android 12 to 13.
Interesting stuff, will be cool to see where it can go, but man is it sketchy to recommend people still on Android 12 to downgrade to April and then try flashing the Android 13 system images, real possibility of making bricks.