anyone haveing trouble with super one click try this - Streak 5 Q&A, Help & Troubleshooting

i found this at about post 2500 but it works and i thought it might be helpfull to anyone who is haveing problem with super one click
1. disable your anti-virus
2. pull your streak battery off
3. run SuperOneClick with admin rights
4. put your battery back and turn on
5. Unmount SD card
6. Enable debugging mode
7. Connect your USB cable
8. Click Root "I'm did using rageagainstthecage"
9. Enjoy and don't forget your anti-virus
and here is a link to the post
http://forum.xda-developers.com/showthread.php?t=803682&highlight=dell+streak&page=254

Related

NEWBIE - Galaxy SII smashed screen -copy data with ADN? (phone not rooted)

Hi all
Thanks to those who replied though it would be nice if the post was fully read first... for example, I cannot just connect the phone and copy its content via USB!
Here's the problem:
- phone screen is smashed and shows nothing
- phone still powers up though
- it is not rooted
- it has data on its internal memory that I want to copy
- it has pattern lock activated
- computer (MS Vista OS) recognises a USB devise is logged in, but it doesn't read it as a drive, and KIES just idles... no doubt because I would need to change the phone settings, which I can't do with a smashed screen.
QUESTIONS:
- How can I access phone contents to copy them? (repair shop wants $220)
- I was told using ADN....
I installed SDK Tools but how do I start ADN?
Many thanks
the easiest way might be connect to your computer and copy the contents of the internal sdcard if your computer sees the phone.
If you wan to use odin, use file dump to dump the contents of your phone i believe.
I'm quite the noob when it comes to adb scripting, but I believe that
- start a command line within the directory where ADB executable is located
- type in "adb usb" and it should connect to your phone
- then type "adb pull /mnt/sdcard/* X:\path-to-directory\"
commands without parentheses... I hope it will work
Thanks for the replies
I just amended my original post to say the computer does not recognise the phone when USB connected... KIES tries to connect but fails (no doubt because there is no response from the phone).
Did you try and connect it through mass storage?
Settings - Wireless and networks - USB utilities.
Also try uninstalling kies and reinstall
Sent from my ThinkPad Tablet using XDA App
mattyh77 the screen is broken, I can't see a thing on it so I can't changes settings from the phone...
ANYONE ELSE PLEASE?
E3Y said:
mattyh77 the screen is broken, I can't see a thing on it so I can't changes settings from the phone...
ANYONE ELSE PLEASE?
Click to expand...
Click to collapse
adb is it!
open a adb shell if you need to navigate around to where things are..
then do a adb pull to get the stuff you want.
Oh yeah, forgot about that, haha. Sorry.
Sent from my GT-I9100 using XDA App

[Q] XWKT7 by ketut.kumajaya

Hello- USB debugging is turning itself on(putting a check on itself in the settings) automatically as soon as I plug in the USB cord and enable USB storage.
I am using the ROM located at http://forum.xda-developers.com/showthread.php?t=1442889
Any help is appreciated, thank you!
as far as i see its always enabled in stock roms... and there is nothing to worry about unless you have some virus in pc which will use adb to format phone or steal data
madman_amit said:
as far as i see its always enabled in stock roms... and there is nothing to worry about unless you have some virus in pc which will use adb to format phone or steal data
Click to expand...
Click to collapse
The problem is I can not turn off USB debugging, this is not normal behavior. It automatically turns itself on...
Download ROM Toolbox from Market, go to root browser, build.prop Editor, click the pencil on the extreme upper right type - persist.adb.notify=0 in the end of the textbox. Should solve the problem I think..

[Q] How to rescue data from the internal_sd when display is broken?

So here is a hard one: My friend's SIII fell down, display broke. And he didn't do any backup from the files on the internal memory (yeesh...!!). So how can we rescue the data? USB won't work, because you have to verify USB access by clicking the message that normally would appear on the screen after plugging it to your PC. The phone is *not* rooted.
Installing apps will be no problem because you can simply install apps logging in on Google Play with your PC's web browser. So I hope that there's a certain app in the Play Store that would i) grant access via USB/web/something without having to do any click on the phone's screen or ii) that would backup all the phone's data (or specified folders) to another location... without having to perform a single click on the phone's display.
(Guys, we're talking about his girlfriend's private pictures - so please help him! )
Thank you for helping...!
Well IMHO, he is going to be very lucky. Installing an app won't be useful. Anything that allows wireless / network access to local files on the device will require on screen set up or interaction (for security purposes).
If he somehow has USB debugging turned on, he MAY be in luck. But It is doubtful. This is a real longshot....
Firstly, download this file:
https://dl.dropboxusercontent.com/u/20471345/SUroot/Tools/PC/sdktools-toolsonly.rar
Follow the instructions in the read me to add it to windows environment variables.
Then, use this:
http://forum.xda-developers.com/showthread.php?t=1703488
To install all the drivers required. Run through the screens and choose your model of device and follow all the instructions for installing the device drivers. THIS IS WHERE WE NEED TO HOPE USB DEBUGGING IS ENABLED
Hopefully you won't need root for this next part.... If you get this far and do need root, the toolkit can root anyway.
Then open up a command prompt (press start / windows key and type "cmd" and press enter.
in the black window type "adb shell" and press enter
type "cd /mnt/sdcard" and press enter
tpe "ls" (thats LS) and press enter
This is where you identify where the images are. I assume they are in DCIM.
type "exit" and press enter
type "adb pull /mnt/sdcard/DCIM c:\" and press enter.
This should pull all the DCIM contents to the local c: drive of the computer.
It all hinges on whether USB debugging is enabled tough so its a long shot. I really can't think of anything else.
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Actually, the toolkit has a backup internal SD card option anyway so the last section is irrelevant. After installing the drivers, just go into the backup menu.
All you really need is this:
rootSU said:
use this:
http://forum.xda-developers.com/showthread.php?t=1703488
To install all the drivers required. Run through the screens and choose your model of device and follow all the instructions for installing the device drivers. THIS IS WHERE WE NEED TO HOPE USB DEBUGGING IS ENABLED
After installing the drivers, just go into the backup menu.
Click to expand...
Click to collapse

[Q] ADB Will Not Work CM7

Hello , well im sorry to bother you guys but i just cant seem to connect through ADB using any Cyanogenmod rom but adb seems to work on stock roms. Ive tried everything reinstalling drivers and using different cables but nothing seems to work , could anyone help me out?
Try this and see what the outcome is good luck
All credit goes to oc3rulz for finding this.
http://forum.xda-developers.com/show...&postcount=814
Originally Posted by oc3rulz
I have CM7 installed and I just got Windows to recognize the SDCARD via USB Mounting!!!!
Now again I am using Windows 7 so the steps are almost exactly the same. I literally just changed the device to a USB Mass Storage device and it worked!
Lol after trying so many drivers and it being the generic driver makes me angry. Here's what I did.
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your My HTC (should be the second one Android USB Device), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose USB Mass Storage Device
Then it takes some time to think and viola! All working! However we are not DONE!
EDIT: So the next step I did after experienced issues remounting after unplugging the phone. I have change the MTP to ADB Testing Interface and things seem to be mounting everytime. Rebooted phone and PC, both worked again so I think this may be a working solution.
Now go to MTP.
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your MTP (should be under Unknown Devices), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose Google Inc. and the Driver is ADB Testing Interface.
ENJOY!

USB Debugging enable on boot?

I've turned on the developer options and can enable the USB Debugging option to be able to use Titanium backup. However I notice when I reboot the device it gets disabled again. Does anyone know of something/somehow to ensure it's enabled on boot?
Thanks!
---Eric
Got it, need root shell of course:
- Remount /system in readwrite mode.
- Add this to /system/build.prop: persist.service.adb.enable=1
- Save, remount as read only.
- Reboot.
Well...didn't really work...though it did, any ideas? USB debugging for me has to be manually picked each time.
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:
#!/system/bin/sh
echo 1 > /data/property/persist.service.adb.enable
This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
Any chance anyone else has come up wth a different way to retain USB debugging on reboot? I just had to rebuilt my phone from scratch by restoring from stock and executing a script at boot up could potentially be fatal. I'm a linux admin so I do know what I am doing but without a unlocked bootloader and the ability to recover from a CWM backup, I'd rather not mess with the OS too much if possible.
x86cpu said:
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:
#!/system/bin/sh
echo 1 > /data/property/persist.service.adb.enable
This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
Click to expand...
Click to collapse
JCDinPGH said:
Any chance anyone else has come up wth a different way to retain USB debugging on reboot? I just had to rebuilt my phone from scratch by restoring from stock and executing a script at boot up could potentially be fatal. I'm a linux admin so I do know what I am doing but without a unlocked bootloader and the ability to recover from a CWM backup, I'd rather not mess with the OS too much if possible.
Click to expand...
Click to collapse
I use Tasker with the secure plugin.
It allows turning on USB Debugging. I use it to turn on USB Debugging as a condition after boot.
Also the worst case with a script, you re-install/flash the OS.
I've reinstalled my Verizon LG G3 from stock ROM twice now. The first time I rooted it with IOROOT and the USB debugging option stays enabled after reboot. The second time I rooted it with Stump root and the USB debugging option does not stay enabled after reboot. No idea what is different between them but maybe someone else can dig through and figure it out.
I have the same problem, when I reboot the phone and open titanium backup.
tech_head said:
I use Tasker with the secure plugin.
It allows turning on USB Debugging. I use it to turn on USB Debugging as a condition after boot.
Also the worst case with a script, you re-install/flash the OS.
Click to expand...
Click to collapse
Could you share how to set this up? Thanks
bamemanxxa3416 said:
Could you share how to set this up? Thanks
Click to expand...
Click to collapse
Set up a task with the "secure Settings" plug in.
You are going to go into the "System Actions" and select "USB Debugging" then select the radio button to "On" then save.
Now you are going to create a profile that uses an Event.
The even will be a "System" type of event and under system you will see "device boot".
Once you have created the event add the USB Enable task you created.
This all assumes you know how to use tasker.
problem fixed......
tech_head said:
Set up a task with the "secure Settings" plug in.
You are going to go into the "System Actions" and select "USB Debugging" then select the radio button to "On" then save.
Now you are going to create a profile that uses an Event.
The even will be a "System" type of event and under system you will see "device boot".
Once you have created the event add the USB Enable task you created.
This all assumes you know how to use tasker.
Click to expand...
Click to collapse
Very nice instructions and thanks for taking the time
because of stumproot, if using iosroot then problem will never appear.
ericsmart said:
because of stumproot, if using iosroot then problem will never appear.
Click to expand...
Click to collapse
Actually not true.
I used ioroot and I have the issue of USB Debug not sticking.
That's why I came up with the way to fix it in tasker.
tech_head said:
Actually not true.
I used ioroot and I have the issue of USB Debug not sticking.
That's why I came up with the way to fix it in tasker.
Click to expand...
Click to collapse
but, it's good to have other solution, it's all good that you guided them who have similar problem.
I have the same problem as you.
tech_head thanks for giving this tasker newb enough bread crumbs that I was able to figure it out and solve the problem (and learn something in the process).
Real easy check usb debug,then plug phone into computer go to your folder that you have adb shift right click mouse all at once open cmd window here check Ethernet mode on phone check rsa cert when prompted type adb devices press enter then adb reboot then enter when LG logo appears unplug phone now your usb debug will always stay checked
WHATSAMATTA U ALUMNI
the tasker approach is now disabled and deathsquad737`s approach has caused it to stay checked... Thanks!
Hi Guys
I found a easy way to fix it.
1) turn on USB debugging
2) Connect G3 to your PC
3) Reboot your G3 when keep connected to PC
4) Unplug
Now the debugging option will be kept.

Categories

Resources