New SDK - Flashing through Fastboot - Desire General

The new version of SDK has changed a few things within the file system, so I'm just writing something here to show how it will work fast for everyone.
1. Install Android SDK
2. Update Android SDK through the program first.
3. Go to "Android\android-sdk\tools" (or wherever you've installed the sdk-tools) and copy "fastboot".
4. Paste "fastboot" in to "platform-tools"
5. Once that's done, to get directly to "Android\android-sdk\" to run ADB and fastboot without having any errors (or command prompt irritations) press SHIFT then right click "Android\android-sdk\platform-tools" and select "Open command window here".
6. Then it's just the case of pasting your .img file in to the "Android\android-sdk\platform-tools" folder, and you're good to go! (for example, in command prompt type: fastboot flash hboot bravo_alphaspl.img)
Dan.

The reason why I have put this here is because I have had trouble trying to sort out the new SDK and I in fact had trouble with "missing files" within the folders. They weren't missing, it's just that the SDK folders have been cleaned up.
Follow this and you won't go wrong to flash anything through fastboot .
Dan

Please format your first post correctly (like second post), otherwise it's horrible to read.
I guess "old" sdk will still work properly?

Related

[Q] ADB not working

Hello everyone i am having troubles installing adb on my laptop and i need it to flash a splash screen on my mytouch slide so it can match the rom i have made for it. I installed the adnroid sdk to where it needs to be by downloading adb for dummies lol. Except when i open cmd and run adb it says its not an internal batch orrecognized file or whatever but when i type adb.exe on command prompt it shows everything about adb. So can anyone please help me thanks.
Nerd019 said:
Hello everyone i am having troubles installing adb on my laptop and i need it to flash a splash screen on my mytouch slide so it can match the rom i have made for it. I installed the adnroid sdk to where it needs to be by downloading adb for dummies lol. Except when i open cmd and run adb it says its not an internal batch orrecognized file or whatever but when i type adb.exe on command prompt it shows everything about adb. So can anyone please help me thanks.
Click to expand...
Click to collapse
I'm trying to piece together information here. ADB for me is in my C:\, so when opening CMD prompt, I first type "cd/" (without quotes) then "cd AndroidSDK/tools". To get a list of ADB's commands, type "adb help". Maybe you're not using the proper syntax. I base this off the statement you made that when you type adb.exe it shows the adb commands, and command syntax usage.
Also note that changing your splash screen you must first S-OFF your phone. Here's a guide on how to do so
http://forum.xda-developers.com/showthread.php?t=798168
That's the tricky part though, easy part is flashing your custom boot image.
File you will need: View attachment Boot_images.zip
Once you have the 320x480 boot image you want, open "CreateG1Splash", select your boot image, and convert it with this program. Once converted the new file will show in the same folder as CreateG1Splash, named mysplash.rgb565. Move this file to your ADB tools folder. Open CMD prompt and point CMD prompt to your AndroidSDK\tools folder.
Then boot phone into bootloader, then select fastboot. Plug the phone to CPU via USB, and type, "fastboot flash splash1 mysplash.rgb565". Reboot phone to see change.
Hope this helps!

help with unlocking bootloader...

I have a LTE gnex. I am having problems getting my bootloader unlocked.
If I attempt to use fastboot commands at all I get the error 'fastboot is not recognized as an internal or external command, operable program or batch file.'
If I attempt to use adb devices while I am in fastboot it says "List of devices attached." If I use the adb devices command when my phone is turned on it lists my device like normal.
I feel like I am so close, but yet so far. Any ideas?
EDIT: I'm attempting this on XP, and I am on 4.0.2
I am no expert in these matters, but a few things come to mind:
1) have you got all the proper drivers installed?
2) in the cmd prompt, are you in the directory where fastboot.exe is located?
Have you followed this thread? I'd recommend downloading superboot, extract the contents, go into that folder, and then use: 'fastboot-windows oem unlock'. That should definitely do the trick. Good luck.
EDIT: I don't specifically know all the differences for the GSM/LTE/CDMA versions, but the above should be okay for all versions. To root, and install recovery, on CDMA versions, check out this google+ post.
EDIT2: Also, this thread may be worth looking into.
Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.
aldouse said:
Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.
Click to expand...
Click to collapse
^^^^^^This.....beat me to it LOL. This should work for ya just fine. Just make sure tour fast boot file is in the same as tour adb file. Hope ya her it man. It can def get frustrating
Sent from my Galaxy Nexus using Tapatalk
When I shift + right click I don't have any option to open a command window...well this is frustrating.
twiz0r said:
When I shift + right click I don't have any option to open a command window...well this is frustrating.
Click to expand...
Click to collapse
just open command prompt manually and then go to folder. Eg 'start' -> 'run' -> type 'cmd' and hit enter. Then cd c:\path to folder\ etc.
edit: plus, i gave you a few links to other threads. I really recommend to follow the steps described there if you haven't so far...

Wiped Phone Now Can't See SD Card On Lappy, PLEASE HELP

I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...
The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.
gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped

help me here thanks guys

im trying to unlock my gsm nexus bootloader in command run it says 'adb' is not recognized as an internal or external command,operable program or batch file. what do i do?
I'm assuming you have Android SDK downloaded to your C:\ drive or or some place like that. if so then navigate to SDK folder and hold shift then right click platform-tools folder and then click open command window here. .
PhazeDelta1 said:
I'm assuming you have Android SDK downloaded to your C:\ drive or or some place like that. if so then navigate to SDK folder and hold shift then right click platform-tools folder and then click open command window here. .
Click to expand...
Click to collapse
yeap i did that already i open command window and type adb reboot bootloader it gives me that msg
galaxy16 said:
im trying to unlock my gsm nexus bootloader in command run it says 'adb' is not recognized as an internal or external command,operable program or batch file. what do i do?
Click to expand...
Click to collapse
You need to get adb working on your PC. You don't have it installed or you are using it wrong (not in the directory it is in, or it isn't set to PATH as examples).
Side note adb doesn't work in the bootloader.
use gnex toolkit in galaxy nexus android development
Open the CMD and navigate to the folder where ADB.EXE is located and like someone mentioned about adb wont work in bootloader, so instead you'll have to use "fastboot", type "fastboot /?" for help and commands.
also make sure you execute CMD as Administrator.
on the toolkit, adb file's name is different. try "adb-toolkit" instead of "adb"
so: "adb-toolkit reboot bootloader"

Bootloader unlocking problem

Morning.
No doubt I am missing something dumb out here but I'm having problems here. Following HTC Dev instructions to the letter but when I open CMD it says C:\Windows\system32 NOT C:\Users\Admin\cd \Android
Tried typing in fastboot devices and just get not recognized. I've installed SDK, HTC Sync, JAVA etc.
Any help would be gratefully received
Navigate to the folder where also the fastboot exe file is located, open the command prompt directly in there and type the command again.
Mr Hofs said:
Navigate to the folder where also the fastboot exe file is located, open the command prompt directly in there and type the command again.
Click to expand...
Click to collapse
Thanks. Resolved.

Categories

Resources