[Guide] How to get partition table out of any phone using command prompt in windows

[Guide] How to get partition table out of any phone using command prompt in windows - Xiaomi Redmi 1S

Here i can guide you to get the partition table details out of your phone.
Follow my steps seriously (don't ever miss or mess with any step. Just follow blindly. As I've faced same issue.
First of all take a Nandroid backup of your phone for safety.
Before going through any of these steps you need to install latest mi PC suite and MiFlash on your windows PC. As i am a mi [redmi 1s] phone user,i use pc suite and flash tool to install adb and fastboot drivers.
(If you are any other phone user, then you can get your phone compatible adb and fastboot drivers from google or you can use the universal fastboot and adb drivers).
here is the link to get universal adb and fastboot drivers for windows: http://forum.xda-developers.com/showthread.php?t=2588979
1) Connect your phone to your pc by using a compatible USB cable.
2) Now install Minimal adb and fastboot from here: (note the installation directory here)
http://forum.xda-developers.com/showthread.php?t=2317790
3) Next navigate to inside of installation directory (minimal adb and fastboot folder in my computer).
4) if you see adb and fastboot applications inside the folder then you are in the right directory.
Now by press and holding shift button make a right click inside the folder. Here you see open command window here, click on it. Or you can navigate to this folder through command prompt.
5) Now reboot your phone into fastboot by pressing volume button (in general down) and power button. if that doesn't work try by googling it.
6) Now in command prompt enter command
Code:
fastboot devices
.
If you see any device serial number <space> fastboot. if not wait a minute or two. for ex:
abbf287 fastboot
then your device is successfully connected in fastboot mode.
7) Now download the twrp recovery image file from twrp website. and select your device from devices and download the file by clicking the link with Recommended.
link: https://twrp.me/
8) And copy this file into the same folder as your adb and fastboot binaries (minimal adb and fastboot folder). Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
press enter
Code:
fastboot reboot
press enter
9) Now to boot into your latest (twrp) recovery by pressing volume button (in general up) and power button.
10) Now in the same command prompt enter command
Code:
adb devices
.
If you see any device serial number <space> recovery. if not wait a minute or two. for ex:
abbf287 recovery
Then your device is successfullu connected in adb (recovery mode).
11) Now download the parted file from the link below and copy the file to the same directory where twrp.zip was copied.
link: https://drive.google.com/file/d/0B_IeQxB3hZfgbU93NzVOcWd6TjA/view?usp=sharing
12) Now in command prompt enter command:
Code:
adb shell mount -o remount,rw /system
13) Then enter next command
Code:
adb push parted /system/bin/parted
14) You should see some kind of push successful message. Then enter command:
Code:
adb shell
.
15) You should see a new command line host-name with a â€œ#â€ sign next to it which indicates youâ€™re connected as root user.
16)Now Enter the following command one after the other followed by enter.
Code:
chmod 0755 /system/bin/parted
Code:
parted /dev/block/mmcblk0
Code:
print
17) Now you have got a table. Which is the current partition table on your phone. Take screenshot of this details in maximized mode for future requirements.
Happy coding. And don't forget take Nandroid backup before messing anything.

Related

[GUIDE][MAC] How to Unlock and Root the Xoom with a Mac

This is a super simple method taken from Arcadia 310 on another thread.
This is assuming you have The Android SDK already installed and updated.
Download these files XoomRoot.zip HERE
and FASTBOOT for MAC - HERE
Unzip both archives into your ~/sdk/platform-tools folder.
I AM NOT RESPONSIBLE FOR YOU SCREWING UP YOUR DEVICE, THIS IS VOIDING YOUR WARRANTY ANYWAYS. HIT ME UP ON TWITTER OR HERE IF YOU NEED HELP OR HAVE QUESTION. ON TO DIRECTIONS.
Follow these steps: (After you have unzipped into your folder)
1. Follow the pre requisites above.
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
You should now have root acces! Enjoy!

Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.

First off thanks for doing this... I figured out my n1 and I can do this too... I'm stuck at the chmod 775 line... I enter that command and its like I didn't enter it... after I proceed to fast boot OEM unlock it tells me that it can't be executed .. what am I doing wrong... God I hate being noobed out... I'm so close!!!
Sent from my Nexus One using XDA App
EDIT: got past that with the help of using fastboot-mac from htc's website... but now I'm stuck on getting the rootboot.img over
Morgan-Brants-Mac-minilatform-tools Chongo$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... FAILED (remote: (0000000f))
Morgan-Brants-Mac-minilatform-tools Chongo$
EDIT2: Well it was due to my xoom being almost dead (not enough juice to flash)
on the other hand this was a refresher course and I now understand ADB a whole lot more... thank you for this educational piece I am now a tiger blood enfused SUPER USER

I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see

b16a2smith said:
I am glad I could help, I have this tutorial on my website along with many other devices, http://rootzwiki.com if there is any other devices you would like to see
Click to expand...
Click to collapse
Thanks.. ill let you know when I get a new phone.. should be soon
Sent from my Nexus One using XDA App

thanks for this. Cant wait to get mine on the 27th

wheeeler said:
Thanks for posting this. Another thing I did, because I use ADB quite frequently, was add the SDK tools to my path. For those that need help, it looks something like this:
Open Terminal and type echo 'export PATH=~/Downloads/android-sdk-mac_x86/tools:$PATH' >> ~/.profile
This only works if your SDK folder is in your Downloads folder inside your Home folder.
The next time you open a Terminal window, you can simply type adb remount or whatever you need without having to add the ./
Another bonus is this makes it much easier to keep kernels, ROMs, and modules out of your SDK tools folder, where they do not belong.
Click to expand...
Click to collapse
Well the default shell in a mac is bash so wouldn't be:
Code:
echo "export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH" > .bash_profile
This is a video walkthru of rooting that happens to be on a Mac but the process is the same for Windows:
http://www.youtube.com/watch?v=4YkIw0y_Os4

im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either

Magenta you say.

chevyman46933 said:
im not sure if it is just me or not, but i get stuck at step 5 for some reason?
i type ./adb reboot bootloader it shuts down then turns on and i get stuck at "starting fastboot protocal support" it sits forever then i have to hold volume up and power to reboot and its fine, but cant ever get past that.
it no longer shows as attached device at that point either
Click to expand...
Click to collapse
can anyone help me?

OK, thanks for the initial post and outstanding directions. I've updated what you listed based on what I have seen on my mac. I've just been through this process now and everything is working great. I hope this helps.
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
2. Open a terminal (located in the utilities folder)
3. Navigate to your sdk/platform-tools folder
Example: "cd /home/b16/Desktop/sdk/platform-tools" (no quotes)
4. Type "./adb devices" and make sure your Xoom shows up on the list.
This command will show you if your device is connected to the Android Debug Bridge.
goonmac-2: platform-tools goon$ ./adb devices
List of devices attached
028040c743e111d7 device
5. Now type in "./adb reboot bootloader" (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
This will reboot your device into bootloader mode accepting fastboot commands.
FYI - your xoom will just say "Starting..." but it is ready to accept the next step.
6. I had to type "chmod 755 fastboot" first to get it to execute.
This will change the permissions of the FASTBOOT BINARY so it can execute.
7. Now type in "./fastboot oem unlock" and choose to unlock it. (wait for reboot)
This will make your device "Hackable" and will VOID your warranty, you can re-lock it later if you like using another guide on this forum. Located HERE.
goonmac-2: platform-tools goon$ ./fastboot-mac oem unlock
... INFO To continue, follow instructions on the device's display...
OKAY
8. Once it has rebooted type "adb reboot bootloader" and hit enter.
Now you are going back into bootloader mode to finish the job.
*after the reboot, initially, I got this error:
goonmac-2: platform-tools goon$ ./adb reboot bootloader
error: device not found
when the reboot completes, you will come to the original setup screen. it is worth noting that you need to select the language and follow the on screen directions. Re-enter your account information etc. When you get to the desktop, your device will then be re-seen by your mac.
9. Once in bootloader mode type "./fastboot flash boot rootboot.img"
This is going to flash the boot image needed to have root working properly within the system.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... OKAY
writing 'boot'... OKAY
10. Type "./fastboot reboot" (wait for reboot)
command wil now boot you back into Android.
* Again, need to use the fastboot-mac:
goonmac-2: platform-tools goon$ ./fastboot-mac reboot
rebooting...
11. Type "./adb remount"
We are now mounting the system partition in order to push the Super User binary.
no issues
goonmac-2: platform-tools goon$ ./adb remount
remount succeeded
12. Type "./adb push su /system/bin"
Does what it says. Pushes binary to system folder.
no issue
goonmac-2: platform-tools goon$ ./adb push su /system/bin
701 KB/s (26336 bytes in 0.036s)
13. Type "./adb shell" You should now see a "#" sign.
This will put you into a root shell to change the permissions of files in the next step.
no issue
goonmac-2: platform-tools goon$ ./adb shell
14. Type "chmod 4755 /system/bin/su"
You just changed the permissions of the super user binary to run properly.
no issue
# chmod 4755 /system/bin/su
15. Type "exit".
You will now be back in your home terminal ready to push the Super User Apk.
16. Type "./adb push Superuser.apk /system/app"
no issue
goonmac-2: platform-tools goon$ ./adb push Superuser.apk /system/app
1137 KB/s (196521 bytes in 0.168s)

still stuck at same step, after ./adb reboot fastboot i cant go any farther, the xoom just isnt connected to recieve and additional commands, heres a copy n paste from my terminal...
Mac-Users-Mac-mini:tools Home$ pwd
/Users/Home/desktop/sdk/platform-tools
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
161c10c94180d557 device
Mac-Users-Mac-minilatform-tools Home$ ./adb reboot bootloader
Mac-Users-Mac-minilatform-tools Home$ chmod 755 fastboot
Mac-Users-Mac-minilatform-tools Home$ ./fastboot oem unlock
-bash: ./fastboot: cannot execute binary file
Mac-Users-Mac-minilatform-tools Home$ ./adb devices
List of devices attached
Mac-Users-Mac-minilatform-tools Home$
any help/suggestions?

Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App

wheeeler said:
Are you using the Mac fastboot binary? I'm not by my computer right now, but I believe the Mac version is called fastboot-mac by default. Download it, make sure it's executable (chmod 755 fastboot-mac), then try fastboot-mac oem unlock. After you run adb reboot bootloader, you will lose your ADB connection, and your Xoom won't display anything but the boot logo and something about starting fastboot. This is your cue to unlock. Hope this helps.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
that was exactly it, i was using the fastboot from another post, got the fastboot-mac from the website adn it works perfect!! thanks!!!
xoom unlocked, finally

thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html

goon55 said:
thats why I amended the steps
1. Follow the pre requisites above.
* I also had to download the fastboot-mac file from the HTC site- http://developer.htc.com/adp.html
Click to expand...
Click to collapse
For some respason I didnt realize the difference between the two fastboots until he mentioned that and thankfully your ad was right above with the link to htc thanks to you guys im now have rooted and unlocked and overclocked my xoom and its incredible now! Thanks for the patience with me

I did a video that was done on my MAC in the MAC OS. If anyone wants a more visual way to see how this is performed. I follow all these steps exactly. I show how I set my environment PATH, and this actually is what tripped me up, because my user profile wasn't looking at the PATHs I originally setup, but all that is required is entering
echo 'export PATH=xyz:$PATH' >> ~/.bash_profile (this whole line )
Where 'xyz' is your path to the android-sdk/platform-tools/ from the root of your Hard Drive, for most Macs it should be ' /Users/[Ur User Name]/android-sdk/platform-tools '
http://www.youtube.com/watch?v=26EhGGOGUus
Hope this helps

I also have a WiFi Xoom Video Tutorial available available as well. Check it out.
http://www.youtube.com/watch?v=zC6J-hV6SM4
I try to go over common hiccups that I have seen some users have come across as well in the video.

I'm getting the following error:
./fastboot-mac flash boot rootboot.img
sending 'boot' (2902 KB)... ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
fastboot-mac is chmod 755, rootboot.img is there, alongside it, I'm in as root and it's still failing for me.
Edit: Nevermind. Right after pulling the reboot before the rootboot.img - or boot.img for wifi users - immediately go into the aforesaid command and it should work just fine.
Took me a couple of times.

Can you unroot on mac?

[Q] Stuck at < waiting for device>

http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
I'm having a rooted 8.3.1 KF
Please help

tkien212 said:
http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
Please help
Click to expand...
Click to collapse
With the Kindle powered down, type the following command into a cmd/terminal window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and it will boot. It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04 this has to be done in a command window opened where fastboot is located. Shift + right click in the folder where fastboot is located select open command window here, then run the command and follow above instructions to get it into fastboot.
Edit also to let you know if you are running system version 8.4.1 other thing will need to be done to install freedom boot and recovery just to send an air of caution if you use the present instructions for this you will become stuck at the blue kindle fire logo so I would wait till methods have been updated.

yes I did that, unplugged my kindle and powered down -> type the command in cmd < waiting for device> -> Plug my kindle in and automatically turn on
The cmd still show < waiting for device> even after it's fully boot, it doesn't show fastboot screen
I managed to go to Fastboot mode by using KF First Aide, but my computer couldn't recognize kindle while it's in fastboot mode. So I couldn't do anything
Edit 1st post: I'm using 8.3.1 rooted

Thepooch helped me through teamviewer on how to install Android and here I share my experience on how to do it.
Your kindle need to be rooted. I suggest to use KF First Aide and root. It's easier
You will need ADB enable by go to settings in Kindle.
Download this file (Amazon 8.4.1 OS): http://d-h.st/VnR and put it in sdcard for backup purpose.
You don't extract ZIP files.
1. Download and extract #1 on below link
http://forum.xda-developers.com/showthread.php?t=2191010
2. Go to Root_with_Restore_by_Bin4ry_v21\stuff -> Shift + Right Click on folder -> Open command window here
*Steps 3,4,5,6,7 are from http://forum.xda-developers.com/showthread.php?t=2128201
3. Use these command to backup your stock partitions, these *.img will be in the Root_with_Restore_by_Bin4ry_v21\stuff folder.
Take 4 of those *.img to somewhere else safe
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img
4. Download these files (go to different topic above for latest version)
http://goo.im/devs/Hashcode/jem/stack
http://goo.im/devs/Hashcode/jem/kfhd8-freedom-boot-8.3.0.img
http://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.4.4.0-recovery.img
5. Install stack:
Code:
adb push stack* /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
*Replace stack with location to your stack file
Example: adb push C:\Users\Admin\Desktop\stack /data/local/tmp/
6. Stop the auto recovery update script (this file may or may not be present): Mine was not present, it will show file not sound after enter 2nd command
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
6.5: APPLIES IF YOU ARE ON SOFTWARE VERSION 8.3.0 OR GREATER
Download this: http://goo.im/devs/Hashcode/jem/kfhd8-u-boot-prod-8.1.4.bin
Enter fastboot mode and flash:
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
*You will need a file called fastboot.exe, open command from there, KF First Aide have it
or you can download from here: http://d-h.st/ttL <- Do not use anything from this, just go to tools and open command from there
7. Continue with these command in fastboot mode:
Code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-recovery.img
fastboot -i 0x1949 reboot
***If everything is done correctly, when you booting up, the word Kindle Fire should switch from orange -> blue -> orange, then fully boot
***If you get orange screen, then you didn't do step 6.5
8. Download these and put them in sdcard:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130604-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130301-signed.zip
To enter recovery mode, unplug, shut the kindle down. Plug in (it should power on), when the word Kindle Fire is orange, hold the volume up button, it should switch to blue and then twrp recovery mode. If you failed, hold the power button until it shut down and try again.
8.5. Drivers problem: Kindle not recognized
When I get into recovery mode, my computer couldn't recognize Kindle. So this is what you have to do.
Download this and extract: http://d-h.st/9We
Open android_winusb.inf
Go to/Search for
Code:
;Kindle Fire HD
Now go to Device Manager -> Right Click on "couldn't recognize driver kindle" -> Details -> you will see there are two codes.
Edit android_winusb.inf (below your device, mine is Kindle Fire HD) to match with the two codes.
Then just right click, update driver
9. Now back to Kindle, you should be in TWRP Recovery Mode.
You should backup first: Go to backup -> backup everything and check compression
Next go to Wipe -> Wipe 4 of the thing on the first line (Caches, Dalvik Caches, Factory Reset, System)
Next go to Install, choose 2 of the files at step 8.
Code:
cm-10.1-20130604-UNOFFICIAL-jem.zip
gapps-jb-20130301-signed.zip
Then reboot system
10. Now you should see CyanogenMod (Android) loading
After you are in, don't let Google backup your things. It will somehow messed up your system and will crash when you try to run apps.
Next, go to settings, go to about, and tap the last line 8 times to enable developer mode
Next, check advanced boot and ADB
After that, when hold your power button for a little bit, you will see a boot button, tap it and there should be 3 options to boot in case something happens.

Nice job you make a helper proud.

[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]

[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download

[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]

Need a little help flashing radio.img

Ok it's hopefully just something I'm overlooking but haven't gotten it to work so far. I have ADB and Fastboot set up on computer and the phone is T-Mob m8, unlocked, rooted, TWRP, Custom ROM, S-Off, Super CID. I have downloaded the radio zip, extracted the radio.img and put it in the adb folder in my c drive. Now I followed a couple of steps posted:
Fiash via adb:
1. Download the radio.img above
2. Put the radio.img file into your ADB folder
3. Open up command prompt and copy and paste the EXACT lines
4. adb push radio.img /storage/sdcard0/radio.img
5. adb shell
5. su
6. dd if=/storage/sdcard0/radio.img of=/dev/block/mmcblk0p20
7. adb reboot
I get cannot stat "radio.img" no such file or directory any suggestions? thanks
but each time i get a file not found so what is

http://www.androidfilehost.com/?w=f...ce08cd20294c7e0997d32ce5203bee4a606a03d8be1b9
i used this to fix my radio problems. flashable in twrp

Okay, make sure the radio.img is in the folder you have adb and fastboot setup, then do the following once your phone is connected to your computer:
Open command and type the following:
Code:
adb reboot bootloader
fastboot flash radio NAME_OF_FILE_.img
Then reboot your phone afterwards.

Da Kine said:
Okay, make sure the radio.img is in the folder you have adb and fastboot setup, then do the following once your phone is connected to your computer:
Open command and type the following:
Code:
adb reboot bootloader
fastboot flash radio NAME_OF_FILE_.img
Then reboot your phone afterwards.
Click to expand...
Click to collapse
Thanks! got it working, I knew I was having a vegetable moment, I was putting the radio.img in the actual adb folder. Once I removed it from there and put it in the c: drive folder it worked like a charm :good:

Develop Bugs

welcome