Is it possible for us to get Huawei's EROFS File System on our OP 7 Pro ? It seems it's actually more important than ufs 3.0. https://www.youtube.com/watch?v=TaKC1qIlo9Y
Maybe it's going to take months until such ROMs come but IS IT POSSIBLE ? (or its a proprietary Huawei thing that u cannot copy ... like Apple's iOS ?).
Related
Xiaomi Redmi Note 4 got full support for project Treble..
Here is the link of the news
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Our kernel has released..I think we can do that too..
I would request our developer to work for this project...
https://forum.xda-developers.com/re...ment/rom-lineageos-15-0-t3690465/post75527103
---------- Post added at 10:44 PM ---------- Previous post was at 10:43 PM ----------
He has also mentioned about the goodix fp fix too.
This is not possible on Mi A1 (AT Least using the method described in the link) because Mi A1 has stock Android, not MIUI. MIUI needs the cust partition. Unless someone reformats the interval drive entirely and makes a new partition layout then it's not possible.
konradit said:
This is not possible on Mi A1 (AT Least using the method described in the link) because Mi A1 has stock Android, not MIUI. MIUI needs the cust partition. Unless someone reformats the interval drive entirely and makes a new partition layout then it's not possible.
Click to expand...
Click to collapse
Agree, we need to repartition our internal storage. Here's the guide for how to do that for previous Android One phones that were released in 2014 I think.
https://forum.xda-developers.com/cr...uide-repartition-internal-storage-to-t3292159
According to this post when we shrink a partition, all the data inside it will be lost. Now what I think is that we could try shrinking userdata partition as its of ~51G. If we take out 1GB from it, we won't be loosing much space and also we won't be touching other partitions so they shouldn't get corrupted.
Why OEM didn't do it?
1. There was a high risk of phones getting bricked if they would've tried re-partitioning device via OTA (atleast that's what Nokia and OnePlus said).
2. And also according to Google's CTS, " The update mechanism used MUST support updates without wiping user data. That is, the update mechanism MUST preserve application private data and application shared data.
It can be done with out repartition.... we alread have A/B partition can use either of those pertion as a vender pertion maybe
I would like to keep the A/B partitions but I could sacrifice some of space from user data for this.
I don't actually think we as Mi A1 users need it çause we allready got android one so that's fast updates
Hi, a couple of days ago ArsTechnica reported a 0-day vulnerability with a fully disclosed PoC for root privilege escalation on MiA1 devices and more... I was wondering if it could be used to create a gcam activator without all the hassles of temporary rooting and rebooting with the volume key and never booting into recovery again unless you want a data wipe. Is there anyone with the required skills to try this out?
Found this today:
https://arstechnica.com/information-technology/2019/10/attackers-exploit-0day-vulnerability-that-gives-full-control-of-android-phones/
Should A1 owners be worried?
I think it can be patched in a custom kernel, if it isn't already.
Niyix said:
I think it can be patched in a custom kernel, if it isn't already.
Click to expand...
Click to collapse
I'm not worried about the vulnerability (it will get patched, eventually) - quite the opposite! I think that it could be extremely handy to enable the Camera2 API without having to root with TWRP/tools and risking a device wipe. I can't post the actual exploit proof of concept because I'm a new user here, but the code is reachable from the project zero bug report. Running a process with root privileges would make writing the extra props in the build.properties file way easier. Of course I'm not an Android dev and I could be wrong in many ways... that's why I was asking here.
If you are on Pie, you are safe.
The original bug entry states that it affect Oreo:
...
Other devices which appear to be vulnerable based on source code review are (referring to 8.x releases unless otherwise stated):
1) Pixel 2 with Android 9 and Android 10 preview (https://android.googlesource.com/kernel/msm/+/refs/heads/android-msm-wahoo-4.4-q-preview-6/)
2) Huawei P20
3) Xiaomi Redmi 5A
4) Xiaomi Redmi Note 5
5) Xiaomi A1
...
Click to expand...
Click to collapse
Hi Folks,
I just bought a new device and the seller was nice enough (doh!) to install Android 10 on it. The known way to root up to Android 9 on PX5 and PX6 devices[1] would work here too it seems, at least with minor modifications. I guess the partitions layout, fs-overlay and... stuff... did change a bit, but it was rather straight-forward to implement nevertheless. Enabling ADB over WIFI, adb connect, adb shell remount / and /system rw, moving old su, pushing new su, su --install, pushing SuperSU.apk, correcting permissions, reboot and the system bugs about "app might be for an older version of android, it might not work correctly" and right, nothing root related works. It is like all root requests end in a nirvana and no error messages are generated.
So my guess would be that just a newer su-binary or newer SuperSU.apk (or both) it might just work. I know chainfire left the supersu-team but I am unsure about the implications. Advice here? What about Magisk? I really don't care, I just need root for some apps and general tinkering here and there. Any help appreciated.
regards
UnsettledSoul
[1] https://forum.xda-developers.com/android-auto/mtcd-android-head-units-general/how-to-root-px5-hu-android-9-0-t3940327
EDIT: here is a rooting tool for px6 https://github.com/KswCarProject/KswRooting
Were you able to figure this out? I just bought a px6 android 10 unit since it was a decent bit cheaper than the ones advertising android 9. https://www.aliexpress.com/item/4001090563068.html?spm=a2g0s.9042311.0.0.398a4c4dP5ASrt
Ideally I would like to downgrade to either the Malaysk or Hal9k_ pie roms until a cleanded and optimized android 10 rom is released.
moosefist said:
EDIT: here is a rooting tool for px6 https://github.com/KswCarProject/KswRooting
Click to expand...
Click to collapse
That's basically the same recipe for rooting PX* on Android 9, but crappier implemented (overwrites stuff without creating a backup first). It is no tool, it is just some adb commands gobbled together in a DOS/Windows batch-file, accompanied by Windows-adb-binaries and an arm64 su-binary. Nothing I need. Nothing I don't already have. The su-binary is even identical to the one shipped with the rooting-package for Android 9. The one thing I do need is missing: superuser.apk that actually works on Android 10. Or how does one manage root-access for apps afterwards? At least the guy claims his "package" works on Android 10, so that might be an indication that the su-binary is sane and sound, one thing I can scratch from the bucketlist to get root.
Really weird mix of stuff. No idea if the guy is trustworthy, but mixing the adb-binaries in looks... weird.
Were you able to figure this out? I just bought a px6 android 10 unit since it was a decent bit cheaper than the ones advertising android 9. https://www.aliexpress.com/item/4001090563068.html?spm=a2g0s.9042311.0.0.398a4c4dP5ASrt
Click to expand...
Click to collapse
Figure what out? And at least for me, I don't hunt for cheap, I hunt for good support. That's why I payed almost 400€ for a PX6 device, just to get better support.
Ideally I would like to downgrade to either the Malaysk or Hal9k_ pie roms until a cleanded and optimized android 10 rom is released.
Click to expand...
Click to collapse
Same here. I asked the seller if he can provide an Android 9 firmware for my device and I am sure he will provide it. Then I can see if I go Malaysk again or stay stock for the moment.
Hello. I own Ownice Android 10, MTCP-OLS-PX6. After all, isn't there a valid rooting method so far?
Has anyone succeeded installing the Global rom of Realme 5 Pro on Realme Q(chinese vesion)?
I just flashed the Pixel Experience Plus rom which I downloaded from their official website. It was supposed to be for Realme 5 Pro but working just fine on my Realme Q. I was wondering if could do the same with the Global rom.
munna567 said:
Has any succeed installing the Global rom of Realme 5 Pro on Realme Q(chinese vesion)?
I just flashed the Pixel Experience Plus rom which I downloaded from their official website. It was supposed to be for Realme 5 Pro but working just fine on my Realme Q. I was wondering if could do the same with the Global rrom
Click to expand...
Click to collapse
You can't. Been experimenting since last October. Realme 5 Pro has bigger system partition size. Meaning global version can take a ****load more of preinstalled apps on system that user can't remove and Realmeme uses it throughoutly. That's pretty much the only real difference between Realme Q and Realme 5 Pro. That's why global ROM size is much bigger and that's why you can't flash it on Realme Q which has smaller system partition. Unlike xiaomeme devices changing ROM from China to global because of this isn't possible as of now. I recommend to stick to custom ROMs so do I.
greenys' said:
You can't. Been experimenting since last October. Realme 5 Pro has bigger system partition size. Meaning global version can take a ****load more of preinstalled apps on system that user can't remove and Realmeme uses it throughoutly. That's pretty much the only real difference between Realme Q and Realme 5 Pro. That's why global ROM size is much bigger and that's why you can't flash it on Realme Q which has smaller system partition. Unlike xiaomeme devices changing ROM from China to global because of this isn't possible as of now. I recommend to stick to custom ROMs so do I.
Click to expand...
Click to collapse
Is it possible to change the partition size?
munna567 said:
Is it possible to change the partition size?
Click to expand...
Click to collapse
Some has been experimenting with it. Yes, it is. However if you increase system partition size you'll have to decrease some other partition size which are about just enough to store their data. So overall you won't be able to increase system partition size without losing for example vendor or other partition making ROMs unusable.
greenys' said:
Some has been experimenting with it. Yes, it is. However if you increase system partition size you'll have to decrease some other partition size which are about just enough to store their data. So overall you won't be able to increase system partition size without losing for example vendor or other partition making ROMs unusable.
Click to expand...
Click to collapse
What if I change every partition size to make it exactly same as Realme 5 pro's?
munna567 said:
What if I change every partition size to make it exactly same as Realme 5 pro's?
Click to expand...
Click to collapse
I don't think that's possible for you've limited space to use. However if you could somehow take a bit of storage from internal and increase system partition with it maybe it could work. Anyhow that's way over me and I don't know it can be done or not.
Hello
I will perhaps keep my S22U instead of upgrading to s23u , I will then most probably root it as my warranty will soon come to an end and I won't care about knox flag. But is there any AOSP based custom rom for the S22U snapdragon ? If yes can you use Expert Raw app?
The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.
V0latyle said:
The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.
Click to expand...
Click to collapse
Thanks
Though it looks like an update thread for Pixel phones no?
vegetaleb said:
Thanks
Though it looks like an update thread for Pixel phones no?
Click to expand...
Click to collapse
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com
V0latyle said:
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?
vegetaleb said:
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?
Click to expand...
Click to collapse
I don't think so - I'm pretty sure features like that are not core Android mechanics, so they wouldn't be included in AOSP. I don't know for sure. Keep in mind that the whole idea behind a GSI - Generic System Image - is that it can run on pretty much any device. Google has been using this model since the Pixel 3 - instead of having different system builds for each device, they use a generic common system image, while device specific features are contained in other partitions such as /product. This way, when they provide the monthly update for Pixels, they don't have to completely rebuild the firmware; they can just use the AOSP GSI for the "core", and any device specific changes are separate in /system_ext and /product. It's a modular design that really helps streamline the update process; it also means that devices that no longer receive updates can still potentially run the latest AOSP core.
I imagine you could extract the product.img from the Pixel 7 factory zip and flash it to /product on your device, but because it's device specific, it most likely wouldn't work properly.