yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] jdrch:
That's probably because you flashed a custom recovery before unlocking your bootloader. If you're new to this, don't worry, it's very complex but we'll help you get the hang of it by pointing you in the right direction. For S5 variants with locked bootloaders, the steps are:

On stock ROM:

- Root phone

- Unlock bootloader

In ODIN:

- Flash TWRP

In TWRP:

- Flash custom ROM of your choosing

Basically you need to flash a stock, known-to-be-rootable full firmware to your device in Odin. Then boot into that stock ROM and follow the steps above.

Which S5 variant are you using?
[Galaxy S 5 Original Android Development] Mane123:
No it's not the problem that I flashed a Custom Recovery. My Phone got errors such like "System UIDs inconsistent". After a while my Phone didn't boot anymore (only Galaxy S5 Bootscreen appeard, then reboot, bootscreen, reboot,...). So I tried to flash a Custom Recovery but this doesn't work as it seems due to the locked bootloader. After that I tried to flash Original ROM (got it from updato.com) but my device doesn't boot. Does that mean that's impossible to unlock my bootloader or is there a different way? Is there a way to flash LineageOS without a Custom Recovery (for example via ODIN)?

I have a SM-G900F
[Galaxy S 5 Original Android Development] fitittome:
Sometimes its just easier to goto the Samsung site and use their Smart Switch process.... Then start again. It's super slow but got me out of a hole more than once.
[Galaxy S 5 Original Android Development] jdrch:
This seems like a hardware problem or stock ROM issue to me. It's not a TWRP issue, and so is outside the scope of this thread. Post your issue in the S5 help forum instead.
[Galaxy S 5 Original Android Development] jcadduono:
the lack of 3.1.1 build was just a jenkins setup fail unrelated to incompatibility or device, just an issue that happened during release

3.1.1 should be up sometime soon lol
[Galaxy S 5 Original Android Development] afaneh92:
libinit_msm >> libinit_msm8974 and moved to msm8974-common

I can submit a patch to twrp gerrit if you dont have time.
[Galaxy S 5 Original Android Development] jcadduono:
o i missed it, ok fixed https://gerrit.twrp.me/#/c/2676/

waiting on ethan or mr bigbiffington to verify/submit and rebuild, i think all the s5 qc variants work with intl dtb anyway so could probably get away with unifying it all...unless anyone says otherwise, then i will copy those commits to other klte variants and build those 2
[Galaxy S 5 Original Android Development] afaneh92:
I have done a minimal common device tree and added common init to it and updated variants init.

Will upload them to github now.

Edit:

link to multirom-klte device tree
[Galaxy S 5 Original Android Development] fitittome:
I noticed some test builds up there this morning. Do you want them tested? test2 boots and seems to work OK.
[Galaxy S 5 Original Android Development] jaholm:
Are the test builds able to restore the modem partition also?

As far as I know 3.0.2.1 was the last version which didn't complains about "modem partition is readonly mounted" while restoring.

( Currently I try a couple of modems because of my bettery drain to check if this is modem related)
[Galaxy S 5 Original Android Development] bilbonotry:
Was TWRP able to backup/restore modem before ? I always read it could not.
[Galaxy S 5 Original Android Development] jaholm:
It could with 3.0.2.1. Read this or see this.
[Galaxy S 5 Original Android Development] Ibuprophen:
I'm just awaiting for the release of TWRP 3.1.1-0 for the SM-G900V device. It's still at 3.1.0-1...

I can't believe that the other 4 KLTE devices had already received 3.1.1-0 since 17-May-2017.

I'm not complaining... I'm just a little perplexed...

Though I'm sure that it's for a good reason... I'll just keep waiting.

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] jcadduono:
It's up

I just didn't know that it was still using msm8974 init that was discontinued in the branch it was being built in, and no one emailed me about it
[Galaxy S 5 Original Android Development] culiacanazo:
Honestly, i don't see the difference (but basically, I'm also asking what the difference would be...)
[Galaxy S 5 Original Android Development] Slayerrider:
I have a question:

I tried to install twrp on a Samsung S5 klte SM-G900F through Odin. But it always says that the flashing succeded. But if I try to boot into recovery I will come to stock recovery. (And yes I know that I have to disable auto-reboot, and I did it).

Someone has an idea to help me? This would be really nice. Thanks
[Galaxy S 5 Original Android Development] culiacanazo:
U rooted?
[Galaxy S 5 Original Android Development] MysteryIII:
That doesn't matter, as Custom Recovery is the first step to root. Or in other words you need Custom Recovery to root, so it must work on unrooted phone.

Did you flash as BL or as AP? It should be as AP. Did you try to boot into recovery instantly before booting ROM?
[Galaxy S 5 Original Android Development] fitittome:
Do not give up. It can be a pain.

Power off your phone completely. Pull the battery.

Then fit the battery and boot directly into download mode using Volume down, Home, Power.

Untick Auto-Reboot, Flash in the AP/PDA slot of Odin.

Wait for Green Pass. Pull the battery.

If it doesn't work try again.

If it still doesn't work find a new USB cable and repeat.
[Galaxy S 5 Original Android Development] culiacanazo:
No, it isn't. No you don't.

But since you're so close-minded, I'm done with you.

Your advice is good. But the cable in this case wouldn't have anything to do since Odin is recognizing it to begin with.
[Galaxy S 5 Original Android Development] fitittome:
Keep an open mind. I can send you a cable that does just that yet fails to flash. ;)
[Galaxy S 5 Original Android Development] culiacanazo:
Wow, that'd be a first for me... Ok, guess you do learn something new everyday :P
[Galaxy S 5 Original Android Development] dmcleod:
Sorry but too much information :)

For KLTE, official 3.1.1-0 is broken or not ?

Thanks
[Galaxy S 5 Original Android Development] Ibuprophen:
It works fine on my G900V.

I, personally, haven't experienced any issues but, this is just experience.

I can't speak for everyone. :)

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] j1gga84:
It is working flawlessly now on klte.

I am running it without any issues.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] Slayerrider:
No, do you think this would help?

Yes, I flashed it als AP and unchecked auto-reboot. And yes, I also didn't reboot the system, I tried to boot instantly into the recovery mode.

I tried it a lot of times, this time also with three different cables.

Now I tried also an older TWRP-version, I also tried JODIN and Heimdall and nothing works. I'm a little frustated. I flashed 2 S5s in the last year without any problems and no this...

Someone knows a possible solution? This would be really nice. Thanks for all your reply and answers.
[Galaxy S 5 Original Android Development] fitittome:
OK. Back to basics. What S5 do you have exactly?
[Galaxy S 5 Original Android Development] Slayerrider:
Thanks a lot. You are my hero. I thought it is a sm-g900f (and thought I checked it) but I was wrong. Maybe it was late.

Now everything works fine on the first try! Thanks to everyone!
[Galaxy S 5 Original Android Development] culiacanazo:
Root a different way and flash with flashfire...
[Galaxy S 5 Original Android Development] jcadduono:
Some newer Samsung devices have made it a bit tricker, it's unlikely you have a klte with a newer Samsung BL but if there's some weird way you've managed to make it happen, be sure to enable dev options and check OEM Unlock, then flash twrp-3.1.1-0-klte.tar in Odin (3.12.3's been my go-to, found here) with Auto-Reboot off, use [Vol-Down] + [Home] + [Power] to get into Odin from a cold boot (pull battery then key combo), and use the same combo after flashing, but swap [Vol-Down] to [Vol-Up] immediately after you see the screen blank/vibrate for reboot. Oh and let me know if you manage to catch the Mew.

edit: Oh am I ever late to the discussion
[Galaxy S 5 Original Android Development] Ibuprophen:
You should look/search/post on the following thread since the topic is what you require assistance with and may resolve your situation.

http://xdaforums.com/showthread.php?t=3561529

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] Slayerrider:
Thanks all together. I solved it and TWRP is running fine. The problem was not in but instead in front of the phone. I thought I had a different version of the S5.
[Galaxy S 5 Original Android Development] MarkAndroid.UK:
How come no one latched onto this and kept on answering? Weird.
[Galaxy S 5 Original Android Development] culiacanazo:
Would you try rephrasing that? Or someone who can word it differently for me? I was left in the dark. :(
[Galaxy S 5 Original Android Development] ZioGTS:
All your bases are belong to us.
[Galaxy S 5 Original Android Development] jdrch:
Is anyone else having an issue with the Oct 11 klte LOS build AND the Oct 4 restored backup both failing to boot? Trying to figure out if this is a LOS or TWRP issue.
[Galaxy S 5 Original Android Development] walttheboss:
Can anyone confirm if this recovery will flash on a 9008v. That is the China Mobile S5.
[Galaxy S 5 Original Android Development] MarkAndroid.UK:
Sorry for that.

It was the fact that no one picked up that it was the wrong S5 version in the first place? Having read through it at the time I found that a little strange. Thats what I meant.

I wasn't and am not having a dig at anyone - sometimes we go head long into a problem before realising the problem was more fundamental.

I have never ever done that :angel::rolleyes:

Am just glad it was sorted.

---------- Post added at 01:07 ---------- Previous post was at 01:03 ----------

Would you try rephrasing that? Or someone who can word it differently for me?

:confused::D
[Galaxy S 5 Original Android Development] ZioGTS:
Just kidding: take a look HERE. :D
[Galaxy S 5 Original Android Development] Ibuprophen:
I just wanted to bring this to your attention, [MENTION=5672995]jcadduono[/MENTION], in case it wasn't known..

The Official TWRP-Manager App (from PlayStore) still reflects the latest TWRP version as 3.1.0-1.

If this is a known issue, then I apologize for bringing this up again.

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] Ibuprophen:
I had noticed that the thread title didn't get updated yet but, I just wanted to let everyone know that TWRP 3.2.0-0 was just released for the klte a few days ago.

Enjoy! :)

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] It_ler:
JUST IN ADDITION ... you can download latest TWRP versions for the S5 (klte) here:

https://dl.twrp.me/klte/

v3.2.0.0 is working fine on my SM-G900F :good:
[Galaxy S 5 Original Android Development] Ibuprophen:
Thank you very much for providing this helpful information but, I just wanted to clarify (for the technically challenged LOL!)...

That link is only for 7 of the 18 KLTE (Qualcomm) devices.

Members should go to the following link to select the appropriate download link to match their device.

https://twrp.me/samsung/samsunggalaxys5qualcomm.html

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] ZioGTS:
Is Aroma working again in 3.2.0.0?
[Galaxy S 5 Original Android Development] koobie777:
No and my backups that i created with this version aren't restoring either on SM-G900P
[Galaxy S 5 Original Android Development] Legitsu:
AROMA is dead and gone

no rom dev should be using it period
[Galaxy S 5 Original Android Development] koobie777:
that being said, do you know of a way to customize the opengapps super package without aroma?
[Galaxy S 5 Original Android Development] Legitsu:
https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[Galaxy S 5 Original Android Development] Ibuprophen:
You may be able to obtain better guidance from the following Official thread for the OpenGApps Aroma.

[GAPPS][4.4/5.0/5.1/6.0/7.0/7.1/8.0][DAILY][AROMA] Open GApps by raulx222

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] MysteryIII:
I would call this just a workaround. Most people (like me) prefer GUI over console. Well, editing a text file is not to difficult and can't be called console, but it's far away from the intuitive way to setup your ROM/Gapps that you get by AROMA Installer.

It's a shame that it won't work together again and I don't really get why there are so many posts like "Aroma is worst", "Stupid to use it", "Developer shouldn't work with it to begin with". It looks like a lot of badmouthing about a "tool", giving you the easiest and most comfortable way to modify setup, that hasn't seen any alternatives just workarounds. Because of this many developers recommend to use an old Version of TWRP for setups. To bad we can't see the active users of which version of TWRP like a browser statistic.

And yes I would only call another GUI supported setup an alternative to Aroma.
[Galaxy S 5 Original Android Development] Legitsu:
aroma is bad because it introduces bloat and variables to a otherwise functional rom

there is no good reason it needs to exist

add-ons can be flashed separately
[Galaxy S 5 Original Android Development] ZioGTS:
Arrogant and useless reply, definitely divergent from XDA spirit.

However, thank you for sharing your very personal opinion.
[Galaxy S 5 Original Android Development] Legitsu:
Nope

amarullz abandoned the project there hasn't been a git commit in over 4 years,twrp broke compatibility with no intention of fixing a abandoned projects problems

its dead and gone
[Galaxy S 5 Original Android Development] ZioGTS:
Much more useful. Got it now. Thanks again.
[Galaxy S 5 Original Android Development] MysteryIII:
Flashing separately everything is more or less the opposite of user friendly. Based on this argument you could say everybody should use kitchen tools himself to cook a desired ROM.

Variables are what we wish for as this is the very meaning of customization and this is a core part of this forum.

About bloat: it gives you an easy way to decide if an App is useful for you or not.

Also I won't say it was introduced by Aroma, it just got more common. Now we use editable text files to do the same as we could before and not only users but also many ROM developers that wish for that, because this is the meaning of personal customization. Ok when it's in Recovery it's already fixed because you need to edit before flashing, but still from the view of the users you have variables you have and want to change.

As I said it's a shame that with all that great developers around here no one try to fix the problem. As you stated the sources are on Github, so if somebody with enough knowledge would wish to fix it, it were more than possible.

Don't get me wrong I don't say to anybody please do this and that for me for free. I just state that an easy guided Recovery Setup, without real alternatives just workarounds, gets lost like this.

And on the other hand: about how many tools/programs can you say they are still daily used even though there hadn't been any update for years, even though it's getting hard to use. Especially in this forum where you find a lot of similar tools it's most impressive that a tool giving these days so many problems is still one of the favorites.
[Galaxy S 5 Original Android Development] xxcloudconnectedxx:
I think a better way to put it is that Aroma made install more friendly to those who only want to flash and go, which brought more headache to developers, both those who provided aroma and those who didn't. With a "standard" ROM there is a predetermined config for setup, which IMO reduces the number of variables when troubleshooting. With aroma, the more options that are available, the more chances there are for bugs/failure due to the additional combinations of features. Again, all my personal opinion, but developers do enough supporting their ROMs without also having to support the installer that literally only makes it easier for the end user to accomplish a task they can already do, and should do in sequence. Learning proper flash order etc is part of the fun ;)
[Galaxy S 5 Original Android Development] MysteryIII:
Don't get me wrong I was also a big supporter of Omega ROM for Samsung. However even though I'm used to flash different things and edit some files like fonts, builds.prop, XMLs, I would always prefer the predefined installation.

Also in many cases it can be cleaner if you f.e. choose to use another MOD that a Developer would choose by default. I saw many bugs just because of leftovers of something you deleted afterwards. It's always a cleaner way if you can choose not to install something you don't want to begin with.

Without a question it gives the developers more headaches, but some choose this way without being requested because they think in a similar way as I do. All the TouchWiz modifications and ROM modifications like Resurrection ROM are only about adding variables so the user can decide/transform how the ROM works, acts and looks like. So once again I would say: variables are that what we ask for.

Another example is Xposed. It only exist so the end user can alter things to his favor.

While half of the forum is about personal modification of a ROM afterwards (I would call it step one), Aroma is about modify beforehand which can also safe some trouble (I would call it step zero).
[Galaxy S 5 Original Android Development] xxcloudconnectedxx:
I probably have a unique outlook on how online development should be or go. I agree with your response, just have a different outlook myself. Alot of things are developed so that general users can do what they want, without really knowing how they did it other than an option they checked or a module they installed. I feel that the majority of those programs etc both positively and negatively impact everyone - myself included, not having to program something myself because someone else made it is amazing, and is the benefit of the other developer creating it. But, when the developer leaves or moves on and no one knows how they did what they did or wants to learn or just doesn't want to do their work, the item or whatever they created breaks eventually. Its a double edged sword of sorts, I could also take talk on the subject at length, but I'll stop :) thank you for the awesome discussion - intelligent conversation can be hard to find online :D
[Galaxy S 5 Original Android Development] j1gga84:
new TWRP recovery is out that should fix some issues (for example restoring of backups should work again):

https://dl.twrp.me/klte/

What's new in 3.2.1-0:

* minui fixes (cryptomilk)

* Better android-8.0 compatibility in ROM trees (Dees_Troy)

* Fix missing library in android-8.0 (nkk71)

* Fix inconsistent SDCard naming (DevUt)

* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)

regards
[Galaxy S 5 Original Android Development] tomaasz:
does aroma work with 3.2.1-0 ?
[Galaxy S 5 Original Android Development] fubo73:
No. Aroma support has been removed since a while and I do not think it will be restored anymore.
[Galaxy S 5 Original Android Development] It_ler:
No, at least Aroma File Manager does not work. Just tried it, and recovery rebooted when I select the option to use Aroma File Manager and click on File Manager.
[Galaxy S 5 Original Android Development] tomaasz:
I cant understand why TWRP for other devices still supports aroma but for S5 not.

Many developers still use aroma, so aroma still lives.
[Galaxy S 5 Original Android Development] fubo73:
As reported on Github:

Are you sure that latest TWRP recoveries for other devices still support it???
[Galaxy S 5 Original Android Development] tomaasz:
I have also S8 and Aroma on lastest TWRP work excellent
[Galaxy S 5 Original Android Development] Ibuprophen:
There's still 1 other bug/issue present [MENTION=4699854]j1gga84[/MENTION], [MENTION=5672995]jcadduono[/MENTION] and [MENTION=912474]Dees_Troy[/MENTION]...

If you select, from the main screen in TWRP, "Reboot" then "Power Off", and then turn on the device normally (with just the power button), the device boots into TWRP recovery.

I've got a feeling that this was not realized yet since just powering down in TWRP, followed by a normal boot, isn't a function that is used often in that combination.

In addition, It happens for 2 klte devices that i have too.

Hopefully another member can also (Please) confirm this bug/issue?

Thank you very much! :)

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Galaxy S 5 Original Android Development] It_ler:
Same here with my SM-G900F.
[Galaxy S 5 Original Android Development] j1gga84:
I can also confirm that, allthough it is not a big thing but needs to be fixed sometime I guess ;)

regards
[Galaxy S 5 Original Android Development] huawei92:
I hope that you will reinstate aroma installer in the new trwp also with gapps 7.1 and very useful I do not see why only we do not have to have it and other 4 devices ,do a miracle but re-insert it.
[Galaxy S 5 Original Android Development] fitittome:
I think development of Aroma stopped in 2013. It's probably time to move on. Its not going to get fixed.
[Galaxy S 5 Original Android Development] darin00:
It failed when i flash recovery with odin what can it be??
[Galaxy S 5 Original Android Development] zanmat0:
Hi,

My phone has TWRP installed and I have tried getting into recovery with vol up, home and power but I just get stuck on the regular boot screen (Samsung Galaxy S5 with Set Warranty Bit: Kernel). I have tried using Odin to flash TWRP in download mode (no Pit file error) which fails. I can't get my device to show up in adb or fastboot. I can't enable USB debugging because my device won't boot.

The only mode I can get into is download mode (vol down, home and power). Is there any hope of getting into recovery or accessing my files from there?

I have read through countless threads and posts without finding a solution. I really appreciate any suggestions.

Device: SM-G900T
[Galaxy S 5 Original Android Development] Lister_Oprawca:
If you want use Aroma installer don't use newest version of TWRP on S5 G900F version, not working at this model. You need use 3.0.0.0

I check 3 last version at official page.
[Galaxy S 5 Original Android Development] SuperSandro2000:
Then you can't use the latest boot loader too
[Galaxy S 5 Original Android Development] culiacanazo:
Not like you've been waiting all this time for an answer, but change cables/ports: time and again i can attest, it does make the difference.

A small note, S5 does not use fastboot
[Galaxy S 5 Original Android Development] Brasscat82:
I'm having a problem upgrading to twrp 3.2.1-0 on my SM-G900T(3).

I'm currently on 3.1.1 but every method I've used has failed to upgrade to 3.2.

Odin says "File Analysis" and stops when I flash it.

TWRP app says it flashes, but it crashes to DL mode when restarted; same when flashing through TWRP itself or using a 3rd party flasher (like root essentials).

Can anyone help me?
[Galaxy S 5 Original Android Development] ZioGTS:
Have you tried downloading the file again and checking the md5 hash before flashing? Could be a corrupt file.