Develop Bugs

[Q] Please Help! SuperOneClick is not working and I have tried everything!

Please help me, any advice to point me in the right direction would be appreciated. I have a Motorola Defy running stock 2.2.1 official update from T-mobile. Im using Superoneclick v1.9.5, I have all the drivers installed, Im running Windows 7 on my PC with .NET Framework 4 and every Framework update prior to that version, an all the, put the phone in debugg mode, and also the USB is in Phone portal mode, Run superoneclick under admin, and it still gets stuck on "Waiting for device...." I dont know what else needs to be done... Please anyone...

Try to reinstall motorola drivers ( uninstall > reboot > install ( > reboot if using xp ) ).
Make sure you have the latest ones.

Make sure USB debugging is DISABLED on your phone in Settings > Applications > Development before launching superoneclick..
Launch SuperOneClick on your computer by right-clicking on it and selecting ‘Run as Administrator’.
Click ‘Root’. It will say ‘Waiting for device…’
Now ENABLE USB debugging on your phone in Settings > Applications > Development.
Wait patiently till you see a prompt on your computer saying ‘Device is rooted’.
Reboot your phone and you’re done!
All the best

Take the phone out of portal mode, just enable usb debugging and put it in charge mode.
Install the drivers from the SuperOnClick 1.9.5 package BUT use the 1.7 version of SuperOneClick to perform the root.
I've done my wife's Defy twice in the last two days, info here.

How to root Motorola Defy with Froyo Upgrade

UK Retail Motorola Defy with Froyo ugrade rooted using Superoneclick.
Previously hade Eclair rooted with Z4Root working great.
Z4Root couldn't touch Froyo upgrade.
Here's what I did.
Download Superoneclick Version 2.1.1. Don't use earlier ones.
Unzip Superoneclick & goto the extracted directory.
Before running Superoneclick.
1) Install Busybox version 1.19.2. Not 1.19.3, didn't work for me.
2) On the phone goto Settings/Applications/Development and make sure USB debugging is ticked i.e. ON
3) On phone goto Settings/SD card & phone storage and Unmount the SD card.
Plug the phone in to the USB port. Ensure the USB mode is None. i.e. no card access, no media access no portals & tools.
Run Superoneclick. Hit the ROOT button and let it do that magic thing.
Once Superoneclick has rooted the phone.
Deselect USB debugging.
Mount the SD card.
Reboot the phone.
Happy rooting.
caveats.
I initially tried this with the phone USB mode set to Portal & Tools. Didn't work.
Thank you to the developer(s) of Superoneclick. And a middle finger to Motorola for waisting my time. Now I can get rid of the junk Apps.

I remember that I never use step 3 above and it work just like that playing with the USB debugging mode ON and OFF twice while Superoneclick is accessing the system to get the phone rooted.

I used superoneclick version 1.9 I think and it installed the busybox for me...I just had to enable USB debugging when it said waiting for device
Sent from my MB525 using xda premium

[Q] Unable to sideload?

After rooting and installing the latest Venom 6.16 rom I'm having trouble installing apps via AC_SWM or adb.. adb sees the phone and the file appears to install but never does show a "success" message. The obvious unknown sources and usb debugging are enabled.. what am I missing?

[Q] connecting issue of nexus i9250 in debug mode

its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me

get this: [Toolkit] Wug's Nexus Root Toolkit v2.02
It has a guide for the folder you have, under: Initial Setup > Full Driver Installation Guide... > Step 3 > Driver Solution # > Manual Configuration.

coolncool said:
its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me
Click to expand...
Click to collapse
...
You should be asking these questions on a Windows forum.
You need to right click Android 1.0 device... Update Driver (basically, tell Windows Device Manager that the driver for the "Android 1.0" device is in that folder you got there)... it will install it, and that part is done. Then reboot the device to fastboot mode and manually update the driver again (it will come up as a different, yet again unknown device, you just feed it the same driver again)
Also... for the operations you're mentioning... "root, unlock bootloader, install cwm, flash rom".... you probably won't even need ADB, just fastboot. As in, you don't need to root before all that. You root in the end. And most custom roms are already rooted too.
This is assuming there's an exploit out there that still allows for root to be achieved without unlocking the bootloader.

adb problems

Hi all,
today i tried to connect to my HTC 10 using adb and it wouldn't even find the device.
I updated the android sdk, which did not solve the problem. But i did find some other "fancy" things
First of all some info on my device
software: 1.95.401.4 stock
unbranded eu device
s-off and bootloader locked
phh's systemless root
systemless xposed
After i did s-off my device, i was able to fastboot flash twrp, adb was working, also after installing magisk and systemless root/xposed adb was working fine. When adb did not work i was like "perhaps i disabled usb-debugging, so enable it" but it was still enabled.
Here we come to another problem, with usb-debugging enabled, my mac/phone won't recognize it's plugged in via usb, a message pops up stating
Slow charge
For faster results, use the original HTC charger
Click to expand...
Click to collapse
if i then
uncheck usb-debugging -> the device gets recognized/recognizes it's attached to a usb port
a message pops up asking if i want to enable file transfer
rechecking usb-debugging -> device still recognizes it's attached to a usb port
a message pops up asking if i want to allow usb-debugging
running
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and
Code:
adb devices
List of devices attached
or
Code:
adb usb
error: no devices/emulators found
then i thought, ok revoke usb debugging authorization, unplug the device and plug in again, grant authorization and off we go, but i do not get the message if i want to authorize the pc
anyone else encountered this before or has any idea whats wrong here?
EDIT: it's working now, i do not know exactly why.
went into magisk manager to disable superuser and xposed to be able to rule out they were interfering in some way
saw magisk update is available so i updated magisk to v9
restarted without disabling modules
and now it works again. phone recognizes it's attached to usb even if usb-debugging is enabled.
EDIT2: can be closed by a mod as it's solved