So, I decided that I wanted to try flashing GSI's on this phone and on checking 2 different apps, they specify that the OP9P isn't treble compatible. What gives? Are the apps just not capable of knowing since it's a new device or has something changed and are devices no longer required to be treble compatible?
You sure you want to try flashing roms when we don't even have TWRP yet?
Jhoopes517 said:
So, I decided that I wanted to try flashing GSI's on this phone and on checking 2 different apps, they specify that the OP9P isn't treble compatible. What gives? Are the apps just not capable of knowing since it's a new device or has something changed and are devices no longer required to be treble compatible?
Click to expand...
Click to collapse
Keep in mind the partitioning scheme of the 9 pro. OnePlus phones typically have a different list of partitions when compared to other standard android phones.
I assumed it was but when trying to flash via fastboot, just didn't work out as planned. Thank y'all for answering though.
I think it's gonna be the same as the 7pro you have to have the original boot and vbmeta and used fastbootd
Related
I just have been at a local store, had this phone in my hands and I have to admit, that this phone could be the perfect phone for me. I love the dimensions. My only problem: on my previous phones I always had full access to my phone (root et al), and this seems to be a real problem with sony phones in general. Unlocking the bootloader is difficult, and if you succeed, this might break your hardware (camera, as this is the case with Sony xz1 compact).
I'd need access mainly to extend the phone's lifetime, using custom roms when the device is not supported by the manufacturer any more. (I have high hopes that updates are easier since oreo.) So my question: This would be my first Sony. What do you expect in this regards?
That at least for two years, you'll have top notch official updates.
By that, fixes for it, like happened for previous xperias, are likely to pop out camera just degrade in quality btw it doesn't break completely)
As for extending functionalities, I hate to admit it, but modern android really.
Even freaking betterbatterystats can be granted all the required system permissions with.
Same for shimming applications with virtualxposed.
Well, if you are only using root and custom ROMs after support has ended, you do not have to worry about that for the next two years (maybe three considering security updates). Sony is in the Top3 Android-Manufacturers then it comes to Softwaresupport.
So, after two years you won't have any problems using an AOSP ROM. Thanks to project treble you could already use such a ROM right now. And with the ported Google Camera APP (which will be working on the new Snapdragon 845 shortly) you will not have to compromise Photoquality when switching to a Custom ROM.
To sum up: You don't have to worry for the next two years and you will be able to use this phone for a long period of time thanks to project treble and GCam.
PS: you do not break the actual hardware by unlocking the bootloader, you simply lose some sony-softwarefeatures, which can be replaced most of the times. At least that's how it's been on Sony Flagships in the past years.
Marvinho+ said:
Thanks to project treble you could already use such a ROM right now.
Click to expand...
Click to collapse
Really? Please post where that rom is, and how to use project treble to install it?
Here is one of those ROMs: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
I suggest you to do a search for project treble here on xda. There are several articles and threads to learn more about it.
I do not own a treble enabled device myself, so I don't know exactly how it all works.
Unlocking the bootloader isn't hard, even a noob can do it with ease. Sony is one of few manufacturers that actually supports it natively from their website. But, as you said there are some downsides to it. The DRM-keys will be lost forever, unless you back it up (which you can only do with temp root). But if you going to use a custom rom, there's no need for them anyway.
I'm not sure what loosing the DRM-keys will do with the XZ2 Compact. But with previous models some stuff stopped working, like the image processor. The camera worked, but with a slight impact on pictures taken in low light (probably have to do with image processor).
Marvinho+ said:
Here is one of those ROMs: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
I suggest you to do a search for project treble here on xda. There are several articles and threads to learn more about it.
I do not own a treble enabled device myself, so I don't know exactly how it all works.
Click to expand...
Click to collapse
no custom recovery for this phone yet, so not sure how you can flash a custom rom on it
Via fastboot. At least thats what it says in the instructions, when no custom recovery is available.
I told you to read more about treble and you didn't even read the instructions? I'm not gonna flash the ROM for you.
So to make things clear: I think you could flash a treble ROM like lineage OS et al. but I wouldn't recommend it to you.
Because:
-you would lose your DRM keys. There is no way to back them up yet and no DRM fix, yet.
-Gcam is not working properly an the sd845 yet.
Just wait two months and it will be whole other situation with this phone.
Are you this disappointed with the Sony firmware, that you want to flash another ROM already?
flashing a rom via fastboot is not what I would consider a safe thing to do, and, if you have a disaster doing it, then without a custom recovery there might be a problem getting back to where you were.
I'll wait to flash anything until there is actually something worth flashing, since the Sony stock firmware is pretty good right out of the box
Hey all, so I'm finally thinking of retiring my Motorola Nexus 6. I've had this thing for so long and was such a great device. Now I'm wondering a few things before going all in.
1) I see people selling them brand new on eBay for as low as $550 to $600. They even show pictures of them in the original box with shrink wrap and all, is this too good to be true?
2) How hard is it to get used to the new A/B partitioning scheme Google is going with now? I'm so used to the traditional scheme Android has always used.
3) How's the dev scene looking for this device? At a glance, there seems to be a decent amount of good roms and great devs, but do these Pixel devices see the same support or near it as the Nexus devices always have?
4) Do roms flash to both system A and B and boot A and B partitions?
5) Does flashing a boot.img file also wipe the recovery entirely since there's no recovery partition on these devices? Is it a danger if you forget to reflash twrp zip?
Thanks guys! Really putting thought into getting this phone.
1) Those are almost certainly Verizon phones. They have locked bootloaders. Many will say "unlocked", they mean SIM unlocked. The only way to be sure it is unlockable is to get a Google version straight from the Google store. You can check IMEI's if the seller will give it to you.
2) Pretend the A B system does not exist. When you flash it flashes current slot, that is all you need to know really. It only switches slots when it does an OTA.
3) Not as much as the Nexus devices but it is decent. I suspect the phones cost keeps some devs away.
4) See 2 above.
5) Yes flashing boot wipes TWRP, as does side loading OTA's and so on. If you forget to put TWRP back it is no problem. I have never installed TWRP on either my 2 or my OG XLs. I do it all from my computer. Certainly I boot to TWRP to install zips. There is a bootable TWRP img file for that.
TonikJDK said:
1) Those are almost certainly Verizon phones. They have locked bootloaders. Many will say "unlocked", they mean SIM unlocked. The only way to be sure it is unlockable is to get a Google version straight from the Google store. You can check IMEI's if the seller will give it to you.
2) Pretend the A B system does not exist. When you flash it flashes current slot, that is all you need to know really. It only switches slots when it does an OTA.
3) Not as much as the Nexus devices but it is decent. I suspect the phones cost keeps some devs away.
4) See 2 above.
5) Yes flashing boot wipes TWRP, as does side loading OTA's and so on. If you forget to put TWRP back it is no problem. I have never installed TWRP on either my 2 or my OG XLs. I do it all from my computer. Certainly I boot to TWRP to install zips. There is a bootable TWRP img file for that.
Click to expand...
Click to collapse
Question about 5 right there, with the old partition scheme Android used, all roms had a boot.img inside the zip that could be flashed with TWRP directly. Do Pixel roms have this boot.img file as well? Not at my PC at the moment so I can't download one and see. I always used to reflash the boot.img file from my roms before updating to a different kernel on my Nexus 6. Thanks! Appreciate the reply!
Also, the A/B partitions only change with an OTA and not a rom flash from TWRP correct?
H4X0R46 said:
Also, the A/B partitions only change with an OTA and not a rom flash from TWRP correct?
Click to expand...
Click to collapse
It depends on the ROM. Some flash both partitions, some only one. You can always change slots with TWRP, so this is no issue at all.
But for me, the Pixel 2XL is the first phone where I don't see a reason to flash a custom ROM, the stock ROM is fantastic :good:
Your mileage may vary, of course.
I'm considering upgrading to an OP 9 Pro (used from Swappa, like my last few phones) at some point in the next few months. I know from experience that OP phones use an encrypted data partition, but I was able to use custom ROMs (my own LineageOS fork) on my 3T and 7 Pro with unencrypted data. My question, since I haven't seen it brought up in my browsing of the threads here, is simple: can the 9 Pro can also be used with unencrypted data and a custom ROM, and if so, how? The 3T was easy to keep unencrypted; by contrast, I have to flash Disable_Dm-Verity_ForceEncrypt.zip every time I update the ROM on my 7 Pro (which is no big deal, just one more step in the process), but I'm not sure if that zip is usable on the 9 Pro, or if something else is needed.
(And just to head off the inevitable "why do you want to run unencrypted?" questions: I have my reasons, so please, don't ask. All I want to know is if it's possible, and if so, how to do it. The why's are irrelevant to the discussion.)
Thanks in advance!
It seems there would be better solutions to your problems than to just run unencrypted. You could try the zip and then run MSM if it bricks, but as you're not sharing your reasons why you'd do this, it's hard to come up with a different solution that could solve your issues.
razercortex said:
It seems there would be better solutions to your problems than to just run unencrypted. You could try the zip and then run MSM if it bricks, but as you're not sharing your reasons why you'd do this, it's hard to come up with a different solution that could solve your issues.
Click to expand...
Click to collapse
It's personal preference, and I can't exactly "try the zip" if I don't actually have the device; my purchase is contingent on its ability to run with unencrypted data.
MJPollard said:
I'm considering upgrading to an OP 9 Pro (used from Swappa, like my last few phones) at some point in the next few months. I know from experience that OP phones use an encrypted data partition, but I was able to use custom ROMs (my own LineageOS fork) on my 3T and 7 Pro with unencrypted data. My question, since I haven't seen it brought up in my browsing of the threads here, is simple: can the 9 Pro can also be used with unencrypted data and a custom ROM, and if so, how? The 3T was easy to keep unencrypted; by contrast, I have to flash Disable_Dm-Verity_ForceEncrypt.zip every time I update the ROM on my 7 Pro (which is no big deal, just one more step in the process), but I'm not sure if that zip is usable on the 9 Pro, or if something else is needed.
(And just to head off the inevitable "why do you want to run unencrypted?" questions: I have my reasons, so please, don't ask. All I want to know is if it's possible, and if so, how to do it. The why's are irrelevant to the discussion.)
Thanks in advance!
Click to expand...
Click to collapse
I understand where you're coming from, I was there with you and in the same mindset. I also had a 7pro. But running unencrypted on the 9pro is not possible.
I haven't dabbled in flashing custom ROMs since the Galaxy S2 days and i've just purchased the Poco F3 so i'm starting to research my options for a flashing a ROM that will be more of a stock android experience.
I find YouTube tutorials easier to follow than written ones and I was wondering if anyone like me (a noob, basically) could a recommend a video or series of videos?
I'd also be interested to know if there are any things i should be aware of that you shouldn't do, like common mistakes noobs make? Also, feel free to recommend a ROM you like or any other advice you may have, i'd really appreciate it.
My last question is will banking apps still work after the installation of a custom ROM?
Thanks
Welcome to XDA!
Yes, I can highly recommend the YouTuber "Munchy", he covers a lot related about Xiaomi Smartphone Modding. He is a no-bullsh*t, straight to the point YouTuber who explains steps quite well.
If you type "munchy poco f3 flash custom rom" into YouTube, you'll find his videos!
Have you unlocked your bootloader yet?
You have to do that with Xiaomi's Mi Unlock Tool. It will ask you to sign in with a Xiaomi Account, and then you have to wait 1 week to actually start the Unlocking-process. Unlocking the BL will also factory-reset your phone and erase all data.
To your last question: No, by default, Banking-Apps, Netflix and other apps, will stop working with an Unlocked Bootloader.
This is because "Google SafetyNet" checks if your bootloader is unlocked, and will report to those apps that this device has Failed the certification-test, aka. tell them that your phone has been tampered.
But you can circumvent that and hide the fact that your bootloader is unlocked, by using Magisk, enabling Zygisk, and installing the Magisk Module "SafetyNet-Fix" from GitHub. This is how I've been using my Poco F3 with an unlocked BL and rooted ^^ Everything works.
If you have more questions, you can PM me.
As for good Vanilla Android ROMs, I can recommend ArrowOS, LineageOS, Pixel Experience.. there are many good ROMs.
Question is also, do you want just a basic Android Experience, or also the Pixel-exclusive Goodies. Cuz Pixel Phones come with features that are not included in AOSP, and you may like those features, or you may not care. ^^
@cyanGalaxy
Thanks for the info, really appreciate it. I have a couple more questions if you dont mind?
If install a ROM that requires TWRP which version should I use as i've seen mention of the "official" version and other "unofficial versions"?
In one of Munchy's videos (i think the one where he installs Crdroid) it looks like he has the ROM and TWRP files (plus another i think) on a USB stick rather than on the phone storage itself. Is it standard practice to flash ROMs and recovery images etc from external storage?
Thanks again.
Goooober said:
@cyanGalaxy
Thanks for the info, really appreciate it. I have a couple more questions if you dont mind?
If install a ROM that requires TWRP which version should I use as i've seen mention of the "official" version and other "unofficial versions"?
In one of Munchy's videos (i think the one where he installs Crdroid) it looks like he has the ROM and TWRP files (plus another i think) on a USB stick rather than on the phone storage itself. Is it standard practice to flash ROMs and recovery images etc from external storage?
Thanks again.
Click to expand...
Click to collapse
Official TWRP: https://twrp.me/xiaomi/xiaomipocof3.html
(Doesn't support Android 12's Encryption yet, so don't use this)
Unofficial TWRP ("skkk"): https://dl.akr-developers.com/?dir=skkk/TWRP/A12
(Supports Android 12's Encryption, use this! May have minor bugs.)
Is it standard practice to flash stuff from a USB-connected device?
No, we usually use either the Internal Storage or a PC (using ADB in the Command Prompt). But a USB-device works too!
@Goooober
You just have to be on the latest MIUI before flashing a Custom ROM, that's it.
Only few Custom ROMs require an older version of MIUI as a prerequisite.
Remove any PIN/Password/Pattern (helps to avoid encryption problems in TWRP),
Reboot phone into Fastboot,
Boot into TWRP_xxx_xxx.img from your PC using Fastboot in a Command Prompt:
"fastboot boot twrp.img"
(considering file is called "twrp.img" and is located in same folder as the Google SDK Platform-Tools)
In TWRP, do a factory-reset + wipe data,
Flash crDroid.zip,
Flash NikGapps.zip (contains the closed-source Google Services),
Reboot
I think this should cover the basics... Let me know if this works out. If you have any questions, do let me know.
Note: Many Custom ROMs don't require NikGapps, because they already have the closed-source Google Apps. crDroid however, doesn't contain Google Apps.
So I've been using a b partitions on this device for all previous os's. But I've heard that Android 13 does away with this is this true? If so if I download and want to flash a Android 13 ROM, how is this going to be different than what we've done before? Sorry in advance for any grammatical errors this is voice to text.
I am not sure about OOS 13 has removed slot A and B however, it shouldn't affect the way you flash the ROMs. Just follow the instructions as per posted for Custom Roms and for OOS, just update it like you normally would.
dilar said:
So I've been using a b partitions on this device for all previous os's. But I've heard that Android 13 does away with this is this true? If so if I download and want to flash a Android 13 ROM, how is this going to be different than what we've done before? Sorry in advance for any grammatical errors this is voice to text.
Click to expand...
Click to collapse
I've seen nothing that says Android 13 does away with A/B partitions. If anything, Google is leaning even harder into the A/B partition system. (It makes things something of a hassle for us modders, but it really is beneficial for regular users when they do OTA upgrades.) The biggest exception, of course, is Samsung, who still stubbornly refuses to use them on their phones. Even the new S23 series doesn't use them. As such, you should just keep continuing to flash new versions on the 9 Pro as you've always done.
on further research, I read incorrectly...
Esper editor Mishaal Rahman has reported that Google is now mandating virtual A/B partition support in Android 13.
Yep, A/B partitions are here for the long haul! Cheers
dilar said:
on further research, I read incorrectly...
Esper editor Mishaal Rahman has reported that Google is now mandating virtual A/B partition support in Android 13.
Click to expand...
Click to collapse
And yet Samsung hasn't implemented them even on the S23 series lol