[Q] From locked & stock to unlocked bootloader & custom rom - T-Mobile LG G4

Hi there everyone! I am absolutely 100% noob when it comes to LG. Always had an HTC phone but with the horrible reviews for the M9 I chose the G4. Its a great phone stock but the rooting itch has gotten to strong lol. Read plenty of threads and watched a few videos on how to root this beautiful phone. Yet, questions pop into my head...... I know most likely rule number one is to unlock the bootloader. For HTC I would then boot into Fastboot mode to flash TWRP with the famous command "fastboot flash recovery twrp.img" and then proceed to flash my favorite ROM that is pre-rooted. Would the steps be about the same? If not, what is different? Is there any way to hide root from the T-Mobile Account app that checks for root or should I just get rid of the app? Also, I am still on the 10H build. Should I update to 10N first or would I not be able to root? So sorry for the amount of questions presented here it is just that I'm afraid of bricking. Any help is appreciated.

Upgrade to 10N then follow the instructions here:
http://forum.xda-developers.com/tmobile-g4/development/h81110n-stock-rooted-image-t3191038
Make sure you set OEM bootloader unlocked as well in Developer options.
Then use flashify to install TWRP
I would install debloated ROM here but thats up to you: http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-rooted-rom-t3188858
xhunter187 said:
Hi there everyone! I am absolutely 100% noob when it comes to LG. Always had an HTC phone but with the horrible reviews for the M9 I chose the G4. Its a great phone stock but the rooting itch has gotten to strong lol. Read plenty of threads and watched a few videos on how to root this beautiful phone. Yet, questions pop into my head...... I know most likely rule number one is to unlock the bootloader. For HTC I would then boot into Fastboot mode to flash TWRP with the famous command "fastboot flash recovery twrp.img" and then proceed to flash my favorite ROM that is pre-rooted. Would the steps be about the same? If not, what is different? Is there any way to hide root from the T-Mobile Account app that checks for root or should I just get rid of the app? Also, I am still on the 10H build. Should I update to 10N first or would I not be able to root? So sorry for the amount of questions presented here it is just that I'm afraid of bricking. Any help is appreciated.
Click to expand...
Click to collapse

tk424 said:
Upgrade to 10N then follow the instructions here:
http://forum.xda-developers.com/tmobile-g4/development/h81110n-stock-rooted-image-t3191038
Make sure you set OEM bootloader unlocked as well in Developer options.
Then use flashify to install TWRP
I would install debloated ROM here but thats up to you: http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-rooted-rom-t3188858
Click to expand...
Click to collapse
Thanks for the help! Flashed your stock rooted image so I could Flashify TWRP. I have been a part of the HTC fan club since the Droid Incredible. All the way to the One Max and M8 while I was on Verizon. This LG stuff is all new to me lol.

Related

[QUESTION] Root FRF91 without touching boot loader

I know the update was a security fix but am looking for a method to root while remaining as completely stock as humanly possible. I've never rooted before and am still completely stock now.
Best case scenario would be to gain root while leaving everything stock, boot loader, recovery, etc.. maybe even try one of them nice roms for the first time (i hear cyrogen is the best and yes I probably misspelled that)
Thanks
Sent from my Nexus One using XDA App
Same question
There's a couple of tutorials about this in another thread.
If I were you i'd follow one of them and also install a custom recovery. Then play around all you like with rooted roms, stock, custom or otherwise. Once you have a custom recovery you can flash anything. The only down side is that you won't be able to install any OTA roms. But to be honest they appear on XDA in a format you can use on custom recovery way way before you ever receive an OTA notification anyway.
Then if you're sure you only want a stock but rooted rom, then install that and then finally flash the stock recovery back.
However if you're sure you don't want a custom recovery and only want root, you can follow the first half of the same tutorials.
I myself have an unlocked bootloader, but if I didnt, I would root, install a custom recovery and never look back. If anything ever happened to my device i'd just flash the stock recovery and stock firmware and send it back.
Ok, thanks!
That's good information but I'm unsure if I want to unlock at the moment. Thanks but I'll wait a little longer to see if a solution comes out that this my needs.
Sent from my Nexus One using XDA App
viper2g1 said:
That's good information but I'm unsure if I want to unlock at the moment. Thanks but I'll wait a little longer to see if a solution comes out that this my needs.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
No, thats the point. You dont need to unlock to root OR put a custom recovery anymore. See here for example:
http://forum.xda-developers.com/showthread.php?t=710842
So you can root, put on a custom recovery, try different roms and then go back to stock, rooted or not, without unlocking the bootloader at all.
I see what your getting at, that's what I was looking for but wasn't sure it was working for FRF91 the last few posts in that thread indicated an unlocked boot loader last time I looked.
I thought the update was to fix the security hole that allowed that
Sent from my Nexus One using XDA App
I have read a lot of comments on the guide of how root the nexus without unlocking the bootloader and searched in other places but couldn't find an answer to my question...
I've got at&t version nexus unrooted and I updated it to FRF91 OTA.
can I use this guide to root it without unlocking the bootloader?
If I can, how do I do it? some people wrote that I need to use Passimg.zip
but I think It's for T-mo version only because at&t's version doesn't have the erf79 (I hope I wrote it right).
anyway I'm really confused. can someone please explain?
thanks
I've got at&t version nexus unrooted and I updated it to FRF91 OTA.
can I use this guide to root it without unlocking the bootloader?
Click to expand...
Click to collapse
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
RashaMatt said:
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
Click to expand...
Click to collapse
they should work in the same way as it did for FRF83 or FRF85B.. you could always try without harm
RashaMatt said:
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
Click to expand...
Click to collapse
this link: forum.xda-developers.com/showthread.php?t=717870
is a guide of how to downgrade from FRF91 to FRF85 in an unrooted nexus.
that way you can use this tut and root it w/o touchnig the bootloader
EPE76 to frf85B
Hi,
I am back from frf91 ota to EPE76 by applaing passimg.zip. My question is how can I move to frf85B ? I've tried to download universal frf85B, change name to update.zip and go to recovery, but I only see exclemation mark. Please advise. Thank you.

[Q] OTA updates and root

So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.
At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535
Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G

[Q] XT1053 4.4.4 Root?

Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
You'll have to unlock the bootloader. No way around it.
Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?
Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.
I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app
Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.
4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?
Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)
Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.

[Q]Going from Safestrap/Kryptonite 4.4.2 rom to CM12?

I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
llsmith said:
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
Click to expand...
Click to collapse
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Travisdroidx2 said:
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Click to expand...
Click to collapse
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
llsmith said:
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
Click to expand...
Click to collapse
You should be familiar with flashing a custom recovery via adb if you have used TWRP on other devices. Once you have the bootloader unlocked you would need the correct recovery image of TWRP for the Moto X and then in bootloader mode use the command "fastboot flash recovery 'recovery.img'" where 'recovery.img' is the exact name of the file. If it flashed and it works properly then you could flash CM12 and Safestrap should be gone if you followed the flashing directions exactly. Don't forget to make a Nandroid of your current setup before you begin! Factory Resetting the device would be crucial if jumping from one ROM to another so it kind of takes care of itself.

New user d415

Hi guys I got this old lg d415 from my cousin and Wana install some roms on it since I'm a noob on this device I need some help regarding what to do unlock bootloader or what .... I see that d415 has a unlocked bootloader or no ?
Its bootloader is already unlocked just root and flash twrp. kingroot to root and flashify to flash the recovery seem easiest. *Just make sure to update to LP beforehand. here's a link for recovery. You may be able to get a more updated version of the recovery off the twrp site. Also I suggest using the most recent lineage build. lineage
teknoweanie said:
Its bootloader is already unlocked just root and flash twrp. kingroot to root and flashify to flash the recovery seem easiest. *Just make sure to update to LP beforehand. here's a link for recovery. You may be able to get a more updated version of the recovery off the twrp site. Also I suggest using the most recent lineage build. lineage
Click to expand...
Click to collapse
Ypu wrong you have to unlock before flashing unless you are planning on bricking your device. You first have to root it and then flash laf with zeros u lock bootlosder, flash recocery , thenflash rom
Please don't tell people stuff you don't know about. The T-Mobile variant comes with its bootloader already unlocked. Also there is no laf to mess with.
teknoweanie said:
Please don't tell people stuff you don't know about. The T-Mobile variant comes with its bootloader already unlocked. Also there is no laf to mess with.
Click to expand...
Click to collapse
Really? I have tmobile variant and i had to unlock bootloader. Look at this https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
Wow I guess you did a bunch of useless stuff that does not matter. About as useful as me putting in does not matter instead of doesn't. Read what googlephone says at the end of the thread at post #204..............yeah..
teknoweanie said:
Wow I guess you did a bunch of useless stuff that does not matter. About as useful as me putting in does not matter instead of doesn't. Read what googlephone says at the end of the thread at post #204..............yeah..
Click to expand...
Click to collapse
Ok, didnt know

Categories

Resources