Database Users

Bootloop issue w/o Perm Root...

Morning or evening...
First of all i would like to point out that i have done the temp root via the unlocker.com method. I have done this since week one of owning the phone and never had any issues till recently.
My dilemma:
I am having an issue with the MT4G. This started last Saturday 4-2 when i plugged my phone into the PC when i tried to load a few videos on the SD card. The phone went into a boot loop and the only way i was able to get out of the boot loop was to do a factory reset or something like that using the power+vol down.
Okay once i did that i quickly temp rooted, and reloaded my backups and wham. Back to normal till i rebooted. Don’t get me wrong this does not happen on the first reboot but more like the 3rd to 5th. Once that reboot happens it goes back into the boot loop and im back to square one.
I have been able to reload all apps and accounts in less then 5 minutes but damn I had to do this 4 times yesterday alone. I have better things to do with my time.
I do not want to be permanently rooted where I can load custom roms/themes and all since I like the rom it came with along with the style. It works for me.
So…
I did do a search and once this happens again im going to do the remove battery for 20 minutes thing but I have a feeling that it wont work.
What am I doing wrong and or what is wrong with the phone? Am I missing a step or something? I am unable to figure this one out so Im asking you fine fellas and gals for some assistance.
Thank you,

What ROM and recovery image are you using? wanting to use?

neidlinger said:
What ROM and recovery image are you using? wanting to use?
Click to expand...
Click to collapse
Stock rom stock everything really. I like the way it looks and runs. If i need to load something up then ill have too, but i would prefer to keep it as stock as possible so i can get the updates and all (if any come).
Hope im not upsetting anyone with the questions im just lost and i know this is the place to be for help with this stuff.

may want to really think about custom ROMS and recovery. some of these MT4G's become unstable after root. while others end up running perfect. mine was one that ended up being REALLY laggy. others get the problem you have. even with temp root.
if you to go the route of custom, be sure to install the eng boot. comes in handy if something goes wrong and will have better chances of fixing your phone if you softbrick it. alot of people skip this and end up with a softbrick with no way of fixing it.
EDIT: also use the newest 3.0.0.6 recovery. it can install BOTH 2.2 and 2.3 roms. another mistake some make is installing a new rom with the wrong recovery version and end up with a bootloop.

Sounds like i either have to go all in or enjoy the crap that Tmo gives me... NAH not going to happen. I guess when i muster up enough balls ill do the perm root. To be honest im a bit hesitant on that since i have already bricked 2 MT3G's already. (gold card method)
Ill keep an eye open for simpler methods...
Q?
If i were to perm root do i have to load a custom rom or can I stay stock? Also ill miss any update if there are any correct?
Thank you

dasudevil said:
Sounds like i either have to go all in or enjoy the crap that Tmo gives me... NAH not going to happen. I guess when i muster up enough balls ill do the perm root. To be honest im a bit hesitant on that since i have already bricked 2 MT3G's already. (gold card method)
Ill keep an eye open for simpler methods...
Q?
If i were to perm root do i have to load a custom rom or can I stay stock? Also ill miss any update if there are any correct?
Thank you
Click to expand...
Click to collapse
To me it sounds as if you have a bad application. every thing works, until you reload the apps. But that is just me
If you permaroot you can stay stock.

you dont HAVE to go to a custom with perm root, but as i said some become unstable and lag after rooting which is some go to custom(among other reasons) some have good luck and the stock rom works fine.
you should be able to get updates fine with root as long as you stay stock on the rom and maybe the hboot/ recovery, not sure if the last 2 affect updates but im pretty sure they dont.
EDIT: check into what neidlinger said. also a strong possibility.

Thank you for your time and responses. Im going to start off with what neidlinger said. In the last week i only installed two apps so hopefully its one of them. I wont load them up when restoring... I will also contemplation on the perm root but i hope the stupid app is the deal. I really like this phone...
Thanks again.
Ill post up some details when/if anything happens.

Alright ... UPdate... YEA right before work.
Removed two apps and still did not work. I was afraid to reboot. Phone lasted phone lasted one week, buggy and laggy as a mofo but it worked... Till today
I tired once again to move some vid files to the phone this time taking out the sd card and as soon as i removed it went into bootloop. FN PHONE!!! I starting to wonder if its the SD card. I already formated it once on the PC since that is where all my files were at. 2 hours to load them. YIKES... Do you think it may be the SD card?
I HATE downloading all the apps again. Also Ill be loosing all my data and backups. FUDGE..............
Not going to temp root this time to see if it may just be the phone. If it is the phone calling TMO... If its the temp root issue then i might freak out since i am still hesitant on rooting.
Anyone is AZ who rooted the phone successfully, other then the Tmo guy i know? LOL... (I asked he wont do mine)
Waiting 20 minutes to put batter back in so im hoping thats it.
If not (im sure it wont) back to stock... Yep 20 minutes past and BACK TO STOCK.... bye bye customizations....IM SOO SAD.. it was nice having a SUPER FAST phone and pissing people off at work with my blazing fast speeds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Q] Best root method for the my touch 4g

OK I'm not new to rooting or xda but I am new to this phone.
I'm not just jumping on here and asking either , I have been searching for the best root method and so far this looks like the best howto I can find.
http://wiki.cyanogenmod.com/wiki/HTC_Glacier:_Full_Update_Guide
I would just like to get a little info from a few people who have rooted this phone.
Also I've been reading about the bad emmc chip and that it may or may not have anything to do with the root method that is used , any thoughts on this would be great.
Any input would be great and or a link to a better guide to root this phone if there is one.
I just like to know as much as possible before I root.
TIA for any help or replies.
Edit: Forgot to mention I'm on 2.3.4 btw.

The guide you linked is the correct answer. Just be sure to follow the section on downgrading to 2.2.1, which is needed to permaroot.
If you're experienced with this stuff it takes about 15-20 minutes (if that) from start to finish.
It's a pretty painless experience.
The one catch you might run into is using ADB to push the update file to the phone. Sometimes it doesn't send the entire file, it leave off like 50 bytes for some oddball reason. So make sure to check the MD5SUMS and the exact file length. Or just avoid that part altogether by copying the file to your SD card in another way before starting the root process.
As for the eMMC chip, I'm convinced it's an overblown problem. If you have the 'bad' one it might break. It might not. I had the bad one and flashed it repeatedly and it never gave me a problem. Then I had the 'good' one and it borked the chip on my first attempt to flash. So while there's a higher probability of the 'bad' one breaking, it's not a guarantee nor is the good one immune. You can check it with a simple script in terminal emulator that's available somewhere in the forum but I forget where.

Skipjacks said:
The guide you linked is the correct answer. Just be sure to follow the section on downgrading to 2.2.1, which is needed to permaroot.
If you're experienced with this stuff it takes about 15-20 minutes (if that) from start to finish.
It's a pretty painless experience.
The one catch you might run into is using ADB to push the update file to the phone. Sometimes it doesn't send the entire file, it leave off like 50 bytes for some oddball reason. So make sure to check the MD5SUMS and the exact file length. Or just avoid that part altogether by copying the file to your SD card in another way before starting the root process.
As for the eMMC chip, I'm convinced it's an overblown problem. If you have the 'bad' one it might break. It might not. I had the bad one and flashed it repeatedly and it never gave me a problem. Then I had the 'good' one and it borked the chip on my first attempt to flash. So while there's a higher probability of the 'bad' one breaking, it's not a guarantee nor is the good one immune. You can check it with a simple script in terminal emulator that's available somewhere in the forum but I forget where.
Click to expand...
Click to collapse
OK so I can just put the update zip on the root of the sd card and just flash that from the bootloader from the phone?
Also is there another recovery for the my touch or is cwm the best one?
Edit: One more thing how often does this root method fail and if it does and the chip goes is the phone bricked ?

Yes, you can just put the file in the root directory of the SD card. That's all ADB does via the terminal on your computer as far as putting the file on your card. (It does a lot more in the overall process)
But no. You cannot just use the bootloader. You have to do steps 1-6 on the Wiki guide you linked first.
So basically....copy the PM15IMG.ZIP file to the root directory of the SD card.
Then do steps 1-6.
Skip step 7 because you've already done it.
Then do steps 8 and on.
And you don't have to do it this way. Sometimes ADB will push the entire PM15IMG file. But if you try to flash the update (downgrade) and it doesn't work, then try copying the PM15IMG in another way.
As for this root method failing, there are a couple ways to brick the phone.
If you pull the battery during the radio update....phone will be VERY bricked. Like won't even power to bootloader kind of bricked. So don't do that.
If the PM15IMG file just doesn't work for some reason, the phone will recognize that the file is bad and basically stop itself from updating. So it's pretty fool proof in terms of getting a corrupt file. Even if it goes through the update process and loads all the way but the phone still doesn't work (gets caught in a boot loop, sticks on the animation screen, has various other problems, etc) you're still good as long as you can get to the bootloader. You can always do a factory reset and start over. Or you can retry the update process and see if it works better the second time.
As for ClockworkMod, I love it. It gives you a lot of options in recovery to fix all or parts or things. It'll let you flash ROMs from the recovery screen so if you louse up a ROM install and can't get the phone to boot you can flash a new ROM from the recovery without having to go through the ADB console on your computer.
That's been helpful more than once. I tried to update a CM ROM. Something went wonky and the phone would just get stuck in the boot animation. So I restarted and went into recovery and reflashed my saved ROM backup and viola! Back to a working phone. That's handy because you can fix major ROM problems when you're away from home far away from your computer.
As fro the chip, if it breaks, the phone is dead. There is no fixing it. I have no idea what the actual odds are. But sometimes you've got to live a little and take your chances.
Enjoy! It's a great phone with a lot of great ROM options.

it's PD151IMG.zip
also, please read my guide here: http://forum.xda-developers.com/showthread.php?t=1388962
and also neidlinger's, posted in my thread.

Thanks guys I'm going to give it a go also I know all about recovery and flashing I just used Amon Ra recovery on my evo over cwm only cause cwm always gave me issues thats why I was wondering if there was something better.
I'll post back how it goes, I'm installing everything from scratch cause I lost my computer so I have to set up the sdk, adb and fastboot all over and now adb doesn't want to work LOL but it always works like that.

First you'll need to downgrade via this guide.
Then once you've done that you can either root via the root.sh method or the gfree method.
Good luck!

Follow macksters advice
Sent from my HTC Glacier using XDA App

Thanks for the ripples I still haven't got the chance to root yet but I did find out that I have the bad emmc chip, now I've never had a phone with one of these things in it and I'm wondering is this thing going to crap out on me?
I'm going to root it either way ad soon as I get the time.
Also I got my son the same phone and his has the bad chip as well what are the chances of that.

"bad" is just a name that people gave it. There might be roughly half of all existing MT4Gs with that chip.

Jack_R1 said:
"bad" is just a name that people gave it. There might be roughly half of all existing MT4Gs with that chip.
Click to expand...
Click to collapse
So its just more likely that those chips are the cause of people bricking their phones or just a couincidence?
Also I'm still not rooted yet and I'm having a few issues with the phone like apps fcing and the touch screen gets a little crazy at times like a ghost is messing with my phone, now is that just the stock ROM or can that be do to the "bad labeled" chip?

"Bad" chip has a bit higher failure rate, which means - statistically, if you take 100 people with "bad" chip and 100 with "good" chip, root their phones, and you'll get 1 total failure (probably less, but it's not number-accurate, just for demonstration) of "good" chip that will fail after rooting, and 2-3 failures of "bad" chip.
Again, chips that are really prone to failure ultimately WILL fail - rooted or not. Rooting just stress-tests them.

Jack_R1 said:
"Bad" chip has a bit higher failure rate, which means - statistically, if you take 100 people with "bad" chip and 100 with "good" chip, root their phones, and you'll get 1 total failure (probably less, but it's not number-accurate, just for demonstration) of "good" chip that will fail after rooting, and 2-3 failures of "bad" chip.
Again, chips that are really prone to failure ultimately WILL fail - rooted or not. Rooting just stress-tests them.
Click to expand...
Click to collapse
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium

saranhai said:
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
From what I understand, it's the gfree exploit that stresses the eMMC and causes the fail.
But to the OP, what I've noticed is that people with the bad eMMC chip tends to fail rather shortly after they root. Many people that have had bad chips, including myself at one point, had it rooted and was flashing ROM's weekly for months with no issue. I think if it doesn't fail shortly after you root, you should be in the clear. But that's just my speculation.

mackster248 said:
From what I understand, it's the gfree exploit that stresses the eMMC and causes the fail.
Click to expand...
Click to collapse
It was pretty clearly defined, with help by the guy who wrote gfree, how gfee has nothing to do with it.

saranhai said:
Not the process of rooting. It's the stuff you do AFTER rooting, flashing ROMs, themes, mods, radios etc that will speed up the process of the chip dying. This is because when you flash something, big chunks of data get written to the eMMC chip, and if you keep doing it constantly, there is a possibility that the chip will die. This is the reason behind the chips dying, not the actual rooting process, but the stuff that you do AFTER rooting it.
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
Yes, this is correct, of course.
The rooting itself does only one potentially (arguably?) dangerous thing - it power-cycles the eMMC to intercept its initialization and prevent setting the read-only mode. eMMC seem to be sensitive to power-cycling while they're being accessed, some of the eMMC failures of both "good" and "bad" kinds were reported after pulling the battery on a working phone stuck in the middle of writing something. In any case there's nothing to do to avoid this power-cycling, though - any method of root has to include it.

This is sounding worse and worse lol.
I'm going to root no matter what but how does t-mobile insurance work I'm new to t-mobile but I'm paying for the insurance, or would it be possible to get a replacement through the warrant if this chip goes?

You call t mobile and tell them your new phone stopped working. Act like a dunce who doesnt know tghe difference vetween a phone and your butt and they will send you a new one.
Sent from my HTC Glacier using XDA App

Yeah I'm not usually a crook but they shouldn't really sell a phone with a faulty chip in it either.

This chip (the specific eMMC model) exists in at least 3 another phone models - Desire HD, Desire S, T-Mobile G2.
These chips fail in all of the phone models. There is one in my wife's Desire S (of course, rooted).
Their failure rate is VERY low. The problem is that on the forum you won't see the 99.99% of people that it works for them, you'll most probably see the 0.01% that has failures.

LG G Stylo (T-Mobile/MetroPCS) ROOT (5.0.2 & 5.1.1 ) - TWRP Recovery - Unbrick Guide

LG G Stylo (T-Mobile/MetroPCS) ROOT (5.0.2 & 5.1.1 ) - TWRP Recovery - Unbrick Guide
DO THIS AT YOUR OWN RISK
WARRANTY IS NOW AVOID IF YOU PROCEED WITH ROOT AND TWRP
Windows Machine/OS Only
----------- Lets Proceed on to Rooting LP 5.1.1 (One Click Method) -----------​1- Click Here and Download LGGSTYLO_LP511_OneClickRoot.zip File
2- Click Here and Download LG USB Drivers ( Thanks @GameTheory. )
"NOTE: skip Drivers if you have them already install"
4- Enable USB Debugging via Developer Option.
5- Decompress LGGSTYLO_LP511_OneClickRoot.zip on Root C: drive for easy access or any convenient location.
6- Now lets head over where we decompress that zip file and just double " LG_Root_Script.bat "
7- LET the script run to FULL COMPLETION, Your Device will Reboot twice so be patient.
IF YOU HAVE YOU DEVICE WITH LOCKSCREEN CODE / SWIPE CODE NEED TO UNLOCK SCREEN ON EACH REBOOT FOR THE SCRIPT TO PROCEED
Check Image for the whole process - CLICK TO SHOW CONTENT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8- when the process say
Code:
ui_print - Done !
press Ctrl+C
press N then ENTER
( Check Image - CLICK TO SHOW CONTENT )
- And you are done your device is now Rooted
- Phone will Reset and you need to wait till phone is fully Rebooted to system it may take a few minutes so be patient.
NOW YOU CAN PROCEED TO FLASH CUSTOM RECOVERY (TWRP)
-----------------------------------------------------------------------------------------------------------------------
THIS METHOD ONLY WORKS IF YOU ARE IN LP 5.0.2
----------- Lets Proceed on to Rooting LP 5.0.2 -----------
​
First of all Thank you @avicohh for LG One Click Root GUI/Script base on his Guide I Have successfully Rooted the Stylo using and Following some steps from there just adding some thing you may see in the progress of rooting:
Original LG One Click Root Guide and File Download -CLICK HERE-
After getting all necessary files this is what i did
1- Install LG drivers if they are not installed yet. (VERY IMPORTANT)
2- Download the LG One Click Script Root file above and extract to some folder. (double click on the 7z exe file)
3- Enable Usb debugging on your phone. (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (THIS IS VERY IMPORTANT STEP)
4- Connect your phone to pc. (it will install driver when connected just wait till is done)
5- Switch to MTP when drivers are full install
6- Double click on the LG Root Script.bat file (the Script will run)
7- Follow the instructions.
*Please leave your feedback if it worked for you
Many Many Thanks to @avicohhfor the LG One Click Root
P.S. I'm not a Dev. I just followed the original guide and the only thing i haven't install is Custom Recovery.
If you came across some Fail attend messages just wait a few more seconds, if that doesn't work try again in my case the first try work and 2 fail attends messages came up so just wait a few sec. if that happen
BE PREPARED. First boot can take a while!!! can stay on logo for up to 3 to 5 minutes or sometimes little more before it goes into Optimizing Apps. Have patience. Subsequent boots a pretty speedy.
------------------------------------------------------------------------------------------------------------
TWRP (Custom Recovery) for LG G Stylo T-Mobile (H631) and Metro (MS631) Variant ONLY
------------------------------------------------------------------------------------------------------------​
- Download Custom Recovery File from TWRP 2.8.7.0 v10j Click HERE (Thank you @Unjustified Dev and @fix-this! )
After Rooting your device (T-Mobile or Metro Variant)​
1- Check -Enable OEM Unlock- under Developer Option (Skip this part if you are 5.0.2)
2- download Flashify from Google Play Store
3- Open Flashify.
4- Do a Stock Recovery Back-up (Recommended)
5- Flash Recovery Image.
6- Will ask to Reboot System and will take you to TWRP Custom Recovery.
7- Now you are done just Reboot System from Recovery or do a FULL BACK-UP
NOTE : This New TWRP (Custom Recovery) have the new fix (Showing Half Screen only) for the new LG G Stylo Hardware Panel.
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
LG G Stylo Update Firmware | Unbrick Guide by @GameTheory.
IF YOU ARE USING @GameTheory. v10i UPDATE ZIP DON'T FLASH v10j UPDATE ZIP , I REPEAT DON'T FLASH v10j UPDATE ZIP YOU'LL END UP WITH BOOTLOOPS/SOFT BRICK
-------------------------------------------------------------------------------------------------------------​
Just Follow step from link below - Thank you @GameTheory.
http://androidcreations.weebly.com/lg-g-stylo.html
------------------------------------------------------------------------------------------------------------
Every KDZ Release for T-Mobile and Metro can be found here :
http://forum.xda-developers.com/android/development/read-trying-to-root-kdz-files-kdz-tmo-t3152531
------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
Full v10j Stock Restore / Update
Use this guide if you are on @GameTheory. v10i or want to deleted all trace of root and twrp (Back to Stock)​
Full v10j Stock Restore / Update
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------

i just picked up the tmob version yesterday, nice device. not the greatest screen ive had but not bad. im also rooted, we just need twrp so we can use xposed.

waiting on TWRP
As previously posted, I am also waiting on a conduit to get xposed installed.. a device without it and all the benefits it brings feels unreal to me..

i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.

fix-this! said:
i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.
Click to expand...
Click to collapse
+100 on that (Battery life + dedicated section for the phone) i have to agree with the battery life pretty neat and i'm sure is because CPU is doesn't have higher clock and screen is not so power hunger, other thing i'm satisfied is the memory management no matter what i do i haven't seen going lower than 1gb of ram always i been having between 1.2gb to 1gb free never had that before so pretty neat and i do have a lot of apps install most of them run in the background,
How can be make a request about making a Dedicated Section for the LG G STYLO? where do i need to sign if that happen i'll be posting some Bootanimations for this phone porting some old ones i created for the G2 and probably making some new ones.

I am pretty impressed with the device. I just bought it for my wife, which she doesn't care what phone I give her as long as it doesn't break the bank. Not able to do that with any of the flagships. Decided to give it a try risking not having the dev support. Hopefully more people takes the risk so we can have custom roms to play for. (not sure if my wife would like that) LOL

Ah, good, a T-Mobile Stylo thread. I just posted my thoughts in the thread for the Boost (Sprint) version, but anyway, I'm mostly liking this phone (except that the camera app doesn't offer manual exposure controls). I'm not sure I'm going to root mine just yet (hell, I still haven't rooted my Avant!), but it's nice to see that a root is available.

i'll leave this here First Custom Boot Animation for the Stylo
https://www.youtube.com/watch?v=wP5EZfmE-oQ

This is really a Lollipop issue, rather than a problem with the phone itself, but I found that the Embware call blocker (which disappeared from Google Play, go figure) doesn't work on the Stylo. It turns out, most of the call blockers out there aren't working on Lollipop.
What I particularly want is a pickup/hangup type of block, so Rachel from Card Services can't even leave a voicemail. I had this capability with the Embware blocker on the KitKat-equipped Galaxy Avant, even before I got around to rooting it. It looks like Google tweaked Lollipop to prevent pickup/hangup blockers from working. #&^%$%^!!!
Extreme Call Blocker claims to work on L, but I'm wary of forking over the cash for it.
There is a built-in reject list under the Call Settings menu, but it's just a straight-to-voicemail reject. I don't want to waste my time deleting spam voicemails, though Visual Voicemail is at least quicker than calling in.
I suppose I could just call T-Mobile and see if they could turn off voicemail entirely. That would at least make the native call blocker useful.

Timberwolfhusky said:
,
Click to expand...
Click to collapse
i found this post to open a new phone section if we show support for the STYLO we may get a Section for it and people can just go there for Q&A, Themes,Dev work and so on, i know the Phone still brand new in everyone eyes but early support doesn't hurt
http://forum.xda-developers.com/show....php?t=1660354
P.S. @Timberwolfhusky you are the only person not in Boost Mobile thread so

I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?

guest_2011 said:
I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?
Click to expand...
Click to collapse
is to early to say it but i have seen a lot of activity and a lot of people are interested on this device, some user with the Zmax are going to be upgrading to the Stylo, we have a pretty good start phone is 100% Rootable as you can see on the 1st post and @fix-this! is working getting the TWRP (Custom Recovery) so i would say we are getting good support so far, Not a lot of support but good.
P.S. this Device is Brand new just got release.

I've also seen some articles that indicate that outside of North America, it's being marketed as the "G4 Stylus" - and also in the international market there's also a G4c model with similar specs; like the Stylo, it has a 720p screen, but it has a smaller form factor than the flagship G4, no stylus, and an 8MP camera.
The T-Mobile G Stylo seems to be the best of the bunch, though: double the RAM and double the storage of the Boost version. Having been a T-Mobile subscriber for a while now, I'm glad to see that they bumped up the specs. It also has the unlock app baked-in, so if you're eligible to unlock it, there's no need to call in or fumble around with unlock codes. I used the unlock app on my Avant before I bought the Stylo, and it worked smoothly and easily. If you're not eligible to permanently unlock it, you can still get a 30-day unlock for international travel.
I'm finding that I like this phone a LOT, in spite of the lack of manual camera settings and the Lollipop-related call blocker issues. The HDR mode seems to be able to handle backlit subjects well enough that the lack of manual exposure control isn't as big a deal as I was thinking it would be.
So far, battery life looks to be in the "outstanding to exceptional" range. It reminds me of the F3 in that respect, but this is a vastly better phone than the F3 could ever hope to be. At least somebody is listening when it comes to battery life!
I'm going to hold off on rooting mine for now, though, at least until I can SIM-unlock it. In any case, I've always been a bit cautious about modding my primary phone.

How's the battery life compared to the tmo zte zmax?(for those that had the zmax)
Also, does this have the "feature" that when the phone reaches certain temps it lowers and prevents you from turning up screen brightness?
Sent from my Z970 using XDA Free mobile app

Will it work (root guide) with Metropcs? I just ordered one. Is metro also the same model LG-H631? I see LS770 on the web, not sure if same phone or something else. Anybody tested USB OTG with Stylo?

Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.

fix-this! said:
Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.
Click to expand...
Click to collapse
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.

guest_2011 said:
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.
Click to expand...
Click to collapse
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.

Is it possible to unroot?

fix-this! said:
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.
Click to expand...
Click to collapse
agree with you this phone needs his own section i'm sure will be good success from LG i have friend that have the Zmax and they are going to be getting the Stylo, we just need someone with the MetroPCS Variant to verified if is rootable the same way the T-mobile variant is.
guest_2011 said:
Is it possible to unroot?
Click to expand...
Click to collapse
the SU app have an Option to Unroot, i personally haven't try it but maybe someone else know if that works.... never had the need to unroot a phone so i have no idea about that

SM-T337V - Can't Factory Reset

Howdy all!
I'm a long time lurker and user of helpful tips and tricks, advice, and knowledge on this forum. So thank you to all of you for that! I have been using an Android for several years now and have been able to find the answers to any of my questions up until now! So I've now become a member of this fine establishment and hopefully you guys can help me with this issue!
Typically my issues seem to be common amongst fellow Android users, but this one I was only able to find ONE thread that had a similar issue. However, it was with a different device, so I didn't want to try and follow it for my device! That thread is here:
http://forum.xda-developers.com/galaxy-tab-s/general/factory-data-reset-hard-reset-problem-t2926702
So, as the title of this thread states, I am having a problem doing a Hard Reset on my recently purchased SM-T337V Samsung Galaxy Tab 4 8.0. I bought this from ebay with the description that the password/PIN was unknown and it couldn't be reset. So, naively I figured they just didn't know how to do a factory reset and I bought the tablet. I received it today and that's when the troubles began.
I will say this before I go any further, I am not a total newb at this stuff. I have been using Android for years and have successfully rooted a few of my devices and installed custom ROMs, but that's about it. I really only know and understand this stuff just enough to get in trouble, so if I leave out any pertinent information, just let me know. I will try and be as thorough as possible.
I received the tablet today, booted it up and it boots right into a PIN lockscreen. Obviously I don't know the PIN and so that leaves me at a dead end. Next step was to try and do a Factory Reset. Here are the following steps that I took that lead me here:
1. Turn off the tablet
2. Boot into Recovery by holding HOME+VOL UP+POWER
3. When the tablet boots into Recovery, this is displayed:
Android system recovery <3e>
KOT49H.T337VVRU1ANE1
​...along with the typical options for recovery.
4. Volume Down to "wipe data/factory reset"
5. Press POWER to select.
6. This is then displayed at the bottom of the screen:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC
-- Warning ...
MDM does not allow factoryReset.
Phone will REBOOT automatically.
​7. Phone then reboots automatically back to the PIN lock screen.
Now, from what I have been able to learn by Googling this warning, it seems as though this tablet was a Live Demo version or something like that? I'm guessing one they had in the store for people to try out or something along those lines?
What do I need to do to get this tablet back up and running like a stock factory brand new tablet? I was thinking that I just needed to install the Stock ROM via Odin and then I'd be able to have the tablet working, but I read somewhere that doesn't remove the MDM restrictions? I don't know if that's the right way of thinking or if I need to do something else? In the link to the thread above that I found with a similar issue, it seems as though they just installed the Stock Firmware via Odin and all was good to go?
I have also gathered from reading about this that the ROM that is on this tablet right now (KOT49H.T337VVRU1ANE1) is based off 4.4.2 and is also able to be rooted. Which is a good thing that it is not updated to the 4.4.4, which apparently cannot be rooted. Obviously, that will need to come AFTER I can get this thing reset.
Oh, I forgot to mention that I can also boot it into Download mode by holding HOME+VOL DOWN+POWER.
Hopefully I have supplied you guys with enough information to help me out. Like I said, if I've left something out, please let me know and I'll give you whatever information you need!
Rawk!
-NDN

Any luck with this issue? I have the same problem.
Thanks
shawneendn said:
Howdy all!
I'm a long time lurker and user of helpful tips and tricks, advice, and knowledge on this forum. So thank you to all of you for that! I have been using an Android for several years now and have been able to find the answers to any of my questions up until now! So I've now become a member of this fine establishment and hopefully you guys can help me with this issue!
Typically my issues seem to be common amongst fellow Android users, but this one I was only able to find ONE thread that had a similar issue. However, it was with a different device, so I didn't want to try and follow it for my device! That thread is here:
http://forum.xda-developers.com/galaxy-tab-s/general/factory-data-reset-hard-reset-problem-t2926702
So, as the title of this thread states, I am having a problem doing a Hard Reset on my recently purchased SM-T337V Samsung Galaxy Tab 4 8.0. I bought this from ebay with the description that the password/PIN was unknown and it couldn't be reset. So, naively I figured they just didn't know how to do a factory reset and I bought the tablet. I received it today and that's when the troubles began.
I will say this before I go any further, I am not a total newb at this stuff. I have been using Android for years and have successfully rooted a few of my devices and installed custom ROMs, but that's about it. I really only know and understand this stuff just enough to get in trouble, so if I leave out any pertinent information, just let me know. I will try and be as thorough as possible.
I received the tablet today, booted it up and it boots right into a PIN lockscreen. Obviously I don't know the PIN and so that leaves me at a dead end. Next step was to try and do a Factory Reset. Here are the following steps that I took that lead me here:
1. Turn off the tablet
2. Boot into Recovery by holding HOME+VOL UP+POWER
3. When the tablet boots into Recovery, this is displayed:
Android system recovery <3e>
KOT49H.T337VVRU1ANE1
​...along with the typical options for recovery.
4. Volume Down to "wipe data/factory reset"
5. Press POWER to select.
6. This is then displayed at the bottom of the screen:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC
-- Warning ...
MDM does not allow factoryReset.
Phone will REBOOT automatically.
​7. Phone then reboots automatically back to the PIN lock screen.
Now, from what I have been able to learn by Googling this warning, it seems as though this tablet was a Live Demo version or something like that? I'm guessing one they had in the store for people to try out or something along those lines?
What do I need to do to get this tablet back up and running like a stock factory brand new tablet? I was thinking that I just needed to install the Stock ROM via Odin and then I'd be able to have the tablet working, but I read somewhere that doesn't remove the MDM restrictions? I don't know if that's the right way of thinking or if I need to do something else? In the link to the thread above that I found with a similar issue, it seems as though they just installed the Stock Firmware via Odin and all was good to go?
I have also gathered from reading about this that the ROM that is on this tablet right now (KOT49H.T337VVRU1ANE1) is based off 4.4.2 and is also able to be rooted. Which is a good thing that it is not updated to the 4.4.4, which apparently cannot be rooted. Obviously, that will need to come AFTER I can get this thing reset.
Oh, I forgot to mention that I can also boot it into Download mode by holding HOME+VOL DOWN+POWER.
Hopefully I have supplied you guys with enough information to help me out. Like I said, if I've left something out, please let me know and I'll give you whatever information you need!
Rawk!
-NDN
Click to expand...
Click to collapse

I'm having same trouble. Odin failed to flash twrp. Still plugging away at it.
My skill level, experience and issue at hand is the same as OP.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
http://www.sdse-samsung.com/solutionline/mdm.html

ericpeacock79 said:
I'm having same trouble. Odin failed to flash twrp. Still plugging away at it.
My skill level, experience and issue at hand is the same as OP.
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
http://www.sdse-samsung.com/solutionline/mdm.html
Click to expand...
Click to collapse
You can't have TWRP on a SM-T337V, it has a locked bootloader which means no custom kernels, no custom recoveries

thisisapoorusernamechoice said:
You can't have TWRP on a SM-T337V, it has a locked bootloader which means no custom kernels, no custom recoveries
Click to expand...
Click to collapse
ohh, man.
Would Samsung or Verizon be able to unlock the bootloader? (i know able and willing are two different things)
i see many references around the interwebz to custom ROM's being installed on it, rooting, etc. I hadn't seen that it was BL locked. (i've currently got about 30 tabs open, xda and a few other websites)
I've tried flashing the stock firmware via Odin, and it gives green pass, but after reboot, there is no change at all.
This makes me think there is a secure storage area to retain corporate settings outside the normal ROM areas.
I was desperately hoping to get custom recovery on it.
i bought this tablet for cheap on ebay (although, it was listed as a different model, i don't blame the seller for not knowing how to get into Odin mode and get the exact model)
It's locked out thru some mdm, not sure which; only the one corporate app on the home screen shows and literally nothing else is accessible. (can't even swipe down for notification area)
I tried to sideload towelroot and kingroot, tried to sideload another launcher - nothing works.
Based on the ebay listing, it seemed as though I would be able to just flash new recovery, install custom rom and be able to flip it for profit.
Looks like I've just got a shiny paperweight.
---------- Post added at 01:56 PM ---------- Previous post was at 01:37 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/pwd1rt4
I guess that's what the secure magic code is? "You can't do this".

ericpeacock79 said:
ohh, man.
Would Samsung or Verizon be able to unlock the bootloader? (i know able and willing are two different things)
Click to expand...
Click to collapse
I don't know about able, but they're definitely not willing. I have a locked bootloader phone and it's awful not being able to have custom anything
Unfortunately I don't know anything about the mdm issue, can't really help you there

So, called Samsung support and explained situation and asked for bootloader unlock tool.
They would not give it to me, but told me to go to any Best Buy and the Samsung center would factory flash it for free.
Went to best buy and they flashed Lollipop ROM for free, as promised. I asked if he could unlock bootloader and he said he could not.
But tablet is now functional on stock lollipop now!!!

Wow verizon seems to be some real cancer out there if they wont let their device get factory reset normal way! Also my old tab acer iconia cant be unlocked!

thelous said:
Wow verizon seems to be some real cancer out there if they wont let their device get factory reset normal way! Also my old tab acer iconia cant be unlocked!
Click to expand...
Click to collapse
In the case of my tablet, and the OP of this thread, the tablet had restrictions from an MDM (Mobile Device Management) software. Also, tablets that were display models could have this, aka "kiosk mode".
If I'd had access to the company that originally set the device policy, they could have unlocked it thru their enterprise control software and I would have been able to do the normal factory reset in recovery mode.
This wasn't Verizon or Samsung's fault, but Samsung fixed it for free.

BOOT into ODIN downloading screen
hold POWER + VOLUME DOWN + HOME BUTTON
NO NEED for ODIN PC Software,
just
"Verizon Wireless Software Upgrade Assistant "it will download lastest firmware and repair and factory reset, also unlock boot MDM block

Won’t hard reset done tried everything keeps saying security policy prevents it from hard reseting

Meh I'm in the same boat.... **** MDM...
Got it, semi brick the SOB w/ Nand Erase, stock firm then you'll probably get this option
Maintenance Boot Mode, go ahead for a safe mode boot, probably won't work so you'll
need the PIT file for it and a stock firm w/ full certs et al. and it'll do the trick and boot the MDM Block.

shawneendn said:
Howdy all!
I'm a long time lurker and user of helpful tips and tricks, advice, and knowledge on this forum. So thank you to all of you for that! I have been using an Android for several years now and have been able to find the answers to any of my questions up until now! So I've now become a member of this fine establishment and hopefully you guys can help me with this issue!
Typically my issues seem to be common amongst fellow Android users, but this one I was only able to find ONE thread that had a similar issue. However, it was with a different device, so I didn't want to try and follow it for my device! That thread is here:
http://forum.xda-developers.com/galaxy-tab-s/general/factory-data-reset-hard-reset-problem-t2926702
So, as the title of this thread states, I am having a problem doing a Hard Reset on my recently purchased SM-T337V Samsung Galaxy Tab 4 8.0. I bought this from ebay with the description that the password/PIN was unknown and it couldn't be reset. So, naively I figured they just didn't know how to do a factory reset and I bought the tablet. I received it today and that's when the troubles began.
I will say this before I go any further, I am not a total newb at this stuff. I have been using Android for years and have successfully rooted a few of my devices and installed custom ROMs, but that's about it. I really only know and understand this stuff just enough to get in trouble, so if I leave out any pertinent information, just let me know. I will try and be as thorough as possible.
I received the tablet today, booted it up and it boots right into a PIN lockscreen. Obviously I don't know the PIN and so that leaves me at a dead end. Next step was to try and do a Factory Reset. Here are the following steps that I took that lead me here:
1. Turn off the tablet
2. Boot into Recovery by holding HOME+VOL UP+POWER
3. When the tablet boots into Recovery, this is displayed:
Android system recovery <3e>
KOT49H.T337VVRU1ANE1
​...along with the typical options for recovery.
4. Volume Down to "wipe data/factory reset"
5. Press POWER to select.
6. This is then displayed at the bottom of the screen:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC
-- Warning ...
MDM does not allow factoryReset.
Phone will REBOOT automatically.
​7. Phone then reboots automatically back to the PIN lock screen.
Now, from what I have been able to learn by Googling this warning, it seems as though this tablet was a Live Demo version or something like that? I'm guessing one they had in the store for people to try out or something along those lines?
What do I need to do to get this tablet back up and running like a stock factory brand new tablet? I was thinking that I just needed to install the Stock ROM via Odin and then I'd be able to have the tablet working, but I read somewhere that doesn't remove the MDM restrictions? I don't know if that's the right way of thinking or if I need to do something else? In the link to the thread above that I found with a similar issue, it seems as though they just installed the Stock Firmware via Odin and all was good to go?
I have also gathered from reading about this that the ROM that is on this tablet right now (KOT49H.T337VVRU1ANE1) is based off 4.4.2 and is also able to be rooted. Which is a good thing that it is not updated to the 4.4.4, which apparently cannot be rooted. Obviously, that will need to come AFTER I can get this thing reset.
Oh, I forgot to mention that I can also boot it into Download mode by holding HOME+VOL DOWN+POWER.
Hopefully I have supplied you guys with enough information to help me out. Like I said, if I've left something out, please let me know and I'll give you whatever information you need!
Rawk!
-NDN
Click to expand...
Click to collapse
Got the same problem on a T337V it camed with a Service firmware from something like a BodyShop for Service, I couldn´t make any factory reset, I realized the it was "MDM Locked". I flashed 2 diferent firmwares hopping to make it functional, but I got stucked at "Samsung" boot Logo. Then I just restored one today with Verizon_EUT_Installer_0601 program. Found on Verizon support page, seems that they have they firmwares for their locked bootloader Devices. Try ut it took me up 2 hours to make ir work. :fingers-crossed:

> MDM does not allow factoryReset.
Sometimes MDM has an erase data feature after 10 bad login attempts. So, you just type 10 random passwords and you might get a warning that it will factory reset the device. You still have to contend with Knox and/or MDM thereafter, so this is only a partial workaround.

ericpeacock79 said:
So, called Samsung support and explained situation and asked for bootloader unlock tool.
They would not give it to me, but told me to go to any Best Buy and the Samsung center would factory flash it for free.
Went to best buy and they flashed Lollipop ROM for free, as promised. I asked if he could unlock bootloader and he said he could not.
But tablet is now functional on stock lollipop now!!!
Click to expand...
Click to collapse
will your where there you should have asked for the combination files too sigh

blaze2051 said:
will your where there you should have asked for the combination files too sigh
Click to expand...
Click to collapse
You realize you are replying to a 5 year old comment?

ericpeacock79 said:
You realize you are replying to a 5 year old comment?
Click to expand...
Click to collapse
lol of course bro

[Root][FIX][S8+]Root Green Screen/Corruption FIXED with AQI1 COMBINATION Boot Firm

Greetings!
Allow me to present to you:
How to Dramatically improve your Rooted S8 Display Quality
And Eliminate the Green/Garbled Screen bug
NOTE: Some users are still experiencing the green/garbled screen issue after flashing.
However all reports of this have indicated that it is happening noticeably less frequently.
Update:
I am looking into this and will have some changes out shortly that will hopefully help. It is difficult for me to troubleshoot because I literally can not get it to happen to my phone anymore so it is difficult to verify improvements before shipping them out to you, but I am doing my best.
​
WHAT?!
I found the following today while digging around chinese phone firmware sites via baidu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In case you can't tell what that is, it is a BRAND NEW "Combination" Firmware with the label AQI1. The combination firmware is a special factory image used by service workers and XDA members who want to do things like change their CSC or bypass a FRP lock. meaning its almost completely brand new! AQI1 stands for "September 2017", which means this is a brand spanking new image only a few days old!
WHO CARES?
Why is this important? Well it just so happens that the Combination firmware boot image (boot.img) is what we all flashed as part of the SamPWND root. The boot.img file contains the kernel and root filesystem ramdisk. We were running one from sometime around April, which is very old compared to the modern builds most of us flashed after rooting. Furthermore, the image we all are currently running is likely one of the first kernels rolled out for the phone, so its no wonder there was an issue like this that was not fixed (who cares if you get greenscreen in 5m of CSC update).
So all it takes is a simple flash in FlashFire of the AQI1 boot.img (provide at the bottom of this post), an operation that does NOT require a wipe of /system, /data, or anything really (although I recommend a cache wipe in recovery for good measure, but it is very likely not necessary). Your phone will just come back up with a slicker modern kernel and most of all NO MORE ANNOYING DISPLAY BUGS!!!
WHAT IT IS NOT:
Now that I have explained what this thread is about, I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN UPGRADED OS.
This is ONLY the special factory / Combination CSC and diagnostic ROM that has been floating around forever, just a modern build.
It is also the ONLY AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE
I tested this on my S8 G950U but I don't have an s8+ to test with. I imagine that it will work the exact same way but I can't be sure. Hopefully some of you early adopters can share your results with the thread so that we can build some confidence here
NOTE: This is for the s8+ G955 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it. See the other thread if you have a regular S8 US Snapdragon model.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere as I don't have an s8+
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: G955USQU1AQI1 BOOT.IMG
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and factory reset your device tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I will be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: There is an s8 thread in the s8 forums, if you have one of those use that method. There absolutely are binary diffs between versions so SOMETHING is different, and Id rather not have your briked phone on my concious.
SPECIAL THANKS TO:
@elliwigy and @stf_TimelessGoD and the rest of the SamPWND crew for getting us this awesome root in the first place
@elliwigy again for turning me on to the fact that this was a thing at all
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, the tons of you out who have made so many awesome mods, themes, apps, workarounds, tools, etc etc etc. What you have made I use every day and all of it makes me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
BONUS: Here is a link to the entire combination image if you want to take a look at the rest of it. Don't flash the rest of it if you don't know what it is, as it wipes everything and you will have to root from scratch again!
http://goo.gl/pYyg7s

@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again

This can be flashed over AQH3, right ?.

jawonder said:
This can be flashed over AQH3, right ?.
Click to expand...
Click to collapse
why not? as long as its not incremented you are good.. u could prolly even dd it if u want

Working ok for me .

mopartonyg said:
@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again
Click to expand...
Click to collapse
Good idea I will post a rollback tar in case anyone has issues

All seems to be working well, if not, things are more fluid for me. No green screen yet either. Thanks, will continue to report in.

Glad to hear it's working out!
I thought the screen looked better too but I thought it was likely I was seeing things lol

The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.

Great job @wildermjs8 - thanks for the upload ?????

patmorris said:
The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.
Click to expand...
Click to collapse
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img

elliwigy said:
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img
Click to expand...
Click to collapse
I'm perfectly content. It's definitely much better than it was.

Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk

Araltd said:
Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk
Click to expand...
Click to collapse
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol

It's early days with new firmware so we will see

Quickvic30 said:
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol
Click to expand...
Click to collapse
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Sent from my SM-G955U1 using Tapatalk

Araltd said:
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Click to expand...
Click to collapse
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point

elliwigy said:
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point
Click to expand...
Click to collapse
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm

wildermjs8 said:
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm
Click to expand...
Click to collapse
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today

elliwigy said:
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today
Click to expand...
Click to collapse
Except that isn't always the case. Having run pre-release engineering kernels from cupcake-marshmellow I have a little experience in this area, and outside of VERY early days G/Nexus/Pixel never exhibited a problem like this so I find it a bit surprising.
Forgive me for putting the thread in the wrong place, I guess I deserved that for trying putting related things together. Why does it feel like I'm being dragged into a pissing contest?
I was just trying to help people out, maybe I just shouldnt bother.
Mods can move the threads wherever it doesn't matter to me.