yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
@dandreye I am happy it worked out for you in the end 🎉!

Yeah I also had the feeling that a card with no partition is not really a good idea sometimes.

Something else I don't know is if you can still decide to manually move files or apps between the internal and external memory or if the system decides for you anyway. Also, I am not sure that you can or should edit the micro SD card on another device (for instance adding a file from the computer on it).

Nevertheless, congrats for giving this Galaxy A3 a fresh new start! 😉
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dandreye:
@maxanthem:

Well upon completion of the formatting job it did offer to "export" (whatever existing apps and data can be exported I guess) onto this extended internal storage. I decided not to: just wanted to ensure it's ready for use at this stage. There are lots of threads on moving individual files across, so it should be possible. Whether one really wants to do it manually file by file is a different question: I'd personally have preferred the OS to manage it all for me instead and move as many files as it pleases, ridding me of the need to even think/care about it. Still being able to move a desired file would be useful indeed.

Perhaps Linux could, as that partition probably uses ext4 filesystem (like with built-in internal memory) or something similar. It doesn't get exposed upon connecting the phone with it to my Windows laptop, and when I plug it into the latter directly I can only open it with DiskInternals Linux Reader. So this is a bit of a pain when copying a lot of music etc across from the laptop for instance. If not that I'd probably give up on the 2nd partition, which still isn't working for me for some reason.

Thanks :-) Tbh it's still a learning exercise at the moment: there's ~2.3GB free out of 10GB internal.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Yeah I also see something like this but:

1. I don't know if I can trust this value or if it is exaggerated / random / false

2. I don't know if this is an issue because I assume that the OS is dealing automatically with this to move or not content to the microSD card

I've read that you can mount an ext4 partition from windows using WSL (Windows Subsystem for Linux). But I guess that you would have to do it on the microSD card when the phone is turned off, and I am not sure if this could corrupt the partition. I guess that it is somehow encrypted?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dandreye:
I've just tested it with Ubuntu 18 running on my old laptop and the ext4 partition isn't visible there. Interestingly when I tried creating 2 partitions manually using Minitool Partition Wizard on my Windows laptop the ext4 one was perfectly visible in that old Ubuntu 18 laptop. Looks like the phone formats it differently... would be great to understand those diffs so we can mimick them and hopefully make the phone use adoptable on the manually crafted ext4 partition leaving the exFAT one intact.

Wrt encryption: looks like stock ROM should encrypt it indeed unless "no verity" was flashed before the first start to prevent it (assuming "no verity" disables encryption everywhere and not just on built-in internal memory alone)... Perhaps someone reading this could confirm/deny it..
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Yeah, it would be nice to know from an expert. I have the gut feeling that the no-verity-opt-encrypt still leave the system encrypted, but I cannot find any source confirming or deny this.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dandreye:
Trying to reverse engineer it here meanwhile. Firstly (just for comparison) script 01-no-force-encrypt under patch.d in no-verity-opt-encrypt-6.1.zip replaces all occurences of forceencrypt or forcefdeorfbe in all fstab.* files with encryptable:

sed -i "s/\b\(forceencrypt\|forcefdeorfbe\)=/encryptable=/g" "$fstab"

Script 01-enable-adoptable-storage under patch.d in adoptable_storage_enabler_ashyx.zip just appends ",encryptable=userdata" behind any occurence of voldmanaged=sdcard:auto in the same fstab files:

sed -i "s/\bvoldmanaged=sdcard:auto/voldmanaged=sdcard:auto,encryptable=userdata/g" "$fstab"

I can see the effect of it in my fstab.* files although ",encryptable=userdata" seems to be appended twice in 2 out of 3 such files (I even tried deleting the "duplicate" one but it's added back after a reboot), as if the script gets triggered twice - just hope it's fine:

Spoiler content hidden.

Now it'd be nice to understand what exactly this ",encryptable=userdata" does to the card :) Perhaps the intention was to make encryption optional (like in no-verity-opt-encrypt-6.1.zip) in case it's enforced onto the card by default..
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Hi Dandreye,

Then, it is you the expert :D ! You dived deep in this, and I am not sure that I can follow you 🤿...

You might be right, but I wonder on the opposite if the "encryptable=userdata" make it possible to encrypt the card such that the system can use it as adoptable. I guess that if you cannot read the card on linux / ext4 partition reader in windows, it might mean that the micro SD card is encrypted (and so is the phone).
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dandreye:
ChatGPT is :ROFLMAO:

Quite possible. Sadly there's little hope @ashyx himself will see this as his ID seems inactive and he was last seen here mid-2020...

https://xdaforums.com/m/ashyx.4899305/about
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Love it 😍!

Did you manage to mount and read / write your card on a computer (Linux or Windows / WSL) ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dandreye:
After failing to open that single partition on it in Windows 11 and Ubuntu 18 I switched attention to dual partitioning as per that other thread and finally managed to create 2 partitions (albeit using yet another phone - Samsung S9+ as no other Samsung phone in my household could do it for some reason). So my card has ~30GB "portable" FAT32 partition followed by "internal" ext4 partition taking the rest of the space now. Unfortunately it didn't help make the latter one open in Windows/Linux and even the target Samsung A3 2017 phone won't see/adopt that partition alone - it just says "New SD card inserted" and prompts to format it (entirely) as internal or portable as usual. I decided to keep its dual partitioning intact for a day or two while awaiting answers on my questions in that other thread on it in case I'm asked to try this or that with it there. If no luck I'll probably revert back to a single partition to proceed/complete the experiments with it. Of a particular interest is whether at least TWRP can see it in Mount: I recall seeing "sdcard" there alongside system, data etc, but didn't try mounting it. Afaik TWRP's ability to take entire back up incl system and/or data is an indication of no encryption on them (which I personally evidenced with no-verity-opt-encrypt.zip before), so perhaps we could try this: install some app onto the "internal" partition of the card and see if it gets backed up.

As for WSL, in the recent past I unexpectedly struggled to set it up on my current laptop (got it working once elsewhere earlier this year, incl all that USB port mapping with usbipd) and didn't have time to proceed any further, so had to give up. Tbh I don't expect it to bring any benefits to the subject of our interest vs my Ubuntu 18 laptop, which I could upgrade to 20 or 22 if required.

Btw I'm somewhat surprised it's ext4 despite so many reports about f2fs being much faster. Perhaps it's f2fs in more recent Samsung phones though.. And one more thing that I noticed with this dual partitioning by S9+ is one more tiny partition immediately preceding the "internal" one and called android_meta as can be seen in the Diskinternals Linux Reader screenshot attached. Perhaps there's more to ext4 with Android unless it's something specific to the newer Android version on the S9+.

And one more idea on making it work with dual partitioning: perhaps we could let the phone format entire card to its liking and then just shrink that partition somehow to make room for the portable one that could be added manually.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
This is a lot of inputs! Good luck with your research!

Let me know if you have some updates (maybe we can move to PM until we have something to share here :) )!

Maybe the shrinking trick could work.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dandreye:
Good point actually (was thinking about the same lately) - will keep you updated via PM then.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Hi @Asphyx, @dandreye and @jnflos!

I have bad news...

I was so proud to have my newly adopted storage (256GB) working for few weeks, and today I couldn't install an app on my phone: I reached the full capacity of the internal storage (see screenshot)😭😭😭

Wasn't it the whole point of having adopted storage?

I feel that the phone is putting the app on the "internal internal" storage anyways 😡

I feel scammed by Samsung (once again)...

If you know a fix for this, I'd be glad to hear it! At least, before, I could move some apps to the SD card.

Thank you very much for your work! 🙏😊
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Asphyx:
Not sure why I got this shoutout as I do not have this phone...

But in the past (I now have a Pixel 7Pro no SD Card but 512G of storage) you used to have to go into Settings/Apps and select a App and then select storage.

If the App supports moving to SD card the option should be available there.

Move what apps you can to SD Card and you should get back some Internal Storage space.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Hi,

Sorry for the out-of-nowhere bump 😅 I was still under the rollercoaster of emotions.

@jnflos who, for some reason, I can't tag, apparently presented in 2017 a method using your patch to give the option to Samsung Galaxy smartphones (2017 series) to offer adoptable storage.

The method you just referred to is typically what you do when the SD card is not adopted (ie when it is external storage).

When the SD is adopted, it should behave as one with the phone storage as one big internal storage. So the option to move app does not appear anymore, because the phone doesn't "think" it has an external storage, right?

At least on my side, the setting app crashes when I try to open the setting/apps/<any app>/storage 😅

Maybe I can start to work with this!

Thank you for your help 😊!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] alecxs:
No. opposite. external storage is required. it just switches external storage location from phone storage to adopted storage. AFAIK Samsung never supported Adoptable Storage, so OneUI is lacking that option.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Thank you for your reply :)

Indeed Samsung doesn't let you adopt a storage (by adopt I mean consider a SD card as internal storage). But thanks to this thread based on @Asphyx patch (Marshmallow) you can do it on Samsungs.

What I don't understand yet is how to fix my issue that despite having an adopted storage, my phone still put most of the apps on the build-in storage. I might try this method. Or I might end up rooting my phone and use Link2SD, however, I would lose the possibility to use my banking apps, which is not good :-(
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] alecxs:
if you have any app that is moveable, you can move it to adoptable storage with 3rd party apps (no root). Link2SD provides this button too (alongside with its symlink method)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lefti696:
Thanks for the guide.

Do you have files needed for flashing that you have mentioned? (or links to them) "no-verity-encrypt file" and "adoptable storage enabler"
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maxanthem:
Hi!

I found the no-verity-encrypt there (I took v6.1). The other one is attached to the head of this thread.

With more perspective after time, I decided to move back to my stock rom with adopted SD because it caused too many issues. For instance, as I mentioned before, it got full quite fast as well because even though the sd was adopted, most of the apps went in the internal part of it... I didn't try Link2SD but I'm expecting a lot from it. I guess that only movable can moved which is exactly what you can already do with stock rom.

I am considering removing more bloatware by force without root using adb.

I hope this helps :)

Keep me updated if things work for you!

Let's keep these A3 2017 alive forever!
[Tilt, TyTN II, MDA Vario III General] brianlb:
is there a way to make the pcm keyboard the defualt keyboard on a Tilt instead of the small keyboard it comes with? i can select it w/quicmenu but everytime my phone goes in standby or is turned off it goes back to the original keyboard, is there a registry edit or something i can do to fix this?
[Tilt, TyTN II, MDA Vario III General] petervbeck:
SIPChange

you can change your default keyboard with SIPChange
[Tilt, TyTN II, MDA Vario III General] brianlb:
Thanks, appreciate it.
[Tilt, TyTN II, MDA Vario III General] mikeeey:
thanks, ive always wodnered this, never got around to asking on the forum tho.
[ONE Q&A, Help & Troubleshooting] Jesusopfer:
EDIT: Nevermind, XDA App set up the wrong Oneplus phone - now where can I delete my post?

Hey folks,

I just noticed my phone is having some issues with mobile data measurement. See attached screenshots.

- the raw data counter is way off

- the values shown in overview differ

- in reality, I've used just under 700MB

Is there any way to fix accuracity? Measurement being 50% off is just not useful at all. Is it possible to turn it off completely? I'd like to do so if I don't find a solution.

Same issue for my other SIM-card I use occasionally.

Running on 3.5.4 as I need xposed.

What process does measure data usage? Maybe I messed it up using Amplify.

Thanks in advance, cheers!
[ONE Q&A, Help & Troubleshooting] Stephen:
Moderator Information,

Thread closed at OP's request.
[Nexus 6P Q&A, Help & Troubleshooting] robiulrana:
Problem first appeared when I enrolled beta program N 7.0 (unrooted)

Then i unenrolled beta program and went back to Marshmallow but then it appears unknown baseband version.

Then I root my device and

I tried to flash the 7.1.1 stock (nmf26f) but still no go.

Tried to do custom rom (du 7.1.1) but still no go.

Tried to downgrade to stock (6.0) still no go.

Tried to rebuild EFS partition with latest TWRP using

ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384

and

ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

Still no go

Try to Flash vendor image, radio image still i'm crying......:crying:

please help me.

There is no service center here for nexus device. I am from Bangladesh.

[IMG="Dialar"]https://goo.gl/photos/dLX1YVsFz5bCdJ367[/IMG]

[IMG="No service"]https://goo.gl/photos/6uo5vWE1qjQydQJc9[/IMG]

[IMG="Sim Status"]https://goo.gl/photos/jkvFa3Gb3jAKdZdx8[/IMG]
[Nexus 6P Q&A, Help & Troubleshooting] v12xke:
Read the end of this thread, maybe it will help. Basically used flash-all.bat to flash the latest February stock image from Google. For you that would be N4F26O.
[Nexus 6P Q&A, Help & Troubleshooting] robiulrana:
Thanks. I'll try & inform the update.
[Nexus 6P Q&A, Help & Troubleshooting] robiulrana:
Not working for me....

I tried with Factory Image N4F26O, NMF26F even MDA89D(6.0.0) still no change

No service, no signal :crying:
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
Maybe something on the carrier side needs to be reset?
[Nexus 6P Q&A, Help & Troubleshooting] Paidinfull:
Two images

Well there are two factory images for 6P for Feb. N4F26O & NUF26K. Maybe the other one fixes the connectivity?
[Nexus 6P Q&A, Help & Troubleshooting] v12xke:
NUF26K is for Verizon and contains a different baseband with fixes specific to Verizon. N4F26O is for all others- including Bangladesh... besides OP has already flashed a different radio.
[Nexus 6P Q&A, Help & Troubleshooting] robiulrana:
My Carrier won't help

I've contact with my carrier also, they cannot help me in this regard.

I post this thread on Nexus Help Forum. Maryg Comex said there:

"I am from Buenos Aires, Argentina, and I have the same problem.

I called Huawei Argentina and was told that the last Android 7.1 upgrade blocked the cellular network un my country, because I purchased my Nexus in the USA.

They also advised to contact the store in the USA and ask them to get the international free code from the manufacturer in China in order to unblock the system foro South América.

Still waiting for this code... "

I don't know what to do
[Nexus 6P Q&A, Help & Troubleshooting] robiulrana:
Thanks.

Tried both, N4F26K is only for verizone though. Now I'm in N4F26O. New problem appeared now, Baseband version: unkonw.
[Nexus 6P Q&A, Help & Troubleshooting] v12xke:
Your thread is very confusing. Are you saying your phone is from NA (H1511) carrier locked (SIM locked to carrier). Please verify and confirm your phone is NOT carrier locked. Secondly, where exactly are you trying to use the phone and have you tried a local SIM from that location.
[Nexus 6P Q&A, Help & Troubleshooting] robiulrana:
This was a reply on nexus help forum

Dear v12xke,

Your qouted thread was actually a reply from my same post on nexus help forum. If possible pls visit this post on nexus help forum: https://groups.google.com/a/googlep...91b-bc41-93052d51b908@googleproductforums.com.

I post some screenshot there.

I don't think my phone is carrier locked. I am from Bangladesh and i tried various sim from various carrier from Bangladesh. Those Sim worked fine when i purchase my Nexus 6P from local store. This issue happened when I enrolled to Android N (beta program).

Sorry for my English. Thanks
[Nexus 6P Q&A, Help & Troubleshooting] parvezrobi:
Have you fixed the problem?? i am from Bangladesh also.

Have you fixed the problem?? i am from Bangladesh also.
[Nexus 6P Q&A, Help & Troubleshooting] kach22:
@v12xke

I am also facing the same issue. My phone was bought from google play store and delivered in Texas. It was unlocked and no carrier dependent. I used the t mobile while I was in Houston and when I came back to Bangladesh I have been using the local SIM without any problem until last week. I have tried almost everything (flashing the stock image, flashing a custom rom: purenexus, restoring efs backup and now trying to flash latest radio image). I don't think any of them going to solve the issue if the phone is locked for the country.
[Nexus 6P Q&A, Help & Troubleshooting] v12xke:
What were you doing when this happened to your phone last week? There is no "country" lock. Your US phone was sold "carrier unlocked" and is supported in Bangladesh via GMS 900 and 1800, and UTMS B1/B8. All of which are supported by the H1511 (NA) variant. That is why it was working before. If you were lucky enough to have a TWRP backup of your own EFS partitions, restoring those should have worked BUT there was a time when the EFS backups from TWRP were not working because of an error in the script which was corrected in later versions. There is a thread and sticky dedicated to this issue. If not, format them completely and reboot the phone. Have you tried a SIM from another carrier there, preferably one that uses a different frequency as your carrier? Grameenphone appears to support the most frequencies of all the carriers in your area. What happens when you put your TMo SIM in?
[Nexus 6P Q&A, Help & Troubleshooting] kach22:
1. I was enrolled in android beta and installed Nougat 7.1.2 . I practically did nothing that could hamper the phone functioning. Yes it was working fine in Bangladesh, and in other country as well.

2. I was not lucky enough to have a TWRP backup of the EFS but I got a back up EFS and restore following instruction. It didn't help. I am using TWRP angler 3.1.0. angler. I also flashed the radio to latest one (3.82) and with no success. You can have a look at the phone information and the drop down menu (Screenshots).

3. I have flashed the stock Nougat 7.0 and reboot the phone several times. It didn't work. Can you explain a bit about "formatting and rebooting". Need to know whether I did the right thing.

4. I have tried another SIM from another carrier but still it didn't work. These sims are working fine in my Nexus 5 which I also bought from Houston.

5. Haven't tried the Grameenphone sim but I don't think it is a SIM issue. and I don't have the TMo sim with me now. It is now being used by my mother who is currently in Houston.

6. Can you share the link of the sticky thread that you have mentioned?

7. I must thank you for your time, your suggestion and your cordial support. I really appreciate that.
[Nexus 6P Q&A, Help & Troubleshooting] v12xke:
>>3. What I meant was to manually format the EFS partitions using fastboot and note any errors:

fastboot format modemst1

fastboot format modemst2

>>6. The thread on TWRP/EFS botched backup/restore does not really apply to your case. It forensically details how the dev mistakenly coded the EFS backup script, why it broke many phones, and how it was fixed. Your problem is more likely one or both of the EFS partitions is corrupted. Your best bet is probably finding someone else with a fully working N6P, make a backup of their EFS partitions and then restore that backup to your phone. A pretty tall order.
[Nexus 6P Q&A, Help & Troubleshooting] kach22:
I did that couple of hours ago already. Downloaded the working EFS partition from a reliable source and flashed through fastboot. Didn't solve the problem. I will check again with the command you have mentioned to see which partition is corrupted. What do you suggest me to do if there is an error in any of the partition?
[Nexus 6P Q&A, Help & Troubleshooting] parvezrobi:
bro, same problem.Here, does tinkering with EFS will work?? Has anyone really solved this issue? I am finding a pattern here, in Marsmallow, there was no problem. But as soon as we switched to Android Nougat, this "no service" issue arised. But, who knew updating a OS will brick a phone!!!! I wish i could go back in time and continued with Marshmallow. I have spent 47k on this phone. Now, i wish nobody buys phone of google or huwaei . DON'T BUY NEXUS 6P :( :( :(

---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------

from where did you download "working Efs partition"? can u provide me the link. I am helpless here :( :(
[Nexus 6P Q&A, Help & Troubleshooting] parvezrobi:
Google will not admit this but there were major security flaws in factory images before jan,2017.

They patched it in Jan. But effected users like us(who got effected on 2016) got proper fu***.

Hence, the only solution is:

find a nexus 6p user who has everything working....make a backup of their EFS using TWRF (ROOT their phone)...and apply that efs to your phone. Both the phone must have same build version. Both phones must be unlocked to use TWRP to make backup amd restore EFS. N.B. EFS are responsible for detecting celluar modem in your device. Maybe it got corrupted.

if anyone is gracious enough to upload their stable NEXUS 6p Efs backup with build number mentioned, it would be really helpful to us, the affected users.
[Nexus 6P Q&A, Help & Troubleshooting] kach22:
@parvezrobi

Firstly this only solution didn't work for me. I restored the efs partition collected from a reliable source (link provided in the conversation between me and Mr. Dhananjay) matching the build number but it rebooted with the restored EFS but the problem is still there. I have also flashed latest radio image (3.81) and it didn't work as well. If you have time you can read the conversation I am having with Mr. Dhananjay who is well aware of the issue and supplied me the fresh EFS. You can try the same solution which he offered, who knows it might work for you. If it fixes your device let me know. Best of Luck.

https://www.droidorigin.com/how-to-flash-custom-rom/#comment-3275809153