yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Pier_89:
Can we flash it without any issue like first release that's been deleted days ago?

Regards.
[Galaxy S II Android Development] Spyr0s:
not for the faint-hearted lol, but you need to flash the experimental first over the unofficial
[Galaxy S II Android Development] Pier_89:
Ok, steps are:

1. Flash Experimental over the last Unofficial Build

2. Flash Official Nightly

3. Reboot?
[Galaxy S II Android Development] Spyr0s:
flash experimental+gapps, boot, reboot, flash nightly+gapps
[Galaxy S II Android Development] Pier_89:
However, If I don't want to do these steps, can I flash only the nightly without experimental?

So I start to the beginning...

Thank you! :)
[Galaxy S II Android Development] Spyr0s:
yes if you want to clean install
[Galaxy S II Android Development] Pier_89:
I think it's the best way to try this new build experience ;)
[Galaxy S II Android Development] Spyr0s:
https://download.lineageos.org/i9100
[Galaxy S II Android Development] Pier_89:
Download very slow.... strange.
[Galaxy S II Android Development] Boolian:
Yeah, the nightly is a little bit of a PIA

Installs fine via TWRP (Wipe+System) from Rinando's 29th build. No Experimental required.

But the SU add-on failed to install with error "Updater process ended with signal: 4"

*See below for Solution*

The File manager requires elevated permissions ie root and won't function without it. Doesn't function even when given root permissions.

Gave it up used eg: Solid Explorer. Which bizarrely, prior to flashing SU add-on had access to /root - but not to Storage... Pfff !

Browser/ DownloadManager throws MTP errors downloading. Some download links fail - Which I suspect may be certification errors which are not being displayed.

Gapps picoo installs ok, but I noticed blurring/ artifacts on "Next" advance button during setup.

**

Solution for SU errors tested successful: credit to [MENTION=1540913]MiroBiala[/MENTION] at this Thread

Basically requires the 'Update-binary' from the Arm-64 SU zip package and copied into Arm version.

It's late, it's on. It has Root & Gapps it works fine.

Goodnight.
[Galaxy S II Android Development] jojobg:
Sole purpose of experimental is to have mean to perform a no data loss upgrade from 13 or unofficial 14.1 to official 14.1. The ones willing to go full wipe may skip it and install directly the official build. Again will note Experimental is time bound and will be removed after a while.
[Galaxy S II Android Development] ran000:
Success with Install over Rinando's 29th build with system+data+cache's wipe. BUT No success with SU. Please, more detail instruction.
[Galaxy S II Android Development] Boolian:
Read the link in the post. Or the whole thread It's only 3 pages... Oh never mind.

I quote from the post which was linked above, 1 click away, just one @#*# click!

"When I got update-binary (META-INF/com/google/android/update-binary) from addonsu-arm64-signed.zip and replaced in addonsu-arm-signed.zip, I was able to flash it!"

The very helpful poster even has a modified file for download - In that thread -In the link - 1 click away...If copy & paste is too much trouble. * Edit I just checked and you asked the same question in that thread - there is a download there FFS!
[Galaxy S II Android Development] ran000:
What I have done:

1) Flash signed nightly without SU

2) Download both addonsu-arm64-signed.zip and addonsu-arm-signed.zip. Unzip both and replace update-binary in addonsu-arm-signed directory and then zip the directory in new file with name addonsu-arm-signed.zip

3) Switch to recovery, adb sideload addonsu-arm-signed.zip and get error

Please, correct me where I have done wrong?
[Galaxy S II Android Development] Boolian:
Try the download supplied if your modification didn't work and flash through TWRP then... And this is important ! - Go to Settings/Developer Options/Root access and enable Root for Apps, Adb etc...

To enable Developer Options go to Settings/About Phone & tap "Build Number" 7 times...
[Galaxy S II Android Development] ran000:
Thank. I get succes with downloaded file. So I have done something wrong with preparation my own.
[Galaxy S II Android Development] Boolian:
Yaaay! For anyone else, Error in my mirrored file(tired) have removed - here it is without encryption :

add-on-su- modified

Again credit to [MENTION=1540913]MiroBiala[/MENTION] for his modification
[Galaxy S II Android Development] Spyr0s:
Dirty install with system + data + cache wipe ?
[Galaxy S II Android Development] Boolian:
Tested only clean install Over 29th Unofficial only

TWRP standard wipe (Data/cache/dalvik) + advanced + System wipe.

Boot & configure.

Recovery and flash modified SU add-on zip

(or modify yourself from Arm-64 version)

Boot & activate root access in Developer settings.

(Root/SU is retained over reboots)

Radio is i9100XXMS4

Recommend flashing modem of choice.

Known issues for basic functions (my experience) : Browser/DownloadManager/FileManager/MTP and associated access to directories buggy.

Recommend 3rd party (Chromium) Browser & File manager install.
[Galaxy S II Android Development] Spyr0s:
Dirty install means, install new build over previous build without wipes. The procedure you performed is a clean install and not a dirty one. SD card doesn't matter.
[Galaxy S II Android Development] Boolian:
Yeah, sorry (tired) you're correct. Have edited that post - apologies.
[Galaxy S II Android Development] Boolian:
As amends for being a dumbass I just tried dirty install.

Flash SU Remover add-on zip.

Throws "...signal error 4" as per original SU-add-on. However, on Reboot it has removed SU.

That 'Remover" zip file will probably need similar mod as the SU-add-on to avoid error message.

Recovery - Wipe+System "Clean install" of 29th Unofficial build. Configure & tested Ok

Boot recovery.

Attempt "Dirty Install" of LOS - no wipe at all Throws error "...Cannot install over incompatible Data"

TWRP standard Wipe "Data/cache/Dalvik"

No system wipe

LOS install successfully.

Booted/configured.

Reboot to recovery and installed modded SU-add-on.

Reboot - Successful install with SU.

Hope that helps, I'm off for some sleep before I say anything else dumb and stop hogging the thread.

Peace out.
[Galaxy S II Android Development] Nobby1960:
I don't know otherwise. Was already so with previous Android versions in Google setup (OpenGApps).
[Galaxy S II Android Development] althafvly:
official lineage os builds started

https://download.lineageos.org/i9100
[Galaxy S II Android Development] Nobby1960:
This is a nightly build from yesterday, no official release. But the page looks good, a special menu for our S2 :)
[Galaxy S II Android Development] laptopu:
I'm considering emu storage if I have to wipe data, has anyone tried this and any issues on this version please?
[Galaxy S II Android Development] jojobg:
Sorry to bother, but did you read the thread at all or just went nuts on install spree. For dirty flash you need to go via experimental first ... It's explained on the official LOS page ... Geez man stop whatever you are taking ;)

---------- Post added at 05:42 PM ---------- Previous post was at 05:31 PM ----------

For the sake of sparing other enthusiasts from loosing their mind, sleep and time, that

really really need

to perform

dirty

upgrade to Official LOS 14.1 from older CM13.1 or Unofficial LOS14.1 Please read the thread but for your ease of use:

https://xdaforums.com/showpost.php?p=70766164&postcount=1173

Links available in the corresponding posts in the thread, I've got your attention now read or at least use thread search, it's right there on the right just go top page ;) Wow we have it already on the nav bar to the right just after top posts section ;)

Thank you for your attention and have nice reading, we are nice guys once you get to know us ;)
[Galaxy S II Android Development] Boolian:
Yeah, man I was fully aware of the experimental requirement for "Dirty"

Just did that extra install for the hell of it, to show what happens if you try without it.

I already had an install and the original posts were to draw attention to the SU-add-on issue. Insomnia is hell
[Galaxy S II Android Development] rINanDO:
I just tested a clean flash with this first nightly. I boots and is working properly!
[Galaxy S II Android Development] marzametal:
I can confirm that the first nightly boots and works... just gotta' figure out now how to enable root access for apps... root access in developer options only shows disabled and adb...

Ooooerrrr.... SU-addon!

EDIT: Back to December release I go...

EDIT: Thought I'd try again with the first nightly...

Clean install, full wipe via TWRP

Installed Nightly

Reboot and did standard config as per first boot

Reboot and flashed modified su-addon

Reboot and enabled Developer Options, then provided Root Access to Apps

Reboot and accessed File Manager, swapped from Safe Mode to Root Mode - got Privacy Guard confirmation!

Wierd, got root access, but not sdcard access... Ugh!

File Manager is buggy, so was Simple Explorer and File Manager Pro... but only wanted it to copy the swipe file over to system/lib...

Very happy AFWall+ works.

Ahhh, it's still on January 5th Security Update... that tears it, lol...

EDIT: Might just ask next time before I go through all this mess, if the Security Updates have been installed... hindsight eh...
[Galaxy S II Android Development] reusever:
Thanks!

I am using now and preformance, batery life are good.:good:
[Galaxy S II Android Development] John D J:
Hi ye I too have new official build works beautifully except that the file manager only opens my external SD card and not my internal one. Any reason for this please?
[Galaxy S II Android Development] reusever:
I don't have this problem.Try older build.
[Galaxy S II Android Development] John D J:
Did the same thing on the older version I've been running on the unofficial for some time now doing a clean wipe for each install. When I try to get in it says "requires elevated root access" I switch it on but still says the same thing.:confused::confused:
[Galaxy S II Android Development] dwarf_hero:
[MENTION=5712124]John D J[/MENTION]

I've installed official 20170206 signed build with clean install and I have similar objects with file manager. It can't open phone memory - there is info about lack of permissions and suggestion to add root permissions. Unfortunately in this build there is only adb root - no app mode.

I had similar problem with build in file manager in unofficial build 20170126 - problem was solved in 20170129 build.

There is still problem with "do not disturb mode" and silencing ring tone because phone revert by its own to default sound level.

Please add in privacy mode option to block calls especially from unknown/restricted numbers.
[Galaxy S II Android Development] reusever:
Maybe is error in file manager.Download other file manager from google play.Try ES File Manager.
[Galaxy S II Android Development] John D J:
Sorry to say this but I already have, however, i shouldn't have to. Is there a solution please? Other than your above suggestion.
[Galaxy S II Android Development] mrfrantastic:
Going from latest unofficial build to official build via experimental worked for me (dirty flash):

1. Flash experimental build (link in this thread) + fix (link in this thread) + Gapps

2. Reboot

3. Flash official build + Gapps + SU add-on

(4. Wipe cache +Art/dalvik)

Root and file manager works without problems.
[Galaxy S II Android Development] dwarf_hero:
Thx for nice tutorial but I will wait for fixed official build or revert to 20170129.

Nie I'm testing battery :)
[Galaxy S II Android Development] MigoMujahid:
File manager is buggy since the beginning, so you should use another file manager, it won't cost you anything, use "ES File Explorer" or "MiXplorer file manager"

Ps: MiXplorer isn't available in playstore, you will find it in apps section in "XDA Labs app"
[Galaxy S II Android Development] John D J:
OK mate thank you.:good:
[Galaxy S II Android Development] dii86700:
In official build I have problem with auto rotate not work aftet one day. How to fix that? Thanks anyway. Please help
[Galaxy S II Android Development] steiner.seevetal:
I fix it to wipe the cache only!.

Gesendet von meinem Pixel C mit Tapatalk
[Galaxy S II Android Development] Nobby1960:
Root issues with the latest build (only ADB, no apps). I am back to build 01/29.
[Galaxy S II Android Development] abdulhkeem:
Me too?
[Galaxy S II Android Development] rogers11:
Me not
[Galaxy S II Android Development] dii86700:
Root work perfectly adb and apps but file menager not acess internal sd card and fb messenger not notification work when receive messages. Problem with install adins su script
[Galaxy S II Android Development] toy_story:
addonsu-arm-signed.zip can't flash via recovery.

Root Addon Packages for Lineage OS!

Fixed the error 4, when installing addonsu-arm-signed.zip !

addonsu-arm-signed.zip can't flash via recovery. Gives an error : Updater process ended with signal: 4

Set in TWRP: addonsu-arm-signed.zip !

_______________________

Help must be mutual ...

[i9100] Useful fixes for LineageOS 14.1 [7.1.2]

_______________________
[Galaxy S II Android Development] Nobby1960:
Hm - dumb question: Is "build-in SU" removed in the latest build and you need this special addon to root the phone correctly? Super SU from Play Store does not work, this was my first test.

In build 01/29 root and the file manager works perfectly here on the internal/external SD.
[Galaxy S II Android Development] Kurt Krummbein:
Just read the message above yours...
[Galaxy S II Android Development] shkedov:
root addon fix

Worked for me (modded the zip myself as you instructed).:good:

Thanks man!

Still file manager is freaking out.

---------- Post added at 08:22 PM ---------- Previous post was at 07:59 PM ----------

I found a way to BYPASS the file manager problem!

After gaining root access thanks to [MENTION=8052153]toy_story[/MENTION] 's help (see above):

1. I went into file manager app.

2. Went to settings (the three lines at the upper-left corner), and then tap that wheel.

3. Go to "General settings".

4. At the advanced section you'll see "Access mode". Tap it.

5. Choose "Root Access mode". (This won't solve the main issue).

*Now comes the trick; The file manager has problems in accessing the file system through the address "/storage/nameOfYourStorage", so instead you navigate to the actual location and bookmark it!

6. Navigate to /mnt/media_rw

7. You'll see there your storages. Enter into each one of them and bookmark them.

8. That's it! Now you can simply access the location from the menu.

Cheers guys!

p.s. I know it's too detailed, but just in case I'm saving a few noobing questions.
[Galaxy S II Android Development] the.gangster:
Congratulation!

LOL

I had only mentioned that as a solution already like three times since October. Simply search for "bookmark"

[irony]Strange, that (well-known) issues that existed already in early builds can still be solved the same way as before. [/irony]

But anyways, as community flashing CM14-builds grows fast, no one can expect them to read all the thread. And for the rest who took part since day one many things seem to fall into oblivion.

;)
[Galaxy S II Android Development] Spyr0s:
lineage-14.1-20170208-experimental-i9100-signed.zip

lineage-14.1-20170208-nightly-i9100-signed.zip

http://www.lineageoslog.com/14.1/i9100

https://download.lineageos.org/i9100
[Galaxy S II Android Development] Teekanne3000:
Where is the different between experimental and nightly?

Greetings
[Galaxy S II Android Development] Spyr0s:
http://lineageos.org/Update-and-Build-Prep/
[Galaxy S II Android Development] Nobby1960:
Very easy to explain: the experimental build bricks your phone, the nightly is running very stable ;) :p
[Galaxy S II Android Development] Pier_89:
Is there another released nightly? From LineageOS download page I can see lineage-14.1-20170208-nightly-i9100-signed.zip.

Does anyone flash this build?

Regards.
[Galaxy S II Android Development] Spyr0s:
flashing now
[Galaxy S II Android Development] marzametal:
Does 0208 release have February Security updates?
[Galaxy S II Android Development] waldi801:
I can flash the experimental Rom but the Zip verification failed on the nightly lineage-14.1-20170208-nightly-i9100-signed.zip same as with the lineage-14.1-20170206-nightly-i9100-signed.zip. But if i check the hash he is ok. So anyone can give me a hint whats the problem.

THX
[Galaxy S II Android Development] Spyr0s:
nop
[Galaxy S II Android Development] OllieW:
Official Lineage Experimental ROM is a migration build which has to be flashed first and booted up once if an unofficial Lineage or (un)official CM build is installed. Otherwise official Lineage Nightly ROM cannot be installed without wiping the complete "/data" partition. Both 20170206 and 20170208 nightly build can be flashed!
[Galaxy S II Android Development] waldi801:
I have flashed the experimental build without any problems, but if i try to flash the nightly the zip verification fails. I already startet into the experimental and then try to flash the nightly again, but it still fails.
[Galaxy S II Android Development] king555:
You have tap seven times to Build Number ... :)
[Galaxy S II Android Development] John D J:
Can I flash this over the last nightly official build via ota without bricking?
[Galaxy S II Android Development] toy_story:
No, flash through TWRP!
[Galaxy S II Android Development] John D J:
OK thank you. So does that involve a full clean wipe?
[Galaxy S II Android Development] pronti:
CyanDelta updater

Does CyanDelta update work with lineage nighties? :confused:
[Galaxy S II Android Development] Boolian:
Haha yeah! Probably thinking of my vape mod at the time which is 5 presses.. Haven't counted in years.:good:
[Galaxy S II Android Development] Pier_89:
sdcard0 issue from File Manager still remains to me with lineage-14.1-20170208-nightly-i9100-signed.zip.

Who flashed it have the same issue?
[Galaxy S II Android Development] toy_story:
Yes!

---------- Post added at 10:00 AM ---------- Previous post was at 09:45 AM ----------

Here is the solution

---------- Post added at 10:05 AM ---------- Previous post was at 10:00 AM ----------

Read this post
[Galaxy S II Android Development] shkedov:
Hey, you're right. We should always search before dumping the thread with already-been-answered-questions!

I actually looked up through most of this thread and solved quite a few issues of my own thanks to that. For some reason I didn't see a thing regarding a solution for the file manager.

BTW (as I mentioned) the method of bookmarking isn't an actual solution, it's a bypass. It's like those issues we had with the kernel and linux enforcing at cm13 (@Lysergic Acid the amazing developer was leading this project), and the temporary solution was a kernel with a disabled setting to linux enforcing, until he (LA) solved it.

Same does to here.
[Galaxy S II Android Development] Pier_89:
I used to flash new nightly from TWRP recovery...anyone is flashing it by Lineageos Updater?

Any issue updating via OTA?
[Galaxy S II Android Development] shkedov:
No issues to me. It's technically the same! When you perform an update via OTA it just boots into recovery and gives it the same command to install and reboot to system as you would do manually. If you have some personal prefferings (such as updating gapps, su, some wipings and so on) you should do it manually.

Although it is recommended (but not necessary) to wipe cache partition each time you update, if I remember correctly, the OTA updating is not performing cache wiping. Just installs and reboots.
[Galaxy S II Android Development] Pier_89:
I know that it does a wipe cache/dalvik after flashing via OTA at first boot automatically.

After an update, does it delete the downloaded build? Or should I do it manually?
[Galaxy S II Android Development] Boolian:
Just testing OTA with latest nightly.

Noticed that through OTA installer it throws error "Unable to boot to recovery"

I'm assuming this is an issue with TWRP recovery and that with stock LOS recovery OTA install would be successful.

Anyone confirm?
[Galaxy S II Android Development] Pier_89:
For this reason I've just made the question... I know about an issue updating via OTA.

Maybe I'm wrong, at the moment I'm flashing via TWRP recovery and it does a good job :)

PS: I always do a wipe cache/dalvik after flashing.
[Galaxy S II Android Development] Boolian:
Just checking OTA again to flash manually via TWRP. Notice OTA download location is /Data/Data/org.lineageos.updater/ app_updates

However TWRP unable to navigate/browse there or other root directory locations via Zip install (data not mounted)

Which is probably related to the OTA "Unable to boot to recovery" ?

So moved OTA download to internal storage to Flash via TWRP

In answer to another query, OTA does not clean cache during install (to my knowledge.. which is slim! ) as it's an 'Unconditional patch'
[Galaxy S II Android Development] Pier_89:
How have you moved OTA download to internal storage to Flash via TWRP?

Thank you in advance.
[Galaxy S II Android Development] Kurt Krummbein:
... via download ;) ... that's the physical location where the updater is storing the update.zip.

You just have to remember to mount data in TWRP, otherwise you won't find it.

GTZ

Kurt
[Galaxy S II Android Development] Boolian:
Can't unless data mounted

Unable to browse/navigate root directories via TWRP - have to Reboot and use a File manager or mount data in TWRP and use 'Advanced/File manager'
[Galaxy S II Android Development] shkedov:
No, it's not deleting it for cases of unsuccesful update or reversing option; and you better keep the most recent update that worked for you aside to the current update, since sometimes one nightly might be very buggy and you'll need to reverse (which can also be done from the OTA).

The rest that you don't need should be erased, they're eating some 330 MB of your storage each...

The files are located at the folder /data/data/org.lineageos.updater/app_updates

(As opposed to cyanogenmod, where it was at sdcard0/cmupdater
[Galaxy S II Android Development] John D J:
BTW I absolutely hate substratum. Causes my ROM to crash too much so I have to reset.
[Galaxy S II Android Development] shkedov:
Sorry, I didn't notice you answered already!:good:
[Galaxy S II Android Development] kolAflash:
Migration CM -> LOS fails with "System UI has stopped"

Used recovery:

https://dl.twrp.me/i9100/twrp-3.0.2-1-i9100.img.html

What I did:

Wiped data via TWRP.

Installed cm-13.0-20161218-NIGHTLY-i9100.zip from: https://archive.org/download/cmarchive_nighlies/cm-13.0-20161218-NIGHTLY-i9100.zip

Booted into the system and went trough the setup wizard.

Rebooted into TWRP and installed lineage-14.1-20170208-experimental-i9100-signed.zip from: https://mirrorbits.lineageos.org/fu...e-14.1-20170208-experimental-i9100-signed.zip

Booted into system and got the message "System UI has stopped" -> "Close app" / "Mute until device restarts". There is nothing else on the screen.

If I click "Close app" the message reappears after a few seconds.

If I click "Mute until device restarts" the screen just stays black until I enforce a restart via longpressing the power-button.

Flashing "I9100 LineageOs Fix.zip" directly after lineage-14.1-20170208-experimental-i9100-signed.zip doesn't help.

"I9100 LineageOs Fix.zip" downloaded from: https://mega.nz/#!QMo0ATyB!3qrr47Jby08N1nnVh0K1g9uU8ywBpTsPX1JbEhqPDEQ

Don't wonder why I'm not installing LOS directly. This was intended as test, before I start migrating another phone from CM to LOS.
[Galaxy S II Android Development] toy_story:
Quick update if the error via OTA

I know about an issue updating via OTA.

As I updated!

Opened in TWRP 3.0.2-1 :

- Install/ addonsu-arm-signed.zip / Wipe cache/dalvik

- Install/ data/ data/ org.lineageos.updater/ app_updates/ lineage-14.1-20170222-nightly-i9100-signed.zip/ Swipe to confirm Flach/ Wipe cache/dalvik

Reboot System.

Excellent solution, checked !
[Galaxy S II Android Development] shkedov:
Reporting - still calendar is crashing, file explorer cannot access normally via /storage/sdcard0 & 1

OTA is giving a "cannot reboot into recovery" message so updating is still manually

Cat plate easter egg is working great!