Related
Hmm, so I flash the downgrade then power on, wait til phone is recognised and run the qsd8250_setool2.cmd but it says access denied for every step. Anyone got any ideas?
turn off any antivirus running and try again !!
Thanks ill give it another shot tonight, wish me luck!
Sent from my X10i using XDA App
Had same issue, I replaced the adb included in the package with
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
from android sdk, worked like charm
Thanks for your help guys closed my antivirus software and it worked like a charm
Sent from my X10i using XDA App
Im trying to unlock my bootloader so I can root my phone. When I get to the step to get my identifier token, it is stuck on <waiting for device>. If anyone can help me, Id greatly appreciate it.
ThatGuyMitch said:
Im trying to unlock my bootloader so I can root my phone. When I get to the step to get my identifier token, it is stuck on <waiting for device>. If anyone can help me, Id greatly appreciate it.
Click to expand...
Click to collapse
Make sure your drivers are installed on the computer and that you are in the fastboot option in hboot, not just the bootloader. I know thats probably a duh, but just making sure. Also when you first connect it to the computer, run adb devices and make sure its seeing the devices.
It also doesn't help that the HTC Dev site is having issues giving up the .bin file after you give them your token identifier. Feel free to tag along here: http://forum.xda-developers.com/showthread.php?t=1475864
clmowers said:
Make sure your drivers are installed on the computer and that you are in the fastboot option in hboot, not just the bootloader. I know thats probably a duh, but just making sure. Also when you first connect it to the computer, run adb devices and make sure its seeing the devices.
Click to expand...
Click to collapse
Should I check to make sure adb can see the device before I pull the battery out to reboot into the bootloader?
You can have it in charge only mode with the rom booted and everything and type "adb devices" and it should spit out the serial number.
Make sure you have USB Debugging checked in settings/developer options. Amd also make sure any antivirus type security business is turned off on your computer.
Sent from my ADR6425LVW using xda premium
Are you using Ubuntu (or any Linux clone) I had a heck of a time setting it up to work on Ubuntu.
Sent from my SCH-I815 using XDA Premium HD app
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??
I am having problems trying to root my GNote2 with casual. I have java updated as well as Samsung drivers downloaded. First I was stuck on Initializing Protocol but got past that with a hard boot from battery pull. Now the problem is the device restarts into download mode and does its thing and casual states that it will continue once windows 7 recognizes the device again and after that it goes through the next stage but this is the errors I am getting. Cant just post the log from casual since XDA thinks it is links to websites and I am not over 10 posts. I attached it as a .txt file.
edrompa said:
I am having problems trying to root my GNote2 with casual. I have java updated as well as Samsung drivers downloaded. First I was stuck on Initializing Protocol but got past that with a hard boot from battery pull. Now the problem is the device restarts into download mode and does its thing and casual states that it will continue once windows 7 recognizes the device again and after that it goes through the next stage but this is the errors I am getting. Cant just post the log from casual since XDA thinks it is links to websites and I am not over 10 posts. I attached it as a .txt file.
Click to expand...
Click to collapse
I did find this post (http://forum.xda-developers.com/showthread.php?p=42077290) with the same error but I am not quite sure what they needed to download differently.
edrompa said:
I am having problems trying to root my GNote2 with casual. I have java updated as well as Samsung drivers downloaded. First I was stuck on Initializing Protocol but got past that with a hard boot from battery pull. Now the problem is the device restarts into download mode and does its thing and casual states that it will continue once windows 7 recognizes the device again and after that it goes through the next stage but this is the errors I am getting. Cant just post the log from casual since XDA thinks it is links to websites and I am not over 10 posts. I attached it as a .txt file.
Click to expand...
Click to collapse
Figured it out. It was my anti virus(Microsoft Security Essentials). Maybe this will help people with the same problem.
I'm having issues with casual.....when I run it, it doesn't recognize the phone is in download mode???? Any help would be awesome..
Sent from my SCH-I605 using xda app-developers app
rclar144 said:
I'm having issues with casual.....when I run it, it doesn't recognize the phone is in download mode???? Any help would be awesome..
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Are you using the latest version of casual, No You Verizon?
Yes
Sent from my SCH-I605
---------- Post added at 11:48 PM ---------- Previous post was at 11:44 PM ----------
Possibly a driver issue?
Sent from my SCH-I605
rclar144 said:
I'm having issues with casual.....when I run it, it doesn't recognize the phone is in download mode???? Any help would be awesome..
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Is developer options and use debugging on?
Yes I've double checked. It's puts phone into download mode but then doesn't recognize it done it
Sent from my SCH-I605
rclar144 said:
Yes I've double checked. It's puts phone into download mode but then doesn't recognize it done it
Sent from my SCH-I605
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=41294112
Try to use this post by jrloper. This post says for win8, but he has also stated it works on win7
Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
I have this exact same problem right now.
Would love to get a solution for this.
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
COLDrum said:
I have this exact same problem right now.
Would love to get a solution for this.
Click to expand...
Click to collapse
Please post here if you find a working solution for this.
demkantor said:
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Im on hold when it gets to downgrading so far. Im not familiar with Android Commander, but Droid Explorer requires adb to be working. And that is kinda my whole problem. I cant accept my PC as a secure adb-client since the digitizer is broken (touch input wont work). I hope there is a way to override this through recovery or some other way.
Breakdown:
When connecting device to computer (adb), I have to (on my device) accept my computer as secure. This is a problem since digitizer is broken.
Sent from my Nexus 7 using xda app-developers app
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
demkantor said:
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Indeed this seems to be a fix. Thanks!
Do you know if there is a way to get rid of the authorization through adb. Are there any files who could be manipulated? Would be great if I could use some sort of screencast-app eg. Droid Explorer.
Sent from my Nexus 7 using xda app-developers app
I'm sure being you can use adb shell in recovery that there is a way, can't say off hand but a bit of digging will probably get you there, it couldn't be all that hard I wouldn't think
Sent from my Nexus 4 using xda premium
Streaker said:
Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
I do have more than one instance of ADB.exe installed yes, but does that matter to my problem? My Nexus isnt even showing up in fileexplorer in windows. So I cant access my files. Or am I wrong here?
Sent from my Nexus 7 using xda app-developers app
maxrfon said:
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
Click to expand...
Click to collapse
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
....
maxrfon said:
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
Click to expand...
Click to collapse
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have had the same problem with my S4.
After updating ADB i did "adb devices" and got my S4 as offline, and i noticed the popup on my phone, accepted and my samsung is now working fine with ADB.
FYI before the above mention operation i have tried everything, even making sure i run the correct adb.exe but there was no popup.
First of all kill the adb server via task manager then when you start the adb command-line type In ADB root this may solve your problem :thumbup:
Hit thanks if I helped
Sent from my Xperia Live with Walkman using xda app-developers app
Somehow I managed to delete the stock OS and CM on my LG G2 (Verizon) and now my device is stuck on the loading LG screen. I am also getting the unauthorized device when checking ADB devices. I've got TWRP running as the bootloader, but just need to be able to push over the CM file to boot and I'll be good to go. Any suggestions on how to force the file over to the phone?
Boot into your twrp recovery and use adb sideload to flash a ROM from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
VreebieZ said:
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
Click to expand...
Click to collapse
I'm having the same problem as the OP... This is impossible. *the screen and digitizer are broken*
The question is "How can I bypass the New authorization, since I can't click anything on my phone". I can't check "USB Debugging" - I need the phone screen and digitizer to do that. come on people, read the post.
Has anyone figured this out? I'm having a similiar problem except my screen isn't broken. I forgot to make a backup and my OS got erased and I'm getting the unauthorized notification in ADB. You have to be able to get into the OS to accept the authorization so I'm at a catch 22. I have a Nexus 7 so I can't swap out a different SD card.