Develop Bugs

Root method

I think i saw someone post this method before, but can't find it. So i post root method. Currently this method work on the latest Canadian OG firmware (Both E971 and E973). i did not make this method, i just find it from a chinese web. Here is the link
http://bbs.gfan.com/android-5698914-1-1.html
Here is the instruction.
1. Unzip the zip file
2. turn on usb debug and plug in the cable to pc
3. double click the root.bat
4. unplug the cable.
5. Turn off the usb debug
6. turn on the usb debug
7. plug in the cable.
8. Press enter until it root.
9. Done.

So this work for the E973 on latest stock firmware...? e973H ..?
Be careful, this root is for "[Tutorial] F180 the series 4.1Root method"
That's the title of the other forums.. So this might not WORK!

Yes I tried on my e973 and it work
Sent from my Nexus 7 using xda premium

I can confirm it works on my Rogers E971

it's great.it works indeed.
was repost before but renamed after ,you may find it on the thread finally!
credits:
[email protected]
[email protected]
Sent from my LG-F160L using xda premium

Opacac said:
I can confirm it works on my Rogers E971
Click to expand...
Click to collapse
Do you, or anyone, know if freegee will work on latest firmware if rooted using this method?
Thanks
Sent from my LG-E971 using Tapatalk 2

ATRIXXIRTA said:
Do you, or anyone, know if freegee will work on latest firmware if rooted using this method?
Thanks
Sent from my LG-E971 using Tapatalk 2
Click to expand...
Click to collapse
I just tried FreeGee and its a no go.

I want to root this thing soooo bad!! But I want to have a backup of the official JB update, and I don't want something to prevent me from installing it via OTA. I'm curious to see what lg will do with jb. I'm really liking the stock ICS experience on this phone, and I think they'll just kill it (in a good way) with jb!
Sent from my LG-E971 using Tapatalk 2

athris said:
I think i saw someone post this method before, but can't find it. So i post root method. Currently this method work on the latest Canadian OG firmware (Both E971 and E973). i did not make this method, i just find it from a chinese web. Here is the link
http://bbs.gfan.com/android-5698914-1-1.html
Here is the instruction.
1. Unzip the zip file
2. turn on usb debug and plug in the cable to pc
3. double click the root.bat
4. unplug the cable.
5. Turn off the usb debug
6. turn on the usb debug
7. plug in the cable.
8. Press enter until it root.
9. Done.
Click to expand...
Click to collapse
I really would have posted this much sooner, however, this particular method was being kept secret with the intention of the exploit still being available upon US Jelly Bean release. Since this has been outed, and is now public, i will share a more proper script of the same method. I actually kept the adb shell id command, as it is pretty useful for this operation.
Main differences in my script is that you don't need to ever disconnect your phone.
1. Unzip the zip file
2. Make sure USB Debugging is on, and your are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt
4. Change to MTP mode.
5. Wait for your computer to ask how to view files.
6. Press enter in the CMD prompt to continue.
7. Done.
This is a fully working method for the most current US/Canadian releases, and Jelly Bean releases. BTW, the current release does not install busybox correctly, includes SuperuserPro.apk (which I'm sure wasn't purchased by everyone downloading this). Also I have updated it to the latest busybox, su binary's, and Superuser.apk available.

hi, is there any way to unroot it? thks

A Million Thanks!
fiddy619 said:
I really would have posted this much sooner, however, this particular method was being kept secret with the intention of the exploit still being available upon US Jelly Bean release. Since this has been outed, and is now public, i will share a more proper script of the same method. I actually kept the adb shell id command, as it is pretty useful for this operation.
Main differences in my script is that you don't need to ever disconnect your phone.
1. Unzip the zip file
2. Make sure USB Debugging is on, and your are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt
4. Change to MTP mode.
5. Wait for your computer to ask how to view files.
6. Press enter in the CMD prompt to continue.
7. Done.
This is a fully working method for the most current US/Canadian releases, and Jelly Bean releases. BTW, the current release does not install busybox correctly, includes SuperuserPro.apk (which I'm sure wasn't purchased by everyone downloading this). Also I have updated it to the latest busybox, su binary's, and Superuser.apk available.
Click to expand...
Click to collapse
I can't thank you enough.... I got my Optimus G in Dec. and I immediately found root method and was completely content with my new phone. Then came the dreaded OTA update that I knew would remove root. I avoided the update with determination. I shouldn't have let my goofy sister touch my phone... After our got it back from her I realized I wasn't receiving the update reminders. I panicked, checked root, root was lost! :crying: I began searching everywhere only to find that there was no root for zv9....For weeks it was the same. Then yesterday I found your method, fired up my laptop and within 5 minutes my LGOG ZV9 on Sprint was rooted again! Thanks again. I can't tell you how much I rely on my free wifi tether.
---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------
I re-rooted my LGOG after the OTA update to ZV9 robbed me of my original root. It only took about five minutes and worked flawlessly. Well tonight I tried to root my girlfriends phone (also a LGOG running ZV9 on the Sprint network) and although it ran through the process just as mine did, as well as stated root was successful, when I run root check to confirm it comes back negative. What am I doing wrong? Any ideas? Thanks

How do you unroot?

fiddy619 said:
I really would have posted this much sooner, however, this particular method was being kept secret with the intention of the exploit still being available upon US Jelly Bean release. Since this has been outed, and is now public, i will share a more proper script of the same method. I actually kept the adb shell id command, as it is pretty useful for this operation.
Main differences in my script is that you don't need to ever disconnect your phone.
1. Unzip the zip file
2. Make sure USB Debugging is on, and your are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt
4. Change to MTP mode.
5. Wait for your computer to ask how to view files.
6. Press enter in the CMD prompt to continue.
7. Done.
This is a fully working method for the most current US/Canadian releases, and Jelly Bean releases. BTW, the current release does not install busybox correctly, includes SuperuserPro.apk (which I'm sure wasn't purchased by everyone downloading this). Also I have updated it to the latest busybox, su binary's, and Superuser.apk available.
Click to expand...
Click to collapse
Every time I run CurrentRoot.bat I receive the error " 'adb' is not recognized as an internal or external command, operable program or batch file" after every step.
Im on Telus running E97310g

confirmed working on LG E975 Singapore version

Afraid LG did something, cant get it to root.
I have an E975 with 4.1.2, software version E97510a-525-05.
I won it in LGs test pilot contest so not sure if its something they did to this or if they plugged the hole completely for the future also.
The guy I spoke to said something about them being flashed as we spoke, and it looked like the phone could have been taken from the box.
Should I wait and hope they send a update after the contest is over or can I use a KDZ and if so, what KDZ can I use to maintain same radio bands?
EDIT: Tried the LG sMobile Support tool and it said it found an update. So now its downloading that *holds thumbs*
EDIT2: Updated to E97510B and still no go, guess they did something to the euro version...

cant root
hi, i tried the CurrentRoot.bat and followed the instructions but couldn't root. it said phone now rooted and restarted the phone but there was no superuser after that
i saved a screenshot of it incase anyone can figure out whats wrong. just got the phone yesterday.... Best phone i've ever used.(from starhub singapore if it helps)
i think its because of the uid and gid not being zero. any ideas??

omnius1 said:
How do you unroot?
Click to expand...
Click to collapse
+1 for unroot method?

root
keltai said:
hi, is there any way to unroot it? thks
Click to expand...
Click to collapse
does NOT work on all E975 OG, mine didn't root

Awesome! Worked perfect on my E975 10b - europe edition :good:

No root for my E750 v10D. Instead since my root atempt can't get iGO Primo 2.0 to work again. The phone closes apk with no error message. I have been trying diferent versions, factory reset still no luck.
How can I reflash firmware again since LG support tool says I have the latest version?
L.E. Done with the reflash and iGO primo works again...

[Q] Trouble Unlocking Bootloader

Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.

Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app

I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967

Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.

Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults

UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.

Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/

Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.

Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).

It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it

I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?

razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.

Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve

Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app

@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices

I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...

[ROOT] Root your G2 [ATT|VZW|TMO|KT|RGS|BELL|TELUS|OPEN] [Yay!]

Howdy everyone!
Here's another neat root!
What is this?
This is a very simply and easy to use root package for the LG G2.
For now I'm calling it IORoot, despite the fact that it's not really all that deserving of a name.​
Which phones does this support?
Currently the following phones are supported by this root package:
AT&T G2 (D800) - D80010d
Verizon G2 (VS980) - VS98010B (Shipping ROM)
Verizon G2 (VS980) - VS98011A (OTA)
T-Mobile G2 (Shipping ROM)
KT F320k (Shipping ROM)
Rogers D803 (Shipping ROM)
Bell D803 (Shipping ROM)
Telus D803 (Shipping ROM)
OPEN D802 (Shipping ROM)
How do I use this?
Here's a video!
Or, in List Form:
Ensure you have the proper USB drivers installed, and your phone is in the proper mode (For Verizon, use Ethernet mode on the PC settings menu)
Enable Developer Mode on your phone and enable USB Debugging
Extract this zip file somewhere on your PC
Run root.bat
The phone will ask you to disconnect USB, disable USB debugging, then re-enable it and plug the phone back in, do so when prompted
You will then be asked if you would like to have a superuser package installed, which you can accept or decline
Why is it asking if I want to 'trip rootchecker'?
LG's phones come with some software loaded that detects the presence of root on a phone, and invalidates your warranty.
Rooting the phone, by nature, voids your warranty. You can put your phone in a special mode where ADB shell has root permissions, however your phone is not technically 'rooted' by app standards.
You will not be able to use 'root required' apps on your phone if you do not let the root script install Superuser.​
Okay, where do I get this?
See @autoprime's post here: http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
-- OLD VERSION --
Code:
[url]http://downloads.codefi.re/thecubed/lg_g2/root/ioroot10.zip[/url]
I'll be keeping this link up to date, and changing the version number as new releases come out.
Please do not mirror this link, as it makes my life easier to keep everything under one roof. Thanks!​
News:
NEW UPDATE: Now supports F320k on KT
NEW NEW UPDATE: Supports the VZW OTA, haven't confirmed yet, but this should do the trick.
NEW NEW NEW UPDATE: Thanks to DeamonFish in IRC, we now have a lovely howto video for this root!
NEW NEW NEW NEW UPDATE: Rogers AND Bell AND Telus AND D802 now supported!
Okay guys, so, @autoprime is taking over from here -- see his post http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869 and be sure to thank him!​
Help! I cant even! I accidentally a phone!
Calm down, don't panic. Join us in #lg-g2 on Freenode.
If you're new to IRC, click here http://webchat.freenode.net/?channels=#lg-g2 and it'll connect you to the channel.
I'm IOMonster on IRC, I still don't know why I have two nicknames. Personality disorder I suppose
PLEASE don't PM me on XDA asking for help. My inbox has exploded, and can no longer handle it. I will not be able to help you over PM of any sort (IRC or XDA, or even email).​
Alright guys, let me know if you run into any issues!

thecubed said:
Howdy everyone!
Here's another neat root!
This is confirmed to work for the ATT and Verizon variants, I'll add support for T-Mobile as soon as I get someone in #lg-g2 in Freenode who owns one.
Simple:
Ensure you have ADB drivers installed and USB Debugging enabled
Extract this .zip file somewhere
Run the root.bat file, and read the instructions
During the installation, you'll have to disable USB Debugging and re-enable it, then the app will ask you if you care about rootcheckerd (rctd).
If you don't want your phone to show "rooted" in download mode, or in settings, hit CTRL-C when prompted and you'll just have a root shell through ADB.
Personally, this is enough for me, but if you want full root, press continue and it'll install superuser and a superuser binary for you.
PLEASE do not mirror this! It makes my life easy if I can just edit the file on my server if need be instead of contacting all the mirrors.
Click to expand...
Click to collapse
First!!! Thanks IO and all the devs responsible :highfive:

Can you explain the difference between root shell (leaving it to say unrooted) and "full" root? Will this affect once we get a way to unlock the bootloader or get a recovery for roms? And is there a way to unroot? Thanks for this!!

friguy3 said:
Can you explain the difference between root shell (leaving it to say unrooted) and "full" root? Will this affect once we get a way to unlock the bootloader or get a recovery for roms? And is there a way to unroot? Thanks for this!!
Click to expand...
Click to collapse
Root shell allows you to have root only through ADB. Apps on the phone will not be able to use the root functions of the device if you don't let my script install superuser.

djkinetic said:
First!!! Thanks IO and all the devs responsible :highfive:
Click to expand...
Click to collapse
Most definitely thanks, I see I have USB debugging on but am not sure what is meant by:
command prompt and type adb devices, you should see your Serial Number and online.
Command prompt from where?
Thanks...
Mike

Mikef3j said:
Most definitely thanks, I see I have USB debugging on but am not sure what is meant by:
command prompt and type adb devices, you should see your Serial Number and online.
Command prompt from where?
Thanks...
Mike
Click to expand...
Click to collapse
What?

thecubed said:
Howdy everyone!
Here's another neat root!
Click to expand...
Click to collapse
I dont have the phone (yet) but thanks for rootz!

Awesome. Now I'm gonna go buy a G2. Hehe.

What can we do if we rooted with that weird Chinese exe?
How can I unroot so that I can use this?

thecubed said:
Howdy everyone!
Here's another neat root!
http://downloads.codefi.re/thecubed/lg_g2/root/ioroot2.zip
This is confirmed to work for the ATT and Verizon variants, I'll add support for T-Mobile as soon as I get someone in #lg-g2 in Freenode who owns one.
Simple:
Ensure you have ADB drivers installed and USB Debugging enabled
Extract this .zip file somewhere
Run the root.bat file, and read the instructions
During the installation, you'll have to disable USB Debugging and re-enable it, then the app will ask you if you care about rootcheckerd (rctd).
If you don't want your phone to show "rooted" in download mode, or in settings, hit CTRL-C when prompted and you'll just have a root shell through ADB.
Personally, this is enough for me, but if you want full root, press continue and it'll install superuser and a superuser binary for you.
PLEASE do not mirror this! It makes my life easy if I can just edit the file on my server if need be instead of contacting all the mirrors.
Click to expand...
Click to collapse
what happened to the other thread (which links to this one) in which there were t-mobile variant rooting instructions? i mean i know what happened, they were deleted but why?

scrosler said:
I dont have the phone (yet) but thanks for rootz!
Click to expand...
Click to collapse
You should get it (now)
Also on topic, you need something from every version or just want to know if it works?

Guys im about to get this version soon LG G2 F320S LTE-A 4G LTE,its the korean version of the phone.Does the root works with this version too?Or if not is there any root that works?I hate on screen buttons and the 1st think i want to do when i get it,is to hide them lol

Thanks man! I swear I remember you from the Revolution days and trying to figure out recovery on that thing!

RiverdALIEN said:
what happened to the other thread (which links to this one) in which there were t-mobile variant rooting instructions? i mean i know what happened, they were deleted but why?
Click to expand...
Click to collapse
The other thread contained a link to a root that could possibly compromise your phone's security (and your desktop too, since there's all sorts of other stuff in those exe files).
If someone pops into the #lg-g2 chan with a TMO phone I'll gladly support TMO as well!
If you did happen to use the old root, I'd recommend restoring your phone back to stock with the TOT / KDZ files before applying this root.

stetsonaw said:
Thanks man! I swear I remember you from the Revolution days and trying to figure out recovery on that thing!
Click to expand...
Click to collapse
You got this phone too? Join #lg-g2 ! It'll be like old times!

Mikef3j said:
Most definitely thanks, I see I have USB debugging on but am not sure what is meant by:
command prompt and type adb devices, you should see your Serial Number and online.
Command prompt from where?
Thanks...
Mike
Click to expand...
Click to collapse
You need to have the android sdk installed on your computer. I find it easier to use a distro of linux but windows is fine too. Find android sdk install and make sure adb is in the /platform-tools folder. Then run this adb devices cmd with your phone attached via usb and if it works you should have an rsa security pop up on your phone you have to allow. Then your phone is connected via adb.
Sent from my LG-D800 using xda app-developers app

thecubed said:
The other thread contained a link to a root that could possibly compromise your phone's security (and your desktop too, since there's all sorts of other stuff in those exe files).
If someone pops into the #lg-g2 chan with a TMO phone I'll gladly support TMO as well!
If you did happen to use the old root, I'd recommend restoring your phone back to stock with the TOT / KDZ files before applying this root.
Click to expand...
Click to collapse
how does one "pop into the #lg-g2 chan" ? i have a tmo g2 and i'm no dev or hacker but i'm clever and have been rooting and customizing since 4.0.
all i really want at this point is the ability to remove the bloatware and then possibly unroot

RiverdALIEN said:
how does one "pop into the #lg-g2 chan" ? i have a tmo g2 and i'm no dev or hacker but i'm clever and have been rooting and customizing since 4.0.
Click to expand...
Click to collapse
An easy way would be going here: http://webchat.freenode.net/?channels=#lg-g2 putting in a username, filling out the captcha and then connect.

thecubed said:
If you did happen to use the old root, I'd recommend restoring your phone back to stock with the TOT / KDZ files before applying this root.
Click to expand...
Click to collapse
Sorry... can you please explain how to do this? Or at least point me towards the right posts?

Han Solo 1 said:
What can we do if we rooted with that weird Chinese exe?
How can I unroot so that I can use this?
Click to expand...
Click to collapse
mastertwiz said:
Sorry... can you please explain how to do this? Or at least point me towards the right posts?
Click to expand...
Click to collapse
You will need to go back to stock, and then reroot with this rooter.
If you are on VZW ONLY, follow my guide here: http://forum.xda-developers.com/showthread.php?t=2448960
if you are on anything else, this guide is better to follow, but I had issues with the first section (which is why I wrote my VZW-specific guide) http://forum.xda-developers.com/showthread.php?t=2432476

From Samsung to Sony and confused about Bootloader unlocking.

Im thinking of buying a Z5P and while i have searched a lot, i just cant seem to find the answer to a question i have maybe someone here can help. On Sonys developer website there is instructions on how to unlock the bootloader and the last line of the instructions are as follows, note the part in blue text.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.[/B]
My question is how/where do i buy a Z5P that will definitely be Bootloader unlock allowed yes, surely its not just a case of random devices are unlockable is it? I was going to buy this from carphone its sim free so im expecting to be allowed to unlock the bootloader but dont want to buy it only to find i cant.
http://www.carphonewarehouse.com/phones/sony-xperia-z5-premium/handset?colourCode=BLACK

If the phone has no SIM lock, it's bootloader should be unlockable. I say "should" since I am not aware of other factors that keep the bootloader locked, but there might as well be.
On another note, unless you are a fairly advanced user and are set on flashing your device with a custom kernel, I would not recommend a bootloader unlock before root or an option to back up of TA becomes available.
It contains your device's DRM which gets irreversibly lost which makes your camera perform worse(BIONZ stops working), among other things.

CPW is the place to go for unlockable fones. I got my Z5P from there.
Sent from my SGP311 using XDA Free mobile app

As mentioned elsewhere, IN GENERAL (rare exceptions) - if it's SIM-unlocked it'll be bootloader-unlockable. If it's SIM-locked, the bootloader is almost guaranteed to be perma-locked.
While SIM locks and bootloader locks are technolgically independent, in the case of Sony devices (This rule of thumb can NOT be applied to any other manufacturer), SIMlocked devices have a permanent bootloader lock, devices sold without a SIM lock can have bootloader unlocked. Note that in the case of phones sold with a SIM lock that are later unlocked with a PIN - the bootloader lock is still disallowed.

Cheese for the replys everyone I got the phone from the carphone and its boot loader unlock allowed yes
I got the regular z5 instead though.

Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root

NJ72 said:
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
Click to expand...
Click to collapse
Try flashing another firmware through flashtool that is allowed.

KbaB.BroS said:
Try flashing another firmware through flashtool that is allowed.
Click to expand...
Click to collapse
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.

NJ72 said:
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
Click to expand...
Click to collapse
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.

KbaB.BroS said:
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
Click to expand...
Click to collapse
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...

NJ72 said:
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
Click to expand...
Click to collapse
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.

KbaB.BroS said:
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
Click to expand...
Click to collapse
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?

NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
You can try this guide:
http://m.youtube.com/watch?v=F0bSsGxFdks

NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Android studio can be found here: http://developer.android.com/sdk/installing/index.html?pkg=studio
Read everything throughly, it is important to get all the details regarding usage and installation.
After installing Android studio, you should download all the required SDK's found inside android studio->Configure->SDK Manager.
On the left side you will see several options in the navigation menu.
First go to Appearance & Behavior->System settings->Android SDK. Then in the "window" you have, make sure the first tab is selected (SDK Platforms).
Here you need to check all the android versions your phone(s) run.
Then go to the second tab (SDK Tools) and download:
Android SDK Build Tools
Android SDK Tools 24.4.1
Android SDK Platform-Tools 23.1
Google USB Driver
Android NDK
I am not sure if you really need the NDK one, but the rest I think is required. You can do as I did and choose all if you want.
On the last tab (SDK Update Sites) I have checked everything.
When you have done all of this, you should install Flashtool and go to the install directory and open the Driver folder, where you will find a .exe file. Run this and click next untill you can choose a few items from a list, in this list you should check Fastboot drivers, and USB drivers, and any other options that are relevant to your use, then finish the installation. (The entire installation of Flashtool should be done with 100% admin rights on the user).
After this is done, connect your phone to your pc and go to device management on your pc and you will likely find something similar to this:
If you have this yellow exclamation mark triangle thingy, then you will need to manually install your USB drivers.
Download your driver here: http://developer.sonymobile.com/downloads/drivers/
Then right click the yellow exclamation mark triangle thingy device in device management, and select update driver, then select "Browse my computer for driver software".
On the next window, select "Let me pick from a list of device drivers on my computer".
In the list that appears, select "Show All Devices" and click next.
Click the "Have Disk" button, then navigate to the driver you downloaded, and you will get 3 options in the window on you screen, select "Android ADB Interface" and click next.
Confirm by pressing "Yes" Then press "Install".
If completed without problems you should see "Windows has successfully updated your driver software".
*NOTE* On the above steps, you can also navigate to the folder where you installed android studio, which should be something similar to this: C:\Program Files(x86)\Android\android-sdk\extras\google\usb_driver OR it can be found your USER folder.
and here you can install the usb_driver aswell, which should make most phones support USB debugging and ADB on via your pc.*NOTE*
now reconnect your phone and the exclamation mark triangle thingy should be gone, good!
Next thing you can do is navigate to the installation folder of Android studio, and go to the Platform-Tools folder.
Inside the folder, hold down shift, while right clicking any white empty space inside the folder, and click open terminal here.
In the terminal, type: "adb devices" /Without the " marks. then it should say something about daemon not running etc, when its done, do the same command again, and you should se you device listed. Good, at this point you are ready to unlock bootloader!
If you have succeeded in every step so far, then go ahead and unlock bootloader following sonys instructions!
When you are done, you can simply follow the guides provided in the custom Rom thread itself most of the time.
If not, then a simple way to do it is:
Get all the files you need for the rom flash. That means Kernel, rom img, and a custom recovery like TWRP and SuperSU.
It is REALLY important that all files are for your device specifically!
Put the SuperSU.zip and the custom Rom.zip on your sd card and put it in the phone.
To avoid any trouble, do as I did and save all those files in the Platform-Tools folder, because you need to open the terminal as shown earlier in the post, by holding shift and right clicking in the same folder as the files, this is a must.
Open the terminal from the same folder as the rom, kernel and recovery.
type:
Code:
fastboot flash boot NAMEOFYOUR_KERNEL.img (This is usually boot.img)
fastboot flash recovery NAMEOFYOUR_RECOVERY.img (Usually contains TWRP in name)
fastboot reboot
You should now press volume up key when a led lights up while you see the sony logo, a orange light, not the red one, this will bring you into recovery, from here choose install, then navigate to your SuperSU.zip and install it.
Reboot your phone and you are now rooted, if you also have a custom rom, then place it on your sd card like the SuperSU.zip, but make sure the custom rom is a ZIP file!
Boot into recovery and install the custom rom, wipe cache and dalvick cache.
Congratulations on your custom rom!
Hope this helps a bit, sorry for any errors, but this is exactly how I did it, as far as I can remember!
Btw, this can seem like alot of work, especially when and if you encounter any problems while installing. I know I did encounter ALOT of them, but hopefully with my simple guide you can avoid them!
Luckily, this is just something you have to do once if you do it 100% right!

xirt0n said:
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Click to expand...
Click to collapse
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.

KbaB.BroS said:
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
Click to expand...
Click to collapse
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.

xirt0n said:
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
Click to expand...
Click to collapse
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.

KbaB.BroS said:
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
Click to expand...
Click to collapse
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.

xirt0n said:
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
Click to expand...
Click to collapse
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.

KbaB.BroS said:
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
Click to expand...
Click to collapse
Ok, I never personally used PC companion so I didnt know what it does, I just saw people suggest it around

Can’t get out of bootloader

Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,

I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone

rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?

Well not really. But I follow many instrucciones from differents post and nothing

rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:

I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.

Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/

Ok., I will let you guys know thank you

Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.

You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.

@rectangularspace Link to the standalone platform tools HERE. This is all you need.

Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?

rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.

rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.

I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out

I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.

rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.

My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?

rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.

rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good: