yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] raven428:
trying to restore my backup with adopted storage to new phone and sdcard after loosing of original.

I installed lineage-13.0-20170423-UNOFFICIAL-serranodsdd.zip with full device wipes;

I boot the device and choosen to format sdcard as internal (adopted) storage;

I transfer my backup to sdcard through MTP and reboot to recovery;

I restored all partitions, including data from twrp and checked it from twrp file manager: /external_sd/app and /external_sd/user/0 have my apps and their data;

I reboot system, wait for boot and cannot see my apps, which was at adopted storage;

I reboot the phone to recovery again, open file manager and /external_sd/app and /external_sd/user/0 is empty, but /external_sd is still have other directories like /external_sd/media/0 and so on;

I tried to restore data partition again and result the same.

why android wipe my restoration of adopted storage? how correctly to restore my apps and their data to new sdcard? I tried twrp 3.0.3 and 3.1.0 - both have same behavior.
[Galaxy S 4 Mini Android Development] IronRoo:
I'm not 100% sure what you have done.

But I think it's due to adopted storage being encrypted storage and can only be accessed by the phone that created it, not another phone of even if the exact same model. Another phone would use a different key to create the adopted storage so cannot read if from another phone.

And you cannot just copy the adopted storage from one SD onto new SD (using original phone) and expect it to work as again encryption key would be different.

Whatever it is you have done I think it's because the backup and the new phone have different encryption key for SD so it cannot work.

You would need to have files in an unencrypted backup eg you can view on your PC. If you have these files then you can copy them to your new adopted storage.

So you cannot just restore a TWRP backup with adopted storage to a new phone (or SD?) as encryption key is different.

That is my understanding but I might be wrong as I never used adopted storage, partly due to this reason. (But I may have misunderstood how it works, so hopefully someone else can confirm)

That said this thread talks about a possible solution to get TWRP backup onto another phone, but it doesn't talk about adoptable storage, so not sure if it will help you .....

https://xdaforums.com/showthread.php?t=2223545&page=2
[Galaxy S 4 Mini Android Development] filipexda:
Is there any problem using an older version of TWRP (3.1.0-0 TRYOUT) to flash the latest LineageOS build?

Regards,

Filipe
[Galaxy S 4 Mini Android Development] RedSkull23:
Nope, staying on 3.1.0-0 it's ok.
[Galaxy S 4 Mini Android Development] edav.mx:
Encrypt

Hi guys, firstly let me thank you for all the work, it's great!

I did find an issue with 3.1.1 and lineage 14.1-20170630-NIGHTLY-serrranoltexx, it seems I'm unable to encypt phone, is this a know issue? I haven't tried with any other version of twrp or lineage yet, I come from cm14 which did encrypt correctly.

Thanks.

- Erik
[Galaxy S 4 Mini Android Development] Frank.Furter:
Sucessfully installed LineageOS 14.1 on a serranoltexx with the 3.1.1-0-0 version. Thanks! Yet, it takes a pretty long time (> 5 minutes) until the menu buttons appear after TWRP splash screen.
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks,

The long booting time is likely caused by adopted storage on your device and also because S4 mini series are not a recent product since a while now (ramdisk décompression)...

Cheers [emoji482]

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Chris56:
I have successfully installed lineage-14.1-20170714-nightly-serranoltexx-signed.zip with 3.0.2-1

Chris
[Galaxy S 4 Mini Android Development] umuturunc:
Restoring stock rom's backup causing too much fcs. v3.0.3-0 behaves same.

9190 4.4.2 stock SER rom

Edit:Hmmm. I've managed to get a working backup. I was just backing up my phone without changing default values. Now I tried including cache. If I backup system+data+cache+boot and restore it,, I don't get any force close. (v3.0.3-0)
[Galaxy S 4 Mini Android Development] ne0zone75:
I am working on latest upstream code... updates will come shortly...

Cheers [emoji482]

Tapatalked from my OnePlus 3

PS : i am glad that it is working for you now [emoji106].
[Galaxy S 4 Mini Android Development] Phenom2122:
Just want to say that I've been using the tryout version on my i9190 and it's basically perfect. Not using the stock rom but backups work fine for me.

Maybe I've never noticed this before but I've realised that TWRP doesn't update partition sizes. For example, it will read my SD card as 500mb free, then I go into the file manager and delete another 200mb but TWRP will still read it as 500mb free. The only way it seems to get it to refresh is to reboot. Is this normal?
[Galaxy S 4 Mini Android Development] jonathan2020ec:
I do all the steps because I do not go into recovery mode my device is a duos
[Galaxy S 4 Mini Android Development] IronRoo:
you mean you can't get into "recovery" mode? But you can get into "download" mode?

You can try setting "advanced restart" in Linage developer options, see if you can get it that way.
[Galaxy S 4 Mini Android Development] dav1129:
Is 3.1.1 TRYOUT also suitable for S4 Mini DUOS i9192 serranodsdd?

sorry after clicking DS I see that maybe it is. At first I didn't realise what DS stood for. But now I guess Dual SIM ......
[Galaxy S 4 Mini Android Development] ne0zone75:
Yes you're right, 'DS' stands for dual SIM.

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] thesteel8:
Hello, when will this be compatible with Android N custom ROMs? I would like to install LineageOS 14.1 on my old S4 mini, but I haven't done it yet as the disclaimer says you should not install custom Android N ROMs with this recovery currently.
[Galaxy S 4 Mini Android Development] :
IIRC, the only issue with N roms with this recovery was with backup/restore. And this was working last time I tested. So, you can be confident that you can flash N roms and gapps no problem. There is a chance you might not be able to restore a backup without some small errors like developer settings disappearing. But as I said, when I tested it, worked perfectly.

I would guess ne0zone75 has just forgotten to update the OP. Most users of this device are flashing N roms fine.
[Galaxy S 4 Mini Android Development] xdmusicbx:
Hell. I'm running 3.0.2 and backup/restore works fine for me.
[Galaxy S 4 Mini Android Development] ne0zone75:
Yes, you're right.

I am working on latest upstream TWRP code and new files will be available along with a massive OP cleanup when i will find some time to do so...

My best regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Snofru1:
In my case it takes 15 minutes (!) after the appearance of the TWRP splash screen until I can start using TWRP. Is this normal?

I use TWRP 3.1.1 on a I9195 LTE with adopted storage on a 256GB SD-card.
[Galaxy S 4 Mini Android Development] Smeagal192:
If I remember correctly, memory for sdcard limited to 32gb for S4 mini, surprised if you have 256gb working, no wonder it takes so long to load!!
[Galaxy S 4 Mini Android Development] heilbron:
Fast sdcards with much more memory than 64GB are working fine, see here for more details: https://xdaforums.com/showthread.php?p=64740369
[Galaxy S 4 Mini Android Development] Snofru1:
My 256GB SD card (which is filled to more than 50% with music, maps, etc.) is running without problems. It´s only TWRP that needs really long to start.
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
Try flashing stock recovery.

It reads it.
[Galaxy S 4 Mini Android Development] Snofru1:
I don´t understand...

TWRP can read my SD card, I am just surprised that it takes so long to start.
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
S4 mini does not supports 256gb sd that's the reason
[Galaxy S 4 Mini Android Development] mdx54:
LineageOS 14.1 update app

Does TWRP LineageOS 14.1 update from the app work with either 3.0 or 3.1.1? I'm struggling to perform the update from the zip file either from the OS update facility or using TWRP directly. The zip archive downloads properly to /data/data but any attempt to install the update fails with TWRP querying for password first (expected - using LineageOS encryption) but then making it to the TWRP main menu instead of proceeding to update as one would expect. A manual attempt to install the zip from TWRP fails with TWRP stating the zip file is corrupt (it isn't, checksum matches).
[Galaxy S 4 Mini Android Development] Old Jimbo:
For my i9195, I've tried to flash recovery.tar.md5 using Odin v3.12 but without success. I followed the steps above but when I get to step 5, the phone won't restart by itself, it seems to be stucked. I've waited for 15 minutes or so, but nothing happent.

Odin's log:

<ID:0/027> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/027> Odin engine v(ID:3.1203)..

<ID:0/027> File analysis..

<ID:0/027> SetupConnection..

<ID:0/027> Initialzation..

<ID:0/027> Get PIT for mapping..

<ID:0/027> Firmware update start..

<ID:0/027> SingleDownload.

<ID:0/027> recovery.img

<ID:0/027> RQT_CLOSE !!

<ID:0/027> RES OK !!

<ID:0/027> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

Should I wait more? :) Or else, what can I do?

LE: In Odin's main window, above 0:[COM27], is a PASS! message on a green background.
[Galaxy S 4 Mini Android Development] ne0zone75:
If i followed you correctly, your phone is stuck before rebooting after using successfully 'Odin'...

What is written on your device screen please ?

What you could try is :

-> remove your USB cable and reboot manually by using your phone's reboot buttons combination ...

-> remove your device battery if previous step did nothing

-> put your battery back and boot to 'Android' in order to check if everything is OK

-> follow the 'Odin' guidelines, that you quoted, again after having secured your personal data by some way... BUT :

° use a reliable USB cable and USB port on your computer (no USB hub please, plug your device directly on your PC motherboard)

* disable any antivirus software before launching 'Odin'

° which is your PC operating system please ?

Let me know if it helped and if you need further assistance...

Regards

Tapatalked from my OnePlus 3

PS : which of my package are you trying to flash please ?
[Galaxy S 4 Mini Android Development] Old Jimbo:
Thanks [MENTION=5280400]ne0zone75[/MENTION] for your fast reply! :) After 20 minutes of waiting for the phone to reboot by itself, I've closed Odin (exit button) and rebooted the phone manually using its button. TWRP was installed successfully and I already did a backup of the phone's stock ROM. It seems that everything works fine and that reboot thing was the only anomaly. Next is the custom ROM installment... Thanks a bunch for your work! :)
[Galaxy S 4 Mini Android Development] mdx54:
Bug in all the releases tested: will install an archive in a directory on external sdcard but fails when the same update archive is copied to /data/data/org.lineageos.updater/app_updates. The error reads corrupt zip file. The root partition is encrypted but since twrp decrypts it at the start, it shouldn't matter. Why isn't twrp able to pick up the same install from a /data/data directory?
[Galaxy S 4 Mini Android Development] rogers11:
dto.
[Galaxy S 4 Mini Android Development] Nissiah:
I got fresh to Linage OS Nougat 7.1 a few days ago and everything runs fine.

Today I switch my SD card to adoptable storage because my internal storage is to small for all my Apps and now I notice I can't boot into TWRP recovery anymore.

Always freeze at the TWRP start logo screen, when I remove my SD card TWRP starts without any problems.

Is there a way to fix this so I can boot into TWRP recovery with adoptable storage and without remove my SD card?
[Galaxy S 4 Mini Android Development] Snofru1:
I also use adoptable storage and TWRP works. It just takes really long to start and seems to freeze at the splash screen. You should wait for at least 15 minutes to be sure.
[Galaxy S 4 Mini Android Development] Nissiah:
Awesome thank you very much, it works with patience.
[Galaxy S 4 Mini Android Development] rm43115:
Automatic LineageOS-Update mechanism fails

Thank you ne0zone75, for your work!

I use your TWRP for over a year - I have already successfully moved a defective S4mini to a new device.

But now I wanted to switch to "automatic" LineageOS updates and must note that the automatic update mechanism does not work on the current TWRP 3.1.1-0.

That means LineageOS is booting into the TWRP (when it wants to update itself) and then ... nothing happens!

Is this error known? Is there a solution?
[Galaxy S 4 Mini Android Development] OllieW:
Same problem here! Is this a TWRP specific bug (are all versions affected?) or a configuration error in the Lineage Updater auto-update (recovery) script for the Galaxy S4 Mini? Any solutions would be welcomed - manual update procedure is very annoying because of the "special" path of the Lineage Updater app with the downloaded firmware! It seems that either the path to the downloaded firmware in the auto-update (recovery) script is wrong (different mount points in LOS and TWRP?) or the auto-update script can't be found by TWRP at all..
[Galaxy S 4 Mini Android Development] tomscot2:
Lineage0s 14.1 for serranoltexx auto-updater

1. Auto-updater has never worked with TWRP 3.0.2.1 for me. It reboots into recovery to TWRP's main menu. I have to manually install the update. However, I prefer this because I always backup the current system with TWRP before I INSTALL the update (has come in handy at least once). It was somewhat of a hassle to remember the /data/data/org.lineageos.updater/app-updates folder in the root, however, once I started doing the weekly updates I can now remember it. I find it really simple.

2. I created adoptable storage and now find that auto-updater is not downloading the update to the /data/data ....... folder. It downloaded something somewhere, but I could not find it. I ended up downloading the most recent update via my web browser to the Download folder and then installed it manually.
[Galaxy S 4 Mini Android Development] IronRoo:
[MENTION=5695282]OllieW[/MENTION] [MENTION=8274398]rm43115[/MENTION]

Yes this is what I have been doing as the browser download was much more reliable as updater kept aborting (though this might now be fixed), download is easy to access as it will be in download folder and you can use a checksum app on sha1 since md5 no longer given.
[Galaxy S 4 Mini Android Development] fankool:
I installed 3.1.1-0-0 ... is there something wrong? I thought this was the last version. And, however, on this version hw keys are not working. Do I have to downgrade to 3.1.0-1?
[Galaxy S 4 Mini Android Development] ne0zone75:
I am on vacation ATM. I will work on this ASAP...

Same comment as above...

Same comment as above too...

[emoji106]

Is anybody else experiencing this issue ?!

Thanks to all of you for installing my files and for reporting back [emoji106].

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] MJay99:
As per changelog, auto-updater has changed behavior, it imho now downloads to /data/lineageos_updates.

Hand picking it for install is still the way to go with TWRP 3.1.1 for me, too
[Galaxy S 4 Mini Android Development] bongo2515:
Sry, I'm new here, but is there a way to put LineageOS 14.1 on my s4 mini since LOS 14.1 is the Nougat-version?
[Galaxy S 4 Mini Android Development] IronRoo:
Flashing LOS14 works fine, it also worked for me though I can't recall which recovery ver I was on when I flashed it. Ver 3.0.3 may not backup/restore, that is the only issue. The tryouts ver 3.1.X seems fine many of us are using that, I'd suggest you use the tryout, but whichever ver you use it will flash LOS14 fine but you might want to use alternative backup method (you have to for your all your media files anyhow as TWRP does not back up the media partition!)
[Galaxy S 4 Mini Android Development] IkerST:
Do this works too in the GT-I9195L??
[Galaxy S 4 Mini Android Development] rm43115:
Don't know - I have a GT-I9195 - but I think you can test it risk free.
[Galaxy S 4 Mini Android Development] ne0zone75:
No ! It is not working with GT-I9195L because AFAIK it does not have the same chipset.

Please do not use my files with your device.

Thanks

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] mielletseed:
I thought this too first. But one shouldn't take GT-I9195I for GT-I9195L. The newer 9195I has an other chipset but the 9195L seems to be identically to the "normal" 9195 as far as I have read.

best regards
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks ! I mismatched GT-I9195L with GT-I9195l.

My kindest regards

PS : FYI GT-I9195l features a QUALCOMM Snapdragon 410 AND the S4 mini series do have a Snapdragon 400...

[MENTION=7713764]IkerST[/MENTION] : Yes, you can proceed with your GT-I9195L.

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] rm43115:
LineageOS Update mechanisman / function

Hello ne0zone75, is there any success in the support of the automatic LineageOS Update mechanisman / function?
[Galaxy S 4 Mini Android Development] ne0zone75:
I will build new recovery images as soon as TWRP upstream code version will have bumped. I am building those along with LineageOS sources. So, my guess is that it is a recovery code issue : usually TWRP is built using OmniROM sources... maybe there is some incompatibility between TWRP and LineageOS about this particular feature...

Anyway, IMO it can be fixed in a way or another...

Cheers [emoji482]

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] rm43115:
Fine - I'm already looking forward to this OTA update comfort ... so even laity will be able to bring their S4mini to a super-current patch level.
[Galaxy S 4 Mini Android Development] miguel497:
Can confirm. I'm using the GT-I9195L model with TWRP 3.1.0.0 and everything works perfectly.
[Galaxy S 4 Mini Android Development] avalondrey:
Merci
[Galaxy S 4 Mini Android Development] droopyar:
Links from first post are down

https://androidfilehost.com/?fid=24499762636003165

Shows ERROR
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay and thank you for reporting back...

I will fix this ASAP and i will release updated packages soon...

My best regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] bongo2515:
I don't know if this got mentioned before, but when I tried the tryout in the end of september....I always forgot to mention this here...well whatever...the thing is at end of the installation of the tryout or LineageOS (I don't remember) there were "wipe dalivk cache" or something, and "reboot system".

I pressed "reboot system", but it powered off completely. I had to manually turn my phone on. It's not hard to press the power button, but if I press on the "reboot sytem" button, I expect it to reboot automatically.

So that's maybe a bug.

Also there was something, when I wanted to wipe something called Usb otg (because I wanted to wipe everything for a fresh install of LineageOS) or something and I got:

E:Unable to wipe '/usb-otg' -- unknown file system 'auto'

Unable to wipe /usb-otg.

So maybe this information can be helpful in any way.
[Galaxy S 4 Mini Android Development] MJay99:
Not saying it isn't, but at least I can't confirm this for my two devices on 3.1.1- reboot does reboot the device as intended here. Only issue I'm still having is with the OTA updates still needing manual install in TWRP.
[Galaxy S 4 Mini Android Development] bierma32:
To wipe USB / Otg is not necessary. It means it will wipe a ext.HDD or USB Stick
[Galaxy S 4 Mini Android Development] ne0zone75:
Well..., i think that everything has already been written down to answer your questions [MENTION=8566394]bongo2515[/MENTION] ... Thanks for reporting back !

[emoji122] to all of you who are keeping this thread alive.

Updates are coming... you will tell me if LOS updating process is fixed... ?

Stay tuned !

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening everyone,

Updated packages are building... [emoji106]

They will be available very soon and are versioned v3.1.1-3...

You will tell me if LOS updating script is working with them...

Regards

Tapatalked from my OnePlus 3

INFO : new files are now available from AFH as 'Odin ready' archives as usual for TRYOUTs

3G | DS | LTE
[Galaxy S 4 Mini Android Development] MJay99:
Thank you very much for this new tryout! The image flashed and booted successfully... but, sadly, the attempted LOS OTA update, after downloading and checking, just rebooted into TWRP and dropped it into the starting menu - no automation.

A manual picking of the latest LOS update from /data/lineageos_updates/ did install successfully afterwards (without the former log errors, so there definitely is some positive change).
[Galaxy S 4 Mini Android Development] rm43115:
First of all many thanks for your efforts!

I've flashed the new TWRP version - so far so good - at the moment I can not test LOS updating - I have lineage-14.1-20171103 installed and I'm waiting for the new LOS version - as soon as it's there, I'll test and give feedback.
[Galaxy S 4 Mini Android Development] Claudio4780:
Tapatalked from my OnePlus 3

INFO : new files are now available from AFH as 'Odin ready' archives as usual for TRYOUTs

3G | DS | LTE[/QUOTE]

Have you got the Flash version for the DS?
[Galaxy S 4 Mini Android Development] ne0zone75:
ATM only 'Odin ready' packages are available for the three S4 mini variants for the latest TRYOUTs, including DS one...

If you are searching for a recovery flashable file, i will release them too in a few days...

Stay tuned

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] fankool:
thank you for this new release. Just installed, it works. I'll try it soon.
[Galaxy S 4 Mini Android Development] rm43115:
I can saidly confirm - LOS-OTA-Update-mechanismen unfortunately fails. :(

Reboots into TWRP and stops in the main menu.
[Galaxy S 4 Mini Android Development] ne0zone75:
OP is updated

I've just updated TRYOUTs post link in post #1.

Are they working well ?

Unfortunately LOS updating script is still failing with it... :crying::crying::crying:

Regards
[Galaxy S 4 Mini Android Development] rm43115:
Can I help somehow to get to the bottom of the problem?

For example, with certain log files?
[Galaxy S 4 Mini Android Development] ne0zone75:
That is a kind offer but i am afraid that this issue cannot be fixed on my side... of course i am maybe wrong and if any of you has any info. about how to fix it, it will be more than welcome [emoji6]...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] MJay99:
Not sure if I should even risk a post, since I am in no way a programmer or having much experience in building Android, but is there maybe some build flag related to OTA updates that might affect it not running at all?

I did have a very tiny peek into TWRP's Android.mk and a few header files and saw this:

ifeq ($(AB_OTA_UPDATER),true)

LOCAL_CFLAGS += -DAB_OTA_UPDATER=1

I wasn't able to dig into it much more and am not even sure it is related to the OTA integration, so it's just wondering and groping in the dark as of now.
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks for this info. it is maybe a good lead, i will check TWRP build flags in its source files and i will then offer updates...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Anewkine:
Hi,

Flashed in my I9195 with FlashFire and everything works perfectly.

Backups, Restores, Install, Files manager, everything works.

Thanks for your great work [MENTION=5280400]ne0zone75[/MENTION]

Regards. :svetius:
[Galaxy S 4 Mini Android Development] Claudio4780:
Any news ?
[Galaxy S 4 Mini Android Development] ne0zone75:
I will release them this weekend for v3.1.1-3 [emoji106]...

Regards

Tapatalked from my OnePlus 3