yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] suapoc:
Thank you, i just switched to emulated storage and it was doable even though i made some errors on the way ;D :

I used the files provided in the post of Weibl67 and somewhat followed his instructions. There was no valuable Data on my phone or on sdcard0 in particular so i just skipped anything related to backing up my data.

i realize that windows destroyed the file name of the repit.zip by replacing "=" with "_"

*edit the renaming issue was caused by xda forum... some kind of wonky renaming mechanism

rename file

my first attempt fails as it is obviously a bad idea to start scripts from a partition you are about to format

repit is kind and just displays an error message that itfailed and moved the script to /tmp

hit back button, see the repit.zip in \tmp and execute it

realize that i somehow have to edit /data/system/storage.xml in twrp recovery

TIL twrp actually provides a terminal with an editor vi ;D

i mount the needed partitions via twrp

i need nearly 20 minutes to relearn basic vi and to remove the "XML attribute primaryStorageUuid="primary_physical" in Storage.xml

reboot device.... it somehow worked ;D

if anybody wants to make his life hard by using vi to edit the storage.xml file here are the basic commands:

i - to enter edit mode

ESC (is actually on the keyboard)- exit edit mode

arrow keys navigate in file

to leave vi you have to leave edit mode: (ESC)

:q - leave and discard changes

zz - leave and save changes

switching to emulated sd fixed following issues for me(LinOS-14.1-20170222-Nightly-i9100):

the explorer can finally open the (emulated )internal SDCard

storrage now displays sane values for the size of my system partition

however the explorer still can't access my external SD-Card.

To make things even easiear one could provide a script that automatically edits the storage.xml file.

this could be a special repit/script file that has a few lines more after the repartitioning stuff...

I also don't understand why there is no link to a suitable repit file in the OP. It took me 30 minutes just to navigate the download page and i still didn't find the right file there ;D

However now that i have used it i really really like it. Great tool that makes things so much easier.
[Galaxy S II Original Android Development] rINanDO:
New TWRP Build is up

The only change is it is now build on top of Android M so it should work in Android M and N.

Download here: TWRP-3.0.3-EMU-MIGRATION_M-20170224.zip
[Galaxy S II Original Android Development] Pier_89:
And what about new TWRP Recovery NO-Emulated?

Any news about it?

Is it in the future necessary to switch to emulated storage (ex. for a new Android version) or not?

Thank you :)
[Galaxy S II Original Android Development] the.gangster:
Just to point out: All the development was done by [MENTION=2222292]rINanDO[/MENTION] (and of course by [MENTION=4141005]Lanchon[/MENTION] showing us the way). My "hard work" was only limited to reading, testing what Lanchon and rINanDO published, sometimes looking at code and trying to give advice where I thought something was wrongly stated or unclear. While I was still experimenting with modifying TWRP for that myself in the beginning, rINanDO came up already with first builds and meanwhile delivered a great implementation to automate the whole process. (If only users followed his instructions)

"Flashing on top of incompatible data" is related to different releasekeys between official Lineageos- and non-official- and CM-builds. I already answered to that several times here and/or in the main thread. (nothing to do with storage-type)

And the renamings upon download were one of the reasons why I asked [MENTION=3964850]Weib67[/MENTION] to remove the downloads some posts back. Sadly he didn't reply yet. I still hope he does though.

For the camera you could have also shared the solution to help others in case they experience the same issues. Now it's not clear if you simply had formatted non-emulated sd with wrong FS or didn't switch to the storage in the camera-settings, or whatever else ...

I already answered your crosspost in the mainthread.

It would be great if you didn't repost the 'wrong' way. If you'd read here you would have known that following the full instructions given by rINanDO would have done the job without the need for manual editing. Deciding there is no valuable data to backup and restore instead of backing up and restoring at least almost empty partitions was leaving the migration-track.

And posting the wrong way in the main thread only makes it worse if you ask me.

Cool, thank you for rebuilding. So now the danger to bootloop will be restricted only to those reverting to IsoRec-kernels for LP and earlier. Great!

Please stop spamming in the wrong threads (and asking for ETAs). (I also replied in the main thread)
[Galaxy S II Original Android Development] suapoc:
it's not supposed to be a howto...

it's not the wrong way. it's just another way to do it.... but you are right it's more a collection of errors you can make and how to fix them if you made them. so i think it can be helpful for people that made errors like weib67 for example... or all the other people that will wonder why the repit.zip doesn't work because exfat or windows don't like "=" in filenames.
[Galaxy S II Original Android Development] the.gangster:
The reason why I find this annoying is simple:

rINanDO put a lot of work into making it almost dummy-proof and gave instructions on how to use this special recovery.

But if you see quotes of these steps, they are usually those where the key step is skipped: the recovery of the previously backed up data from internalsd with the choosen option to migrate.

Even in your description I read, that you decided to skip these parts as you had no valuable data, as was already the decision of weib67.

It's fine to give a solution for people who made mistakes, and also guiding them thru vi-commands, but I cannot even see a single hint in your posts, that the whole manual effort is not needed if you only choose to do the backup/restore. Maybe you understand my comments or my point of view better now.

If you did backup and restore using this migration-option there would be an error in the recovery scripts to be fixed, but it reads as if you simply went the same way like weib67 not using it.

Also explained that in here already: it is not a filesystem-restriction. It's the crappy forum-software on XDA that renames the repit-files.

If you download them from their original location (linked in the OP) this doesn't happen.
[Galaxy S II Original Android Development] suapoc:
that's because many people installing this rom right now have no valuable data on the phone after repartitioning it with odin to to accomadate the large 7.1.1 system images.. I also thought this forum is about dsicribing errors and solutions and not about providing safe spaces^^

maybe it would be a good idea to provide a button that removes the primary flag in /data/system/storage.xml and yes calling that migration is confusing...

1. I had nothing to backup and restore so that step seemed unnecessary

2. It's not the route i took so i why should i do that?

3. it's not that much effort...

4. just look at the time i published those posts... cut me some slack.

yes... this seems to be true. i still don't understand why renaming on the device failed yesterday maybe some whitespace in the wrong place.

I still can't find the link to the repit file in the op. ;D
[Galaxy S II Original Android Development] the.gangster:
[MENTION=8093949]suapoc[/MENTION]

There is no direct link to "the file" in the OP. As usual Lanchon links to the repit project to give you the chance to read what you will be doing and to make you always use the latest version.

[IRONY]

Therefor It's incredible three clicks far away from the OP. First one to the project itself, second on the Downloads-link in there and a final one choosing the newest folder.

Damn, there is a fourth one, as you need to pick the version for your device.

And then you still face the challenge to rename it as suggested in the OP or to the values of your choice.

[/IRONY]

Not meant to be offensive: But let's stop this senseless discussion here. You obviously didn't get my point anyway.
[Galaxy S II Original Android Development] kraehetest:
If made a flashable zip-file which flashes a modified storage.xml. I made a mistake in the updater script. So the storage.xml wasn’t flashed. Now everything is fine.

BTW, if you flash an official nightly, every time you must modify the storage.xml before you boot your device.

[MENTION=2222292]rINanDO[/MENTION] (and [MENTION=6560258]the.gangster[/MENTION], [MENTION=4141005]Lanchon[/MENTION])

In your emu-build (lineage-14.1-20170126-UNOFFICIAL-i9100_emu.zip), the 8MB SD Partition isn’t shown. In my modified nighty I see the partition. Are there more differences in your build? Do you unmount or hide the partition? How you do that?

thank you in advance
[Galaxy S II Original Android Development] rINanDO:
In my emu-builds I removed sdcard0 in fstab. And enabled multiuser overlay option.
[Galaxy S II Original Android Development] kraehetest:
Can you explain a little bit more, i have never use fstab. The command line you use...

Thank you very much
[Galaxy S II Original Android Development] rINanDO:
I don't use a command line. Fstab is the filesystem table which android uses to mount storage when booting. See his commit

https://github.com/rINanDO/android_...mmit/30fb687bf51b99e6925ca65fd1cd56df0339600c
[Galaxy S II Original Android Development] the.gangster:
This is not true.

I have already updated my official nightlies several times and never had to touch the storage.xml again. Not a single time.

Maybe there is another reason for this, so please describe in detail what you are doing if you flash a new nightly.
[Galaxy S II Original Android Development] PhoenixNZ:
Interested to know as well.

Am on 0126 with emulated storage and interested in updating to official latest.

Just wipe cache and davilk, flash official and gapps?
[Galaxy S II Original Android Development] kraehetest:
I have not yet dared update without modifying storage.xml.

At next time a make a backup with emu twrp an check this.

But good to know, that everything should running fine.

---------- Post added at 04:20 PM ---------- Previous post was at 04:03 PM ----------

I'm not sure if that really works. "Flashing on top of incompatible data" is related to different releasekeys between official Lineageos- and non-official- and CM-builds.

You should try a backup in twrp. Then install experimental and nightly from lineage homepage. I do not know if it works and I also give no guarantee. I have reinstalled everything from scratch.

1. lineage-14.1-20170226-experimental-i9100-signed.zip

2. lineage-14.1-20170228-nightly-i9100-signed.zip

3. open gapps
[Galaxy S II Original Android Development] PackElend:
short one, I've just read through all 16 pages, that sounds very promising (great work [MENTION=2222292]rINanDO[/MENTION] [MENTION=6560258]the.gangster[/MENTION], [MENTION=4141005]Lanchon[/MENTION]) but if I use dropbox etc. I will easily hit the 16GB limit of the build-in storage again. How can I optimally combine it with an external SD Card (e.g. Adoptable Storage) ?

Did I understand correctly that I can flash again RR OS on it instead of Lineage OS as described in the very beginning since anyone is using an adapted Linage rom?
[Galaxy S II Original Android Development] laserkater:
I'm not sure whether to ask the questions here or in the TWRP-Thread:

Are there any devices with two alternative but official TWRP recoveries?

Is it necessary to keep the two versions seperate (emu and non-emu)?

If so, what will the next steps be? I'm not asking for an ETA. Just want to know if we'll ever have an official emu-TWRP.

Many thanks!
[Galaxy S II Original Android Development] laptopu:
I've just posted on the official los 14 thread but it's definitely worth mentioning here, there are two of us unexpectedly got into bootloop using emulated storage even though it worked fine for days at first, only wiping data solved problem. May not definitely be emulated problem but coincidence both of us have this issue.
[Galaxy S II Original Android Development] rINanDO:
Can you provide a logcat during boot? I'm currently using emulated storage on unofficial and official (two s2's as daily drive). I don't have bootloops after updates/dirty flashes.
[Galaxy S II Original Android Development] the.gangster:
Just using emulated on one of my two phones, but: me neither.
[Galaxy S II Original Android Development] laptopu:
The only thing I could do when this happened was to wipe data so don't think I can provide much in way of help unfortunately. It might not even be emulated storage causing this but it's being reported by me and one other person currently and we both have emulated storage.
[Galaxy S II Original Android Development] PackElend:
[MENTION=4141005]Lanchon[/MENTION] can you align you post on the first page with (IMHO) latest guide

otherwise is hard to find the right guide. May you even merge it with

Thank you.

[MENTION=2222292]rINanDO[/MENTION] TWRP 3.1.0 was released some days ago, could you update your TWRP build?

Thank you.
[Galaxy S II Original Android Development] rINanDO:
New TWRP EMU-Migration build is up!

Only upstream merge (and build on M)

Download here: TWRP-3.1.0-EMU-MIGRATION-M-20170318.zip
[Galaxy S II Original Android Development] laptopu:
Using brave browser, download failed due to missing sd card I am already emulated on latest nightly, how do u get around this please?
[Galaxy S II Original Android Development] MigoMujahid:
Try clearing app data or reinstall it, or go to the settings of the app and see if it has an option to set the download directory and choose the correct place.
[Galaxy S II Original Android Development] laptopu:
Disabled storage permissions and reenabled that worked
[Galaxy S II Original Android Development] the.gangster:
LOL [MENTION=4419266]laptopu[/MENTION]

for someone, as experienced and as frequently posting here like you do, I would have assumed you had tried such basic steps already before posting your problem in (at least) two threads.

:)
[Galaxy S II Original Android Development] laptopu:
Yeah I thought about hiding in the forest after posting that one ;) lol
[Galaxy S II Original Android Development] iwl:
Hi,

it's a little hard to get the facts out of this long thread as newcomer.

I have a S2 with Cyanogenmod 13/6 / TWRP (not 3.x)

Because the internal sdcard0 and external sdcard1 I have several trouble.

I can't get google music storing music on external sdcard1 e.g. and so have all my music.

Is it possible to partition the S2 like other phones having 1 internal memory and 1 external sdcard only and so work like all other phones and no confused apps about the 2 sdcards.

I would upgrade to latest android / lineos / 7.x then also.

It's only my backup phone and isn't very usual so and can be completely wiped.

Would root it also if recommended.

I would appreciate some help to get that done.

Regards Ingo
[Galaxy S II Original Android Development] the.gangster:
[MENTION=8161225]Moertel[/MENTION]

check your list against the how-to of rINanDO and I guess most of your questions are gone.

Anyway my answers to your questions according to your numbering:

To 1. will be done by recovery

To 2. see how-to

To 3. yes it is (or would be)

To 4. if you read about the preconfigurations that is automatically done by repit you knew that +same+keep will always be added for a partition that is not provided in the name or for a parameter that is not given for a partition that is. Don't use +swap.

To 5. if you follow the how-to it is enough to only restore the sd-card to the new emulated storage. Nevertheless, if you want to wipe and restore stuff that wasn't changed at all you can also do that. But it is important to use the migrate-switch when you select the sd-card in the restore menue as this will does the switch to the emulation itself (the change inside storage.xml).

It's no problem if you resized the preload partition earlier already, as already explained, repit will leave it as is if you don't redefine it in the name.

So simply follow rINanDO's how-to and you'll succeed. Use his latest build. If it is really still not emulated at the end of the process, you can still manually modify the storage.xml then. But I guess this should not be needed.
[Galaxy S II Original Android Development] Moertel:
Hello the.gangster and thank you for your help. Everything worked fine. I have now only one question. Is there any way to let the sdcard0 completely disappear from the system? I mean from the memory management in the system under setting / storage e.g. In addition, I would still like to know how I update my Emulated Lineage or does it work?

So I do not believe it since I'm already forever busy and 1000 different possibilities tried to find a solution but I can even add it with times. The whole change to the Emulated system I have only carried out because I always the error message: 13 volume partition disk: 179_0 public failed with 400 17 Command failed (numbers differ depending on the frequency of the trials) when trying my internal SD via lineage in the system Format. Until CM11 has still everything works, CM12 I have not tested and since CM13 is the problem. If someone for a functioning and comprehensible solution for the problem has that would be really great.
[Galaxy S II Original Android Development] the.gangster:
[MENTION=8161225]Moertel[/MENTION]

How to update:

update as usual. Updating won't change your storage-configuration unless you wipe the data partition.

Remove the non-emulated SD (/dev/block/mmcblk0p11) from settings' storage menu:

Never tried (and wouldn't even like to remove it there). Most apps simply use the emulated anyway so I like to keep up an option to access the non-emulated if I need to. I didn't even minimize it to the maximum (or lets better say minimum) possible value (of 8MB) as I wanted to be able to keep some files there for the case I need them once.

Not sure if I understand the rest correctly at all but it sounds as if you might have once resized partitions with odin (and Pit-files) without properly formatting internal storage again. Or you might have used an unsupported filesystem on it. But if you used the repit-options now with "sdcard=min+wipe" it should have formatted your non-emulated storage with its default filesystem (vFat).

(maybe you should add again your german original to above post, but on the long run, as you obviously really need google translate for every post, you might be better off, posting to a german forum like e.g. android-hilfe.de where - as far as I know - some gifted talents from here also share their knowledge ;) LOL)
[Galaxy S II Original Android Development] matee89:
Do you also encounter camera and gallery problems after migrating to emulated storage? With default LOS gallery and camera apps, I can't save any image or switch storage for photos in camera app settings (not enough space error). I can't even take a screenshot due to insufficient storage space. Do you have any workarounds for those issues? Everything else seems to work correctly (although "minimized" sdcard0 partition is still mounted).
[Galaxy S II Original Android Development] the.gangster:
[MENTION=3842399]matee89[/MENTION]

if re-selecting the storage location from an app's menu/settings doesn't already fix it: clear an app's cache, if still not enough, also clear its appdata or reinstall it.
[Galaxy S II Original Android Development] matee89:
Wiping cache through TWRP did the trick - camera and gallery apps works without any issues. Now, I will try to remove that minimized sdcard0 partition from automounting. I guess it should be similar to any linux distribution (/etc/fstab, saw that rINanDO did that in one of his customized LOS builds).
[Galaxy S II Original Android Development] The Weeping Angel:
Also looking for the same work around as I cannot recieve files sent from bluetooth or take photo's . Another thing I have noted is that after flashing Gapps and installing Titanium Backup to remove a few unwanted apps I still find them in the menu list.
[OnePlus 3T Questions & Answers] vvaklnprm:
If we get the camera blobs for our phone, will our custom ROM devs be able to improve the post-processing and/or image quality using the sources?

Or will it be too difficult a project to work on?
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] tawkeer:
Hi,

I tried to use the inbuilt call recorder to record whatsapp, imo calls but it wont let me to.

Can anybody suggest how to record the internet calls (like imo,whatsapp,skype)?

Thanks
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] thilak devraj:
there are a few apps on ply store , check them out, but i dont think they are gonna work perfect
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] hassanjavaid8181:
Search on play store...may be you will find something useful related to your issue
[Android General] nurul.momen:
asdf
[Android Apps and Games] SingleMind:
Recently my bf started working out so i made an app for him. It is simple but very useful guys in his gym loved it so i made one for google play. Enjoy it.

id=com.sporttimer.singlemind.sporttimer
[OnePlus 3 Questions & Answers] Dipinn Verma:
After the update to Nougat, my PC does not recognize my OP3, doesn't even show any mobile device in Device Manager! Please suggest, tried resetting phone, restarting laptop, installed drivers also, nothing working

Update: So after starting from scratch, following the guide https://xdaforums.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757 I reinstalled 4.0.2 and everything working smooth as ever, surprisingly, laptop recognizes phone in fastboot and adb, but not MTP.

What can be done? anyone
[OnePlus 3 Questions & Answers] Puddi_Puddin:
And of you boot into fastboot?
[OnePlus 3 Questions & Answers] Dipinn Verma:
it doesn't recognise there also
[OnePlus 3 Questions & Answers] Puddi_Puddin:
It doesn't boot? Try unbrick method 2.
[OnePlus 3 Questions & Answers] Dipinn Verma:
no, the phone is working fine, and surprisingly works with any other laptop, but not the one through which I updated it to nougat, the one which I have always used it with
[OnePlus 3 Questions & Answers] Puddi_Puddin:
Hmm, and when you phone is on does it show something in the notification row?
[OnePlus 3 Questions & Answers] Dipinn Verma:
no nothing out of ordinary, even when I switch on mass storage, nothing, I have the verity-error also, can that be the problem? coz I lost my twrp and root when updated, should I do everything again from scratch ?
[OnePlus 3 Questions & Answers] Puddi_Puddin:
DM verity should be a issue, I do recommend you to start from scratch..
[OnePlus 3 Questions & Answers] Dipinn Verma:
thanks a ton for prompt reply ! I'll post here how it goes, it might help someone else
[OnePlus 3 Questions & Answers] Hw4ng3r:
DM-verity is a non issue with MTP/fastboot/adb. It's usually related to the USB cable or port itself, or a driver issue (fastboot/adb or device).

When you connect and toggle the USB setting to MTP, toggle it to charge only then to MTP again. I've noticed in the past that it takes longer for the PC to recognize or it requires a second try.
[OnePlus 3 Questions & Answers] Dipinn Verma:
okay, so this is strange, i did what you said, PTP mode is working, only pictures are accessible though, nothing else, so the problem seems to be with MTP only
[OnePlus 3 Questions & Answers] null0seven:
It's from windows. I think youre on windows 10 and have updated without knowing. Then youre phone it's not recongnise by pc.

Reinstall windows.
[OnePlus 3 Questions & Answers] Dipinn Verma:
windows 8.1 only, hasn't changed. I'll try following this guide tomorrow : https://xdaforums.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757

and start from scratch, please suggest if I should be following any other guide if there is one. Thanks.
[OnePlus 3 Questions & Answers] null0seven:
Mate, i can't tell you what to do.

On my case, it was windows 10. How i know? I try co connect at work (windows 7) & it workt fine. Reinstal windows, all ok.

FIRST, i suggest to check on another PC. If it works, 100% it's youre windows.