Database Users

new to android! help!!!

so im new to the android phone scene i have had blackberry for 5 years noe and decided to try out the new HTC Evo. but im sooo lost with thing, help!!! please
first off my phone is running the newest software 1.47.651.1
im trying to root the phone but to do so all instructions ive found require using adb. what is this adb? and what is adb shell?
when i plug my phone to my computer it says the adb is not set up and it ask for the driver disk, phone didnt come with this.
also im running vista 32 on my laptop if it makes a difference.
any help with getting this done or where to find info would be great!!

adb is apart of the android SDK package which is required for transfer from computer to phone. google "android SDK" and download + install
you need it in order to transfer the files required for rooting to your phone so i suggest reading the instructions so you know what your doing

Need SDK
Android SDK can be downloaded at the following address:
http://developer.android.com/sdk / index.html
Once downloaded extract the folder to one of the PATH for example E: \ android_sdk_windows
i have tried in win xp and 7.
how to install SDK

wolf13 said:
so im new to the android phone scene i have had blackberry for 5 years noe and decided to try out the new HTC Evo. but im sooo lost with thing, help!!! please
first off my phone is running the newest software 1.47.651.1
im trying to root the phone but to do so all instructions ive found require using adb. what is this adb? and what is adb shell?
when i plug my phone to my computer it says the adb is not set up and it ask for the driver disk, phone didnt come with this.
also im running vista 32 on my laptop if it makes a difference.
any help with getting this done or where to find info would be great!!
Click to expand...
Click to collapse
I would suggesting following any of the threads on rooting the evo that tell you exactly what to do.
Simpleroot method:
http://forum.xda-developers.com/showthread.php?t=706411
http://forum.xda-developers.com/showthread.php?t=720565
Rooting the EVO for noobs:
http://forum.xda-developers.com/showthread.php?t=721055
Both of these are simple and tell you everything you need to do.

[Q] Duth(netherlands) G1 Cant Root

T-mobile G1
Firmware version 1.6
Baseband Version 62.50S.20.17U_2.22.19.26I
Kernel Version 2.6.29-00479-g3c7df37
[email protected] #19
Build Number DRC92
Hi guys ,new in here.
I have a T-mobile G1 that i Bought From Netherlands . I wanted to root and upgrade it into cyanogen but i had to downgrade it first into 1.5 or 1.0 . i tried many links and guides but i always get the 00028002 error and then the rainbow screen with the Serial0 error. many had the same problem but no clue ... Any Ideas??? i am 100% sure that the format of my SD is FAT32 but not sure about the file i download. i tried many.I cant even install the original SPL.
Thanks in advance!
on the Rainbow screen it shows these for me :
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.2

i have same problem

Can somebody pleas help us? of is a way or not , because is stressfull to waith for a message

What is easier than trying to downgrad is useing exploid exploit
Here is a draft of the steps:
http://forum.xda-developers.com/wiki/index.php?title=User:Ezterry/G1_1.6_To_Custom_Firmware
I made it in a rush so clean if need be.. but don't completely re-write if you want to do that post elsewhere.
As for the problem with downgrading is the files are only intended for US/UK dreams and you don't have one of those..
however my steps above are probably also safer for those with said dreams.. since it tries to avoid the brick potential with dangerSPL

Now i have been trying that link, but i cant go forward from step 3
run the following adb commands:
* adb push exploid /sqlite_stmt_journals/exploid
* adb push flash_image /sqlite_stmt_journals/flash_image
* adb push recovery-RA-dream-v1.7.0-cyan.img /data/local/recovery-RA-dream-v1.7.0-cyan.img
* adb push spl_1_33_2003.zip /sdcard/spl_1_33_2003.zip
* adb shell chmod 755 /sqlite_stmt_journals/exploid /sqlite_stmt_journals/flash_image
* adb shell /sqlite_stmt_journals/exploid

red_net0 said:
Now i have been trying that link, but i cant go forward from step 3
Click to expand...
Click to collapse
You run them from your computers command line..
Is there an error?

IT dosnt work and yes i have that line from cmd on my computer

red_net0 said:
IT dosnt work and yes i have that line from cmd on my computer
Click to expand...
Click to collapse
Unless you give details I'm not sure how you expect anyone to help
"It doesn't work" could mean:
1) adb/fastboot isn't properly installed on your computer
2) you are not running adb from the directory with the files
3) you are making a typo in the command line (or I made a typo in the commands in that document.. unlikely but not impossible)
4) phone doesn't have USB debugging enabled or is not plugged into the computer
5) Your USB port on the phone is fired.

Ok i think the first adb running and the 2cond I think? How can i running that adb ?

red_net0 said:
Ok i think the first adb running and the 2cond I think? How can i running that adb ?
Click to expand...
Click to collapse
Try either the xda thread for adb/fastboot/sdk or the adp1 developer site
wiki page said:
[size=+2]Install ADB/Fastboot[/size]
For this to work I expect that you have adb/fastboot installed on your computer and understand that adb/fastboot commands are entered into your computer; not the phone
The XDA thread on setting this up is: http://forum.xda-developers.com/showthread.php?t=532719 Otherwise additional information is on the htc adp site: http://developer.htc.com/adp.html#s2
Click to expand...
Click to collapse
Many windows users find it easiest to put the files in the tools directory with adb. That said I'm primarily OSX and set up the path to allow me to access the commands anywhere.

I have been trying to install adb but i dont have the SDK Setup.exe file!

2cond thing that i see is
that
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
I dont have a rooted HTC Dream

That line lies; adb is used by developers on non rooted devices all the time..
the setup is the windows drivers..
Questions about adb *if* posted in the adb thread will be read by many more windows users that may be able to help.
You don't need to pm if you are asking the question in this thread.

I thing
I have the problem that i cant downgrade i have been 1 month trying to downgrade my g1 no lukky!:S

Try downgrading to RC7.....instead of RC29.
I had DRC93 (Dutch G1) and I followed the follwing link step by step
http://forum.xda-developers.com/showthread.php?t=727688
remember to use RC7
.....mine is working perfectly

i really dont understand

I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.

mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!

Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.

You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G

ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.

tried your directions again
I have tried them again and they do not work.

Try the usb cable for the droid x. Its a really good one.

if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.

mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G

thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.

mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!

I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.

SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.

I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk

[Q] Trouble running adb

I am determined to downgrade and root my phone on my own, as opposed to paying someone on CL to do it for me. I just moved from Sacramento, CA to Cleveland, OH and I just got my comp unpacked and connected to the internet.
I Just downloaded SDK w/ all of the platform tools, ect. I have also been reading up on ADB and the appropriate commands. My only problem is my comp isnt recognizing the platform tools. it is located at the root of my C:\. Am I missing something? I was going to post in the development forum, but because I am new I can't. Can someone help me out please? I know I am close.
Thanks

How did you typed the command?

First of all be very grateful you can't post in the development sections because if you did it would only of lead to problems with these hungry users that are always ready to flame someone... Anywho...
Follow this guide to downgrade:
Downgrading
Follow this guide to downgrade and root the phone after that you can flash cyanogen if you want or anyother rom that u chose (((HINT: Black Unicorn Resurrected v4.1.1)))

lol, thanks for the heads up.
Does anyone have a link to a thread that shows step by step what to type and what the correct returns would look like?
The all seem to be a little different, and maybe im just an idiot but its pretty confusing seeing so many different ways to accomplish this

Ok, so I am going to try the wiki way to downgrade and root my phone. Hopefully this works.
Thanks for the help

TurboBrickMike said:
I am determined to downgrade and root my phone on my own, as opposed to paying someone on CL to do it for me. I just moved from Sacramento, CA to Cleveland, OH and I just got my comp unpacked and connected to the internet.
I Just downloaded SDK w/ all of the platform tools, ect. I have also been reading up on ADB and the appropriate commands. My only problem is my comp isnt recognizing the platform tools. it is located at the root of my C:\. Am I missing something? I was going to post in the development forum, but because I am new I can't. Can someone help me out please? I know I am close.
Thanks
Click to expand...
Click to collapse
So you have your platform-tools folder in C:\platform-tools? right?
Go into that platform-tools folder under command prompt, and type adb shell, see if it can detect the device.

Try this thread for adb help:
http://forum.xda-developers.com/showthread.php?t=928370

Thanks
Thank you guys for all of your help. It worked! My phone is now downgraded back to Froyo. Next is Root w/ S-Off and Cyanogen Mod.

[Q] Setup rom request

Morning all,
So here is the deal. Buddy of mine broke his phone last night, I gave him one of my spares and he is keeping that. I took his broken S4.
The screen si dead and the digitizer does not work
Had CWM flashed on it but stock rom when I gave him the S4 initially
I tried every possible way to get usb debugging working without the screen. edited the build.prop and default.prop
change the settings.db no luck
using adb in recovery i was able to flash cyanogenmod 10 as i read it had usb debugging enabled by default
well after the flash and booting the device (using an MHL) i still cant access an adb shell. I'm guessing i have to go through the setup process of cy mod before it kicks on maybe.
so i'm stuck here. now what I was hoping, and I know its a long shot. Could someone maybe make a nandroid of a stock rom, any rom that is rooted. but with vnc or other remote software installed and setup so I can flash and access this device.
I was also going to try to find a TV with CEC support as I heard the MHL will pass them through
If I can convince someone to upload a nandroid for me (I'll provide hosting) anyone have any ideas on controlling this thing remotely. I just need to be able to install arliberator, pair it with my cars deck via Bluetooth and i'll be good to go.
-pete
More thoughts. Having usb debugging enabled is clutch. Just realized, it wont be on my wifi so vnc wont work to well. I know droid vnc and do usb using adb. so maybe thats my best bet

making some progress
Copied the wifi settings from wpa+supplicant.conf from my brothers phone
so the S4 witht he broken screen now connects to my wifi
I installed the droid vnc apk using recovery
also installed it on another phone, setup the way I want
copied the settings folder from the /data/data frolder and copied it to the S4
chmod the folder and files to 777 and set 776 on "androidvncserver" file not sure about that step
cant get vnc to connect. but making progress

made a bit more progress
downloaded fastdroid vnc
pushed it to /data/ in recovery using adb
set 777 as i didt feel like dealing with permissions
made a super simple script to load it and placed in /data/local called userinit.sh or something like that
so it started and I was able to make a vnc connection, but it was all black and didnt accept mouse or key inputs.
i assume this is because it is no longer maintained and is many years aold
tried to do the same with droid vnc server and starting the androidvncserver file.
unfortunatly it never accepted a connection and i'm not even sure if the file starts
need more work
anyone willing to save me all the trouble and get me a nandroid with usb debugging enabled? pretty please! :crying:

Final update. Working
so I ended up placing androidvncserver in /data/
chmod 777 /data/androidvncserver
placed my wpa_supplicant.conf in /data/misc/wifi
chown system.wifi wpa_supplicant.conf
made a userinit.sh and pushed to /data/local/userinit.sh
chmod 777 /data/local/userinit.sh
reboot
connected to wifi, accepted the vnc connection and mouse movement. still a black screen but with the MHL and the mouse. I was able to get ARliberator installed and connected to my appradio2 and configured everything there
done