I've just updated the Dell Streak 5 wiki with a guide to setup fastboot for linux in the Flashing guide section.
Oh, the sdk finally readded the fastboot binaries for *nix and osx are finally readded.
Main reason the nix and osx guides were stubs were that previously the fastboot binaries for all 3 os groups were missing from like platform-tool r6-r9 and they're included again in r10
I'm gonna update fastboot+adb.zip to include these files and take a look at the win drivers and do a big update.
I'm also going to rewrite your portion once I get fastboot+adb.zip reorganized and bring it to parity with the win version. Thanks!
Finally, the *nix portion will be added to the s7 and venue guides too to maintain parity and the s10 one when I get around to making the rest of it
Yeah, i saw your edit, i've since shortened the guide, because the relevant additional info is available on the android website and i've linked it, however, having only adb and fastboot in a zip is even better.
I'll see if the Mac version works on PC-BSD 9, and if it does, i'll add that as well (you never know)
No command udev in my fedora. At least in the my user PATH! In my root's PATH, I have only udevd and udevadm! I use Fedora, are these instruction Ubuntu specific?
Ultimately only the basics will be covered, I'm not willing to add (or even let others add) a dozen different branches to support every different flavor of linux.
When I'm ready to release a new Fastboot+ADB I will trim it down more if needed and leave it at that, currently it's pretty much about what I'd like it to be, it's mostly just a little formatting to make it match the rest of the guide.
The guide techincally also skirts the issue of different windows versions, there might be some minor things depending on which ver of windows and if it's x64/x86 but those details are left to the user to fill in on their own.
Users should be able to fill in some stuff like this on their own, just like the implied availablity of a unzipper.
If it's something that's specific to fastboot or adb and it's missing, we'll add it of course.
bazzoon said:
No command udev in my fedora. At least in the my user PATH! In my root's PATH, I have only udevd and udevadm! I use Fedora, are these instruction Ubuntu specific?
Click to expand...
Click to collapse
Udev is the udev daemon. I'm not familiar enough with Fedora to know what's the command to restart it, but you could reboot the computer and the new rules should take effect.
Yes, it is Ubuntu specific, since i use it, and the intructions on the official android site are for Ubuntu.
Actually the only thing that isn't mentioned anywhere, except in the Streakdroid install guide, was adding the -i 0x413c option after fastboot (or the respective USB VendorID), an omission that took me along time to find and kept me really frustrated by being unable to change ROMs.
Edit The Manii
I've linked to the SDK-Platform tools zip on the official android site, to save a few steps of installing the full SDK, so for now, you don't need to host a separate zip of adb and fastboot, until Google updates the SDK.
-i 0x413c is optional depending on how your env is set up.
I believe that optional step you made to register that ID makes it optional on *nix too, but as I dont use fastboot under linux I cannot verify.
It is optional under windows though.
I merely havnt finished testing the s7 drivers, the zip was missing the *nix/osx fastboot binary, it always had the adbd binary
For me fastboot didn't work without that option, just stayed on 'waiting for device' despite having read pretty much every guide that's out there for setting up fastboot and adb on linux (and ubuntu specifically), even though adb worked perfectly fine.
As far as not adding a custom rule in udev, I'm pretty sure it's needed since it's posted on the official android site and it's stated that it's required in order for the OS to recognize your phone.
As for the Mac OSX version, just downloading and extracting the SDK Platform-tools package and running fastboot from there should just work, but i don't have a Mac to test it on.
Related
hey guys, for those that havnt seen it today Ubuntu has been released for the Nexus 7 and for both 8GB and 16GB Models! wondering if anyone in the community has figured out how to dual boot it or if it is even possible? thanks all!
Heres the link of how to install if your wondering
What you will need:
Nexus 7 Tablet (8GB or 16GB)
Standard MicroUSB Cable (should come with the device)
Ubuntu Nexus 7 Desktop Installer installed on your development system
Ubuntu 12.04 LTS or Later
Optional
Micro USB Host Cable (OTG Cable) - used for attaching keyboard, mouse, etc. Directions on how to get and use one of these are towards the bottom of this page.
Ubuntu Nexus 7 Desktop Installer
A simple one-click installer has been provided, and is available in a PPA.
sudo add-apt-repository ppa:ubuntu-nexus7/ubuntu-nexus7-installer
sudo apt-get update
sudo apt-get install ubuntu-nexus7-installer
Usage instructions for the installer are provided below.
Unlocking the Nexus 7
The Nexus 7 ships with a locked bootloader. You must unlock it in order to flash different images to the device. Fortunately, this is a trivial process, and you only need to do it once.
Warning: Unlocking the bootloader erases all data and resets the device to factory defaults.
Reboot the Android device into the Android boot loader. To do this, hold the volume down button and press the power button. Continue holding the volume down and power buttons until you see the boot loader UI. The device now displays the boot loader GUI, which looks like this:
Verify fastboot lists the device:
$ sudo fastboot devices
1234567891234567 fastboot
Start the bootloader unlock process:
sudo fastboot oem unlock
You are prompted on screen to unlock the bootloader on the Android device screen. Follow the on-screen directions to continue. Your screen should now look like this:
Complete the process by rebooting:
sudo fastboot reboot-bootloader
Or simply press the power button.
Installing Ubuntu on Nexus 7
Once all setup has been completed, the installation can start. To install, ensure the Nexus 7 is in fastboot mode, plug it into your computer (and make sure NO OTHER DEVICES are plugged in).
Find the installer in the dash (search for 'nexus'):
This will provide a Graphical Interface for installing Ubuntu. This tool will download the latest image automatically, and flash it accordingly. The flashing step should take about 2 minutes. Once the flashing is complete, the device will reboot and finish the installation. This step can take 10-15 minutes.
Returning your Nexus 7 to Stock Android
Warning: Disconnect ALL other mobile devices connected from your computer or they might get erased too. This will erase ALL DATA on your Nexus 7.
In case anything happens while developing, the system image for Nexus 7 can be found here: https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
After downloading the above tarball, uncompress it with the following:
tar zxvf nakasi-jro03d-factory-e102ba72.tgz
Then, place your machine into fastboot mode and run the resulting script:
cd nakasi-jro03d/
sudo ./flash-all.sh
You may get the following warnings, which you can ignore, the restoration will continue anyway.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Troubleshooting the Install
If you have problems installing the image, please use the following troubleshooting steps:
Detach the USB cable, restart the tablet back into fastboot mode, and re-attach the USB cable.
If problems persist, reboot your host PC.
If you still have issues, try a different USB cable.
If you have a 16G tablet, try using the 8G image.
If you still have issues after doing all this, return the image to stock using the directions above and re-try.
If none of that works, ask a question on Ask Ubuntu using the mobile tag, or ask for help in the #ubuntu-arm channel on freenode. If you believe it's a bug, file a bug against ubuntu-nexus7 in Launchpad.
Ehm, do i miss something or is this ubuntu only installation?
Edit: i mean, not dual boot, but only ubuntu
Do I need a mouse and a keyboard to use Ubuntu? Or I can also without them?
Rusl1TA said:
Do I need a mouse and a keyboard to use Ubuntu? Or I can also without them?
Click to expand...
Click to collapse
it has a built in touch keyboard/mouse, so you can do either way
you can use a touch screen for it, mouse and keyboard is compatible
what do you mean ubuntu only install?
sorry if you mis understood, but i posted the guide there but i am also curious if theres a dual boot avaliable.
is bluetooth not usable in the in ubuntu while installed?
And I saw this install method over at androidcentral.com and I dont recall it being dualboot. It did a complete install of ubuntu only and erased android from the device
As of right now, dual-booting is not an option, however, this build did just come out today, and in the coming weeks, we'll likely have many updates and options, so i'd hang tight. Needless to say, it's a great experience
yess dual boot will be awesome.
Download and follow the instructions in the complete Linux installation guide. (Its an app in the play store) It works pretty well and you can use Ubuntu, Debian and a few others without wiping your system. I prefer the Ubuntu lite version. Something else to try out
Sent from my Nexus 7 using xda app-developers app
technolust109 said:
what do you mean ubuntu only install?
sorry if you mis understood, but i posted the guide there but i am also curious if theres a dual boot avaliable.
Click to expand...
Click to collapse
Why did you title the thread as "Dual Boot Ubuntu" then?? Confused as well.
Change your thread title,its misleading.
yes my question was about dual booting, sorry if theres any confusion caused.
Folks, it's not that hard of a question when you actually read what the poster states. CURRENTLY, THERE IS AN INSTALLER THAT INSTALL UBUNTU TO THE NEXUS 7, BUT DOING THIS WILL CAUSE THE DEVICE TO BE FULLY WIPED FIRST REMOVING ANDROID. HE IS WONDERING IF THERE COULD BE [OR IS] AN INSTALLER THAT INSTALLS UBUNTU ALONGSIDE ANDROID TO BE ABLE TO BOOT THE DEVICE TO EITHER OS AS THE USER WISHES [ ALSO ASKING IF DUAL BOOTING BETWEEN THE 2 IS EVEN POSSIBLE.SO HE KNOWS IF IT IS WORTH HIS TIME TO INVEST IN MAYBE FIGURING IT OUT ON HIS OWN]. I am going to assume some form of dual booting would be possible as Linux bootloaders are generally very capable of booting OSes that use environments totally different from itself.
I am wondering the same thing as I am a very good technical user who can deal with a lot of issues, but have never gotten deep in to the programming side of things. I am shocked that for such an alpha build [really flaky Bluetooth, [Wi-Fi is solid] Unity crashes quite often and nVidia has had sucky Linux driver support for years now [wish they would take Linux more seriously but hey at least they have drivers]]. All leads to a painful experience for most [especially if you are not a nerd or techie and not used to dealing with very new alpha Linux type issues, if you don't mind it it does work].
Why wouldn't they have set it up as a dual boot to begin with? That way if you know something you need to get done can be done in Android and not in Ubuntu then you could just restart and choose the different OS. Not to mention if this is for modders and enthusiasts to test bed things on the tablet then they are going to most likely be some Android developers to start who would love to say use Eclipse to develop Android code for whatever and then oh no restart in to Android to I dunno test their work.
All that to say PLEASE SOMEONE WITH THE KNOW HOW let's figure out a way to fully dual boot a NATIVE Linux [not that install a loop file system and have it use VNC server to view the session junk you see on the Play Market, it's quaint and all, but not nearly as nice as a full Linux with full access to the hardware [I use it too, much love to backtrack] but am dying to dual boot an Android/More full [ I REALLY want Backtrack 5+ but Ubuntu would be worth keeping around until Backtrack gets around to working out their builds to be dual boot on some Android based systems] Linux as needed.
The approach that the Boot Manager app uses would probably work. They modify the /boot partition to point to a different device for /data than normal. Then you can switch between ROMs by flashing a different /boot partition. They automatically bundle the /boot partition into an update.zip and store them next to the image file on you SD card.
thanks for clearing it out RealPariah! by the way your username link to the band pariah orr? Cheers.
I would like to try this but what's the best/easiest way to back up my system? (I.e. app and game save data as well as for directory bind and folder structures). I tried clockworks backup process before, but I either did it wrong or it doesn't cover everything.
Can I just copy paste everything from my root folder?
Nikguy said:
I would like to try this but what's the best/easiest way to back up my system? (I.e. app and game save data as well as for directory bind and folder structures). I tried clockworks backup process before, but I either did it wrong or it doesn't cover everything.
Can I just copy paste everything from my root folder?
Click to expand...
Click to collapse
you might want to try and use titanuium backup and copy out the entire "titanium backup" folder onto your computer, so when you revert back to android you should be able to copy it back in and restore from titanium backup. hope it works.
technolust109 said:
you might want to try and use titanuium backup and copy out the entire "titanium backup" folder onto your computer, so when you revert back to android you should be able to copy it back in and restore from titanium backup. hope it works.
Click to expand...
Click to collapse
Huh great idea! Thanks, I'll give it a shot
all good mate! good luck!
So tomorrow I'll be receiving a Nexus 10 from swappa that is already rooted and unlocked.
I still want to be prepared to have all the tools just in case I need to unroot & lock her back up.
I read that ADB needs to be updated for 4.2.2. I am no longer familiar with ADB and just wanted to know the best place to find the most recent files.
I read through some of wugfreshs' thread and I'm still a little in the dark.
Any help would be appreciated :beer::beer:
Install android sdk, and platform-tools inside it, you'll have latest ADB/fastboot version.
If you type just 'adb' (you may have to reboot or even add it to your path then reboot), it will give you all the adb command parameters, same with fastboot, then it's only a matter of finding further explanation if needed.
If the toolkit fails, you'll have no idea where it failed. Better learn it how Google does it first. This is a Nexus after all.
I think you should read the link below, ADB and fastboot still applies, what might not apply is partition tables, kernels, etc, but you already know that.
http://forum.xda-developers.com/showthread.php?t=1814266
Sent from my Nexus 10 using xda app-developers app
bk201doesntexist said:
If the toolkit fails, you'll have no idea where it failed. Better learn it how Google does it first. This is a Nexus after all.
Click to expand...
Click to collapse
100% this. You will have a far better time later on (and with other devices even) if you learn how to do stuff manually early, via ADB and Fastboot provided by Google. Toolkits do nothing for your knowledge besides hampering it, and there's even talk of some toolkits (I don't know of any for the N10) containing malware.
Would you rather trust your device security with random programs, executables, and very likely un-updated drivers from a complete stranger, or you would trust Google's own tools? :good:
To give a brief setup process with Android SDK, you first need Java SDK installed, then grab Android SDK (either just the basic 21MB installer or the entire ADB developer bundle with eclipse), install it, run SDK Manager, grab Tools (may be already installed), Platform-tools, and Google USB Driver, install Google's USB Driver (via right-click driver inf > Install), add platform-tools folder to PATH (for easy access to adb and fastboot commands), and done You now have the latest binaries and drivers from Google, and now know how to setup a basic Android SDK environment, something a toolkit wouldn't teach you
KEarlier I saw a thread that demonstrated a python wrapper for the adb command. I remembered a while ago that adb uses a TCP protocol (duh it's written in the docs)
I had some spare time today so I decided to write a script for you all (I know how redundant it is, but hey why not)
This script incorporates the core functionality of adb into it, such as detecting your device... that's pretty much it at this stage..
so here it is. PyAdb​
I doubt this will brick anyone's devices... but just in case..
disclaimer:
if this bricks your device, it was not my fault. you used this at your own risk.
I don't care if this crashes your computers, or shoots you in the foot. you used it, not me
Click to expand...
Click to collapse
The general concept with how this works is below:
firstly, you have to choose your command from this list
secondly: the length of that command (in hexadecimal) needs to be prefixed before the command is sent. This is probably to do with security so the adb server on the device only reads the right amount of data
thirdly:... well there's not much more to it. just enjoy, tinker with it, and remember to contribute!!
note about getting device detected:
You need to ensure that the Android Debugging Bridge driver is installed for your device. this is normally supplied with standard device drivers. please refer to your device forums for instructions on how to install these
You also need to make sure your pc is authorised with stock adb, otherwise you won't be able to connect with PyAdb (for 4.2 upwards)
note about the current shell integration:
I now have a threaded interactive console, however single commands are still not read from a thread. If you want to use grep or kmsg, launch a full session
page not found!
Fixed link: https://github.com/cybojenix/PyAdb/
Looks like OP removed the file he linked to and forgot to change the link.
404 page not found?
cybojenix said:
Earlier I saw a thread that demonstrated a python wrapper for the adb command. I remembered a while ago that adb uses a TCP protocol (duh it's written in the docs)
I had some spare time today so I decided to write a script for you all (I know how redundant it is, but hey why not)
This script incorporates the core functionality of adb into it, such as detecting your device... that's pretty much it at this stage..
so here it is. PyAdb​
I doubt this will brick anyone's devices... but just in case..
disclaimer:
The general concept with how this works is below:
firstly, you have to choose your command from this list
secondly: the length of that command (in hexadecimal) needs to be prefixed before the command is sent. This is probably to do with security so the adb server on the device only reads the right amount of data
thirdly:... well there's not much more to it. just enjoy, tinker with it, and remember to contribute!!
note about getting device detected:
You need to ensure that the Android Debugging Bridge driver is installed for your device. this is normally supplied with standard device drivers. please refer to your device forums for instructions on how to install these
note about the current shell integration:
I haven't added a threaded data capture method yet, purely because I don't have time at the moment. it will (should) work with single commands. it isn't reliable for commands that take a while to run (such as grep)
Click to expand...
Click to collapse
404 page not found?
omegavesko said:
Fixed link: https://github.com/cybojenix/PyAdb/
Looks like OP removed the file he linked to and forgot to change the link.
Click to expand...
Click to collapse
lol yeah thanks. I did some file changes and forgot I linked to the file in the thread rather than the repo
Ok Devs-
(ALSO sync owners, don't update your sync systems anymore by ford, we are getting close to unlock it, and they will put out updates to bork our hack).
I need some help please. I need to modify this POS sync. You can't do anything with it. I want to get navigation running or bluestacks to run android.
I got the official ford , usb reboot file I have attached it here. It has the signed files that we need.
I was able to tigger the install event with those files. And I believe this is our key to Jailbreak the system.
The best part is that you can run stacked commands on those install scripts. https://www.coalfire.com/The-Coalfire-Blog/October-2014-(1)/Reverse-Shells-and-Your-Car?feed=blogs
I have been struggling to get it it to execute, presumably, I don't know anything about win CE.
I have the win CE cmd.exe on my usb. Place it into the system, it recognizes and initiates upload. What the code below is trying to do is piggy back on the copy via stacked code to upload cmd.exe to the system then execute it. UNless there is another way to get a shell, once we get the shell, WE OWN THEM.
This is what my path is listed on my autoinstall.1st file -
Open1 = DelayedReboot.cab; cmd.exe \tmp\cmd.exe; \tmp\cmd.exe
the cab is required as it is signed by microsoft and bypasses the lock to load additional code.
Changing the semi colon to & makes it error out, so the semi colon is correct, just dunno if I have the paths right. Normally, it would be something like for linux /fs/usb0/etc...... but I am not sure about CE lists the usb device path...again I am win CE retarded. UNless there is a way to % to the paths, but I dunno much about win.
Sync, recognizes and executes with no errors. If I change my code a little, it will not work and say error.
SO what am I missing to get the cmd to run? Or is it already? I was expecting a shell to pop up?
If someone can point me in the right direction, or to point what file I can call to execute the onboard navigation, that would be awesome as well.
Even if we can't get a shell, I'd like to be able to execute a file, then I can run MIOpocket on this thing and ditch sync for android apps.
I have also attached the sync app developer guide link. With programming commands for apps.
https://developer.ford.com/uploads/DevConf%20-%20Track%205%20-%20Best%20Practices.pdf
Here is a link to the windows 7 automotive guide on how the system operates, kernel info, driver info, and stuff.
http://download.microsoft.com/download/0/A/1/0A1E07D6-7562-4566-AACF-E04DF4FF8879/A%20Technical%20Companion%20to%20Windows%20Embedded%20Automotive%207%20(final).pdf
UPDATE: 04/19/2015 -
While it is not a software hack, IT IS possible to unlock the navigation only portion of the MFT 8", if you have it without nav.
IF YOU DO THIS, YOUR CAR WARRANTY IS VOID. You've been warned.
It will cost a little money, but not set you back $1000 like nav tv and lockpick are charging. Maybe $100 or so.
Here is what you need to do, if you can't wait for us to unlock the bootloader.....
1 - Get a used APIM only part with the numbers DS7T in it. (aluminum only part with the fins, you DO NOT need the screen)
2 - Get the VIN# of the car it came out of and check the VIN to see if it was enabled with factory NAV. There are internet sites that will check the VIN for you. Must be a unit with NAV enabled.
http://researchmaniacs.com/VIN-Number-Lookup/WindowSticker/Ford.html
3. Install the APIM only to the back of your LCD.
4. The system will reboot and reset.
5. The system will them ask you to insert the NAV sd card, do that. (obviously, you have to buy a nav card from ebay as well, but those are $10)
6. Enjoy factory NAV for about $100
This is the only workaround for now. THE APIM is separate from the sync system and only interfaces with it. So, you will retain all your OEM VIN# locked stuff and it will survive reboots and updates. The nac actually just unlocks on that APIM portion, believe it or not. This method doesn't tie into the file system software, it merely accesses it.
Now.... if someone would be so kind as to just rip the NAND chip from one of those units and post it, so that we can just flash over our existing equipment, we can do this for FREE!!!!!!
Still working on the video bypass.... It would be nice if our Russian friends can start chiming in for that one please.....
DON"T FALL FOR THE EBAY GUY CHARGING $600 to $700 for this. Let's put him out of business.... Your help is needed.
PROPS TO rahrena8690 for the find.
WORKING FILE LINKS - FOR DEVELOPERS ONLY
Delayed Reboot project
https://mega.co.nz/#!m0BEWSrA!qrdgIRYTvccH52794ktdpRfrulI_pSdY3g-iiCyhaFs
awesome work
kthejoker20 said:
Ok Devs-
(ALSO sync owners, don't update your sync systems anymore by ford, we are getting close to unlock it, and they will put out updates to bork our hack).
I need some help please. I need to modify this POS sync. You can't do anything with it. I want to get navigation running or bluestacks to run android.
I got the official ford , usb reboot file I have attached it here. It has the signed files that we need.
I was able to tigger the install event with those files. And I believe this is our key to Jailbreak the system.
The best part is that you can run stacked commands on those install scripts. https://www.coalfire.com/The-Coalfire-Blog/October-2014-(1)/Reverse-Shells-and-Your-Car?feed=blogs
I have been struggling to get it it to execute, presumably, I don't know anything about win CE.
I have the win CE cmd.exe on my usb. Place it into the system, it recognizes and initiates upload. What the code below is trying to do is piggy back on the copy via stacked code to upload cmd.exe to the system then execute it. UNless there is another way to get a shell, once we get the shell, WE OWN THEM.
This is what my path is listed on my autoinstall.1st file -
Open1 = DelayedReboot.cab; cmd.exe \tmp\cmd.exe; \tmp\cmd.exe
the cab is required as it is signed by microsoft and bypasses the lock to load additional code.
Changing the semi colon to & makes it error out, so the semi colon is correct, just dunno if I have the paths right. Normally, it would be something like for linux /fs/usb0/etc...... but I am not sure about CE lists the usb device path...again I am win CE retarded. UNless there is a way to % to the paths, but I dunno much about win.
Sync, recognizes and executes with no errors. If I change my code a little, it will not work and say error.
SO what am I missing to get the cmd to run? Or is it already? I was expecting a shell to pop up?
If someone can point me in the right direction, or to point what file I can call to execute the onboard navigation, that would be awesome as well.
Even if we can't get a shell, I'd like to be able to execute a file, then I can run MIOpocket on this thing and ditch sync for android apps.
I have also attached the sync app developer guide link. With programming commands for apps.
https://developer.ford.com/uploads/DevConf%20-%20Track%205%20-%20Best%20Practices.pdf
Here is a link to the windows 7 automotive guide on how the system operates, kernel info, driver info, and stuff.
http://download.microsoft.com/download/0/A/1/0A1E07D6-7562-4566-AACF-E04DF4FF8879/A%20Technical%20Companion%20to%20Windows%20Embedded%20Automotive%207%20(final).pdf
Click to expand...
Click to collapse
I have been wanting to get into this system since the day I got my truck. All ford has succeeded in doing is piss me off with "updates" that didn't amount to much. I would be happy if they would at least allow applink on the touch systems, as that would at least give us some options to add our own work.
I would love to help, but don't have much experience with "rooting", Windows CE, etc. But looking at what you have so far, I will offer some thoughts that came to mind:
It seems to me that you are working at the bootloader level, not the OS level. I may be way off here, but this could be why cmd won't work, as the OS is not loaded, so a traditional shell is not yet possible.
If you are indeed at the OS level, I wonder since you didn't get any errors when trying to launch cmd, if it was indeed actually running. I know on windows systems, if you manage to launch a process as "system", you typically can't interact with it (security issue). I don't know CE at all, but wonder if PsExec would work if it is launching your exe, but as system...
If it is executing your exe as system, perhaps a script or small app that writes some info about the system to a file on the usb drive would help. IE, have it list the folder structure for example.
I know we are not alone on people wanting to work on this. It looks to me that with Sync 3 dumping MSFT, we may be left in the dust with no further updates, although, this guy has found some signs that it might still get some useful updates:
http://www.reddit.com/r/Ford/comments/2rf2cc/ford_may_announce_updates_to_sync_gen2_myford/
Thanks
kthejoker20 said:
Ok Devs-
(ALSO sync owners, don't update your sync systems anymore by ford, we are getting close to unlock it, and they will put out updates to bork our hack).
I need some help please. I need to modify this POS sync. You can't do anything with it. I want to get navigation running or bluestacks to run android.
I got the official ford , usb reboot file I have attached it here. It has the signed files that we need.
I was able to tigger the install event with those files. And I believe this is our key to Jailbreak the system.
The best part is that you can run stacked commands on those install scripts. https://www.coalfire.com/The-Coalfire-Blog/October-2014-(1)/Reverse-Shells-and-Your-Car?feed=blogs
I have been struggling to get it it to execute, presumably, I don't know anything about win CE.
I have the win CE cmd.exe on my usb. Place it into the system, it recognizes and initiates upload. What the code below is trying to do is piggy back on the copy via stacked code to upload cmd.exe to the system then execute it. UNless there is another way to get a shell, once we get the shell, WE OWN THEM.
This is what my path is listed on my autoinstall.1st file -
Open1 = DelayedReboot.cab; cmd.exe \tmp\cmd.exe; \tmp\cmd.exe
the cab is required as it is signed by microsoft and bypasses the lock to load additional code.
Changing the semi colon to & makes it error out, so the semi colon is correct, just dunno if I have the paths right. Normally, it would be something like for linux /fs/usb0/etc...... but I am not sure about CE lists the usb device path...again I am win CE retarded. UNless there is a way to % to the paths, but I dunno much about win.
Sync, recognizes and executes with no errors. If I change my code a little, it will not work and say error.
SO what am I missing to get the cmd to run? Or is it already? I was expecting a shell to pop up?
If someone can point me in the right direction, or to point what file I can call to execute the onboard navigation, that would be awesome as well.
Even if we can't get a shell, I'd like to be able to execute a file, then I can run MIOpocket on this thing and ditch sync for android apps.
I have also attached the sync app developer guide link. With programming commands for apps.
https://developer.ford.com/uploads/DevConf%20-%20Track%205%20-%20Best%20Practices.pdf
Here is a link to the windows 7 automotive guide on how the system operates, kernel info, driver info, and stuff.
http://download.microsoft.com/download/0/A/1/0A1E07D6-7562-4566-AACF-E04DF4FF8879/A%20Technical%20Companion%20to%20Windows%20Embedded%20Automotive%207%20(final).pdf
Click to expand...
Click to collapse
Thanks Pro. any new updates. Actually i just purchase Lincoln MKZ 2014, although i know it is hardware capable to run navigation since i get latitude and longitude, but unfortunately no navigation from the factory. i just play with My Lincoln Touch and on the sittings there is a tab for installing apps. so can we install and windows CE app?
Nothing yet.
Sync updates are rolled out every 6 months.
Rumor was that we are all getting blackberry upgrade from Microsoft.
Update is expected Feb 2015 or so.
We are sitting on the sidelines waiting to see what Ford will do, before we start porting over. There may be no need for our work if we get port link to the new system. I think Ford is on our side, as they don't want us open sourcing the system and have to deal with warranty claims.
kthejoker20 said:
Nothing yet.
Sync updates are rolled out every 6 months.
Rumor was that we are all getting blackberry upgrade from Microsoft.
Update is expected Feb 2015 or so.
We are sitting on the sidelines waiting to see what Ford will do, before we start porting over. There may be no need for our work if we get port link to the new system. I think Ford is on our side, as they don't want us open sourcing the system and have to deal with warranty claims.
Click to expand...
Click to collapse
i don't think so. we will not get the QNX update. I think it is a different system with different architecture and requirements. but i hope they unlock the FMT or LMT so we can install any windows ce app.
Please don't reply to this thread with comments or requests.
I'd like to keep it clean to only development comments.
Based on what I'm reading around the page 26 mark (bootloaders section of the windows embedded 7 pdf), it sounds like we need to attempt to give the IPL boot arguments to get into update or development mode and from there we could have a chance of pushing our own files. I would think update mode looks for a signature but dev mode might let anything in.
Way ahead if you. The attached file has the signature. I was able to successfully run stacked commands by modifying the attached reboot file. Problem, the command doesn't stick on reboot.
kthejoker20 said:
Way ahead if you. The attached file has the signature. I was able to successfully run stacked commands by modifying the attached reboot file. Problem, the command doesn't stick on reboot.
Click to expand...
Click to collapse
So you were able to launch a command prompt via the delayed reboot zip? I wonder if it would be possible to hack a sync update and then use this to push it.
I need a zip please... I can induce an update no command prompt yet
I can only run commands stacked, but I need to run a script on the sync side, but I can't figure out how to push the script to the sync
kthejoker20 said:
I need a zip please... I can induce an update no command prompt yet
I can only run commands stacked, but I need to run a script on the sync side, but I can't figure out how to push the script to the sync
Click to expand...
Click to collapse
This the latest myford touch update Gen2-V3.7.11
http://www.mediafire.com/?79v3d0d8972sy44
Here is the Delayed Reboot zip
http://outofmytouch.com/assets/delayed_reboot.zip
So some very quick looking tonight and I found EA5T-14D546-ATD contains the master patch. Decompiling some of the shockwave files I have found some interesting code. These would most likely be the files to hack to change factory behavior. Getting them flashed to a vehicle might be a whole other issue though.
Edit: After more browsing I think we need to target a master patch for an older version of Sync. I was looking at the master patch for the most current so there are going to be less files patched. I will have a peek at those later.
For some reason, the coalfire site took down it's information regarding the reverse shell of the infotainment system.
Here is what I am talking about with the command on the delayed reboot file. I have conveniently located the stacked command image and attached it for your viewing pleasure.
If we can patch the files, this is how we push them to the chip. Otherwise, I may have to PHYSICALLY pull the system files through JTAG tap... sigh... not really wanting to do that though...
If we can push them, we would have to unlock the bootloader to bypass the sigs... This is where my brain is staring to hurt....
Obviously, these commands do not apply to what we are doing, as that is QNX. Plus, I don't want any noobs spunking their system with our fashizzle yet...until we test it.
Just a final thought, as a plan B, we could reverse shell with the USB exploit as well... just saying.. might be easier
An integer overflow might work as well, but I have never experiemented on an embedded chip. Stacked command invoking an integer overflow, might give us write access to the system.
Has any thought gone into rewriting one of the dll's included in the latest patch to include some sort of backdoor? It seems it'd be easy (maybe I'm missing something here) to just modify the latest patch's install files to install our new dll.
I haven't had time yet, but I am going to try to USB otg pull.... I'm sure I can probably at least disable the vss lock.
kthejoker20 said:
I haven't had time yet, but I am going to try to USB otg pull.... I'm sure I can probably at least disable the vss lock.
Click to expand...
Click to collapse
When you tried running the cmd prompt with the stacked command approach did get any indications of the program running? I was thinking about adding some arguments to the end of the command to write a random file to the root of an available drive (like you said, who knows how the thumb drive is recognized).
Also, what type of processor does the system run on?
---------- Post added at 11:51 PM ---------- Previous post was at 11:30 PM ----------
duckboy81 said:
When you tried running the cmd prompt with the stacked command approach did get any indications of the program running? I was thinking about adding some arguments to the end of the command to write a random file to the root of an available drive (like you said, who knows how the thumb drive is recognized).
Also, what type of processor does the system run on?
Click to expand...
Click to collapse
I think I answered one of the questions. From the PDF you posted "A Technical Companion..." it's a Freescale IMX35 processor.
freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX35_FAMILY&cof=0&am=0
Looking forward to following the progress of this thread! I hope that you all will discover a new solution to our these outdated systems! Good luck guys, I am rooting for you!
duckboy81 said:
When you tried running the cmd prompt with the stacked command approach did get any indications of the program running? I was thinking about adding some arguments to the end of the command to write a random file to the root of an available drive (like you said, who knows how the thumb drive is recognized).
Also, what type of processor does the system run on?
---------- Post added at 11:51 PM ---------- Previous post was at 11:30 PM ----------
I think I answered one of the questions. From the PDF you posted "A Technical Companion..." it's a Freescale IMX35 processor.
freescale.com/webapp/sps/site/taxonomy.jsp?code=IMX35_FAMILY&cof=0&am=0
Click to expand...
Click to collapse
Actually I am pretty sure the MyFord Touch processor is an I.MX51 acccording to a Ford PDF I found. Unfortunately I am new to posting here and it won't let me post links.
I work on the almost identical I.MX53 processor at work doing Linux kernel, u-boot boot loader, and Linux application software, so I might be able to help.
Most of the I.MX processors have built in ROM code that allows booting to a USB or Serial downloaded mode. This allows loading any software you want into any RAM address and then booting from it. Then you run completely out of RAM (like a live CD). Depending on how Ford setup the I.MX51 e-fuse settings, there may be an external pin that could be used to enter this serial downloaded mode. Freescale provides a tool called the MfgTool to load software using the serial download mode. Then you could load Linux, Android, or whatever. The e-fuses also allow you to lock out JTAG, serial downloaded mode, and enable boot time signature checking, but I am not sure if Ford used any of these to lock the system down.
Do we know where the processor is located in the fusion?
I just got my Moto X Play and wanted to root it and flash CM13. I installed the Google USB Drivers to get Windows to recognize the ADB interface, and getting into fastboot mode with ADB works just fine. But once there, "fastboot devices" fails to recognize the device. The device manager shows an unrecognized device "Fastboot lux S" for which the google USB drivers don't work. I've read that this should be fixed by installing the official Motorola drivers, but I would like to avoid that if possible - I'm doing this to get rid of the Motorola crap, installing more of it on my PC to do so would be disappointing.
So, I've got a heap of questions:
- Can I use fastboot on Win7 without installing Motorola-specific drivers? It seems that there should be a generic driver for the fastboot interface as it's a feature on all modern android devices AFAIK.
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
- Does my objection to the Motorola Drivers make sense? Are there any benefits to having the drivers installed if I flash CM on the device?
The drivers are irrelevant to the OS you want. You need the drivers, install the drivers. Your computer is trying to talk to the phone, and right now they are speaking different languages, the driver is an instruction on how to talk to the phone. It has very little to do with Motorola, google didn't build your phone, they supplied the OS. Fastboot is effectively the BIOS of your phone, imagine what would happen if you flashed the wrong BIOS on your computer., would you call Microsoft and say fix it? no.
Install the damn drivers and get over it.
ImWarped said:
It has very little to do with Motorola ...
Click to expand...
Click to collapse
That's exactly why I asked, I thought this was a standartized part of Android for which there might be a generic Windows driver - I guess that's not the case, thanks for the clarification. But I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.
fckmoto said:
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
Click to expand...
Click to collapse
fckmoto said:
I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.
Click to expand...
Click to collapse
Since my wife moved to an Android phone, our house is Microsoft free. Being a fairly novice user who likes to tinker, this always introduces extra layers of doubt and uncertainty ...even fear, at times. I am forced to wonder, in the presence of all the Windows software and Windows-based procedures and advice, does it work on Linux?
My answer, so far, over three phones, is that if it is adb or fastboot stuff, then, yes it does. Or, at least, so far, everything I've tried works.
Depending on your linux distro, you might have to install some extra package containing those commands. You might want to install the whole Google android package. 99.999% developer stuff, but includes the two commands that you want. It's probably more up-to-date than the Linux-distro versions.
You might have to insert a line with some manufacturer ID (I didn't for the X Play) in some configuration file.
Look... my anti-MS biases show even through a thick overcoat. But do the linux thing only if you want to do linux. By the time you've read this post, you could probably have installed those drivers .
Does my objection to the Motorola Drivers make sense?
Click to expand...
Click to collapse
No.
Thad E Ginathom said:
No.
Click to expand...
Click to collapse
Heh, I guess it's somewhat thick-headed to look for alternatives instead of just installing the drivers. My main problem with that is that Motorola doesn't offer a direct download of the driver but wants me to install a driver manager tool instead... I've kept my pc crapware-free thus far and intend to keep it that way If it's as simple as installing a few Android dev packages under Linux, I'll definitely take that route.
But with bash and the full Canonical repositories coming to Win10, maybe one could use the Linux adb and fastboot binaries under Windows in the not-so-far future... I wonder if those would then work without a device driver
Install 15 seconds adb 1.4.3 and run it in your fastboot folder you create in C of Windows7, no Motorola drivers.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118