Hi, I have a problem with ADB: when phone connected check if adb sees it with the command 'adb devices' shows me the error 'can not connect to daemon, Create Process failure, error 2'. Of course, all of the drivers installed, even i installed a lot of unnecessary packages to be sure sdk is installed correct. I have tried many ways but it's all for nothing. The important thing is that before starting play with the Desire Z went without any problems, without any errors adb seen the phone. Unfortunately, because of the desire goes to sell had to restore it to factory condition, but I had to get rid of the other phone so the Desire Z came back to me. Since then the problems started. If anyone would have any idea kindly ask for help. Thanks in advance.
I assume you made sure adb is turned on on the phone. Try uninstalling then reinstalling the drivers. If that doesn't work (i assume you have windows) change the path in environmental variables. You can try adb kill-server then adb start-server
See if any of this helps
Sent from my Desire Z using xda premium
Which ROM are you using? I had similar issues with some CM7.2 builds.
If you have the option “ADB over network” in “Developer options” try to switch it on/off. It helped for me.
Thanks a lot for answers but i already did all this methods :/ Realy dont help. And about my rom i have stock 2.2 at the moment, that's why i need adb...for root,S-OF
Have you tried a different USB cable? Sometimes it will work for charging and such but will not work for adb or fastboot, only poorly made cables are like this so its rarely an issue. I still think the problems lie in th drivers, did you uninstall and manually install the right ones? Don't let windows do it
Sent from my Desire Z using xda premium
Yes sure i tried with 3 different cabels and always install drivers manual on system partition C:
Looking back over your posts it looks like you can even start adb on your computer, phone/cable makes no difference if you can't open adb. What exactly is your path in environmental variables? My guess is this is set up wrong. Find the folder that adb.exe is in on the computer and make sure the path is set correctly to this.
And just for fun, find the folder, find adb.exe, hold shift and right click within that folder. Now choose open command here. Now type just
adb
What happens?
If you need help setting adb up I wrote a fastboot guide (includes setup for adb/fastboot) http://forum.xda-developers.com/showthread.php?t=1728208
Check out the third post for instructions
Sent from my Desire Z using xda premium
Listen i read about installing sdk 2 years ago, i have of course path edited correctly to the folder where adb is...
Which API do you have? Older ones put adb in tools, newer in platform-tools, if you just open a command and type adb (without phone even connected) it should open. If not then you will need to change directories (or the path) if it still won't run then you don't have adb.exe installed correctly.
What happens when you open a command prompt from within the folder adb.exe is in? Have you tried that?
Adb does not need a phone connected just to run, having the right drivers won't matter if adb isn't even running on pc.
Sent from my Desire Z using xda premium
Btw. now im installing again sdk, tell me is it normal on start of installing packages i see: "Installing Android SDK Platform-tools, revision 14
Stopping ADB server failed (code -1)."
Or is it a problem and that's why i cant work with adb ?
Completely uninstall all of the SDK and remove your path in environmental variables. Then install SDK directly from google, install all the platform tools (the whole first section) make sure you check you updated java (jdk needed?) Open a command window where adb is and type adb and check for error codes, if all is good then update path in environmental variables
Sent from my Desire Z using xda premium
Tell me if i delete PATH accidentally can i create it again in environment variables ?
Yup, and just so you know creating a path just makes things easier, it isnt needed. If you want just open the command where adb.exe is located or change directories.
Sent from my Desire Z using xda premium
And in PATH i should only add "C:\SDK\platform-tools" nothing more ? Sorry for my noobish questions, i didnt work with Android for 7 months i lost a lot of memories
I remember i should always add backslash on the end right like: "C:\SDK\platform-tools\" ?
yep and don't forget to seperate the values with a ;
Sent from my Desire Z using xda premium
About drivers i should install HTC Driver installer and HTC BMP Driver ? All in same location ? Best on partition system C or other ?
EDIT: I tried so hard as i can and now everything work, adb se my phone and my Desire Z is rooted Thanks a lot for all answers.
Related
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
I bought the Motorola Bravo which is similar to the Flipside and an app on the market called Z4ROOT was able to root the phone. It works on many phones not just the Bravo. Give that try and see if it works.
z4root does work for permanent root i have tried and can confirm
jediskywalker said:
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
Click to expand...
Click to collapse
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Got my Flipside rooted and non market apps allowed
I followed the instructions given at modmymobile dot com forum. Look up "fully unlock 3rd party apps backflip" It allowed me to root my phone and install non market apps. I tried and tried to follow the instructions given here, but i guess they weren't idiot proof. It is for the backflip, but it worked perfectly for my Flipside. I couldn't post the link here.
Someone found some typos in my scripts. I have updated them so they are accurate. Should make things run better.
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
ishiiisbooyah said:
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
Click to expand...
Click to collapse
Lets say you installed your SDK in the default folder, you would need to type
Code:
cd c:\"Program Files"
cd Android
cd appinventor-extras
Now, I put mine in c:\SDK, so all I type is
Code:
cd c:\SDK
you either must add the SDK to your PATH, or find the directory that you installed it to, and then try running adb from there. If adb.exe isn't in the folder, you aren't in the right folder.
jonsjava said:
Rooting a Motorola Flipside
[/url]
Click to expand...
Click to collapse
hi
i m new in unlocking field
can i unlock this handset "flipside" by motorola came from usa at&T
if yes then plz explain
thanks in advance
RZ4root does not appear on the marketplace and when I click the link above it starts to download, then says the content is not supported on my phone.
Model num MB508 Motorola Flipside running Android 2.1 update 1.
You need to push it to the phone from a computer using adb to install z4root, now that it has been removed from the market.
Sent from my Liberty using Tapatalk
adb.exe not in the zip file
jonsjava said:
Rooting a Motorola Flipside
grab the ADB SDK files
android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
(...snipped...)
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Click to expand...
Click to collapse
adb.exe is not present in the SDK that you linked. Are you sure that is the SDK we need to root the Flipside?
You have to install it manually. It comes with the platform-tools.
how do i install adb.exe from platform-tools
lol, i may ask stupid questions but this one wasnt me, i shouldnt leave my laptop lying around haha
jonsjava said:
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Click to expand...
Click to collapse
Notice:
For anyone having trouble rooting the Motorola Flipside with these instructions, after much trial and error I managed to get my girlfriend's rooted. I'll provide the method I took.
Note: The easiest way to do this is to have downloaded and extracted "android-sdk_r08-windows" directly to your (C: ) drive. Not under programs or another system folder.
Once you have it extracted to (C: ), copy and paste z4root.1.3.0.apk into the "android-sdk_r08-windows" folder. ADB.exe will most likely not be in here. What you have to do now is click on SDK Manager within the SDK folder. A Black Command window will pop-up, ignore it. A secondary window will pop-up prompting you to install the packages I went ahead and installed all of them (better if you don't know which to install).
Now that they've all been installed, a command line will state that ADB has to be restarted. Let it restart and it should say completed.
Now -- here's where everything was messing up. When you click open the SDK-R08 folder, you should have the z4root.apk file right there amongst a list of folders. Go to the "platform-tools" folder and in there you should see the ADB.exe file. Ignore that for now. While in platform-tools press Ctrl+A so that everything is highlighted. Right click and select Cut, back out to the main directory of the SDK R08 folder and select Paste so that the ADB.exe, .dll, and all the other files from within platform-tools is out and listed alongside the z4root.apk.
Next - Follow all of the instructions up to "Plug in your phone, and have it set to "Charge only" Like JonsJava said, open up command prompt (type in CMD in the "search programs and files bar"). If you extracted the "android-sdk-r08-windows" file directly to the (C: ) drive, all you have to type in is...
(Note: Before I go into that, it'll be easiest to rename the file "SDK" instead of the whole "android-sdk, etc, name... I'll complete the instructions assuming you renamed it to SDK. Continued below... all you have to type in is...
cd C:\SDK
(The next line below will look like this)
c:\SDK>
Here, type in... adb install z4root.1.3.0.apk
Total should look like... c:\SDK>adb install z4root.1.3.0.apk
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Last note:
Uploaded with ImageShack.us
This is what the main directory of the SDK folder should look like before you enter anything in the command line.
I don't seem to be able to get this...
I'm using x64 windows 7, I have a Flipside MB508 on 2.1, and I can't get this to work.
I followed all the instructions, updated all the platform-tools stuff, and now my problem lies with the driver, I believe.
I installed those Motorola drivers that were linked, with my phone unplugged, successfully..
copied the apk to C:\SDK...
found adb.exe in the platform-tools folder..
...and this happened..
C:\SDK\tools>cd C:\SDK
C:\SDK>cd platform-tools
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
error: device not found
C:\SDK\platform-tools>_
"error: device not found" every time i try this
USB debugging is on, phone is plugged in set to charge only..
Windows even sees it, the taskbar eject icon says 'Eject MB508"
please please help me get adb to see my phone.. I really want to be able to root this thing!!
EDIT: I noticed the Motorola drivers are 32bit.. I'm going to try 32 bit windows 7 instead of 64 bit and see if I get more successful results
EDIT 2: Bazinga!! Installed Win7 32 bit on my other HDD, booted up, followed the steps again, worked flawlessly! Thanks a lot for the easy instructions, got z4root installed, and my phone worked with permanent root
ErebusRaze said:
Notice:
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Click to expand...
Click to collapse
You wrote in here that once rooted, thebphone would no longer have low memory issues...i rooted my wife's phone, was able to sideload applications (but for some strange reason I am now unable to, as adb command prompt states 'device not found')- but she still gets low memory issues at least 2-3 times a week...
I should just hold up a sign...
LINK2SD
Its in the market
Sent from my MB508 using XDA App
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
thehotrod11 said:
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
Click to expand...
Click to collapse
Link2sd makes installing to sd card possible on 2.1...
Sent from my MB508 using XDA App
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
DressedUpPanda said:
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
Click to expand...
Click to collapse
The PATH issue, relates to ADB, if you are running into errors like:
'adb' is not recognized as an internal or external command
Click to expand...
Click to collapse
When executing ADB commands that is your issue, it can be resolved by adding the path where ADB lives to either your user or system PATH in Windows. The PATH is irrelevant if you are running ADB from the folder where the ADB files live.
The other (common) issue is drivers, where ADB is working but won't see your device. Do you see an "ADB Device" or similar with a yellow icon in your device manager when your phone is connected to your PC? If so you don't have the correct driver loaded. The only reason you install HTC Sync is to load this driver but the driver can also be loaded separately.
Sorry to hi-jack this thread, and since I'm new to adb I might as well use this.
I have adb running, did the file paths and everything. I'm just trying to test it out, since I'm already rooted using visionaryr13 as well as s-off. Went back and gfree over that, and I've also verified through terminal emulator on my phone, but I'm just testing my skills with adb and failing miserably. I Have d/l the verify file, and unzipped in a folder inside my downloads folder I might add.
When it says:
"
VERIFY (using "gfree_verify")
Now you can try using a new SIM card to verify that it worked.
In addition you can use gfree_verify to verify the state of your locks.
Download gfree_verify.zip from gfree_verify_v01.zip
ON YOUR PC:
Unzip gfree_verify_v01.zip to a place on your computer. Navigate to where the file is on your computer, and type:
$ adb push gfree_verify /data/local
"
I'm having a problem with the navigate to where the file is on your computer and type. I have cmd open, and have tried everyway but the right way to push this through. This is the error I'm getting.
cannont stat 'gfree_verify': no file or directory
EDIT: I got it and I'm sure everyone is laughing at this idiot. So in the cmd prompt you have to navigate to where you put the folder, then push the file to your phone, DUH!
OK, stupid question number two, since I answered number 1.
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
mrbmg said:
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
Click to expand...
Click to collapse
Type "exit".
ty ty.
Ok so I updated something in adb and it's not working. LOL, well restarted, and now the sdk manager is updating some more stuff so hopefully that is the reason I was not getting in.
EDIT: everything is working now.
Ty stevie, really appreciate all your hard work helping us noobies man!
steviewevie said:
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
Click to expand...
Click to collapse
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
DressedUpPanda said:
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
Click to expand...
Click to collapse
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
steviewevie said:
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
Click to expand...
Click to collapse
Ok well here is the path that i have set up.
- C:\AndroidSDK\tools;C:\AndroidSDK\platform-tools
I saved the file right to my "C" drive so thats why i didn't go to the program files. I also changed the name of the folder so it was easier to type.
Edit: I got it to finally recognize my device. I went back to my path and found that i had spaced in between my ';' and 'C:/' so thank you very much Stevie on making me double check it!!!
Hey guys I'm getting setup to root my buddies Evo shift. I Dloaded android sdk followed the instruction. I've opened cmd.exe when I type in a command it says it says 'adb ' is not recognized as an internal or external command, operable command or batch file.
I'm trying it out on my Evo first just to get familiar with the system any direction is greatly appreciated
Sent from my PC36100 using XDA App
30bushido1 said:
Hey guys I'm getting setup to root my buddies Evo shift. I Dloaded android sdk followed the instruction. I've opened cmd.exe when I type in a command it says it says 'adb ' is not recognized as an internal or external command, operable command or batch file.
I'm trying it out on my Evo first just to get familiar with the system any direction is greatly appreciated
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What version of windows are you on? You followed all of the instructions on setting up adb from that thread in the Shift forums? I also rooted my roomate's Shift, and I read that adb setup tutorial when I was over there. It was pretty solid. I already had adb set up, but read it through to see. When I set up adb, I had someone advise to me to place the adb.exe, and that .dll file (found in platform tools, in the SDK download) in my 'system32' folder of my PC. Once I placed those two files in the 'system32' folder, adb has worked flawlessly.
Also, have you made sure you have all the correct drivers installed? I believe I also had to install HTC Sync, because that installed some drivers that were necessary. Once it installed, I uninstalled it (the drivers will remain installed) because it can interfere with adb communication, apparently. Hope you get it set up. Once you do, rooting the Shift wasn't hard. Just follow the instructions to the t, and just copy and paste the commands, to eliminate the possibility of messing up the commands.
Thanks man I'm gonna give the HTC sync thing a shot
Sent from my PC36100 using XDA App
30bushido1 said:
Thanks man I'm gonna give the HTC sync thing a shot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You're welcome, feel free to PM me if you have any more issues.
to get adb to work, you need to be in the same directory as all of the sdk tools to use my setup as an example, my stuff is located in
C:\SDK\platform-tools
when I open the cmd prompt, it starts in
C:\Documents and Settings\Chris>
to change directories, type
C:\Documents and Settings\Chris>cd \
the display will change to
C:\>
type (in my example, yours may vary unless you set your folders up the same way)
C:\>cd SDK\platform-tools
it will change to
C:\SDK\platform-tools>
then you will be able to use adb commands like push/pull, shell, devices, etc.
Muellersirch said:
to get adb to work, you need to be in the same directory as all of the sdk tools to use my setup as an example, my stuff is located in
C:\SDK\platform-tools
when I open the cmd prompt, it starts in
C:\Documents and Settings\Chris>
to change directories, type
C:\Documents and Settings\Chris>cd \
the display will change to
C:\>
type (in my example, yours may vary unless you set your folders up the same way)
C:\>cd SDK\platform-tools
it will change to
C:\SDK\platform-tools>
then you will be able to use adb commands like push/pull, shell, devices, etc.
Click to expand...
Click to collapse
By putting the adb.exe and the .dll files in the 'system32' folder, that will allow you to execute adb commands from any directory in the command prompt. I don't have to navigate to my sdk tools to use adb. It saves a few steps, so you can just open up your command prompt and command away.
Or you can put the directory that contains adb in your system PATH. This will let you execute adb in a command prompt anywhere...
Sent from my ADR6300 using XDA App
I'm running wd7. I've gone through it again and installed the drivers then uninstall HTC sync I'm still not able to access sdk through the command prompt. I know its something simple I'm missing how do I move adb to the system path
Sent from my PC36100 using XDA App
C:\user\paul>
Is what the terminal reads any command I enter is not recognized as an internal or external command.
I have got the command list to show up but cannot exicute any of them
Sent from my PC36100 using XDA App
I hope this is in the right place, please mode feel free to move or flame me.
I've read the guides and know what I need to be doing, but I'm having trouble with downgrading. I've downloaded the downgrade and the zip file, but once I'm in the cmd prompt the code I'm putting in is not working. I've got HTC Sync installed on my of, but.I've.noticed that the adb shell tag is not.present in the cmd prompt bar accross the top.
Now the guides require HTC sync or adb drivers. Am I missing something obvious?
Sent from my Desire HD using XDA Premium App
Waiting for the answer..
Sent from my Desire HD using XDA App
i dont think htc sync is the problem.. the problem is , do you have the android adb file ?
if you are using windows, then download the adb file here .. --> http://dl.dropbox.com/u/22096653/Android-adb.zip
extract the file (at desktop for example) , and then cmd, point to the folder ..
cd /desktop/android-adb/
only then you can use "adb" command..
Im still having trouble.
I extracted the adb file to c: along with the downgrade folder and radio tool etc.
Once in the cmd prompt i can change directory and get to
c:/downgrade
From here i just get error messages.
I tried installing htc sync to see if the drivers from that will help but i seem to be missing something.
Also i just cant get it to work on my windows xp sp2, but can get to this stage using a windows 7 sp3 laptop
Hmm.. Make 'Charge only' and 'USB-debugging'. And try again.
Already tried that.
It's wierd, although its been a while since I rooted anything I'm struggling to do the most basic part when it comes to the DHD. I rooted and flashed my G1 like a whore, but can't even downgrade this thing.
Sent from my Desire HD using XDA Premium App
hi my htc desire keeps restarting when i flash any gingerbread miui rom i have tired data2ext and a2sd and have wiped and also formated my sdcard and stil have same problem with both but it works fine with all other roms and the froyo version of miui. please help
What hboot are you using and how did you root your phone?
Sent from my HTC Desire using xda premium
hi im using normal hboot-0.93.0001 i used unrevoked to root my phone i am not really a noob i have flashed and rooted many phones but for some strange reason all other roms including miui froyo work on my phone but gingerbread miui wont it loads up to the home screen and then just reboots ive tried data2et version and a2sd version and same thing happens with both versions.i have also tried using diffrent recoverys amon-ra,clockwork etc and still get the same problem.
You need to understand what is going on under the hood.. Getting an adb logcat is the way to go..
Code:
Windows>Start>Run
echo "null" > log.txt
start log.txt
adb logcat > log.txt
Use Notepad++ to associate with the txt file and reload the file every couple of seconds while keeping the cmd shell in the background.. See what's happening just before it reboots. It could be anything from a bad script to a bad module
Have you tried gingerbread 2.8, its simple and a very plain ROM, I have had issues with miui roms with my desire, if that doesn't work I will keep looking my self, sorry I'm not very insightful, you have an odd problem.
Sent from my HTC Pyramid using xda premium
Nice one Droidzone, I will have to try that also.
Sent from my HTC Pyramid using xda premium
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
casanova786 said:
Hi droidzone thanks for your reply could u please maybe help me and tell me the steps to get the log cat i know how to access adb by cmd but thats about it im a noob when it comes to adb commands and dont know much about it and didnt really understand the commands that u asked me to do,do i enter those while in adb or before.
Click to expand...
Click to collapse
Once you open a command line prompt in the folder where adb is installed (or anywhere else, if the file adb.exe is in your Windows path variable-Dont worry about that if you dont know), you can directly type each line of the commands starting from step 2.
Before that, install Notepad+, and associate .txt file to open with it by default..
By the way, you have to start typing those commands directly after rebooting from recovery after installing the Rom..
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.also i typed the commands u gave me once in adb and it says "the process cannot access the file because it is being used by another process."
casanova786 said:
hi droidzone i have installed notepad++ but dont understand how to install Notepad+, and associate .txt file to open with it by default. also my adb is located in c:\androidsdk\tools that is what i type in cmd to get adb working and if i type adb devices it shows my device.
Click to expand...
Click to collapse
Hmm.. I seem to be offering more Windows support than Android!
I meant Notepad+. Hold Shift, rightclick any text file, Choose Open with Notepad+ as default. You can go to your adb folder like you normally do and then type each line I posted and hit Enter after each time. You can also make a batch file with all those commands (search Google for that if you dont know how)
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
casanova786 said:
hi thanks i have made notepad+ to open as default but when i type the commands u told me it says "the process cannot access the file because it is being used by another process."
Click to expand...
Click to collapse
Hmm yes, that can happen if you have more than one adb.exe process running in the background because you exited it by closing the command shell with the close button instead of typing
Code:
exit
after done with it.
Use Ctrl+Alt+Del or Process Explorer to terminate the background adb.exe processes