I am trying to root my Verizon Galaxy Note 2 SCH-I605 via Casual R515, I am running win7 x64. I got the phone into USB debugging and connected the phone to my PC using the samsung cable that came with the phone. I clicked "Do It". The program showed "connected" and proceeded. The phone restarted and threw a critical error. Since I cant seem to paste it below. I have attached it as a txt file. Also, the phone seems to be uneffected and works fine now but it is not rooted.
Any and all assistance is greatly appreciated.
_keith
mcinvalek said:
I am trying to root my Verizon Galaxy Note 2 SCH-I605 via Casual R515, I am running win7 x64. I got the phone into USB debugging and connected the phone to my PC using the samsung cable that came with the phone. I clicked "Do It". The program showed "connected" and proceeded. The phone restarted and threw a critical error. Since I cant seem to paste it below. I have attached it as a txt file. Also, the phone seems to be uneffected and works fine now but it is not rooted.
Any and all assistance is greatly appreciated.
_keith
Click to expand...
Click to collapse
I am not adept at reading Casual logs and have never done so before but before that critical error showed up it shows that the user canceled the process. Maybe you did so inadvertently? I may also be wrong.
What update are you on? Are you on VRAMC3 or one of the previous updates?
Have you tried using Casual again since this error? If not you should give it another try and pay close attention to it this time while it's running. If it messes up again pay the log from it too.
Sent from my SCH-I605 using XDA Premium HD app
eparsas canons
shangrila500 said:
I am not adept at reading Casual logs and have never done so before but before that critical error showed up it shows that the user canceled the process. Maybe you did so inadvertently? I may also be wrong.
What update are you on? Are you on VRAMC3 or one of the previous updates?
Have you tried using Casual again since this error? If not you should give it another try and pay close attention to it this time while it's running. If it messes up again pay the log from it too.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the reply. I am on VRAMC3, I just purchased the phone on 5/24/13. I ran the process again. I have attached the log as "casual log2". I began the process and the phone went into download mode and then proceeded to the first reboot. It seems to fail when the phone reboots. A small snippet of the log below seems to communicate that 'LIBUSB' is throwing an error of not supported. I am not sure what that means. For what it is worth. I have tried this process a few times and have used different USB ports on my desktop. Each time using the USB cable that came with the phone.
[INFO]
[Heimdall Error Report] Detected:
'LIBUSB_ERROR_NOT_SUPPORTED'; Attempting to continue
[/Heimdall Error Report]
You need to install a different driver for hedimal. In the original post, there is a link to a single post for the drivers and how to install. I had the same error process.
Sent from my SCH-I605 using Tapatalk 4 Beta
aerichards1977 said:
You need to install a different driver for hedimal. In the original post, there is a link to a single post for the drivers and how to install. I had the same error process.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
In addition to what aerichards wrote, I'm posting a video that explains the entire process along with the driver that is needed to install
http://www.youtube.com/watch?feature=player_embedded&v=e5stlbQ3Ysw
AngryGibson said:
In addition to what aerichards wrote, I'm posting a video that explains the entire process along with the driver that is needed to install
AngryGibson said:
In addition to what aerichards wrote, I'm posting a video that explains the entire process along with the driver that is needed to install
It worked!!! Much thanks and appreciation to shangrila500, eparsas canons, and aerichards1977. It was a drivers issue. For any future readers that run into the same problem. I cant post a link yet as I am a noob. But I will spell out the URL location.
libwdi
Windows Driver Installer library for USB devices
sourceforeget libwi and the name is zadig v2.0.1.160.7z
Regards,
_keith
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Trying to use Casual on my stock SCH-1605. Casual sees the device, starts the process after "Do It", but seems to stop at "initialising protocol" and hangs (10 minutes so far).
Log document attached.
Running on Windows 7 Pro.
Thanks,
Chris
ive tried everything even the posts before mine and downloaded the drivers and still ive gotten the causal error reading error with sch-I605VRAMC3 parsing command . i attached a txt file to show the error
mcinvalek said:
AngryGibson said:
In addition to what aerichards wrote, I'm posting a video that explains the entire process along with the driver that is needed to install
AngryGibson said:
In addition to what aerichards wrote, I'm posting a video that explains the entire process along with the driver that is needed to install
It worked!!! Much thanks and appreciation to shangrila500, eparsas canons, and aerichards1977. It was a drivers issue. For any future readers that run into the same problem. I cant post a link yet as I am a noob. But I will spell out the URL location.
libwdi
Windows Driver Installer library for USB devices
sourceforeget libwi and the name is zadig v2.0.1.160.7z
Regards,
_keith
Click to expand...
Click to collapse
where did you put that driver at so causal could read it ?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I had a similar problem where casual actually cause my drivers not to work, tried deleting all of my drivers and causals drivers but I had to remove them from registry too because windows kept assigning the wrong drivers to my device and odin / casual wouldn't pick them up. The best part is that I got the yellow triangle and had to wait to be able to use my phone.
Did you ever get by this error? I'm having the same problem.
I am getting this same LIBUSB_ERROR_NOT_SUPPORTED error. Have tried everything I know how to and can't get by it.
mcinvalek said:
Thank you for the reply. I am on VRAMC3, I just purchased the phone on 5/24/13. I ran the process again. I have attached the log as "casual log2". I began the process and the phone went into download mode and then proceeded to the first reboot. It seems to fail when the phone reboots. A small snippet of the log below seems to communicate that 'LIBUSB' is throwing an error of not supported. I am not sure what that means. For what it is worth. I have tried this process a few times and have used different USB ports on my desktop. Each time using the USB cable that came with the phone.
[INFO]
[Heimdall Error Report] Detected:
'LIBUSB_ERROR_NOT_SUPPORTED'; Attempting to continue
[/Heimdall Error Report]
Click to expand...
Click to collapse
I am facing same problem
mcinvalek said:
AngryGibson said:
In addition to what aerichards wrote, I'm posting a video that explains the entire process along with the driver that is needed to install
AngryGibson said:
In addition to what aerichards wrote, I'm posting a video that explains the entire process along with the driver that is needed to install
It worked!!! Much thanks and appreciation to shangrila500, eparsas canons, and aerichards1977. It was a drivers issue. For any future readers that run into the same problem. I cant post a link yet as I am a noob. But I will spell out the URL location.
libwdi
Windows Driver Installer library for USB devices
sourceforeget libwi and the name is zadig v2.0.1.160.7z
Regards,
_keith
Click to expand...
Click to collapse
Keith- I am facing same problem. Can you please guide me?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Casual Log
mcinvalek said:
I am trying to root my Verizon Galaxy Note 2 SCH-I605 via Casual R515, I am running win7 x64. I got the phone into USB debugging and connected the phone to my PC using the samsung cable that came with the phone. I clicked "Do It". The program showed "connected" and proceeded. The phone restarted and threw a critical error. Since I cant seem to paste it below. I have attached it as a txt file. Also, the phone seems to be uneffected and works fine now but it is not rooted.
Any and all assistance is greatly appreciated.
_keith
Click to expand...
Click to collapse
5221 KB/s (96260 bytes in 0.018s)
Pushing SuperSU app...
4443 KB/s (996704 bytes in 0.219s)
Pushing Exynos-Abuse exploit
[CRITICAL]1
1
java.lang.ArrayIndexOutOfBoundsException: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
A critical error was encoutered. Please copy the log from About>Show Log and report this issue
[CRITICAL]CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:73)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
... 2 more
Casual Error Log after reboot Whats going on??
Related
QUESTION!
Good evening all. I'm brand spankin' new to this and have a question (which is more of an issue ).
So..
Rooted my Prime, and the "Unlock Device Tool" gives me the following error message: "An unknown error occurs, which may be a network connection issue. please wait and try again later".
Now, I've installed everything correctly and noticed a similar thread regarding this, but the verbatim of the error message was different. I'm unable to boot into recovery--when I do, the Android falls down with an exclamation mark coming out of his chest. Poor guy, must be painful..
Anyway, can anyone lend me a hand?
Thanks in advance.
Maybe you should install CWM recovery first...
You can use ROMManager to do this.
Oh and we guys here in these forums love to see actual thread titles...
Oh and we love to have threads in the right section too...
Diamondback is correct, we do like thread titles.......but I would also try looking to make sure when you have your prime plugged in via usb to your computer that you have the correct drivers installed I had that issue as well till I put the right drivers in. I used the naked drivers posted here works great has I have 4 android devices and it doesnt require to reinstall a driver for each device everytime you connect the device to the computer.
http://forum.xda-developers.com/showthread.php?t=1426502&highlight=naked
And boom goes the dynamite..
I apologize, gentleman..I thought I had constructed an appropriate thread title and posted in the correct forum. Apparently, I was mistaken.
Regardless, your suggestion (Ultraman666) did the trick. I really appreciate your help! Thanks a bunch! Huge help. Pumped.
Awesome glad to help at one point or another we have all been there!!!!
Sent from my Transformer Prime TF201 using Tapatalk
Hey There
Also a noob here. I was wondering what you did KMayock87.
I'm having the exact same issue with my Transformer Prime. I've got no issues with getting OTA's and my serial number is showing up and valid. But when I try to Unlock, always the same message for a month now.
Laubot said:
Hey There
Also a noob here. I was wondering what you did KMayock87.
I'm having the exact same issue with my Transformer Prime. I've got no issues with getting OTA's and my serial number is showing up and valid. But when I try to Unlock, always the same message for a month now.
Click to expand...
Click to collapse
The same question with this guy!
Laubot said:
Hey There
Also a noob here. I was wondering what you did KMayock87.
I'm having the exact same issue with my Transformer Prime. I've got no issues with getting OTA's and my serial number is showing up and valid. But when I try to Unlock, always the same message for a month now.
Click to expand...
Click to collapse
duy_ctytvxdkg said:
The same question with this guy!
Click to expand...
Click to collapse
Ultraman666 said:
Diamondback is correct, we do like thread titles.......but I would also try looking to make sure when you have your prime plugged in via usb to your computer that you have the correct drivers installed I had that issue as well till I put the right drivers in. I used the naked drivers posted here works great has I have 4 android devices and it doesnt require to reinstall a driver for each device everytime you connect the device to the computer.
http://forum.xda-developers.com/showthread.php?t=1426502&highlight=naked
Click to expand...
Click to collapse
The issue was bad drivers. Download the naked drivers utility, duly linked by Ultraman666, and follow through with whatever it needs and you should be fine.
-----------------------------------------------------
BTW, OP, as stated a little more in the title will pull more people that know what's up to the thread. As it is right now you're just catching us Curious Georges. Anyway, welcome, glad the issue is solved!
buxtahuda said:
The issue was bad drivers. Download the naked drivers utility, duly linked by Ultraman666, and follow through with whatever it needs and you should be fine.
-----------------------------------------------------
BTW, OP, as stated a little more in the title will pull more people that know what's up to the thread. As it is right now you're just catching us Curious Georges. Anyway, welcome, glad the issue is solved!
Click to expand...
Click to collapse
It's a wrong point bro.
May I explain:
Already upgrade .21
Now, if I want to root I have to do some steps:
1. Unlock bootloader
2. Install CVW
3. downgrade to .15 via CVW
4. Root with viperMOD PrimeTime v4.5
Normally, step 1 will run without any issue. this time always receive this error:
"An unknown error occurs, which may be a network connection issue. please wait and try again later"
It only run on the tablet, no need to connect to PC so I'm quite sure it not the driver problem.
duy_ctytvxdkg said:
It's a wrong point bro.
May I explain:
Already upgrade .21
Now, if I want to root I have to do some steps:
1. Unlock bootloader
2. Install CVW
3. downgrade to .15 via CVW
4. Root with viperMOD PrimeTime v4.5
Normally, step 1 will run without any issue. this time always receive this error:
"An unknown error occurs, which may be a network connection issue. please wait and try again later"
It only run on the tablet, no need to connect to PC so I'm quite sure it not the driver problem.
Click to expand...
Click to collapse
Got ya. So you're voiding warranty just as a round-a-bout for root?
I'm not sure what the issue would be, and ASUS doesn't seem too keen on providing support even for the unlock utility. Keep looking around, maybe try PM'ing Gary from one of his stickies; let us know if you find a solution.
buxtahuda said:
Let us know if you find a solution.
Click to expand...
Click to collapse
I've just returned it to store
Tried out both these sets of instructions:
http://androidadvices.com/root-motorola-atrix-4g-45141-gingerbread-236-firmware/2/
http://www.androidauthority.com/atrix-4g-android-2-3-6-firmware-4-5-141-root-63533/
None of them since I can't even get past step one with the command lines. The command prompt won't recognize either saying "[name] is not recognized as an internal or external command, operable program, or batch file.
When I rooted while I was using 2.3.4, I had no issues doing it manually this way. I'm at my wits end. Don't know if it's a problem on my end or just the result of Motorola intentionally trying to make it hard to root and unlock this phone(apparently rooting also voids the warranty with them).
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
moto-fastboot.exe flash preinstall preinstall.img
Click to expand...
Click to collapse
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
octahedron said:
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
Click to expand...
Click to collapse
Did you try just fastboot instead of moto-fastboot? I had to use fastboot the other day and that held me up. But if its waiting for devices then it possibly is a driver issue. Im on the xda app so going to the link you provided wont work for me. Trying uninstalling and reinstalling the drivers.
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
octahedron said:
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
Click to expand...
Click to collapse
Go to device management of the computer and under usb should be your phone (when plugged in). If you aren't seeing it, then the drivers didn't install correctly. I can't remember where I got my drivers from to point you in the direction for that.
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Just to clarify the one I'm referring to is "Motorola ADB Interface". "MB860" has everything current on it.
octahedron said:
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Click to expand...
Click to collapse
When I get on my computer, ill see if I still have all the drivers that I dl. If so will ul to dropbox and post.
Ok this is what I have. Don't know what is what so included what I've got.
http://db.tt/jKixEKQL
http://db.tt/QmpO0ZUx
http://db.tt/CEu1k5q5
The description will pop up with each download. Hope it helps.
Thanks for the help!
I went back to an old bookmark I had when I rooted with 2.3.4 and found drivers. For some reason the motohelper link in my second post in this topic was not helpful. Here's a link for future reference in case anyone needs it:
http://db.tt/XHjBBnGh
I got my phone rooted again and now that I know that works I'll probably go ahead and try unlocking my bootloader to install cm7
When i use the one click casual root method it goes through all the steps sucessfully then i get error, no partition with identifier 60 exists in pit
are you using the latest java 7?
I'll check when I get home Thanks
Sent from my SCH-I605 using Tapatalk 2
I'm using Java version 7 update number 15 and I'm having this issue
Sent from my SCH-I605 using Tapatalk 2
phnman390 said:
I'm using Java version 7 update number 15 and I'm having this issue
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
this is whats happening then the phone goes to android system recovery
WindowsLinux Galaxy Note 2 Jailbreak.scr...4kb ... Update Sucessful! MD5s verified!
Rebooting into download mode
Waiting for Downoad Mode device.detected!
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
Your device should be rebooting into Android now.
Pushing dependencies
Pushing su binary...
Pushing SuperSU app...
Pushing Exynos-Abuse exploit
Pushing root script
Pushing Busybox
Pushing viewmem
Pushing pit
Setting Permissions....
Executing Root Exploit.
[x]Ready for exploit
[x]Device Verification Checks Complete
[x]Ready for exploit
Injecting Code
[x]Exploit Injection Done.
your device is now rebooting into a totally insecure download mode. Press the Volume Up buton when requested by Download Mode. You will then flash the Suck It Verizon bootloader located here: http://d-h.st/DQG. Upon completion of this step, you will be rebooted into TWRP Recovery. CASUAL will wait for you to complete the insecure flash of the Suck It Verizon Bootloader. Press the Up Key before you flash the bootloader in Odin Mode.
Waiting for Downoad Mode device.detected!
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Ending session...
Rebooting device...
Releasing device interface...
ERROR: No partition with identifier "60" exists in the specified PIT.waiting for device
Rebooting into recovery
Done
done
Any suggestions
Sent from my SCH-I605 using Tapatalk 2
ya the one click method seems to giving folks some trouble, mainly on macs. do you have access to a windows 7 pc?
droidstyle said:
are you using the latest java 7?
Click to expand...
Click to collapse
yes
droidstyle said:
ya the one click method seems to giving folks some trouble, mainly on macs. do you have access to a windows 7 pc?
Click to expand...
Click to collapse
yes getting same error on windows 8 pc and windows 7 pc
same?
I seem to have the same trouble. Windows 7 64 bit. Verizon Galaxy note 2. Casual r311. Ran once, failed, pulled battery, ran again, made some progress, stopped with the following error message:
>>>ERROR: No partition with identifier "60" exists in the specified PIT.waiting for device
>>>Rebooting into recovery
Now my phone is sitting in recovery and I have no idea what to do. Can't find an answer online. Too timid to press any of the options. I got a pop up window from the Casual BackAtcha Verizon R311 program saying my phone should be unlocked. That was the last pop up I got. Then the error and my phone sitting in recovery mode.
What do I do? I feel so ridiculously stupid. Been trying this for hours and it's supposed to be the simplest method out there. Heh. Ya'll really know how to confuse a man.
If the program is to be believed I have unlocked my phone. But that is all. I wish there was something more intelligent I could ask than simply "WHAT DO I DO????"..... But that's all I got... WTF do I do? My best guess is press "DO IT" again and hope it realizes it already did a few of the steps. But my phone is sitting in this "Android System Recovery (3e)" menu, which was not where it was when I first started. So that can't be right.
Help! Please! I am so sorry for wasting your time!
Reboot mine does the same thing
Sent from my SCH-I605 using Tapatalk 2
But you won't be rooted but your phone will work
Sent from my SCH-I605 using Tapatalk 2
phnman390 said:
But you won't be rooted but your phone will work
Click to expand...
Click to collapse
Awesome. Thank you very much! That is what I expected but I'm just too lost in the overly complicated process to know if it was safe.
Thanks again. It was tough without my phone for a whole day. Hopefully this problem can get figured out so we can both get root working!
I'm having the exact same problem. I hope this is addressed soon.
I see that Cheshire Delusion and phnman390 are both actively posting and trying to find a solution. If either of you get your phone rooted please post to this thread explaining how you did, as we all seem to have the same problem.
I'm going to re-run Casual and see if that works. If it fails, I'm going to try doing it on a different windows 7 PC. I'll post if I make any progress or brick my phone or whatnot.
I was wondering if it is possible for the USB cable to be the problem? I've read somewhere that it can sometimes cause a root to fail, at least with other phone models. I had to try a couple different cables to get Casual 311b to show "LINK CONNECTED". One cable would charge but wouldn't show up as "LINK CONNECTED". If it shows link connected, and I have up to date Samsung drivers, then the cable should not be an issue, right?
I don't think it's a driver issue I think it's the fact that I had the phone rooted before took the update and somehow this is not working with it it has something to do with that I think I show the superuser icon but I'm not rooted
Sent from my SCH-I605 using Tapatalk 2
I'm having same issues ! Cant get it to work
Is it the same error I'm getting
Sent from my SCH-I605 using Tapatalk 2
I am getting the same error. OI have tried two different USB cables and I am on a windows 8 64 bit machine. I am going to try and load windows 7 in a vm and see if that does any better.
Ok let me know
Sent from my SCH-I605 using Tapatalk 2
Ive been looking everywhere to find out if someone has answers, im trying too root my lg g2. I just installed the OTA 4.4.2 software version (VS98024a). It gets all the way too the part where i can apply update through the abd, but when i click that, i hear the windows noise telling me my device disconnected. I still tried to install it, but it would not send the information over to my phone. I used the ioroot25, but it still doesn't work. Can anyone help me out?
savagebeast02 said:
Ive been looking everywhere to find out if someone has answers, im trying too root my lg g2. I just installed the OTA 4.4.2 software version (VS98024a). It gets all the way too the part where i can apply update through the abd, but when i click that, i hear the windows noise telling me my device disconnected. I still tried to install it, but it would not send the information over to my phone. I used the ioroot25, but it still doesn't work. Can anyone help me out?
Click to expand...
Click to collapse
i think this can help you
http://forum.xda-developers.com/showthread.php?t=2633150
Vaibhav Chauhan said:
i think this can help you
http://forum.xda-developers.com/showthread.php?t=2633150
Click to expand...
Click to collapse
Caution: That is a guide for the At&t version of the G2. OP is trying to install VZW G2 software, so hoping he is using the VZW version of it.
So, you HAVE been able to update, or you have not? How are you trying to update if it is not working for you? You tried to use ioroot25 on 4.2.2 or 4.4.2? What was the error or where did it stop before failing? Have the correct drivers on the PC?
In general, the more details we have, the easier to help. Just saying "It didn't work" is not helpful for troubleshooting.
I have been able too update my phone with the OTA. So my phone is running the 4.4.2. I used ioroot 25, the rooting fails when the root.bat is supposed too send the files too my computer. When I hit the apply through adb, that's when the computer makes the sound that my phone was disconnected. My computer will send it, but phone doesn't receive it for some odd reason. I hope I gave enough information, my bad about last time.
Sent from my VS980 4G using xda app-developers app
You sure you have the drivers for adb mode installed properly? Do you have USB Debugging enabled? If you open CMD prompt and change directories to the ioroot25 folder that has the adb program in it and run:
adb devices
does anything returns?
Yes, I've followed all the directions and watched videos, and when i open cmd prompt, it does state that a device is connected. I just don't understand what I'm doing wrong. Like I said I've followed all directions exactly how they state, downloaded all the drivers.
Sent from my VS980 4G using xda app-developers app
Have you made sure that when accepting the RSA Key for adb / USB debugging that you selected always? If so, then you should try the manual method via adb as described farther down the OP here:
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869&nocache=1&z=7334539103321731
Please and thanks!
I need a PIT file from your device, extracted through Heimdall. It's very simple. No modding or flashing or anything, just a file that's on your device that will bring mine back to life. I've been working on root and need to confirm there is a solid way out in case it doesn't work. So far, it can't be done without a PIT.
-----
Using a Mac
I had to install VirtualBox and run Odin through that.
The way to set it up is here: http://www.onebadkid.com/?p=6930
sbrownla said:
Please and thanks!
I need a PIT file from your device, extracted through Heimdall. It's very simple. No modding or flashing or anything, just a file that's on your device that will bring mine back to life.
Cheers.
Click to expand...
Click to collapse
you should probably post specific instructions for the mac users out there on how to extract what you need..
wase4711 said:
you should probably post specific instructions for the mac users out there on how to extract what you need..
Click to expand...
Click to collapse
Heimdall is not just for Mac it is now available on all platforms.
If anyone is willing to do it, I will guide them through it. It's basically:
(1) Put the watch in in Download Mode:
press and hold home button until screen goes off (keep holding and when it comes on and says "Rebooting...")
then tap, tap, tap, the home button until the menu comes up (Continue, Download, Recovery, Power Off or something like that)
then single-tap through the menu to highlight choose "Download"
then press and hold the home button with "Download" highlighted, to choose to enter into Download mode
(2) Open Heimdall: available for OSX, Linux and Windows
(3) Select Utilities (tab)
(4) Plug Device In: you'll see where it says "Device Detected" indicate that you are, in fact, connected
(5) Download Pit: it has its own section, you choose the destination file and location
interesting info; I did not know there was a version for windows too..
good info, especially on how to get it into download mode!
wase4711 said:
interesting info; I did not know there was a version for windows too..
good info, especially on how to get it into download mode!
Click to expand...
Click to collapse
I cleaned it up to make it more easy to understand. Yeah, Heimdall is incredible, but its most important feature is the creation of a PIT from an existing device.
if I had the watch, I would do it for you, but, unfortunately, I dont...yet..
I have an ATT Gear S....
Ok, I have an ATT watch and can provide the file you need. I will work on it tomorrow morning when I can get in front of my desktop.
On a side note, do you know if I can unlock this and use it on Verizon?
Thank you JEEBUS!!!
Mulox said:
Ok, I have an ATT watch and can provide the file you need. I will work on it tomorrow morning when I can get in front of my desktop.
On a side note, do you know if I can unlock this and use it on Verizon?
Click to expand...
Click to collapse
THANK YOU!!!! :good::fingers-crossed::good: I am desperate. I was figuring I was going to have to drive two hours, buy another Gear S, pull the PIT off, and then return it.
I have an AT&T Gear S with my Verizon Note II. My Gear S came carrier unlocked, I have no idea why, it's a long story though. What you will have to do to get it to work with a Verizon phone, is get a plan for the watch (I now have an H20 nano sim--I had StraightTalk before but it wasn't worth it for how little I used it--that I pay 10 bucks for 100 minutes and some tiny amount of data), and that suits my needs perfectly.
You have to have a Verizon phone plan that allows call forwarding. Make sure you have that. Other than that, it works perfectly.
The rest is cake.
Error downloading pit file...
Ok, I was able to enter download mode ok, and Heimdall was able to detect the device, but when I click on download, this is the error I get:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
sbrownla said:
I have an AT&T Gear S with my Verizon Note II. My Gear S came carrier unlocked, I have no idea why, it's a long story though. What you will have to do to get it to work with a Verizon phone, is get a plan for the watch (I now have an H20 nano sim--I had StraightTalk before but it wasn't worth it for how little I used it--that I pay 10 bucks for 100 minutes and some tiny amount of data), and that suits my needs perfectly.
You have to have a Verizon phone plan that allows call forwarding. Make sure you have that. Other than that, it works perfectly.
Click to expand...
Click to collapse
So I do have a Galaxy S5 on Verizon. I purchased a brand new ATT Gear S, only because I got a ridiculous bargain at $250, vs. $400 from Verizon!
When I called Verizon and gave them the IMEI, they said it could not be used on their network. So I guess I just need to figure out how to unlock it now, without having to pay.
Mulox said:
Ok, I was able to enter download mode ok, and Heimdall was able to detect the device, but when I click on download, this is the error I get:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
So I do have a Galaxy S5 on Verizon. I purchased a brand new ATT Gear S, only because I got a ridiculous bargain at $250, vs. $400 from Verizon!
When I called Verizon and gave them the IMEI, they said it could not be used on their network. So I guess I just need to figure out how to unlock it now, without having to pay.
Click to expand...
Click to collapse
Gear S Pit
Are you running Heimdall on a PC or Mac?
If you're on a PC, you have to make sure the right drivers are installed to connect your Gear to your computer.
Did you ever install Kies? If you did, you'll have to uninstall it to get rid of the Kies versions of the drivers. Windows can naturally detect the proper drivers for the Gear S. Kies installs other drivers, and I think they install other drivers that cause conflicts with competing device mod software ... mmmhrrmmmm ... Same situation if you're on a Mac.
To get rid of the Samsung drivers on your PC you have to go into the program manager and uninstall them as an application. Running CC Cleaner and deleting Samsung mobile drivers helps too (unless you're using a Samsung PC!). Don't worry too much about that because if you want to install Kies again later to connect it to your phone, you just re-install and it will overwrite the drivers. You'll also need to restart after uninstalling the Kies drivers and Samsung drivers, then just plug in the phone and let Windows do the rest. It knows which drivers to install.
Verizon/ATT
So, you shouldn't need to give Verizon the IMEI unless you were hoping that you'd be able to add it to your existing Verizon plan in which case, you have to use the Verizon edition of the watch.
Mulox said:
Ok, I was able to enter download mode ok, and Heimdall was able to detect the device, but when I click on download, this is the error I get:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
So I do have a Galaxy S5 on Verizon. I purchased a brand new ATT Gear S, only because I got a ridiculous bargain at $250, vs. $400 from Verizon!
When I called Verizon and gave them the IMEI, they said it could not be used on their network. So I guess I just need to figure out how to unlock it now, without having to pay.
Click to expand...
Click to collapse
I will seriously pay for your unlocking if you can just get that pit file off of your watch via the instructions.
No one else has offered to help. Which is shocking.
And it's very simple.
still need help?
sbrownla said:
I will seriously pay for your unlocking if you can just get that pit file off of your watch via the instructions.
No one else has offered to help. Which is shocking.
And it's very simple.
Click to expand...
Click to collapse
If you still need this just let me know i can get it to you right away.
bda714 said:
If you still need this just let me know i can get it to you right away.
Click to expand...
Click to collapse
Yes, I still need the AT&T Gear S PIT.
sbrownla said:
Gear S Pit
Are you running Heimdall on a PC or Mac?
If you're on a PC, you have to make sure the right drivers are installed to connect your Gear to your computer.
Did you ever install Kies? If you did, you'll have to uninstall it to get rid of the Kies versions of the drivers. Windows can naturally detect the proper drivers for the Gear S. Kies installs other drivers, and I think they install other drivers that cause conflicts with competing device mod software ... mmmhrrmmmm ... Same situation if you're on a Mac.
To get rid of the Samsung drivers on your PC you have to go into the program manager and uninstall them as an application. Running CC Cleaner and deleting Samsung mobile drivers helps too (unless you're using a Samsung PC!). Don't worry too much about that because if you want to install Kies again later to connect it to your phone, you just re-install and it will overwrite the drivers. You'll also need to restart after uninstalling the Kies drivers and Samsung drivers, then just plug in the phone and let Windows do the rest. It knows which drivers to install.
Verizon/ATT
So, you shouldn't need to give Verizon the IMEI unless you were hoping that you'd be able to add it to your existing Verizon plan in which case, you have to use the Verizon edition of the watch.
Click to expand...
Click to collapse
I never had Kies installed and I am getting the same error. I have a watch and I'm hooked up just need to get past this lib 12 error
EDIT: Forgot to mention no samsung drivers listed in programs either. I can unistall the driver from device manager and reboot but I doubt that will make a difference? I'm trying now to update the driver maniually through the zdiag tool thing
---------- Post added at 04:37 PM ---------- Previous post was at 04:27 PM ----------
I replaced the driver using the zadig.exe tool with all three options. Each time I get
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
EDIT: What version of Heimdall are you using? I have zero experience with it and the only thing I found was suite 1.4.0. I just tried with the mac version on a test mac I have at work and it wont even see the device.
EDIT 2: So I took a look at the read me and it says it should be listed as "Samsung USB Composite DEvice". when plugged in my device is listed as MSM8960. I uninstalled the driver and deleted it. Rebooted the computer and plugged it back in....came right back up as MSM8960. I'll try it on a freshly installed computer for ****s and giggles.
d0ntp4n1c said:
I never had Kies installed and I am getting the same error. I have a watch and I'm hooked up just need to get past this lib 12 error
EDIT: Forgot to mention no samsung drivers listed in programs either. I can unistall the driver from device manager and reboot but I doubt that will make a difference? I'm trying now to update the driver maniually through the zdiag tool thing
---------- Post added at 04:37 PM ---------- Previous post was at 04:27 PM ----------
I replaced the driver using the zadig.exe tool with all three options. Each time I get
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
EDIT: What version of Heimdall are you using? I have zero experience with it and the only thing I found was suite 1.4.0. I just tried with the mac version on a test mac I have at work and it wont even see the device.
EDIT 2: So I took a look at the read me and it says it should be listed as "Samsung USB Composite DEvice". when plugged in my device is listed as MSM8960. I uninstalled the driver and deleted it. Rebooted the computer and plugged it back in....came right back up as MSM8960. I'll try it on a freshly installed computer for ****s and giggles.
Click to expand...
Click to collapse
Uh oh ... I just did a search and found that newer Samsung devices with newer bootloaders are facing incompatibility issues w/ Heimdall. I may have to generate a PIT manually.
Yeah v1.4 is what usually works.
Looks like either Samsung hates modders ... or Yosemite has caused major problems ...
I'll keep looking around.
THANK YOU
sbrownla said:
Uh oh ... I just did a search and found that newer Samsung devices with newer bootloaders are facing incompatibility issues w/ Heimdall. I may have to generate a PIT manually.
Looks like Samsung hates modders ...
I'll keep looking around.
Click to expand...
Click to collapse
Bummer.
If you find something that should work I will give it a shot. I've only ever bricked one device in my years but it f-ing SUCKS!
d0ntp4n1c said:
Bummer.
If you find something that should work I will give it a shot. I've only ever bricked one device in my years but it f-ing SUCKS!
Click to expand...
Click to collapse
That's so cool of you.
So ... I'm back out of bootlooping and I'm going to work on flashing again ... I'm still bricked (stuck in download mode) but I'll do some more looking at what's up with Heimdall.
I am rrreeeeally curious about what's going on ... is it really Heimdall or is it the new Samsung bootloaders ... or ...
Hm, I have an idea though ... I am certain that the rootfs that that person who claimed they'd figured out root changed my permissions and my PIT even though I modded it with my stock firmware. So I'm going to try to pull out the rootfs from my stock firmware for my AT&T Gear S and see if I can just flash that.
Odin can see my device and recognizes that it is in download mode ... it's just that it needs to be repartitioned ... usually, however, that's done with a separate PIT but the thing is, the PIT is supposed to be contained in a few locations within the stock firmware TAR ball, or it's its own separate file within the stock firmware TAR ball. Hehe, tar ball ... And Heimdall has a feature that can extract a usable PIT file ... but nothing else out there seems to.
We need @AdamOutler!!!!! I don't know what his thoughts are on Tizen and Samsung right now ... or on wearables, but the man is a genius.
I also tried the different USB drivers and same issue...
Mulox said:
I also tried the different USB drivers and same issue...
Click to expand...
Click to collapse
yours showing up as msm too?
By the way I'm using the AT&T variant of the Gear S with a Verizon S5. Haven't had any issues but yeah if you want the device on a Verizon telephone number I'm sure they are doing everything they can to say no. Their same damn watch is 100 bucks more then their competitor! >.<
d0ntp4n1c said:
yours showing up as msm too?
By the way I'm using the AT&T variant of the Gear S with a Verizon S5. Haven't had any issues but yeah if you want the device on a Verizon telephone number I'm sure they are doing everything they can to say no. Their same damn watch is 100 bucks more then their competitor! >.<
Click to expand...
Click to collapse
Mulox said:
I also tried the different USB drivers and same issue...
Click to expand...
Click to collapse
Thanks for trying you guys. I am trying every combination of connection and firmware I can.