can US variant of s9+ be rooted - Samsung Galaxy S9+ Questions & Answers

As far as I have read somewhere, the US version, Snapdragon I believe, can NOT be rooted.
Is that still true?
EDIT: I think that I found 1 answer
https://forum.xda-developers.com/galaxy-s9-plus/help/guides-request-unlocked-tmo-s9-plus-t3936676

People have asked this question a lot already (and it's been answered a lot as well).
Answer is no it can not be as of now.
Who knows what the future holds, but I wouldn't be anxiously waiting either. Way it sounds they have the phone locked down good.

Does flashing a custom rom bypass frp lock

JimmyTatz said:
Does flashing a custom rom bypass frp lock
Click to expand...
Click to collapse
Just enter the google account info last used and perform a factory data reset. This will properly deactivate the FRP lock.
The FRP lock is an anti-theft measure put in place by Google. Since discussions on how to carrier unlock financed phones isn't allowed, then it is reasonable to see how discussions over bypassing an anti-theft measure would also not be allowed.

How can a custom rom be loaded if the phone can't be rooted? I'm confused. Or was he referring to a non-us variant?

nabril15 said:
How can a custom rom be loaded if the phone can't be rooted? I'm confused. Or was he referring to a non-us variant?
Click to expand...
Click to collapse
Your confusion is understandable.. Especially when someone tries to hijack a thread for a totally unrelated and different subject.
The US variant can not be rooted so it must be a non-us variant.

Related

[Q] What should I do with my phone? (rooting, unlocking, ROMs, etc)

Hi Everyone!
Just want to start off by saying I’m new to the Atrix, but not new to the forums or android itself. I’ve rooted and flashed ROMs and kernels on other devices for myself and others, but the Atrix seems different from all those, so I have a few questions that I couldn’t find definitive answers to (and yes, I know where the search button is).
First off “unlocking” the phone seems to be more of a risk than I am willing to take, considering I’m doing this for a friend.
So I realize I won’t be a able to flash custom ROM’s, but what can I do after rooting?
Can I even get CWM?
Can I flash a kernel that lets me overclock?
Can I do OTA updates? (I hear ICS is coming to the Atrix soon, which is why I’m not worried about custom ROMs at the moment)
Once I OTA update to gingerbread will I be able to unlock the phone down the line?
Also what are some other things you guys say are a "must do" for this phone?
I know I’m asking a lot of questions, but any help would be greatly appreciated (and yes, I know where the thanks button is too)
You can unlock up to and including GB 2.3.6. How do I know cuz I did it myself.
Second you are very limited on what you can do until you do in fact unlock your bootloader. CWM can only be installed after your BL is unlocked.
Finally there's a few YouTube videos that show you step-by-step instructions on how to do this (even on GB) so it's really not that bad. Just watch them a couple of times, go slow, and most of all make sure your phones battery is charged. In the end once you unlock, you'll be glad you did...
Sent from my GT-I9100 using xda premium
Thanks for your answer, you've convince me to unlock it, but I have one more question.
Since my friend bought the phone new off amazon very recently is there a chance that unlocking the bootloader will be blocked, which I've seen other users saying.
kingv10 said:
Thanks for your answer, you've convince me to unlock it, but I have one more question.
Since my friend bought the phone new off amazon very recently is there a chance that unlocking the bootloader will be blocked, which I've seen other users saying.
Click to expand...
Click to collapse
No, use the following link to unlock the bootloader.
http://forum.xda-developers.com/sho...r UNLOCK/ROOT for AT&T 1.26/1.57/1.83/4.5.91 [UPDATE%2007/31/11]
Follow everything the command say. Make sure at no point do you take the cable out, if you are asked at any point to select a command on the phone but it does not let you just carry on with the process. It worked for me. Mine was locked to Gingerbread 2.3.6 build 4.5.141
anaschillin said:
No, use the following link to unlock the bootloader.
http://forum.xda-developers.com/sho...r UNLOCK/ROOT for AT&T 1.26/1.57/1.83/4.5.91 [UPDATE%2007/31/11]
Follow everything the command say. Make sure at no point do you take the cable out, if you are asked at any point to select a command on the phone but it does not let you just carry on with the process. It worked for me. Mine was locked to Gingerbread 2.3.6 build 4.5.141
Click to expand...
Click to collapse
+1 on unlocking usa att 2.3.6 4.5.141 with that program
MB860, CM7.2.0, Faux 026b1 1Ghz
One thing to consider though is that you´ll probably void the warranty. That would be the case in Brazil. IMHO, the benefits of rooting/unlocking far outweighs the loss of warranty. I would only let my friend know that even though it doesn´t happen very often, things can go wrong and you cannot be held responsible for any demage...just like we see in each every custom ROM disclaimer.

[Q]at&t unocked vs international factory unlocked

I want to buy one m8. what is the difference between at&t factory unlocked and international factory unlocked version. can i flash roms in international version thread on at&t factory unlocked model directly??
Yes you can flash any rom you want from the international thread. I am currently running Android Revolution.
Sent from my unknown using XDA Premium 4 mobile app
The 3G and LTE band compatibility is different. Do you intend to use on the AT&T network? If so, the "international" (EMEA) version is compatible with AT&T's 3G bands (850 and 1900 MHz); but lacks both of the LTE bands used by AT&T (700 and 1700 MHz) according to this: http://www.gsmarena.com/htc_one_(m8)-6074.php
Not band compatibility is set in hardware, and cannot be changed by flashing different software (ROM, radio, etc.). This means the EMEA version cannot be used on AT&T's LTE network, not matter what you do.
If using on a carrier besides AT&T, I'd check the band compatibility with what your carrier uses. Even if the AT&T version is compatible (with you carrier), I'd probably recommend the international version over it (if compatible as well). The AT&T version is loaded with crappy AT&T bloat and limitations. For instance, WiFi hotspot is blocked, so bootloader needs to be unlocked and the phone rooted in order to make it work on other networks.
Plus, there is the ugly AT&T logo on the back.
Just thought i would bump this thread instead of making a new one. I bought an unlocked at&t htc one m8 off of ebay that i plan to use in another country (i study abroad). I already checked that the frequency bands are compatible, etc. Here's the thing, i don't want my phone to have anything to do with at&t other than the logo in the back. In other words, i want to make it as similar as posible (if not exactly the same) to the international unlocked version. Is this possible with just software changes, etc? (i've read the phones are the same in terms of hardware). I want to remove all at&t bloatware and limitations. can someone please give me quick explanations of what i need to do or point me in the right direction? I'm not new to xda or rooting, but the only smartphone i've ever had is a samsung vibrant (which i've rooted and flashed roms countless times).. this is my first htc phone, so im not very familiar with htcdev or s-off.. but i learn quickly.
I would really appreciate some help
Maelstrom08 said:
Just thought i would bump this thread instead of making a new one. I bought an unlocked at&t htc one m8 off of ebay that i plan to use in another country (i study abroad). I already checked that the frequency bands are compatible, etc. Here's the thing, i don't want my phone to have anything to do with at&t other than the logo in the back. In other words, i want to make it as similar as posible (if not exactly the same) to the international unlocked version. Is this possible with just software changes, etc? (i've read the phones are the same in terms of hardware). I want to remove all at&t bloatware and limitations. can someone please give me quick explanations of what i need to do or point me in the right direction? I'm not new to xda or rooting, but the only smartphone i've ever had is a samsung vibrant (which i've rooted and flashed roms countless times).. this is my first htc phone, so im not very familiar with htcdev or s-off.. but i learn quickly.
I would really appreciate some help
Click to expand...
Click to collapse
Then I suggest you start reading...
http://forum.xda-developers.com/htc-one-m8?nocache=1
Look in there and
https://www.youtube.com/results?search_query=htc+one+m8+root
I have the ViperOneM8 rom installed. What is even cool is in the tweeks, you can change the AT&T bootup and logoff screen to a viperone screen. And change the AT&T logo in the pull down menu to any picture you want. s-off isn't really needed unless you plan on changing the kernel.
Maelstrom08 said:
Just thought i would bump this thread instead of making a new one. I bought an unlocked at&t htc one m8 off of ebay that i plan to use in another country (i study abroad). I already checked that the frequency bands are compatible, etc. Here's the thing, i don't want my phone to have anything to do with at&t other than the logo in the back. In other words, i want to make it as similar as posible (if not exactly the same) to the international unlocked version. Is this possible with just software changes, etc? (i've read the phones are the same in terms of hardware). I want to remove all at&t bloatware and limitations. can someone please give me quick explanations of what i need to do or point me in the right direction? I'm not new to xda or rooting, but the only smartphone i've ever had is a samsung vibrant (which i've rooted and flashed roms countless times).. this is my first htc phone, so im not very familiar with htcdev or s-off.. but i learn quickly.
Click to expand...
Click to collapse
What you describe is easy to do by just unlocking the bootloader, installing custom recovery, and flashing any international based stock rooted ROM or custom ROM. I basically have done the same, as even though AT&T is my carrier, I absolutely hate their branding, non-standard signal icons, bloatware, and limitations (particularly Wifi Hotspot/tethering).
As the previous user already suggested, learning and reading is the best thing for you to do. Don't proceed until you have a good understanding of the concepts and process. My Index thread (specific to the AT&T versions) is a good place to start up reading: http://forum.xda-developers.com/showthread.php?t=2751432
Great, thanks for the information and guidance guys. i'll definitely spend the next couple days reading before rooting the device, i can't afford to brick it. Any other tips or advices as to how to go about rooting, etc?
Developer build device and ATT device are same exact hardware, ONLY difference is ones sim locked and other isnt, bought 2 developer device from [email protected]'s both run fine on ATT networks...
Maelstrom08 said:
Great, thanks for the information and guidance guys. i'll definitely spend the next couple days reading before rooting the device, i can't afford to brick it. Any other tips or advices as to how to go about rooting, etc?
Click to expand...
Click to collapse
no additional advice. I think red point has a wonderful index that should work well for you.
I just wanted to tell you what a wonderfully refreshing attitude you have . Feel free to PM me anytime if you have any specific questions.
Maelstrom08 said:
Any other tips or advices as to how to go about rooting, etc?
Click to expand...
Click to collapse
If you look at my Index thread I linked above, the first item under "Unlock Bootloader, ROOT, S-Off" is an excellent step-by-step guide to rooting. There really isn't much I can't add, the guide is so thorough. But I'd still advise to read around and make sure you fully understand all the concepts and steps, and not just blindly follow the guide.
If the goal is to install a custom ROM, you can stop before the step in guide where it says to flash SuperSU (after flashing TWRP), and just put a ROM on the phone and flash in recovery similar to how you have done in the past. The guide is written with the intent of staying on the stock ROM and rooting.
One tip I can give, is that you may notice there are some Toolkits that attempt to automate some of the process (bootloader unlock, custom recovery, root, etc.). I would actually recommend avoiding the use of these. Reason being, the steps aren't actually all that hard to do "manually", plus these toolkits (while well meaning) shortcut the learning process, and rob you of a valuable learning opportunity.
I'm assuming OP doesn't want a custom ROM or root. Just to convert the AT&T branded model to a stock unlocked model, and still get OTA updates. This is possible. You need to unlock the bootloader, get S-OFF, and then follow this guide (you can skip step 1, changing MID): http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
mindmajick said:
no additional advice. I think red point has a wonderful index that should work well for you.
I just wanted to tell you what a wonderfully refreshing attitude you have . Feel free to PM me anytime if you have any specific questions.
Click to expand...
Click to collapse
Thanks a lot man, you seem to have a really nice personality yourself as well. I'll definitely take you up on that offer when I get a chance.
redpoint73 said:
If you look at my Index thread I linked above, the first item under "Unlock Bootloader, ROOT, S-Off" is an excellent step-by-step guide to rooting. There really isn't much I can't add, the guide is so thorough. But I'd still advise to read around and make sure you fully understand all the concepts and steps, and not just blindly follow the guide.
If the goal is to install a custom ROM, you can stop before the step in guide where it says to flash SuperSU (after flashing TWRP), and just put a ROM on the phone and flash in recovery similar to how you have done in the past. The guide is written with the intent of staying on the stock ROM and rooting.
One tip I can give, is that you may notice there are some Toolkits that attempt to automate some of the process (bootloader unlock, custom recovery, root, etc.). I would actually recommend avoiding the use of these. Reason being, the steps aren't actually all that hard to do "manually", plus these toolkits (while well meaning) shortcut the learning process, and rob you of a valuable learning opportunity.
Click to expand...
Click to collapse
Yeah, I plan on doing it manually. Thanks for all the good advise man. I'm liking what I see in these forums, I'm glad I landed here.
Sorry it took me this long to reply guys, I have been very busy in the past week. Time to learn me some HTC one m8.
Sent from my HTC One_M8 using XDA Free mobile app
One last question guys, hopefully somebody can answer me. I've already read a few topics on the terminology used (s-off, ruu, htcdev, etc.), and things don't seem to be too far from what i thought they were. I'm ready to root and flash a custom rom, but here's my question:
I'm a very methodical person, i like to know what I'm doing and that it's the right way to do it. When i flashed a new rom (or rom version) on my samsung vibrant i would do a full wipe (factory reset, clear chache, clear dalvik cache, format system, and format data) before flashing, then i would flash the rom, and then i would flash the rom on top of itself without doing a full wipe. This method worked for me for over 3 years and kept me from getting common bugs some people complained about. Is it fine if i do this with my m8? (i mainly want to know if it can cause problems).. What's your common flash routine?
Thanks for the help guys
I am simple, I do what you do except the double flash.
Sent from my HTC One_M8 using Tapatalk
Maelstrom08 said:
I'm a very methodical person, i like to know what I'm doing and that it's the right way to do it. When i flashed a new rom (or rom version) on my samsung vibrant i would do a full wipe (factory reset, clear chache, clear dalvik cache, format system, and format data) before flashing, then i would flash the rom, and then i would flash the rom on top of itself without doing a full wipe. This method worked for me for over 3 years and kept me from getting common bugs some people complained about. Is it fine if i do this with my m8? (i mainly want to know if it can cause problems).. What's your common flash routine?
Click to expand...
Click to collapse
What you've stated is fine. Although factory reset already wipes data, cache and Dalvik, so its a bit redundant.
I'm the opposite of methodical (at least in the way you describe). I like to get things done with as few steps as possible (while still doing it right). I've similarly been flashing ROMs on Android devices for 4 years (4 HTC devices and 2 Samsung). But I hardly ever wipe system (flashing a ROM does that by default) and never double flash, and I've never had any issues I would attribute to flashing methods.
Some folks will swear by wiping system for every ROM flash, but honestly while there is nothing wrong with it, I don't believe in it and almost never do it (unless sometimes where the ROM specifically says to do so in the instructions).
On the other hand, there is nothing wrong with redundancy, and if you like to be methodical and thorough I would say just keep doing what you have been doing.
Hi there,
i hope that i will get better answer here.
My question is that i have m8 cell htc, but the problem is i dont know how to check what software was intalled in it at beginnig, i installed at&t marshmallow but want to know weather it was of at&t of international and device does not have any icon on the back of the device. thanks
bilalkamal said:
Hi there,
i hope that i will get better answer here.
My question is that i have m8 cell htc, but the problem is i dont know how to check what software was intalled in it at beginnig, i installed at&t marshmallow but want to know weather it was of at&t of international and device does not have any icon on the back of the device. thanks
Click to expand...
Click to collapse
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) and if we look at that info, we can probably determine what version it is.

[Q&A] [ROM][Galaxy Light T399][ANG6] LightWave V3[Fast]

Q&A for [ROM][Galaxy Light T399][ANG6] LightWave V3[Fast]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Will this custom ROM unlock the phone?
I have bought this phone from T-Mobile, but chose the wrong option when buying (not the unlocked one) and now the only way I could find to unlock the phone would be paying for the network unlock code (around $30).
Would anyone know if by flashing this ROM it will unlock the phone to use another carrier's SIM card?
Any other option on how to unlock the phone using another method would also be greatly appreciated.
No, the custom ROM will not unlock the phone
Spuqui said:
I have bought this phone from T-Mobile, but chose the wrong option when buying (not the unlocked one) and now the only way I could find to unlock the phone would be paying for the network unlock code (around $30).
Would anyone know if by flashing this ROM it will unlock the phone to use another carrier's SIM card?
Any other option on how to unlock the phone using another method would also be greatly appreciated.
Click to expand...
Click to collapse
Already found the answer to my own question. I flashed the custom ROM to the locked phone and tried to place a SIM card in it, but still get the Invalid SIM card message and it requests the network unlock code.
I can also say that kitkat metropcs twrp backup works on the Univision variant and it works with a sim card from another country, thanks!!
EDIT: This ROM won't unlock your phone, this is another part of the device that is not dependant on the rom, to unlock you'll need an unlocking box like z3x, or pay for an imei unlock code, mine could be unlocked with 13 dlls from unlockscout, samsungs made in china.
What is the version 4.4 or 4.2?
Dogg_mc said:
What is the version 4.4 or 4.2?
Click to expand...
Click to collapse
4.4.2
Phone is now unlocked and updated to Kit Kat
Indeed, the part of the phone responsible for the network lock is not messed with by the custom ROM or the update to Kit Kat method, but I actually found a way to unlock without a z3x box or having to buy the unlock code online.
The phone I was trying to unlock is a friend's phone, but I have my own phone and it was bought already unlocked, and is the same model. The trick here was to find out that the network code lock was part of the EFS partition. I made a full backup of my phone (unlocked) through TWRP and restored it in my friend's phone. It did unlock. Then it was just a matter of resetting to factory defaults and performing the procedure to update to Kit Kat and it now is unlocked and updated. \o/
Spuqui said:
Indeed, the part of the phone responsible for the network lock is not messed with by the custom ROM or the update to Kit Kat method, but I actually found a way to unlock without a z3x box or having to buy the unlock code online.
The phone I was trying to unlock is a friend's phone, but I have my own phone and it was bought already unlocked, and is the same model. The trick here was to find out that the network code lock was part of the EFS partition. I made a full backup of my phone (unlocked) through TWRP and restored it in my friend's phone. It did unlock. Then it was just a matter of resetting to factory defaults and performing the procedure to update to Kit Kat and it now is unlocked and updated. \o/
Click to expand...
Click to collapse
Heres my question, if the phone is from tmobile how did you get kitkat? Unless you did it with the METRO backup
cm version
Thanks. Looking forward for that CM ROM.
One potentially noob question: cm11 is based on 4.4 while this device is officially still 4.2.2. Would that be OK?
Yes thats why people started making xustom roms
tazmaniondvl said:
Heres my question, if the phone is from tmobile how did you get kitkat? Unless you did it with the METRO backup
Click to expand...
Click to collapse
I read somewhere that someone was trying to download KK update from T-Mobile this could be just a 4.2 update or they could be pushing it. Maybe new lights are shipping with KK as well who knows
---------- Post added at 06:44 AM ---------- Previous post was at 06:41 AM ----------
mehmetneset said:
Thanks. Looking forward for that CM ROM.
One potentially noob question: cm11 is based on 4.4 while this device is officially still 4.2.2. Would that be OK?
Click to expand...
Click to collapse
There are many phones who are stuck on outdated firmware. Gnex, nexus s, htc mytouch 4g/slide all running kit Kat. Many many more examples. The Roms may not be stable due to various reasons (no source, outdated hardware, lack of Dev etc) it is possible
Is there a test that will show if a phone is locked or not. I hosed my efs partition a while back and had to format it, change permissions, and reset to factory default to get my Galaxy Light to boot. Does that mean that my phone is unlocked?
tazmaniondvl said:
Heres my question, if the phone is from tmobile how did you get kitkat? Unless you did it with the METRO backup
Click to expand...
Click to collapse
Yes, I did it with the MetroPCS backup. Tried to flash the kernel of KitKat straight from the T-Mobile system on 4.2.2 but it did not work.
mehmetneset said:
Thanks. Looking forward for that CM ROM.
One potentially noob question: cm11 is based on 4.4 while this device is officially still 4.2.2. Would that be OK?
Click to expand...
Click to collapse
The work I'm doing is based on the metro PCs released kernel source and device files which are 4.4. They have the same everything just different bloat from carrier.
GJSmith3rd said:
Is there a test that will show if a phone is locked or not. I hosed my efs partition a while back and had to format it, change permissions, and reset to factory default to get my Galaxy Light to boot. Does that mean that my phone is unlocked?
Click to expand...
Click to collapse
I believe you are looking for an app that is able to test if the phone is network locked or not. I do not know of such an app. The basic test you can do is try to insert a SIM card from another operator and see if it allows it or displays the message of it being an invalid SIM, asking for the network unlock code. And you don't need to buy another SIM, just borrow a friend's, it will only take a minute...
Thanks, that's my little problem in that I don't have access to a micro or mini SIM like the one in this device.
Anyone know where the boot animation is? Or how to change it?
tazmaniondvl said:
Anyone know where the boot animation is? Or how to change it?
Click to expand...
Click to collapse
Here's a thread about it http://forum.xda-developers.com/showthread.php?t=2611682
Greetings XDA Zombies!
Got the T399NUVUANH1 working on my T-Mobile T399. Having issues getting ViPER4Android FX drivers to work. Have BusyBox Pro and seems that it wont install property. The ViPER4 2.3 version says the drivers are installed but actually not working, and the ViPER4 4.x version I keep getting the drivers failed.
Appreciate any help.
Footnote: X Tether works!
Bummer. Think TMO watching XDA and clamping down on whatever loose ends they can bind.
Metropcs GL
Will this work on a galaxy light with Android 4.4.3? Does the build have to be the same?

[Q] Questions about T-Mobile and MetroPCS Galaxy S5

Hello everyone,
Let me preface this by saying that I have googled this extensively and used the search feature on XDA but so far I have come up with no clear results. Apologize if this has been asked before (it probably has). I hope you guys can help me by providing me with some definite answers.
Background:
I've been researching about getting Lollipop on my device (I had it on my rooted sprint s4 and I miss it dearly). I've heard that the MetroPCS S5 is the exact phone as the T-Mobile S5. Unfortunately, I haven't been able to confirm whether that's the case or not. I have a MetroPCS S5 (SM-G900T1), and I would greatly appreciate it if you guys took the time to answer these questions for me:
1) Are they really the same phone?
AFTER SIM-UNLOCKING THE PHONE
2) Can I put T-Mobile S5 custom recoveries on the Metro Version?
3) Can I put T-Mobile S5 custom ROMs on the Metro version?
If the answers to question 2 and 3 is "NO" then where can I find a place where people are developing for the MetroPCS S5 or that place doesn't exist?
Thank you all for reading and for any help.
1) They are mostly the same as they do use the same network.
2) Any KLTE recovery will work.
3) Any KLTE rom SHOULD work, check the OP of the roms developer. Any KLTE AOSP rom will work.
Here is a site showing the recoveries are the same. -->HERE<--
Brian_svc said:
Hello everyone,
Let me preface this by saying that I have googled this extensively and used the search feature on XDA but so far I have come up with no clear results. Apologize if this has been asked before (it probably has). I hope you guys can help me by providing me with some definite answers.
Background:
I've been researching about getting Lollipop on my device (I had it on my rooted sprint s4 and I miss it dearly). I've heard that the MetroPCS S5 is the exact phone as the T-Mobile S5. Unfortunately, I haven't been able to confirm whether that's the case or not. I have a MetroPCS S5 (SM-G900T1), and I would greatly appreciate it if you guys took the time to answer these questions for me:
1) Are they really the same phone?
AFTER SIM-UNLOCKING THE PHONE
2) Can I put T-Mobile S5 custom recoveries on the Metro Version?
3) Can I put T-Mobile S5 custom ROMs on the Metro version?
If the answers to question 2 and 3 is "NO" then where can I find a place where people are developing for the MetroPCS S5 or that place doesn't exist?
Thank you all for reading and for any help.
Click to expand...
Click to collapse
You can actually flash the stock firmware and have the new modem and everything.(won't have metro bloat anymore but will have tmo which you can delete all that and grab metro bloat if you wanted it) But yes firmware, recoveries, roms, etc
esjames said:
1) They are mostly the same as they do use the same network.
2) Any KLTE recovery will work.
3) Any KLTE rom SHOULD work, check the OP of the roms developer. Any KLTE AOSP rom will work.
Here is a site showing the recoveries are the same. --><--
Click to expand...
Click to collapse
Thank you very much for your answer and your time.
ShinySide said:
You can actually flash the stock firmware and have the new modem and everything.(won't have metro bloat anymore but will have tmo which you can delete all that and grab metro bloat if you wanted it) But yes firmware, recoveries, roms, etc
Click to expand...
Click to collapse
Thank you for your reply. It's cool to hear everything is compatible although I'm still very nervous about trying it lol
Can you expect in the distant future a way to install a custom recovery without tripping the knox count (I believe that's what it's called)? As far as I know there's no way to reset that.
Brian_svc said:
Can you expect in the distant future a way to install a custom recovery without tripping the knox count (I believe that's what it's called)? As far as I know there's no way to reset that.
Click to expand...
Click to collapse
Doubtful that Knox will be figured out anytime in the near future. And you are correct, you cannot reset it once it's tripped.
But if you look around at the Knox threads, the vast majority of users that have tripped Knox have not had any problem getting service or warranty work. So for the most part it's a non issue.
Of course YMMV

MM Potential root?

Has anyone seen it have tried this?
(ScreenShot)
Glitch15 said:
Has anyone seen it have tried this?
(ScreenShot)
Click to expand...
Click to collapse
There is no root for 6.0 unless there is a bootloader unlock
If the method you see on srs is real im sure you see it here on xda that 6.0 is rootable
Untill then root is not possible on 6.0
If you are on 5.1 i do have a video that shows you how to root 5.1
LASERWOLF452 said:
There is no root for 6.0 unless there is a bootloader unlock
If the method you see on srs is real im sure you see it here on xda that 6.0 is rootable
Untill then root is not possible on 6.0
If you are on 5.1 i do have a video that shows you how to root 5.1
Click to expand...
Click to collapse
Why is this being said? 5.1.1 on Verizon V10 got rooted without bootloader unlock.
Not that I have anything to offer here for root but it kind of seems no one is trying. This Phone has horrible developer support. Idk why since this is such a great phone.
5.1.1 rooted without bootloader unlock. All the way up until root was achieved for 5.1.1 people kept saying bootloader must be unlocked, which obviously wasn't true.
While he claims to have it working, it is not tested on marshmallow LG Verizon phones.
Glitch15 said:
Has anyone seen it have tried this?
(ScreenShot)
Click to expand...
Click to collapse
ANTI VIRUS recognizes as a threat
beavis5706 said:
Why is this being said? 5.1.1 on Verizon V10 got rooted without bootloader unlock.
Not that I have anything to offer here for root but it kind of seems no one is trying. This Phone has horrible developer support. Idk why since this is such a great phone.
5.1.1 rooted without bootloader unlock. All the way up until root was achieved for 5.1.1 people kept saying bootloader must be unlocked, which obviously wasn't true.
Click to expand...
Click to collapse
if i was a dev i can tell you, but all the post that talks about root and questions about root, downgrades etc. i subscribed to the post, thats the answer i see, maybe someone can put it into detail for you
all i know is they need the bootloader to be unlocked so it can be modified, without the bootloader being unlocked and you just root the system, it will just fail and this is true ive tried it on my G4
i tried upgrading my g4 and it got ito a bootloop and when i KDZ it it knows its been modified and no one knows why fter doing a factory reset unless you KDZ it,
if you want a downgrad, that is not possable but there was talk about it in another post but no one had gotten around it for the V10 cause they work, have a life and family
someone may step up and do the work, its all a matter of time, it may take 2 years like i heard 1 device they want rooted took 2 years before it got root
hacking, modifying bricking and waiting to get a replacement takes time and money for the research to be done with the time the dev has
Well unless there is something specifically different about MM 6.0 unlocked bootloader not needed for root. Every VS990 owner with 5.1.1 already knows this.
The same was said about Lollipop 5.1.1 in the months prior to root, that unlocked bootloader was needed for root. This obviously was not true since 5.1.1 was rooted without bootloader unlock.
OEM unlock for VZW lg10 vs990 MMallow
I got my unlock OEM dev options marked... Its super simple.... Just saying... Message me if interested. I'm super excited to finally start the rooting process, my first time ever. Some help would be sees him shpanx
seems that all the "developers" have disappeared as of late. Havent seen one even make a comment now that rooting requires a bit more of a challenge.

Categories

Resources