Database Users

want your GS2 as close as possible to stock with PHENOMENAL battery life? READ THIS!

This is my first post on xda, but don´t underestimate me because of that. In fact, I´ve been following all the GS2 sections and read ALL the tutorials since i got my phone a couple of months ago. Never needed to open an account here to do all the customizations on my phone; This should tell a lot about the completeness of this forum (i.e. SEARCH, there´s a 95% chance that your question is already answered in some thread).
In fact i´m baffled by the amount of people that appears to be unhappy with their phones, doing lots of changes in kernels, roms, themes, etc., looking to improve performance, battery life, fanciness or only for the sake of change. In my experience, you won´t get a "life changing" improvement in GS2 only by a software change. As official firmwares get more and more advanced, their performance delta in contrast with custom firmware gets smaller. The only two areas where the gap is still big lies on eye candy and usability. Moreover, with Ice Cream Sandwich knocking at the door, there´s no additional functionality coming from newer Gingerbread firmware versions.
The customization I have done involves kernel and rom, and prioritize stability and energy comsumption over up to date firmware (as i said in the last paragraph, ICS is not ready yet and latter gingerbread versions doesn´t bring anything new). With that, I could achieve a battery life of 3+ days with average use; For demonstration, i´ve just checked my phone and it shows 2 days and 15 hours with 60% charge. Naturally I am not a heavy user, and the phone is deep sleeping on average 80% of the time, but here on the forum is generally assumed that a drain of 1%/hour is very good mark, so i guess this combo provides excellent battery life (0,6%/hour). I can testify it´s rock solid as well - I´ve been using it for almost a month without any FCs or reboots. And this scheme doesn´t involve underclocking at all, so don´t worry about performance.
Unfortunately (at least for the "spooners") this guide won´t have any images, just links to the respective threads - I´m assuming you do want to learn and read to get your information. The main purpose of this guide is to point a safe/fast/easy way of doing all the stuff, avoiding the need to read all the tutorials and choose the best route among many roads that lead to the same place in the end. The target reader is the complete beginner, who has a desire to learn and unlock his phone in a safe way. Naturally i am not responsible if you blow up your phone or something like that while following this guide; I´ve followed this and it works on my phone, that´s all i can say. I will describe here exactly what i did, step by step, since i opened that damned box
So without further ado, this is it:
1) Getting root
1.1) Install the samsung drivers and software (KIES) on your computer ( http://www.samsung.com/ae/support/d...d_mdl_name=GT-I9100/M16&srchword=Galaxy+S+II# )
1.2) Download the zergrush exploit (http://forum.xda-developers.com/showthread.php?t=1321582). If needed (and you will), read the zergrush guide on the respective thread. Warning: There´s a chance that your phone firmware is already patched, so this exploit won´t work.
1.2.1) IF AND ONLY IF zergush doesn´t work on your phone, you will have to use Odin to flash CF-Root (http://forum.xda-developers.com/showthread.php?t=1103399). Read the thread.
2) Backup
2.0) Although you can do all the flashing with Odin, i must assume i´m a lazy person, so i bought Mobile Odin from Android Market. It simplifies A LOT the process of flashing things on the GS2, and as a bonus it doesn´t change the rom counter on the phone! (Read this : http://forum.xda-developers.com/showthread.php?t=1347899)
2.1) It´s an excellent idea to download CF-Root kernel for your kernel version and flash it (http://forum.xda-developers.com/showthread.php?t=1103399 - read the thread to know how to find your kernel version), then enter clockworkmod recovery and do a backup of your internal card (http://forum.xda-developers.com/showthread.php?t=1118693).
2.2) After getting root, install Titanium Backup (from android store) and backup everything you need on the phone. Backup the efs folder as well (http://forum.xda-developers.com/showthread.php?t=1308546).
2.3) Store all backups you made in a safe place (that means away from your phone). Pray to the Android gods with faith, and you will never have to use them.
3) Customization
3.1) Download firmware version KK2 (http://www.multiupload.com/PBBE9HBXTS). Flash it, then enter CWM and clean cache and Dalvik. After that, you will lose root, all your customizations and all installed software. PS: Here in Brazil the last firmware version is 2.3.4, so this version still brings many improvements. If you already have a newer version on your phone, keep it.
3.2) Download CF-Root kernel for KK2 (see step 2.1). Flash it on your phone to get root back.
3.3) Install Titanium Backup again and use the backup you did on step 2.2 to get all your software back, including Mobile Odin if you bought it.
3.4) Download Ninphetamine kernel version 2.1.3 (http://forum.xda-developers.com/showthread.php?t=1179814) and flash it.
3.5) Install voltage control (http://forum.xda-developers.com/showthread.php?t=829731) and use it to do the following settings:
* General - don´t change anything
* Voltages : 200 mhz / 850 mv ; 500 mhz / 850 mv ; 800 mhz / 950 mv ; 1000 mhz / 1050 mv ; 1200 mhz / 1150 mv
3.6) Download Bloat Freezer from android market and use it to freeze all stuff you don´t want. (http://forum.xda-developers.com/showthread.php?t=1069924)
And it´s done. You can continue from where i stopped, installing jkay mod for eye candy and more functionality (http://forum.xda-developers.com/showthread.php?t=1154278), trying a custom firmware like Cyanogen, changing your kernel or doing God knows what. If you read all the stuff i´ve linked, i´m sure you can go on with your own legs from now on. The phone is yours to mess with!

You root with Zergush then you root with CF root then you flash firmware and wipe CF root then CF root again
Why not flash KK2 then cwm and root .
Or even just flash CWM root and do a nandroid backup then flash KK2 .
jje

Well, i just reproduced step by step what i did to customize my phone from the moment i opened the box. I was really afraid of changing the internal ROM counter, and was afraid as well of using odin, so i opted to use zergrush and buy mobile odin, and i still think that is the easiest and most secure way for the complete noob to customize his phone.
You are part right, because the KK2 firmware will not change the rom counter, but you must use odin to flash it. Mobile odin is easier, but if the reader is okay with using odin, in fact he will pass over many steps of the guide.
And when you say "You root with Zergush then you root with CF root", that´s not true. In fact, i recommend using zergrush and ONLY if it doesnt work you should use CF-Root instead.

b_sal said:
This is my first post on xda, but don´t underestimate me because of that.
Click to expand...
Click to collapse
I'll try and give you the benefit of the doubt then.
b_sal said:
The customization I have done involves kernel and rom, and prioritize stability and energy comsumption over up to date firmware (as i said in the last paragraph, ICS is not ready yet and latter gingerbread versions doesn´t bring anything new). With that, I could achieve a battery life of 3+ days with average use
Click to expand...
Click to collapse
Damn, I shouldn't have bothered.
Your post is written in such a way that it might fool an idiot into thinking you know what you're talking about, but it's pretty clear you don't. Let's see some of the things I took issue with in your post.
There's no such thing as "average use".
You recommend an old ROM.
Your "tutorial" involves several unnecessary, repeated steps (root, then flash a rooted kernel, then flash another rooted kernel ad infinitum?)
Your customisations are nothing more than undervolting which is specific to your device and some rather vague freeze stuff you don't want statement.
You finish the post by saying you can flash a different, AOSP based ROM, after all of the spam before it, negating everything.
Overall, good job.

JJEgan said:
You root with Zergush then you root with CF root then you flash firmware and wipe CF root then CF root again
Why not flash KK2 then cwm and root .
Or even just flash CWM root and do a nandroid backup then flash KK2 .
jje
Click to expand...
Click to collapse
His kinda defying the point of his root method.

Ignoring the repetitions, the post's still very useful. I'm on a 2.3.4 ROM as well and the OP's right about the minimal delta improvements of gingerbread updates.

Okay, i think you are not getting the objectives of the post:
1) it reproduces exactly what a noob (me) did to unlock his phone.
2) I never said i know every single way of rooting the phone, and didn´t made this post to prove anything.
3) it´s not exactly meant for the senior members, or at least, the senior members should filter from the post only the info they judge is valid for them.
4) it´s very clear in the post that i´m prioritizing stability and battery life over firmware versions. So i guess you bashed before reading the part i say that.
5) i really did that in the good intention of helping newbies to find their way, reading the links i "spammed" on the guide. But I may be hurting more than helping, who knows? If so, sorry, i´ll get back to reading, i don´t really mind writing guides at all.

b_sal said:
Okay, i think you are not getting the objectives of the post:
1) it reproduces exactly what a noob (me) did to unlock his phone.
2) I never said i know every single way of rooting the phone, and didn´t made this post to prove anything.
3) it´s not exactly meant for the senior members, or at least, the senior members should filter from the post only the info they judge is valid for them.
4) it´s very clear in the post that i´m prioritizing stability and battery life over firmware versions. So i guess you bashed before reading the part i say that.
5) i really did that in the good intention of helping newbies to find their way, reading the links i "spammed" on the guide. But I may be hurting more than helping, who knows? If so, sorry, i´ll get back to reading, i don´t really mind writing guides at all.
Click to expand...
Click to collapse
my friend by all means you have put all your information nicely organized and nicely put. you do have good intentions and please carry on doing what you are doing. but you need to re-evaluate what you have written because you might get people getting confused by what you are guiding them through. and plus they are already stickies regarding guides and the threads in development that helps people on how to root phones.
Give you one example you say to people the guide on how to zergrush exploit. and then you ask them do download a cf-root for something else. can not go through the whole thread. but you are asking people to re root twice with two different methods. hence why people above are pointing out to you...anyway good luck and hope you get the feedback you are looking for from this thread

Suarez7 said:
my friend by all means you have put all your information nicely organized and nicely put. you do have good intentions and please carry on doing what you are doing. but you need to re-evaluate what you have written because you might get people getting confused by what you are guiding them through. and plus they are already stickies regarding guides and the threads in development that helps people on how to root phones.
Give you one example you say to people the guide on how to zergrush exploit. and then you ask them do download a cf-root for something else. can not go through the whole thread. but you are asking people to re root twice with two different methods. hence why people above are pointing out to you...anyway good luck and hope you get the feedback you are looking for from this thread
Click to expand...
Click to collapse
I guess that´s a good feedback on the post. I know there is a lot of guides on xda, and that´s a lot of information. Because of that, i had to read lots of tutorials, filter many of them saying mostly the same things, and assembling all the parts together in the end. So i thought of writing something that would unify all that, to make easier to the beginner and to avoid people having to read all the guides, like i had to do. I don´t feel the urge to do something perfect on my first post, but i fully acknowledge the need to edit the post and add more information about discarding some steps and adding alternative ways to get to the result. But in the end, i´m sure someone who follows it will as it is now won´t have any problems and will get the battery life i´m telling.

Download Ninphetamine kernel
your joking right, no doubt it was a good kernel at the time but it's old hat now technology advances everyday and there are far better kernels on here now that will offer much better battery life,etc,etc
I'm not knocking your post but most on here would know all of this already, noobs will just keep posting duplicate questions regardless of how many times they have already been answered previously.

oinkylicious said:
Let's see some of the things I took issue with in your post.
There's no such thing as "average use".
You recommend an old ROM.
Your "tutorial" involves several unnecessary, repeated steps (root, then flash a rooted kernel, then flash another rooted kernel ad infinitum?)
Your customisations are nothing more than undervolting which is specific to your device and some rather vague freeze stuff you don't want statement.
You finish the post by saying you can flash a different, AOSP based ROM, after all of the spam before it, negating everything.
Click to expand...
Click to collapse
I think the post can be improved, so i´m taking your suggestions as well:
1) Okay, i think that expression can be changed.
2) I haven´t found any evidence of KK5 and latter improving battery life, that´s why i recommend KK2.
3) Like i said before, I was worried about the rom counter issue, and didn´t know i was going to flash an official firmware. I guess that if you want to install a custom firmware without incrementing the counter you must do what i did. If that´s not true, please let me know and i will change that.
4) Many people are using this same voltages on the forums without issues, and i just told what settings i use. Many beginners have this curiosity about what settings "everybody" is using.
5) In the end everybody is free to do whatever they want. If they read all the links and felt confidence about doing anything else, then the guide´s job is done in the same way.

jonny68 said:
Download Ninphetamine kernel
your joking right, no doubt it was a good kernel at the time but it's old hat now technology advances everyday and there are far better kernels on here now that will offer much better battery life,etc,etc
I'm not knocking your post but most on here would know all of this already, noobs will just keep posting duplicate questions regardless of how many times they have already been answered previously.
Click to expand...
Click to collapse
You may call me an heretic or whatever, but i really don´t see the point of, say, Siyah kernel launching a new version every couple days. I´m using Ninphetamine and it does everything my phone can do. A mobile phone is not (yet) the same thing as a desktop computer, so it doesnt need kernels updated that fast. I ask in all my noobiness : What the newer kernels can do that this kernel can´t?

b_sal said:
4) Many people are using this same voltages on the forums without issues, and i just told what settings i use. Many beginners have this curiosity about what settings "everybody" is using.
5) In the end everybody is free to do whatever they want. If they read all the links and felt confidence about doing anything else, then the guide´s job is done in the same way.
Click to expand...
Click to collapse
I think you're still missing the point a bit. The name of your thread is "want your GS2 as close as possible to stock with PHENOMENAL battery life? READ THIS!"
The thread doesn't really address anything relating to battery life (such as wakelocks, misbehaving applications, screen brightness, signal strength). Voltage modifications which work for you may not work for someone else and the battery savings are negligible. You also don't mention the risks involved.
Then, since you've pulled me up on me taking issue with you saying to flash CM7, I'll repeat. Your thread title is "want your GS2 as close as possible to stock with PHENOMENAL battery life? READ THIS!" CM7 is about as far from stock as you can get. Also, telling people to flash a custom kernel (Ninphetamine) and saying it's "as close as possible to stock" is pretty absurd.

jonny68 said:
Download Ninphetamine kernel
your joking right, no doubt it was a good kernel at the time but it's old hat now technology advances everyday and there are far better kernels on here now that will offer much better battery life,etc,etc
I'm not knocking your post but most on here would know all of this already, noobs will just keep posting duplicate questions regardless of how many times they have already been answered previously.
Click to expand...
Click to collapse
One of the best kernels of all time. If it's not broken why fix it.
O/T I think we miss Harce. Post 5 was awesome most newb posts are post 5 material.
Look at VillainRom, see what base it is using, and why it's also a popular rom.
Sent from my GT-I9100 using Tapatalk

oinkylicious said:
I think you're still missing the point a bit. The name of your thread is "want your GS2 as close as possible to stock with PHENOMENAL battery life? READ THIS!"
The thread doesn't really address anything relating to battery life (such as wakelocks, misbehaving applications, screen brightness, signal strength). Voltage modifications which work for you may not work for someone else and the battery savings are negligible. You also don't mention the risks involved.
Then, since you've pulled me up on me taking issue with you saying to flash CM7, I'll repeat. Your thread title is "want your GS2 as close as possible to stock with PHENOMENAL battery life? READ THIS!" CM7 is about as far from stock as you can get. Also, telling people to flash a custom kernel (Ninphetamine) and saying it's "as close as possible to stock" is pretty absurd.
Click to expand...
Click to collapse
Since you´ve commented only about items 4 and 5, should i assume that you have nothing to say about items 1-3? I´m looking forward to read your opinion about that too.
You are damn right about item 4. For the sake of completeness i should warn about the risks of messing with voltages and the other topics you mentioned. You may not believe, but i really don´t see this thing as "my post" anymore. I guess we could improve on it and make it good , even if just for a person or two.
About item 5, i must disagree a little. Well, i say "as close as possible to stock" and not "stock". If i don´t change anything, so it´s stock, right? What you would define as "close to stock" then?
And the guide ended before the CM part - What I recommend is installing the KK2 firmware + ninphetamine + voltage settings, nothing else. I only left open the possibility of any customizations the reader wants to do, i´m not saying CM7 or jkay installation is a "must do".

b_sal said:
Since you´ve commented only about items 4 and 5, should i assume that you have nothing to say about items 1-3? I´m looking forward to read your opinion about that too.
Click to expand...
Click to collapse
b_sal said:
1) Okay, i think that expression can be changed.
2) I haven´t found any evidence of KK5 and latter improving battery life, that´s why i recommend KK2.
3) Like i said before, I was worried about the rom counter issue, and didn´t know i was going to flash an official firmware. I guess that if you want to install a custom firmware without incrementing the counter you must do what i did. If that´s not true, please let me know and i will change that.
Click to expand...
Click to collapse
I can't really respond to 1). 2) I still disagree with, there's no reason to stick to an old version, especially one which is not supported by the latest version of the JKay mod (which you later recommend). Therefore, in my opinion it makes more sense to recommend XWKL1. 3). The process to get what you wanted was zergrush followed by flashing Ninphetamine (with mobile Odin/other app to avoid counter increase). None of the other kernel flashing was necessary.
b_sal said:
About item 5, i must disagree a little. Well, i say "as close as possible to stock" and not "stock". If i don´t change anything, so it´s stock, right? What you would define as "close to stock" then?
And i the guide ended before that. I only left open the possibility of any customizations the reader wants to do, i´m not saying CM7 or jkay installation is a "must do".
Click to expand...
Click to collapse
Flashing any custom kernel, especially one which describes itself as "Now with 100% less Samsungyness" in the thread title is deviating a lot from stock. I would define "close to stock" in that regard as CF-Root.

b_sal said:
You may call me an heretic or whatever, but i really don´t see the point of, say, Siyah kernel launching a new version every couple days. I´m using Ninphetamine and it does everything my phone can do. A mobile phone is not (yet) the same thing as a desktop computer, so it doesnt need kernels updated that fast. I ask in all my noobiness : What the newer kernels can do that this kernel can´t?
Click to expand...
Click to collapse
I tend to agree with you which is why i don't bother with Siyah anymore i just stick to Speedmod which is pretty much proven as having the best battery life out of all the current kernels available.
What the newer kernels can do that this kernel can´t?
Click to expand...
Click to collapse
Well Siyah at this stage of development probably has many more features, Speedmod offers the best battery life which is good for me

New to s4 flashing few quick questions

Hi, sorry to sound like a noob, but I have read so much and am trying to keep up with what works now but didn't work when some of the old posts I read were posted, and just some general questions to clear things up. My s4 comes tomorrow and I want to be clear I have this down, seems like a much bigger pain than my S3 at least upfront.
So lets assume it comes with mf3 out of the box. I assume it will, is this still the issue? Safestrap is what I do, there still isn't an unlocked bootloader?
So assuming it is mf3 this is what I gather I need to do. I will root by doing the thing with terminal and a micro sd. This still works? It's still as easy as the guide I found says it is? Just have the files on root of micro sd and run the command in terminal?
Ok, so after I root I install the safestrap apk (turn on all sources of course first) and then install it or hit install recovery or whatever it says. Then boot and when I see the splash screen hit the recovery option.
At this point is the most confusion. There is a lot of talk in older posts about creating ram slots and not over writing stock rom. However some more recent posts I read mention over writing stock rom with a custom rom. So what do I do here. Assuming I create a few rom slots can I essential dual boot between roms? Can I have a google play edition and a TW edition just a reboot away?
After I do whatever with a rom then flash the kernal from the safestrap post.
Then reboot into said rom.
Then that's it? Going forward I can overwrite a rom slot with whatever custom rom I want?
Is there any limitations to roms or anything?
Lastely, is there any progress in unlocking the bootloader to just put a custom recovery on and have it be like other devices, or with safestrap has everyone just given up on that?
Thanks.

You need to read this from the beginning of the page.
http://forum.xda-developers.com/showthread.php?t=2428254
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
You need to read this from the beginning of the page.
http://forum.xda-developers.com/showthread.php?t=2428254
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
That doesn't really answer anything and in fact just seems to add to my issues.
"Also, at this time, only TW based ROMs will work with SS. CM, AOSP, AOKP, MIUI, etc will not work. "
is stated. However there are million other posts about people saying they are on CM or other AOSP roms.
It seems so much has changed over the past few months and sifting through all these posts and figuring what still applies now and what's old information seems impossible.
Plus I saw no post with actual discussion about overwriting stock rom. Just following along the safestrap thread all of a sudden people were saying don't do it, then all of a sudden people are doing it.

failedjedi said:
That doesn't really answer anything and in fact just seems to add to my issues.
"Also, at this time, only TW based ROMs will work with SS. CM, AOSP, AOKP, MIUI, etc will not work. "
is stated. However there are million other posts about people saying they are on CM or other AOSP roms.
It seems so much has changed over the past few months and sifting through all these posts and figuring what still applies now and what's old information seems impossible.
Plus I saw no post with actual discussion about overwriting stock rom. Just following along the safestrap thread all of a sudden people were saying don't do it, then all of a sudden people are doing it.
Click to expand...
Click to collapse
Okay let me clear this up for you. A guy that worked at best buy got the mf3 tar files from the Samsung smart that they use at best buy to fix peoples phones. So with the newer posts saying do it, is because you have the tar files to Odin back to stock in case anything happens. So older posts we weren't able to do that because we didn't have the tar files.
Now there are 4.2.2 Google edition roms that are based on tw but has the aosp feel to it you can have as one slot, than you can have a tw in another slot and flash back and fourth, which you can have up to 3 or 4 Roms slots as long as you have the storage for it you can make it. It use to be that you could only make 1,2, or 3 gig ROM slots for safestrap but I think you can partition more gigs now.
The people that are saying that they're on cm, aosp Roms are people who have the MDL firmware which there was an exploit for the boot loader, once mf3 hit Samsung and att locked that exploit up and its been so locked down people are getting rid of their s4's.
If your phone comes with mf3 first thing to do is not to set up WiFi yet and don't take an update. Root the device via the SD card method or kingo root method, than get safestrap installed and flash whatever ROM two based ROM for 4.2.2 you want. Hope that clears up some things
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[email protected] said:
Okay let me clear this up for you. A guy that worked at best buy got the mf3 tar files from the Samsung smart that they use at best buy to fix peoples phones. So with the newer posts saying do it, is because you have the tar files to Odin back to stock in case anything happens. So older posts we weren't able to do that because we didn't have the tar files.
Now there are 4.2.2 Google edition roms that are based on tw but has the aosp feel to it you can have as one slot, than you can have a tw in another slot and flash back and fourth, which you can have up to 3 or 4 Roms slots as long as you have the storage for it you can make it. It use to be that you could only make 1,2, or 3 gig ROM slots for safestrap but I think you can partition more gigs now.
The people that are saying that they're on cm, aosp Roms are people who have the MDL firmware which there was an exploit for the boot loader, once mf3 hit Samsung and att locked that exploit up and its been so locked down people are getting rid of their s4's.
If your phone comes with mf3 first thing to do is not to set up WiFi yet and don't take an update. Root the device via the SD card method or kingo root method, than get safestrap installed and flash whatever ROM two based ROM for 4.2.2 you want. Hope that clears up some things
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Ok, thanks for clearing that app. So when browsing ROMS I just have to make sure I get a TW based one, or even within touchwiz is there specific ROMS for mf3?

failedjedi said:
Ok, thanks for clearing that app. So when browsing ROMS I just have to make sure I get a TW based one, or even within touchwiz is there specific ROMS for mf3?
Click to expand...
Click to collapse
If you would have bothered to read the thread that was linked for you (that you claimed didn't help you) you would have seen a list of ROMs in the OP.

scott14719 said:
If you would have bothered to read the thread that was linked for you (that you claimed didn't help you) you would have seen a list of ROMs in the OP.
Click to expand...
Click to collapse
I see the list, does it say "these are the only working roms" - no.
It also says TW roms work, so do roms beyond those listed work. Or rather even if not confirmed "should" they work?
And lastly, the reason I made the original post in the first place, how current is that info. There is conflicting info all over the place, and so many posts like the one linked don't date updates and changes consistently.
If that was the definitive list 3 months ago, but more are widely accepted as working since then, I have no way of no way of knowing that.
There is no single post that has properly dated updated information all in one place. I appreciate there are people that have been doing this and keeping up with this stuff for a while now, but as a new s4 owner, this mf3 stuff is not only different, but all the proper info is spread out all over the place and not dated.

failedjedi said:
I see the list, does it say "these are the only working roms" - no.
It also says TW roms work, so do roms beyond those listed work. Or rather even if not confirmed "should" they work?
And lastly, the reason I made the original post in the first place, how current is that info. There is conflicting info all over the place, and so many posts like the one linked don't date updates and changes consistently.
If that was the definitive list 3 months ago, but more are widely accepted as working since then, I have no way of no way of knowing that.
There is no single post that has properly dated updated information all in one place. I appreciate there are people that have been doing this and keeping up with this stuff for a while now, but as a new s4 owner, this mf3 stuff is not only different, but all the proper info is spread out all over the place and not dated.
Click to expand...
Click to collapse
That is why you need to take time to learn and read. It sounds as if you are wanting someone else to do all of the research for you. If the information is spread out to you, than it is to others also. Search, read, and learn...that is the only way to get the information you need. I'm really not sure what else you are looking for? If you are looking for someone to tell you exactly what ROMs (out of every ROM available) will work 100% in your situation you are, that person doesn't exist. So like I asked, what is it you are looking for? Maybe if you clarify your request you can get more help, but remember, not that you will do this, but don't ask for anything that you should be able to do yourself.

scott14719 said:
That is why you need to take time to learn and read. It sounds as if you are wanting someone else to do all of the research for you. If the information is spread out to you, than it is to others also. Search, read, and learn...that is the only way to get the information you need. I'm really not sure what else you are looking for? If you are looking for someone to tell you exactly what ROMs (out of every ROM available) will work 100% in your situation you are, that person doesn't exist. So like I asked, what is it you are looking for? Maybe if you clarify your request you can get more help, but remember, not that you will do this, but don't ask for anything that you should be able to do yourself.
Click to expand...
Click to collapse
"It also says TW roms work, so do roms beyond those listed work. Or rather even if not confirmed "should" they work?"
That's what I'm looking for.
Can I in theory flash any TW ROM without risk of bricking, or am I actually limited to those confirmed. And follow up, how up to date is the confirmed list?
I can see all the information, I can do all the research, the problem is none of the information is dated, I read something about not overwriting stock rom slot, then I read something about doing it, and when nothing is dated for edits just the date of the original post shown, I don't know which piece of information is relevant and which piece to ignore.
If that list was dated and it was dated recently, I wouldn't have asked, I would have trusted it as an up to date list. But what if that list is 2 months old and there other roms now that are more relevant.

failedjedi said:
"It also says TW roms work, so do roms beyond those listed work. Or rather even if not confirmed "should" they work?"
That's what I'm looking for.
Can I in theory flash any TW ROM without risk of bricking, or am I actually limited to those confirmed. And follow up, how up to date is the confirmed list?
I can see all the information, I can do all the research, the problem is none of the information is dated, I read something about not overwriting stock rom slot, then I read something about doing it, and when nothing is dated for edits just the date of the original post shown, I don't know which piece of information is relevant and which piece to ignore.
If that list was dated and it was dated recently, I wouldn't have asked, I would have trusted it as an up to date list. But what if that list is 2 months old and there other roms now that are more relevant.
Click to expand...
Click to collapse
This is probably the best answer you are going to get (though others might be able to help you). The thread states to only use 4.22 TW ROMs. That means, that in theory, any 4.22 TW based ROM should work. However, if the ROM isn't specifically listed in that thread, it is your own risk to try it. There is always risk. No one can guarantee anything even if it somehow worked for them them. So if you try a ROM that is not in the list, you are taking a risk. There is no other way to put it. If you want to know about a specific ROM not on the list, and it meets the requirements, you will need to search the ROMs development thread to see if it is mentioned as working with SafeStrap and if it hasn't been mentioned, then ask in that specific thread. The information in the SafeStrap thread's OP is generally current but it is also important to read the entire thread to see what has changed from early on. It doesn't matter what anyone else claims to be running or doing, if it says to do or not do something in the OP, then listen to it. It you choose to do something different than what the OP states, it is your risk. Good luck.

scott14719 said:
This is probably the best answer you are going to get (though others might be able to help you). The thread states to only use 4.22 TW ROMs. That means, that in theory, any 4.22 TW based ROM should work. However, if the ROM isn't specifically listed in that thread, it is your own risk to try it. There is always risk. No one can guarantee anything even if it somehow worked for them them. So if you try a ROM that is not in the list, you are taking a risk. There is no other way to put it. If you want to know about a specific ROM not on the list, and it meets the requirements, you will need to search the ROMs development thread to see if it is mentioned as working with SafeStrap and if it hasn't been mentioned, then ask in that specific thread. The information in the SafeStrap thread's OP is generally current but it is also important to read the entire thread to see what has changed from early on. It doesn't matter what anyone else claims to be running or doing, if it says to do or not do something in the OP, then listen to it. It you choose to do something different than what the OP states, it is your risk. Good luck.
Click to expand...
Click to collapse
"it is also important to read the entire thread to see what has changed from early on"
"It doesn't matter what anyone else claims to be running or doing, if it says to do or not do something in the OP, then listen to it."
This is my issue with the snarky comments here. You have been helpful, but all over there are snarky comments all with similar statements.
Make sure you read it, but don't trust what you read, make sure you spend 4 hours reading a 100+ page forum before you ask a simple question, I have seen simple yes/no questions answered with paragraph responses bashing OP for not reading.
Now in my case the 3 main posts that people should read to do this, if they were dated I would have been fine.
Again, not anyone here specifically for the most part, but XDA in general is full of this superiority attitude.

failedjedi said:
"it is also important to read the entire thread to see what has changed from early on"
"It doesn't matter what anyone else claims to be running or doing, if it says to do or not do something in the OP, then listen to it."
This is my issue with the snarky comments here. You have been helpful, but all over there are snarky comments all with similar statements.
Make sure you read it, but don't trust what you read, make sure you spend 4 hours reading a 100+ page forum before you ask a simple question, I have seen simple yes/no questions answered with paragraph responses bashing OP for not reading.
Now in my case the 3 main posts that people should read to do this, if they were dated I would have been fine.
Again, not anyone here specifically for the most part, but XDA in general is full of this superiority attitude.
Click to expand...
Click to collapse
It's not a "superiority" attitude as you put it, it is the RULES. You are expected to read as much as you need to to learn. If that means 1 day or 100 days, it's up to you. This is a development forum and not a "tutorial site. People are very helpful if you at least try to help yourself first. I told you, there is no "easy" answer for what you ask. You HAVE to try the ROMs for yourself if you want to risk it. Expecting someone else to do it so they can run back and give you the answer after they took the risk is a "superiority" attitude. I also told you,DO WHAT THE OP STATES! Anything else is your risk. Why is that hard to understand? Anything you try that is not stated in the OP is untried, unproven, and risky. It's that simple.

scott14719 said:
It's not a "superiority" attitude as you put it, it is the RULES. You are expected to read as much as you need to to learn. If that means 1 day or 100 days, it's up to you. This is a development forum and not a "tutorial site. People are very helpful if you at least try to help yourself first. I told you, there is no "easy" answer for what you ask. You HAVE to try the ROMs for yourself if you want to risk it. Expecting someone else to do it so they can run back and give you the answer after they took the risk is a "superiority" attitude. I also told you,DO WHAT THE OP STATES! Anything else is your risk. Why is that hard to understand? Anything you try that is not stated in the OP is untried, unproven, and risky. It's that simple.
Click to expand...
Click to collapse
I asked for clarification on conflicting information.
It's not hard to understand do what OP says. It's the fact that in 2 sentences you said both to read EVERYTHING for information, then insist on only getting viable information from OP, which is it?
I tried to only follow OP but saw conflicting info so asked for clarification, then get told to read everything. Then get told don't trust what I read only follow what OP says. When there are 3 different "must read" posts, by 3 different authors and they are conflicting what the f*** is anyone supposed to do.
You are the one that makes seem like I'm asking to be guided through baby steps. I didn't. I asked if all TW roms should in theory work, a simple yes, or as you finally did say in theory they should, would have sufficed. Just a simple clarification, instead you are the one putting more work into the issue. That could have ended it right there, instead you keep posting more contradictory statements.
I read, I figured out all the steps I needed to take, some stuff was worded odd, or had conflicting info and I just wanted clarification on what was still relevant. God forbid someone have to say yes or no to a few questions to save others the time of reading hundreds of pages stuff that is out of date.

Hey Mod this is going know where.
Sent from my SGH-I337 using XDA Premium 4 mobile app

Disappointing community...

I must say I'm deeply disappointed by the lack of responsiveness on the LG forums. So far, none of my queries (none too difficult, mostly regarding specific steps or problems during flashing) have been answered. Coming from a Samsung I must say those XDA forums were beehives compared to the utter deadliness that reigns here. I understand that there can't be many roms as long as only the international version can be unlocked, but it is frustrating to have to get into a whole new ballgame as far as flashing etc. is concerned (compared to Samsung practices) without some assistance from the community.
Sorry about this, I just needed to unload my chagrin...

I don't have experience flashing this device. One reason is that Verizon detects if you're rooted and I don't want to void my warranty so soon after getting the device.
Sent from my VS986 using Tapatalk
---------- Post added at 08:26 AM ---------- Previous post was at 08:25 AM ----------
Also, no ROMs anyway... :' -(
Sent from my VS986 using Tapatalk

I've had a couple of questions and whilst they have taken a little longer than normal to be answered, I'm not overly fussed because I'm getting help for free so if it's not immediate, it doesn't really matter. LG rooting/flashing is completely new to me too so I'd rather wait than rush in without fully understanding what I was doing.
What issues do you have?

El Presidente81 said:
I've had a couple of questions and whilst they have taken a little longer than normal to be answered, I'm not overly fussed because I'm getting help for free so if it's not immediate, it doesn't really matter. LG rooting/flashing is completely new to me too so I'd rather wait than rush in without fully understanding what I was doing.
What issues do you have?
Click to expand...
Click to collapse
I know it's free and I shouldn't complain. But the difference with the Samsung community is striking. And it's precisely because all is new that one hopes for some assistance. Look at the last post of this thread. Maybe I'm spoilt having to wait for 2 days, but somehow I suspect I'll never get an answer. And maybe it's also because there are not enough knowledgable members on the LG forums, which means that one is always dependent on the OP.

bartveld said:
I know it's free and I shouldn't complain. But the difference with the Samsung community is striking. And it's precisely because all is new that one hopes for some assistance. Look at the last post of this thread. Maybe I'm spoilt having to wait for 2 days, but somehow I suspect I'll never get an answer. And maybe it's also because there are not enough knowledgable members on the LG forums, which means that one is always dependent on the OP.
Click to expand...
Click to collapse
You must understand that it's not we people don't want to reply to you, and for your question in regards to the post, I'm pretty sure a search would bring up many queries that you have been asking before. The phone has only been out for a few months, and people are slowly working on the progress for this phone. It's not that people have no knowledge, it's just that the community (let's be frank) is not as large as Samsung's community. We can try to provide as much help as possible, but sometimes help us out by doing a search before questioning stuffs.
We all that come towards this forum wanted to see something more, something exciting and play around with custom roms and stuff, but there's their pros and cons.
For example, there's already a team building towards CM/Blisspop, and they are progressing steadily, bringing us updates and fixes that will eventually be available for everyone.
So sometimes, just have the patience to wait, or if you really need to query in regards to stuff, you could do a PM.

Do not follow that guide until you are already running version F. You will lose exfat on your SD card
Sent from my LG-H810 using Tapatalk

Coming from a Nexus 4 the tumbleweed here is a bit odd but if a phone is pretty well locked down that does cramp this forums style a bit.
On the other hand the only niggle I have with the G4 is the horrible over saturated tones that make reds look purple. If I could tone that back say 20% it would be nearly perfect for me.

tdevaughn said:
Do not follow that guide until you are already running version F. You will lose exfat on your SD card
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
tdevaughn, you are referring to my question in the other thread? But how am I ever getting to version F as I am already rooted and running a flashed stock rom (version d, with necessarily Updates turned off)?
Indicious Flow said:
You must understand that it's not we people don't want to reply to you, and for your question in regards to the post, I'm pretty sure a search would bring up many queries that you have been asking before. The phone has only been out for a few months, and people are slowly working on the progress for this phone. It's not that people have no knowledge, it's just that the community (let's be frank) is not as large as Samsung's community. We can try to provide as much help as possible, but sometimes help us out by doing a search before questioning stuffs.
We all that come towards this forum wanted to see something more, something exciting and play around with custom roms and stuff, but there's their pros and cons.
Click to expand...
Click to collapse
It's just that sometimes a question is so specific that a search won't do. As is my question in the thread which you OP'ed (or was that already answered in that thread and I overlooked it?). And PM'ing... now that I would consider harrassment.
Anyway, I hear you and I certainly appreciate the efforts of people like yourself. “Trees that are slow to grow bear the best fruit.”

The only question nobody can answer in the G4 is why are we obliged to flash a kdz file to update the fw when you have an unlocked bootloader (official root). Losing internal data + root everytime we want to update the fw!!
Why isn't a way to extract the fw files from the kdz so we can flash them without data and twrp loss like they do it on htc s_off phones?
Sent from my LG-H815 using XDA Free mobile app

bartveld said:
how am I ever getting to version F as I am already rooted and running a flashed stock rom (version d, with necessarily Updates turned off)?
Click to expand...
Click to collapse
just taking a stab at it
1. flash back to a non-rooted system image (a search will probably turn something up) for your current version
2. ENABLE UPDATES! and retrieve the OTAs to, um, UPDATE? (gee.. if you disabled updates, I WONDER why updates won't work)
3a. find a rooted system image for your new version and dd flash that
or
3b. follow guide to dd pull your non-rooted system partition, inject SuperSu, and dd flash your self-made rooted system image

bartveld said:
It's just that sometimes a question is so specific that a search won't do. As is my question in the thread which you OP'ed (or was that already answered in that thread and I overlooked it?). And PM'ing... now that I would consider harrassment.
Anyway, I hear you and I certainly appreciate the efforts of people like yourself. “Trees that are slow to grow bear the best fruit.”
Click to expand...
Click to collapse
Well for me, I've never thought of PM as a spam. At least you can easily get your questions asked and answered without questioning the other members who may or may not be new to the forum and just slowly learning So if you really have anything to ask, feel free to ask. And to answer your question in regards to the other thread, the command for that is universal for H815 variants, and works on all the rooted images out there.

you know what I was thinking the exact same thing
When i first got my G4 i tried to root and cocked it up totally so posted on here and got about 3 replies, this was my first Android phone previously having the crappy fruit phone for 10 years
I am an experienced computer user and have mucked about with all kinds of stuff for years
One thing that has stuck in my mind i read a comment on a thread here that said something like 'thats why noobs shouldnt root phones' - what kind of person thinks this way? I will go out of my way to help people in this type of situation
Anyways I am now pretty mustard on the G4 and know my phone/rooting inside out after spending the last 6 or so weeks finding out the wrongs and rights of rooting with several mishaps and always finding my answers due to the few helpful peeps around here
There are some brilliant posters on here and there are also some right ****ing morons

disappointing user...
all answers already out there.. but wants hand held instead of searching/reading.
(see, goes both ways)

autoprime said:
disappointing user...
all answers already out there.. but wants hand held instead of searching/reading.
(see, goes both ways)
Click to expand...
Click to collapse
If you ever have a problem with your electrics let me know i will be more than happy to help you if i can ... without patronising you
BTW you have helped me out more than you know

Well usually if someone has an answer they'll share ot or tell you where to look. If they haven't then maybe they don't know either.. I rarely have to ask questions because I read and search and help out where/when I'm able. Half the time IF I do.ask a question I end up finding the answer shortly after on my own because of my diligence and risk taking. There aren't necessarily a lot of roms out there( which I don't care anyway), but the rest is still okay. I mean there's root and xposed and that's even for locked down variants too. Maybe it's just me cause I didn't always have it so good. I had phones that we had ridiculously hard methods of obtaining root and unlock if ever. We found a way though and now things are a hell of a lot easier. Idk I just don't see the point in a thread like this..

As a matter of fact this is the first phone I haven't rooted or Jailbreaked day one, mostly because I bought it as a cure for a flash o holic A new Nexus line is on its way, hopefully with a ok camera, it's going to be my flashy phone and this one will be the stockish backup
Skickat från min LG-H815 via Tapatalk

I'm not sure it's fair to compare a forum for this device to the various Samsung ones when Samsung is the second largest phone manufacturer in the world and by far the most popular Android OEM.

vegetaleb said:
The only question nobody can answer in the G4 is why are we obliged to flash a kdz file to update the fw when you have an unlocked bootloader (official root). Losing internal data + root everytime we want to update the fw!!
Why isn't a way to extract the fw files from the kdz so we can flash them without data and twrp loss like they do it on htc s_off phones?
Sent from my LG-H815 using XDA Free mobile app
Click to expand...
Click to collapse
You can flash as many KDZ's as you want without losing data. I have done it a few times now myself. I don't know where you got the idea that you lose your data every time..
Yes you lose root though. It's pretty simple to flash a rooted image after you get root back, though.
There are two options when flashing a KDZ with LG Flash Tool. Wipe or don't wipe. Pretty simple.
Or is it different with an unlocked bootloader?

GibMcFragger said:
You can flash as many KDZ's as you want without losing data. I have done it a few times now myself. I don't know where you got the idea that you lose your data every time..
Yes you lose root though. It's pretty simple to flash a rooted image after you get root back, though.
There are two options when flashing a KDZ with LG Flash Tool. Wipe or don't wipe. Pretty simple.
Or is it different with an unlocked bootloader?
Click to expand...
Click to collapse
I have no idea! The dude who made the tutorial on how to get back to stock using kdz told me I will loose TWRP, though no idea if I will loose bootloader unlock too, if that's the case the process of unlocking the bootloader will wipe all data

vegetaleb said:
I have no idea! The dude who made the tutorial on how to get back to stock using kdz told me I will loose TWRP, though no idea if I will loose bootloader unlock too, if that's the case the process of unlocking the bootloader will wipe all data
Click to expand...
Click to collapse
Ah ok. Yes, you will also lose TWRP. I guess it is more of a pain with an unlocked bootloader. Mine is locked, so I don't get TWRP. I just flash whatever KDZ, pull system image, inject root, flash the rooted image.

Installed a custom KERNEL but it broke my phone (or I did something wrong) .

I really need help, my Samsung Galaxy S7 Edge has just got a red screen since i installed a Kernel and i cant use my phone at all.
Any help would be greatly appreciated.
The Kernel I uses was Super Kernel and I also had the Super Man ROM
Thanks A Lot Guys

Just flash stock boot.img from TWRP recovery and you will be fine if you cant get into recovery go to download mode and flash stock firmware with odin
Sent from my SM-G935F using Tapatalk

Why did you flash a kernel? Do you know what a kernel is, and what is does? Do you know how to recover in case things go wrong? Nope, so you should probably do some reading before you decide to modify anything next time.

You probably flashed the "Flat" kernel. Download the Edge kernel and install it.
I always do a nandroid,and back up recovery and boot via Flashify.
Your phone will live.
Sent from my SM-G935F using XDA-Developers mobile app

J.Biden said:
Why did you flash a kernel? Do you know what a kernel is, and what is does? Do you know how to recover in case things go wrong? Nope, so you should probably do some reading before you decide to modify anything next time.
Click to expand...
Click to collapse
he asked for help not a lecture.

simonhcai said:
he asked for help not a lecture.
Click to expand...
Click to collapse
He still needs to do his research and tons of reading
"And on that bombshell!"
Sent from my Gorgeous Echoe driven AEL Kernel Powered G935F

simonhcai said:
he asked for help not a lecture.
Click to expand...
Click to collapse
Do you really think that people are lining up here to help people that have not read a single guide or anything? Do you think people are getting paid helping around here? I'm not giving him a lecture, but it's expected that you know what the F you're doing before doing anything. You must be new around here.

J.Biden said:
Do you really think that people are lining up here to help people that have not read a single guide or anything? Do you think people are getting paid helping around here? I'm not giving him a lecture, but it's expected that you know what the F you're doing before doing anything. You must be new around here.
Click to expand...
Click to collapse
How do you know he hasnt read a single thing?everyone's a noob at some point and if hes made a genuine mistake then maybe asking for help from people who could stop him from ruining his phone which he might have a long contract on,if you know how to help him the time you spent replying you maybe could of solved this problem for him.

simonhcai said:
How do you know he hasnt read a single thing?everyone's a noob at some point and if hes made a genuine mistake then maybe asking for help from people who could stop him from ruining his phone which he might have a long contract on,if you know how to help him the time you spent replying you maybe could of solved this problem for him.
Click to expand...
Click to collapse
He would know how to recover from this if he had done some proper reading. If he isn't even aware what a kernel is, or how to recover, he hasn't been reading, has he? The solution is not to first flash, fail, and then ask questions. Read, read and read, then flash and succeed.
TL;DR: Read.

J.Biden said:
He would know how to recover from this if he had done some proper reading. If he isn't even aware what a kernel is, or how to recover, he hasn't been reading, has he? The solution is not to first flash, fail, and then ask questions. Read, read and read, then flash and succeed.
TL;DR: Read.
Click to expand...
Click to collapse
Basically sums up XDA. Also don't like people who go on spamming "HALP" without posting a logcat (or a last_ksmg in case of kernels) or any other info that could possibly help identify the issue and expecting devs to magically help them. People really need to read this: http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Although I would like to add that sometimes it's not totally the user's fault, as many kernel threads don't really provide any information regarding the behavior of the kernel in certain conditions, or the OP of the thread does a poor job at explaining which files to grab or how to flash and whether to wipe any cache partitions (or whatever the post-flash requirements are) or the requirements of the kernel. For example, I installed jesse's kernel and it caused my phone to fail verification on bootup, even when I had dm-verity disabled. Now, people should read the thread before flashing, because there's a possibility that someone else had a certain issue that you may face upon installation, but I feel the OPs should have a section called "Common/Rare Issues" in the thread where user-verified solutions to common/rare problems found when flashing the OP's kernel/ROM are available, so you don't have to search hundreds of pages to find a fix. If you look at the threads of some popular ROMs/kernels, they have one, for the same reason. In my case, I was the first one to face it, so I had to figure out on my own why it happened and find my own fix, that took me a couple of hours. But having such a section saves you time, which is helpful regardless of whether you're capable of identifying the cause of a problem and fixing it yourself or not. I have a "Common problems" section in my app's descriptions for the same reason, because I like to think from the user's perspective as well, plus I don't want my users to be spamming my inbox asking for fixes to common problems, it's more efficient to have a FAQ.
But yeah, READ, UNDERSTAND, LEARN, instead of just expecting people to magically help you with your problems.

Hello !
1. Download Samsung-smart-switch.
2. Install it and run it.
3. Choose more on Top of program and choose the first Part of the menu (intialize software...or so)
4. Follow the instructions on screen and voila .....
YOUR PHONE IS BACK WITH ALL ON STOCK
Hope it helps you

The strange encryption misfire between TWRP & LOS-based OS's (questions/thoughts?)

The strange encryption misfire between TWRP & LOS-based OS's (questions/thoughts?)
Things we know:
TWRP and LOS-based systems with encryption either don't install correctly or boot correctly afterward. (2 different things perhaps).
Installing Magisk on non-encrypted partition gives boot loop
All LOS-based OS's must be installed on non-encrypted partitions
There is no easily found issue in the Jira issue tracker or TWRP bug tracker about this problem for the OnePlus 5.
I earlier posted this reply in the RR LOS ROM thread in response to another question about LOS-based OS's and encryption. I thought that rather than take a thread off topic, this is a better place for it. (where it can be totally ignored ). I shouldn't have attached this issue to a single ROM's thread since it affects a lot of LOS-based ROMs. There are other little offshoot pieces to this and some may deserve their own threads or questions at least.
TWRP: A number of people using TWRP (official or non) have problems restoring nandroid backups, which pretty much defeats much of the utility of TWRP if you can't do this. Does it have anything to do with Encryption? IT appears to, at least on the encrypted version when using the non-official version. There is a warning about it right in the thread title for non-official TWRP. I've had no problems restoring while encrypted using the official 3.1.1-1 version, but I'm beginning to feel kind of lucky in that regard.
LOS-based systems: These devices that are going to use LOS based systems require decryption of the data partition before installing whichever LOS-based ROM you're interested in. For some people, it's fine. They don't care so I don't see them as having a problem. I actually like encryption and want it, so this problem will keep me from using LOS-based ROMs until it's fixed. I've got a lot of years with Linux and Android experience, have helped with coding and customizing kernels, OSs and recoveries (mostly Philz) in the past, and would be glad to dig into the problem, at least for awhile to see if anything new can come to light but I'm not kidding myself or anyone that I can figure any of this out myself and I'm way out of practice.
Magisk: and non-encrypted partitions are also not happy together, but since I'm not too sure about the nature of that problem, I'll just call it a one-off for the moment.
Things to do: It'd be nice to figure out which area this "blob" of a problem is most likely to be in, and it'd be even nicer if one of the devs that I'll list below already knows where it is and could tell us. I can see some reason for suspecting TWRP and some reason for suspecting a combination of the OP5 FS in combination with the LOS-based ROM (or it's installer). It's not clear yet. I made a quick dirty list of some of the devs either involved with OP5 TWRP or OP5 LOS-based systems and will "mention" them in this thread in case they already know and/or are working on these things.
Another bit of this is that I signed onto Jira bug tracker (Lineage OS) to see if I could find even one sample issue that resembled this on an OP5. I couldn't but I can find some similar ones on other devices with dates only a month old. Part of this would be to try to get this either/both onto the Jira bug tracker or the TWRP bug tracker or both. Another part before that is really deciding whether this issue belongs in those places.
My question:
It's even be helpful to know whether the suspicion of LOS-based ROM and TWRP devs @apascual89, @DarkExistence, @Dees_Troy, @koenkk, @chenxingyu and @xdvs23 is that it is a problem due to TWRP or LOS ROMS or is it the combination of the two? It's be more useful to know what is most suspected to be the actual problem.
Thinking it over: It seems possible that encryption as it exists on the OP5 (in it's native OSs) is not yet available either as a blob or in an API (or in code of course) to LOS. If that's a decent premise, then LOS is just awaiting some nebulous release of either code or prebuilts from OP (not that that's any small thing or can even be counted on).
Personally I'm just curious to know what is thought to be the biggest factor preventing using LOS with encrypted partitions.
Many thanks in advance to anyone that can supply an answer(s). I'm going to do a git on Resurrection Remix to start looking into it. I've got TWRP already and am looking at that. My odds of finding anything are slim alone. If anyone is interested in this, it'd be useful for you to note your interest. If I can think of a unique way (or if you can) to describe this as a LOS-based bug or a TWRP one, then please feel free to either tell me or just open a bug report on Jira or TWRP.
Addition: May as well ask if there's already a link to an issue in Jira. I've scanned it but not found one: https://jira.lineageos.org/browse/BUGBASH-612?filter=-5
Click to expand...
Click to collapse
Clarifications of what I/others would like for the OP5 (TWRP/LOS/MAGISK) spoken of above & below:
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.
Click to expand...
Click to collapse
Updates regarding latest encryption fixes in a couple of LOS-based ROMS:
I got multiple reports that CRDROID (Los-based) and Unofficial RR (LOS-based) are both now patched to work with Encryption.
SO: It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.
More updates about ROMs and TWRP's:
Here's some updates:
1) ROMs: It's looking like the custom LOS based ROM world is headed for encryption in some cases within a few versions. You can look at the last couple pages of official and unofficial RR to see what's been discussed, but it sounds like a trend is forming that pretty much matches the trend of smartphones in general.
2) TWRP: Even though this discussion (it's about the most recent dozen replies that include me, katinatez and xdvs23) is , I think, in the official twrp thread, it's about some combination of a) official b) unofficial and c) katinatez (Damn, I know I spelled his name wrong , sorry).
Official : Good points: Can do working restores encrypted /// Bad: Can't work with OTG
UnOfficial : Good points : Work's with OTG // Bad :: Can't do working restores usually.
katinatez TWRP: Good points: OTG OK, Restores OK, Encryption/Decrytion OK; But: It's not an official nor has a thread for it and you have to self-mount /system before doing these things.
The idea is to combine the best points of unofficial and katinatez and it sounds like development is back on, and maybe a commit of both katinatez and xdvs23's code can be performed pretty soon.
Some progress seems possible!
Click to expand...
Click to collapse
Looks possible that TWRP (Unofficial) just took a leap forward and is doing a bunch of things right:
Things it's doing well (well via the few reports starting here: https://forum.xda-developers.com/showpost.php?p=73220260&postcount=910)
1) Backup / Restore nandroids (I just asked for some details on encryption states in that thread but I think the restore was to encrypted partition.
2) OTG working
3) TWRP Themes working.
4) I'll try it and check adb access and sideload as well and report back.
Click to expand...
Click to collapse
Thanks for carrying on the battle. So far it seems good to me, so nice work! -- I just installed, plugged in and mounted OTG device and did a full (all partitions) encrypted backup to the usb-stick, then restored it. I saw no red characters, and I may have forgot to save the log (doH!) but will look in the backup folder in a bit.
Currently I'm running noLimits with Elemental 1.06. No problems. Oh yeah, themes working fine as well. Unless something odd crops up, this could be a real recovery.
Good work to you guys for persevering.
Other things tested: Sideload mode OK; Adb shell OK. Installed xXx ROM latest version with another kernel: OK.
-- Probably this will be the last entry since a fully functional TWRP was a big thing on the wish list and it appears to be here. The thread is the "Unofficial TWRP" thread currently, but maybe it'll be renamed.

This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.

ArkAngel06 said:
This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.
Click to expand...
Click to collapse
Same with me. I can a step back and sort of see the long view where this thing gets somehow solved in a day or a month or whatever, and the moment it's solved, no one recalls it was such a pain in the butt. IT does keep me from testing LOS-based OS's because encryption won't work with them. It does keep me on my toes whenever I have to restore my phone from a nandroid backup and that stuff seems like where we should focus some energy.
The thing that bugs me as much as anything is that there's no visibility into anyone "doing anything" about this. I keep hearing people saying (devs too) "I don't know" and "Someone will fix it" and that could certainly happen, (or not). I'd feel much better about it if I could at least search up a bug tracker issue in one of the fairly obvious places (Lineage (Jira) bug tracker) or (TWRP bug tracker).
You're right. It's an insane amount of time to waste for something that should be a 10 minute restore from nandroid backup, but the problem is clearly bigger than that even.
Forgot to add this::
Please try to add any ideas you've got no matter how stupid you might think they are. I'm going to start when I return home.

This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.

ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week.
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
@ArkAngel06
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585

snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
Click to expand...
Click to collapse
It's no problem, I thought the video might be like a week old or something, but i figured you wouldn't just now be posting the fix if it was done a week ago.
I hope some people give it a try and it works for them. You'd be a hero. :highfive:

There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app

ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.

snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585
Click to expand...
Click to collapse
Thanks snowwolf;
I think I replied to some of this in my reply to @ArkAngel06 already and I appreciate it. For Magisk, it seems like we're in a race between Google and the Magisk/SuperSU developers that'll never end. They have to keep leap-frogging each other which I suspect they'll do for a long time yet. It's great to have work-a-rounds and with SuperUser utilities, maybe that's about all we can ever hope for. The emphasis has been thrown on "high security" devices by too many companies and even governments so that the security world will never again look like the beginning of the smartphone era when nearly every phone had an unlocked/able bootloader. I appreciate the reply.

dladz said:
There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.

hachamacha said:
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.
Click to expand...
Click to collapse
This is my thread, never got round to making a script but shouldn't be too hard.
Haven't tried this on the OnePlus but the principle should be the same.
https://forum.xda-developers.com/showthread.php?t=3604856
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app

Another thing to take into account now that may be getting solved with some luck is that the RR official build has had this commit applied today to attempt to fix a LOS-based build to boot encrypted. No one has any idea (I think anyway) whether it works yet, but we should know pretty soon. RR is pretty popular.
Here is the commit(s) I found ::: https://github.com/apascual89/andro...mmit/a13eef258620e0726c6dcd9e83dacc1342080ed6
I'll update the OP if it worked.

Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!

MrWilsonxD said:
Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!
Click to expand...
Click to collapse
Thanks. That was my goal I thought maybe we're getting closer on some of these issues that all sort of whirl about one another in the encryption realm. The 'commit' in RR I noted above in some other reply was at least a brief ray of light but I've heard one report that it didn't work so far. I guess we'll see if anyone gets it to work. Cheers.
Quote of someone (and myself asking questions) from the RR Official thread where the commit to try to fix encryption+LOS happened earlier:
Hecke92 said:
Tried encrypted install, but cannot get past boot screen
Thanks anyway
Click to expand...
Click to collapse
Just curious if there's any details you could share about which version TWRP,
which version and type (SuperSU or Magisk) SU and what you had installed prior to this encrypted attempt.
Also which type of encrypted (ext4, f2fs, etc) would be the target?
many thanks for any information either way.
And the reply I got back::
I have the latest tarp by xdvd (as i saw it was newer than official twrp). I am always using magic, but that is of no relevance I think (because I clean flashed RR and no SU is integrated).
Partition is ext4 and before I had OOS (XXX)

so apparently over in the RR unofficial thread there are users reporting that they flashed and booted on an encrypted device.
success.

Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350

heisenberg33 said:
Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350
Click to expand...
Click to collapse
Hey cool! That's terrific. I don't have time to scan the source and see if it's any different than the changes I listed from official RR but really this at least halfway satisifies the premise of this thread. I guess I'll keep it going until we're sure that TWRP can backup/restore nandroids no sweat regardless of encryption state and also handle OTG devices. Then I think we're onto a more solid start.
I'll fix this thread up tomorrow in the OP and when it's served a purpose will stop updating it. Shouldn't be long
Thanks to you last two guys for shouting this out for people. I asked a question at the end of official about where their github is located. I don't see it in the OP where official RR lists theirs.

Updates from recent comments in RR ROM LOS-based Unofficial & Official versions::
Since I've not yet found the exact source used in the unofficial version which is now working encrypted on the OP5, I'll have to wait to put up a link to it. @Eliminater is the author so credits to him and whoever did the working commit. If @Eliminater can give us a link to the working github where the changes that made encryption work were committed, it'd be appreciated.
Comments from https://forum.xda-developers.com/oneplus-5/development/los-resurrection-remix-n-t3632856 (unofficial RR) seem to indicate that although they managed to get encryption working OK with RR unofficial that they "may" have lost the ability (at this point) to run non encrypted. I'm not certain of this but that's how the comments/replies look. I'm sure it'll settle out soon. I'm also pretty sure that every LOS-based developer for the OP5 knows where the source is where this change occurred and that's more important than me knowing where it is. (so good job!)
Comments from Official RR: https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578 where I found and posted the commit that was supposed to fix encryption, indicate that they're not yet quite there. Comments say that encrypted official RR is not yet working and still boot-loops. Shouldn't take long for them to get these two synced up, but that's just my take. On Official RR, decrypted works.

and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174

gershee said:
and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174
Click to expand...
Click to collapse
Thanks for the report. It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.