Related
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
UPDATE
Samsung is now working to release a fix for this issue. Also glad to know Samsung is working closely supporting developers in this XDA community
More info here:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
Thank you to all members that helped contacting Samsung, and in a constructive way identifying the problem and report it in a professional way.
I hope Samsung is here to stay and work more collaboratively with this community
Cheers!
____
Hi
Just received a response from Samsung developers on the topic, and need your help providing more details.
Please note that, you must only refer to scenarios using the STOCK Samsung ROM (not custom, cooked, rooted) and standard flashing methods (OTA or Kies).
If we're not able to provide this information, the case is closed.
http://innovator.samsungmobile.com/...Id=1&selectedSequence=00dgu030000~&viewMode=2
Hi,
We have failed to reproduce the bug, please provide a sure way to reproduce it, otherwise we won't be able to help.
While reading through the xda developers forum where this issue is discussed, I noticed that everyone reporting this is using rooted or leaked software. We cannot help you if you don't provide us with all the information - which software version? What are the exact steps?
Regards,
Adam Panasiuk
Samsung Developers
Click to expand...
Click to collapse
nCoder said:
Hi
Just received a response from Samsung developers on the topic, and need your help providing more details.
Please note that, you must only refer to scenarios using the STOCK Samsung ROM (not custom, cooked, rooted) and standard flashing methods (OTA or Kies).
If we're not able to provide this information, the case is closed.
http://innovator.samsungmobile.com/...Id=1&selectedSequence=00dgu030000~&viewMode=2
Click to expand...
Click to collapse
I've seen at least one report of XXLPY killing someone's device in stock recovery.
Also, Sprint was able to reproduce this on their devices (and apparently is deploying a fix) - I'll try to find more on that later.
"please provide a sure way to reproduce this" - ARE THEY KIDDING? If you reproduce this, YOUR DEVICE IS DEAD. One can't provide a sure way to reproduce a bug that you can test ONCE successfully. As stated by others, even a Google engineer himself, the fwrev 0x19 ERASE bug is intermittent and won't always happen. There is no "sure" way to reproduce this. However, this is a bug that was confirmed by Google during Galaxy Nexus development and we have confirmed that we have the same chip/fwrev as ones that Google experienced problems with in GNex prototypes.
Entropy512 said:
I've seen at least one report of XXLPY killing someone's device in stock recovery.
Also, Sprint was able to reproduce this on their devices (and apparently is deploying a fix) - I'll try to find more on that later.
"please provide a sure way to reproduce this" - ARE THEY KIDDING? If you reproduce this, YOUR DEVICE IS DEAD. One can't provide a sure way to reproduce a bug that you can test ONCE successfully. As stated by others, even a Google engineer himself, the fwrev 0x19 ERASE bug is intermittent and won't always happen. There is no "sure" way to reproduce this. However, this is a bug that was confirmed by Google during Galaxy Nexus development and we have confirmed that we have the same chip/fwrev as ones that Google experienced problems with in GNex prototypes.
Click to expand...
Click to collapse
I understand, but not proving evidence the bug exists in a stock rom, or reference to a reliable source (Do you have a formal statement from Sprint?) Even if the scenario is "Install ROM version N7000XXXLPx using Kies, then go to recovery and do this, then repeat XX times step 3, reboot, ...", we need to provide a scenario and examples of users that bricked their devices or else this channel to Samsung simply closes .
From what I understand, they are willing to break some devices to be able to confirm the problem.
Feel free to go to the link above and reply directly to Samsung
Weasels! I'm seriously disappointed that their "engineers" don't read up on the latest regarding their own devices....
one thing is for sure, if they can't reproduce it, they wont fix it and pretend that it has nothing to do with their roms..
same situation as franco on his kernel, he can't reproduce the wifi problem so he wont do anything.
i can't use a stock ics + cwm thinking that this bug is present...
We just need as much information as possible.
This is a privileged channel to Samsung, and we should take advantage of this opportunity.
Complaining doesn't help. We need constructive ideas and reliable information
Well, can just say one thing.
Long Live to CM9 and all CM based roms.
Seems that those will be the only safe roms for a long long time.
@nCode : Then go for it bro', break your phone and tell samsung what happend. I wont try to find a way to reproduce the bug except if they give me a Note to test on it.
Well this gonna be challenging. Actually there's no exact way to reproduce hardbrick.
Maybe Entropy or someone of the guys that understand situation to the details should simply try to EXPLAIN what is actually going on... but i agree with Samsung developers it's hard to fix something when you can't reproduce the problem ...
nCoder said:
We just need as much information as possible.
This is a privileged channel to Samsung, and we should take advantage of this opportunity.
Complaining doesn't help. We need constructive ideas and reliable information
Click to expand...
Click to collapse
Well, they could try this scenario on a dozen phones, and they will reproduce it:
1. install a GB Rom, root it
2. make a nandroid backup
3. flash official ICS Rom, get root
4. do several factory resets and cache wipes
5. attempt to do a nandroid restore from the CWMR
They are bound to brick at least one device on step 4 or 5.
Yes, there is a sure way to reproduce the bug:
Take as many Notes as you can that have LPY or any official ICS, it doesn't matter how they got it.
Now factory reset them at least 100 times.
This is no joke, they can do it, it's quality assurance.
chasmodo said:
Well, they could try this scenario on a dozen phones, and they will reproduce it:
1. install a GB Rom, root it
2. make a nandroid backup
3. flash official ICS Rom, get root
4. do several factory resets and cache wipes
5. attempt to do a nandroid restore from the CWMR
They are bound to brick at least one device on step 4 or 5.
Click to expand...
Click to collapse
They won't accept this since it involves root and/or CWM.
I'll try to dig up the report of a user dying on stock recovery.
Why does not Samsung contact Mr Sumrall and other Google developers who worked on the Nexus?
i thought they support developers by supplying smartphones with unlocked bootloaders... they should support rooting and cwm in a way (even the slightest consideration for the betterment of stock )
If I'm not wrong the guy who bricked his phone with stock recovery was Robotu.
http://forum.xda-developers.com/member.php?u=2526707
His brick post. He used stock recovery but was rooted though.
http://forum.xda-developers.com/showpost.php?p=26046849&postcount=140
musashiro said:
i thought they support developers by supplying smartphones with unlocked bootloaders... they should support rooting and cwm in a way (even the slightest consideration for the betterment of stock )
Click to expand...
Click to collapse
That's not the point, if the bug can only be reproduced on a rooted/unofficial ROM then they can simply ignore it by saying that it's not a bug introduced by them. They're not liable for other people's mistakes.
Dragooon123 said:
That's not the point, if the bug can only be reproduced on a rooted/unofficial ROM then they can simply ignore it by saying that it's not a bug introduced by them. They're not liable for other people's mistakes.
Click to expand...
Click to collapse
and again, im just saying its like a "pathway" to fixing it and its proven to be present on official roms by Ken Sumrall..
sorry for not helping a lot, and posting chitchat...
im no big developer but whenever i troubleshoot, i make it to a point that i inspect every possible angle or scenario..
somehow reminds me of the quote "When you have eliminated the impossible, whatever remains, however improbable, must be the truth."
just my 2 cents on this
Dragooon123 said:
That's not the point, if the bug can only be reproduced on a rooted/unofficial ROM then they can simply ignore it by saying that it's not a bug introduced by them. They're not liable for other people's mistakes.
Click to expand...
Click to collapse
But it's a way for them to ESTABLISH that there's something wrong with their kernels. If they want to, of course.
You can wipe everything, and do restores till you drop dead on rooted GB, and everything will be fine.
Not so on ICS, as we all know only too well.
old news, everyone know/should know that samsung software support is peace of sh*t.. even if they will find that bug, they wont announce it because they dont want to reduce company reputation :/
Dragooon123 said:
That's not the point, if the bug can only be reproduced on a rooted/unofficial ROM then they can simply ignore it by saying that it's not a bug introduced by them. They're not liable for other people's mistakes.
Click to expand...
Click to collapse
This is very true. It needs to be something that "the average users" could recreate, meaning going through the "OFFICIAL" steps that Samsung put out. When I was developing for RIM/Blackberry we didn't support any custom software packages and the same thing when I was doing freelance development for Apple as we did NOT support and jailbroken software since it altered out factory coding....LOL.
Ueihtam said:
Well, can just say one thing.
Long Live to CM9 and all CM based roms.
Seems that those will be the only safe roms for a long long time.
@nCode : Then go for it bro', break your phone and tell samsung what happend. I wont try to find a way to reproduce the bug except if they give me a Note to test on it.
Click to expand...
Click to collapse
Nobody is asking to break anyone's phone. We just need reliable information either from people that bricked his phone using a stock ROM, or someone that understands and is able to explain the scenarios.
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
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.
This is an effort to consolidate fixes, tweaks and mods specific to the rooted G955U/G955U1 SnapDragon S8+ via SamPWND.
The initial release of root for this version by the development, contributions and tireless efforts from elliwigy, Harry44, akiraO1, BotsOne, GSMCHEN and jrkruse are obviously being enjoyed by many, as is evident by the visits to elliwigy's release page.
Unfortunately, that thread is in dire need of clean-up because it has become a hodgepodge of redundant rooting questions, helpful answer posts (and complaints), all infused with a few mods and tweaks mentioned.
So let's share what can be done (and what cannot thus far) with this rooted version.
Please (!!!), already be aware of which device you have, and if SamPWND works on your device. "How do / Can I root my..." questions simply don't belong here!
Let's try to keep it clean in here by looking around the forum first before posting, but also by being helpful and not condescending to those of us enjoying root who are perhaps not as knowledgeable about such matters as others.
Some of the most common questions being asked, and their answers from that thread
Flashfire infinitely spinning for part 2 root steps
Turn on airplane mode
Is there a fix for the 80% battery max capacity?
No, and it seems unlikely at this stage. Make yourself happy and hide your battery percentage.
Green/glitchy screen
Most (including myself) have resolved or heavily mitigated this via the AQI1 fw posted recently.
S8+: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810
S8: https://forum.xda-developers.com/ga...ampwnd-green-screen-corruption-fixed-t3673782
Does Magisk work with this root?
No.
Does Xposed work on this root?
Unofficially yes, search for unofficial Xposed s8, it will be in the device forums. Edit-or use this link: https://forum.xda-developers.com/galaxy-s8+/how-to/unofficial-xposed-guide-snapdragon-s8-t3663728
Can I install custom roms?
No, the BL is still locked. The last I read is there are some ideas around how we might achieve an unlock, but nothing so far. There's is the modified stock rom available in the OP of the root thread that provides csc and superSU but beyond that, no.
Screen rotation is messed up / reversed
You downloaded the wrong step 1 files. Try again for your device (plus or non-plus)
I can't think of any other recurring questions, but I've been keeping up to date on that post for more of the 318-or-so pages, and there's a lot of other useful information held within them. Worth a read.
Awesome first response!
So can I start with this:
"Unofficial Xposed'...
Where are the where's & how's located for our specific device, along with the yeahs & no's about what Xposed can do? I've looked and read, but there really is no clear post (that I have found) saying that our model can (or can't) DL Xposed and make things work.
Out of level 8, I'm probably a level 2 coming from rooting back in the days of the first Droid LOL! So I figure if we can keep things down to a level 3 or 4 here, we can learn and teach about WHY certain things won't work.
I'm also very interested in the capabilities of our camera. I used to use chdk to hack Cannon P&S cameras, and despite all my hours doing so, the hardware could never deliver night shots like this phone!
AddictedToGlass said:
Awesome first response!
So can I start with this:
"Unofficial Xposed'...
Where are the where's & how's located for our specific device, along with the yeahs & no's about what Xposed can do? I've looked and read, but there really is no clear post (that I have found) saying that our model can (or can't) DL Xposed and make things work.
Out of level 8, I'm probably a level 2 coming from rooting back in the days of the first Droid LOL! So I figure if we can keep things down to a level 3 or 4 here, we can learn and teach about WHY certain things won't work.
I'm also very interested in the capabilities of our camera. I used to use chdk to hack Cannon P&S cameras, and despite all my hours doing so, the hardware could never deliver night shots like this phone!
Click to expand...
Click to collapse
You may have read my post just before I edited it to add the links. The link I posted for the s8 is where all if the Xposed info is held for our devices. I am currently running it with the latest fw I also linked to with no problems. That thread also contains a few modules the OP has verified working. I am currently only using it for a couple of tweaks from "all my.." and xVoice++. I also was utilizing this Xposed version before flashing the fw mentioned, and it's worked perfectly for both. I can't remember which fw I was on previously though.
regarding camera mods, I made an attempt the moment I got the phone to replace the stock camera with a ported pixel, before researching how to do it properly these days. Wound up with crashing camera warnings every 30 seconds and my backup wouldn't restore properly in titanium and had to reset completely and start fresh.
I used to root back in the Motorola Droid (original) days, when root required 30-or-so lines of commands, I'm sure you remember funny how we've come full circle. I swapped to iPhone for the iPhone 4, enjoyed a bootrom exploit for several iOS versions, and stuck with apple up until just last weekend so it's been a while since I've been on the root scene myself, much has changed indeed. It's the first Android device (S8+ here) that actually made me want to switch away from apple, and I don't yet regret it.
nice concept.. just a forewarning tho, these posts typically go in general discussion..
elliwigy said:
nice concept.. just a forewarning tho, these posts typically go in general discussion..
Click to expand...
Click to collapse
Thanks! And it's alright if it gets moved there so long as it still helps everyone out and you wizards walk through once in a while to bless us all with a bit of wisdom. LOL!
Meanwhile, for as long as it's allowed to stay here, it might serve well to keep distractions off your release thread.
elliwigy said:
nice concept.. just a forewarning tho, these posts typically go in general discussion..
Click to expand...
Click to collapse
Considering less than one hour after I replied with the common questions and answers, someone asked about flashfire on page like 318 again, I'm sure this post is pretty low on priority for the people who tend to ask the questions.
I just finished rooting my sprint s8+ with sampwned. I installed my 256gb micro sdcard and I get the kernel panic reboot to error screen. Am I unable to use the sdcard? I'm scouring xda for any info. Just looking for a little help if anyone knows anything I don't. Thanks.
Nice idea OP.
Some fixes may be had by using the @partcyborg ROM for S8. It is in the S8 ROMs, Kernels, ... Forum https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
For the S8+ @jrkruse has some good info in the S8+ Verizon, ROMs, Kernels, ... Forum. https://forum.xda-developers.com/verizon-galaxy-s8+/development
monroe0328 said:
I just finished rooting my sprint s8+ with sampwned. I installed my 256gb micro sdcard and I get the kernel panic reboot to error screen. Am I unable to use the sdcard? I'm scouring xda for any info. Just looking for a little help if anyone knows anything I don't. Thanks.
Click to expand...
Click to collapse
i think u pmd me but flashing a newer combo boot.img fixes it.. its a known issue with samsungs older combo firmwares, not related to root
elliwigy said:
i think u pmd me but flashing a newer combo boot.img fixes it.. its a known issue with samsungs older combo firmwares, not related to root
Click to expand...
Click to collapse
Yea thats what I did. Problem solved.
Just want to add that the Official xposed app and framework, work on this device
Sent from my SM-G955U using Tapatalk