Hi everybody.
This worked for me so hope it helps you.
Extract Rom files, copy nk:nbf to your device folder ieH20B, copy SetOperator &
xda3nbftool(found in PH20B1) into PH20B copy this folder into C drive (C:\PH20B) or whichever is your
local/main drive
Now click Start-run,type cmd click ok
in the command line window type the following (where [ENTER] means hit the ENTER key)
cd \ (space after cd) [ENTER]
cd PH20B [ENTER]
SetOperator O2UK001 (your code) [ENTER]
when completed type exit [ENTER}
basically cd means change directory.
starting from c:\, and wanting to get to c:\my documents\pocket pc\helmi rom\ph20b, you would type:
cd c:
cd my documents\pocket pc\helmi rom\ph20b
setoperator .....................
I copied the folder Ph20B to C: drive to simplify the command prompt
if you type cd C: it just copies the same line of text
Type cd \
you get
C:\>
Type cd PH20B after >
you get
C:\PH20B> then type SetOperator & code after > and hey Presto you get
Setting Operator to[???????] for ROM
updated checksum to ????????
Completed
C:\PH20B> type exit after > to close prompt
stealph said:
if you type cd C: it just copies the same line of text
Click to expand...
Click to collapse
sorry, typo - i meant c:\
No problem
After searching for ages for a step by step guide, i remembered i'd done something with command prompt to intergrate XPsp2 into XP and it helped me to understand this.
Just hope it helps others
Hi developers, senior members and all who have knowledge to dump or create a rom.
All these shortcut language kills me. What I want is my original ROM saved, in case of damage (to restore for warranty).
What I did so far is that I have the 4 raw files actually successfully stored, but from than on it´s start to be difficult.
I used now "BlackStoneKitchen" as admin. but it stucks after starting BuildOs.exe. Wich means I can´t get the 4 files as a *.nbh or *.nb or what ever.
Somebody said in this forum (thread) you will loose your warranty because of your SPL is older than the current one and other people said there is no problem.
I´m tired to seach around in this thread to confuse myself continue, because you will not get an concrete answer.
I´m ready to give my original ROM (4 files raw) to this forum or for wiki to update the Rom list. The latest Rom that I saw is from November and I have from December (NL).
If there is a developer who can help me to do it for me, please let me know. I was seaching in this thread and I saw that I´m not the only one who have this problem. That is why I decide to pay for this work and I´ll donate a better and newer Rom.
I hope there is somebody who have mercy for my begging
Taken from Raphael ROM thread found here http://forum.xda-developers.com/showthread.php?t=427507
This is based on the assumption that you have a 1.14.x NLD ROM!
- Download official HTC 1.14 NLD ROM for RUU_signed.nbh from http://rapidshare.com/files/182960521/Blackstone_HTC_NLD_1.14.404.3_R.ZIP (link from Blackstone Wiki).
- Extract the zip file and you have the file "RUU_BlackStone_HTC_NLD_1.14.404.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe".
- Use 7-zip or another tool to extract all files from "RUU_BlackStone_HTC_NLD_1.14.404.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe".
- You will have - among other files - the required "RUU_signed.nbh".
- Download the Blackstone kitchen from this thread http://forum.xda-developers.com/showthread.php?t=438456 and extract it.
- Place Part01.raw, Part02.raw from ROM dump and RUU_signed.nbh in the folder BaseROM.
- Start BlackStoneKitchen.cmd
- Select "(e) extract a rom", "(b) if you want to rebuild and cook dumped ROM into flashable ROM" and wait for extraction process to finish (Message "Now start cooking your ROM!"). You should now have additional folders "OEM","ROM" and "SYS".
- Press space (or any other key) to return to the main menu.
- Select "(c) cook a rom", "(a) if you want to use the old BuildOS.exe"
- In BuildOS, press the green play button (see attached image) and wait for it to finish.
- Close BuildOS, wait until you see the message "Done!"
- Press space (or any other key) to resume the cooking process.
- After a while the HTC ROM Tool will start.
- Wait for it to finish - it will close automatically.
- After that, XVI32 is started. Don't change anything there, just close it.
- Temporary files will be deleted and you should see the message "Now flash your ROM!"
- Press any key and exit the kitchen.
- You can find your reconstructed ROM in the main kitchen folder. It's "ruu_signed.nbh". Place it in a folder together with "BlackstoneCustomRUU.exe" from subfolder "Tools" and you can flash it anytime you want.
- That's it, you're done!
Hope that helps clarify things.
Regards
K_Hismoom
k_hismoon,thanks for another explanation.i already try to cook a rom in this way several time,but every time when i press the green button,program delete temp file,then he do something with the OEM file,and then he throw me an error: external component has thrown and exception.in bould os it stops and says: error,last satus: creating shadow order file...
i reinstal .net,and problem is still here.any sugestion?
Sorry, haven't come across this problem.
Are you sure you have the right files (ruu_signed same version as your rom dump), enough free space?
Have you used the "old" BuildOS?
Can't think of anything else right now that would cause the error.
not sure about same version as my dump rom,but i am sure i have enough space.hm,i need to check now which version i have in raw files.
K_Hismoom said:
Taken from Raphael ROM thread found here http://forum.xda-developers.com/showthread.php?t=427507
This is based on the assumption that you have a 1.14.x NLD ROM!
- Download official HTC 1.14 NLD ROM for RUU_signed.nbh from http://rapidshare.com/files/182960521/Blackstone_HTC_NLD_1.14.404.3_R.ZIP (link from Blackstone Wiki).
- Extract the zip file and you have the file "RUU_BlackStone_HTC_NLD_1.14.404.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe".
- Use 7-zip or another tool to extract all files from "RUU_BlackStone_HTC_NLD_1.14.404.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe".
- You will have - among other files - the required "RUU_signed.nbh".
- Download the Blackstone kitchen from this thread http://forum.xda-developers.com/showthread.php?t=438456 and extract it.
- Place Part01.raw, Part02.raw from ROM dump and RUU_signed.nbh in the folder BaseROM.
- Start BlackStoneKitchen.cmd
- Select "(e) extract a rom", "(b) if you want to rebuild and cook dumped ROM into flashable ROM" and wait for extraction process to finish (Message "Now start cooking your ROM!"). You should now have additional folders "OEM","ROM" and "SYS".
- Press space (or any other key) to return to the main menu.
- Select "(c) cook a rom", "(a) if you want to use the old BuildOS.exe"
- In BuildOS, press the green play button (see attached image) and wait for it to finish.
- Close BuildOS, wait until you see the message "Done!"
- Press space (or any other key) to resume the cooking process.
- After a while the HTC ROM Tool will start.
- Wait for it to finish - it will close automatically.
- After that, XVI32 is started. Don't change anything there, just close it.
- Temporary files will be deleted and you should see the message "Now flash your ROM!"
- Press any key and exit the kitchen.
- You can find your reconstructed ROM in the main kitchen folder. It's "ruu_signed.nbh". Place it in a folder together with "BlackstoneCustomRUU.exe" from subfolder "Tools" and you can flash it anytime you want.
- That's it, you're done!
Hope that helps clarify things.
Regards
K_Hismoom
Click to expand...
Click to collapse
Hi K_Hismoom,
I will follow your instruction this evening. Later I will inform you, but anyway how the result will be
Thanks a lot for helping me
Hi, K_Hismoom
Sorry that I don´t explode for happiness, because I still have five noob-questions that makes me a little bit nervous.
It seems (so the program was saying it) everything seems to be ok.
For this advice THANK YOU SO MUCH everything was easy to understand.
What I´m still thinking is, that I have actually four raw files. I used now one and two, but the biggest file is raw three. For what is this file? Do I need it? and what of raw 00 the smallest?
If I press the Startbutton for flashing, it tells me my current version 1.14.404.3 and if I press the Update Button it shows me an update to 1.00. Is this correct? Should it not telling me the same Versionnumber (current version)?
I´m afraid to press the button "start"
A quick replay will be nice, because I don´t want that my food will be burned in the kitchen
Regards
Dude10
Hi Dude_10,
sorry for taking so long to answer.
Part00.raw is the area with IPL, SPL and Splashscreen
Part03.raw is content of your local storage
I haven't actually flashed a reconstructed ROM myself, so I cannot tell.
But I suspect that is okay, since the rom upgrade utility also does this with many cooked ROMs that after flashing display the correct version number.
Maybe someone else can answer that question?
K_Hismoom said:
Hi Dude_10,
sorry for taking so long to answer.
Part00.raw is the area with IPL, SPL and Splashscreen
Part03.raw is content of your local storage
I haven't actually flashed a reconstructed ROM myself, so I cannot tell.
But I suspect that is okay, since the rom upgrade utility also does this with many cooked ROMs that after flashing display the correct version number.
Maybe someone else can answer that question?
Click to expand...
Click to collapse
Hi K_Hismoom
I did not try it out yet. But for saving my ROM, Excellent!!
I´m so happy that I could save now my original ROM, but let me tell you something about description. The way how you discribe it and the way how wiki or other peopel discribe it, is different.
For instance: nobody write, that I have to create a folder in the base program.
(- Place Part01.raw, Part02.raw from ROM dump and RUU_signed.nbh in the folder BaseROM.) This Folder doesn´t excist, so I had to create it.
Before I´ve got always "can´t find the directory" but as soon as I create the folder, everthing just goes for it self.
Yeah !!!
As I just talking to you and I hope that I´m not disturbing you with my question. Can you tell me your opinion concerning another ROM.
I want to Flash Dutty 2,1 extrem. Is it a good stabil ROM? or is there a better one available? The best for me will be a german one but it should look also nice with the new manila, if it is possible.
Regards
Dude10
Dude10 said:
Hi K_Hismoom
I did not try it out yet. But for saving my ROM, Excellent!!
I´m so happy that I could save now my original ROM, but let me tell you something about description. The way how you discribe it and the way how wiki or other peopel discribe it, is different.
For instance: nobody write, that I have to create a folder in the base program.
(- Place Part01.raw, Part02.raw from ROM dump and RUU_signed.nbh in the folder BaseROM.) This Folder doesn´t excist, so I had to create it.
Before I´ve got always "can´t find the directory" but as soon as I create the folder, everthing just goes for it self.
Yeah !!!
As I just talking to you and I hope that I´m not disturbing you with my question. Can you tell me your opinion concerning another ROM.
I want to Flash Dutty 2,1 extrem. Is it a good stabil ROM? or is there a better one available? The best for me will be a german one but it should look also nice with the new manila, if it is possible.
Regards
Dude10
Click to expand...
Click to collapse
I have tried out several ROMs from the Blackstone forum, including the German Starbase64 and Davideucks WinMo 6.5 ROM, but Dutty's 2.1 is the ROM that I like best. It is quite fast and stable and I just love the new manila. Also if you set the manila language to German and install the expanded language file from http://forum.xda-developers.com/showthread.php?t=490844, you have at least a German manila.
But I suppose, you should try out some of those ROMs for a few days, before deciding which one you want to have on your phone permanently.
Hope that helps.
Regards
K_Hismoom
K_Hismoom said:
I have tried out several ROMs from the Blackstone forum, including the German Starbase64 and Davideucks WinMo 6.5 ROM, but Dutty's 2.1 is the ROM that I like best. It is quite fast and stable and I just love the new manila. Also if you set the manila language to German and install the expanded language file from http://forum.xda-developers.com/showthread.php?t=490844, you have at least a German manila.
But I suppose, you should try out some of those ROMs for a few days, before deciding which one you want to have on your phone permanently.
Hope that helps.
Regards
K_Hismoom
Click to expand...
Click to collapse
Hi, I will try first the Dutty Rom as you say. Actually I just want a stabil with landscape and new manila Rom and I think thats one of the best.
Do you have any problem with Internetconnection? I had before such a problem, that I can´t enter any Internet or Weather or Email connection. It told me always "can not find the remote server" but I could use the phone. So I hope this Rom doesn´t have such a "bug"
Hello
Sry for using your thread for my question...
I've dumped my Orange UK 1.19.61.1 Rom to save my ROM for warranty issues.
Wich BaseRom should I take? An Orange Baserom or an HTC. 1.14 or 1.19...
I've no Idea
Thanks
Terrorhuhn said:
Hello
Sry for using your thread for my question...
I've dumped my Orange UK 1.19.61.1 Rom to save my ROM for warranty issues.
Wich BaseRom should I take? An Orange Baserom or an HTC. 1.14 or 1.19...
I've no Idea
Thanks
Click to expand...
Click to collapse
You would just need RUU_signed.nbh extracted from an official HTC WWE 1.19 ROM, but can also use it from an Orange UK ROM, which you can find at http://rapidshare.com/files/191585731/ruu_signed.rar.html, I think (link is from the Wiki).
Dude10 said:
Hi, I will try first the Dutty Rom as you say. Actually I just want a stabil with landscape and new manila Rom and I think thats one of the best.
Do you have any problem with Internetconnection? I had before such a problem, that I can´t enter any Internet or Weather or Email connection. It told me always "can not find the remote server" but I could use the phone. So I hope this Rom doesn´t have such a "bug"
Click to expand...
Click to collapse
So far I didn't have any problems with my Internet connection, neither WiFi nor GSM/UMTS/HSDPA, but I always have to select "Best performance" when using WiFi (this is probably a problem with my WiFi router, as I had to do this on every ROM, even the stock ROM).
K_Hismoom said:
You would just need RUU_signed.nbh extracted from an official HTC WWE 1.19 ROM, but can also use it from an Orange UK ROM, which you can find at http://rapidshare.com/files/191585731/ruu_signed.rar.html, I think (link is from the Wiki).
Click to expand...
Click to collapse
Oh, thanks.
What's different if I would choose a Orange UK ROM as BaseROM?
Thanks
Terrorhuhn said:
Oh, thanks.
What's different if I would choose a Orange UK ROM as BaseROM?
Thanks
Click to expand...
Click to collapse
I'm not sure, but I think there wouldn't be any difference.
I'm gonna hijack this thread for a bit
i'm trying to dump the ROM from my Blackstone. I've got the 4 raw files, but i'm kinda confused now, since all the kitchen tutorials only mention the first two files. Seeing the sizes of the files, it makes me think - the first two files are only about 8 megs, and the other two are huge. What is taht about? Why did we make the last two files and when do we get to use them?
Also, another question, the ROM on my Blackstone comes with Sunnysoft Interwrite preinstallled - is it possible to extract it's cab from dumped rom?
Thanx!
EDIT: Whooops, possible problem here:
I was dumping ROM according to this
CMD outputs info that's similar to the one in the guide
Code:
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part00 -t
real nr of sectors: 1598 - 3.12Mbyte, 0x31f000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part01 -t
real nr of sectors: 2176 - 4.25Mbyte, 0x440000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part02 -t
real nr of sectors: 64768 - 126.50Mbyte, 0x7e80000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part03 -t
real nr of sectors: 166016 - 324.25Mbyte, 0x14440000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part01 0 0x440000 Part01.raw
CopyTFFSToFile(0x0, 0x440000, Part01.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x7e80000 Part02.raw
CopyTFFSToFile(0x0, 0x7e80000, Part02.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x1440000 Part03.raw
CopyTFFSToFile(0x0, 0x1440000, Part03.raw)
But the generated files are of different sizes:
Part00.raw 3,12 MB (3.272.704 bytes)
Part01.raw 4,25 MB (4.456.448 bytes)
Part02.raw 126 MB (132.644.864 bytes)
Part03.raw 20,2 MB (21.233.664 bytes)
WTF? Is this ok?
I used RUU_signed.nbh from Duttys HD 2.6 Xtreme rom.
And kitchen gives me a "RecMode.exe has encountered an error and needs to close...." error after this:
Code:
Please wait for this script to finish after you see "Done!".
Don't close it, but press enter to continue!
------------------------------------------------------------
NBSplit 2.1rc2
Using data chunk size = 0x800 and extra chunk size = 0x8
on file OS.NB
Done.
ImgfsFromNb 2.1rc2
Sector size is 0x800 bytes
ImgFs partition starts at 0x00840000 and ends at 0x079a0000
Dumping IMGFS at offset 0x00840000 (size 0x07160000)
Done!
And the same thing happened even in a virtual xp machine - clean machine, .net 3.5, sp3 and all the updates, which leads me to believe that ROM dump wasn't succesful. Any ideas?
Anyone?
WM_Rizzo said:
I'm gonna hijack this thread for a bit
i'm trying to dump the ROM from my Blackstone. I've got the 4 raw files, but i'm kinda confused now, since all the kitchen tutorials only mention the first two files. Seeing the sizes of the files, it makes me think - the first two files are only about 8 megs, and the other two are huge. What is taht about? Why did we make the last two files and when do we get to use them?
Also, another question, the ROM on my Blackstone comes with Sunnysoft Interwrite preinstallled - is it possible to extract it's cab from dumped rom?
Thanx!
EDIT: Whooops, possible problem here:
I was dumping ROM according to this
CMD outputs info that's similar to the one in the guide
Code:
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part00 -t
real nr of sectors: 1598 - 3.12Mbyte, 0x31f000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part01 -t
real nr of sectors: 2176 - 4.25Mbyte, 0x440000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part02 -t
real nr of sectors: 64768 - 126.50Mbyte, 0x7e80000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part03 -t
real nr of sectors: 166016 - 324.25Mbyte, 0x14440000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part01 0 0x440000 Part01.raw
CopyTFFSToFile(0x0, 0x440000, Part01.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x7e80000 Part02.raw
CopyTFFSToFile(0x0, 0x7e80000, Part02.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x1440000 Part03.raw
CopyTFFSToFile(0x0, 0x1440000, Part03.raw)
But the generated files are of different sizes:
Part00.raw 3,12 MB (3.272.704 bytes)
Part01.raw 4,25 MB (4.456.448 bytes)
Part02.raw 126 MB (132.644.864 bytes)
Part03.raw 20,2 MB (21.233.664 bytes)
WTF? Is this ok?
I used RUU_signed.nbh from Duttys HD 2.6 Xtreme rom.
And kitchen gives me a "RecMode.exe has encountered an error and needs to close...." error after this:
Code:
Please wait for this script to finish after you see "Done!".
Don't close it, but press enter to continue!
------------------------------------------------------------
NBSplit 2.1rc2
Using data chunk size = 0x800 and extra chunk size = 0x8
on file OS.NB
Done.
ImgfsFromNb 2.1rc2
Sector size is 0x800 bytes
ImgFs partition starts at 0x00840000 and ends at 0x079a0000
Dumping IMGFS at offset 0x00840000 (size 0x07160000)
Done!
And the same thing happened even in a virtual xp machine - clean machine, .net 3.5, sp3 and all the updates, which leads me to believe that ROM dump wasn't succesful. Any ideas?
Click to expand...
Click to collapse
I have this problem too ;/
If you need to flash ROM even using fastboot for Smartphone or Tablet in which they use Android OS! Then Ubuntu OS is needed!
This is a guide I made for ubuntu users and included a guide for windows users to setup Android SDK which contains ADB.
Android Debug Bridge (ADB) provides a terminal interface on your PC to interact with your device's file system. This can be useful for many things like installing & uninstalling apps, logcat, backup & restore, and hacking your device just to name a few.
ubuntu 12.04 & 12.10 Guide
1. Go here and download android-sdk (not the adt-bundle)....
https://hotfile.com/dl/241406263/5e6a306/android-sdk_r22.0.5-linux.tgz.html
2. Place the downloaded file in your home folder and then extract it and you should get a folder named android-sdk-linux (do not rename it).
3. If you’re on a 64bit machine run these commands in terminal to make sdk compatible with 64bit (if you’re on 32bit machine then skip this step)....
sudo apt-get update
sudo apt-get install ia32-libs-multiarch
4. Run this command in terminal to install jdk if you don’t have it already....
sudo apt-get install openjdk-6-jdk
5. Navigate to the home folder where you extracted android-sdk-linux and open the folder then open the folder named tools
6. Inside the tools folder there will be a file named android... double click it and select run then android sdk manager will open.
7. In the center pane deselect everything... Now only select the following....
Android SDK Tools
Android SDK Platform-tools
Android Support Library
8. Once selections have been made click on install packages and wait till finished.
9. Upon completion of step 8 in terminal run this command....
sudo gedit ~/.bashrc
When the file opens, go to the very bottom and copy/paste the following 3 lines (make sure they’re each on separate lines)....
# Android tools
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
10. Now reboot your computer.
11. Set your phone to usb debugging then plug it to your pc after pc is done booting
12. Open a terminal on your pc and enter....
adb devices
If all went well, you should see your phone’s serial number and you’ll be ready to go.
~~~~~Important~~~~~
You can use steps 5 & 6 to open Android SDK Manager & update your ADB/SDK installation. Only select your installed packages then update.
Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app
Thank...
gazhead said:
Also if you only need the fastboot/adbtools:
sudo add-apt-repository -y ppa: phablet-team/tools
Note: delete the space after"-y ppa:" -xda creates smileys like ppa
sudo apt-get update
sudo apt-get install -y phablet-tools
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks man! It's also good way!
Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!
qtoon said:
Followed this guide (thank you for posting) but couldn't connect. Scratched around and found I needed to create a new file in /etc/udev/rules.d with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="<4-char_verndorID>", ATTR{idProduct}=="4-char_productID", MODE="0666", OWNER="username"
Followed by:
Code:
sudo restart udev
Then plugged device in and it worked!
Click to expand...
Click to collapse
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.
atmu5fear said:
What did you name the new file you created? Or did you add this string to another existing file from the rules.d directory? I'm not sure what I've done wrong, but I get
Code:
[email protected]:~$ adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'kdb' from package 'elektra-bin' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'openjdk-7-jdk' (universe)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~$
This is after following each step, adding the three lines to the end of .bashrc and rebooting.
Click to expand...
Click to collapse
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.
qtoon said:
@atmu5fear, inferring that you're new to Linux (a common background for all), some notes:
Unlike wlth Win-d'oh-s, there is a worldwide development community that's always working toward improvement of every aspect of the system, including echoed messages and documentation. You may have to shake off the tendency to ignore Windudz messages, which are frequently unhelpful. Linux command echoes are much more on-target. Also, look for files such as README in rules.d and read it!
Now before creating a new config file (which may not be necessary on your system), see the top feedback line: "No command 'adb' found." First, see that the adb binary is present and that it has exec permission. (Since it's a small file and functions alone, I prefer to copy it to the folder I'm working from.)
If it then runs but won't connect, read on...
Directory (or "folder") names with a trailing '.d' are special: They configure, control, or provide executables for daemons (programs which run continuously, providing a service).
Within service-config.d folders, if the service steps through the files sequentially (as in this case), then it does so based on each filename. (True except for the special case of rc.d, iIRC, in which order is set by the special program rcorder).
So in this case, for example, since the existing files are named 70-whatever, your newly-created file could be 80-atmu5fears-phone to load after the others.
Should connect.
Click to expand...
Click to collapse
Thanks @qtoon for the reply. I'm not really new to Ubuntu, albeit, it's been a while. First started using it just prior to the realease of Hardy Heron 8.04 LTS. That being said I am certainly no expert, but am somewhat familiar and comfortable with the command line. I did read the README file before posting, but since I'm not all that familiar with configuration files and the like, I figured maybe I should ask.
As per your suggestion i moved the ADB binary to my home folder, not necessarily my working folder, but to test to see if the adb command would be recognized in terminal.
Code:
mv ~/ADB/android-sdk-linux/platform-tools/adb ~/
Still got same result so I moved it back, then went on to make a new file and add the suggested string
Code:
sudo > /etc/udev/rules.d/80-atmu5fear-adb
sudo gedit /etc/udev/rules.d/80-atmu5fear-adb
After saving and restarting udev I still get the same "adb command not found" error.
I then changed the string to read OWNER"atmu5fear" instead of "username", still nothing
Any more suggestions?
Thanks
atmu5fear
Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work
I get this error...
[email protected]:~$ sudo > /etc/udev/rules.d/80-sjy-phone
bash: /etc/udev/rules.d/80-sjy-phone: Permission denied
ok....... didn't need to add a file, changed phone usb mode to media device and all is ok.
thanks
atmu5fear said:
Sorted it out
instead of:
adb devices
i needed to input:
./adb devices
It's listed, and in order to use the adb shell:
./adb shell
once in the shell all adb commands work
Click to expand...
Click to collapse
Didn't think to mention that, apologies.
Quick 'why' on the ./ here.
Glad you got it running.
Just tried on 14.4 and worked like a charm.
Note: No need to reboot the computer, just reload the bash config with
Code:
source ~/.bashrc
Thanks
A good step by step guide
i will try it and see if it works
Thanks again
Hello, can someone help me ? - I m having problems connecting my device with adb (I ve connected several other devices before with no problems).
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
Using this guide:
http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks
*If you find this Guide Thread helpful, feel free to hit the "thanks" button below!
I'm doing this guide because when I switched to arch linux ,I found no guides to setup sdk in it.Arch is a beautiful OS, but for newcomers like me ,I took some time to get used to it.So,In this guide, we’ll take a look at how to set up a development environment for Android in Arch linux(or Arch based Linux Distros) so you can start working on your Projects.Most of the Arch Linux are pro linux users so there is really no need of this guide, but this guide is meant for those who are switching from ubuntu/mint/fedora/any other disto which are not based on Arch, to say it in short its meant for new users of Arch Linux. Anyway Let's set up.
First let's set see how to install Platform tools.
Setting up platform-tools in UBUNTU(or Ubuntu based distros/Linux Mint)
In ubuntu platform tools can be setup very easily.
1.Open terminal(Default shortcut is ctrl+alt+T)
2. Type "sudo apt-get install android-tools-adb" (this will install the adb)
3. Type "sudo apt-get install android-tools-fastboot"(this will install the fastboot)
Step 4: Check whether the above tools are working by typing an adb command. For e.g. "adb devices"
Now its time to install SDK in Ubuntu and set it up but before that let me tell you there is already a great thread by matt95.You can see the guide and thank him herehttp://forum.xda-developers.com/showthread.php?t=2302780
Fedora/CentOS/RedHat
First lets install Eclipse[You can also use Android Studio if you want]
Code:
sudo yum install eclipse-jdt
Now lets download the sdk from here. http://developer.android.com/sdk/index.html. Its about 500mb , Just wait and let it downlaod. Once the download is done extract it wherever you want.
For newcomers I recommend to extract it to 'home'.So the file is now extracted inside /home/user/AndroidSDK .
Now lets setup .bash_profile file so that we can access adb anywhere or else you have to type the whole location again use the adb command which is lot of work . So let's shorten it up.
Type "sudo vim .bash_profile"in terminal.
Code:
PATH=$PATH:$HOME/AndroidSDK:$HOME/AndroidSDK/tools
export PATH
# For SDK version r_08 and higher, also add this for adb:
PATH=$PATH:$HOME/AndroidSDK/platform-tools
export PATH
Now lets install android plugin for eclipse.
Open Eclipse and click on Help.Select Install New Software. Then click Add, at the top right of that window. Type in Android Plugin for the name and https://dl-ssl.google.com/android/eclipse/ for the address.
Once this is done, click on the Available Software Sites hyperlink below the Add button, then highlight the Android Plugin source and click on Reload. Now exit this window, and choose Android Plugin from the “Work with” dropdown menu. Choose the developer tools option that you see here and Proceed with the installation.
After the installation configure your Android virtual devices.
ARCH LINUX(or Arch based Distros)
Lets install android sdk
Open terminal and type
Code:
wget https://aur.archlinux.org/packages/an/android-sdk/android-sdk.tar.gz
Note:- If terminal shows wget is not found. Type this in the terminal
Code:
pacman -Suy && pacman -S wget
Once it fetches the tarball, lets extract it by typing
Code:
tar -xvzf android-sdk.tar.gz
wait for it to finish. Change the directory to android-sdk by using the command
Code:
cd android-sdk
.
Now lets make the package by using the command
Code:
makepkg -s
now lets install it by typing
Code:
sudo pacman -U *.pkg.tar.xz
Platform tools for Arch
Let's install platform-tools now.Just like above steps ,well get a package and install it.
1. Type
Code:
wget https://aur.archlinux.org/packages/an/android-sdk-platform-tools/android-sdk-platform-tools.tar.gz
2.Type
Code:
tar -xvzf android-sdk-platform-tools.tar.gz
3.Change directory.
Code:
cd android-sdk-platform-tools
4.
Code:
makepkg -s
5.Install it
Code:
sudo pacman -U *.pkg.tar.xz
All the files are installed in /opt/android-sdk/ . Just like we had .bash_profile in FEDORA, we use symbolic links in Arch linux to use commands from anywhere .
Code:
sudo ln -s /opt/android-sdk/platform-tools/adb /usr/bin/adb //this one's for adb
sudo ln -s /opt/android-sdk/platform-tools/fastboot /usr/bin/fastboot //This one's for Fastboot
sudo ln -s /opt/android-sdk/tools/ddms /usr/bin/ddms //This is for DDMS
sudo ln -s /opt/android-sdk/tools/android /usr/bin/android //This is for Android
Now run android by typing "android" in terminal. :good:
Simple as that. If you are yet to switch to Arch linux then I recommened you to use "BBQLinux " its an Arch linux for Android developers. It comes with most of the things needed for android development. You can download it from Here.
Thanks for reading this. Help me by giving me e-books.:angel:
PM me or post here if you have any doubts. :victory:
Install an aur wrapper like pacaur .
pacaur -S android-sdk android-studio android-udev android-platform-tools
Done
Sent from my Nexus 5
Pirateghost said:
Install an aur wrapper like pacaur .
pacaur -S android-sdk android-studio android-udev android-platform-tools
Done
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for the reply, I havent tried pacaur repository though. Will give it a try soon.:good:
sorry, I made an error:
Code:
pacaur -S android-sdk android-sdk-platform-tools android-udev android-studio android-sdk-build-tools
you dont need both platform and build tools, it looks like build-tools is more recent. if you want eclipse instead of android studio, just use 'eclipse-android' instead of android-studio