Hi,
I tried to use psouza4's one click root, but I keep getting an unhandled exception error. I double checked the instructions and believe I am following them correctly, but to to avail. I am using XP, but using his tools for Windows 7 first as instructed. He does have a script specifically for XP in case the Windows 7 tool does not work, but I see that it does not have an unroot or restore option.
Am I missing something that is causing this error, or will I have to use the special XP one? If so, how do I unroot if necessary? He indictaes that the Windows 7 tool should work for most XP users, I wonder what makes some (and apparantly mine) not work, unless this error is something unrelated.
Any input would be appreciated. This is my first foray into android from Windows Mobile, so I am quite (obviously) a noob.
Thanks!
I haven't used his tools, but if you are on the leaked OTA 5.7 that exploit will not work. Try zergRush
Related
First of all, just wanted to say that this is a fantastic forum and resource!
I've got a Captivate with 2.2 Froyo (build FROYO.UCKB1) on AT&T, and so far I haven't been able to root. I've followed the wiki and new users guide without having much success. It seems like Samsung or AT&T have introduced some extra barriers to rooting(?)
I initially tried dropping an update.zip tool into my /sdcard folder and rebooting. The error I received was "E:signature verification failed"
After that I tried using ADB to replace the /system/recovery file, but no luck.
So I also tried the SuperOneClick application, using VirtualBox to load a Windows XP guest (I'm running OS X Lion). Unfortunately, the phone is disabled in the list of USB devices. I tried adding it to a filter in Preferences->Ports->USB. SuperOneClick freezes on the "Waiting for device" part.
Has anyone had the same issues?
Ok so im a total noob on all things Android and i apologise if this has been asked and if there is an answer please post link and i shall delete,
i have downloaded the recommended toolkit for my n7 32g (jop40d) from this site (the mskip one) done the debugging option however the driver wont install,i went the manual route using pdanet but get "installer fail to open device".
im using windows vista.
Any help would be much appreciated
gibd79 said:
Ok so im a total noob on all things Android and i apologise if this has been asked and if there is an answer please post link and i shall delete,
i have downloaded the recommended toolkit for my n7 32g (jop40d) from this site (the mskip one) done the debugging option however the driver wont install,i went the manual route using pdanet but get "installer fail to open device".
im using windows vista.
Any help would be much appreciated
Click to expand...
Click to collapse
I don't know if your problem come from vista but just try to reboot your PC and press F8 many times and check an option to disable signed driver or something like this . Or you can install Raw driver . That's what I did and it work
cydef said:
I don't know if your problem come from vista but just try to reboot your PC and press F8 many times and check an option to disable signed driver or something like this . Or you can install Raw driver . That's what I did and it work
Click to expand...
Click to collapse
Try wug's toolkit, it has step-by step drivers for most every windows system including vista. I've had to set the drivers manually before too, but it's easier if you can follow on-screen directions. Don't worry, we're all noons in some regard. We just have more we can learn here. -Ara
Sent from my Nexus 7 using Tapatalk HD
thanks guys,
i aint going to lie mskips method is infuriating in my opinion.after every step i get "waiting for device" and nothing happens,succesfully completed steps 1 to 3 then on the root step it does some stuff my tablet turns off then comes back on normally not to fastboot mode and on my pc it says "waiting for device"... waiting for what?????
so i decided i woulg give step 8 a try using TWRP and after it does some stuff succesfully exactly the same happens,"waiting on device" and n7 turns off and then comes on in normal mode???
is that the process complete?
gibd79 said:
Ok so im a total noob on all things Android and i apologise if this has been asked and if there is an answer please post link and i shall delete,
i have downloaded the recommended toolkit for my n7 32g (jop40d) from this site (the mskip one) done the debugging option however the driver wont install,i went the manual route using pdanet but get "installer fail to open device".
im using windows vista.
Any help would be much appreciated
Click to expand...
Click to collapse
Are you trying to do the all in one click? I tried that and it did not work for me. I had to do each option separately and it worked.
AraDreamer said:
Try wug's toolkit, it has step-by step drivers for most every windows system including vista. I've had to set the drivers manually before too, but it's easier if you can follow on-screen directions. Don't worry, we're all noons in some regard. We just have more we can learn here. -Ara
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
+1
Use Wug's, it gives you step by step visual instructions. I followed his method and installed drivers manually on my home computer, theis after fighting with two other computers previously. The only thing to note is that you will have to reboot into fastboot manually, then install the drivers and rebooot the computer in the end.
Sent from my LG-P999 using xda premium
ok i'll use Wugs,will the fact that my tablet has completed some steps effect anything or just carry on like nothing has happened??
+1 for Wugs.
I had an issue where it wouldn't root. I rebooted, re started, unplugged, restarted PC, etc. I finally uninstalled WUGS toolkit and installed again. Worked like a charm and there are about 3 YouTube videos showing you step by step.
Sent from my Nexus 7 using xda app-developers app
Thanks for the help guys,i went the wugs waybut how do you know if it was successful? although now i have superSu and Busybox free installed on my device.
Hi Team,
I feel like I'm pretty close to being able to root this thing. Never used ADB, telnet, or any of the other random things I've spent several days reading about, but I think I've got it lined up to give it a shot.
I wish I could do this on my mac, but it seems the MotoWpNoMo step requires a PC. I do have an old laptop running xp (sp3), so for that step I'll use it. Unfortunately I can't seem to get the drivers to work. I've installed the motorola device manager's newest incarnation and still no luck getting it to pick up my device.
Any advice on how to get windows XP to recognize my device?
motoxuser said:
Hi Team,
I feel like I'm pretty close to being able to root this thing. Never used ADB, telnet, or any of the other random things I've spent several days reading about, but I think I've got it lined up to give it a shot.
I wish I could do this on my mac, but it seems the MotoWpNoMo step requires a PC. I do have an old laptop running xp (sp3), so for that step I'll use it. Unfortunately I can't seem to get the drivers to work. I've installed the motorola device manager's newest incarnation and still no luck getting it to pick up my device.
Any advice on how to get windows XP to recognize my device?
Click to expand...
Click to collapse
what do you mean by your computer won't pick up your device.
like when you plug in your device nothing happens no driver's start to install or on your phone does it say USb debugging enabled or MTP.
or when you computer trys to install the drivers it fails.
if you not getting anything at all when you plug your phone in i would try a different USB port if still nothing then i would try a different USB cable
if you are having issues getting the drivers to install you can try downloading the Moto X toolkit, it has a option to download the drivers plus it also comes with ADB and everything else in the folder it installs to.(location is C:/Program Files/stillthisguy)
here is the link for the Toolkit for PC
http://forum.xda-developers.com/showthread.php?t=2477132
ToolKit for Mac
http://forum.xda-developers.com/showthread.php?t=2591875
hey that got it - the toolkits are great. thanks!:good:
motoxuser said:
hey that got it - the toolkits are great. thanks!:good:
Click to expand...
Click to collapse
no problem man glad it got it up and running
Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Lyper said:
Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Click to expand...
Click to collapse
Delete all your android drivers, and try this:
http://forum.xda-developers.com/showthread.php?t=2588979
I removed 4 adb drivers and many samsung ones, installed with administrator settings the linked content, then it tried to install the nexus 6 via the default windows updated. Seemed to work, get the sound for connection, but no option to transfer my stuff. I tried uninstalling the drivers and re-installing, still nothing.
http://puu.sh/jVt0q/57fb6bf8d3.png
No more ideas?
Lyper said:
No more ideas?
Click to expand...
Click to collapse
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
prdog1 said:
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
Click to expand...
Click to collapse
Yeah well I did that multiple times, which didn't work. I really don't feel like reformatting, ho boy, but I really gotta get this going. Thanks for the suggestion!
Try switching ports.
Sent from my Nexus 6 using Tapatalk
I tried switching ports.
Ok so the list of things I tried : Manually removing any drivers that had to do with android/usb phone, I reinstalled the drivers for my motherboard, I fixed every system inconsistency with ccleaner, removed android studio. I had also manually removed any prior detection fo the nexus 6 in the device manager. It will once again pop up the "driver install" from windows, complete, but be impossible to manually update via device manager as it doesn't recognize my device.
I'm also using the default cable from my nexus 6, and tried others. Is there anything else to do? Otherwise reformatting tonight. Thanks everyone for the support.
Hello, sorry to keep bumping this thread. I just reformat... and the problem still persists. I have no clue what to do anymore, I literally tried everything I could possibly think of.
Anyone got any ideas? To state again, I'm running windows 10 x64.
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Nevermind, I did a total complete reformat now, still doesn't work. I'm literally out of ideas now.
Should I contact my motherboard manufacturer (MSI) ?
not sure what to tell you, but definitely samsung drivers and motorola drivers do not play well together very often
Lyper said:
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Click to expand...
Click to collapse
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
prdog1 said:
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
Click to expand...
Click to collapse
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Lyper said:
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Click to expand...
Click to collapse
Have you tried a Windows update since the original boot. On my son's AZUS the touchpad driver was bad. It had changed driver to a Generic. Deleted that driver and ran Windows update and it found the new driver. Worth a shot. Hard to tell what to do. I couldn't see any differences after the Win 10 upgrade. Didn't even effect my dual boot Linux. My friend just lost lost the drive sync to his Linux setup.
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Lyper said:
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Click to expand...
Click to collapse
Can you tell where can I find the media pack for windows 10?
Thanks.
Hi all. Thought I'd check if there is a newer method to root the phone on the Mac.
I can't run Odin on a Mac and I don't have enough space to bootcamp into Windows. I've tried Parallels in the past but it didn't work.
I understand Heimdall is not maintained now? I've tried that in the past too but couldn't find the PIT file for my phone anyway
So I've been stuck and now the phone is acting up. So much junk on the stock rom.
vurtomatic said:
Hi all. Thought I'd check if there is a newer method to root the phone on the Mac.
I can't run Odin on a Mac and I don't have enough space to bootcamp into Windows. I've tried Parallels in the past but it didn't work.
I understand Heimdall is not maintained now? I've tried that in the past too but couldn't find the PIT file for my phone anyway
So I've been stuck and now the phone is acting up. So much junk on the stock rom.
Click to expand...
Click to collapse
I was in the same boat with a new MacBook being my new computer. I ended up boot camping windows 10. I tried to figure out jodin with no success. Maybe someone who has done this recently will chime in. Good luck.
You need to download the heimdall, that is compatible with your operating system. For me, I am on El Capitan, so I downloaded the one from here. Once I installed that, I ran the heimdall frontend app first. I went to the "utilities" tab, connected my phone, and then clicked "detect." Once my phone is detected, I just saved the pit file.
Not for Nothing Folks, You can get a windows computer/laptop very cheap now a days. If you are planning to do a lot of flashing on android phones, nothing beats a cheap windows computer. MicroCenters, Amazon, Ebay, Best Buy have cheap computers that will be able to do what you need for flashing your phones. I know you can do it on a mac ( and some say it is easy or fast), but you have to make sure it is setup correctly or you can do damage to your phone than it is worth. I used to run Mac, and I got tired of trying to get things that run on windows and not on mac, to work correctly. I cant remember the last time i even started my mac book.. LOL
Just something to think about..
****And no reason to argue with me or prove that mac is the best out there, or you will never buy a windows computer. ***
Google and try jodin. It's a Web based java program. Ive successfully flashed my N910T and G900T with it.