yashsingh1/xdaforums huggingface dataset:
[Xperia SP Q&A, Help & Troubleshooting] Jadimo:
Hello,

I'm trying to build AOSPA for Xperia SP but getting this error:

Made recovery image: out/target/product/huashan/recovery.img
Target build info: out/target/product/huashan/system/build.prop
find: ‘out/target/product/huashan/recovery/root/res’: No such file or directory
cat: out/target/product/huashan/recovery.id: No such file or directory
build/tools/generate-notice-files.py out/target/product/huashan/obj/NOTICE.txt out/target/product/huashan/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" out/target/product/huashan/obj/NOTICE_FILES/src

zip error: Nothing to do! (out/target/product/huashan/system/etc/recovery-resource.dat)
make: *** [out/target/product/huashan/system/etc/recovery-resource.dat] Error 12
make: *** Waiting for unfinished jobs....

Does AOSP based roms need some additional commits to be able to build ? I hadn't such problems with Lineage and Vanir ROMs.

Here is my roomservice.xml file and full terminal output.

Thanks in advance for any help :)
[Honor 9  Questions & Answers] Clonimus74:
Hi,

I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.

After that it did low level reset or something of the sort and booted to Android.

After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.

I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.

What can I do???

Thank you
[Honor 9  Questions & Answers] PalakMi:
Return fully stock, then try again
[Honor 9  Questions & Answers] Clonimus74:
How do I do that, use the original recovery?
[Honor 9  Questions & Answers] Clonimus74:
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.

I flashed twrp and somehow booted to the recovery :) I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.

I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.

Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.

In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)

And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?

UPDATE:

I managed to get twrp working.

I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).

When I tried to flash supersu all the files were gibberish (see pic), what am I missing?

If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.

Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?

Appreciate any help I can get.
[Honor 9  Questions & Answers] Midhon58:
This mate is called encryption ;)

Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.

Magisk is another story.
[Honor 9  Questions & Answers] Clonimus74:
:) yeah I figured as much.

Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.

Many thanks, the external sd did the trick
[General Questions and Answers] karim434:
Hello all,

I have a problem syncing my Google contacts with my HTC One M8 (running Android 6.0). In the past, I have been able to sync the HTC People app with Google (and also link them with data from other apps).

Yesterday, I had to reset my Google account settings. I also cleared the People data, before putting the account settings back and syncing the data. Now it will only sync some of the contacts. It's missing about 190 of my contacts (which are clearly still there on Google). I can find no pattern to the contacts it includes/excludes. I have tried repeating the process - clearing all the data and settings and putting it all back - but I cannot get all of the contacts to appear on my phone any more.

Can anyone tell me how to solve this? Failing that, is there another (reliable) app for syncing contacts data from multiple sources, including Google, Whatsapp, and Skype? Thank you in advance!
[General Questions and Answers] asc366:
Can you verify that missing ppl have either google plus profiles or (birth)dates set? Refer to https://xdaforums.com/pixel-2-xl/help/contact-sync-flashing-8-1-image-syncing-t3715229 ... this seems broken since the 8.1 release but also breaks for non-oreo and non-pixel devices
[General Questions and Answers] karim434:
Thanks for posting so quickly - and for directing me to a thread for precisely this issue! I am missing rather too many contacts to go through all of them, but it's definitely not confined to contacts with a G+ profile and/or a date. As you say, the Android version on my phone also pre-dates that of most users experiencing this problem.

It seems there's no clear solution yet, but (from the thread) it seems to be early days. For now, I have manually exported my Google Contacts to a vCard file and imported it to my phone contacts. I guess I'll wait and see if Google comes up with a solution in due course.
[General Questions and Answers] karim434:
Deleted my Google account and People app data (again) today. Replaced them and suddenly I am finding ALL my Google contacts syncing again. I don't really have an explanation for why it worked this time but it might be relevant that I also installed the dedicated Google Contacts app this time round.
[General Questions and Answers] Micronin:
I solved this problem by deactivating power saver. After a few minutes, Contacts started to sync with my Google account.
[Android Q&A, Help & Troubleshooting] dickdickerson:
I found the solution.

I disabled some app at my old android device with "pm disable <app>" and searched for modified files in the last one minute:

# find /system -mmin -1

I found this file:

/data/system/users/0/package-restrictions.xml

Search for the app "com.android.location.fused" in the file and found this line:

<pkg name="com.android.location.fused" ceDataInode="2101300" enabled="3" enabledCaller="shell:0" />

Deleted the enabled and enabledCaller attribute:

<pkg name="com.android.location.fused" ceDataInode="2101300" />

Saved the file and successfully rebooted the phone! Yeah! :D

Thanks to user Marc.2377 at Stackoverflow for the hint to delete this both attributes.
[Android Q&A, Help & Troubleshooting] Rayan19997:
That definitely what i call an autonoumous man
[Android Q&A, Help & Troubleshooting] sneverius:
thanks, it also worked for j1m galaxy
[Android Q&A, Help & Troubleshooting] CiriousJoker:
Thanks so much!

I've been trying for hours to activate adb during boot before /data decryption and a bunch of other stuff.

You're a hero!
[Android Q&A, Help & Troubleshooting] aevan:
You definitely saved my life!

Your solution worked like a charm! For my part, the package-restrictions.xml was a little bit different, I had to replace that piece of code:

<pkg name="com.android.location.fused" ceDataInode="1223">
<disabled-components>
<item name="com.android.location.fused.FusedLocationService" />
</disabled-components>
</pkg>

with this one:

<pkg name="com.android.location.fused" ceDataInode="1223">
<enabled-components>
<item name="com.android.location.fused.FusedLocationService" />
</enabled-components>
</pkg>

(replaced "disabled-component" node with "enabled-component").

Then that's it. Back to business with all my data kept! :D

Thanks again!
[Android Q&A, Help & Troubleshooting] efedezeta:
saved my ass! Xiaomi Redmi Note 7

I disabled the miaccount or micloud services and couldn't log into the phone because of it's inbuild security system.

I had the RPC error trying to reactivate the phone.

This solution worked out like a charm for me. Same steps. Thank you!
[Android Q&A, Help & Troubleshooting] ShihabHT:
Man you saved my ass.

I disabled MI Account (com.xiaomi.account) and got locked out of the device asking to unlock by entering xiaomi account password, but I could not enable by entering the password cause I had the ****ing application disabled.

Respect for you, bruh...
[Android Q&A, Help & Troubleshooting] SomeRandomGuy:
This needs to go in a "so you pwn3d yourself n00b" FAQ somewhere. (Even though I've been doing this for years... )

You saved me an EDL mode flash, thank you sir.
[Android Q&A, Help & Troubleshooting] Bluscream1:
You're a fckn lifesaver. Thanks so much. I really hope someone turns this into a update.zip that can be flashed or a windows script that works on recovery adb
[Android Q&A, Help & Troubleshooting] RainGater:
Thank you for this useful post as it still works on my old phone!

Saved me from a data wipe and much appreciate it!
[Essential Phone Questions & Answers] JoRocker:
Hey guys, I know this probably isn't related to Essential specifically, but when I receive messages over 150 characters it comes in all broken up and out of order. Is there an app or something I need to do to fix this? Are people receiving my messages like this too?
[Essential Phone Questions & Answers] tech_head:
Tell them to not send messages of more than 140 characters?Text messages are limited in length.

If you violate the limit the app has no way of delivering the message without breaking it up.

In principal, it should not be out of order when you receive it.
[Essential Phone Questions & Answers] JoRocker:
Thanks for the unhelpful and sarcastic reply. You should have just said nothing at all... My iPhone sure didn't have this issue, and I have a hard time believing that this is an unsolvable Android issue.
[Essential Phone Questions & Answers] tech_head:
Actually you read the first sentence and didn't read further:

"If you violate the limit the app has no way of delivering the message without breaking it up.

In principal, it should not be out of order when you receive it."

You also never said anything about iPhone functionality.

iPhone/Apple's messaging app uses iMessage as a form of delivery/reception.

This means that MMS is always the way a message is sent. When sending to other iPhone users MMS s the default method.

Android phones use the standard SMS built into the cell network that has a 160 character limit.

Unless the sender specifically can configure their app to convert messages longer than 160 charters to MMS, then the message will be broken because there is a protocol limitation.

https://en.wikipedia.org/wiki/SMS
[Essential Phone Questions & Answers] mrcooter:
Depending on your messaging app, and possibly who is sending it determines this as well. SMS over the character length can be sent as MMS and not be broken up. I've seen it in some app settings before as a choice between the two methods as well. Not familiar at the moment. Doesn't bother me so it's not something I look for but it could be a starting point for you to look as well.

Edit - should have read the previous post all the way though. Just reiterated. Sorry.
[Treble-Enabled Device Guides, News, & Discussion] FSadino:
In this Article by Mishaal Rahman , we can understand why OnePlus and Nokia doesn't have treble support to their devices.

I open this thread to discuss about your opinions about how danger can be to create vendor partition outside system partition.

Tell us your opinion and how we can do it safely!
[Treble-Enabled Device Guides, News, & Discussion] revjamescarver:
/vendor

That partition is not accessible by the user or anyone else unless the phone is rooted, and it's no more dangerous than having the drivers and libraries in the system partition, OnePlus, as nothing more than a rebranded oppo, as well as Nokia, just don't want to put in the effort, Google has made it perfectly clear that treble is not optional, it is mandatory for devices shipping with Oreo and later, Nokia and OnePlus can do what they want with existing phones, but even they have no real choice that to support treble, unless of course that want to be stuck on phones shipping with nougat and maybe upgrading to Oreo, both of them will see the Android world passing them by and their implementations of Android will become more and more fragmented. Each to their own I suppose
[Treble-Enabled Device Guides, News, & Discussion] CommanderROR:
Repartitioning a phone carries a certain risk, especially if it is done via OTA Update, but there are ways to do it and make it relatively safe...if you are willing to put in the work. I think that's the main point.

To me, it's much more interesting to see right now, how OEMs actually use Treble. They no longer have the excuses they used to, so someone like Sony should now be able to provide the Update to Android 8.1 within Days instead of Months...but will they actually do it?

The reasoning behind OnePlus deliberately not using Oreo on the 5T and not preplanning the extra partition...well, that tells it's own story. Not really that unexpected. Nokia though...I would have expected more from them, since they started with big promises about Stock Android and fast Updates, but so far very little has materialised...
[Treble-Enabled Device Guides, News, & Discussion] zelendel:
I really think people are blowing this up far more then it needs to be. In the Google article it stated that even after the treble code is sent, the oems will still have to make their changes. So as far as I can see this will only matter to oems.

I expect to see many devices with day one 8.0 updates for a while.
[Treble-Enabled Device Guides, News, & Discussion] CommanderROR:
Well, like I said, this will be the benchmark for Updates in the future. Since a new OS version can now boot on a phone without any big changes to the UI, Drivers or Apps, it SHOULD be far quicker. How much quicker will be interesting to see. Custom ROMs already show how fast the process can be...so... interesting times!
[Treble-Enabled Device Guides, News, & Discussion] zelendel:
Yeah if you don't want any of the main features from the oem. Like Samsung cameras on aosp. Things like that.

As for faster updates. I doubt it. As now the oems will, have to do twice the work. Instead of adding their code to the stock frameworks. Now they will have to make completely new framework files to over write the default. Downloads will be a lot bigger now as well.
[Treble-Enabled Device Guides, News, & Discussion] CommanderROR:
Hmm... that's not the way I understand Treble!

From what I've read, the OEM can basically exchange the OS Version without really touching much of their OEM UI...

The fact that Custom Roms are limited is mostly due to the fact, that devs don't have access to the OEM Sources, so they can only compile AOSP versions of Android...
[Treble-Enabled Device Guides, News, & Discussion] zelendel:
And see that is why XDA articles are crap. The way OEMS roms have worked for years is that they replace and/or recode all of googles files. Now they will have to make even more. To over write them.

That is what you will get. Either AOSP or OEM. The aosp will not have access to the OEM code. Nor will OEM push their code to aosp for google to make things work right. This comes from the fact that OEMS dont write the drivers and code for alot of the hardware. They get that from others.
[Treble-Enabled Device Guides, News, & Discussion] AsItLies:
Just checked, my us997 LG G6 has a symlink for 'vendor', it points to 'system/vendor'... so no separate partition on the G6 either... I was hoping! alas.
[Treble-Enabled Device Guides, News, & Discussion] CommanderROR:
Not unexpected...the G6 launched way before Treble was announced and hasn't been Updated to Oreo yet...
[Treble-Enabled Device Guides, News, & Discussion] rillrill:
They should build a tool and require a wired connection to a pc to repartition and fallback just in case.
[Treble-Enabled Device Guides, News, & Discussion] phhusson:
FWIW, I made patches to AOSP to be able to have a vendor partition WITHOUT needing to repartition, here:

https://github.com/phhusson/treble_experimentations/tree/master/no-vendor

The way it works, is it tells the kernel to look at the "system" partition, as if it was an hard-drive, to look for partition table, and then use partitions inside this fake hard-drive
[Treble-Enabled Device Guides, News, & Discussion] CommanderROR:
Clever. Sell that idea to Oneplus and Nokia please...?
[Treble-Enabled Device Guides, News, & Discussion] phhusson:
I might be a good coder, but definitely not a good seller :P
[Treble-Enabled Device Guides, News, & Discussion] FSadino:
Did you already tried this? I mean, I'm not developer and I can't understand the pros/cons about your patch but is extremely interesting!

[MENTION=3292224]franciscofranco[/MENTION] [MENTION=3873953]eng.stk[/MENTION] [MENTION=4800121]Sultanxda[/MENTION] [MENTION=4684315]flar2[/MENTION] can you guys share your opinion about this? Thanks in advance
[Treble-Enabled Device Guides, News, & Discussion] phhusson:
Yup, actually my main testing device for my Treble ROM is a device using this.

Pros:

- doesn't need to repartition

- Easy to integrate

Cons are only for community rom devs:

- /system and /vendor are in read-only, even if dm-verity is disabled, the only way

- some TWRP change is required

- fastboot flashing will require to launch a s cript to merge system.img and vendor.img and flash both at the same time

Frankly, I'd guess OEMs had better to repartition. If you don't move partitions, only split system into system/vendor, and write the script with error-checking in mind, I really can't see how you would brick your device.

But this patch makes it possible to answer to OEMs saying they can't because of missing vendor partition
[Treble-Enabled Device Guides, News, & Discussion] CommanderROR:
It will be interesting to see what happens, if a Device with strong XDA Community support like the OnePlus lineup can be "Trebleized" by the community and then supported more easily without help from the OEM that made it.
[Treble-Enabled Device Guides, News, & Discussion] mikey1975:
Following up here, very curious about where this is going.

Not a developer, but willing to test, my device is OP3T.
[Treble-Enabled Device Guides, News, & Discussion] angadsingh97:
In light of a dev getting Treble support on the Redmi Note 4X, is it possible to get it on our devices too? I'm willing to test.
[Treble-Enabled Device Guides, News, & Discussion] Sam Nakamura:
Does the Zenfone 4 use your patch actually? (didn't checked if sources are available yet)

I read a while back that first devices (or just one device?) is now project treble ready without vendor partition, not knowing you might have anything to do with it...

For reference:

https://www.androidpolice.com/2017/11/26/phones-updated-support-project-treble-continuously-updated/
[Touch Cruise ROM Development] thebiker:
Hi All

Today I checked my Cruise with mtty info and the result was this:

nfo 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_k9k2g08

DEVICE ID=0xAA

DEVICE MAKER ID=0xEC

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x800

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 2 (0x2) is reversed block

BLOCK 8 (0xKirály is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

BLOCK 1023 (0x3FF) is bad block

Partition[0], type=0x20, start=0x2, total=0x3E

Partition[1], type=0x23, start=0x40, total=0x780

Partition[2], type=0x25, start=0x7C0, total=0x8680

Partition[3], type=0x4, start=0x8E40, total=0x12480

CE Total Length(with sector info) = 0x4767200

CE CheckSum Length(without sector info) = 0x4720000

I use Beps 0.54. all flash was perfect. I didin't have any error.

I worry about a little bit.

1, What does it mean this bad block exactly?

2, Should I afraid about this?

3, How can I repair this?

I got other result from "fktsndr":

--- 2K bytes sector version ---

DEVICE NAME=samsung_k9k2g08

DEVICE ID=0xAA

DEVICE MAKER ID=0xEC

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x800

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 2 (0x2) is reversed block

BLOCK 8 (0xKirály is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0x780

Partition[2], type=0x25, start=0xDC0, total=0x7580

Partition[3], type=0x4, start=0x8340, total=0x12F80

CE Total Length(with sector info) = 0x41E1A00

CE CheckSum Length(without sector info) = 0x41A0000

It looks better than my Cruise. He use Bepe 0.53.

Any idea?
[Touch Cruise ROM Development] NetrunnerAT:
Ignor this!

Is normal!
[Touch Cruise ROM Development] thebiker:
Pfhuuuuu ...... :) :) Ok. What is this difference between two Cruise?

One with bad block and the other without.
[Touch Cruise ROM Development] NetrunnerAT:
Here is my HTC Nike

info 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_k9k2g08

DEVICE ID=0xAA

DEVICE MAKER ID=0xEC

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x800

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 2 (0x2) is reversed block

BLOCK 8 (0x8) is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

BLOCK 13 (0xD) is reversed block

BLOCK 14 (0xE) is reversed block

BLOCK 16 (0x10) is reversed block

BLOCK 17 (0x11) is reversed block

BLOCK 18 (0x12) is reversed block

BLOCK 19 (0x13) is reversed block

BLOCK 817 (0x331) is bad block

BLOCK 1325 (0x52D) is bad block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0x700

Partition[2], type=0x25, start=0xD40, total=0x8EC0

Partition[3], type=0x4, start=0x9C00, total=0x116C0

CE Total Length(with sector info) = 0x4E4E000

CE CheckSum Length(without sector info) = 0x4E00000

I have in my Work three other Nike with same error! All work without any problems.
[Touch Cruise ROM Development] fktsndr:
DANGER!

Guys, DO NOT use "task 2a" command in MTTY with Polaris device!

Your device will be a brick.
[Touch Cruise ROM Development] NetrunnerAT:
Type(hex) 2A: Check NAND flash and mark bad blocks. (Requires Level!=0xFF)

Can you explane why? I think i know what you mean ^_^

[edit] i have found the Kaiser Thread ...
[Touch Cruise ROM Development] Olipro:
because in the new EVT series, the SPLs are properly written with full ECC checking, task 2a just formats the NAND entirely
[Touch Cruise ROM Development] thebiker:
It's clear but what do you think about the bad block in the firs post? It's normal or not?
[Touch Cruise ROM Development] pof:
yes, it is normal... its a NAND device. Forget about it and be happy.
[Touch Cruise ROM Development] fktsndr:
About NAND devices

http://en.wikipedia.org/wiki/Flash_memory

About bad blocks of NAND devices:

Most NAND devices are shipped from the factory with some bad blocks which are typically identified and marked according to a specified bad block marking strategy. By allowing some bad blocks, the manufacturers achieve far higher yields than would be possible if all blocks were tested good. This significantly reduces NAND flash costs and only slightly decreases the storage capacity of the parts.
[Touch Cruise ROM Development] thebiker:
Thax for all answer!!!