If you take the ZVE update, IORoot no longer works. You must use Stump Root method
According to @autoprime, you must use the Stump Root method in order to root the ZVE update
http://forum.xda-developers.com/sprint-g2/general/ls980-zve-ota-zip-update-zvc-zve-t2912488
Stump root can be found here
http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
It has been confirmed by many that the IO root now works on the LS980 though it is not listed in the main IO root thread. Below is a link with all the specific instructions for how to use this root tool.
http://forum.xda-developers.com/showthread.php?t=2448887
Basic Instructions for rooting on firmware ZVA
1. 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).
NOTE: If you do not have the USB drivers installed, you can get them from here: http://www.lg.com/us/support-mobile/lg-LGD801BK under MANUALS & DOWNLOAD -> Software Update -> USB Drivers (Yes the Tmobile drivers work since the Sprint page doesn't post USB drivers)
2. Enable Developer Mode (Press "Build Number" 7 times) on your phone and enable USB Debugging
3. Extract ioroot zip file somewhere on your PC
4. Plug your phone into your PC. Ensure that the USB connection is set to "Charge Only".
5. On PC, open up command prompt and type adb devices command and accept the ADB RSA command on the phone. It should say "LG-LS980-XXXXXXXXXXX device" If you saw the following it confirms that the device is detected in ADB.
6. Put your phone in Airplane mode.
7. Run root.bat
8. The script will ask you that the USB Connection Mode needs to be toggled. Toggle USB mode from Charge Only to MTP and then back to Charge Only.
9. You will then be asked if you would like to have a superuser package installed, which you can accept or decline
10. Download Root Checker from Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck to verify successful root.
Basic Instructions for rooting on firmware ZVC with IO Root v25
1. 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).
NOTE: If you do not have the USB drivers installed, you can get them from here: http://www.lg.com/us/support-mobile/lg-LGD801BK under MANUALS & DOWNLOAD -> Software Update -> USB Drivers (Yes the Tmobile drivers work since the Sprint page doesn't post USB drivers)
2. Enable Developer Mode (Press "Build Number" 7 times) on your phone and enable USB Debugging
3. Extract ioroot zip file somewhere on your PC
4. Plug your phone into your PC. Ensure that the USB connection is set to "Charge Only".
5. On PC, open up command prompt and type adb devices command and accept the ADB RSA command on the phone. It should say "LG-LS980-XXXXXXXXXXX device" If you saw the following it confirms that the device is detected in ADB.
6. Run root.bat
7. When phone boots into recovery, select 'apply update from ADB' with power button.
8. Reboot phone into system.
10. Download Root Checker from Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck to verify successful root.
Download the latest version of IO Root (6/17/14 build) from @autoprime's post below:
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
YOU MUST USE IOROOT v25 or later if you are on the ZVC (Android 4.4.2) firmware update.
Here is a tutorial video explaining how to install IO Root:
http://www.youtube.com/watch?v=Y45SXPRb31o
I am not the creator of this root method i am simply compiling the information for sprint users since it is scattered in many different places.
Credits go to @autoprime and thank him for maintaining and updating the IO Root method as new updates come up and @thecubed for creating the IO Root method.
Univsoldur said:
It has been confirmed by many that the IO root now has an area for the LS980 though it is not listed in the main IO root thread. below is a link with all the specific instruction for how to use this root tool.
http://forum.xda-developers.com/showthread.php?t=2448887
This is a link to the area for the file that you will use in conjunction with the instructions from that thread. The link that they provide does not link to IO root version 11.
http://downloads.codefi.re/shelnutt2/g2/spr
According to ericdabbs this file works with the IO root method.
http://forum.xda-developers.com/showpost.php?p=47339494&postcount=3
I am not the creator of this root method i am simply compiling the information for sprint users since it is scattered in many different places.
Click to expand...
Click to collapse
anyone try this yet? is there any reason to do this over the other root method?
I did i just prefer methods developed by xda members specifically for our phones.
Sent from my LG-LS980 using Tapatalk
I'm worried that Sprint will issue an update soon, as carriers often do quickly after the launch of a new product, and we won't be able to get it with a rooted phone. Not sure whether to root or not, and if so how long to wait.
TheSapient said:
I'm worried that Sprint will issue an update soon, as carriers often do quickly after the launch of a new product, and we won't be able to get it with a rooted phone. Not sure whether to root or not, and if so how long to wait.
Click to expand...
Click to collapse
You can always unroot if the an update won't take. The only time this has been an issue for me is when I'm running something other than the stock ROM. The downside about OTA's is they break root most of the time, so you'll have to root your device again.
I used this method to root. The only problem I had was where it said to disable USB debugging and reconnect the phone. After I did that it wouldn't connect and complete the superuser install. I tried all the USB connections types; charge only, mtp, & ptp, but the adb interface wouldn't show up in device manager. I finally just re-enabled USB debugging and the install process continued without any problem. Everything seems OK, superuser is installed, I was able to install TWRP and I'm doing a Titanium backup right now.
Does anyone think there will be a mod released later on to "untrip" the built in root checker? I'm holding off on rooting based only on that.
rich_e said:
I used this method to root. The only problem I had was where it said to disable USB debugging and reconnect the phone. After I did that it wouldn't connect and complete the superuser install. I tried all the USB connections types; charge only, mtp, & ptp, but the adb interface wouldn't show up in device manager. I finally just re-enabled USB debugging and the install process continued without any problem. Everything seems OK, superuser is installed, I was able to install TWRP and I'm doing a Titanium backup right now.
Click to expand...
Click to collapse
I'll give you an explanation why it didn't work for you initially and how your accidental discovery was what fixed it.
The instructions in the root.bat file said to do after it pushed the initial files into the phone was
1. Unplug the phone off USB from PC
2. Disable USB debugging option
3. Re-enable USB debugging option
4. Connect phone to USB from PC.
What you did initially was steps 1, 2 and 4 and skipped 3 and expected the root.bat script to continue. Obviously the root.bat file can't detect the phone once you reconnected it to USB because you don't have USB debugging on which is needed for detection. What you did eventually was the smart thing and re-enable the USB debugging that finished the install process.
This is the excerpt from the root.bat file that clearly explains to disable USB debugging and immediately re-enable USB debugging after the root.bat file pushes the initial root files.
echo *******************************************************
echo Now, please unplug usb, go to developer options and
echo disable USB debugging and re-enable it.
echo Once you've done that, re-plug your usb...
echo *******************************************************
This root works 100%. I compared the iorootv10 and iorootv11 root.bat files and it clearly did not have a Sprint option for the root.bat file to detect in iorootv10. Also this was released by a recognized developer/contributer shelnutt2. I hope thecubed edits his XDA thread to upload iorootv11 so that we can reference that XDA thread instead.
Mine stays stuck on "looking for device" ... Any tips?
o0adam0o said:
Mine stays stuck on "looking for device" ... Any tips?
Click to expand...
Click to collapse
Did you ensure you have enabled USB debugging and installed the USB drivers? Also if you have adb, try opening a command prompt in the same folder as adb and type "adb devices". You should see a response of your device listed and "device". If you see a response of a device listed and "offline" that means your phone is not communicating with your PC which is why the root.bat file is giving you an error.
Check out this tutorial video for the ioroot and it should make it more clear. Keep in mind that the video was made when iorootv10 was released but the steps to do the root are the same.
http://www.youtube.com/watch?v=Y45SXPRb31o
Make sure you are downloading the iorootv11 files here that includes the Sprint version: http://downloads.codefi.re/shelnutt2/g2/spr
Here is the link to the USB Drivers in case you need it. It is from the ATT and Tmobile version from the LG website but it works fine. Scroll down the page to Software Update tab and download USB driver.
http://www.lg.com/us/support-mobile/lg-D801
o0adam0o said:
Mine stays stuck on "looking for device" ... Any tips?
Click to expand...
Click to collapse
If you haven't installed the drivers use these.
LG United Mobile Drivers
http://d-h.st/EW4
Edit: was already answered in the post ahead of mine. This file is a direct download.
ericdabbs said:
..
Click to expand...
Click to collapse
removed for less confusion
Univsoldur said:
Could you put together something that references the correct places for sprint users to install recovery. I haven't flashed it yet though I think this is correct. I thought since you had already you would prolly know best and could explain it to people easier than me.
http://www.teamw.in/project/twrp2/197
Click to expand...
Click to collapse
Actually I haven't installed TWRP on my G2 yet.
However I intend to follow WACOMalt's method located here:
http://forum.xda-developers.com/showthread.php?t=2449670
You need to download the Sprint TWRP Recovery file here: http://techerrata.com/browse/twrp2/g2spr
WACOMalt also posted a tutorial video on how to flash recovery using his method shown here:
http://www.youtube.com/watch?v=OZSjL6FCyxA
ericdabbs said:
..
Click to expand...
Click to collapse
removed for less confusion
Univsoldur said:
yea i know thats the correct recovery image but i dont have adb set up on this PC and was wondering if i could do it using terminal emulator. Either way I wont clutter this thread up with recovery because I know people will get confused so I will create a new thread.
Click to expand...
Click to collapse
Please create a new thread so that I can have you post the adb/fastboot files for download. Its very important to have adb and fastboot files installed on your PC if you intend to do Android hacking.
ericdabbs said:
Please create a new thread so that I can have you post the adb/fastboot files for download. Its very important to have adb and fastboot files installed on your PC if you intend to do Android hacking.
Click to expand...
Click to collapse
its up im gonna remove these previous posts
Univsoldur said:
its up im gonna remove these previous posts
Click to expand...
Click to collapse
Can you update the OP for this thread to include reference to the ioroot tutorial video.
http://www.youtube.com/watch?v=Y45SXPRb31o
Also can you remove the reference to me confirming the root works in the OP. I don't think its necessary to have that since we know ioroot is a trusted root method.
Anyoneknow how to disable system updates.
Sent from my LG-LS980 using Tapatalk
Univsoldur said:
Anyoneknow how to disable system updates.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I am not sure. That would be very handy in case Sprint wants to push out an OTA. We know that eventually Sprint is going to get an OTA in early 2014 to enable triband LTE or Sprint Spark.
At this point, I am more interested in leroybrute's message that wifi tether works on the Sprint version.
Used this and flashify to install twrp took less than 5 minutes bring on the ROMS
Sent from my LG-LS980 using XDA Premium 4 mobile app
Related
Hi folks, this is my first post so I apologize in advance for any protocol I might be breaking.
My goal is to be able to flash some of the awesome new ICS ROMs that have been developed. I was able to successfully install the rooted TAR of FC24 provided by sfhub http://forum.xda-developers.com/showthread.php?t=1573752 by utilizing ODIN. My next step was to use the auto root also provided by sfhub http://forum.xda-developers.com/showthread.php?t=1342728 to flash CWM. I have not yet been able to get my E4GT to accept the install.
I have been met repeatedly by this error:
Getting ready to
INSTALL BootImg - FC24+CWM-Rogue (requires ROOT)
Please verify ALL of the following:
USB Debugging is ENABLED
USB Storage Mode is DISABLED
Samsung USB/Android drivers are INSTALLED
Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you *MIGHT*
see a PROMPT asking for permissions. If so, please ALLOW root access.
Press any key to continue . . .
error: device not found
---- BEGIN LOG ----
BOOTIMGNAME = FC24+CWM-Rogue
BOOTIMGFILE1 = zImage-fc24
BOOTIMGFILE2 = zImage-fc24-cwm-rogue
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-fc24-cwm-rogue.sh
...Proceeding to copy necessary files...
error: device not found
push: copy2sd-img/000root/zImage-fc24 /sdcard/000root/zImage-fc24
error: device not found
push: copy2sd-img/000root/zImage-fc24-cwm-rogue /sdcard/000root/zImage-fc24-cwm-
rogue
error: device not found
----
error: device not found
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache. If you are using ICS you will see a status
screen mentioning Android is upgrading during this process.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!
Are you trying to say it didn't install CWM? Did you try to boot into recovery yet and see what happens?
Try uninstalling drivers then reinstall and reboot computer
Sent from my SPH-D710 using Tapatalk 2 Beta-4
Honestly, sfhub is a great guy, very helpful with all of his stuff, I might even pm him with that same post and info.
Sent from my calculator watch.
da8vii said:
Hi folks, this is my first post so I apologize in advance for any protocol I might be breaking.
My goal is to be able to flash some of the awesome new ICS ROMs that have been developed. I was able to successfully install the rooted TAR of FC24 provided by sfhub http://forum.xda-developers.com/showthread.php?t=1573752 by utilizing ODIN. My next step was to use the auto root also provided by sfhub http://forum.xda-developers.com/showthread.php?t=1342728 to flash CWM. I have not yet been able to get my E4GT to accept the install.
I have been met repeatedly by this error:
Getting ready to
INSTALL BootImg - FC24+CWM-Rogue (requires ROOT)
Please verify ALL of the following:
USB Debugging is ENABLED
USB Storage Mode is DISABLED
Samsung USB/Android drivers are INSTALLED
Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you *MIGHT*
see a PROMPT asking for permissions. If so, please ALLOW root access.
Press any key to continue . . .
error: device not found
---- BEGIN LOG ----
BOOTIMGNAME = FC24+CWM-Rogue
BOOTIMGFILE1 = zImage-fc24
BOOTIMGFILE2 = zImage-fc24-cwm-rogue
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-fc24-cwm-rogue.sh
...Proceeding to copy necessary files...
error: device not found
push: copy2sd-img/000root/zImage-fc24 /sdcard/000root/zImage-fc24
error: device not found
push: copy2sd-img/000root/zImage-fc24-cwm-rogue /sdcard/000root/zImage-fc24-cwm-
rogue
error: device not found
----
error: device not found
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache. If you are using ICS you will see a status
screen mentioning Android is upgrading during this process.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!
Click to expand...
Click to collapse
Couple things to try. Were you able to boot into the rooted FC24 you flashed via Odin? If that won't even boot you will need to reflash that. That has to be working. If it doesn't boot you might want to re-download the tar/exe that says 'RESET user data' option - you can't/shouldnt use the 'NoData' when going from GB to ICS. Run that and make sure the phone boots. Also maybe re-download the e4gtauto package, possible a bad/incomplete download. Then once your sure you phone boots turn it off and go into download mode and run the e4gtauto package again.
Also and this is so freaking important I can't overstate it: Try a NEW AND GOOD USB cable. I personally have had problems that I could have solved in seconds (by using a different cable) take me hours! Just had a 'good' amazon cable fail me this week - trying to get my nandroids off my SD card to my PC and copy over new ROM zips; device would not be recognized. I resinstalled samsung drivers, kies, rebooted systems (phones and computers) and other crap. Then took my own flippin advice pulled a new USB cable out of my drawer and BAM device recognized. Sometimes simple should be done first. Good luck!
da8vii said:
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!
Click to expand...
Click to collapse
I don't think your issue has to do with USB Storage since as you noticed, there is no UI to enable mass storage mode and by default it is off (actually it can't be turned on by default on FC22/FC24 because the USB port is set to MTP mode and the USB utilities UI is removed)
I've actually never seen it pass the "Found Device" stage and then later on come up with an "error: device not found" Usually it will stay waiting for the device if there is something wrong with the connection.
Can you get an "adb shell" session started? If you can get that working, then everything should work. If you don't know how to start "adb shell", use Option E (Extra Options) followed by Option G (adb shell)
Once you start the adb shell session, also verify the /sdcard is mounted properly by typing
Code:
ls -l /sdcard
and making sure the contents look like what is on your /sdcard (ie it shouldn't be an empty directory)
Alternative: Buy Mobile Odin from Android Playstore, aka the market...put el26 cwm tar here: http://db.tt/rIxjBIk8 on your sdcard. Flash cwm el26 using Mobile odin and at "First Samsung screen " after boot hold volume up and power button until you see recovery... Then, flash your choice of ics rom.. (at your own risk of course) I do this daily and I have had to go back to gingerbread a few times from ics, and omw back to ics this is what I do... Works perfect! Just make sure you have whatever zips you want to flash on sdcard previous to this.. Sure you know all that...You can repeat this method every time you flash another ics rom... I do, and have about 100 times already. Lol. For real!
I know this is a little late, but Happy flashing!!
You can read about Mobile Odin here: http://forum.xda-developers.com/showthread.php?t=1347899 and here: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en
Sent from my SPH-D710 using Tapatalk 2 Beta-5
There is some driver or USB issue where "ADB" cannot see your phone. This is a standard android sdk tool that Auto Root is using to copy files to your phone.
There are various things you could try. Personally I think you should figure out why adb isn't recognizing your phone as it will help you in the future, especially if you get in some binds, but the quickest way to get CWM installed is to just download the Auto Root zip file to your phone. Then use Mobile ODIN to flash one of the zImage files contained in the copy2sd-img/000root directory in the zip file. You are basically treating the auto root zip file as a complete archive of every stock and cwm recovery that was released for this phone.
Alternatively you could also use the manual instructions in the 2nd post of the auto root thread. The only thing ADB is really being used for in the case of installing cwm is copying files to your phone. Everything else is being handled by scripts that run on the phone itself, which can be done on a terminal running on the phone.
If you want to figure out what is wrong with adb, I can help with that also and I'm sure you'll eventually figure it out, it'll just take a little more time.
First thing I would go over is this troubleshooting post:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Also make sure you are booted into Android rather than Recovery. Stock recovery doesn't enable the ADB interface. Also make sure USB debugging is enabled.
Ok a couple of things. first of all make sure you have your drivers working properly. I'm sure they're good since you rooted..but you never know. Next make sure that when you connect the USB that you don't go into USB mode on your phone. Just plug it up but when your phone asks if you want to connect the USB to share files don't press ok. Make sure system debugging is enabled and accept unauthorized software is checked. Then it should recognize your device.
Hi All,
I just received a used Galaxy Nexus from a buddy and wanted to root and flash it up to 4.2. It is currently at 4.1.1 JRO030.
Everything seems to work fine (phone is not activated yet - no SIM - still need to transfer number), but other than that all is a go. I can see the phone via ADB in Linux and Windows. When I boot in to the bootloader though fastboot will not see the device. The volume keys do not change the menu (stays on START) and I have to pull the battery to reboot. The bootloader does show as being unlocked.
I have tried factory Reset (multiple times)
Linux and Windows - SDK
Wug's Nexus Root ToolKit - followed all the instructions from multiple sources.
Again - ADB works and sees the device and I can use "adb reboot bootloader" with no problem. When the bootloader comes up (either via ADB or 3-button power up) I am stuck.
Any help is appreciated.
Pax,
Arklazak
Make sure u are in USB debugging and make sure the drivers are installed right on your computer.
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Make sure u are in USB debugging and make sure the drivers are installed right on your computer.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply.
The USB Debugging is enabled (first thing I did as I have unlocked and rooted other devices) and USB drivers are correct and working since ADB sees the device correctly. Also, it is my understanding that USB Debugging does not apply when the bootloader is up.
One thing I just noticed in Windows (XP) is that when the phone reboots into the bootloader, the ADB devices go away in device manager.
Any idea why the bootloader is unresponsive - seems locked. It seems as if the bootloader is not loading completely - since the volume buttons do not work and a battery pull is necessary.
Pax,
Arklazak
This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.
g_what said:
This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.
Click to expand...
Click to collapse
Thanks g_what. I will look at it and try it out this weekend - on the road for work right now - and report back. On the plus side, I have been able to get the phone rooted (from Linux) without the bootloader - thanks to efrant's thread here: http://forum.xda-developers.com/showthread.php?t=1894717
I still want to get the everything up to snuff.
Pax,
Arklazkak
You can unlock the bootloader without fastboot when the phone is off using OMAP: http://forum.xda-developers.com/showthread.php?p=41612401#post41612401
im experiencing the same issue
wug fresh cant detect fastboot ... drivers are installs correctly and adb is recognized and i can access fastboot through command prompt .. any suggestions?
its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me
get this: [Toolkit] Wug's Nexus Root Toolkit v2.02
It has a guide for the folder you have, under: Initial Setup > Full Driver Installation Guide... > Step 3 > Driver Solution # > Manual Configuration.
coolncool said:
its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me
Click to expand...
Click to collapse
...
You should be asking these questions on a Windows forum.
You need to right click Android 1.0 device... Update Driver (basically, tell Windows Device Manager that the driver for the "Android 1.0" device is in that folder you got there)... it will install it, and that part is done. Then reboot the device to fastboot mode and manually update the driver again (it will come up as a different, yet again unknown device, you just feed it the same driver again)
Also... for the operations you're mentioning... "root, unlock bootloader, install cwm, flash rom".... you probably won't even need ADB, just fastboot. As in, you don't need to root before all that. You root in the end. And most custom roms are already rooted too.
This is assuming there's an exploit out there that still allows for root to be achieved without unlocking the bootloader.
I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).
creaky said:
I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).
Click to expand...
Click to collapse
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.
Do you have installed the android sdk?
creaky said:
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.
Click to expand...
Click to collapse
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices
uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
wadamean said:
Do you have installed the android sdk?
Click to expand...
Click to collapse
I had to reinstall - that was the problem. Thanks!
uly609 said:
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices
Click to expand...
Click to collapse
Thanks again for the help. Problem solved.
Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.
wadamean said:
Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.
Click to expand...
Click to collapse
Not root, used Debloater tool to block updates. Would love to see a Mac root method released.
oh i see then. i will keep patiently waiting for a simpler root method. this one is already but for sure there has always been even more simpler methods surfaced.
I investigated the ADB program. At How to Install ADB on Windows, macOS, and Linux, I am stuck at step 7 of the instructions for windows. I do not receive any kind of pop up in my SMJ200G phone (j2).
This step:
7. On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).
Click to expand...
Click to collapse
Perhaps my PC's connection to the phone is buggy, not the cable, but the software? by software I mean Windows/PC not my phone.
btw does file AdbWinUsbApi.dll need to be installed?
Are the following applicable for a official device that have never been rooted:
NVCore said:
-Missing ADB Confirmation Dialog(can be bypass by placing adb_keys(from PC/Laptop that has platform-tools and the file name is adbkey.pub, rename it to adb_keys) move the file to device (/data/misc/adb)
Click to expand...
Click to collapse
mbalino said:
Unable to detect the phone -win nor Lin
Hello guys
Something really extrange is happening.
My j2 prime -532G- can't be detected by Windows nor Linux.
The usb is working because it charges the phone, but I can't access the phone at all. I checked all the drivers in Win -google/adb and samsung- and in Linux libmtp/heimdall/etc.
I have tryed different usb -not the original one since i lost it-
Even when i start the download mode, nothing happens.
it there a way to root the phone without a PC? i have tryed also kingroot apk but it is useless.
Thanks
Click to expand...
Click to collapse
citation