yashsingh1/xdaforums huggingface dataset:
[Moto G40 / G60] arsradu:
That's weird.... Platform tools are from the Google's official page? Just checking.

If yes...then honestly I don't know.

Maybe @Raghu varma can help with an idea on this.
[Moto G40 / G60] xindefenggan:
Did you not clear the data before flashing the twrp?
[Moto G40 / G60] anuragnahata:
I cleared the data. Tried flashing it from another windows PC. It worked. Weird.
[Moto G40 / G60] xindefenggan:
AMD？
[Moto G40 / G60] anuragnahata:
Both Intel i5
[OPPO Find X5 Pro Questions & Answers] 1BDB1:
I am currently run the Chinese version on my find x5 Pro and hoping to change the to the global version. Is this possible?
[OPPO Find X5 Pro Questions & Answers] g1xx3r:
From what I understand, no.
[Touch Pro, Fuze General] mxl180:
I'm don't actually want to replace the screen. But I would like to get behind the screen so I can glue it down some.

My problem is the right side of the screen is not flush. It's a bit above the chrome. I kinda lifted it up when I was trying to pull off the screen protecter, but accident pull up the screen instead. I can press on it back down, but it goes right back up.

So I just want to be able to accesse the back/side of it and add a tiny bit of crazy glue to keep it down.

I took off the two screws from the back of the screen (nothing came off) ...nothing came loose.
[Touch Pro, Fuze General] FuzzyLogic_FC:
You're quite mad, you know. JK

Perhaps seeing one deconstructed would assist?

http://www.mikechannon.net/PDF Manuals/HTC Touch Pro - Camera removal photo guide v1.1 by A Mak.pdf

In case that doesn't work, it's from this site:

http://www.mikechannon.net/page1.html
[Touch Pro, Fuze General] darfri:
sorry for my reaction but this kind of shocking information combined with bad english feels really funny. I can almost imagine a VERY foreign guy talking really fast at nighttime on some alley in downtown and lashing with fuze like ti would be like an old Nokia brick.
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] toto6976:
hello

I am unable to enable 'adb sideload' mode on my twrp. it loops and ends up failing
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] Zanci19:
We need more information. Which version of TWRP are you using?
[LG G6 ROMs, Kernels, Recoveries, & Other Developme] toto6976:
Hello

I installed the following twrp version: recovery_h870_20180813-1.img
[General Questions and Answers] TheDuckWithAMonocle:
I seem to have stumbled across some vendor blobs for Xiaomi 9 (Cattail). I was wondering if this was usable to compile a workable kernel. if not, could anything be done with the source i am attaching?

GitHub - Vendor-Blobs/android_vendor_tree_xiaomi_cattail: Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0.RCTINXM

Redmi 9/9 Activ (cattail) - Android 11 - Vendor Tree - V12.5.6.0.RCTINXM - Vendor-Blobs/android_vendor_tree_xiaomi_cattail

github.com

Hopefully we could get something out of this
[General Questions and Answers] Droidriven:
Vendor blobs are part of what is needed to build custom ROMs. To build a kernel you need to find the kernel source code for your model number.
[General Questions and Answers] TheDuckWithAMonocle:
Would it be possible to use a similar but more popular device's build which has its source available, and modify it for my device?

I'm planning to do it as a hobby, so no rush
[General Questions and Answers] RedHood768:
From what i've seen in my research,there are quite a few people who are looking for 64 bit ROM's for cattail,but i suppose that this method might not be the most reliable since i've come across a lot of people reporting bricked devices cuz of it
[General Questions and Answers] sawxda:
Hi,

My android phone does not boot past the boot animation, and I wonder if anyone who understands android boot process could help me with an advice how to fix it.

What I observe is that the phone is stuck in boot animation. When I get shell through usb debugging, I observe that

there boot process repeatedly fails with messages

*** FATAL EXCEPTION IN SYSTEM PROCESS: main

10-08 08:58:59.211 919 919 E AndroidRuntime: java.lang.RuntimeException: There must be exactly one installer; found []

the UI is not starting;

the data partition is still FBE-encrypted.

(The way it got into this state is through some filesystem corruption, I believe -- the phone went into reboot for no reason, then immediately into another one, and became stuck as I described.)

My question is this: what is the main source of troubles?

How is it supposed to work, should the installer be found so that the boot process can continue, launch the UI, and allow to unlock the phone and decrypt data? Or should the UI be able to start first and clear the way so that the installer is found and boot continue? Or what?

My goal is to make the phone boot somehow without wiping the data.

The system is Android 9, and the logcat is attached

Any help would be appreciated
[General Questions and Answers] sawxda:
The logs
[General Questions and Answers] Renate:
/data should not be encrypted.

First, stop Android so you can see what's what.

# stop

Check what's up with /data and /acct. Are they there and sane?
[General Questions and Answers] sawxda:
Thanks for your response.

/data and /acct look ok to my not so experienced eye, /data/system and /data/app look ok as well, /data/data is encrypted.

Another suspicious message that I see in the logs is

10-08 08:58:58.480 919 1137 W SystemConfig: Got exception parsing permissions.
10-08 08:58:58.480 919 1137 W SystemConfig: org.xmlpull.v1.XmlPullParserException: Unexpected token (position:TEXT @1:2 in java.io.FileReader@9a2ce7f)
10-08 08:58:58.480 919 1137 W SystemConfig: at org.kxml2.io.KXmlParser.next(KXmlParser.java:432)
10-08 08:58:58.480 919 1137 W SystemConfig: at org.kxml2.io.KXmlParser.next(KXmlParser.java:313)
10-08 08:58:58.480 919 1137 W SystemConfig: at com.android.server.SystemConfig.readPermissionsFromXml(SystemConfig.java:394)
10-08 08:58:58.480 919 1137 W SystemConfig: at com.android.server.SystemConfig.readPermissions(SystemConfig.java:369)
10-08 08:58:58.480 919 1137 W SystemConfig: at com.android.server.SystemConfig.<init>(SystemConfig.java:296)
10-08 08:58:58.480 919 1137 W SystemConfig: at com.android.server.SystemConfig.getInstance(SystemConfig.java:180)
10-08 08:58:58.480 919 1137 W SystemConfig: at com.android.server.-$$Lambda$YWiwiKm_Qgqb55C6tTuq_n2JzdY.run(Unknown Source:0)
10-08 08:58:58.480 919 1137 W SystemConfig: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
10-08 08:58:58.480 919 1137 W SystemConfig: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-08 08:58:58.480 919 1137 W SystemConfig: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-08 08:58:58.480 919 1137 W SystemConfig: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-08 08:58:58.480 919 1137 W SystemConfig: at com.android.internal.util.ConcurrentUtils$1$1.run(ConcurrentUtils.java:62)
[General Questions and Answers] Renate:
Hmm.. Try this. Does every line look about the same, "xml version blah, blah"?

# cd /system/etc/permissions
# head -3 *

Variation is ok, gobble-dee-gook is not.
[General Questions and Answers] sawxda:
com.oem.feature.xml and a couple of other files start with <permissions> instead of <?xml>, but there is no obvious corruption anywhere. Looks unrelated to the main problem.

You say that the user interface should start and ask to unlock the phone, and afterwards the installer will be found and the boot process continues, right?

From user's perspective, the boot logo should get replaced by the wallpaper and the screen lock should appear asking to unlock.

Any ideas where to look why this is not happening?
[General Questions and Answers] Renate:
One of the problems with Android is that even when working properly the logcat is full of errors from half-baked apps.

Check /system/priv-app/PackageInstaller/PackageInstaller.apk

I don't know why Zygote takes it to heart if there isn't a viable package installer.
[General Questions and Answers] sawxda:
PackageInstaller is there and intact (compared with the ROM image)

Any thoughts why it could be not found?

Thanks
[General Questions and Answers] Renate:
# grep packageinstall /data/system/packages.xml
<package name="com.android.packageinstaller" ...
[General Questions and Answers] sawxda:
The entry in packages.xml looks like this

<package name="com.android.packageinstaller" codePath="/system/priv-app/PackageInstaller" nativeLibraryPath="/system/priv-app/PackageInstaller/lib" publicFlags="810040901" privateFlags="8" ft="11e908ff480" it="11e908ff480" ut="11e908ff480" version="28" userId="10010" isOrphaned="true">
<sigs count="1" schemeVersion="3">
<cert index="0" />
</sigs>
<perms>
<item name="android.permission.KILL_UID" granted="true" flags="0" />
<item name="android.permission.USE_RESERVED_DISK" granted="true" flags="0" />
<item name="android.permission.CLEAR_APP_USER_DATA" granted="true" flags="0" />
<item name="android.permission.INSTALL_PACKAGES" granted="true" flags="0" />
<item name="android.permission.FOREGROUND_SERVICE" granted="true" flags="0" />
<item name="android.permission.RECEIVE_BOOT_COMPLETED" granted="true" flags="0" />
<item name="android.permission.INSTALL_GRANT_RUNTIME_PERMISSIONS" granted="true" flags="0" />
<item name="android.permission.ACCESS_INSTANT_APPS" granted="true" flags="0" />
<item name="android.permission.INTERACT_ACROSS_USERS_FULL" granted="true" flags="0" />
<item name="android.permission.READ_INSTALL_SESSIONS" granted="true" flags="0" />
<item name="android.permission.REVOKE_RUNTIME_PERMISSIONS" granted="true" flags="0" />
<item name="android.permission.MANAGE_USERS" granted="true" flags="0" />
<item name="android.permission.MANAGE_APP_OPS_RESTRICTIONS" granted="true" flags="0" />
<item name="android.permission.CLEAR_APP_CACHE" granted="true" flags="0" />
<item name="android.permission.GRANT_RUNTIME_PERMISSIONS" granted="true" flags="0" />
<item name="android.permission.HIDE_NON_SYSTEM_OVERLAY_WINDOWS" granted="true" flags="0" />
<item name="android.permission.MANAGE_APP_OPS_MODES" granted="true" flags="0" />
<item name="android.permission.WAKE_LOCK" granted="true" flags="0" />
<item name="android.permission.UPDATE_APP_OPS_STATS" granted="true" flags="0" />
<item name="android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS" granted="true" flags="0" />
<item name="android.permission.DELETE_PACKAGES" granted="true" flags="0" />
</perms>
<proper-signing-keyset identifier="2" />
</package>
[General Questions and Answers] Renate:
@sawxda Ok, I think I know what's going on.

It's not loading all the permissions and therefore it has problems recognizing the PackageInstaller.

The unhelpful part of the bombing on XML is that it reports that the problem is with "java.io.FileReader@9a2ce7f".

A path would be more helpful.

I'm not saying that your version is up to master, but that code is:

https://android.googlesource.com/pl...java/com/android/server/SystemConfig.java#605

It's loading from a ton of places.

Here's a minimal version of the code, you can check all the directories with that head -3 *

Path(Environment.getRootDirectory(), "etc", "sysconfig")
Path(Environment.getRootDirectory(), "etc", "permissions")

Path(Environment.getVendorDirectory(), "etc", "sysconfig")
Path(Environment.getVendorDirectory(), "etc", "permissions")

Path(Environment.getVendorDirectory(), "etc", "sysconfig", vendorSkuDir)
Path(Environment.getVendorDirectory(), "etc", "permissions", vendorSkuDir)

Path(Environment.getOdmDirectory(), "etc", "sysconfig")
Path(Environment.getOdmDirectory(), "etc", "permissions")

Path(Environment.getOdmDirectory(), "etc", "sysconfig", skuDir)
Path(Environment.getOdmDirectory(), "etc", "permissions", skuDir)

Path(Environment.getOemDirectory(), "etc", "sysconfig")
Path(Environment.getOemDirectory(), "etc", "permissions")

Path(Environment.getProductDirectory(), "etc", "sysconfig")
Path(Environment.getProductDirectory(), "etc", "permissions")

Path(Environment.getSystemExtDirectory(), "etc", "sysconfig")
Path(Environment.getSystemExtDirectory(), "etc", "permissions")

Path(Environment.getApexDirectory(), "etc", "permissions")

OR

You can pull a copy of /system/framework/framework.jar

Then apktool d it.

Then find SystemConfig.smali in the disassembled directory and post it for me.

*Or if you're lazy, just post the whole jar. :p
[General Questions and Answers] sawxda:
Hi @Renate ,

I extracted SystemConfig.smali from framework.jar, it is attached. Thanks!
[General Questions and Answers] Renate:
@sawxda Thanks, that's what I wanted.

The first line of some XML in /system/etc/sysconfig/ is bad.

I'm not guaranteeing that this is your main problem, but it is bad.

Why? The log shows that ".line 296" (the second occcurrence at line #533 of the smali) is where.
[General Questions and Answers] sawxda:
@Renate : thanks a lot for checking.

Unfortunately, it seems that the message about permissions is really unrelated: there was one file in that directory that got a unicode byteorder mark at the beginning, and when I remove it, the error message in the logs disappears but the system is still unable to boot in the same way.

Any other thoughts?

I also notice that there are messages

PackageManager: There should probably be exactly one storage manager; found 0: matches=[]
PackageManager: There should probably be exactly one setup wizard; found 0: matches=[]

besides the fatal one about the installer. So, it looks that there is some general problem in finding the pieces, but it is not the permissions that we suspected.

Your help is much appreciated, please let me know if you have other ideas about what might go wrong or where to look.
[General Questions and Answers] Renate:
You didn't say what file. Did it have anything to do with PACKAGE?

That file was being completely ignored before. How could it not make a difference?

Was it some vendor file or something?

It's having trouble finding recipients for Intents.

It could be that a number of things, but it's not easy to figure out if it keeps crashing.
[General Questions and Answers] sawxda:
Sorry, it was dialer_experience.xml , and I suspect that the ROM uses a different dialer that does not need it.

I just checked is that fixing the xml file eliminates the error message but does not affect the inability to boot, and that prompted me to say that the problem is somewhere else.
[General Questions and Answers] Renate:
Try this, between it crashing:

# am start -a android.intent.action.INSTALL_PACKAGE -d content://example/foo.apk
Starting: Intent { act=android.intent.action.INSTALL_PACKAGE dat=content://example/foo.apk }
[General Questions and Answers] sawxda:
# am start -a android.intent.action.INSTALL_PACKAGE -d content://example/foo.apk
cmd: Can't find service: activity

From what I understand from the logs, ActivityManager starts from Zygote, and but Zygote quickly exits with the fatal error about exactly one installer, so I cannot really access it. A loop in the shell "while :; do am start ..." does not help
[General Questions and Answers] Renate:
@sawxda I dunno.

Post your /system/framework/services.jar
[General Questions and Answers] sawxda:
@Renate : here it is. Thanks a lot!
[General Questions and Answers] Renate:
@sawxda Try replacing your services.jar with this.

I hope that it will boot further.

You may not be able to install or uninstall anything, but you might have a chance to troubleshoot further.
[General Questions and Answers] sawxda:
@Renate : thanks for sending the replacement jar to try.

The boot process is still stuck at boot animation and with encrypted data.

The main error message now is

10-12 07:43:24.469 1286 1286 E System : ******************************************
10-12 07:43:24.469 1286 1286 E System : ************ Failure starting system services
10-12 07:43:24.469 1286 1286 E System : java.lang.RuntimeException: Unable to find android system
package
10-12 07:43:24.469 1286 1286 E System : at com.android.server.am.ActivityManagerService.setS
ystemProcess(ActivityManagerService.java:2867)
10-12 07:43:24.469 1286 1286 E System : at com.android.server.SystemServer.startBootstrapSer
vices(SystemServer.java:706)
10-12 07:43:24.469 1286 1286 E System : at com.android.server.SystemServer.run(SystemServer.
java:467)
10-12 07:43:24.469 1286 1286 E System : at com.android.server.SystemServer.main(SystemServer
.java:314)
10-12 07:43:24.469 1286 1286 E System : at java.lang.reflect.Method.invoke(Native Method)
10-12 07:43:24.469 1286 1286 E System : at com.android.internal.os.RuntimeInit$MethodAndArgs
Caller.run(RuntimeInit.java:495)
10-12 07:43:24.469 1286 1286 E System : at com.android.internal.os.ZygoteInit.main(ZygoteIni
t.java:839)
10-12 07:43:24.469 1286 1286 E System : Caused by: android.content.pm.PackageManager$NameNotFound
Exception: android
10-12 07:43:24.469 1286 1286 E System : at android.app.ApplicationPackageManager.getApplicat
ionInfoAsUser(ApplicationPackageManager.java:395)
10-12 07:43:24.469 1286 1286 E System : at android.app.ApplicationPackageManager.getApplicat
ionInfo(ApplicationPackageManager.java:377)
10-12 07:43:24.469 1286 1286 E System : at com.android.server.am.ActivityManagerService.setS
ystemProcess(ActivityManagerService.java:2850)
10-12 07:43:24.469 1286 1286 E System : ... 6 more

Why can't the packages get found? Any ideas?

(Attached is a new logcat for a boot with your services.jar.)
[General Questions and Answers] Renate:
@sawxda Well, the package "android" is /system/framework/framework-res.apk

Is that missing/corrupted? Pull it and apktool d it for sanity.
[General Questions and Answers] sawxda:
@Renate I've just verified md5sums of all apk's and jar's under /system relative to the ROM image and all the files are ok.
[General Questions and Answers] Renate:
@sawxda That's pretty thorough.

Somehow the PackageManager is not registering the package "android".

That's a pretty drastic failure.

If you had a stable system you could pm list packages (but you don't).

In ye olde days you could delete /data/system/packages.xml and it would regenerate.

I'm not sure if that's the case now.

# grep 'package=\"android\"' /data/system/packages.xml

Does that give you ~500 lines?

Do you have TWRP or something that can do an update (even if it's the same version)?
[General Questions and Answers] sawxda:
# grep 'package=\"android\"' /data/system/packages.xml | wc -l
465

I do have TWRP, but I also have magisk installed on top, and I do not think that doing an update without uninstalling magisk would do any good.

BTW, magisk and the loss of some of its files could be a source of the current troubles, but I do not see any evidence to that the logs. The filesystem also looks good from the adb shell, /system is in place, there are messages like

10-12 18:21:32.101 923 923 I PackageManager: Finished scanning system apps. Time: 181 ms, packageCount: 206 , timePerPackage: 0 , cached: 215
10-12 18:21:32.199 923 923 I PackageManager: Finished scanning non-system apps. Time: 98 ms, packageCount: 65 , timePerPackage: 1 , cached: 65

that confirm that it is not the case that everything is ruined.
[General Questions and Answers] Renate:
# cat /data/system/packages.list|sort|more
android 1000 0 /data/system platform:privapp:targetSdkVersion=28 1065,3002,1023,1015,3003,3001,1021,1000,2002,1010,1007 0 29
...

You can save a copy of /data/system/packages.xml and delete it.

For these kind of experiments stop and start should be sufficient.
[General Questions and Answers] sawxda:
@Renate : It seems that we've found something.

My packages.list contained

android 1000 0 /data/system platform:privapp:targetSdkVersion=16 none

so the groups were lost. (They were also lost in all other packages, not only for android.) This file is regenerated from packages.xml, so editing it does not change anything.

Then I deleted packages.xml, and it indeed was regenerated, but

- groups are still missing in the packages.list

- moreover, in the regenerated packages.xml, the packages got new random uids, so they no longer match the filesystem.

Any suggestions about how to proceed?

Thanks
[General Questions and Answers] Renate:
$ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc),3011(uhid) context=u:r:shell:s0
$ su
# id
[General Questions and Answers] sawxda:
@Renate :

In the current state of the system, adb gives me the root shell immediately

# id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r
),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc),3011(uhid) context=u:
r:su:s0
[General Questions and Answers] Renate:
If it weren't for that "none" I'd just think that you had a different version than the random device that I was using.

You can do an update without uninstalling Magisk if all your mods were through Magisk.

You'll be unrooted again.
[Samsung Galaxy A52s 5G] Stonos:
Anyone else getting random reboots/freezes on their A52s?

For me, this is what usually happens: The phone freezes for 2-3 seconds (usually without me doing anything demanding like gaming or using the camera), and then it usually does a full reboot (which goes to the bootloader screen that tells me that my bootloader is unlocked), or a soft reboot (that is just the Android boot screen). After it finishes booting, it's very likely that the same thing will happen again within 1-2 minutes. Afterwards, the phone is fine for 1-2 days until it does the reboot thing again.

Very rarely the phone just freezes without rebooting, and I have to turn it off by holding down all the buttons for a few seconds. I've also seen my phone reboot by itself while it was idle on my desk.

It's a very annoying issue that has caused me to lose a picture I had just taken. It could also cause me to lose an important phone call (since I have to enter my PIN after each reboot).

Anyone else having the same issue? I've found a few posts on Reddit mentioning this, but no one has found a solution, and I haven't seen anyone talk about it here.
[Samsung Galaxy A52s 5G] bobfrantic:
I've never had this issue ever even with the various rom and firmware installations. Did this happen out of the box, after installing something, or just start up out of the blue one day?
[Samsung Galaxy A52s 5G] Marvin.the.Martian:
Never, but my bootloader isn't unlocked.
[Samsung Galaxy A52s 5G] gerhard_wa:
I have had this phone since it came out and it has never rebooted on its own or frozen up on me, not even once.
[Samsung Galaxy A52s 5G] zate27:
Yes I have it too and I didn't find out why, even with logcats. It's happened to my friend too but sometimes it stops for a while and then a month later it starts again.
[Samsung Galaxy A52s 5G] wwwsam:
Same problem with my A52s.

I think it happens more often when it is warm.

It's almost like a power brown out.

On one of the reboots, there was a "microsd read error" (or something along those lines) so I removed the microsd. So far it has been working great. The microsd is a Samsung 512GB Evo plus (2021) I baught with the phone from samsung store.

I am so far testing the microsd and it seems it is faulty (extremely slow rear/write speeds after it is filled toa certain capacity)

Only time will tell if this is the problem.