yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] Forgivetr:
Enreto is a blog app that allows you to read different articles for different topics. We are constantly writing qualified articles for you. With all features of Enreto, we are working hard to provide best user experience.

You can share your ideas in an article by signing up. After you sign up, you can write posts to article, discuss with other users. You can add an article to favorites, share with your friends.*

For now there are 4 categories in Enreto: Personal Development, Serial Killer, Telekinesis and Interesting Facts. In time, we will add new articles and new subjects according to your requests.

Features:

* Constantly added articles

* Various categories

* Search what you wonder about

* Favorite articles

* Popular articles sorted by day, week, month or all time

* User login system, you can share your ideas

Link: https://play.google.com/store/apps/details?id=grkn.ctk.enreto

[IMG="im1"]https://i.hizliresim.com/zJajDg.png[/IMG]

[IMG="im2"]https://i.hizliresim.com/V3P97R.png[/IMG]

[IMG="im3"]https://i.hizliresim.com/6yraBk.png[/IMG]
[Android Apps and Games] Forgivetr:
New articles was added, you can read in Enreto.
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
guys i need support , i want to downgrade my sony from 7.1.1 to 6.0.1 to root and backup that key but i ended up twice with

ERROR - Processing of system.sin finished with errors.

please help , i cant find anything usefull than extract that file and install it , but that wont work if i soft brick it
[Sony Xperia X Performance Questions & Answers] f870103:
Do you use the latest Flashtool(0.9.23.2) to flash the FTF file?

If yes, sometimes just flash FTF again right after error occurs may fix the problem.
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
its sloved, it seems it was a corrupt fileso i dled the koran ver and that worked, thx , the only problem is back up ta, i cant find out howto without losing the drm kry,

i watched a couple youtubes, i readed a few guides but nothing is clear enough how to , i got that script but it say device not found , i tried in dwonload mode and local charging mode
[Sony Xperia X Performance Questions & Answers] f870103:
Use this tool to backup your TA partition.

You need to backup it in Android system with adb access, not Download mode or Flash mode.

To check if your computer has adb access, simply type "adb devices" in the command window.
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
i installed adb and drivers and alot other stuff to get it to work like flashtool and so , but can't seems to get it to work, best i could do is rollback rom

thats why i asked if someone can pass me a guide i can folow and understand, because simple im missing something

i never had it this hard with samsung

would be nice if i had more support on this mather
[Sony Xperia X Performance Questions & Answers] f870103:
I see you have enabled ADB on your device, and connected to your computer. But ADB did not find your device.

Maybe you should re-install your adb driver.

You can download ADB Installer by [MENTION=4638083]Snoop05[/MENTION] here.

After installing ADB driver correctly, you should see your device on adb device list.
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
i get more details now, so am i good now ?

-edit guess not
[Sony Xperia X Performance Questions & Answers] f870103:
It's "adb deviceS" not "adb device".
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
oops my bad lol i simply copy pasted missed s

but still not able to see phone i guess ?
[Sony Xperia X Performance Questions & Answers] f870103:
Yes. adb still can't find it. Did you try ADB Installer I mentioned before?
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
uhuh i did,

but i did not install it as admin so i tried again and i guess i have a result now

but in ta still no device found
[Sony Xperia X Performance Questions & Answers] f870103:
Just type "adb devices" again.
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
i did after reinstall, adb devices, go to ta folder and pressed the bat file and error device not found while adb see it right ?

-edit, i tried again this time in 1 windows but same result
[Sony Xperia X Performance Questions & Answers] f870103:
Well, try another installer in the attachment.
[Sony Xperia X Performance Questions & Answers] Wesley_NL:
still not T.T something is blocking it probaly ?

maby the android studio ? although i removed the google driver and reinstalled that adb driver but no luck
[Sony Xperia X Performance Questions & Answers] f870103:
I've PM you for the problem.
[Moto G Q&A, Help & Troubleshooting] enzo.robaina:
I'm in need of a complete /persist folder, mine got corrupted after an unsuccessful flash.

I would really appreciate if someone could zip it and upload it to me.
[Galaxy Note 4 Q&A, Help & Troubleshooting] bigheart90:
i installed it via recovery xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125

and after i open the xposed installer it show active so i press on install/upgrade v88 then device bootloop so i uninstall it

my rom sixperence ported note 5

becuase this port it install other firmware?!

my phone N910H 5.1.1

how to install it

thanks.
[One (M9) Q&A, Help & Troubleshooting] xangma:
Hi all,

I have been trying to boot LineageOS 15 on the One M9 as I think they have it booting on the M8.

By searching through github and looking at the M8 changes, I have managed to pull a bunch of trees together and complete a build, but it does not boot. It does not get past the bootloader to even get to the boot animation.

The roomservice.xml I am using is shown below:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_htc_himaul" path="device/htc/himaul" remote="github" revision="cm-14.1" />
<project name="me2151/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" revision="lineage-15.0" />
<project name="me2151/android_kernel_htc_msm8994" path="kernel/htc/msm8994" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.0" />
</manifest>

And I've had to change the .repo/manifest.xml a bit to include these revisions:

<project path="hardware/qcom/audio/default" name="LineageOS/android_hardware_qcom_audio" groups="qcom,qcom_audio,pdk" revision="lineage-15.0-caf-8994" />
<project path="hardware/qcom/display" name="LineageOS/android_hardware_qcom_display" groups="pdk,qcom,qcom_display" revision="lineage-15.0-caf-8994" />
<project path="hardware/qcom/media" name="LineageOS/android_hardware_qcom_media" groups="qcom,pdk" revision="lineage-15.0-caf-8994" />

I've also had to change a bunch of /vendor/cm/ to /vendor/lineage as said in this post. I might have changed some other things (I seem to remember there was an issue in framework/core/res/res/values.xml or something where some strings relating to rebooting weren't defined ...)

Anyway, any ideas as to how to proceed? None of the logs are showing any kernel activity, only when it boots into the bootloader do I get any kind of logs. I've gone through all the logs in /devlog and there's nothing =[

EDIT:

This build is currently bootlooping, but adb is working. The guide of how I got this far is in this post.

EDIT2:

This rom is currently booting, but camera is broken, selinux is in permissive, and there's probably a load of errors floating around in adb that I don't really have time to solve =[ The link for this build for LineageOS 15.0 GSM/himaul is in THIS POST.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Maybe you can post a link to the source? or the build?
[One (M9) Q&A, Help & Troubleshooting] xangma:
Yay, a reply!

So the sources I'm using are:

/me2151/android_device_htc_hima-common

/me2151/android_kernel_htc_msm8994

/TheMuppets/proprietary_vendor_htc

Then the normal LineageOS 15 sources, except the -caf-8994 ones for qcom_media, qcom_display, and qcom_audio.

I've noticed the generated boot.img is ~10mb smaller than the one I built from the LineageOS 14.1 sources. I'm thinking this might be the problem, but I don't hugely know where to go next. I unmkbootimg'd the boot.img, and the ramdisks are around the same size as in LOS 14.1 , but the zImage's are very different. I can upload the build if you want, but it doesn't boot or even boot the kernel in normal mode to log anything.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Can you post the rom or send it as pm? I want to test something if it's possible...
[One (M9) Q&A, Help & Troubleshooting] xangma:
Yeah no problem. I'll just try to revert some changes that didn't work before I upload (might take a few hours). I'm also going to try a clean rebuild tonight too.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Ok, let me know your progress, I want to test builds and help with what I can...

And about smaller zImage maybe it's just a compilation error or missing some things from kernel source...
[One (M9) Q&A, Help & Troubleshooting] xangma:
Yeah I'm thinking that's the case. Now I just have to learn how the kernel gets built to compare it to LOS 14.1 and the M8.

Sounds great. Here's the download link.

Though I would warn anyone downloading this - this build does not boot. I didn't do anything crazy to the code, but I'm not taking responsibility for other people using their devices to test. I haven't gone back to LOS 14.1 since this either.

With all that said, thanks for your offer to help! And thanks to anyone else that does too! Also thanks to the actual coders of the source =D

EDIT: Oh, and if for any reason I have to take this down, just let me know.
[One (M9) Q&A, Help & Troubleshooting] xangma:
So I found a big problem and I'm rerunning the build now. I wasn't paying attention and hadn't properly updated the LineageOS device_htc_himaul branch. This meant the build was using the vendor_lineage/config/common_full_phone.mk instead of common.mk and missed a lot out.

I've made the changes locally for now while I test *crosses fingers*, then I'll eventually upload my changes to github if they work.

EDIT: I now realise that common_full_phone.mk calls common.mk eventually anyway, so I've just taken out the telephony packages. Oh well, doesn't hurt to make the problem simpler.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Good, I'll wait for the build.

Hope will boot :D
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Any news?
[One (M9) Q&A, Help & Troubleshooting] xangma:
Unfortunately it didn't boot either (nothing changed with the kernel), but I do feel I'm getting a bit closer. I found a new android_device_htc_hima-common and kernel which I'm going to try and build now.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
How's with new kernel source?
[One (M9) Q&A, Help & Troubleshooting] xangma:
Not too good. I'm very lazy and unorganised so purged all the source and started again just to be sure about what's going into the build.

I have 'updated' the android_device_htc_himaul source to LOS15.0. When I say updated, I mean copy what I saw someone else doing for the himawl. I was using this updated version for the previous non working build, but I thought I'd share what I'd done.

Still battling to get this build completed without errors, it's at 5% at the moment and they take up to 5 hours on my PC :eek:
[One (M9) Q&A, Help & Troubleshooting] xangma:
Woohoo! I have a bootanimation! Just waiting to see what it does next =D
[One (M9) Q&A, Help & Troubleshooting] xangma:
Ok, amazingly adb is working, which is great news. Here's my bootloop error log.

Unfortunately, I can't work on this for a while, so I'll post up instructions of how I got where I am.

1. Install all the packages to build LineageOS as listed here and make a folder for your source and initialise the repo in that folder using 'repo init -u https://github.com/LineageOS/android.git -b lineage-15.0'

2. Run 'repo sync -c'.

3. Make a directory in the .repo folder called 'local_manifests' and add a file called 'roomservice.xml' containing this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xangma/android_device_htc_himaul" path="device/htc/himaul" remote="github" revision="lineage-15.0" />
<project name="Mirenk/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" revision="o8.0" />
<project name="Mirenk/chinomofu_kernel_m9" path="kernel/htc/msm8994" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.0" />
</manifest>

4. Force sync all these project paths by running 'repo sync --force-sync $path$'. For example for the first project it'd be 'repo sync --force-sync device/htc/himaul'

5. Comment out the 'TARGET_KERNEL_APPEND_DTB := true' line in device/htc/hima-common/BoardConfigCommon.mk

6. Make this change to hardware/qcom/audio-caf/msm8994/hal/audio_hw.c

7. Added system mount point

/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,barrier=1 wait

to this file: device/htc/hima-common/rootdir/etc/fstab.qcom

8. Run 'source build/envsetup.sh'

9. Run 'brunch lineage_himaul-eng'

10. In the created zip file, remove the assert at the top of the updater-script (spans 4 lines?) to avoid error 7 while flashing in TWRP.

That's it! That's the 10 steps you need to get to a bootlooping Oreo rom! =P

EDIT:

Looks like the error at the bottom of the logcat is looking for /system/vendor/firmware/image/keymaster.mdt when in fact it is stored at /firmware/keymaster/keymaster.mdt ...

And the mc_v2.mdt is in /system/etc/firmware/

Don't know about the others though. Maybe it'll get further into the boot if we point it to those files.

Looks like this might be a good fix ...
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Can you upload the build? I don't have any good pc to build it and will take 10-12 hours I think on my pc.
[One (M9) Q&A, Help & Troubleshooting] xangma:
Sadly not. I have no proper computer access at the moment. I'm actually now unsure the keymaster is preventing it booting as I've seen other logcats that get past this point.

I think the answer might be in /devlog but I've gone back to LOS14.1 until I can get back to this ...
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
Really!? My M9's logcat dosen't move from keymaster error…[emoji26]

Could you show me logcat if you still have it ?
[One (M9) Q&A, Help & Troubleshooting] xangma:
It does after your edits! (I think). I'm just syncing your vendor/htc/ and rebuilding.

Thanks for all your work, seriously, I'm just mashing things together and fixing small problems I think I understand. I updated the proprietary-files.txt a little here: https://pastebin.com/SxSr56hi

And I also added another hidl definition in the manifest.xml so surfaceflinger would start:

<hal format="hidl">
<name>android.hardware.configstore</name>
<transport>hwbinder</transport>
<version>1.0</version>
<interface>
<name>ISurfaceFlingerConfigs</name>
<instance>default</instance>
</interface>
</hal>

EDIT: To answer your question though, the logcats I saw getting past the keymaster error were from other devices. So I thought it wouldn't be a problem. It's to do with qualcomm hardware encryption right? Always good to have that working though I guess haha =]

EDIT2: Now I'm just hoping your vendor/htc/hima-common updates will fix this error:

10-22 16:35:14.033 466 466 E QCOM PowerHAL: Unable to open prefetcher: dlopen failed: library "libqti-iop-client.so" not found
10-22 16:35:14.033 466 466 E QCOM PowerHAL: Failed to get prefetcher handle.
10-22 16:35:14.033 466 466 I QCOM PowerHAL: QCOM power HAL initing.
[One (M9) Q&A, Help & Troubleshooting] xangma:
Ok, after installing your vendor/htc repo, the keymaster error is back. I think when using your latest device/htc/hima-common and the TheMuppets vendor/htc repo, the keymaster error went away.

I'm very confused ...

10-22 18:59:48.194 531 531 E android.hardware.keymaster@3.0-impl: Error opening keystore keymaster0 device.
10-22 18:59:48.195 531 531 E android.hardware.keymaster@3.0-service: Could not get passthrough implementation for android.hardware.keymaster@3.0::IKeymasterDevice/default.
10-22 18:59:53.194 532 532 I android.hardware.keymaster@3.0-impl: Fetching keymaster device name default
10-22 18:59:53.194 532 532 I vndksupport: sphal namespace is not configured for this process. Loading /vendor/lib64/hw/keystore.msm8994.so from the current namespace instead.
10-22 18:59:53.195 532 532 I android.hardware.keymaster@3.0-impl: Found keymaster0 module Keymaster QCOM HAL, version 3
10-22 18:59:53.195 532 532 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
10-22 18:59:53.195 532 532 D QSEECOMAPI: : App is not loaded in QSEE
10-22 18:59:53.195 532 532 E QSEECOMAPI: : Error::Cannot open the file /vendor/firmware/keymaster.mdt
10-22 18:59:53.195 532 532 E QSEECOMAPI: : Error::Loading image failed with ret = -1

This looks different now though. it was looking for them in /vendor/firmware/images before...
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
QSEECOMAPI's error is solved for now.(with my vendor commit "hima: Replace keymaster blobs")

but I have not been able to boot up rom and solve Power HAL issue yet[emoji21]

I'm trying rebuild with some change for HAL's that include Power HAL…
[One (M9) Q&A, Help & Troubleshooting] xangma:
Hi, I did see that one. Thanks. I am still getting these QSEECOMAPI errors, are you?

10-23 01:41:35.467 482 482 D QSEECOMAPI: : QSEECom_load_external_elf
10-23 01:41:35.467 482 482 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/mc_v2.mdt
10-23 01:41:35.467 482 482 E QSEECOMAPI: : Error::Loading image failed with ret = -1
10-23 01:41:35.467 482 482 D QSEECOMAPI: : QSEECom_load_external_elf
10-23 01:41:55.545 482 482 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
10-23 01:41:55.546 482 482 D QSEECOMAPI: : App is not loaded in QSEE
10-23 01:41:55.546 482 482 E QSEECOMAPI: : Error::Cannot open the file /firmware/image/keymaste.mdt
10-23 01:41:55.546 482 482 E QSEECOMAPI: : Error::Loading image failed with ret = -1
10-23 01:41:55.546 482 482 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
10-23 01:41:55.547 482 482 D QSEECOMAPI: : App is already loaded QSEE and app id = 3

I was thinking about fixing the keymaster stuff and mc_v02.mdt stuff with symlinks as seen here.

I'm going to try to look through /devlog next, to see if that can give us any more indications ...
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
What about this kernel source?

https://github.com/LineageOS/android_kernel_htc_msm8994/tree/lineage-15.0
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
When I rebuild rom yesterday, I got the same keymaster error…sorry…

I don't really understand the cause that keymaster and bootloop for now, so I'll try hard but other people may be faster boot up rom than me:p
[One (M9) Q&A, Help & Troubleshooting] xangma:
Thanks for your efforts anyway. It seems we're not the only ones having problems.
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
Good news, I found device configuration in lineage gerrit. And I rebuild rom with it… I could boot up rom!!

but it can't use bluetooth, audio and camera[emoji28]
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Gooood, hope the bugs will be solved quickly, I'm waiting for Oreo for some months :D
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
Gerrit's source is needed small fix. If you build rom, use my device configuration's branch "lineage-15.0".

---------- Post added at 06:11 AM ---------- Previous post was at 06:09 AM ----------

Thanks, I will do my best[emoji4]
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
I want to build it but I didn't built any rom before and I don't know if will succeed.

Also I don't have a very good computer and maybe will be a problem.

If you have some time, can you pm me a little tutorial?
[One (M9) Q&A, Help & Troubleshooting] xangma:
This is great news. Well done and thanks. I'll build the rom tonight and get some logs going =D
[One (M9) Q&A, Help & Troubleshooting] xangma:
Unfortunately I can't get past this error:

hardware/qcom/audio-caf/msm8994/audiod/AudioDaemon.cpp:458: error: undefined reference to 'android::AudioSystem::setParameters(int, android::String8 const&)'
hardware/qcom/audio-caf/msm8994/audiod/AudioDaemon.cpp:442: error: undefined reference to 'android::AudioSystem::setParameters(int, android::String8 const&)'
clang.real: error: linker command failed with exit code 1 (use -v to see invocation)

Which is annoying because I checked the includes ... #include <media/AudioSystem.h> is there. Well I have two I can find, though I don't know which one it's using:

./frameworks/av/media/libaudioclient/include/media/AudioSystem.h

./frameworks/av/include/media/AudioSystem.h

Which both have these lines in:

static status_t setParameters(audio_io_handle_t ioHandle, const String8& keyValuePairs);
static String8 getParameters(audio_io_handle_t ioHandle, const String8& keys);
static status_t setParameters(const String8& keyValuePairs);
static String8 getParameters(const String8& keys);

This confuses me greatly.

EDIT: I think I should really learn c++ instead of just guessing ....
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
I didn't get that error. Maybe it's because I use aicp source.
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
BTW, Bluetooth fixed!
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Can you upload the build please?
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
OK. But I can't post URL…(I haven't done 10 post yet)

What should I do?
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
I think it works with spaces, like "ww w. google. ro"

or

This is your AFH, right? You can upload it here and I'll download from here :)

https://androidfilehost.com/?a=show&w=files&flid=221752
[One (M9) Q&A, Help & Troubleshooting] xangma:
Sounds like that's my problem. I'll switch to AICP and get going.
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
Yes! I've uploded!
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
himawhl isn't Sprint(CMDA) ? I have himaul(GSM).
[One (M9) Q&A, Help & Troubleshooting] preston74:
Info from updater script: "ui_print("Target: htc/himawhl_sprint_wwe/htc_himawhl:7.0/NRD90M/870580.4:user/release-keys");"
[One (M9) Q&A, Help & Troubleshooting] Mirenk:
I think that the error is occered from android_8.0.0_r28…
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Sound works for me(music,youtube,browser, etc works but ringtones and system sounds won't)

Bluetooth works.

Package installer force closes.

Sim card isn't recognized(and I have some CDMA settings, I think is because of himawhl source)
[One (M9) Q&A, Help & Troubleshooting] xangma:
Thanks for the info, I'm going to crudely try to change my himaul source to work with AICP to see if it helps with these errors.
[One (M9) Q&A, Help & Troubleshooting] xangma:
I got the same error with AICP but fixed it with this commit. About to try booting.

EDIT: This didn't work either. I didn't get to a boot animation =[ Back to LOS15 for me.

EDIT2: Disregard me. Think my himaul source was wrong. I'm not going to post until I have something booting haha
[One (M9) Q&A, Help & Troubleshooting] xangma:
Finally. It seems wifi and bluetooth work, and I've heard at least some sounds. It's log collecting time!