Search results

Title is self explanatory.

I wouldn't trust these "custom kernels". A lot of times these custom kernels you haven't ever heard about have security features disabled, have dangerous features enabled that affect the longevity of the device and putting malware to a kernel is really easy.

I have heard quality complains about Umidigi (sorry I don't remember where). And a lot of these small companies intentionally make it hard for any user modification. They use MTK chipsets and don't publish the kernel source code as required by the GPL.

Yes it is possible. I don't know how lg has it implemented or what phone he is using, but there are multiple users in android that you can switch. If lg doesn't have that feature it could be done with a system modification. Since this a real life trust problem I suggest that you talk to somebody...

1. Basic android knowledge, some basic android development knowledge (AlaskaLinuxUser has great guides and explanations for this, he covers everything you need. https://www.youtube.com/c/AlaskaLinuxUserAKLU ), you don't have to know a programming language, but it will be useful. Basic skills...

Keep in mind that the OP8 Pro is a high end phone and the Pixel 5 is something like a mid range flagship. You are getting a worse SoC (cpu, gpu), slower storage, less ram and storage depending on the model, slower charging, less refresh rate, etc. See...

That is not the actual error. That message is not useful.

I might be able to help. The kernel source is missing, but there are some device trees for other mt6580 phones. I will try to craft a device tree for this phone. For now i need these things: 1. The android version. 2. raw dd'ed boot image of the device 3. raw dd'ed system image of the device

kernel source?

So an AOSP kernel won't work with CAF?

Why does this ROM use the 4.4 kernel when 4.14 is available for Nile?

Just a reminder that using a ROM with permissive selinux is not a good idea. https://android.stackexchange.com/questions/149854/how-dangerous-is-the-fact-that-selinux-is-in-permissive-mode-what-should-i-be

You can build even on 8GB. It will just build slower. I know a person who was able to build cm-14.1 with 4GB of RAM, but it took like a whole day to do so. It depends in what you do, but most of the times you must build it to be able to use it. Otherwise you will have to resort to tricks like...

You found that phone? If it's not yours you should find the owner instead of trying to unlock the phone. Just imagine if this happened to you. If you are doing the right thing, try to see if the owner put some of his information to the emergency information of the device. When the phone is on...

Is AVB enabled?

Grab a logcat

AlaskaLinuxUser has made tutorials about building roms and his videos are very beginner friendly. See his youtube channel https://www.youtube.com/channel/UCnGqG_jyyXmTzdamBpKfeHA His XDA thread about his tutorials...

You can run logcat in adb See : https://developer.android.com/studio/command-line/logcat Also you can install a logcat app like MatLog to get logs without a computer (requires root). That might give you a hint to why the wifi doesn't work. If the logcat doesn't show anything that would...

That's not true when you are flashing a Generic System Image.

The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img" See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983

Just don't, you will probably brick your phone https://www.xda-developers.com/flash-miui-global-locked-bootloader-xiaomi-brick/

Huge security risk to have it disabled. https://wiki.gentoo.org/wiki/SELinux

I know all of this. Also the things I said were not questions, but facts. Just look at this fstab. https://github.com/TeamWin/android_device_xiaomi_mido/blob/android-8.1/twrp.fstab#L6 It is mounted as emmc to get the full partition backup.

By this you mean that in twrp you see both a "system" and a "system_image" partition? The system one is the system and the system_image is exactly the same, but instead mounted as emmc instead of ext4.

Wrong! fastboot/adb is made by google, thus it works on Google phones. And a lot of times you can get fastboot and adb to work with generic drivers from google. ---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ---------- @ayewilling On what rom did you lock the...

1. You don't have the device trees, you just have the common trees. 2. I don't see you specify the remotes. 3. You also don't specify the revision here in the manifest you pasted here. 4. The t124 lineageos repo doesn't have a cm-14.1 branch. See...

LuK1337 By WFD you mean Wi-Fi direct or Wi-Fi display?

It doesn't work because the a7 pro has a super partition which is actually just a system partition. It's a system partition, but masked as something else. They even put fake mounting points to the fstab to make it look like it's in fact a super partition phone. The real mounting occurs somewhere...

You can find development thread on this forums, but there is not a lot of them and it takes time to find them. The best xda thread about Android development I have found is this one by alaskalinuxuser...

Bump

Bump

Can you explain in detail what that means? The post states that it uses the prebuilt stock kernel from the miui rom. He also gives a download link to the miui rom where the kernel is taken from.

A device tree would be extremely helpful to people wanting to build AOSP 11 or base their tree of your device tree. abhishek987

You can compare the changes done to a kernel that was built for the same SoC as your phone does. Then you cherry pick the changes. Example Old kernel : https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mido-n-oss Newer kernel : https://github.com/LineageOS/android_kernel_xiaomi_msm8953...

Kernel source?

You can't customize Oxygen Os as the source code doesn't exist for that. (It's not required for companies to publish that.) What phone do you have? You already might have the required trees to build AOSP (or at least LineageOS) You need 1. A Device Tree 2. The kernel (you can use the...

Stop commenting on something you have no idea about. You either don't know how magisk works or you are just deceiving. You either have a personal problem with magisk or just don't know about the matter. The same goes for the person above you saying the same like you do.

priyabrat MI Can you add kernel and device tree? The MiCode kernel is not enough as you made changes to it. When you make changes to a kernel and include that in anything that is available to anyone else except you, you are then obliged to provide the kernel source code. You can see that I'm...

You can use a feature called magisk hide. It bypassed multiple forms of root detection. I have used it before and no app was able to detect root. See screenshots below.

Nobody said that magisk hides the su binary in system. As you know magisk is system-less meaning it resides in the boot image. The only place where it isn't in the boot image is in sbin and /data. It hides itself, no need to hide something that doesn't exist. There is no su binary in /system...

If you are using magisk you can use a feature called magisk hide. For more info you can look here https://github.com/topjohnwu/Magisk/issues/1152

This means that all of the /system not mounting could just be fixed by mounting the super as a /system, but the location of the vendor partition still unknown (from my knowledge it could be the cache partition, you will have to dd that too to be sure.

Is it a super or just a system please?

Don't post questions into the development section. There is a separate section for that. The XDA rules which you should have read before posting don't allow posting questions here.

It doesn't matter if it has or hasn't got a recovery partition. To get more info about making the twrp device tree you can look here. https://www.youtube.com/playlist?list=PLRJ9-cX1yE1lnwTD8QP_e5Ohj8Ys-0oO7&app=desktop

So you must first get the super partition. To do that you can dd the super by doing this in adb This will copy the super partition to your internal storage. Make sure you have a lot of space as this might take like 10 gigs if it's an actual super partition and not just a fake one. You can the...

Yes, it's possible. You can do it by removing these file under system/etc If your phone has a vendor partitions remove those files both under system/etc and vendor/etc The files to delete flp.conf gps.conf gps.cfg izat.conf lowi.conf sap.conf xtwifi.conf Make a backup of these files before...

Does that mean that you could dd the bootloader and reverse engineer it somehow to get the public key? Also what do you mean by "chain of trust" if that means the verification process then why does (or what does it exactly mean) it start from the PBL when it verifies the extended bootloader...

Does anyone know what's inside the extracted super image of the F2? I extracted the the A7 Pro super image and it looks like it's only a system partition. If it's only a system on the A7 Pro it could even be on the F2. I'm not really surprised that umidigi does this (you can't find a single...

What's inside those folder. What type of file and extension?