Database Develop

On / Off button not working good

Hello everyone,
My phone has had some annoying thing since 2 days ago, everything was fine and it just worked the way it had to, but now i have to press the on/off button atleast like 4 times to get the screen on, at very rare occasions its an 2 times click but mostly 3+
im going back to t-mobile to ask what their advice is, what is your advice?
How to minimize the chance they find out i had done root and unlocked bootlaoder ? ^^

Root will be removed after flashing any rom, as for bootloader, someone said flashing taiwan JB relocked theirs, whether it will stay locked when going back to euro is another thing. If it doesn't flash ICS and pray they dont update it
Sent from my rooted P880

@non4 said:
Root will be removed after flashing any rom, as for bootloader, someone said flashing taiwan JB relocked theirs, whether it will stay locked when going back to euro is another thing. If it doesn't flash ICS and pray they dont update it
Sent from my rooted P880
Click to expand...
Click to collapse
ill unroot it with supersu or just something else if i have to send it, i think they gonna try if it is hardware or software failure, so i hope they do not see i installed cwm and unlocked bootloader xd
i think its hardware failure :S

Tomaat said:
ill unroot it with supersu or just something else if i have to send it, i think they gonna try if it is hardware or software failure, so i hope they do not see i installed cwm and unlocked bootloader xd
i think its hardware failure :S
Click to expand...
Click to collapse
Flash ICS, you're less likely to be found out
Sent from my rooted P880

@non4 said:
Flash ICS, you're less likely to be found out
Sent from my rooted P880
Click to expand...
Click to collapse
Also, if it's a hardware failure and you've bought their phone in Europe, they really can't deny fixing it because you have an unlocked bootloader and/or a rooted phone. Read more about it here, so you can go to them with all the information you might need

ain`t you pressing it hard enough? Mine used to be perfect, after a couple of months using it the button became faulty and now I have to press kind of hard otherwise it doesn`t work. But every time I press it hard enough it works.

Hardware
Me too

gabrielgon said:
ain`t you pressing it hard enough? Mine used to be perfect, after a couple of months using it the button became faulty and now I have to press kind of hard otherwise it doesn`t work. But every time I press it hard enough it works.
Click to expand...
Click to collapse
nguyenthanhphong said:
Hardware
Me too
Click to expand...
Click to collapse
If someone as skills, can try to open the device and check how are the metalic parts that activate the hardware.
Its not hard but, take care! Its your phone, your choice.
View attachment 1907737

[Q] Bootloader Unlock Official 4.3 Question

Since we got the new official 4.3 update, that means we got a new bootloader with the update right? If so, does anyone know if anyone has tried to get this unlocked even though we had no success with 4.2.2? I don't know if I can help get it done or not cause I don't have much background with actually unlocking it but I'm willing to help if possible. :fingers-crossed: Might run into problems with KNOX though.. idk.

Samsung GS4 locked bootloader. HELP
xAjCx said:
Since we got the new official 4.3 update, that means we got a new bootloader with the update right? If so, does anyone know if anyone has tried to get this unlocked even though we had no success with 4.2.2? I don't know if I can help get it done or not cause I don't have much background with actually unlocking it but I'm willing to help if possible. :fingers-crossed: Might run into problems with KNOX though.. idk.
Click to expand...
Click to collapse
Hello,
I bought an unlocked Samsung S4 Active I537 from ATT, but I use it in Canada.
I have tried to use Goomanager, TWRP manager, safestrap, quickboot; but the phone goes back to the normal bootloader.
When I try to install a ROM from my SD card (by normal bootloader) it does not do anything at all; just stays on the same screen for a minute then reboots normally.
I am guessing the bootloader isnt unlocked.
What tips you got?
Thanks!

drakul123 said:
Hello,
I bought an unlocked Samsung S4 Active I537 from ATT, but I use it in Canada.
I have tried to use Goomanager, TWRP manager, safestrap, quickboot; but the phone goes back to the normal bootloader.
When I try to install a ROM from my SD card (by normal bootloader) it does not do anything at all; just stays on the same screen for a minute then reboots normally.
I am guessing the bootloader isnt unlocked.
What tips you got?
Thanks!
Click to expand...
Click to collapse
The bootloader is still locked and currently there's nothing you can do about it. If you want to follow the progress read through this thread.

I learned that the hard way
Devo7v said:
The bootloader is still locked and currently there's nothing you can do about it. If you want to follow the progress read through this thread.
Click to expand...
Click to collapse
In advance: sorry to sound bitter; but wasn't fun how useless can be a device with a locked bootloader.
So the google apps stopped working and the whole thing is pretty much gone to hell/
IF samsung hadnt locked it so good (in a non-compliment kind of way) I could just install a new ROM and done, even better than with their weird touch wiz. But they locked it well so the phone is pretty much an average control remote in present time.
All samsung devices are locked like this one?
or that's their only garbage version ?
If that's the way they roll... no more Samsung phones ever for me.
There is a reason I stopped buying apple stuff... I dont like buying a device that is limited not because of its hardware, but because of the useless things a brand adds to make it useless. (like locking the bootloader)
Anyways... I am considering buying another phone for now.:silly:

drakul123 said:
In advance: sorry to sound bitter; but wasn't fun how useless can be a device with a locked bootloader.
So the google apps stopped working and the whole thing is pretty much gone to hell/
IF samsung hadnt locked it so good (in a non-compliment kind of way) I could just install a new ROM and done, even better than with their weird touch wiz. But they locked it well so the phone is pretty much an average control remote in present time.
All samsung devices are locked like this one?
or that's their only garbage version ?
If that's the way they roll... no more Samsung phones ever for me.
There is a reason I stopped buying apple stuff... I dont like buying a device that is limited not because of its hardware, but because of the useless things a brand adds to make it useless. (like locking the bootloader)
Anyways... I am considering buying another phone for now.:silly:
Click to expand...
Click to collapse
The device is far from useless, you can still root and flash custom ROMs, just not CM or AOSP based ROMs. I've posted all the stock ROMs and instructions on how to flash them, so if you do mess up your phone you can always start from scratch.
To answer your question about all Samsung phones, pretty much all Samsung phones from the GS3 an later that were sold by AT&T and Verizon have locked bootloaders. Nearly all the international versions as well as T-Mobile versions are sold with an unlocked bootloader, so you don't necessarily need to boycott Samsung, you just need to be more careful when purchasing a Samsung phone in the future.

Devo7v said:
The device is far from useless, you can still root and flash custom ROMs, just not CM or AOSP based ROMs. I've posted all the stock ROMs and instructions on how to flash them, so if you do mess up your phone you can always start from scratch.
To answer your question about all Samsung phones, pretty much all Samsung phones from the GS3 an later that were sold by AT&T and Verizon have locked bootloaders. Nearly all the international versions as well as T-Mobile versions are sold with an unlocked bootloader, so you don't necessarily need to boycott Samsung, you just need to be more careful when purchasing a Samsung phone in the future.
Click to expand...
Click to collapse
Hey there
Where did you post these ways of re installing all?
I saw many posts around here about reinstalling but I couldnt move on after they required the Samsung to do something through the bootloader.
Also there was a post to uninstall using Odin, but the post had missing files so couldnt do it.
Keep me posted!

drakul123 said:
Hey there
Where did you post these ways of re installing all?
I saw many posts around here about reinstalling but I couldnt move on after they required the Samsung to do something through the bootloader.
Also there was a post to uninstall using Odin, but the post had missing files so couldnt do it.
Keep me posted!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2835481

Strange issue.

Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.

H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
You flashed Npreview radio on a marshmallow build?

Dead-neM said:
You flashed Npreview radio on a marshmallow build?
Click to expand...
Click to collapse
Yes! Yes I did. Could this be an issue?

H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
im going to guess, try a different kernel. as its the kernel that will boot up the device?

H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)

Dead-neM said:
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Click to expand...
Click to collapse
the N radio, is the same exact radio that google released for the may security patch. so the N radio, is the latest official radio for the nexus 6. so no, that wont be the problem.

simms22 said:
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
I wonder if it is. I'm using the newest Elite kernel for Marshmallow, it's always been my go to kernel. It's strange because after turning the device off, I can't turn it back on instantly, screen stays black as if it's not 100% shut down yet. I have to wait a bit before turning it back on, or entering the bootloader.

simms22 said:
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.

Yoinx said:
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Click to expand...
Click to collapse
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?

Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.

Yoinx said:
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Click to expand...
Click to collapse
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.

Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
I flash each partition manually.

H4X0R46 said:
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Click to expand...
Click to collapse
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.

Yoinx said:
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Click to expand...
Click to collapse
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe

H4X0R46 said:
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
Click to expand...
Click to collapse
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).

Yoinx said:
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Click to expand...
Click to collapse
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol

H4X0R46 said:
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
Click to expand...
Click to collapse
Depends, I've never really looked into unbricking this phone. Never had to yet.
Depending on the phone you can use tools like QHUSB and similar which let you reflash partitions just through the USB connection.

I know it's late but it could also be just the rom setup. I know a while ago there were commits that shut the device screen and buttons off before it was done shutting down (to make it appear faster) this made devices seem bricked for a short period. I don't know what ever happen to those commits, so I can't say for sure that it is them. But your issue fits perfectly.

So have I been flashing the bootloader wrong all along? I flashed in twrp a couple times but I try to flash them individually and wipe after flashing.
Sent from my Nexus 6 using XDA-Developers mobile app

Anybody able to find out why? I'm surprised to see I'm not the only one having this issue, it's annoying really.

[Question] S6 Flat SM-G920T 6.0.1 Rooting

Hello Everyone!
Quick (stupid) question. How would one root the Samsung Galaxy S6 (Flat, T-Mobile Variant) running Android 6.0.1 (Stock)? Last night (As of this post) I've tried installing TWRP but ended in a bootloop at the Samsung logo, and (Thankfully) Smart Switch saved my ass. At this point, tripping KNOX isn't of my concern, as my phone's warranty has expired. Attached is my phone's Model, Build, etc.
Any help is appreciated.
-Matt

Use CF-Auto-Root.

EncryptedCurse said:
Use CF-Auto-Root.
Click to expand...
Click to collapse
Looking through all the builds, I don't see my build number. The closest one to mine (which is MMB29K.G920TUVU4EPF1), is MMB29K.G920TUVU3EPD1. Now, I would use this, but I don't want a 600$ brick, so unless it's compatible with my build, I'm gonna have to wait.

msoza1 said:
Looking through all the builds, I don't see my build number. The closest one to mine (which is MMB29K.G920TUVU4EPF1), is MMB29K.G920TUVU3EPD1. Now, I would use this, but I don't want a 600$ brick, so unless it's compatible with my build, I'm gonna have to wait.
Click to expand...
Click to collapse
Ah, yeah, looks like you're running the latest update and it seems to early to tell if CF-Auto-Root will even work on it (I don't think anyone has tried yet).
Anyways, here's all the information you'll need: http://forum.xda-developers.com/showpost.php?p=67623487&postcount=7
Rest assured that you can't brick anything as long as you have access to download mode to reflash stock firmware.

EncryptedCurse said:
Ah, yeah, looks like you're running the latest update and it seems to early to tell if CF-Auto-Root will even work on it (I don't think anyone has tried yet).
Anyways, here's all the information you'll need: http://forum.xda-developers.com/showpost.php?p=67623487&postcount=7
Rest assured that you can't brick anything as long as you have access to download mode to reflash stock firmware.
Click to expand...
Click to collapse
Thanks for the reply. Hmm...last time I flashed TWRP on my phone, It got stuck on the "Samsung Galaxy" logo, stayed there no matter what, thankfully I was able to use "Emergency Firmware Reset." I've been snooping around forms, and some people state to, "UNCHECK AUTO REBOOT, when finished installing, reboot manually." Of course, I'm hesitant to try that, after all Smart Switch only backs up photos, videos, apps, etc, but not the actual Android operating system.

I'm gonna do a back up of what I can and try EncryptedCurse's suggestion. Wish me luck!

EncryptedCurse said:
Ah, yeah, looks like you're running the latest update and it seems to early to tell if CF-Auto-Root will even work on it (I don't think anyone has tried yet).
Anyways, here's all the information you'll need: http://forum.xda-developers.com/showpost.php?p=67623487&postcount=7
Rest assured that you can't brick anything as long as you have access to download mode to reflash stock firmware.
Click to expand...
Click to collapse
Did as instructed, still didn't work, freezes and shuts down at the Samsung Logo. Doing a Emergency Device Initialization now, and then restoring my stuff. Thanks anyway, I knew I shouldn't have updated to 6.0... :sigh:

So im guessing theres no way to root it yet huh?

faratl said:
So im guessing theres no way to root it yet huh?
Click to expand...
Click to collapse
From what I've tried, no. I had a feeling this would happen as soon as I upgraded.

On a side note, is anyone developing a kernel for build MMB29K.G920TUVU4EPF1? Twisted Six's kernel only goes up to EPD1...

What if you just downgrade back to lolipop ??

faratl said:
What if you just downgrade back to lolipop ??
Click to expand...
Click to collapse
The latest update expressly prevents downgrading.

Bricked NO bootloader mode or recovery..Black screen!

So I messed up...Was trying to root and got stuck in a bootloop after flashing MAGISK, so I tried to just reflash the stock image...
I flashed successfully and got out of the bootloop but my wifi stopped working, so I rebooted and tried to reflash with the Pie image instead of oreo. For some reason I was getting errors so I got this bright idea to run the commands one by one in the Flash-All.bat.
But I still kept getting errors so I thought id reboot the bootloader and try again...thats where everything went south..Screen went black cant get to fastboot mode cant get to recovey..Pc recogizes the phone as "Qualcomm HS-USB QDLoader 9008" Bashing my head finding old LG threads that cant work for the razer, I dont know what to do...Any suggestions? Or am i just completely screwed.

Bad news I'm afraid but that's a hard brick you've got there there's nothing you can do to fix that afaik.

Mate, try this link? I googled around for you and this came up. Worth a shot -- best case it fixes it, worst case you're back to square one.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868

w00tnezz said:
Mate, try this link? I googled around for you and this came up. Worth a shot -- best case it fixes it, worst case you're back to square one.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
Click to expand...
Click to collapse
I saw that link on my hunt but I can't use it because the files provided are specific to LG L70 devices, the Razer doesn't use TOT files for firmware they use I'm going file's and the software he provided (which I tried) can only flash tot files.
Thank you though!

Rox598 said:
Bad news I'm afraid but that's a hard brick you've got there there's nothing you can do to fix that afaik.
Click to expand...
Click to collapse
Yeah that's what I was afraid of. Well luckily I am able to get it replaced... maybe not the most honest way but I only had it for a day so I went to where I bought it and told them it stopped working and they are sending me a replacement. Since it doesn't actually turn on they can't see that I unlocked the bootloader.... however...I'm still gonna try to root it I'll be more careful but I need root! I've been rooted since way back in Evo4g and Galaxy S1 days I use allot of root features I just can't give up..it's why I dropped Samsungs and went to Razer since Samsung started locking bootloader's... anyway hope it goes better the second time around lol

majicmazo said:
Yeah that's what I was afraid of. Well luckily I am able to get it replaced... maybe not the most honest way but I only had it for a day so I went to where I bought it and told them it stopped working and they are sending me a replacement. Since it doesn't actually turn on they can't see that I unlocked the bootloader.... however...I'm still gonna try to root it I'll be more careful but I need root! I've been rooted since way back in Evo4g and Galaxy S1 days I use allot of root features I just can't give up..it's why I dropped Samsungs and went to Razer since Samsung started locking bootloader's... anyway hope it goes better the second time around lol
Click to expand...
Click to collapse
I'm glad you're getting it replaced! May I ask what factory image did you try to flash onto the device? Pie MR0 or MR1?

Rox598 said:
I'm glad you're getting it replaced! May I ask what factory image did you try to flash onto the device? Pie MR0 or MR1?
Click to expand...
Click to collapse
It was MR1 from March 2019 the 9.0 one.

Just an update got my replacement and rooted it! I didnt bother with the TWRP method I just patched my boot image with Magisk and BAM! anyway now im happy time to transfer over my old phone stuff and im good!

majicmazo said:
I use allot of root features I just can't give up
Click to expand...
Click to collapse
With the lack of Custom ROMs what root features are you looking for exactly?
I just ordered mine today and like you I've rooted all my past phones except my current LG G6 (which can't be hence my upgrade)
The only thing I usually really need root access for is the free tethering without AT&T knowing and I was able to do that to the G6 without root.
Not trying to be mean or anything I'm just curious.

Nitrous729 said:
With the lack of Custom ROMs what root features are you looking for exactly?
I just ordered mine today and like you I've rooted all my past phones except my current LG G6 (which can't be hence my upgrade)
The only thing I usually really need root access for is the free tethering without AT&T knowing and I was able to do that to the G6 without root.
Not trying to be mean or anything I'm just curious.
Click to expand...
Click to collapse
Block ads.
Overclock for speed
underclock for battery.
Remove bloatware
Change boot animations
Thats just some of many more...
A whole world of possibilities woth root beyond tetheting and roms.
Sorry for the months later answer i just saw this.
Btw i got this thing replaced and rooted the second time around just fine im very happy now