Root is here - T-Mobile LG G3

http://forum.xda-developers.com/lg-g3/development/root-twrp-root-twrp-tmo-lg-g3-t2821005
Have fun

Woot. Did u try it?
Sent from my LG-D851 using XDA Premium 4 mobile app

Just waiting on pc version

Same waiting on pc version as well
LGG3 and beyond

ive tried 10x with linux version and cant get mine to work so i maybe waiting on pc version as well

Got mine rooted and twrp installed

BACARDILIMON said:
Just waiting on pc version
Click to expand...
Click to collapse
Nice to see you over from Note 3. You switch or the LG G3 just an add-on?

vibrantliker said:
Nice to see you over from Note 3. You switch or the LG G3 just an add-on?
Click to expand...
Click to collapse
Yeah man I feel like the new kid at school.lol. but so much better phone. I did not care for the note 3. So many hardware issues. But loving this beast. Good to see you here. Can't wait to start flashing lol.

Failed the first time, but I tried it again and all worked perfectly. Ran it on Mac OS X 10.9.
Had to change the phone to PTP mode since it defaults to MTP for adb to see it.
Thank you!!!

BACARDILIMON said:
Just waiting on pc version
Click to expand...
Click to collapse
Me too

Wow! How exciting. The only reason I want root is to remove the on screen buttons and install LMT PIE launcher.
Nexus ONE

Hopefully with root I can enable mass storage mode and solve my issues running with my Pioneer AVX1500

Have you windows people tried cygwin to get root?

ThePagel said:
Have you windows people tried cygwin to get root?
Click to expand...
Click to collapse
I'd very much like to know the answer to this as well...

From Windows
Just run the adb commands from the root method in the root thread
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
It's really simple, then install the twrp recovery.img with flashify
you're rooted with recovery

koraun said:
From Windows
Just run the adb commands from the root method in the root thread
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
It's really simple, then install the twrp recovery.img with flashify
you're rooted with recovery
Click to expand...
Click to collapse
Can you explain this adb method it always confusing me Im used to using odin this my first lg device

raw2000j said:
Can you explain this adb method it always confusing me Im used to using odin this my first lg device
Click to expand...
Click to collapse
Same here. I searched for a guide for first timers on LG. It is very different

So I'm rooted and have TWRP now. I know I'm rooted cause exposed framework installed and quickboot app works fine but there's no notification for root request. Is a seperate app needed?

Punchatron said:
So I'm rooted and have TWRP now. I know I'm rooted cause exposed framework installed and quickboot app works fine but there's no notification for root request. Is a seperate app needed?
Click to expand...
Click to collapse
Superuser from playstore

koraun said:
From Windows
Just run the adb commands from the root method in the root thread
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
It's really simple, then install the twrp recovery.img with flashify
you're rooted with recovery
Click to expand...
Click to collapse
This method worked perfectly for me!! Time to remove bloat ?
Sent from my LG-D851 using Tapatalk

Related

Massive fail! Need help!

So i was going to flash over a 4.4 rom to my Galaxy nexus, but since i was very tierd i didn't pay to much attention to what i was doing. I flashed in the rom but forgot to flash in the gapps, and for some reason CWM got deleted. So now im running 4.4 with no gapps and no CMW. And that's not all.. the worst thing is that my usbport seems to be broken, i can't connect with usb to my computer so i cant put anything on the phone.
Is there anyway i can fix this problem? Or is my nexus officialy dead :crying:
If you have the Play Store app, or a browser so that you can get to the Play Store, and you still have root, you could download two free apps: Goo Manager, which has ROMs and gapps which you can download, and Recovery Tools, which allows you to flash CWM or TWRP.
Sent from my VZW Galaxy Nexus using xda app-developers app
If your usb port is dead, you may not be in a great situation. Your best bet if it works, is to go into fastboot and flash recovery again.
If you are rooted but have broken USB you have other options. You could sideload apps, transfer via wifi or just browse to them on the internet (not sure if your ROM came with a browser). An app that can install a custom recovery would be ideal, Goo Manager, ROM Manger, or something like that (maybe there are better options here, I am a little out of the loop on these apps). You could also download the proper GApps.
If you aren't rooted and you don't have functional USB, you indeed may have an issue. Fixing the USB may be your only solution.
cupfulloflol said:
If your usb port is dead, you may not be in a great situation. Your best bet if it works, is to go into fastboot and flash recovery again.
If you are rooted but have broken USB you have other options. You could sideload apps, transfer via wifi or just browse to them on the internet (not sure if your ROM came with a browser). An app that can install a custom recovery would be ideal, Goo Manager, ROM Manger, or something like that (maybe there are better options here, I am a little out of the loop on these apps). You could also download the proper GApps.
If you aren't rooted and you don't have functional USB, you indeed may have an issue. Fixing the USB may be your only solution.
Click to expand...
Click to collapse
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Eskimox said:
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Click to expand...
Click to collapse
What happens when you try?
Eskimox said:
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Click to expand...
Click to collapse
you are enabling third party apps through the developers settings right?
Eskimox said:
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Click to expand...
Click to collapse
Which ROM are you currently on? SlimKat, Dreams or A taste of KitKat?
Metalero9389 said:
you are enabling third party apps through the developers settings right?
Click to expand...
Click to collapse
Yes i am, still dosen't work to install any apps. I dont think you can install any apps if you dont have gapps.
RajatPatel said:
Which ROM are you currently on? SlimKat, Dreams or A taste of KitKat?
Click to expand...
Click to collapse
I am on Dreams.
Eskimox said:
Yes i am, still dosen't work to install any apps. I dont think you can install any apps if you dont have gapps.
I am on Dreams.
Click to expand...
Click to collapse
You can try ADB over WiFi if you can confirm you are rooted.
Download the file flash_image in your PC from here and also download CWM recovery from here and then follow these steps:
Extract the flash_image.zip to a folder name say XYZ
Then in your phone, goto developers option and enable ADB over network. Make sure your PC and Mobile are on same WiFi network. After you enable it, you will get and ip:host (e.g 192.168.x.x:5555)
Now on your PC, copy both downloaded files to XYZ folder and do a shift+right click and select "Open Command Window here" and execute following code.
Code:
adb connect 192.168.x.x:5555
adb root
adb push flash_image /data/local
adb shell chmod 777 /data/local/flash_image
adb push recovery-clockwork-touch-6.0.4.3-maguro.img /data/local/
adb shell chmod 777 /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
adb shell /data/local/flash_image recovery /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
If this goes successful, your recovery is back. Try rebooting to recovery to confirm that.
Wish you luck :good:
P.S The issue is caused due to ROM as it this particular ROM flashes stock recovery over your custom recovery :silly:
RajatPatel said:
You can try ADB over WiFi if you can confirm you are rooted.
Extract the flash_image.zip to a folder name say XYZ
Then in your phone, goto developers option and enable ADB over network. Make sure your PC and Mobile are on same WiFi network. After you enable it, you will get and ip:host (e.g 192.168.x.x:5555)
Now on your PC, copy both downloaded files to XYZ folder and do a shift+right click and select "Open Command Window here" and execute following code.
Code:
adb connect 192.168.x.x:5555
adb root
adb push flash_image /data/local
adb shell chmod 777 /data/local/flash_image
adb push recovery-clockwork-touch-6.0.4.3-maguro.img /data/local/
adb shell chmod 777 /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
adb shell /data/local/flash_image recovery /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
If this goes successful, your recovery is back. Try rebooting to recovery to confirm that.
Wish you luck :good:
P.S The issue is caused due to ROM as it this particular ROM flashes stock recovery over your custom recovery :silly:
Click to expand...
Click to collapse
wow this might work. I just have one problem, i cant find the option you are talking about. Are you sure its accessible without having to install any apps. I have been looking around on the internet and most people seems to be using some kind of app to access that option.
Eskimox said:
wow this might work. I just have one problem, i cant find the option you are talking about. Are you sure its accessible without having to install any apps. I have been looking around on the internet and most people seems to be using some kind of app to access that option.
Click to expand...
Click to collapse
Its in settings itself. If you can't see developers option in your settings, then goto setting > about phone and tap 5 times on "build number"
RajatPatel said:
Its in settings itself. If you can't see developers option in your settings, then goto setting > about phone and tap 5 times on "build number"
Click to expand...
Click to collapse
no yeah i know that, but i cant find the setting to activate to ADB over network.
Eskimox said:
no yeah i know that, but i cant find the setting to activate to ADB over network.
Click to expand...
Click to collapse
Here is a screenshot that might help you.
Sent from my Galaxy Nexus using xda app-developers app
RajatPatel said:
Its in settings itself. If you can't see developers option in your settings, then goto setting > about phone and tap 5 times on "build number"
Click to expand...
Click to collapse
RajatPatel said:
Here is a screenshot that might help you.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I guess im not rooted then coz i cant find that setting
Eskimox said:
I guess im not rooted then coz i cant find that setting
Click to expand...
Click to collapse
Can you see root access option just over these debugging options? If yes, then select apps and adb
Sent from my Galaxy Nexus using xda app-developers app
There is an APK somewhere on the web which installs any gapp you pick in android right away.
Unfortunately, it doesnt work in 4.4
Sent from my Galaxy Nexus using xda app-developers app
Actually the apk for gapps android installer is working for 4.4 . I can send it to you, if you want.
Sent from my Galaxy Nexus using xda app-developers app

[Q] Optimus G E975 - ADB does not work anymore :(

Problem:
Optimus G E975 - ADB does not work after (FreeGee) TWRP update 2.6.3.0.
What happened:
Was on CM10.2 TWRP 2.6.0.0 and ADB worked fine. Used FreeGee to update TWRP.
Booted to recovery, wiped _everything_. Now adb does not work at all (device does not show up in "list").
I can see Yellow triangle with exclamation mark in windows device manager (LG-E975).
Any suggestions? I havent dared to boot, so Im still in TWRP. TYIA!
Lol freegee to update recovery, you my friend is a BOSS
Sent from my LG-E975 using Tapatalk
atifsh said:
Lol freegee to update recovery, you my friend is a BOSS
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
are a BOSS
What rom are you on? With cm-10.1 (android 4.4.2) or later you have to accept your RSA keys for adb to work. If you wipe data it wipes the stored rsa keys so you have to accept it again.
Also using freegee to update twrp is fine. It now detect if you are already unlocked or not, and if so only installs the new recovery.
Shelnutt2 said:
Also using freegee to update twrp is fine. It now detect if you are already unlocked or not, and if so only installs the new recovery.
Click to expand...
Click to collapse
That's good. ?
Did you find anything about boot issue with new freegee with nexus bootloader
Sent from my LG-E975 using Tapatalk
atifsh said:
That's good. ?
Did you find anything about boot issue with new freegee with nexus bootloader
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
That was an issue with 4.1 devices only, and it has been resolved. Everyone is now good to go.
Shelnutt2 said:
What rom are you on? With cm-10.1 (android 4.4.2) or later you have to accept your RSA keys for adb to work. If you wipe data it wipes the stored rsa keys so you have to accept it again.
Also using freegee to update twrp is fine. It now detect if you are already unlocked or not, and if so only installs the new recovery.
Click to expand...
Click to collapse
I was on CM10.2
RSA keys are good point. But shouldnt TWRP notify about this (I know CM notfied this earlier, but I cant boot now, can I?
Atleast TWRP warns me about booting (NO OS INSTALLED - ARE YOU SURE YOU WISH TO BOOT?).
Shelnutt2 said:
What rom are you on? With cm-10.1 (android 4.4.2) or later you have to accept your RSA keys for adb to work. If you wipe data it wipes the stored rsa keys so you have to accept it again.
Click to expand...
Click to collapse
Adb devices doesn't ask to accept rca keys if you are on recovey, I think he needs to install adb drivers again.
Sent from my LG-E975 using Tapatalk
atifsh said:
Adb devices doesn't ask to accept rca keys if you are on recovey, I think he needs to install adb drivers again.
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
And I think if RSA is missing, adb should show device in list (as OFFLINE)
Installing LG UNITED MOBILE DRIVER again was my first guess too. But doesnt seem to work (LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1).
For some reason, Im afraid that FreeGee did something wrong. Maybe wrong TWRP version (wrong device)?
And now windows drivers do not work correctly? (device manager has yellow triangle @ LG E975)
If TWRP reports windows device id, this could be the case?
Is it safe to boot? Can I still get back to TWRP?
iliasus77 said:
And I think if RSA is missing, adb should show device in list (as OFFLINE)
Installing LG UNITED MOBILE DRIVER again was my first guess too. But doesnt seem to work (LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1).
Click to expand...
Click to collapse
Only if you are in a rom, but you are not with any OS installed. Just try to reinstall adb drivers
Sent from my Nexus 7 using Tapatalk
atifsh said:
Only if you are in a rom, but you are not with any OS installed. Just try to reinstall adb drivers
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Did not work.
Had to KDZ. Now back to stock. Still have no idea what really went wrong. But Ill post it if Ill find out.
Thanks for trying to help guys. You are what makes XDA great.
iliasus77 said:
Did not work.
Had to KDZ. Now back to stock. Still have no idea what really went wrong. But Ill post it if Ill find out.
Thanks for trying to help guys. You are what makes XDA great.
Click to expand...
Click to collapse
I had the exact same issue yesterday.... while connecting the phone in recovery mode to your system, you have to install the LG united mobile drivers 3.8.1, and then update the same from device manager... select the yellow exclamation mark, update driver... now your device will show up in adb but as offline, but still you can push a cwm or rom.zip to get the phone working and restore the nandroid backup... that's how, i managed to get back mine...
BtW: I have philz recovery installed and now want to try cm11... Is CM11 already rooted or we have to flash the super su.zip like we did in houston's kk rom's???
Apologies, if asking this question in the wrong section...
iliasus77 said:
Problem:
Optimus G E975 - ADB does not work after (FreeGee) TWRP update 2.6.3.0.
What happened:
Was on CM10.2 TWRP 2.6.0.0 and ADB worked fine. Used FreeGee to update TWRP.
Booted to recovery, wiped _everything_. Now adb does not work at all (device does not show up in "list").
I can see Yellow triangle with exclamation mark in windows device manager (LG-E975).
Any suggestions? I havent dared to boot, so Im still in TWRP. TYIA!
Click to expand...
Click to collapse
Go to device manager,go to the one with exclamation mark,right click then click update driver software.
then click browse computer for software.then click the let me pick option.then it should show you a bunch of options.choose something like 'Android Sooner Single ADB interface'then wait till install is finished.Then check using adb devices.Good Luck!
BlackPie said:
Go to device manager,go to the one with exclamation mark,right click then click update driver software.
then click browse computer for software.then click the let me pick option.then it should show you a bunch of options.choose something like 'Android Sooner Single ADB interface'then wait till install is finished.Then check using adb devices.Good Luck!
Click to expand...
Click to collapse
I know this is a few weeks old... but I cannot thank you enough. Lost root and needed to use adb... to find out nothing came up anymore in devices. This fixed it for me. :good:
Hello, I have an LG F180L with Android 4.4.2 and when I run adb devices it appears offline. However I have not this problem with my Galaxy S4 (Android 4.4.2 also). I have tried using different USB 2.0 ports and sdk is updated. I will be grateful if someone could help me.

[Q] I am now S-Off w/ Bootloader Unlocked using Firewater!

Okay, so now I can confirm that Firewater worked great - using the temproot method. Where do I go from here? The instructions I've found for installing TWRP were extremely confusing. I had no problems following the directions for Firewater, but this is a different story. Now that I'm unlocked and S-Off, where do I go from here?
Congrats! Well you need to flash a recovery. Get a recovery.img http://flyhalf205.com/getdownload.php?file=recoveries/openrecovery-twrp-2.6.3.4-m7vzw.img and place it on your pc in the same folder as the fastboot.exe file. Open a cmd prompt and navigate to the directory where the 2 files are. Boot the phone to bootloader (hboot). Then in the cmd terminal type
Code:
fastboot erase cache
then
Code:
fastboot flash recovery nameofrecoveryimg.img
Thank you very much! I do have some questions. Do I need to be rooted? In the bootloader screen it says I am S-Off and Unlocked, but I don't think I am rooted. I have to use the temproot included with Firewater. I downloaded a twrp .img. Am I supposed to flash that? Once that is flashed, am I free to download a custom rom?
Thanks for the info
Sent from my HTC6500LVW using xda app-developers app
If you are s-off and unlocked all you need to do is flash that recovery i posted, and then flash a rom of your choosing. Most every rom comes pre-rooted. I assume right now you are stock. If you want to stay stock just flash that recovery, then flash superuser thru recovery and you will be rooted.
---------- Post added at 05:21 PM ---------- Previous post was at 04:58 PM ----------
Where did you get the firewater download from, got a link?
Never mind i found it http://firewater-soff.com/instructions/
Cool so you were 4.3 with s on and locked boot loader and firewater now has you s off and unlocked. So you just need a custom recovery and then whatever Rom you want.
I was going to ruu back to stock locked and s on to try firewater for fun but I don't want to run into snags so I'll just stay how I am for now.
Sent from my HTC6500LVW using Tapatalk
is it normal to hang at "waiting for device"?
wwindexx said:
is it normal to hang at "waiting for device"?
Click to expand...
Click to collapse
How long has it been? Windows or Linux? Turned off firewall and antivirus, and removed sync manager if on Windows?
Sent from my HTC6500LVW using Tapatalk
wronge galismt
Linux - Xubuntu to be specific. It seems to only recognize the device half of the time when connected to USB. It hangs indefinitely - 5 min was the longest I would wait. When I select Recovery from the hboot menu, I get a silhouette of my phone with a "NO" symbol through it. This is not normal.
Are you using the quick android sdk or did you download the whole sdk and install platform tools then set path in your home directory profile?
Edit: try these directions at the bottom to set your path.
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Sent from my HTC6500LVW using Tapatalk
I got a error that said i don't have su binaries? anyone else?
J_Abdalla52 said:
I got a error that said i don't have su binaries? anyone else?
Click to expand...
Click to collapse
yes I got that too. I didn't get around to trying it right after running temproot though.
J_Abdalla52 said:
I got a error that said i don't have su binaries? anyone else?
Click to expand...
Click to collapse
Are you rooted? Or did you install twrp and it says that? You have to be root in Linux to run the command.
Ex: cd Downloads/firewater
Sudo su
Type your password
Sent from my HTC6500LVW using Tapatalk
selayan said:
Are you rooted? Or did you install twrp and it says that? You have to be root in Linux to run the command.
Ex: cd Downloads/firewater
Sudo su
Type your password
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
No i just ran the temp root method then i tried to run the normal method and thats what i got.
selayan said:
Are you using the quick android sdk or did you download the whole sdk and install platform tools then set path in your home directory profile?
Edit: try these directions at the bottom to set your path.
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I installed adb and fastboot via apt. I guess assuming that was the optimal way to get it was a mistake. I am assuming now that you need to run temproot beforehand?
Yeah you need the temp root method because your stock and locked, unrooted. Make sure you are admin when you run it.
Sent from my HTC6500LVW using Tapatalk
selayan said:
Yeah you need the temp root method because your stock and locked, unrooted. Make sure you are admin when you run it.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I used minimal adb do you think that could have tampered with the process?
J_Abdalla52 said:
I used minimal adb do you think that could have tampered with the process?
Click to expand...
Click to collapse
It should not as long as you place the firewater files in the same location of the temp adb directory and run commands as admin.
Sent from my HTC6500LVW using Tapatalk
selayan said:
It should not as long as you place the firewater files in the same location of the temp adb directory and run commands as admin.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
do you mean adding the "sudo" prefix?
wwindexx said:
do you mean adding the "sudo" prefix?
Click to expand...
Click to collapse
Yeah to keep from typing Sudo before each command I usually do Sudo su before running any commands.
It will ask for your password then throw you in admin mode. Otherwise you will need to add Sudo before each command.
I use Linux mint 16 but it's built on ubuntu so it should not be different.
Sent from my HTC6500LVW using Tapatalk

[Q] I'm in a bind, need temp root

OK, so, I messed up a bit.
My phone works nearly perfectly. In fact, I would say perfectly aside from being able to download OTA updates.
A while back I used Stump root to root my LS990.
Everything worked and it was rooted.
I modified my build.prop to make it seem as if it were a samsung phone in order to use the Milk music app.
Once I had finished fooling around, I used SuperSU to unroot, only to remember a day later that i forgot to restore my build.prop.
I cannot re-root due to the version incompatibility I created by modifying build.prop.
Is there any way to gain temporary root access so I can restore the original build.prop?
Thanks for your help
fooman19 said:
OK, so, I messed up a bit.
My phone works nearly perfectly. In fact, I would say perfectly aside from being able to download OTA updates.
A while back I used Stump root to root my LS990.
Everything worked and it was rooted.
I modified my build.prop to make it seem as if it were a samsung phone in order to use the Milk music app.
Once I had finished fooling around, I used SuperSU to unroot, only to remember a day later that i forgot to restore my build.prop.
I cannot re-root due to the version incompatibility I created by modifying build.prop.
Is there any way to gain temporary root access so I can restore the original build.prop?
Thanks for your help
Click to expand...
Click to collapse
You got twrp installed?
Sent from my LG-D855 using XDA Free mobile app
Neurom707 said:
You got twrp installed?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
I do not have TWRP installed, unfortunately.
fooman19 said:
I do not have TWRP installed, unfortunately.
Click to expand...
Click to collapse
Have you tried pushing a build.prop through ADB ?
Neurom707 said:
Have you tried pushing a build.prop through ADB ?
Click to expand...
Click to collapse
This is what i've tried
adb devices
<device shows up>
adb pull /system/build.prop
<make necessary changes to build.prop>
adb push build.prop /system/build.prop
failed to copy 'build.prop' to '/system/build.prop': Read-only filesystem
When i enter the shell and type su, it says command not found, most likely because my device is not rooted.
fooman19 said:
This is what i've tried
adb devices
<device shows up>
adb pull /system/build.prop
<make necessary changes to build.prop>
adb push build.prop /system/build.prop
failed to copy 'build.prop' to '/system/build.prop': Read-only filesystem
When i enter the shell and type su, it says command not found, most likely because my device is not rooted.
Click to expand...
Click to collapse
EDIT: Try this use brute force mode http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
So thats a no go too. Hmm
Have you tried using universal root tools to try and root it
Other than that starting from stock is all thats left i think
Neurom707 said:
EDIT: Try this use brute force mode http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
So thats a no go too. Hmm
Have you tried using universal root tools to try and root it
Other than that starting from stock is all thats left i think
Click to expand...
Click to collapse
I don't know of any other useful universal root tools. I can't restore to stock; for some reason it refuses to connect to my LG PC Suite.
When I try stump, it says my device is incompatible.
fooman19 said:
I don't know of any other useful universal root tools. I can't restore to stock; for some reason it refuses to connect to my LG PC Suite.
When I try stump, it says my device is incompatible.
Click to expand...
Click to collapse
Yeah selecting the brute force option should allow you to bypass the warning
Neurom707 said:
Yeah selecting the brute force option should allow you to bypass the warning
Click to expand...
Click to collapse
I did not clarify well enough. I cannot pick any options. The Grind button is grayed out and I cannot select any options.
fooman19 said:
I did not clarify well enough. I cannot pick any options. The Grind button is grayed out and I cannot select any options.
Click to expand...
Click to collapse
So, i did even *more* digging and found a work around for the LG Flash Tool. I had to replace the stock .dll file with a generic LG G3 .dll file.
For those with a similar problem
http://forum.xda-developers.com/spr...de-how-to-restore-sprint-lg-g3-ls990-t2852042
Thank you for the suggestions.

How to flash twrp with no root on top of cynogenmod recovery?

Can any one help me I think I didn't sleep for 3 days lol..I flashed cm13 official and then for some stupid reason I flash that recovery too.I had twrp before that..so now I got no root I can't flash anything..that root option in dev set don't work...I got d855 and I use Linux.but I tried adb and all that nothing seems to work.. Thanks regardless... It's first time I can't fix that..:/
russiandroidx said:
Can any one help me I think I didn't sleep for 3 days lol..I flashed cm13 official and then for some stupid reason I flash that recovery too.I had twrp before that..so now I got no root I can't flash anything..that root option in dev set don't work...I got d855 and I use Linux.but I tried adb and all that nothing seems to work.. Thanks regardless... It's first time I can't fix that..:/
Click to expand...
Click to collapse
hm... have you adb acess within cyanogenmod recovery? if yes try dd method
Sent from my Xperia T using XDA Free mobile app
Thenx for reply ... What u mean by that... Like inside recovery???if so.. Yes but absolutely nothing works in that recovery..only thing I can do is browse thru the files
SdtBarbarossa said:
hm... have you adb acess within cyanogenmod recovery? if yes try dd method
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Ye but with dd u have to use adb she'll and then "su" command and since I got no root ..I tried
russiandroidx said:
Ye but with dd u have to use adb she'll and then "su" command and since I got no root ..I tried
Click to expand...
Click to collapse
nope... "su" is not necessary when in cm recovery... because you are already superuser within it
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
nope... "su" is not necessary when in cm recovery... because you are already superuser within it
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
But there is no adb in that recovery.. Only thing I seen is when u press on install update but when I press on it says adb cancled..
russiandroidx said:
But there is no adb in that recovery.. Only thing I seen is when u press on install update but when I press on it says adb cancled..
Click to expand...
Click to collapse
do you even know what adb is?
google "minimal adb and fastboot" ... install on pc...
reboot phone to cm recovery and connect to pc
on minimal adb and fastboot type
adb shell
then the dd command for YOUR and ONLY YOUR device (otherwise you will brick it)
Sent from my Xperia T using XDA Free mobile app
russiandroidx said:
But there is no adb in that recovery.. Only thing I seen is when u press on install update but when I press on it says adb cancled..
Click to expand...
Click to collapse
OK there aplly update->from adb or emulator.when I press adb it says adb saidload..but that just bring me right back ina first page of recovery
russiandroidx said:
OK there aplly update->from adb or emulator.when I press adb it says adb saidload..but that just bring me right back ina first page of recovery
Click to expand...
Click to collapse
you dont read what i posted above?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
you dont read what i posted above?
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
. Just seen it... Ye ofcourseci know what adb is .its just I don't Linux kinda comes with it build in already.. But that might actually work.. Since it ina recovery already...thx bud..I'll try when I get home

Categories

Resources