Rooting issue - General Questions and Answers

I'm trying to root my phone by using Pre-kitchen but when I do the "diagnostic" test I get this error message; "cannot find a part of the path C:\Documents and Settings/acollins/Destop/adb/help.bat' can anybody help me?

well for starter the thread name is wrong, your supposed to give an insight into the issue you're having
secondly, without any knowledge of the actual phone you have then people cant really be of any assistance can they
if you explain the problem clearly along with the name of the phone you have then people will be able to provide help
also giving us a clear idea of the type of computer you have and os its running#

HTC Hero
I tried going back and changing the thread name but it wouldn't let me edit.
I have a HTC Hero that I'm trying to root on a windows XP computer. I tried using Flash's pre-kitchen and have followed the directions as listed on the website. When I try to run the program, during the "diagnostic" stage, I get the message "cannot find a part of the path C:\Documents and Settings/acollins/Destop/adb/help.bat'. I copied pre-kitchen into the C directory thinking that was the issue but still get the missing "adb/help.bat" message.
I read in a forum somewhere that I need to have Android SDK installed on my computer and that I could also get that from this website (xda) but I'm not sure I need it and what exactly it is.

Related

[HOW-TO] ADB for Dummies(How-To Learner's Guide)

Hi,
My name is Joe aka AndroidSamurai.. I will be releasing more guides and media content in the weeks to come.
I'm currently very busy with "life events(new baby)" and apologize for my absence.
I will be updating this post since it was my original with a new guide updated to new SDK and Android methods.
Thanks again,
AndroidSamurai
Android4D Inc
<golf clap>
Well done.
</golf clap>
What do i do if the new hardware device notification doesnt pop-up ? NM i got it. Thanks for the writeup
@King_tee: Assuming windows, you follow the following steps.
1. Start > Control Panel > System.
2. Hardware > Device Manager
3. Click on the last icon below the File menu. It should correspond to "Scan for Hardware Changes."
If that doesn't work, try unplugging / replugging USB cable, different USB cable, restarting phone, restarting computer, etc.
If you never see the notification, navigate to the Device Manager(inside "System" in the control panel in XP and inside Device Manager on Vista).
You will see ADB Android Device at the top of the list with a Yellow Icon beside it meaning the device is not working. Right-click on the device and select "Update Driver".
Follow the dialogs that pop-up and navigate to where the unzipped drivers are at...
You should be good to go from there...
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
devildogg2001 said:
ok, i need some help please... I downloaded the SDK and followed the instruction in this thread, but when i try to update my driver for the phone, it says the driver is not compatible with my phone.. I am using Haykuro's ROM 4.5 with FW 1.5.. would that be the reason for this issue?
Click to expand...
Click to collapse
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
I dont know if thats the problem because when i plug it in, it doesnt show up as a notification, and when i go to the device manager it shows the little yellow triangle.. I'll look again. Thanks for the quick reply though. I am no expert in linux, but i have it installed, let me see if i can figure it out there..
tubaking182 said:
you may need to uninstall the current driver for your phone if you have mounted it before downloading the SDK. if you don't have the SDK setup the first time you plug the phone in then your computer will auto-update the driver to a regular UMS driver and it won't help you when you try adb. i forget how to uninstall your current driver since i don't use windows, but i'm sure you can find a nice crash course online
Click to expand...
Click to collapse
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
devildogg2001 said:
ok, so i am in linux now, and i just noticed this guide was for windows.. lol can you or someone tell me how to install the SDK on linux?
Click to expand...
Click to collapse
Downloading
http://developer.android.com/sdk/1.1_r1/index.html
Installing
http://developer.android.com/sdk/1.1_r1/installing.html
Found through Google...imagine that.
as well as what xyrcncp said can you you can download it and just mv ~/Desktop/sdk/tools/adb /usr/bin/adb abd you should be able to run the adb commands from any directory. not too hard to cd to the correct directory but i personally don't like to type cd ~/Phone/tools/android-sdk/tools every time cause i tend to make typographical errors. let me know how it worked but you shouldn't have any problems at all
umm no offense but your writing a tutorial for people that are not sure on how to do this, so you must assume that they do not know how to run an executable file...... write yourself a better tutorial without actually bashing the self esteem of some people... tutorials are positive not negative. I already know all of this but still... dont degrade someone due to the fact they dont know how, thats the whole point of writing your tutorial. Nothing should have been left out (including how to run a .exe .com or .bat
" (If you do not know how to install a windows executable file, please kill yourself now! ) "
this isnt honestly written with any hatred towards you, it was a good tutorial. Just might want to think about how you write it next time.
The "bashing" comments in my tutorial are directed towards the people with a true sense of humor. My tutorial was written to tell you how to simply complete a task and not to make you feel better about yourself. I do not get pleasure in abusing people's self esteem nor do I enjoy putting people down.
Just because you got a little sand in your crack does not mean you need to come in a very honest and informative thread and start bashing the people who are bending over backwards to help everyone out.
The reason I created this "tutorial" in the first place was because all the other threads are full of "start searching and stop asking so many damn questions" comments.
So start looking in the mirror when you wake up in the morning and stop saying "My, I think I will run over to good ole' XDA and be an @$$ to everyone today".
I am sincerely sorry that a little sense of humor has caused so much hatred in my thread. Please contact the forum moderators and see if the think my tutorial is so hateful.
lol i dont see any hatred but anyway when i download the adb driver when extracting it says unknown method
@ Nabzilla1990
Are you using Windows or Linux?
Are you using the built-in Zip tool or 7-zip from the links I provided?
Are you using a 32 or 64-bit OS?
using the same operating system as you 64bit vista ultimate sp1 and using winrar to extract
Try using 7-zip man, I have been using it for 3 yrs now.
Basically what I am saying is that everything in my guide is guaranteed to work.
Just to add, if you take adb.exe and adbwinapi.dll and copy or move them to the \windows\system32 directory you can run adb from any dos directory prompt.
it worked with 7-zip thank you and also want to add if it doesnt work for some people plug in ur phone and update the usb mass storage with the usb driver from here and it should work i had that problem earlier
Okay, so I did everything and got up to run cmd, when I type in the cd C:\android-sdk-windows-1.1_r1\tools it says not a specififed folder, but when I type it without the \tools it doesnt work. can anyone help?

Cannot open ddms.bat in order to take screenshots on Nexus One

I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it
Open up a command prompt. (Start -> search "cmd")
use CD to get to the folder where you keep ddms.bat
open ddms.bat from the command prompt by simply entering "ddms.bat" then press Enter. That will keep it from closing the window.
Just to see if it gives any errors.
Thank you so much!
However the error message that cmd is now giving me is : WARNING: Java not found in your path.
Could you please tell me how I can do this? for the time being I'm searching the internet for help but the first thing I found seems super complicated
I finally got it to work, wish I could link the imgur pic, but I'm still a new user but here's the end of the imgur link code :ucBpY
TaeKwonDonkey said:
I finally got it to work, wish I could link the imgur pic, but I'm still a new user but here's the end of the imgur link code :ucBpY
Click to expand...
Click to collapse
how did you fix it?
Follow this guide....it may help you click me..!! :good:
thank you,
P.007

[Q] Help please! Sdk/usb problem

Computer Hardward: Windows Vista 32 Bit
Phone: HTC Hero-Sprint
Ultimate Goal: Putting Android 2.2 on my phone
I'm not a programmer or have any in-depth developing knowledge . However, I follow directions precisely. I feel like I've tried following several different directions on XDA and I start completely over each time trying a different one(uninstalling SDK and re-installing per particular directions) and they have all came to no avail.
The following link I will use as an example set of directions:
droidoholics.com/forum/viewtopic.php?f=20&t=187
BUT, when i get to this section in the directions:
" When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android-sdk-windows\google-usb_driver) and install the adb driver"
I follow the directions and I've verified the folder and contents are there. I unfortunately ALWAYS get the following message:
"Windows was unable to install your ADB"
"Windows could not find driver software for your device"
I need help getting past this beginning step and feel like I've looked everywhere and followed all directions. Any help out there?? I'm drooling in anticipation of getting 2.2 for my device that the carrier will not be updating. This small step is stumping me severely.

[Q] noon needs help figuring out how to root nexus 5 using a mac

Could someone help me figure out what I'm doing wrong when I try to root my nexus 5?
I've followed the many similar cf-autoroot instructions I've found online, but to be honest, I think that there must be some prerequisite steps I need to do before I can actually root.
Here's what I've done so far: I've downloaded the ADT bundle and installed the 4.4 SDK and recommended tools. I've also downloaded the cf auto root files and have them saved on my desktop. However, when I enter chmod +x root-mac.sh into terminal it says command not found. When I simply try to open the file from finder it opens the script in text editor, which obviously does nothing. I have no idea what I'm doing wrong. Everything i have seen online make it look so easy, but I'm getting nowhere... Could someone please help me figure this out?
Have a look here: http://forum.xda-developers.com/showthread.php?t=2515640
Using a toolkit my be useful if you're not sure of things, but obviously caution is still advised if you aren't sure what you are doing.
I used this with absolutely no problems. I was originally looking forward to manually inputting the commands in terminal just to get familiar with it but saw the Android icon. in my curiosity I clicked it and it started the process for me. Took a couple of minutes.
It's done on Mac just like it's done on ANY os.
You need fastboot and adb in your PATH or you need to have all the files in the same directory.
Sent from my Nexus 5

Unbricking / converting a BAT script to a POSIX shell script

It looks like following the official instructions on wiki.lineageos . org/devices/I01WD/install can brick your device if you're unlucky - at least for me, the bootloader seems to have vanished; trying to boot will just return a black screen. So, I looked for unbricking instructions. Unfortunately, the only two I found were getdroidtips . com/unbrick-zenfone-6-asus-6z-qdloader-9008-mode/ and piunikaweb . com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/, which both use BAT scripts. I only use Linux, which doesn't support such scripts, and I'm not familiar with the Windows shell. I wondered whether anyone here could convert the instructions for Linux? The driver installation shouldn't be a problem, as Linux is monolithic and lsusb shows the Qualcomm modem being in QDL mode (I suppose that's the same as QDLoader 9008/EDL?). (remove the spaces from the links)
FantasyCookie17 said:
It looks like following the official instructions on wiki.lineageos . org/devices/I01WD/install can brick your device if you're unlucky - at least for me, the bootloader seems to have vanished; trying to boot will just return a black screen. So, I looked for unbricking instructions. Unfortunately, the only two I found were getdroidtips . com/unbrick-zenfone-6-asus-6z-qdloader-9008-mode/ and piunikaweb . com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/, which both use BAT scripts. I only use Linux, which doesn't support such scripts, and I'm not familiar with the Windows shell. I wondered whether anyone here could convert the instructions for Linux? The driver installation shouldn't be a problem, as Linux is monolithic and lsusb shows the Qualcomm modem being in QDL mode (I suppose that's the same as QDLoader 9008/EDL?). (remove the spaces from the links)
Click to expand...
Click to collapse
Would this help you?
https://forum.xda-developers.com/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Or this:
https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
I am sure you can easily read windows batch and convert them to your favorite shell language. I suppose it is simply a list of adb and fastboot commands. I don't know if I actually can help, but I'll be available for discussion, if you have any problems during your try with either of the two options above.
abprie said:
Would this help you?
https://forum.xda-developers.com/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Or this:
https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
I am sure you can easily read windows batch and convert them to your favorite shell language. I suppose it is simply a list of adb and fastboot commands. I don't know if I actually can help, but I'll be available for discussion, if you have any problems during your try with either of the two options above.
Click to expand...
Click to collapse
The first links seems to be basically the same as what I found. The last one only works if the bootloader is still there, which is not the case. That's also the reason why I think, while not actually had looked into them, that it's not just adb and fastboot commands (those won't work anymore with my device). ADB only works in Android, and fastboot only in the bootloader. But yes, I'll look into it and see if I can do anything.
So, after looking into it, I noticed I basically understand even less of that script than I do understand Unix shells. I guess I'll probably ask in that thread however, as this seems to be the original developer of the script(s). (actually, there's several scripts, XMLs and so on there)
I had a quick look at the update_image_EDL.bat file and noticed that the file itself calls an executable in Windows format. I guess this won't be easy to convert.
But did you try to run this in wine?
I believe the best solution to your problem would be a VM with Windows 10 installation and USB support.
aleksander002 said:
I believe the best solution to your problem would be a VM with Windows 10 installation and USB support.
Click to expand...
Click to collapse
This would require the OP to own a win10 version and if that was the case, (s)he could also boot from a installation disk and run the scripts on a live boot. But still, maybe a true Windows version is required.
As far as I know, Windows 10 is free to install without key and it will be legal as a short-period evaluation copy.
aleksander002 said:
As far as I know, Windows 10 is free to install without key and it will be legal as a short-period evaluation copy.
Click to expand...
Click to collapse
True, might work...
So, while QFIL.exe would start with wine and Mono (apparently it's a .NET application) installed, it wasn't actually able to connect to the phone (I think direct hardware access is one of the things WINE cannot really do anyway). Thus I tried the suggestion with Windows in a VM and USB redirection, however, I got `ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.` and some other errors after this which were apparently caused by the first error when executing the `update_img_EDL` script. I found another solution that may possibly work: Using https://www.96boards.org/documentation/consumer/guides/qdl.md.html, however I don't really know which partitions I need, and which XML files I should use from the many that are present in the zip file. The signed ELF programmer is apparently `prog_firehose_ddr.elf`, at least that's what the script seemed to use.
EDIT: Looks like some people in the original thread are having the same issue as I do.
FantasyCookie17 said:
So, while QFIL.exe would start with wine and Mono (apparently it's a .NET application) installed, it wasn't actually able to connect to the phone (I think direct hardware access is one of the things WINE cannot really do anyway). Thus I tried the suggestion with Windows in a VM and USB redirection, however, I got `ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.` and some other errors after this which were apparently caused by the first error when executing the `update_img_EDL` script. I found another solution that may possibly work: Using https://www.96boards.org/documentation/consumer/guides/qdl.md.html, however I don't really know which partitions I need, and which XML files I should use from the many that are present in the zip file. The signed ELF programmer is apparently `prog_firehose_ddr.elf`, at least that's what the script seemed to use.
EDIT: Looks like some people in the original thread are having the same issue as I do.
Click to expand...
Click to collapse
Sorry for the late reply. Could you find out what kind of dragonboard the zenfone 6 has? I guess that will give you a clue through the manual linked at the end of you referenced threat.
Oh, and did you try to just install a win10 version as suggested before?
abprie said:
Sorry for the late reply. Could you find out what kind of dragonboard the zenfone 6 has? I guess that will give you a clue through the manual linked at the end of you referenced threat.
Oh, and did you try to just install a win10 version as suggested before?
Click to expand...
Click to collapse
Afaik Dragonboard is just the name of that line of SBCs which also uses Qualcomm SoCs. So while the Zenfone very likely doesn't use a Dragonboard as PCB, the SoC modes and such should be similar. The device-specific instructions most likely won't work, however the software should work on all Qualcomm-based boards.
I didn't try to install Windows 10 on my PC, however I also tried it at a friend's PC with W10, where I got the same error.
FantasyCookie17 said:
I didn't try to install Windows 10 on my PC, however I also tried it at a friend's PC with W10, where I got the same error.
Click to expand...
Click to collapse
Meaning that even the Windows scripts that reflash the bootloader did not work?
Interesting. Looks like the issue was the cable; it worked with a different one (though both cables had both data and power lanes).
I'm in the same situation, with a dead Zenfone6 and only a Linux desktop.
Was there a way to bring it back to life?
Marlin79 said:
I'm in the same situation, with a dead Zenfone6 and only a Linux desktop.
Was there a way to bring it back to life?
Click to expand...
Click to collapse
See the original thread which was linked here. (the cable I originally used did not work, however it wasn't the original one that came with it) The only way I see is downloading the Windows installer and starting that in a VM with USB redirection (e.g. use QEMU/KVM and virt-manager). Then install Windows in that VM (if you don't want to create a Microsoft account, disconnect from the internet before it asks you to do so), and then follow all the instructions in the original thread.
FantasyCookie17 said:
See the original thread which was linked here. (the cable I originally used did not work, however it wasn't the original one that came with it) The only way I see is downloading the Windows installer and starting that in a VM with USB redirection (e.g. use QEMU/KVM and virt-manager). Then install Windows in that VM (if you don't want to create a Microsoft account, disconnect from the internet before it asks you to do so), and then follow all the instructions in the original thread.
Click to expand...
Click to collapse
My Asus brick has been lying in my drawer for a while but I had a bit of spare time so I thought to see what I could do with it. I have a bit of spare parts so I put together a bare bone computer and installed Windows 10 on it (the windows installer iso-file from microsoft.com)
I then tried to follow this guide https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
But when running the update_image_EDL.bat script I get "Environment variable _COM not defined". The USB cable I'm using is the one that came with the phone.
I know next to nothing about Windows. Somebody who has an idea what to do about that error message?
Marlin79 said:
My Asus brick has been lying in my drawer for a while but I had a bit of spare time so I thought to see what I could do with it. I have a bit of spare parts so I put together a bare bone computer and installed Windows 10 on it (the windows installer iso-file from microsoft.com)
I then tried to follow this guide https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
But when running the update_image_EDL.bat script I get "Environment variable _COM not defined". The USB cable I'm using is the one that came with the phone.
I know next to nothing about Windows. Somebody who has an idea what to do about that error message?
Click to expand...
Click to collapse
Yes. Happened to me, too. The problem was that the phone is not recognized as a Qualcomm device in Windows. I had to open it and bridge two points on the board. See this: https://forum.xda-developers.com/showpost.php?p=82965385&postcount=66
I finally got to the stage where i could execute update_image_EDL.bat script
It ran for a minute or so but then terminated in an error.
Code:
13: E:\firmware\prog_firehose_ddr.elf
06:28:01: ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
06:28:01: ERROR: function: sahara_main:983 Sahara protocol error
06:28:01: ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'QMSL_MSVC10R.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at QC.QMSLPhone.Phone.QLIB_DisconnectAllServers()
at QC.QMSLPhone.Phone.DisconnectAllServers()
at QC.QMSLPhone.Phone.Finalize()
2020-07-11 06:28:02.931 Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
press any key to continue . . .
Any ideas what that is about? The file it mentions QMSL_MSVC10R.dll does exist in the firmware directory

Categories

Resources