Database Develop

Root Problems

Cant seem to find any possible way to root my G2. I tried Towel root and ioroot25. For the towel root it tells me my device is not supported, fair enough... For the IoRoot however, it goes fine until the reboot part. The command prompt tells me to select an option with my volume/power buttons but all I see is an Android laying on its back with a red exclamation saying "No Command" under it.
I just need some noob friendly help as this is my first android and root attempt.
Heres some info:
-Lg G2 Verizon
-Baseband Version: VS98026A
-4.4.2 android version
Kernel Version: 3.4.0-perf-g95fa932
-im in debug mode
-ethernet mode/option when i connect to my PC
-no lock on screen
-fully charged, ect
I really cant figure out what im doing wrong

You try Stump Root?

FaustM said:
Cant seem to find any possible way to root my G2. I tried Towel root and ioroot25. For the towel root it tells me my device is not supported, fair enough... For the IoRoot however, it goes fine until the reboot part. The command prompt tells me to select an option with my volume/power buttons but all I see is an Android laying on its back with a red exclamation saying "No Command" under it.
I just need some noob friendly help as this is my first android and root attempt.
Heres some info:
-Lg G2 Verizon
-Baseband Version: VS98026A
-4.4.2 android version
Kernel Version: 3.4.0-perf-g95fa932
-im in debug mode
-ethernet mode/option when i connect to my PC
-no lock on screen
-fully charged, ect
I really cant figure out what im doing wrong
Click to expand...
Click to collapse
Have heard stump root works.
If you want to use ioroot25, you have to be on the 24a firmware. You can always kdz back to 24a, root using ioroot25 (don't flash custom recovery yet), take ota to 26a (root is maintained), then flash custom recovery using freedom tool (this was my work flow and worked perfectly).

njstein said:
Have heard stump root works.
If you want to use ioroot25, you have to be on the 24a firmware. You can always kdz back to 24a, root using ioroot25 (don't flash custom recovery yet), take ota to 26a (root is maintained), then flash custom recovery using freedom tool (this was my work flow and worked perfectly).
Click to expand...
Click to collapse
:crying: I dont know what half of that means :crying:
Well i tried stump root and my device isnt supported, all it does is ask for me to brute force it.
I'll try njstein's method later on today and see if that works, I just need to figure out exactly what all that meant. Ill look around in the forums for "kdz to 24a...ota to 26a"
Thanks so much for the help, ill report my results later in the day :good:
Update: Wow i wasnt counting on the brute force to work but it did, device is now rooted.
and on a side note, my proxy settings got all messed up after root, i couldnt connect or do anything over wifi and also my adblock+ was messed up. Easily fixed, just fyi for anyone else that might experience that.

FaustM said:
:crying: I dont know what half of that means :crying:
Well i tried stump root and my device isnt supported, all it does is ask for me to brute force it.
I'll try njstein's method later on today and see if that works, I just need to figure out exactly what all that meant.
Click to expand...
Click to collapse
Read this thread brotha...
http://forum.xda-developers.com/showthread.php?t=2713954

On 24A radio I used ioroot for the first 2 G2's I went through, this third one i used Towelroot and AUTOREC.APK for custom recovery... Root and custom recovery in less then a minute!!!

HELP!! Phone will only boot into recovery!

Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??

Fixed!
Found this thread after a search and reading a thread on the G3.
http://forum.xda-developers.com/showthread.php?t=2451696

Tsip85 said:
Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??
Click to expand...
Click to collapse
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.

mach01 said:
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
Click to expand...
Click to collapse
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.

Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Glad it helped. As for a recovery switcher, you might want to consider using a simple one of the Play Store. They are convenient and easy to use. This thread is really great: http://www.xda-developers.com/simple-recovery-switcher/
Hope this helps.

Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Would you mind sharing that link I need to find my bosses g2 please help

chazla86 said:
Would you mind sharing that link I need to find my bosses g2 please help
Click to expand...
Click to collapse
Yes...check the link I posted on the second post.

Soft brick because of AT&T update?

Just got a update for my LG G Flex D950 from AT&T. I didn't think twice, and hit update. Now my phone will only go to TWRP. I'm using TWRP v2.8.6.0 any suggestions? All I've done is root it, it has the original ROM it came with.

mine is also soft bricked

I was not rooted and the update installed fine. Just curious what it was....
Edit:
Oh wait this explains everything
(Not really, not at all actually)
http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB423840&cv=820
Update summary**
Effective September 17, 2015, AT&T released a software update for the LG G Flex (D950). This update will be available via Firmware Over The Air (FOTA)*using a Wi-Fi connection.****
*
What's changing?
Device security improvements
What to expect after the update**
Although there should be no impacts to settings or data, we recommend that you back up your important files and media prior to upgrading the software.

bryanizmir said:
I was not rooted and the update installed fine. Just curious what it was....
Click to expand...
Click to collapse
My mom, uncle, and I all have the same phone, the only difference is mine is rooted with TWRP, so something with it being rooted, or with TWRP has screwed it up, and I have no idea which it is

try the steps here. scroll down to the terminal commands and that will get you going.
http://www.androidayos.com/2014/10/0...download-mode/
(How to Fix bricked LG G2 stuck in Recovery after taking OTA update
If you have LG G2 rooted and installed with TWRP recovery then suddenly and automatic OTA update came around but then its too late that your phone just stuck in TWRP Recovery. If you bricked your phone after doing an OTA Update with root and TWRP installed and happens that it stuck at recovery. This can be fixed either by installing the official firmware via flashtool using the KDZ file but sometimes your phone can’t boot into Download mode and it won’t connect to the computer, so this could be a very frustrating situation.
Before doing anything else you may first try this, this has been reportedly worked on some LG G2 users at Androidcentral forum and thanks to the folks at XDA-developers for this workaround.
On your TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and reboot.)

I have the same problem. Rooted/TWRM and soft brick.

I get to terminal window, but no keyboard

tap on select when in terminal
---------- Post added at 05:10 PM ---------- Previous post was at 05:05 PM ----------
That should open the keyboard

I don't have select, I have home, back and the icon that put me in the terminal window from the folders

Do you see this?

Full phone

Sonny beach, trying it now

Got it, now how do I get that software update to go away?

Your phone should keep the update... at least mine did

Mine didn't, in fact it just bricked again, because I accidentally hit the update again

Hi Guys, I have the same problem although I have CWM instead of TWRP. I got the D950 ATT version rooted on stock 4.4.2 and the updated came up on my phone yesterday but I kept on clicking remind me later. Until last night I noticed my phone was booted on CWM and when I tried to reboot, it just went back again to recovery. Also tried restoring from my backup, goes normally and completes but after reboot it just goes back to CWM again. I hope there is someone who can help coz I have pictures and files I need from it...

Those same commands should work. Those are Linux commands for the base system

Texas_Dave said:
Those same commands should work. Those are Linux commands for the base system
Click to expand...
Click to collapse
I guess you are right, although I did it via fastboot it still worked and got all my files back. Thanks for the quick reply. And by the way the update notification is still active, do you think I still have to unroot before installing the update or would it be ok not to unroot and just defrost all the bloatwares that came with the stock OS then accept the update? I am just afraid that it might brick my phone if I went through with it...

I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how

Texas_Dave said:
I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how
Click to expand...
Click to collapse
I just wish IOroot had a way to support the G flex on android 4.4.2 so we do not have to go back to JB just to root. At least from KK we only have to do this new software update, then root the device, install recovery and we are good to go. I guess that would be too much to ask right now on a low activity device like ours. For now all I did to stop the update nag, I froze the software update file from Titanium backup rebooted and now the nag is silenced for a while until we get news that it's ok to do the update on our rooted devices running KK.

Flashing from Build Number SU3TL-39 to SU4TL-44

Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!

coconutt said:
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
Click to expand...
Click to collapse
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it. http://www.kingroot.net/
Then download this version of Sunshine and install it. http://forum.xda-developers.com/showpost.php?p=64027688&postcount=4064
Once both are installed, open Kingroot and follow the instructions to try and get temporary root. It doesn't always work, and sometimes you have to try multiple times. If it fails, uninstall Kingroot, reboot the phone and try again. Wiping cache in the recovery menu sometimes helps too.
After Kingroot says it is successful, run Sunshine and follow the prompts. Sunshine costs $25, so if you're not cool with that, don't try this method. If Sunshine succeeds, your phone will reboot and instead of the Motorola M that you usually see at boot, you'll see a bootloader unlocked warning message. If Sunshine fails, uninstall Kingroot, reboot, reinstall and try again.
Once your bootloader is unlocked, you need to get a custom recovery installed (TWRP), which you can get here http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308. The easiest way to flash that in my opinion is with Fastboot. The easiest way to install Fastboot is by installing this: http://forum.xda-developers.com/showthread.php?t=231779. You'll also need to make sure you have the appropriate drivers so that your PC will recognize your phone. This will ensure that: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Once you have that, the sky is the limit. If you only want to add permanent root to your phone, download this: http://forum.xda-developers.com/showthread.php?t=1538053, put it somewhere on your phone, boot into recovery mode (which will now be TWRP instead of the stock recovery), select install, navigate to the .zip file and flash it. That's it. If you want to try cyanogenmod or any other custom rom, see their respective xda threads for details.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
---------- Post added 7th December 2015 at 12:00 AM ---------- Previous post was 6th December 2015 at 11:45 PM ----------
If you need more help, this guy might explain better than I did: http://forum.xda-developers.com/droid-turbo/general/videos-tutorials-root-restoring-droid-t3076456

http://forum.xda-developers.com/showthread.php?t=2317790
Link for minimal adb and fastboot, I think this is the right one?

TheSt33v said:
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
Click to expand...
Click to collapse
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.

coconutt said:
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
Click to expand...
Click to collapse
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here http://theroot.ninja/download.html and use it to unlock once you're on -44.

TheSt33v said:
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here therootdotninja/download and use it to unlock once you're on -44.
Click to expand...
Click to collapse
Well that was easy! Bootloader unlocked!! Thanks.
Now on to the rooting process. Currently getting my Moto drivers updated on the PC, and I've also downloaded the TWRP file onto the PC as well. As for Fastboot, the link you've provided takes me to a 2005 thread! I'm sure I can find a link to Fastboot to download, but I wanna make sure I get the one I need, if that makes any sense? (Don't mind me being paranoid)

TheSt33v said:
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Click to expand...
Click to collapse
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!

coconutt said:
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
Click to expand...
Click to collapse
If you want twrp flashify works well.

LG Optimus L90 Root problems. HELP

Hello all. I Recently attempted rooting my phone, running on 5.0.2, and it seemed to have worked. But then after attempting to use SuperSU to add root permissions to an app, my screen went black, and the only thing visible was the top status bar, which had some animations still running (Like the battery icon filling up or the signal bars changing), but thats it. It wasn't responsive to any of my button presses, and then it shut off. It keeps doing this over and over, and i cant keep the phone on for more than 5 mins maybe 10. How would I fix this? I used this "tutorial". - andromods .com/news-root/lg-g3-g-flex-2-g2-lollipop-one-click.html - (Stupid thing wont let me post links)
I would like to solve this without factory resetting, as I have apps that have data on them that needs to be transferred from one phone to another, and i dont have a second phone to transfer to at the moment.
Thanks in advance.

As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...

lfom said:
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
Click to expand...
Click to collapse
I'm very new to this, and probably shouldnt have attempted this without knowing more, so I have no idea what you are asking me. What is ADB root (shell)? I probably dont have it. And I didnt do any sort of custom recovery. But it seems that me messing around with SuperSU (clicking the uninstall root/turning of superuser once or twice) seems to have stopped the crashing all together. Ive been using my phone since and it hasnt crashed. Whether or not that's fixed the real issue, I don't know. And I'm not sure I want to mess with it further. :crying: