Develop Bugs

anyone know anything about ANDROID SDK?

im trying to install android sdk from this link http://wiki.cyanogenmod.com/index.php?title=Howto:_Install_the_Android_SDK
and im on step #17
everything before that worked fine and my command prompt recognized my device so i know its recognizable.
step 16 and 17 ask
16. Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
17. You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark
i do no see my phone listed on their. Any idea's?

Do you see anything?

Yeah i see a bunch of things but not my device..

Joey_UFC said:
Yeah i see a bunch of things but not my device..
Click to expand...
Click to collapse
How about a screen shot, so I can see exactly, you may have messed up somewhere else, possibly.

teh roxxorz said:
How about a screen shot, so I can see exactly, you may have messed up somewhere else, possibly.
Click to expand...
Click to collapse
aight no problem. 1 minute

{
"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"
}

i just read the sdk instructions again and i think i know whats wrong.
it says: On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue

i don't think i need to go on any further lol

Joey_UFC said:
i don't think i need to go on any further lol
Click to expand...
Click to collapse
Yea you're good cuz I see android phone, and if you click the plus, you should see bootloader interface.

im gonna try and root my nexus right now and see if it works. SDK is a hassle man. rooting the nexus is soo easy but the drivers are whats really difficult

Joey_UFC said:
im gonna try and root my nexus right now and see if it works. SDK is a hassle man. rooting the nexus is soo easy but the drivers are whats really difficult
Click to expand...
Click to collapse
Naw, basically you just gotta run the exe, then the sdk manager starts downloading a bunch of stuff, then you just really need the adb folder.

teh roxxorz said:
Naw, basically you just gotta run the exe, then the sdk manager starts downloading a bunch of stuff, then you just really need the adb folder.
Click to expand...
Click to collapse
this is my first time working with sdk and im just following instructions and getting my way to start rooting. everything i have done so far was just to get all the drivers. there was 27 steps just for sdk.
now im gonna start root using this process
http://www.redmondpie.com/how-to-root-nexus-s-4g-tutorial/

now im on the first step and downloaded the files and extracted it so i can get the superuser zip and the recovery.img
there not even in there so i had to find them myself and get them. I seen a few nexus s root instructions and all of them are different and not put well together at all

Joey_UFC said:
now im on the first step and downloaded the files and extracted it so i can get the superuser zip and the recovery.img
there not even in there so i had to find them myself and get them. I seen a few nexus s root instructions and all of them are different and not put well together at all
Click to expand...
Click to collapse
Ah, its not too bad, though just follow instructions. If you get errors doing any code, have someone check it for you, take a 5 min break, or ask for help.

teh roxxorz said:
Ah, its not too bad, though just follow instructions. If you get errors doing any code, have someone check it for you, take a 5 min break, or ask for help.
Click to expand...
Click to collapse
yeah thanks, i hope you and some others don't mind helping me out here. i run into road blocks every other step lol

Joey_UFC said:
yeah thanks, i hope you and some others don't mind helping me out here. i run into road blocks every other step lol
Click to expand...
Click to collapse
I practically have a flawless victory record in getting people rooted...lol, and no worries. Feel free to ask away.

teh roxxorz said:
I practically have a flawless victory record in getting people rooted...lol, and no worries. Feel free to ask away.
Click to expand...
Click to collapse
Yeah man thats one of the few things i literally miss about the Evo 4g. the community is ****ing rock solid and full of people like you and DirkyD3rk. No offense but the nexus forum are DEAD. and some of them on there aren't even current nexus owners, they just stop by here and there so theres no guaranteed help.
But here goes my first question..
Now in order to proceed, you will need to unlock bootloader of your Nexus S 4G. You can unlock your Nexus S 4G’s bootloader by installing Android SDK and then using Fastboot OEM unlock command by opening tools folder in Command Prompt. You can simply hold shift and then right click on tools sub folder in Android SDK main folder and select “Open Command Window Here” from context menu.
Click to expand...
Click to collapse
Can you explain this a little simpler for me please, not really understanding it correctly.
here's the link to it if you wanna take a peak : http://www.redmondpie.com/how-to-root-nexus-s-4g-tutorial/

Joey_UFC said:
Yeah man thats one of the few things i literally miss about the Evo 4g. the community is ****ing rock solid and full of people like you and DirkyD3rk. No offense but the nexus forum are DEAD. and some of them on there aren't even current nexus owners, they just stop by here and there so theres no guaranteed help.
But here goes my first question..
Can you explain this a little simpler for me please, not really understanding it correctly.
here's the link to it if you wanna take a peak : http://www.redmondpie.com/how-to-root-nexus-s-4g-tutorial/
Click to expand...
Click to collapse
Well thank for the compliment, I try to do what I can, as well as derk.
And as for your question:
open command prompt, navigate to you sdk folder. To make it easiest: rename the sdk folder android, place on your desktop, then in command prompt run: cd desktop/android/tools [i copy all the adb file from platform-tools into tools-]
connect your phone via adb, then run adb remount [should say remount successful], then run that command, Fastboot OEM unlock

how do i connect my phone to adb

Joey_UFC said:
how do i connect my phone to adb
Click to expand...
Click to collapse
Connect it to the pc via usb , and from the application settings on the phone you should have usb debugging enabled, so adb can see it.
After getting to the folder via command prompt, run adb devices, to make sure you see your device.

[ROOT](11-17-12) Root Nexus 10 with CWM and SuperSu Zip (Stress Free and Simpler)

{
"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"
}
Updated 11-17-12: Now that we have a stable CWMR image thanks to damien667 this procedure should be a lot less risky and less stressful!
This is confirmed working but due to the procedure involved is risky! The standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your tablet by following this procedure!​
You must unlock the bootloader before performing this procedure!
Credits: Kidgoo for testing and coming up with the method, thanks to damien667 for the fixed CWM images, and Chainfire for the SuperSu zip and binaries!
Before you begin make sure you read and reread the procedure and fully understand the directions.
1. Download the CWM-SuperSU-v0.98.zip
2. Download damien667's fixed CWMR 6.0.1.6 touch version of from here
3. Connect the Nexus 10 to your computer
4. Flash the CWMR image you downloaded in step 2 using fastboot
Code:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
5. Touch "Install from SD Card" in CWMR
6. Select CWM-SuperSU-v0.98.zip that was downloaded in step 1
7. Let CWM-SuperSU-v0.98.zip install
8. Select "Reboot System"
9. Enjoy your rooted Nexus 10 !
To keep your custom recovery installed permanently and not get overwritten by the stock recovery when your reboot your tablet delete the following:
Code:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p

Reserved

works! thank you very much!

Awesome!
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!

WannaB101 said:
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!
Click to expand...
Click to collapse
One-Klick CWM Tounch + SuperSU would be great!!! :good::good::good:

So what am I supposed to do if ADB doesn't recognize the "sideload" command?

gravis86 said:
So what am I supposed to do if ADB doesn't recognize the "sideload" command?
Click to expand...
Click to collapse
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.

Perhaps a video?
Perhaps you could provide a video to help us along?

shimp208 said:
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.
Click to expand...
Click to collapse
Yep, my ADB was out of date... Thanks!

Got the latest version of ADB?

With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?

WannaB101 said:
Perhaps you could provide a video to help us along?
Click to expand...
Click to collapse
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!

shimp208 said:
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!
Click to expand...
Click to collapse
I hit ya with a question above...

joeski27 said:
With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?
Click to expand...
Click to collapse
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.

I know this is probably a noob question but the fastboot commands (the first two, for booting from CWRT) -- should they be done in Fastboot Mode or can they be done while Nexus 10 is on and at home screen with USB debugging enabled? If you need to be in Fastboot Mode, how do you get there with Nexus 10?
Thanks!

shimp208 said:
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.
Click to expand...
Click to collapse
Ok, the problem I have now is while I have the files on my tablet, I cannot move them to the root of the internal storage at this point...??? Suggestions??? Don't you have to be rooted in order to do this???

For some reason when I'm not in fastboot mode, I can use adb (adb devices lists my Nexus 10), but when I'm in fastboot mode, adb no longer recognizes the device. fastboot devices does however see it when in fastboot mode.
Anybody else have this problem or know why this might be happening? Thanks!

I'm still getting the sideload error after updating the ADB
Any insight, please?

So to others who are working on this and awaiting responses from the OP, where exactly have you placed the downloaded files on your tablet? specific locations?? and if so how did you get them there? I'm totally lost at this point, LOL, hoping to get some clarification soon...

Worked ... however .. you DO have to be in FASTBOOT already (power + Vol UP + Vol DOWN) - yeah it might be obvious when you're not tired as hell - but for those wondering
The first line should be:
fastboot boot /path/to/<recovery>.img
no fastboot reboot was needed - it rebooted itself.
I had a HELL of a time finding the sideload entry in CWM (that's just my brain deadness).
You have quite a bit of time More than enough.
THANK YOU!

[Q] Wiped OS need help to sideload zip file

I just messed up big time.
I have been rooted for a couple of months now and played around with a couple of roms. I noticed my free storage shrinking when there apparently should have been nothing on my Nexus 7 except for the system files. What I did was delete my system,storage and cache with Clockworkmod Recovery leaving me with a blank tablet. Unfortunately now I can't install any zip from my sdcard as there is just emptiness on my tablet meaning I have no OS. I had initially thought I would be able to just install the OS from my usb stick but I couldn't find any way to mount my usb stick in recovery mode and I have reason to believe it just isn't possible.
As far as my research has taught me the only way to install a OS now is via sideloading it. I have spent like 2 hours reading through several threads and various other sites how to sideload a zip file onto my tablet but I'm having trouble with that. I downloaded ADB tools and I looked into this thread: http://forum.xda-developers.com/showthread.php?t=2380913
My current state is that I am in recovery mode and selected 'install zip from sideload' I have ADB tools and the OS but can't sideload it onto my tablet. When I use the command 'adb devices' my N7 is not listed. When I go to device manager the N7 is listed but there is also a warning sign displayed.
{
"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"
}
I desperately need help to resolve this issue, I love my Nexus 7 and can't bear the thought of having bricked it for good because of my own stupidity.
Much thanks in advance.
P.S. It is already late at night in Germany so I won't answer in the next few hours.

I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images here:
http://developers.google.com/android/nexus/images
Pick nakasi or nakasig depending on whether you have wifi or mobile version

You need to install this to use ADB while in recovery. You can use fastboot to flash the stock ROM.

sfhub said:
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images
Click to expand...
Click to collapse
I'm sorry I wasn't aware of this being the wrong sub-forum.
Thanks for your submitted fix, it sounds very simple yet I don't know how to perform it. Do you mean I have to select 'Restart bootloader' on my N7?
How do I then get the factory image onto my tablet?

I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.

sfhub said:
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery. He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.

sfhub said:
...
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
Username invalid said:
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery.
Click to expand...
Click to collapse
That's why I suggested he follow your post to install the naked drivers if he wanted to use adb sideload in recovery instead of using fastboot and the images.
Username invalid said:
He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
Click to expand...
Click to collapse
According to the OP for naked drivers, he suggests removing old drivers. I just relayed what was in that post.
1wayjonny said:
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse

merchants oicedBri
Update:
Thanks for your helpful answers, I figured it out now.

[SOLVED] Need help rooting I747M

Original Post
Hello, I am running an unlocked Bell S3 (SGH-I747M/d2can, hope this is the right forum) on 4.4.2 official Sept. 2015 update. Screenshot shows the build info.
{
"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"
}
I had a similar issue with my Skyrocket, although I was able to root it with Saferoot.
I have a MacBook on Yosemite and a Windows Vista PC (don't hurt me). Windows fails to cooperate with any drivers I install on it if they install at all. All I can get is the file transfer. JOdin3 can recognize it, but gives me libusb error -12. It just won't work. Odin..... Nope.
On my Mac, I have access to ADB and file manager. But there are no root tools for Mac.
On the S3 itself, I tried Towelroot v2, Saferoot, Framaroot, Kingo, ActiveRoot, MotoChop, that odd Chinese one, and more. They all failed.
I'd be more than happy on rooted stock, I was rocking that on my Skyrocket (pun intended) for a good 2-3 months, though I would prefer a custom ROM.
Sorry if this has been asked before.
Edit: I managed to get the drivers working by myself after reading about the registry issues.
I had an issue with a partial installation that the installer (or the computer) didn't like. Here is how I fixed it:
Manually reinstalling the Samsung USB Drivers (Windows)
First, open the file explorer (Pro tip: Hold the start button and press E) and in the address bar, type C:\Program Files\SAMSUNG\USB Drivers. If you see Uninstall.exe, right-click it, Run as Administrator, let it uninstall, and you can skip 7-10. Lucky. Otherwise...
Download 7-Zip and install it. I suggest 15.xx beta, the 9.xx is old.
Download the official universal USB driver from Samsung. Don't open it yet.
Now, find the driver ZIP file. This is most likely going to be in your Downloads folder as SAMSUNG_USB_Driver_for_Mobile_Phones.zip
Right-click on it and find 7-Zip > Open Archive...
Drag the file to your Downloads folder, and close 7-Zip.
Right-click on the EXE file with the similar name as the ZIP and do 7-Zip > Open archive...
Hit Extract and it should extract to a directory with the same name.
Open that folder and find the Uninstall.exe and Uninstall_1.exe.
If you're on a 64-bit installation, right click Uninstall_1.exe and select Run as Administrator. Otherwise, choose Uninstall.exe. (Google the way to find it if you are not sure).
Let it uninstall.
Now go back to your Downloads folder and right-click SAMSUNG_USB_Driver_for_Mobile_Phones.exe and Run as Administrator. This installation seems to take a very long time for some reason, don't panic.
Once that is done, you (hopefully) have drivers now! Plug in your phone and you should see "Installing driver software..." and it works!
Click to expand...
Click to collapse
Sent from my SGH-I747M using Tapatalk

You need to be in download mode on the phone, connect it to vista machine, launch Odin, flash twrp from Odin, boot into twrp, flash supersu from twrp, and you will have a rooted stock rom.

audit13 said:
You need to be in download mode on the phone, connect it to vista machine, launch Odin, flash twrp from Odin, boot into twrp, flash supersu from twrp, and you will have a rooted stock rom.
Click to expand...
Click to collapse
No, I can't get Odin to recognize my S3 (or my Skyrocket) in download mode. I tried.
Thanks, though.
Sent from my SGH-I747M using Tapatalk

Does it show up as an unknown device?

audit13 said:
Does it show up as an unknown device?
Click to expand...
Click to collapse
I get nothing. It doesn't see it.
Drivers are not working right or something. I installed Samsung drivers but, even still, each time I plug in my phone it asks to install drivers.
Sent from my SGH-I747M using Tapatalk

Tried different USB cables and USB ports? Doesn't even show up as a device in OS X?

audit13 said:
Tried different USB cables and USB ports? Doesn't even show up as a device in OS X?
Click to expand...
Click to collapse
Yes, yes.
OS X has ADB access and file access, but JOdin3 won't recognize the thing, and when I start it I get a message saying that heimdall-mac.dmg has no mountable filesystems or something.
Sent from my SGH-I747M using Tapatalk

What about running win7 in VMware? Or getting access to a win7 machine to try it out?

audit13 said:
What about running win7 in VMware? Or getting access to a win7 machine to try it out?
Click to expand...
Click to collapse
Can't afford a Win7 disk. But I may be able to try a friend's computer.
Sent from my SGH-I747M using Tapatalk

I ran into the same issue last night trying to root mine.
Win 7 would not install the correct drivers for my S3, I installed kies 3 just for the heck of it, and after that it picked up the correct driver for the S3. After that Odin picked it up right away after plugging it back in and I was able to flash TWRP on it. I installed Kies 1 first. Then Kies 3.
Give it a try, see if it works for you, I spent all day yesterday trying to get TWRP on it.
Good Luck!

Rooting I747m
I know it's answered, but here we go.
1. Flash TWRP.
2. Flash CF Auto-Root.
3. Flash TWRP again.
Done.

The i747m can be rooted by:
1) flashing cfautoroot without TWRP;
2) flashing TWRP, flashing supersu from TWRP; or
3) flashing TWRP, flashing custom rooted ROM from TWRP.

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?