Develop Bugs

[Guide]Running BackTrack5(Ubuntu Lucid v10.04) On Your ET4G!!!

-Found this little gem posted in this thread, located under the AT&T Samsung Galaxy S II Android Development Forum. So I decided to installed it on my phone and SURPRISE SURPRISE, turns out it works great on our Epic Touch 4G too !
-Anyways, you can follow the instructions which I've quoted right below, and they are also found in the link above. This installation/setup takes all but 5-10minutes if not less!!! Hardest part, if you wanna call it that(its really just the longest part), is downloading the required files. Once you've downloaded all 10 7zip files into a single location, just open ONE OF THEM and extract it by double clicking it and then dragging the bt.img file to your computer. AND you only have to do this to ONE of the downloaded files, no need to open each of them and drag out the bt.img 10 different times, BUT you do need to have all 10 of them copied into the same folder in order for the full image to extract correctly!
-Also, the instructions stated to run the following command:
Code:
su
cd /sdcard/bt
sh installbt.sh
startbt
bt
but they were made for the AT&T version, so on our phones you need to either:
a)copy the bt folder off of /sdcard/external_sd to /sdcard instead; or
b)use the following commands instead:
Code:
su
[B]cd /sdcard/external_sd/bt[/B]
sh installbt.sh
startbt
bt
-If you make use of it, please be sure to thank the originator of it, anantshri, on his thread here, and DooMLoRD on his thread here for assisting in porting it over from the Xperia10 to the SGSII! Good things!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DooMLoRD said:
\\----[ Announcement ]----//
[12/July/2011] Updated with new package (bt5_sgs2_shell_scripts_v2.zip) containing shell scripts & busybox
//----[ Announcement ]----\\
hi guys DooMLoRD & anantshri present to u:
BACKTRACK 5 on SGS2
all the work was done by anantshri, i mostly assisted by testing it on my SGS2 and modding it slightly so that it will work properly for SGS2... dont forget to thank him!
i will try n keep it short and simple...
for more details u can read the original thread at X10 sub-forums...
[DEV] BACKTRACK 5 on Xperia X10 chroot
[ Screenshots ]
on startup (shell):
in GUI:
phone + BT5 GUI:
[ Requirements ]
rooted device with busybox installed, if u are using CF-root kernel then u already have busybox installed
Some apps from Android Market:
Android Terminal Emulator
androidVNC
[optional] highly recomended keyboard: Hacker's Keyboard
7zip (for PC), for extracting the files
around 3.3 GB free on internal sdcard (/sdcard/)
[ How To : File Setup ]
u need to do this only once
download the files from the links provided in this thread
extract the files using 7zip to a temporary folder (needs 3.3GB free on that drive)
connect ur SGS2 to PC and mount USB storage
create a folder named 'bt' (without quotes) in the root of ur sdcard and copy the bt.img in that folder
also place the file bt5_sgs2_shell_scripts_v2.zip in root of sdcard, this file has to be flashed via recovery
once u verify that the above is correct then un-mount usb storage
reboot into recovery and flash the file bt5_sgs2_shell_scripts_v2.zip stored in root of sdcard (or if u are using CWM app then just select the file for flashing and the app will do the rest )
once ur phone reboots into OS just check the /sdcard/bt folder
final directory structure should look like this:
/sdcard/bt/bt
/sdcard/bt/bt.img
/sdcard/bt/installbt.sh
/sdcard/bt/startbt
/sdcard/bt/stopbt
once u verify that the above is correct then u can proceed
[ How To : Launch BT ]
start Terminal Emulator app on ur SGS2 and enter the following commands step by step (accept/allow any SuperUser request/popup that u may receive)
su
cd /sdcard/bt
sh installbt.sh
startbt
bt
now u are in BackTrack5 shell
to launch GUI (vncserver) enter the following command
ui
now note the number N shown localhost:N
e.g. as u can see from the above image that "New 'X' desktop is localhost:1", so N=1
the vncserver is running at (5900 + N, N=1 ; so server port is 5901)
now launch androidVNC app on phone and fill in the detials as follows
Nick : bt
Address : 127.0.0.1
Port : 5901
Password : 12345678
Username : <leave it blank>
Color Format : 24-bit color (4 bpp)
inside vnc window select input mode (i personally recommend the following)
TouchPad (here your screen works like a big touchpad use it to navigate mouse.)
and then press connect... now u are in BackTrack GUI!
if u want to exit/close BT5 then u need to follow these steps:
close the androidVNC app (Menu -> Disconnect)
go back into Terminal Emulator app and enter the following commands
u should be at this shell [email protected]:~#
killui
exit
now u will get back to this shell> #
now enter the following commands to stop bt and exit
stopbt
exit
exit
u can now exit the Terminal Emulator app
i would also recommend that u reboot ur phone
[ Important Info ]
root password is 12345678
[ Download Links ]
update.zip package containing shell scripts, busybox (which gets installed to temporary location) [to be flashed via recovery]
this will not disturb/conflict with busybox of ur ROM/CF-Root kernel
bt5_sgs2_shell_scripts_v2.zip (~800KB)
main bt.img
these links are 7zip archives split into 50mb files, u will need to download the following:
total size: 486MB
bt.7z.001 (50 MB)
bt.7z.002 (50 MB)
bt.7z.003 (50 MB)
bt.7z.004 (50 MB)
bt.7z.005 (50 MB)
bt.7z.006 (50 MB)
bt.7z.007 (50 MB)
bt.7z.008 (50 MB)
bt.7z.009 (50 MB)
bt.7z.010 (36 MB)
also uploading to mediafire for mirroring...
Mediafire Folder: http://www.mediafire.com/?f9gk3p3t9wip5
md5 hashes:
Code:
bt.7z.001 f19e769bf42b44867c8bb1d9bb9c5d44
bt.7z.002 a4dd26a98d2c6925d871fb108fb5fadb
bt.7z.003 ecca5a5d72c449117b1d3dbc23aeb1a2
bt.7z.004 8ad487a01e4d149f0247ad9288201f32
bt.7z.005 adab9cb3778cd8ac89ccc0e21997c3d7
bt.7z.006 ba6a28de70a1115dc316f45cea508215
bt.7z.007 f59757e891631607e1a35abadb231b3b
bt.7z.008 cdb8c28a1fbd03657bb42e8d69f0600b
bt.7z.009 426d892f872679e3d53d0ebb0376e138
bt.7z.010 c7d2957bc65340d967b9dd3646d7cb39
ENJOY!
Click to expand...
Click to collapse

ScreenShots

does injection and/or wep hacking works?

leond said:
does injection and/or wep hacking works?
Click to expand...
Click to collapse
Unfortunately it does not...I know the main purpose running BackTrack is being able to use its Networking Security Tools, but it is based on Ubuntu Lucid, v10.04 LTS, so you're still able to run a fully functional operating system on your mobile phone! ATM its more of a novelty than a practicality but Im hoping they find a way to turn the tables soon !

Double Post

Triple Post

Nice thanks for trying it and sharing it!

Question the 10 files that you say to download they can not be extracted? i tryed or am i doing it wrong and when i run commands it fails at bt and says chroot cant execute bin/bash no such file or directory help please!

can you still txt and make calls with this?? looks awesome tho

kyhassen said:
can you still txt and make calls with this?? looks awesome tho
Click to expand...
Click to collapse
It side loads it, so you still get all your notifications and phone calls, and if you just hit the home button it'll take you back to the android OS, it doesn't NOT replace it
donnyevo4g said:
Question the 10 files that you say to download they can not be extracted? i tryed or am i doing it wrong and when i run commands it fails at bt and says chroot cant execute bin/bash no such file or directory help please!
Click to expand...
Click to collapse
They ALL have to be downloaded into the same location before you can successful extract it. ie, if you have bt.7z.001 - bt.7z.009 and are missing bt.7z.010, it will not work....did you download and flash the zip? There's more steps than just extracting the bt image(10 7zip files), also just a heads up, when flashing the zip make sure to clear both cache and dalvik, or you may get an installation error...let me know if you need additional help

all ten of the files i downloaded and put into a folder called bt and i flashed the zip and did not get any error message i have 7zip on my pc and it does not even give me the option to extract what am i doing wrong when i right click on the files and go to properties the file type is not a unzippable file

donnyevo4g said:
all ten of the files i downloaded and put into a folder called bt and i flashed the zip and did not get any error message i have 7zip on my pc and it does not even give me the option to extract what am i doing wrong when i right click on the files and go to properties the file type is not a unzippable file
Click to expand...
Click to collapse
Gotcha! wasn't really sure what kind of error you were having but if that is it, all you need to do is double click on any one of the files, I used the bt.7z.001, and when it opens, just drag the bt.img file to your desktop, and let it extract! Its not really a zip so thats why it doesn't have an option to extract it in the menu but again just double click on anyone of them and you'll be all good broda!

ok i got the one file to extract but the others wont now what do i do once i have that image file do i put it in the bt folder and then run commands?

donnyevo4g said:
ok i got the one file to extract but the others wont now what do i do once i have that image file do i put it in the bt folder and then run commands?
Click to expand...
Click to collapse
-Yup you got it! They way 7z file work is that it evenly breaks a larger file down into multiple smaller .7z files.
-In this example, the bt.img file is about 486MB. So, 9/10 of the bt.7z files are 50MB each and then the 10th file, holding the remain bytes, is 36MB. So once you have them all downloaded into the same location, you can open ANY one of them and drag its content to the hard drive, and it will extract the entire 486MB, using all of the files. And you only have to do this ONCE, you DON'T have to open each of them and drag all of their content out.
-So yea, now copy the bt.img file to the bt folder located in the /sdcard/external_sd folder, and then copy the entire bt folder to the /sdcard folder instead(Im guessing the ATT version doesn't have an external sd card, cuz the cd /sdcard/bt command is for the /sdcard location and not /sdcard/external_sd, which is where flashing the zip places the bt folder). So in the end you're going to use this /sdcard/bt folder and not /sdcard/external_sd/bt...EDITED..and don't quote me on the .7z file sizes from above, not really sure how large they are cuz looking at the file now in my phone its 3.26GB, I was using 50MB for an easy explanation and arguments sake only, thx...and Im actually gonna update OP w/ the step needing to copy the bt folder from the /sdcard/external_sd location to /sdcard instead

now im getting a chroot error when i type bt it says chroot execute bin/bash innput/output error? HELPPPPP

donnyevo4g said:
now im getting a chroot error when i type bt it says chroot execute bin/bash innput/output error? HELPPPPP
Click to expand...
Click to collapse
post exactly what you have done so far and what commands you are able to enter successfully and at what command you are getting the error, thx

Posting now stay online

Heres the error im getting look towards the bottom

donnyevo4g said:
Heres the error im getting look towards the bottom
Click to expand...
Click to collapse
ok and where's the rest of the info I asked for?

i can only fit so much in the screen shot what else you looking for

Tutorial Htc Bootloader (Complete With the new ruu)

BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
NOTE: If you do not find your ROM version in the table below, and your ROM version is newer, then your device does not require the RUU.
To install the RUU, simply follow these instructions:
1. On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes.
2.If your computer cannot find your phone, you may need to install HTC Sync. You can download HTC Sync http://www.htc.com/www/help/
After your computer has found your phone, double click on the RUU to start the process.
3Follow the on screen instructions to finish flashing the RUU on your phone.
NOTE: If you encounter an error while flashing your phone, it’s possible that the connection to your phone was interrupted. Simply exit the program, disconnect your phone and start over.
Fully exit the RUU to ensure there is no conflict of multiple instances of the program running.
Disconnect the USB cable from both the phone and the computer.
After a few moments, reconnect the USB to the computer and phone. See above if your phone or computer cannot find each other.
Run the RUU.
Disclaimer: You may not be able to get further FOTA updates once the RUU was applied to your device.
Ruu:
Htc Eu http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R.exe
htc Arabic: http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.09.0099_0209_R.exe
Step 1
Remove and reinsert the battery then proceed to step 2. For devices without a removable battery, long press the power key then select restart. Hold down the volume down key while restarting to start the device in Bootloader mode.
Step 2
Press Volume Down and Power to start the device into Bootloader mode.
Step 3
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 4
Connect the device to the computer via a usb cable
Step 5
On your computer create a new folder (For Example: C:\Android) where we will be putting the following 3 files in this new folder:
adb.exe
AdbWinApi.dll
fastboot.exe
Note: for Mac OS X and Linux you will only need adb and fastboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To find these files:
a.
Run the “SDK Manager.exe” which is found in \android-sdk-windows\
.
Wait about 3 minutes. You will see there are many packages you can update. Please install Android SDK Platform Tools and Android SDK Tools (Please update it if your SDK version is r11).
c.
After you have installed this, you will be able to find the files in the following locations.
1.
To find adb.exe, AdbWinApi.dll, look in \android-sdk-windows\platform-tools
2.
To find fastboot.exe look in \android-sdk-windows\tools
Note: fastboot.exe may be unavailable in the latest Windows Android Tools release. You can extract it from a previous release available here: android-sdk_r13-windows.zip
3.
Mac OS X or Linux users can download the fastboot binary using the following links:
https://www.htcdev.com/process/legal_fastboot_mac
Step 6
Open up command prompt. ( Start > Run > Type CMD,). The window that appears is called Command Prompt.
Step 7
Navigate to where you unzipped the ZIP file and go to the folder you just created (For Example: If you created the folder in C:\Android, then you would type in Command Prompt: cd c:\Android).
Step 8
Type in Command Prompt: fastboot oem get_identifier_token.
Step 9
You will see a long block of text. Copy and paste this text into the the token field below (in the command prompt: Right Click > Mark > highlight the block of text > Right click to copy).
You will see one of the following two screens:
Ref. 9a
Ref. 9b
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)
Step 10
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.
Example:
use the link below to make the bootloader unlock correctly
http://www.htcdev.com/
Program to download
Google android sdk
http://developer.android.com/sdk/index.html
Java Runtime
http://java.com/
htc Sync
http://www.htc.com/www/help/
Credit:
Htc Dev For this page
Thehack1
DjOlivier
Me to have the time to paste and write
If some person have a question and i going to help for every thing

[root] mk3 4.3

WARNING!
Warranty may be void of your device if you follow the procedures given on this page!
You only are responsible for your device. I won’t be liable if any damage occurs to your device and/or its components.
BEFORE YOU BEGIN..
You must do this pre-installation stuff before attempting to root your device in order to avoid any complications later, and have a smooth and successful process.
BACK UP YOUR DEVICE
Back up important data and stuff before you start playing around here as there are chances you might lose your apps and app-data (app settings, game progress, etc.), and in rare case, files on sd card, too.
For help on Backup and Restore, check out our exclusive page on that linked right below.
ANDROID BACK UP AND RESTORE GUIDE: APPS AND TIPS
INSTALL DRIVER
You must have proper and working driver installed on your windows computer to be able to successfully root your device using Universal Root de la Vega script . In case you’re not sure, follow the link below for a definitive guide for installing driver for your Samsung Galaxy device on your computer.
Samsung Drivers
CHARGE YOUR DEVICES
If your android device, or PC, powers off due to lack of battery while the process is underway, it could damage the device. So,make sure both of them are adequately charged and that no power interruption takes place when the process is undergoing — at least 50% battery of the device and laptop is what we would recommend.
OTHER THINGS TO TAKE CARE OF:
└ Use original USB cable to connect your phone to PC.
└ Do not use the procedures given below on Mac (using VMWare) as it works best on proper Windows PC only.
DOWNLOAD FIRMWARE
Download the firmware you want to root. You can get the firmware from either SamMobile’s samsung firmwares directory or just Google the firmware you want to download to get the download link.
Once you’re done downloading the firmware make sure it’s a .tar/tar.md5/.exe file. If in case it’s in .zip format than extract the zip file to obtain either the .tar/.tar.md5/.exe file..
MK3 Firmware
STEP-BY-STEP GUIDE
Once you’ve downloaded all the required files given above, proceed with the instructions given below to get a knox-free root for your firmware using the URDLV (Universal Root de la Vega) script.
PART 1: Cook the firmware file using URDLV script
We’ll first cook your firmware file to make it compatible with the root scripts we’ll use in further parts of this guides. For this, we’re going to use URDLV script first
Extract the Universal-RDLV.zip file to a separate folder on your computer
└ If you have a anti-virus program installed, and it’s trying to delete some of the extracted files, then disable it for a while and re-extract the Universal-RDLV.zip file again, making sure nothing gets deleted.
Open a command prompt window inside the folder where you extracted the Universal-RDLV.zip file. Press “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” option from the context menu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can either create a FULL modified firmware file or just a CSC file from the firmware you want to root. In this guide we’ll be creating a FULL modified firmware as we believe it to be more reliable than creating a CSC file. Input the command given below in command prompt window and hit ‘Enter‘ to start building your modified firmware file
urdlv full C:\I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5
└ The command above is only for illustration purpose. After “urdlv full”, you must insert the path to location of the firmware file saved on your PC. It can be in either .tar, .tar.md5 or .exe format. To get the path to firmware file, you may drag n drop the file in command prompt window and it’ll automagically pickup the file’s path
Right after hitting enter, you’ll see another command window showing you progress of the file creation, which may take time, so be patient here!
You’ll see a similar window (like below) once the file is successfully created
Your modified firmware file is now created with ‘_VEGA’ added to the end of file name, I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME_VEGA.tar.md5. The file is saved under “Output” folder inside the folder where you extracted files in Step 1
PART 2: Flash the modified firmware using Odin
Extract the ‘odin3.09.zip‘ file that we downloaded from the downloads section above. You’ll get the ‘Odin3 v3.09.exe‘ file
Boot your device into Download Mode:
Power Off your device first. Wait for 6-7 seconds after display is off
Now, press these 3 keys together until you see warning screen: Volume DOWN + Power + Home
Press Volume Up to continue to Download Mode
Start/Run the ‘Odin3 v3.09.exe‘ file that we extracted in Step 1
Connect your device to PC. Odin window will show an Added!! message in bottom left box.
└ If you don’t get the Added! message, then make sure you installed driver as given above, if yes, then uninstall and re-install driver again.
Also, try another USB port on your PC and make sure you use good quality cable, preferably that came with the phone. Reboot phone and PC and try again.
Click on AP button in Odin and select the firmware file we created in Step 5 of Part 1, I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME_VEGA.tar.md5
In the “Option” section of Odin, keep only the “Auto Reboot” and “F. Reset Time” boxes checked. All other boxes in the “Option” section should be kept unchecked
Double check the above two steps carefully. You must not make any mistake with the steps above or else you may brick your device. Your Odin’s screen should look like the screenshot below:
Click the ‘Start‘ button on Odin to start flashing the firmware file, and wait until you see ‘PASS!’ message on Odin’s top left box
When you get PASS! message, your phone will restart automatically. You can then disconnect your phone from PC.
└ If you see FAIL instead of PASS in Odin’s top left box, disconnect device from PC, close Odin, remove phone’s battery and put it back in 3-4 seconds, open Odin and then repeat PART 2 and PART 3 of this guide again
PART 3: Root your device
Extract the root_de_la_vega_sdcard.zip file to get these (one file and one folder):
root_de_la_vega.sh (file)
root_files (folder)
Important! Remove the external SD Card from your device, if connected
Connect your phone to PC and Copy the file (root_de_la_vega.sh) and folder (root_files) to the root of internal SD card on your device
└ It’s very important that you transfer the file and folder to the root on your device’s internal SD card.
Now, restart your device
Once it has restarted, delete file and folder you copied to SD Card in Step 3 above. Yes, delete the file (root_de_la_vega.sh) and folder (root_files), both of them
Important! Now, after you’ve deleted the files, restart your device again.
Once your device has rebooted, Root Access should be there. You can now insert your external SD Card back if you have one
└ Put the external SD card back only after rebooting the device (as instructed in step 6)
CONFIRM ROOT ACCESS
You must have a new app installed now: SuperSU. Check it in app drawer. Also, to check whether you got root access or not, use this simple made-for-this-purpose app, Root Checker.
Note: this will trip knox use it at your own risk
respective owner and all credits go to the people HERE

If you're saying that this may still trip Knox, the easiest and fastest way to root still remains just flashing a custom recovery with Odin and then flashing root.
Much simpler and much less time consuming than patching an entire tar and then flashing that huge file with Odin.

i understand cnexus but this was requested by a member of the community ive heard some people having problems with cf auto root i myself had problems with cf autoroot and a few other root ways so im just giving this to the community if all else fails for them like myself

Root Celkon A225 Android Mobile and Install Touch Recovery

This Post will help you to root your Celkon A225 Android Mobile.
Installing Celkon A225 ADB Drivers
Download and install Celkon A225 Android Mobile drivers from download links below.
To install the drivers follow the below steps.
Extract the downloaded driver file to any folder you want.
1. Open Device Manger(You can open open it from control panel or from search in start menu.)
2. Right Click on your PC name and click add Legacy hardware.
3. Then choose 'Install hardware that i manually select from list(Advanced)' and click on next.
4. Select 'Show All devices' and click next. Then Click on Have disk and browse for the folder you have extracted your drivers(Choose .inf file inside the SP_Drivers_v1.4 folder).
5.Then you will get as in screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. Choose 'Google ADB Device Interface' from 'Google,Inc' Manufacturer and click on next. Then the ADB driver will be installed.<br />
7. Repeat the same procedure (steps 1-6) for other 2 google drivers and for MTP, Media Tech drivers. That's All.
You can check your ADB drivers installation by using below method
1. Download adb from link below.
2. Extract all files and place them in C:\Windows Directory
3. Turn on USB Debugging(From Developer Options) in your Android mobile and connect to your PC with USB cable.
4. Open Command Prompt and run the below command. Then it should list your device as below. If your device is not listed indicates that drivers are not properly installed.
HTML:
adb devices
Rooting Celkon A225
If drivers are properly installed rooting procedure is very simple. Download the 1 click rooter software from the download link below.
After Downloading the file follow below steps to root your mobile.
1. Enable USB Debugging in your Settings from Developer Options
2. Make sure you have installed properly. Now launch MTK Tools(Root Genius) that you have downloaded from above link.
3. Connect your Mobile with USB Debugging enabled and click on next. Then it will show as connected and you can see Root button if drivers were installed properly.
4.Click on Root and wait till your device gets rooted. It took around 15 minutes for my Celkon A225 Mobile.
That's All
Install Touch Recovery
By Rooting with Root Genius(MTK tools) you will get a custom recovery in Chinese language. So I will recommend to install Carliv Touch Recovery(CTR) to make your recovery to look ultra modern. With this one you can navigate from touch in Recovery Mode.
Download and install CTR from link below.
Follow the Below steps to install touch recovery. Do not disconnect your mobile while installation is in progress
1. Extract the archive to any folder.
2. Connect your Android mobile to PC with USB Debugging Enabled.
3. Run CTRv2.2.exe as administrator. Then it will show below message. Click OK when it shows the message(It will aumatically close if files are copied)
4. Then it will turnoff UAC and add some entries to registries as it needs some open port to access your android and update recovery from your PC. Click OK when it shows the message.
5. After that it will start porting. Make sure your android device is booted up and is connected to PC with USB Debugging enabled. Then click yes.
6. Wait for 2 minutes it will install the touch recovery automatically for you.
Now you can check your touch recovery by going to recovery mode ( use power + volume down when android is off) . That's All
Caution:Rooting/ Recovery installation is a risky process. Your Device may brick if its wrongly done. Keep your original firmware with you before going to this process to install your firmware in case if you got any problem.
Attachments
adb.zip
CTRv2.2.zip
SP_Drivers_v1.4.zip
MTK6589_6577_w6575_V1.06.zip

Windows 10 Mobile System32 supplement (taken from IoT build 14393)

I made a zip file with what I feel will be usable now that we have cmd working. This zip file includes cmd.exe, bcdedit.exe, powershell.exe, reg.exe, ipconfig.exe, tracert.exe, ping.exe, shutdown.exe, xcopy.exe, mountvol.exe, netsh.exe, sleep.exe, tlist.exe, tracelog.exe, tzutil.exe, winrshost.exe, and the files required for those all to function properly. Everything is in its correct place, just move the contents of the zip into system32 and reboot. I chose these files due to what I saw happening on the forums and what I personally needed, but if you need anything else, feel free to ask and I'll add it to the zip so you don't all have to download the entire IoT image.
https://1drv.ms/u/s!Ao6Il1GG4MMNouQZW4f7xWJWiDBf7g

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for sharing but I can't use bcdedit.

ninjaofbacon said:
I made a zip file with what I feel will be usable now that we have cmd working. This zip file includes cmd.exe, bcdedit.exe, powershell.exe, reg.exe, ipconfig.exe, tracert.exe, ping.exe, shutdown.exe, xcopy.exe, mountvol.exe, netsh.exe, sleep.exe, tlist.exe, tracelog.exe, tzutil.exe, winrshost.exe, and the files required for those all to function properly. Everything is in its correct place, just move the contents of the zip into system32 and reboot. I chose these files due to what I saw happening on the forums and what I personally needed, but if you need anything else, feel free to ask and I'll add it to the zip so you don't all have to download the entire IoT image.
https://1drv.ms/u/s!Ao6Il1GG4MMNouQZW4f7xWJWiDBf7g
Click to expand...
Click to collapse
how can i run cmd in windows phone 10

parth0072 said:
how can i run cmd in windows phone 10
Click to expand...
Click to collapse
To run cmd on Windows 10 Mobile, look at the SFTP and cmd over SSH thread

BlueTR said:
Thanks for sharing but I can't use bcdedit.
Click to expand...
Click to collapse
I noticed that, I'm hoping to have this fixed within a few days

i guess this is for the older devices and non x50 windows devices or ?

Works on x50 devices

todarkness said:
i guess this is for the older devices and non x50 windows devices or ?
Click to expand...
Click to collapse
I don't have any x50 devices, but they should work for them too, I can't think of any reason they wouldn't

I got cmd.exe and the mui file in my system32 folder with the help of a ssh app on my android phone. How do I get the cmd function to work on my windows phone now?

svaethier said:
I got cmd.exe and the mui file in my system32 folder with the help of a ssh app on my android phone. How do I get the cmd function to work on my windows phone now?
Click to expand...
Click to collapse
If you have interop tools installed, tap the bottom button on the CMD page

I hit the cmd button on the bottom of the ssh page but nothing happens. It just says that the user failed to respond in time.

svaethier said:
I hit the cmd button on the bottom of the ssh page but nothing happens. It just says that the user failed to respond in time.
Click to expand...
Click to collapse
I've been getting that too, I've only been using SSH to use cmd. It does say cmd access is a work in progress, so I'm waiting for the next update to try to use it locally.

Have you been getting a not enough space to use command error when using ssh after putting the cmd exe and mui file into system32 even though you have 3+ gb left?

svaethier said:
Have you been getting a not enough space to use command error when using ssh after putting the cmd exe and mui file into system32 even though you have 3+ gb left?
Click to expand...
Click to collapse
What command are you trying to use?

It happens when I login to the ssh app to use cmd, it also says something about missing some text file for something. This didn't start happening until I put both cmd files into system32

svaethier said:
It happens when I login to the ssh app to use cmd, it also says something about missing some text file for something. This didn't start happening until I put both cmd files into system32
Click to expand...
Click to collapse
Is cmd.exe.mui in en-US?

Yes, I deleted both files from system32 then did the copy process over again but same message happens.
'the system cannot find message text for message number 0x2350 in the message file for application.'

svaethier said:
Yes, I deleted both files from system32 then did the copy process over again but same message happens.
'the system cannot find message text for message number 0x2350 in the message file for application.'
Click to expand...
Click to collapse
It sounds like cmd.exe.mui is in the wrong place, make sure it's in system32\en-US

The directory was called EN-US so copying it to en-US didn't correctly copy it over

svaethier said:
The directory was called EN-US so copying it to en-US didn't correctly copy it over
Click to expand...
Click to collapse
Is it working now?