yashsingh1/xdaforums huggingface dataset:
[Moto G5S Plus Questions & Answers] EmiAndroid:
Hello! you need to have root and know how to fiddle with your phone's internal storage, I do not recommend making changes at the system level if you are not sure of what you are doing
[Moto G5S Plus Questions & Answers] crazytech2:
Warning : This May cause bootloop. Take a Complete backup before doing anything.

Root your device. Install Root explorer. Remove anything that you don't want.

For startup image flash a boot animation ( Search for that you will get for your device.).

It's not recommended to change anything because this will break OTA.
[General Questions and Answers] tejasmodi:
Hi

I flashed the latest twrp-3.2.1-0-Z00A.img & twrp-3.1.1-0-Z00A.img on my Asus Zenfone2 (Z00AD) but they are not working... Therefore I flashed twrp-3.0.2-0-Z00A.img, which is working well for marshmellow roms but the nougat roms do not install and show error 7... please help me out... Awaiting your response... Thanking you in Advcance....
[Huawei Y5 (2017) Questions & Answers] m1z23r:
Hello guys, first of all thanks for all the hard work you do for us noobs :o

So to begin, i am trying to build a simple kernel without any modifications (for now) using source code provided by Huawei on their official website (You will need to select Y5II(CUN-L01) to get something downloadable).

consumer*huawei*com/en/support/phones/y5ii/

(New user external url block)

I've tried at least 5 different toolchains, I've followed many tutorials for building kernels including the mediatek specific guides but without luck. I would be grateful if someone could point me in the right direction and tell me if I am the one doing something wrong or is the source code broken ?

From many tutorials i've followed i've come to some usual steps i do:

1.

export ARCH=arm

export SUBARCH=arm

export CROSS_COMPILE=/home/mita/toolchain/bin/arm-eabi-

2.

I create a .config using predefined config

make hq6735_35u_b1n_l1_defconfig

3.

I try to do a make clean - i get an error

4.

I try to do a make mrproper - also an error

5.

I try just make and make -j4 - also errors

I can post the errors i am receiving, i have experience with android application development but i can't figure out a way to track down errors like i did in Eclipse and Android Studio.

Edit 1:

I forgot to mention i tried building on multiple OS’s: Ubuntu 32bit and 64bit, Lubuntu 32bit and 64bit, Kali Linux 64bit, and even on Raspberry Pi (i know it’s low spec but i had to try building on arm device just to rule it out) - Raspbian Stretch.

Thanks in advance for all the help
[Huawei Y5 (2017) Questions & Answers] m1z23r:
Bump

Before bumping i’ve read the rules “Once every 24h bumping”

I just not sure if there is a button to bump or is post like this required, sorry in advance if there is a bump button.
[Huawei Y5 (2017) Questions & Answers] m1z23r:
Once again a bump...

I would really be grateful if someone could tell me if source is broken or not so i can know my next steps.
[P8lite Q&A, Help & Troubleshooting] kadirc5:
Hi guys,

Im trying update.app methode but always "system update failed" how fix this thing ?
[P8lite Q&A, Help & Troubleshooting] keikari:
You probably have a wrong firmware version. Stock update method is very strict about that.
[LineageOS Questions & Answers] Sammyboy21:
Hello guys, I really appreciate the hard work you're doing on linage os, it has given my galaxy s5 new life, the smoothness is unreal, but linage does have its cons, one of my major concerns if the camera app, tbh the camera app is really bad, the picture doesn't come out no where near as good as the stock s5 camera app, is there a way you guys could either massively improve the camera app or just and a whole new on to linage os? Or would it be possible for me to flash a new camera app on top of linage OS? Please respond guys. I have major respect for you devs but I would like this major area addressed. Thank you and keep up to good work, my s5 is the SM-G900T BTW.
[Huawei Mate 10  Questions & Answers] wisemanwizz:
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.

Anyone facing the same issue?

Any solutions? :(

:confused:
[Huawei Mate 10  Questions & Answers] wisemanwizz:
I also realised the picture doesn't actually save in the DCIM folder, however only the thumbnail saves in the DCIM>cache folder as a .tmp file. :(:(
[Huawei Mate 10  Questions & Answers] ante0:
Are you using a custom kernel?
[Huawei Mate 10  Questions & Answers] wisemanwizz:
I am using the following custom kernel...

https://xdaforums.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
[Huawei Mate 10  Questions & Answers] ante0:
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
[Huawei Mate 10  Questions & Answers] wisemanwizz:
thanks man, i hope its fixable, it's actually quite annoying :rolleyes::rolleyes:
[Huawei Mate 10  Questions & Answers] ante0:
Are you using B137 from 03-29 or 04-04?

It seems the latter is some test build, because it has the required files for Face Unlock (which probably is not enabled in Settings?).

I only did a diff so far on the 2 different B137 builds, but will have to flash to find out if it can be fixable.
[Huawei Mate 10  Questions & Answers] wisemanwizz:
I'm using the 04-04 version of the B137 update.
[Huawei Mate 10  Questions & Answers] ante0:
I'm getting the same, one way to get camera back is simply to reflash but use B137 from 03.29. I have only had time to check what camera does briefly. It can't write to /sdcard/DCIM/ for some reason.

Face Unlock works btw, just need to set prop

ro.config.face_recognition=true

Can be done in build.prop or using a Magisk Module to set it at boot.
[Huawei Mate 10  Questions & Answers] ante0:
It's fixed now. I will release a fix for this version in a couple of hours.

Huawei built kernel using different sources (V10 source it seems), where it uses a new/different vcodec for images.

I compared kernel configs from 4/4 B137 kernel to 3/29 B137 and it's different.

I first tried using the config from 4/4 but it wouldn't build with BLA source (Missing codec).

Then I checked 4/4 B137 config to Honor V10 sources config (It was a little different but codec was there), then built kernel and tested.

Wifi, BT and Camera works now.
[Huawei Mate 10  Questions & Answers] wisemanwizz:
That's great! Thank you so much! I look forward to testing it! :D :D :angel::angel::angel:
[Huawei Mate 10  Questions & Answers] ante0:
Here it is: https://mega.nz/#!ZD43wBxa!qPWTiOgcuafWUX1DzZd2RFVU-eZdSn71LFFlJR3Z7Ac

This will probably break camera on other builds (I've not tested).

If you want Face Unlock root is required, you can flash this Magisk module (if you use Magisk) https://mega.nz/#!5e4VSS4L!4vbZr0Pyzm39k2Ltcxi10gcFg_bcSlj7iLosK6SLKtM

Or add the prop manually to /product/etc/prop/local.prop

ro.config.face_recognition=true
[Huawei Mate 10  Questions & Answers] wisemanwizz:
The kernel works like a charm! Thanks! :):)

For face unlock I tried to manually edit prop & then restart the phone, I am rooted but it is not working (I do not have Magisk) maybe I am doing something wrong.

Is there any specific place I have to put the "ro.config.face_recognition=true" within the prop file - i.e. should i just paste it right at the bottom of the prop file? And also where will the facial recognition option appear once it is enabled so I can confirm?

Sorry (I'm kind of a noob) I will probably try later. :angel::angel:
[Huawei Mate 10  Questions & Answers] ante0:
After setting that prop, doesn't mater where so just place it at the bottom, reboot and then got to Settings - Security & Privacy, you should have the Face Unlock option. If you enroll your face you can unlock phone by using the power button and looking at screen. It unlocks instantly in most cases.

Also I noticed I failed at setting a custom string to kernel that would show in Settings - About - Kernel. But it just says Unavailable now. Don't worry about it if you were wondering.
[Sony Cross-Device General] kv123:
I looked through the fixed vulnerabilities and found the stack corruption in the fastboot mode. Can it possibly get the TA party through it? Maybe someone guide me in right direction?

Use is extremely simple: run some like "fastboot flash dahdbachegwekjwekghkusbcekfyewkuwgkeufgwyfw4gfsmncqdbxvsffg some_file".

I've tested on XZP with latest firmware and think other models are also may be affected.

CVE-2017-11007

P. S. qdbxvsffg is mistake of forum, i can't delete it.

fastboot flash <random 59 chars string> some_file
[Sony Cross-Device General] serajr:
This thread seems to be a great opportunity to remember and discuss this: backup of the TA partition on the latest devices (2017/2018)!

If I'm not mistaken, even if we somehow figured out a temp root, allowing us to backup (dd) TA (and/or any other partition) on locked BL, that would not be enough to allow us to relock BL again, nor to create a hack like we did with ta-poc, since both drm and unlock keys do not seem to be present in the TA partition anymore (maybe now inside at own bootloader... don't know)!! Would DRM-fix be our last hope from now on?

I would like to hear some enlightening words from the masters [MENTION=4120742]munjeni[/MENTION] [MENTION=3665957]the_laser[/MENTION] [MENTION=8363210]sToRm//[/MENTION] [MENTION=357342]tobias.waldvogel[/MENTION] [MENTION=3975929]zxz0O0[/MENTION] (everyone is welcome ofc)

Thanks in advance!
[Sony Cross-Device General] pbarrette:
On the topic of possible exploits:

A user posted here that he's getting an error when attempting to flash the v47.1.A.12.119 partition SIN file. The error is "FAIL Command not authenticated" which suggests that it's requesting SAKE authentication.

The v47.1.A.2.374 firmware was the last one to have the LA1.1_O_77 bootloader (which is the BL version I'm on) and doesn't have a problem flashing the partition SIN. The v47.1.A.5.51 firmware, and all subsequent firmware versions, have the LA1.1_O_79 bootloader.

So that makes me wonder if they've blocked partition flashing in the newer bootloader to prevent a bypass of some sort.

What's new about the v47.1.A.12.119 firmware is that it has the partition SINs pre-extracted to a folder called

partition

, where they were previously contained in a zip file. So it's possible that nobody was flashing the partition SINs previously because Newflasher will only flash them if they are extracted.

It would be interesting if you can flash a set of partition data that allows access to a partition that isn't normally allowed.

For an extreme, but unlikely to be workable example, flash partition data that says the TA partition sectors are at the end of the userdata partition, then create a file table entry that encompasses that set of sectors.
[Sony Cross-Device General] munjeni:
Guy who flashed partition forgot to move partition sin files to partition folder which gaved error "command not authentificated", it was error because instead of command "repartition" wrong command was set "flash" because partition files was in top folder with sin files which use command "flash". For partition flashing diferent command must be used "repartition".
[Sony Cross-Device General] pbarrette:
Are you sure about that?

Look at the log he posted:

Repartition: partitionimage_0

Error, didn't got Repartition OKAY reply! Got reply: FAILCommand not authenticated
[Sony Cross-Device General] kv123:
I wrote about fastboot mode (led is blue) not flashmode (led is green). That message was about error in flashmode.

To go in fastboot you need poweroff the phone, push vol_up button and connect phone to PC.
[Sony Cross-Device General] pbarrette:
Yes, I know that.

Serajr, however, brought up the point that this would be a good thread to use for a broader discussion of possible exploits that could be used to access the TA partition.

Since I recently saw a situation which suggests that Sony may have blocked the ability to flash the partition table, I thought it warranted a mention here as opposed to being hidden on page-26 of a thread about VoLTE. Because if they have blocked that ability in a newer bootloader, it suggests that there's a way to alter the partition table in a way that Sony did not intend. And if that's true, it could open the door to accessing other partitions, including the TA partition.
[Sony Cross-Device General] munjeni:
You mean this post? -> https://xdaforums.com/showpost.php?p=76162897&postcount=769 It was what I talking about. That thing is fixed with latest v11 version, see -> https://xdaforums.com/showpost.php?p=76163127&postcount=773 partition sucesfully flashed!

---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------

Sucesfully flashed partition table -> https://xdaforums.com/showpost.php?p=76163127&postcount=773

One more thing, you can't flash modified partition sin file since its signed! All sin files is signed. Only maybe trought bootloader command "write_block", "read_block", maybe a chance for modifying partition table (in case not protected by sake authentification like it was protected to some trim area units like drm key unit...etc). List of command you can get inside LILO which lives in one of the sin files in bootdelivery, didn't remember name of the file but know only it was .img file format when unpack that sin file, inside that .img file inside ramdisk there is lilo file which is our bootloader, just decompile it and see what you need...

I know for sure about drm + unlock key (more about unlock key since I didn't found it on unlocked bootloader ta dump) is being outside trim area from 2017 and including 2018 models, and I'm believing booth drm key and unlock key is inside trust zone! Somehow I'm not believing which [MENTION=3665957]the_laser[/MENTION] says about drm key being deleted from trim area on android boot, its somehow nonsense, lets hope it is not true. Only a chance having that info for sure is soldering Easy Jtag Tool with emmc adapter directly to emmc pins and reading directly first partition while device is power down...

---------- Post added at 05:29 PM ---------- Previous post was at 05:09 PM ----------

Can you give me link? I see now, instead of Repartition:0 wrong command is set Repartition: partitionimage_0 that might be again partition string changes. My tool use basename of the extracted file to send command e.g. 0.img and 0.cms, than basename of the file is 0 and command is xxx:0, but again where you saw that post? Can you post link? That thing would not cause problem since I have fixed that s o n y changes https://github.com/munjeni/newflasher/commit/a70e4984dc6863413043d2ce8bdd557879db5b69 , might be you found some old post?
[Sony Cross-Device General] Deleted member 3665957:
device key ( unit 66667 ) is deleted from trim area only after rooting process completed.
[Sony Cross-Device General] pbarrette:
The link was in my first post, but here it is again.

The next post in the thread is me asking him to flash the old bootloader to see if that allows the partition flash, but I never got a response.

This is on a XZ1c.

Previously, Sony firmware included the partition SIN files as a zip file. So if you wanted to flash them with Newflasher, you had to extract them to the

partition

folder yourself.

Starting with v47.1.A.12.119, there's no zip file anymore. Instead, there's a folder called

partition

and the partition SIN files exist inside it. So, if you're using Newflasher, you don't have to move or extract anything.

I also get that the images are signed. But, it looks like you have to:

1] Extract the signature and upload it.

2] Extract the data to be flashed and upload it.

So you're already feeding the signature separately from the data, as opposed to uploading the entire SIN file.

Is it possible that Sony made a mistake in the old bootloader? That the partition data gets flashed before the signature validation occurs?

There have been some CVE's against the Qcom bootloader for flash before validation issues, as well as flash OOB issues in the Android Security Bulletins.

I mean, Sony didn't change the bootloader in Nov-2017 for no reason.

I'd test it myself, but I'm on the old bootloader version with the bootloader still locked. So I don't want to flash the newer one at this time if it's possible that I won't be able to downgrade it. I almost got burned that way with my old Moto phone.
[Sony Cross-Device General] munjeni:
It was 01.Apr.2018 but latest version of the newflasher is from 08.Apr.2018, it might work now as like already comfirmed.

Yes, no need to extract anything in case it is already inside partition folder.

It will not work since data is uploaded in chunks, every chunk is processed and in case you have modified any part of it entire process will fail, in worst case you get hardbrick.

Don't know but might be true.

---------- Post added at 03:47 PM ---------- Previous post was at 03:41 PM ----------

But now booth keys is no more seen in trim area partition dump, which is not a case on pre 2017 models, on 2017 and up models e.g. after unlocking bootloader unlock key 0x8b2 is no more inside trim area as like it was a case on pre 2017 models. The same with drm. It might be that unit number is moved to some diferent number? Or booth stored in tz? On short search I'm unable to get anything in secd about 1046b or 8b2 or inside ta lib
[Sony Cross-Device General] Deleted member 3665957:
device key ( unit 66667 ) still present in trim area and parsed by appropriate routines.

bootloader unlock key parsed by linuxloader.efi application and removed from trim area after parse as many other one-time keys ( remote lock reset, etc )
[Sony Cross-Device General] munjeni:
That mean with temp root we can dump drm key?

But if it is removed from trim area than whats going on on next boot, its restored to trim area and again deleted? Somehow unclear and somehow nonsense for me. It might be that unlock key have backup key? But in that case where is that backup key stored?
[Sony Cross-Device General] sToRm//:
Yes, with temp root it's possible. Because with the drm fix (patched secd and the relevant libs) the system doesn't wipe the unit at boot (logs proof this). So there should be a way to dump the TA as backup (for future use maybe) and fix the security checks (like I did) in the relevant files while the device is running. After that, the device thinks it's not rooted and we can use it like a brand new device out of the box, but with root and modifications.
[Sony Cross-Device General] Deleted member 3665957:
yes, we can dump all high-area units, including device key

bootloader unlock key checked by linuxloader.efi, if correct - linuxloader.efi erase userdata, erase device key and modify DEVINFO partition ( set flag "critical unlocked" or "unlocked", whatever )

so, if dump raw trim area before bootloader unlock via exploit, then unlock bootloader and restore trim area dump back - we will get unlocked bootloader and phone with original drm keys.

of course, on next boot releases s1team could add check and erase device key from trim area if devinfo.unlocked true, but this is "could" ;)
[Sony Cross-Device General] munjeni:
"could". That was a case on pre 2017 models, on newer models it is diferent now. Just dump your bootloader UNlocked trim area and search for unit 0x8B2, its not existent! I'm believing drm key too not exist inside LOcked trim area dump. Why I think that? I know, on old models, pre 2017, default case AFTER unlocking bootloader is: trim area gets totaly new unit 0x8B2 which is unlock key string. On new models, all after 2017, unit 0x8B2 NOT exist! Chech if you not believing me! I don't have new sony model but if I somehow decide to buy one (3 percent possible, I promised that I will never buy sony again because of its infinity unfriendly camera-audio-video proprietary libs) I will definitelly disasemble it and connect emmc tool to it and dump trim area and get thing confirmed. Now I not believing about drm unit is inside trim area, lets hope I am wrong.
[Sony Cross-Device General] Deleted member 3665957:
you did not read my message - once again - linixloader.efi check if unlock key valid and delete it after check.

device key ( unit 66666 ) still in trim area, if you believe in it or not, this will not change how things works.
[Sony Cross-Device General] munjeni:
Ok, but where is 0x8B2 unit? Its gone? Thats a first diferent thing I have noticed. Don't know about 6667 but about 0x8B2 I know. Probably 0x8B2 is no more need, right?
[Sony Cross-Device General] Deleted member 3665957:
you kidding, right ?

In order to enable locking/unlocking of the bootloader through
FG4, the xfl has support for oem lock/unlock commands. When executing
those commands, the xfl writes data in miscTA, which is then verified by
the boot on the next boot up, and if valid, the bootloader is locked or
unlocked respectively.

1. If MiscTA Unit 2226 (TA_RCK) is not empty, the boot SHALL check whether
unlocking of the bootloader is allowed.

If unlocking of the bootloader is allowed and the RCK is valid, the bootloader SHALL be unlocked.
Before unlocking the bootloader, the userdata and cache partitions, as well
as MiscTA Unit 66667 (TA_DEVICE_KEY) MUST be erased.
After unlocking the bootloader, MiscTA Unit 2550 (TA_MASTER_RESET) SHALL
be set to 0x2.
MiscTA Unit 2226 MUST be erased after the check.

2. If MiscTA Unit 2237 (TA_RESET_LOCK_STATUS) is not empty,
the boot SHALL validate whether the content of the unit is a valid CMS signed message.

If the message is verified, the bootloader SHALL be locked.
Before locking the bootloader, the userdata and cache partitions, as well as
MiscTA Unit 66667 (TA_DEVICE_KEY) MUST be erased.
After locking the bootloader, MiscTA Unit 2550 (TA_MASTER_RESET) SHALL
be set to 0x2.
MiscTA Unit 2237 MUST be erased after the check.
[Sony Cross-Device General] munjeni:
Not kidding! Dump an trim area for example from xz premium unlocked bootloader phone, and see, there is no unit 2226 (0x8b2)! Believe me!

Edit:

This is wrong:

Thas never worked that way! Unit 2226 IS NOT cleared after the check (at least on pre 2017 models), that unit keep bootloader unlocked! Erasing unit 2226 on e.g. xperia z1 compact giving bootloader unlock status "unknown", I can say that for sure! Lets make thing clear, you mean that for 2017-2018 models and NOT for pre 2017 models?
[General Questions and Answers] metropical:
I was reading about this command and was curious as to the "coding" to use it. The other day I was restoring a phone and had to interrupt the Play store restore of my apps.

Can this command be used to restart the restore of apps from Play store? If so, what would be steps or "coding"?
[General Questions and Answers] BillGoss:
You should be able to complete (restart) the restore process. You can do it using ADB or Terminal (if you have it installed and your phone is rooted).

I'm assuming you know how to run ADB commands.

adb shell
bmgr list sets
bmgr restore <tokenID from the previous command>

If there are multiple backup sets listed, you can find out the one that was used to start the restore process on your phone using the following command:

dumpsys backup | grep Ancestral:
[HTC Excalibur] dav2276:
I dropped my phone and now the keyboard works on and off...

Is there any way i can try to "clean" the keyboard to fix it?

Or perhaps just buy a replacement keyboard?
[Android Q&A, Help & Troubleshooting] Quetzakoatlus:
Hi.

Sorry I don't know how to explain it very well.

Sometimes I give my phone to my brother to play games, call someone, listen music etc. So I need an app or method to lock apps with two different security code or pattern. Depend on pin code or pattern used some apps will be locked. So is there any app or method thank I can use for this problem?

"Why I need something like this?

Well my brother use youtube and watch some weird youtube channel for kids, or listen different type of music on spotify. So that's make thing worse when youtube suggest videos or channels for me, or when spotify suggest music based on my previous listening habit."

(I have Samsung Touchwiz 5.01. So multi user it's not an option for me.)

Soryy for bad english.