yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] gm0:
If you can boot into recovery you're not bricked, not even soft-bricked. Your account is very detailed on irrelevant information but mostly skips over what you actually did to mess your system up. Anyway, you can change partitions the same way you did it the first time, but CM13 also needs a bigger system partition if you're planning to flash any form of gapps as well so there's really no reason to go back to default.

So if you tinkered with the partitions after you had a working LOS install (is that even possible with LOS recovery?) just flash the pit file you used last time to get 1GB /system. More likely you'll just need to properly format your partitions though (you do not typically want to change ext4 formatted partitions into exFAT, for example).

PS: By the way, since you're not actually asking for help with LineageOS I suppose you're rather off-topic in this thread.
[Galaxy S II Android Development] ori.on:
Thanks for your replies guys! I followed Nobby1960 advise and flashed the Odin-based TWRP recovery. That worked! Great! So I am now on TWRP 2.8.7.0. However, when I try to wipe the dalvik cache it fails. Wiping "cache, system, data, emmc" succeeds however. What does that mean?

Also, when I try to install a zip, I can only select either EMMC or the Micro-SD card as sources. Is that normal?

Currently I only have CM13 on the SD card. Trying to flash that failed.

Before trying anything stupid again and messing things up even more, I figured I asked for your advice first.

Can I flash a ROM via ODIN? Do I flash the ROM first, and the PIT after? Or do I do it in one go? What's a source for the Samsung stock ROM? Sorry for being so noobish - I just am when it comes to Android ;)
[Galaxy S II Android Development] gm0:
[MENTION=8125930]ori.on[/MENTION]

- flash the latest official TWRP, not that ancient version

- I wouldn't repit again if you're already having a 1 GB /system partition.

- nothing wrong with internal and external sdcard as .zip sources, if you need other partitions you need to mount them first, but why you would want that is beyond me - the only thing you should do with the other partitions is wipe them (if you really changed them to exFAT you should change that again to ext4)

- last but not least, to get on topic for this thread, download and flash the latest LineageOS build (http://wiki.lineageos.org/i9100_install.html)
[Galaxy S II Android Development] ori.on:
Thanks for your reply gm0!

In the meantime I had tried to flash a Samsung Stock ROM plus the original 16GB PIT file - via Odin. That worked, but during the boot into the OS errors popped up like "failed to mount /cache" and "failed to mount /efs". So I went back to the Odin-based TWRP recovery.

Now, when I go into "Advanced Wipe" I noticed that I can look at each partition as of what size and file-system it currently has. This is what I currently have:

cache: 98 MB, ext4

system: 503MB, ext4

data: 0MB, f2fs <<===

eMMC: 7176MB, exfat <<===

Dalvik Cache: ERROR "invalid partition selected" <<===

The first two are probably OK (apart from the 503MB size for system), But the last three partitions look "wrong" to me? Data is size 0, and a weird FS. eMMC is exfat (ok that's probably what I did wrong), and dalvik is not accessible at all?

I figure that all my attempts to flash any OS will fail until this is resolved?

You originally asked why I went to exFAT in the first place? That's from here

https://xdaforums.com/galaxy-s2/orig-development/repartition-memory-s2-t3018749

Note, after I had done that step "Internal Storage" was listed as eMMC. I figured my troubles started with this step...
[Galaxy S II Android Development] ThePhoenixII:
f2fs did not work for me (cache and data). I had to reformat these partitions to ext4 to make things work.

I used twrp to do it.
[Galaxy S II Android Development] gm0:
Yes there's definitely something wrong with those partitions, /data is obviously messed up and eMMC size is also not the stock one.

I'd re-flash the entire partition table. I'll attach a .pit for a 1 GB /system and 3 GB /data configuration if you want to try flashing that via Odin or Heimdall and then formatting via TWRP (by default they should all be ext4 except for eMMC, that is fine as exFAT - my TWRP calls that internal storage btw, are you sure you've got the correct TWRP version flashed now? https://dl.twrp.me/i9100/).
[Galaxy S II Android Development] ori.on:
That fixed it! I changed the FS for both data and eMMC to ext4, and all of a sudden system showed as 1GB, data as 6GB! (as it should, cause that's the PIT I used)

The I flashed LOS14-1 again, and this time no problems/glitches what so ever! Looking good :) Big Thanks to the developers!
[Galaxy S II Android Development] gm0:
If you format internal storage as ext4 you might run into trouble accessing it from Windows via USB in case that's something you're interested in doing.
[Galaxy S II Android Development] ori.on:
I had not updated to the latest TWRP yet, because any attempt to so failed, because the partitions were messed.

After installing LOS 14-1 the Lineage Recovery is back. I am relatively certain that if I installed TWRP now, it would show eMMC as "internal storage" again.
[Galaxy S II Android Development] gm0:
The Lineage recovery is back because your TWRP version was outdated, so if you go back to TWRP make sure to use v3.0.2.1 because that one is IsoRec compatible and won't be removed when you update LineageOS.
[Galaxy S II Android Development] ori.on:
Ah ok! Thanks for the explanation! That's why...
[Galaxy S II Android Development] jt12345:
Can you please show me which stock rom from sammobile you are referring to? (Can you give me a link to its download page?) Also, what app is telling you that you only have a connection to 3 satellites? Try installing satstat - you can download it here. Here's a screenshot of my satstat (it "locked on" after about 10 seconds):
[Galaxy S II Android Development] Nobby1960:
[MENTION=2709988]jt12345[/MENTION]

Great app - I must test it. First screenshot is indoor (brick built 4-storey house, ground floor), signal strength low but 6 satellites - the second outdoor on our balcony. Stock LineageOS baseband I9100XXLS8.
[Galaxy S II Android Development] gm0:
10 seconds is pretty slow with that many satellites in view, mine usually takes 3-5 seconds (XXMS4 modem, custom gps.conf).
[Galaxy S II Android Development] thepredictor:
Illumiate buttons......

Hello

I need help guys, When I enable illuminate buttons from settings the lights wont turn off, timer doesnt work so i have to disable it.

I need help on how to make illuminate button lights turn off after 1 sec or my desired timed setting

Thanks
[Galaxy S II Android Development] the.gangster:
Hello

Please read here and follow the link in there.
[Galaxy S II Android Development] thepredictor:
So what can I do witn BLN mod other then making leds work? Is it safe to flash bln?
[Galaxy S II Android Development] jt12345:
I'm glad that you like the app. (For me, the fact that it's open source is an extra bonus - I love learning how these things work!)

As far as I am aware, there isn't a "Stock LineageOS baseband" - I might be incorrect, but I think that most (all?) custom roms do not include a baseband at all, so unless you have intentionally flashed a baseband, you will continue to have the baseband that came with the last stock ".tar.md5" file that you flashed. I normally use I9100XWLSW_I9100XXMS2_I9100XEULS5_HOME.tar.md5 when I want to "return to stock", hence my baseband is I9100XXMS2 (even though I have flashed dozens and dozens of CM and LOS roms since then).

HTH :)

---------- Post added at 06:26 AM ---------- Previous post was at 06:06 AM ----------

That sounds good! I can upgrade to XXMS4 - would you like to share your modifications to your gps.conf (or give us an idea where you got it from)?

Do you use A-GPS? If yes, what app do you use to download the almanac/ephemeris data?

J :)
[Galaxy S II Android Development] robby2107:
Hello together,

the gps-fix on my S2 takes less than 10 seconds . I have installed the XMS2 Modem, the modified sirfgps.conf and switched the gps-server from "NorthAmerica" to "de" (for Germany). So good.

But my main Problem is the gps accuracy. If i driving on a street, the gps is pointing my Position 20-50 meters left or right the street. Especially in inner cities, the GPS is thus useless, since recalculations always take place.

greetings

Robby
[Galaxy S II Android Development] suapoc:
I just had to wipe my data partition because my phone wouldn't boot up. It stuck at the lineage logo and morsed with the buzzer.... never saw this before ;D

i updated to the latest nighly(20170307) before.... but i don't think that's the issue as i already rebooted the phone after the update.

the only major thing i changed was playing around with the protected app feature.

i put settings, the file manager and the playstore into a protected folder...

has anyone else played around withe the protected apps feature... especially by setting up the playstore and settings app as protected apps?
[Galaxy S II Android Development] robby2107:
I will test the XXMS4-Modem from this site with the modified sirfgps and the lokal gps-server.

I hope the gps-accuracy will be better than now.
[Galaxy S II Android Development] laptopu:
Yes I had this problem I posted a couple of days ago. The only difference with me is I am on unofficial twrp 3.03 emulated storage, are you?
[Galaxy S II Android Development] jt12345:
Robby, as far as I am aware, the "gps-server" (that you are changing) is only used if you use an app to download "a-gps data". If you *are* downloading a-gps data, could you please try your gps *without* using a-gps (if you don't know how to do this, let me know and I will try to explain). Also, does your "Settings/Location/Mode" say "Device only"?

J :)
[Galaxy S II Android Development] suapoc:
yes... i am also on emulated storage and emu-recovery.

i guess you did not play around with the protected apps feature.

which would be a shame as this is the only notable thing i did after updating...

the only other thing that was odd before the reboot was that my mobile didn't recognize my sim card which was the reason for the restart...
[Galaxy S II Android Development] gm0:
Sure, I'll attach it. You can flash that zip via recovery.

Let me know if it makes a noticeable different for you, I wouldn't even know. For me TTFF on a cold start still takes up to 30 seconds, but subsequent ones are always in the 3-5 second range.

If you give the location service data access the android system handles A-GPS itself, you do not need an app for that.
[Galaxy S II Android Development] robby2107:
I always use the "device only" mode in the gps-setting.

greets
[Galaxy S II Android Development] laptopu:
I had none of those things, phone switched off fine then stuck on los boot with camera autofocus clicking away loads. Once it booted to the lock screen but wouldn't unlock and I had to wipe data. As there's 2 of us and we're both on emulated storage think we need help from [MENTION=2222292]rINanDO[/MENTION]
[Galaxy S II Android Development] gm0:
Will be in the next build thanks to [MENTION=2222292]rINanDO[/MENTION], see https://review.lineageos.org/#/c/164712/
[Galaxy S II Android Development] Nobby1960:
Yes, indeed - you are right. In the last flashed Samsung stock ROM (4.1.2 "Jelly Bean") there is the XXLS8 modem as a .tar.md5 file. Thanks for explaining, again something learned.

---------- Post added at 05:43 PM ---------- Previous post was at 05:30 PM ----------

Yeah, great! Thank you :) And biggest thanks to [MENTION=2222292]rINanDO[/MENTION] too!
[Galaxy S II Android Development] devslo:
Hi all, can you advise if this rom is stable enough to use as my daily driver? I don't like to update roms very often (once per year or so) or do you suggest I wait a little bit more? Currently still on CM12.1.

Thank you.
[Galaxy S II Android Development] gm0:
No complaints here, it's very stable.

Also I suggest you consider updating more often for security reasons. If you're still on CM12.1 there are a lot of easily exploited vulnerabilities in your phone. It makes sense doing monthly ROM updates in sync with Google's monthly android security patches - in particular since it only takes a minute or two to do so.
[Galaxy S II Android Development] devslo:
Thanks, but in my experience it takes quite some time to setup a new rom. I've always wiped the phone clean before installing a new rom and setting the phone up like I want it takes hours. If you're referring to making a backup of apps and then restoring them, there are still a bunch of phone settings to go through before I'm satisfied. Is there any faster way to update?
[Galaxy S II Android Development] gm0:
Yeah, use the built-in updater, click on "download" and "install" when it notifies you of an available update, done. There's a difference between flashing a different ROM or just updating the one you've already got installed. Updates can be done in place without wiping anything.

Don't get me wrong, making backups is important and should be done regularly regardless of whether you flash a new ROM or not (your phone could also die or get lost/stolen, a backup allows you to be up and running again without losing much time and data) and when moving from CM12.1 to LineageOS I do suggest you do another one of your clean installs which will take a little while, but once that's done then keeping LineageOS up to date is painless.
[Galaxy S II Android Development] Weib67:
Hi,

Did you get rid of this charging issue ?

Also, front camera image in Snapchat is very dark. Way darker than stock camera app (same lighting conditions of course). Does anyone experience this as well ?

Thanks. :)
[Galaxy S II Android Development] s2l9100:
Supporting LOS

Hello guys,

Where can I donate to the LOS team cause I don't see donation option in LOS's web page?

Thanks to keeping i9100 alive! :good:
[Galaxy S II Android Development] the.gangster:
[MENTION=8114875]s2l9100[/MENTION]

That's because they haven't set up donations yet.

Simply wait for this footer to disappear from lineageos.org:
[Galaxy S II Android Development] suapoc:
no... however i still haven't found the original charger. i tried resetting batterie stats (deleting them via recovery and also some of that ****ty electronic vodoo you find anywhere nowadays (remove the batterie for two minutes... charge until full, charge again, sacrifice two cats at midnight, charge again, ... you know the drill ) i also bought a new batterie.... so i am slowly running out of options.... next thing i might try is reverting to stock as this could very well be just some stupid rule in the kernel...
[Galaxy S II Android Development] Lokio:
Is a stable 14.1 planned? It looks like it's pretty usable as it is.
[Galaxy S II Android Development] gm0:
Let's say it this way: the last CyanogenMod release that was labelled stable was CM10.1 many years ago.

---------- Post added at 05:39 ---------- Previous post was at 05:38 ----------

In other news, official TWRP 3.1.0.0 is out:

https://twrp.me/site/update/2017/03/10/twrp-3.1.0-0-released.html

https://dl.twrp.me/i9100/

edit: tested it, it's broken, don't use it. the backup feature is entirely non-functional in 3.1.0.0, had to go back to 3.0.2.1

edit2: and while it said it had flashed 3.0.2.1 correctly now I'm booting into Lineage recovery instead. TWRP 3.1.0.0 is very very broken. You have been warned.

disregard that. flashed it again and this time it seems to be working, the new adb backup still breaks it all though.
[Galaxy S II Android Development] rogers11:
And what exactly should be broken in the backup feature? I've made a backup that does not look different. However I did not restore it yet.
[Galaxy S II Android Development] gm0:
no idea, backups just straight failed when I tried without further explanation. so it's working for you? strange.
[Galaxy S II Android Development] rogers11:
Yes, I've made backups on four different devices including S2.

Delete the .twrps file and try again.
[Galaxy S II Android Development] gm0:
Didn't delete the settings but did try again, this time flashing it via Heimdall rather than from within TWRP. Don't know if that made the difference but it works fine now. Maybe just some freak error flashing it last time, no idea.

edit: or not entirely. the new adb backup feature is still failing and breaks local backup functionality as well until recovery gets rebooted. maybe my device is strange...
[Galaxy S II Android Development] zurien:
Yup Snapchat front camera is way to dark compared to stock camera for me as well.
[Galaxy S II Android Development] Boolian:
Can anyone confirm:

Setting Battery Power Saver Profile below a threshold eg: 15% Starts correctly.

When the battery charges beyond this threshold or the battery is changed, the profile remains in Power Saver mode and does not change back to previous profile eg: Balanced

*Edit reverting profile on charge is working*

Ok so it sticks on power save if you switch off and swap the battery out.

I suspect if the phone auto-shutdown with a dead battery and you change it, the power profile will also be stuck.

It's very time consuming trying to test this, which is why I ask for any confirmation.
[Galaxy S II Android Development] ThePhoenixII:
In my case, I just mentioned that cache and data was formatted in f2fs and that was the blocking point.

My internal partition was still using vfat.
[Galaxy S II Android Development] Saftpresse99:
Hi,

i'am on rINanDO's Lineage 14.1 unofficial builds. Is it necessary to flash the experimental build first and then the rom?
[Galaxy S II Android Development] the.gangster:
[MENTION=6936653]Saftpresse99[/MENTION]

Yes, unless you wanna wipe data or mess around with the installer. Reason
[Galaxy S II Android Development] Arcix:
Which recovery would I use to set up this rom? 'cause I'm trying to do this but I go wrong.. maybe the recovery version is too old :(
[Galaxy S II Android Development] MigoMujahid:
TWRP 3 is highly recommended
[Galaxy S II Android Development] Arcix:
I tried to install that, but I couldn't succeed in it with odin.. Is there any zip flashable file for it?
[Galaxy S II Android Development] MigoMujahid:
Yes there is, [MENTION=6560258]the.gangster[/MENTION] made a flashable zip for it, are you sure you have all requirements first? Did you repartition your phone? Do you have a rom with isorec kernel?
[Galaxy S II Android Development] suapoc:
what recovery are you using right now.... stock, cwm ??

if you use a somewhat recent version of twrp or cwm you could just proceed with flashing a recent nightly... (if your system partition is already large enough- 1 GB)by doing that a recent version of twrp will be installed too...

that's at least what happened when i flashed the first LOS nightly via a cwm-recovery.
[Galaxy S II Android Development] Arcix:
I'm mounting cyanogenmod 11 with android 4.4.2... what have I to do to install that recovery?

---------- Post added at 01:44 PM ---------- Previous post was at 01:37 PM ----------

Now I'm using cmw-based recovery v6.0.4.7
[Galaxy S II Android Development] MigoMujahid:
You must have the latest LineageOS 11 to have isorec support,and also you must repartition first to be able to install this rom, follow this guide, there are other guides of course, just look around and you will find them :)
[Galaxy S II Android Development] iSonik:
Is OTG enabled in this rom?
[Galaxy S II Android Development] Arcix:
I followed this guide. All went right, but the recovery didn't change :rolleyes:

I flashed the gangster recovery as it is written in the guide but nothing changed so I can't set up the lineage :crying:
[Galaxy S II Android Development] MigoMujahid:
What do you mean didn't change, you must have done something wrong, did you flash latest LineageOS 11 with the recovery using CWM as mentioned in the guide?

You should use the LineageOs 11 in the guide, if you have another one, it might be old so won't do the job.
[Galaxy S II Android Development] Arcix:
The guide says to flash the cm11 and then the twrp 3.0.x zip, but when I reboot recovery after flashing the twrp, recovery keeps the same (cwm)
[Galaxy S II Android Development] gm0:
I think you meant to say CyanogenMod rather than LineageOS there.

But isn't that overly complicated either way? He could just download latest LineageOS nightly and then flash (in download mode) the boot.img that's in there plus twrp-3.1.0-0-i9100.img at the same time (using an appropriate pit file), then reboot into recovery and flash the full nightly that he already downloaded. At least that's how I would do it.
[Galaxy S II Android Development] MigoMujahid:
i meant the latest unofficial LineageOS 11, it was released this year after the announce of LineageOS so it was named LineageOS 11 :o, your way is good, i never tried it because it didn't come to my mind :rolleyes:

---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------

are you sure you used this cm11??
[Galaxy S II Android Development] gm0:
Oh lol ok. My remark still stands though, all you need is an IsoRec compatible kernel so you can just take the one that comes with LineageOS anyway.
[Galaxy S II Android Development] the.gangster:
come on guys. You could discuss that in the help thread itself.

But (even if I wouldn't use odin at all in such a how-to) I would totally agree on instructing to flash an IsoRec-kernel instead of a full ROM.

So there is no way of misinterpreting a ROM version. (Especially as CM11 got IsoRec-Support after it was officially discontinued back then).
[Galaxy S II Android Development] Arcix:
I found a video guide on youtube and finally I succeed. I have to thank you a lot anyway :)
[Galaxy S II Android Development] MigoMujahid:
[MENTION=8082465]Arcix[/MENTION]

glad you solved your problem :)

[MENTION=6560258]the.gangster[/MENTION]

sorry for going off-topic..

[MENTION=8075440]gm0[/MENTION]

thanks for the workaround, i havn't thought about it before, it's a lot easier :o
[Galaxy S II Android Development] darkRd:
Hi,

I was using latest unofficial rom up to this morning and decided to pass to official.

I downloaded lineage-14.1-20170307-nightly-i9100-signed.zip and flashed with wiping data, cache and Dalvik.

But the device could not pass the boot screen.

I tried many times to power off and on again, re-flashed the ROM at least three times but can not pass boot screen not matter how many minutes I wait.

Boot animation continues to run so it does not frozen.

any idea?
[Galaxy S II Android Development] rogers11:
Try it with lineage-14.1-20170226-experimental-i9100-signed.zip first
[Galaxy S II Android Development] Pier_89:
[MENTION=6560258]the.gangster[/MENTION] Maybe I'm in the wrong thread, but could you make a .zip file of the new 3.1.0-0 TWRP recovery?

Regards.
[Galaxy S II Android Development] gm0:
You are most definitely in the wrong thread but I stopped fighting the windmills.

Also show some initiative, download twrp-3.1.0-0-i9100.img, rename it to recovery.img, drag'n'drop it onto [MENTION=6560258]the.gangster[/MENTION]'s existing zip file, replacing the file inside. Done. Make sure you don't upload it though or you'll get shouted at. :D

And in case it wasn't obvious, at least TWRP can flash .img files directly.
[Galaxy S II Android Development] Boolian:
Well after lengthy testing, I can confirm that when the Power profile is triggered by a low battery percentage, it does not reset from "Power Save" when a battery is replaced.

Either via manual shutdown at low percentage and battery replace or following an auto-shutdown at 0%

I carry spare batteries and will have to remember to manually change the power profile after each battery replacement when using the powersaving feature.

The Powersave profile will reset itself to the original setting, but only if the battery is charged beyond the set limit, while it is in-situ and while while the OS remains on.

Well that explains the poor performances I experience when sticking a fully charged battery in !

[MENTION=2222292]rINanDO[/MENTION] do you think there is a viable way to fix this, or is it just the inherent way it works?