Database Info

Help with downgrade?

What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.

well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in

teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)

Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.

teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.

Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception

So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.

AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.

GM21AA OOS 9.5.6 update: how can I keep root?

Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB

Don't do like me. I updated to 9.5.6, rebooted and update went ok, but I lost root. Thought there would be a patched boot image already but havent found one.
update: go here
go to Post #299

dy2592 said:
Don't do like me. I updated to 9.5.6, rebooted and update went ok, but I lost root. Thought there would be a patched boot image already but havent found one.
Click to expand...
Click to collapse
Just open the downloaded ota, rip the boot.img from that file. Patch manually in magisk that boot.img. Then install the update, and reboot afterwards to fastboot mode. Flash the patched img and you are done.

Lucifer6 said:
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Click to expand...
Click to collapse
Post 6 in this thread is how I did it and retained root, but I lost TWRP (I knew I would before doing it) I used the steps used for the OnePlus 6t for rooted users, knowing I would lose TWRP.
https://forum.xda-developers.com/oneplus-7-pro/help/t-mobile-converted-to-9-5-4-received-t3934761
These are the steps for the 6t for TWRP users but I know TWRP is having decryption issues so I'm not sure if the below will work.
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss

Lucifer6 said:
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Click to expand...
Click to collapse
A partial ota with unlocked bootloader will brick your phone. Download the full zip and update in TWRP if you have it. If bootloader locked, install as normal, wait for it to finish and ask to reboot, don't reboot and open magisk manager and install to inactive slot. Reboot. That process will cause you to lose TWRP if you have it. If you have TWRP, flash full ROM in TWRP, flash TWRP.zip, reboot recovery and flash magisk.zip.

This way is easy and painless.
Yep performed the system update as well. It saw I was rooted and proceeded to download the full OTA. I let it update, did not reboot. Went to Magisk and Install to Inactive Slot(After OTA) and all is well. Im still rooted.
Posted by another user and the way I just did 9.5.6. Yes you will lose TWRP as usual if installed.

schmeggy929 said:
This way is easy and painless.
Yep performed the system update as well. It saw I was rooted and proceeded to download the full OTA. I let it update, did not reboot. Went to Magisk and Install to Inactive Slot(After OTA) and all is well. Im still rooted.
Posted by another user and the way I just did 9.5.6. Yes you will lose TWRP as usual if installed.
Click to expand...
Click to collapse
So dumb question here since I'm sorta new with this device (I've had Samsung and other devices that I've rooted so I'm aware of the basics).
Where do I download the entire fastboot zip files for say 9.5.6.GM31CB (TMobile variant)? I can't find it on OnePlus or T-Mobile. Also side question, do we still need to use Chinese certain of TWRP to get decryption working for internal storage? Thank you for whatever info you can provide.

I wonder, is there a patch for 9.5.6 yet? Let's say I have a locked bootloader now and stock on 9.5.6, how would I go about rooting my device? Or will I have to wait for the patched boot.img?

Lucifer6 said:
I wonder, is there a patch for 9.5.6 yet? Let's say I have a locked bootloader now and stock on 9.5.6, how would I go about rooting my device? Or will I have to wait for the patched boot.img?
Click to expand...
Click to collapse
Not if you unlock it, install magisk and patch the boot image within the app. I'd suggest looking for full zip of 9.5.6 just to use in case.

Which TWRP are you guys using? I see there is a Chinese version with decrypt working. Is that one safe?

photolarry said:
So dumb question here since I'm sorta new with this device (I've had Samsung and other devices that I've rooted so I'm aware of the basics).
Where do I download the entire fastboot zip files for say 9.5.6.GM31CB (TMobile variant)? I can't find it on OnePlus or T-Mobile. Also side question, do we still need to use Chinese certain of TWRP to get decryption working for internal storage? Thank you for whatever info you can provide.
Click to expand...
Click to collapse
There doesn't seem to be any fastboot ROM for the T-Mobile variant nor any Full OTA zips yet. Just have to keep looking in the PRO Guides, News and Discussion section. Personally I would not use that version of TWRP. Im waiting for the other TWRP by Maurinofrio to get Decrypt working.

schmeggy929 said:
There doesn't seem to be any fastboot ROM for the T-Mobile variant nor any Full OTA zips yet. Just have to keep looking in the PRO Guides, News and Discussion section. Personally I would not use that version of TWRP. Im waiting for the other TWRP by Maurinofrio to get Decrypt working.
Click to expand...
Click to collapse
So weird they claim they are as friendly to developers as pixel yet I don't see links to firmware. Not sure if I'm going to even bother rooting without backup of a full zip with all images inside. I guess I could get 9.5.3 and then do a few upgrades to get back to 9.5.6 but I'd rather have full file for 9.5.6.GM31CB

photolarry said:
So weird they claim they are as friendly to developers as pixel yet I don't see links to firmware. Not sure if I'm going to even bother rooting without backup of a full zip with all images inside. I guess I could get 9.5.3 and then do a few upgrades to get back to 9.5.6 but I'd rather have full file for 9.5.6.GM31CB
Click to expand...
Click to collapse
They are as developer-friendly as Pixel phones, (when you buy unlocked directly from OnePlus) not the T-Mobile version. Buy a Pixel from Google it OEM unlock to unlock the bootloader, buy a 7 Pro from OnePlus it's OEM unlock to unlock the bootloader.
In addition about you going to 9.5.3 and then upgrading to get back to 9.5.6
The 9.5.6 you're currently running on the T-Mobile version is not the same as 9.5.6 on the unlocked version. The unlocked version is a few builds newer.
If I were you I'd wait till the MSM tool that works with the T-Mobile version is released.

bp328i said:
They are as developer-friendly as Pixel phones, (when you buy unlocked directly from OnePlus) not the T-Mobile version.
In addition about you going to 9.5.3 and then upgrading to get back to 9.5.6
The 9.5.6 you're currently running on the T-Mobile version is not the same as 9.5.6 on the unlocked version. The unlocked version is a few builds newer.
If I were you I'd wait till the MSM tool that works with the T-Mobile version is released.
Click to expand...
Click to collapse
Msm tool? I'll get an unlock token Friday. Why would I need that? Newer than 9.5.6.GM31CB? I don't think so. This includes April security patch. I'm guessing the only big difference is the radio image is different for TMobile. Again I'm new to this mfgr so I'm trying. They aren't making it easy for me. I have an unlock phone. So shouldn't matter if I got it from T-Mobile. I can OEM unlock. So I can manipulate at will. Trouble is I'm scared I'll break the phone since I don't know this line of Android devices. I considered changing this to international but afterwards in worried it'll not work well in T-Mobile

photolarry said:
Msm tool? I'll get an unlock token Friday. Why would I need that? Newer than 9.5.6.GM31CB? I don't think so. This includes April security patch. I'm guessing the only big difference is the radio image is different for TMobile. Again I'm new to this mfgr so I'm trying. They aren't making it easy for me. I have an unlock phone. So shouldn't matter if I got it from T-Mobile. I can OEM unlock. So I can manipulate at will. Trouble is I'm scared I'll break the phone since I don't know this line of Android devices. I considered changing this to international but afterwards in worried it'll not work well in T-Mobile
Click to expand...
Click to collapse
There are a lot more changes in the international 9.5.6 GM21AA then that. they optimized double tap to wake and ambient display, fixed Bluetooth headset delays, camera updates, and other things.
The T-Mobile version will always be behind on software verse the international version.

bp328i said:
There are a lot more changes in the international 9.5.6 GM21AA then that. they optimized double tap to wake and ambient display, fixed Bluetooth headset delays, camera updates, and other things.
The T-Mobile version will always be behind on software verse the international version.
Click to expand...
Click to collapse
So are you saying I should update to AA? Even if I'm on T-Mobile network?? Will that not mess with the radio?

photolarry said:
So are you saying I should update to AA? Even if I'm on T-Mobile network?? Will that not mess with the radio?
Click to expand...
Click to collapse
That's the main reason everyone with the T-Mobile version is trying to unlock their bootloader, so they can run the international software. T-Mobile's software will always be behind the unlocked version. 9.5.3 for the unlocked version had the April security patch, that was three versions ago.
I owned the T-Mobile version of the 6t and the unlocked version of the 6t, the reception was the same.
My T-Mobile 7 Pro is unlocked running the international GM21AA software on T-Mobiles network. I uninstalled the Renovate Ice ROM for the screenshot so you can see I have the same model number as you running GM21AA.
But currently if you mess up a T-Mobile version there's no way to get it back because the MSM tool for it is not available yet. If something goes wrong you might be stuck with a phone that doesn't work until it's released.

bp328i said:
That's the main reason everyone with the T-Mobile version is trying to unlock their bootloader, so they can run the international software. T-Mobile's software will always be behind the unlocked version. 9.5.3 for the unlocked version had the April security patch, that was two versions ago.
I owned the T-Mobile version of the 6t and the unlocked version of the 6t, the reception was the same.
My T-Mobile 7 Pro is unlocked running the international GM21AA software on T-Mobile. I uninstalled the Renovate Ice ROM for the screenshot so you can see I have the same model number as you running GM21AA.
But currently if you mess up a T-Mobile version there's no way to get it back because the MSM tool for it is not available yet.
Click to expand...
Click to collapse
Thank you for your feedback. It's helpful to me. I am guessing an msm tool is something that puts stock firmware onto the device fresh in case you brick it. Couldn't I just fastboot flash 9.5.3 full package which I think is downloadable within OnePlus support?

photolarry said:
Thank you for your feedback. It's helpful to me. I am guessing an msm tool is something that puts stock firmware onto the device fresh in case you brick it. Couldn't I just fastboot flash 9.5.3 full package which I think is downloadable within OnePlus support?
Click to expand...
Click to collapse
Correct about the tool, returns the phone to 100% stock out of the box. Not 100% sure about whether or not the fastboot flash would fix a soft bricked device. That could possibly work.
But I know currently it's impossible to go back to T-Mobile software without the tool.

has anyone contact oneplus support either via email and chat and requested full ROM download links?
theyre pretty helpful like that.

Motog8 plus root

Does anyone know how to root? Till yet ?
Today IT was my Christmas.present
Thanks
Daniel

No source from motorola, nor updates yet.

Hello you can root your moto with magisk.

Mounib BOULAABI said:
Hello you can root your moto with magisk.
Click to expand...
Click to collapse
If you have a copy of the boot.img
Sent from my mata using XDA Labs

Thanks by the way. I found i way to root my Device.

Please do tell, how?

Danieldergrosse said:
Thanks by the way. I found i way to root my Device.
Click to expand...
Click to collapse
Would you mind sharing your way to root your device? Every piece of knowledge can help other users here on XDA.
Sent from my Moto G5 Plus using XDA Labs

http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method

Danieldergrosse said:
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Click to expand...
Click to collapse
*
your link seems dead or not correct. - edit: link correct, was not working due to my vpn...
I assume he patched a G8+ boot.img with magisk manager.
boot image can be extracted from official Doha firmware found here: https://mirrors.lolinet.com/firmware/moto/doha/official/
manual on how to do this can be found on official magisk manager website.
be aware that when unlocking bootloader your phone will reset to factory settings.

This is what I did. Yes..

Worked great for my G8+. I guess people should just check which stock ROM file they get from lolinet to make sure it's the right one. I say that because, in my case, lolinet list had two files for the Brazilian stock ROM. I went to Settings / About / Version number and downloaded the matching file. Don't know whether the other file would work the same or not. Just didn't want to risk having any issue since G8+ is somewhat new and there's not much info on solving root problems on the Internet.

Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl

carl.13 said:
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
Click to expand...
Click to collapse
Hello, Carl. I guess it's not possible unless there's a flaw in the security. There are some articles on the Internet about that. Google "is-there-a-way-to-root-an-android-phone-without-unlocking-the-bootloader". I can't post URLs yet.
As for Motorola devices, I was able to unlock the bootloader without problems on my G8+, last week. The only caveat, I'm my case, is that I had to wait some days for the unlock bootloader option be available under developer options. It was disabled by default in my G8+. And, yes, they're releasing bootloader unlocking codes.

THANKS!

Have anybody with a rooted device tried to get wide angle camera working in gcam ports?
Thanks.

successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google

esrd43 said:
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
Click to expand...
Click to collapse
magisk module debloater and also sdmaid helped with most of the bloatware, the only thing I could not remove was google files but I just deactivated it.

a really weird thing happened with the April 1st update, basically the update started automatically and it failed at 3/6 so I tought I should restart my phone and test it again, but it got stuck in bootloop and I had to reflash a rom with fastboot cmd.
I think that's because I unlocked the bootloader and rooted my phone, cause u lose the right for updates after you do that, but for some reason lenovo/moto update system goes automatically the next second u connect to the internet and fails halfway thru so u have a higher chance to ruin your phone or something, instead of denying the update from the start
so the solution I found was to try and delete "moto update service" app that I can't force stop or disable but I couldnt find it in system/app or system/priv-app, that's because the app name is "3c_ota", so deleting that with SD Maid app worked and the "update system" option in settings is reverted to a sort of default android one that lets you check manually.

Had a similiar issue. I soft bricked my phone (bootloop) and installed a stock rom from an unofficial source. The funny thing is, this version did make like 3 or 4 system upgrades to PPSI.29.65-51 without any issue. But the 1st April updated failed to install. I then flashed the official 1st april stock image with the moto rescue and smart assistant. After that, the official ROM tells me my phone is not allowed to do updates because the security of this phone is compromised and I should contact lenovo support
Those upates are kinda annoying if they don't work, I guess I'll just completey flash the phone every 6-12 months with the moto assistant.

yeah you should always have a backup rom that you can download with moto assistant or from lolinet g8 roms (https://mirrors.lolinet.com/firmware/moto/doha/official/)
I also got the same message saying that my phone is compromised ( unlocked bootloader + rooted) and it won't receive any further updates, but I just deleted the "3c_ota" app (the moto update service) which is bad cause if forces automatic updates the second u connect to internet.
I'm not going to touch any further updates or security patches until android 10, which I will attempt to flash via moto assistant

Google Pixel 3 noobie queries

Hi!
I come from the Galaxy S series (S4, S5, S7) phones and I m considering of buying a Google Pixel 3
I can find many decent options, all of which are carrier unlocked
My concern with the Pixel 3 is whether I ll be able to install Android vanilla (without any carrier-related bloatware)
For all of my Samsung's so far, I could easily pick the retail ROM (well not exactly 'vanilla'!) from sammobile and load it with Odin (without breaking the knox)
Can I do something similar in the Pixel 3 or are there any security mechanisms to prevent me? (I m talking about installing original ROM - not custom..)
Bonus question - does any of you know if the Pixel 3 from Verizon and US Cellular have branding [carrier logo(s)] on the device?
Thank you in advance!

Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.

Note10.1Dude said:
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Click to expand...
Click to collapse
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks

jstoner said:
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
Click to expand...
Click to collapse
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.

dcarvil said:
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
Click to expand...
Click to collapse
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon

jstoner said:
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
Click to expand...
Click to collapse
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.

dcarvil said:
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
Click to expand...
Click to collapse
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!

jstoner said:
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
Click to expand...
Click to collapse
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.

dcarvil said:
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
Click to expand...
Click to collapse
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)

jstoner said:
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
Click to expand...
Click to collapse
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.

dcarvil said:
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
Click to expand...
Click to collapse
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..

jstoner said:
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
Click to expand...
Click to collapse
Hmmm I think the way it works is that when the phone is produced, for a specific carrier, and the carrier wants it to have a sim, it's put in at the factory. So, I think, sealed with a sim in it, possible.
I don't think us cellular uses e-sims. Double check that but it doesn't look like one of the carriers that's capable of e-sims.
cheers, good luck. I have a vzw coming today, hoping it's new and can unlock as others have... we'll know soon.

Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...

jstoner said:
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
Click to expand...
Click to collapse
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.

dcarvil said:
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
Click to expand...
Click to collapse
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best

jstoner said:
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
Click to expand...
Click to collapse
If security is a concern, you'll want to go to Android 11. 10 has not been updated since August 2020, when Android 11 came out. Also, I believe there have been camera improvements since August 2020, which would not be in the latest Android 10 build.
I have not seen any reports of stability problems with the June 2021 Android 11 update, which has the latest security patches.
I don't know if you can do an OTA update to Android 11 from Android 9. You might have to go from 9 to 10 to 11. You can flash the Android 11 image without going to 10 first.

I intend to do via flashing (whichever version I decide in the end). Not a fan of OTA

Question Using wrong boot .image?

Booted up a oneplus 9 pro boot image, it fixed my phone being stuck in fastboot because I didn't have stock image.
Now updates don't work.
Oneplus 9 T-Mobile, stock rom, pro boot image, unlocked bootloader, unlocked sim - Any help would be appreciated.
Was thinking MSM tool but unsure what one to use.

I'm in a similar situation but I can't get out of fastboot. What OnePlus Pro boot image did you flash to your phone and what firmware are you on?

I gave the pro boot.img a try and it worked!
I grabbed it from this post: https://forum.xda-developers.com/t/...t-keep-root-oos-12-c-48.4252373/post-87096189
I want to back a few things up before tinkering anymore but will report back on how I try to fix it.
Thinking ahead, did Oxygen Updater not allow you to change your device back to a OnePlus 9, download the software update, flash and revert back?

Glad you could get your phone fixed...
I wish my system updates worked though lol ugh

Harley1979 said:
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Click to expand...
Click to collapse
Are you using Oxygen Updater or the native update tool?
If the latter I would try the former.
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com

No I'm on a t-mobile oneplus 9 with android 12.

Soooo have you tried Oxygen Updater?

No it doesn't work for my version of this phone.
Thanks though

I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...

Harley1979 said:
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Click to expand...
Click to collapse
If your bootloader is unlocked and Google Play is telling you that your device is not supported, it's because of the unlocked bootloader most likely. Are you successfully passing both basic and CTS safetynet profiles?

Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.

Harley1979 said:
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Click to expand...
Click to collapse
I think your problem is that your bootloader is unlocked and it needs to be locked in order to pass safeynet. More and more apps are not allowing for detected unlocked bootloaders in which makes safetynet fail.

Wish I knew how to relock it... Little reluctant to use a random site's information... Xda probably has information on relocking it, wish I had a link to a good post.

Could it possibly brick my phone if I'm using a pro boot image an try to lock bootloader?
Any advice or help would be much appreciated thanks for your time.

I will follow-up more later as I'm walking out the door. I'm not convinced that we are on a different or should I say, incompatible boot.img. When I get home I need to do some research to see what is actually different in the boot.img when being compared each other (C.61 boot.img on OP9 and OP9 Pro).
Back history for anyone following along... I was unlocked, rooted, Google Play certified and on C.48. I upgraded via OTA, no reboot and chose an inactive slot. It did not work and soft bricked slot a. I lost root, was on C.48 still but on slot B. I successfully upgraded to C.61 but didn't have root. I could not find a good boot.img or patched_boot.img. I tried a stock OP9 Pro image and that got me working. That same user provided a patch img too so I tried that and obtained root as well.
Soooo what is the difference between the boot images on C.61 pro and non-pro OP9 models?
Stay tuned....!

Thanks I'll keep checking back on this

Unfortunately the difference is that the pro version is available to tinker with and the non pro version isn't. Sorry to state the obvious.

My phone so far is working fine on the OP9 Pro kernel. C.61 is rooted and Google Play is certified. All my previous Magisk config is there as well and modules. I'm not sure what the difference between the kernels are at this point but also not a kernel expert either.
Once the next full release comes out for OP9, I will swap it out.
@Harley1979 I got your PM and will follow-up with you there.