Develop Bugs

[PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available)

What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices.
How does it work?
Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in Heimdall is handled by the popular open-source USB library, libusb-1.0.
Why “Heimdall”?
The flashing software Odin is named after the king of gods in Norse mythology. Loke, the software component on the Galaxy S that provides functionality to flash, may also to be named after an important character in Norse mythology, often translated as Loki. As such I have named my flashing software Heimdall, after the Norse god, and guardian of the Bifrost Bridge.
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Why use Heimdall when we can use Odin?
Odin is generally unreliable and only runs on Windows systems. Furthermore, Odin is leaked Samsung software that is not freely available or well understood by the community.
Is Heimdall safe?
No matter what method you chose, flashing firmware onto your phone has a lot of potential for disaster. We have tested Heimdall with a variety of phones flashing several different firmware versions resulting in a 100% success rate. As such we believe that Heimdall is generally reliable. However keep in mind, just like any flashing software, Heimdall has the potential to brick your phone if not used correctly.
How do Galaxy S phones get bricked when flashing?
Besides the inherent risks like power outs, accidental removal of the USB cable etc. The Galaxy S appears to be running extremely unreliable USB control software.
A failure to flash does not automatically equate to a bricked phone. However if you're extremely unlucky and the flash fails whilst transferring the primary boot-loader, secondary boot-loader or params.lfs (all quite small) than you've got yourself a paper weight that you're hoping Samsung will replace.
Please be extremely careful mixing files from different firmware releases. Don't do so unless you're certain it will work!
What Galaxy S variants has Heimdall been tested with?
We’ve tested Heimdall with a Galaxy S GT-I9000 (8 GB) from the United Kingdom and Galaxy S GT-I9000 (16 GB) from Australia. We don’t personally have access to any other devices to test with, however users have confirmed Heimdall functions correctly with the AT&T Captivate, Bell Vibrant, Telstra GT-I9000T, Epic 4G and the Galaxy Tab.
Enough talk, where can we get it?
The latest release is available here. Please read the instructions and README files included in the archives.
I love you, man. Will you have my baby?
No, but I will very gladly accept donations. If you appreciate my work and would like to support future development you can make a donation here. If you think you have something else to offer, then feel free to shoot me a PM or contact me via the contact form on the Glass Echidna website.

Sounds interesting.. Certainly something to watch in the future..

for linux? YES! i love u

Kudos for you! wow it looks impressive
A question though....
the instructions seems to be very... Windows oriented.
What about Linux or MAC OS?
Do we need to run it with WINE, or just run it as a DOS executable?
same question for MAC OS, you know people in MAC are so used to plug and play, If i were a MAC user i'll just plug my phone in, and expect to run Heimdall by click on it and have it come up.
However at the moment it seems to require Windows emulation for it to run.

Thanks guys.
Also, I forgot to add in the README that you also need the same PIT file as the one that is installed on your device, probably version 512.
I can see by my website's bandwidth usage that people have been downloading the alpha. Has anyone tested it yet?

AllGamer said:
the instructions seems to be very... Windows oriented.
What about Linux or MAC OS?
Do we need to run it with WINE, or just run it as a DOS executable?
same question for MAC OS, you know people in MAC are so used to plug and play, If i were a MAC user i'll just plug my phone in, and expect to run Heimdall by click on it and have it come up.
However at the moment it seems to require Windows emulation for it to run.
Click to expand...
Click to collapse
The alpha release is just the Windows binaries. Whilst the source code certainly compiles for OS X and Linux I want to make sure that everything is running fine on Windows first, with Odin nearby if need be.

Benjamin Dobell said:
The alpha release is just the Windows binaries. Whilst the source code certainly compiles for OS X and Linux I want to make sure that everything is running fine on Windows first, with Odin nearby if need be.
Click to expand...
Click to collapse
ahh, Good to know, i was worried there for a second
I can't test it yet, my phone hasn't come back from repair.
i'll help test as soon as my phone is back.

go public linux binary too, else ppl will use odin instead your and you wont receive much feeback as much as if you release linux binaries.

husq510 said:
go public linux binary too, else ppl will use odin instead your and you wont receive much feeback as much as if you release linux binaries.
Click to expand...
Click to collapse
I know it's a pain that Linux users have to wait (as usual). As much as I do want feedback, I don't want feedback from Linux users saying that the flash failed for some reason and that they don't have access to Windows/Odin.
I'm not actually sure if I'll ever release Linux binaries as binary compatibility across multiple Linux distributions is problematic. Of course once I've confirmed everything is working on other peoples' devices, what phone models are supported etc. then I will release the source code with instructions to compile for all supported platforms.
EDIT: Has Heimdall really been downloaded ~45 and no-one has bothered to install and run it?

I'm having trouble with the following step:
4. Under Universal Serial Bus Controllers right click on the Samsung composite driver and chose Properties.
I don't have such device in device manager.
Windows 7 x86

very cool stuff, thank you a lot!!!
first of all. i am a linux only user and had to run odin on a virtual box which is a pain in the ass but i fully understand your argument to first only release a windoze version to get it out of alpha state.
now, while i know that it's also possible to brick the device with odin and i have flashed several times now. i am a little afraid to try heimdall (to be honest). did you implement the additional security measures (delay+resend) after you bricked your device or before? you wrote that heimdall supports only full firmware flashes atm. it would be cool if we could also use it to just flash a kernel. any plans to implement this?
thanks!

mike.sw said:
I'm having trouble with the following step:
4. Under Universal Serial Bus Controllers right click on the Samsung composite driver and chose Properties.
I don't have such device in device manager.
Windows 7 x86
Click to expand...
Click to collapse
Is your device plugged in to your PC and in download mode?
I suppose you would also have needed to install Kies at some stage. However, Odin makes use of this driver so if Odin works it should be there.

Oh god, I'm an idiot.
Connected phone to wall charger, and was sure it's my USB cable.... *facepalm*

jodue said:
very cool stuff, thank you a lot!!!
first of all. i am a linux only user and had to run odin on a virtual box which is a pain in the ass but i fully understand your argument to first only release a windoze version to get it out of alpha state.
now, while i know that it's also possible to brick the device with odin and i have flashed several times now. i am a little afraid to try heimdall (to be honest). did you implement the additional security measures (delay+resend) after you bricked your device or before? you wrote that heimdall supports only full firmware flashes atm. it would be cool if we could also use it to just flash a kernel. any plans to implement this?
thanks!
Click to expand...
Click to collapse
I implemented the delay and resend after my phone was bricked.
I think I was ludicrously unlucky in how my phone got bricked. Given that the primary boot loader is only 256 KiBs whilst the factory filesystem is over 250 MiB (plus other files). The chance of failing whilst the primary or secondary boot loader is being sent is quite slim.
When I was debugging Heimdall I would often intentionally stop at other points during the flash. After resetting it would just result in the connect phone to PC image being displayed (instead of booting). Then I could just restore with Odin (after several attempts) and then further restore using ClockworkMod backups.
However, by no means do I want to pressure anyone into running the software, especially whilst it's only an alpha release.
EDIT: I just realised I didn't answer your question about just kernel flashing. Yes, I definitely intend to implement functionality to only flash singular components at a time. I'd also like to implement functionality to dump files if possible. However I won't know if I can do that until I get my phone repaired or get my hands on another Galaxy S device.

Hey again
I'm looking the flash.bat and see it need two files that my firmware (I9000JPJG8) don't have in zip/tar file:
-boot boot.bin -sbl Sbl.bin
How heimdall will handle it? Is it safe to go on?

mike.sw said:
Hey again
I'm looking the flash.bat and see it need two files that my firmware (I9000JPJG8) don't have in zip/tar file:
-boot boot.bin -sbl Sbl.bin
How heimdall will handle it? Is it safe to go on?
Click to expand...
Click to collapse
Heimdall won't let you continue as the first thing it does (before connecting to your phone) is check that the specified files exist. Those two files are the primary boot loader and the secondary boot loader. I'm a bit surprised they're missing from your firmware. They're usually in the Code tar archive.
You'll have to grab them from somewhere. If you don't want to download more firmware then you can retrieve them from your device. Err, I'll update this post in a minute or two with instructions.

This is one little tricky FW.
The last one I tried was I9000XWJM5 and it had 3 tar files as supposed.
This one just have one tar file, and people who installed it with Odin said to use only the PDA section with the single tar file.
I'm not sure, but it seem to work for them.
BTW in your README I think you should remind for the folks to put the pit file in the dir as well
Also here in WIN7 it didn't let me change the driver as simply as stated in README.
What I had to do is to use the Have Disk option, and point it to the dir. Otherwise it says that Windows already have the correct driver installed.

mike.sw said:
This is one little tricky FW.
The last one I tried was I9000XWJM5 and it had 3 tar files as supposed.
This one just have one tar file, and people who installed it with Odin said to use only the PDA section with the single tar file.
Click to expand...
Click to collapse
If you still have I9000XWJM5 laying around you could give that a go, it is the firmware I use.
If not you can get the boot loaders by copying them first to your sdcard using:
Code:
sudo dd if=/dev/block/bml1 of=/sdcard/boot.bin
sudo dd if=/dev/block/bml4 of=/sdcard/Sbl.bin
Clearly your phone needs to be rooted to use sudo.
EDIT: I need to go to bed now (it's actually well and truly morning here). I'll be on in 5-6 hours if you require any more help. Thanks for going to all this effort so far!

Yea, I'll grab JM5 again just in case the **** hits the fan

Benjamin Dobell said:
I implemented the delay and resend after my phone was bricked.
I think I was ludicrously unlucky in how my phone got bricked. Given that the primary boot loader is only 256 KiBs whilst the factory filesystem is over 250 MiB (plus other files). The chance of failing whilst the primary or secondary boot loader is being sent is quite slim.
When I was debugging Heimdall I would often intentionally stop at other points during the flash. After resetting it would just result in the connect phone to PC image being displayed (instead of booting). Then I could just restore with Odin (after several attempts) and then further restore using ClockworkMod backups.
However, by no means do I want to pressure anyone into running the software, especially whilst it's only an alpha release.
EDIT: I just realised I didn't answer your question about just kernel flashing. Yes, I definitely intend to implement functionality to only flash singular components at a time. I'd also like to implement functionality to dump files if possible. However I won't know if I can do that until I get my phone repaired or get my hands on another Galaxy S device.
Click to expand...
Click to collapse
thank you for the additional information on the process. i think i will give it a shot next time i want to flash a new firmware. donation is on the way!

[Windows Phone Utility]Rapi Communications

Program to communicate between the PC <-> Device WP7.The application supporting the connection to the device.
It works on the principle of RAPI communications. He pulled out of the Zune Program
Info:
Description of the product: Windows Phone RAPI Communication Service EXE
Product Name: Zune
Product Version: 4.7.109
Usage:
Waiting....
Files in Attachmend

How to Use?Demo?

Is there any way to access phone without Zune drivers or Zune software installed using this application? Clicking on the EXE doesn't do anything.

thesecondsfade said:
Is there any way to access phone without Zune drivers or Zune software installed using this application? Clicking on the EXE doesn't do anything.
Click to expand...
Click to collapse
have any idea what the communication RAPI?
See this: RAPI in MS

Nokser said:
have any idea what the communication RAPI?
See this: RAPI in MS
Click to expand...
Click to collapse
But how does this package fit into that? This looks like perhaps a way to get native debugging working, but I don't see what to do with this.
You haven't provided any information about what it does--the program just quits regardless of zune state or WP-device connected state. What does it do? Through what means is someone to interact with it? I don't know too much about how RAPI worked on Windows Mobile, but there isn't any indication of how to use /this/ in the article you linked.

davux said:
But how does this package fit into that? This looks like perhaps a way to get native debugging working, but I don't see what to do with this.
You haven't provided any information about what it does--the program just quits regardless of zune state or WP-device connected state. What does it do? Through what means is someone to interact with it? I don't know too much about how RAPI worked on Windows Mobile, but there isn't any indication of how to use /this/ in the article you linked.
Click to expand...
Click to collapse
I give to more info... but not now my friend

[This is a reverse engineering effort in progress. Your mileage may vary and information below could be completely inaccurate. Proceed at your own risk.]
It's a Windows service. Copy it somewhere handy, and issue the command (editing the path as necessary). NOTE: The spaces are required.
Sadly, I don't recall retail phones having RAPI bits, so doubt this will be useful. I'll have another look at the filesystem though.
Update: Judging by the way this executable behaves, it's likely meant to replace WMZuneComm.exe.
Update 2: Because of the reliance on Zune libraries (e.g. ZuneSA.dll), this is for 32-bit Zune users.
Update 3: Listens on localhost, port 64694
These are old binaries from old Zune client software. Retail devices don't have RAPI bits (verified via samsung ffus), therefore this is useless. Silly original poster.

WithinRafael said:
[This is a reverse engineering effort in progress. Your mileage may vary and information below could be completely inaccurate. Proceed at your own risk.]
It's a Windows service. Copy it somewhere handy, and issue the command (editing the path as necessary). NOTE: The spaces are required.
Sadly, I don't recall retail phones having RAPI bits, so doubt this will be useful. I'll have another look at the filesystem though.
Update: Judging by the way this executable behaves, it's likely meant to replace WMZuneComm.exe.
Update 2: Because of the reliance on Zune libraries (e.g. ZuneSA.dll), this is for 32-bit Zune users.
Update 3: Listens on localhost, port 64694
These are old binaries from old Zune client software. Retail devices don't have RAPI bits (verified via samsung ffus), therefore this is useless. Silly original poster.
Click to expand...
Click to collapse
You do not have right to end because of ... Each distributed system WP7, has the shell RAPI applications and libraries.

You can't just dust off old Zune files from 2009 and magically connect this to a phone. Get real.

How to use Bitpim with the Kin 2(tutorial)

I have seen many people asking about bitpim and the kin phones and many with no solutions or answers to their questions. It IS possible to use bitpim to view the file system with these devices. I haven't seen any tutorials on how to do it so I've decided to post a step by step guide.
The things you will need:
Kin Two or Kin TwoM(I have not been able to test this on a Kin One or OneM)
A micro usb data cable
Bitpim
Drivers for the Kin available below
http://rapidshare.com/files/439206164/KinPixiPreCentroTreo800w_etc_DiagDrivers.zip
Don't worry about fixing the error in the qcser.inf, since I have already done this for you.
I would like to thank jennydevil for reminding us that these drivers are for 32-bit not 64-bit operating systems.
Step 1
On your kin device go to the phone application. Once there dial ##77647266488 and call. It will ask you for your Service Programming Code. The default code is 000000. You will now be in a menu labeled "SETTINGS". Navigate to OTHER and then swipe to the left. Here you will see PPro, USB Pass-Through, and USB VID Stream. All of these options will be off. You will want to turn USB Pass-Through on.
Step 2
Now connect your phone to your Windows PC. Your pc will try to find a driver called "Pink CDMA diagnostics" and will fail. Fear not. Open the start menu and right click on Computer then Manage. On the menu to the far left click device manager. In other devices you will see the Pink CDMA diagnostics. Right click it and press "Update Driver Software". Click "Browse My Computer for Driver Software". Browse for the location of the drivers downloaded earlier and click next. It will show a warning that the drivers are not signed. Continue anyways.
Step 3
Now you are ready to open up bitpim. Set it to the same COM as the phone and make sure in the View menu that View Filesystem is checked. Now feel free to browse through the file system of your kin.
If you run in to any problems feel free to ask questions. If you have any ideas or information to make this tutorial more useful feel free to speak your mind.

Fantastic!!
This is a great start to making our kin experience much better! Thank you, and keep up the solid work! Your friends at Microsoft Kin Forums thank you aswell! Check our sites for updates that could help, and together we can make KIN the phone it truely can be!
social.answers.microsoft.com/Forums/en-US/pmxphone/threads
link to MS kin forums (gotta add http)

Thank you for putting the tutorial together (and posting the pre-fixed drivers)! In case anyone else runs into the same hiccup I did - the drivers are for 32-bit OS, not 64-bit OS. Once I used the right system, the drivers and BitPim worked like a champ.
Thanks again!

I can see filesystem
Hey thanks, I can see the filesystem, I think? It says nothing is detected when I manually set the phone. I cannot "get phone data" but can read the filesystem.
.efs_private
CGPS_ME
CGPS_PE
DMU
...etc
But what does this all mean? Can I access ringtones/sounds to edit the list? Please all I want is to add and delete ringtones! Ugh why is this so difficult. Anybody know how to do this?

sabernat said:
Hey thanks, I can see the filesystem, I think? It says nothing is detected when I manually set the phone. I cannot "get phone data" but can read the filesystem.
.efs_private
CGPS_ME
CGPS_PE
DMU
...etc
But what does this all mean? Can I access ringtones/sounds to edit the list? Please all I want is to add and delete ringtones! Ugh why is this so difficult. Anybody know how to do this?
Click to expand...
Click to collapse
No at the moment you can't do that with BitPim but you can email a ringtone to your phone.

Help in step two
Can not find driver location on Windows Vista. I can get to Windows32 file/ then to driver file but new downloaded drivers as in step two.
Thanks

Ah ok, dang. Problem is...Kin has no function to delete ringtones. So once its on, its on forever. I just can't commit to that.

Moved to KIN two forum and stickied.
Also, fix the rapidshare link, the file seems to be unavailable.

jekikeyes said:
Can not find driver location on Windows Vista. I can get to Windows32 file/ then to driver file but new downloaded drivers as in step two.
Thanks
Click to expand...
Click to collapse
Download the drivers extract them somewhere like a folder on your desktop. Let's call the folder kindrivers. Then when you are browsing to the files you would go to C: (or the drive vista is located on)/Users/Yourusername/desktop/kindrivers
Hope that helps.

Any chance we'll be able to get 64-bit drivers soon?

activesack said:
Any chance we'll be able to get 64-bit drivers soon?
Click to expand...
Click to collapse
Not unless someone wants to take the time to write them.

After trying it myself I am not convinced that "we" are seeing anything. It states no phone is connected. There are no signs that I see anything from the phone. Keep trying and keep posting.

dezgrz said:
Not unless someone wants to take the time to write them.
Click to expand...
Click to collapse
someone please do

Kin_Two 2
I am at a lost, I did all the steps, plus the driver download. Everything went fine. I can see what port the phone is using, and have it set on bitpim. When I go to detect the phone on bitpim, it can not find the phone. Have tried on two different computers and can not get it to work. Bitpim can not find the phone, any thoughts?
Ron

phoneinu said:
I am at a lost, I did all the steps, plus the driver download. Everything went fine. I can see what port the phone is using, and have it set on bitpim. When I go to detect the phone on bitpim, it can not find the phone. Have tried on two different computers and can not get it to work. Bitpim can not find the phone, any thoughts?
Ron
Click to expand...
Click to collapse
Bitpim won't find the phone you have to manually set it to the correct COMM port.

I found the com port in device manager. It has been set, but it says it can not still detect phone. When I do go to settings in bitpim, I go to Verzion Wireless, Motorola, and then Kim? Is that correct, there is no Kin just Kim,so is that the same thing?
Ron Fone

phoneinu said:
I found the com port in device manager. It has been set, but it says it can not still detect phone. When I do go to settings in bitpim, I go to Verzion Wireless, Motorola, and then Kim? Is that correct, there is no Kin just Kim,so is that the same thing?
Ron Fone
Click to expand...
Click to collapse
It won't detect it. Just show the file system. Just set it to other cdma.

Hey, I'm about to be forced to get the Kin TwoM (its the best phone on Verizon without a data plan). Has there been any progress on the ROM dumping front? It seems like you would know. Thanks...

Just wanted to post in here saying that I just got myself a Kin TwoM this weekend without knowing anything about it's limitations or potential. I got it working with BitPim using this tutorial, but... yeah, I have no idea what to do now. I'll certainly be watching this board for anything cool that comes of this, though!

Well I have had my Kin Twom for more then a week. I am probably going to return it, its a shame because it is not a bad little phone. Microsoft and Verizon will be the death of this thing. Know what to do about my cell phone?
Ron

Kin 2 nvidia tegra

So I tried to flash android on to the phone using the tegra 250 images when I realized I need the apx series images for android. The thing about that is I can't find them anywhere. Anyone have any idea where a development site for the tegra apx series is? It seems Nvidia has no support for the old series anymore.

how do you upload android to the phone? what program or steps do you do? is there a debug mode or recovery mode? I believe we have to make are own images.

I was using a program provided by nvidia for programming a tegra based development kit. It is capable of flashing android and windows ce 6. If anybody with more experience would like to take a look at the drivers images and program here are the files.
http://tegradeveloper.nvidia.com/tegra/downloads

Don't the images you are looking for have to have drivers for the hardware interfaces specific to this phone?

stetkas said:
Don't the images you are looking for have to have drivers for the hardware interfaces specific to this phone?
Click to expand...
Click to collapse
I wasn't exactly worried about the hardware working as much as getting android onto the tegra and viewing the os. Creating drivers is the easy part.

dezgrz said:
I wasn't exactly worried about the hardware working as much as getting android onto the tegra and viewing the os. Creating drivers is the easy part.
Click to expand...
Click to collapse
Do you think you could write a driver for this.
APX
USB\VID_0955&PID_7416&REV_0103
USB\VID_0955&PID_7416
This VID supposedly belongs to Nvidia. This is the device that is found by Windows if you plug your phone into the usb when it is turned off and then press the u+s+b+power buttons.

I tried the Recovery Mode, like the person described above me, and it came up with the APX device.. So, if someone makes a driver for that, then we might be able to jailbreak it? (iPod Touches and iPhones jailbreak though Recovery Mode). This doesn't seem much diffirent from an iPhone or an iPod Touch.

I found out a driver that we might be able to modify to give us access. I downloaded both the froyo and c36 downloads available from the tegra site that was mentioned earlier. http://tegradeveloper.nvidia.com/tegra/downloads
These file paths could be different if your hard drive has a different drive letter and perhaps also if you have a 64-bit processer, but I found the drivers in the following directories.
C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105\usbpcdriver\NvidiaUsb.inf
C:\Program Files\NVIDIA Corporation\ce6_tegra_250_5265393\os\usbpcdriver\NvidiaUsb.inf
These drivers have the hardware ID in the inf file and so Windows recognizes it and starts to install the driver and finishes, but says there is an error. I'll keep working on it though.

So, the drivers do actually work; it was my computer that was causing the problems, not the drivers. Now that the drivers are installed I think we can use the SDKs provided by Nvidia on the Tegra download page.
If this works, we now have a serious decision to make. Do we try to get android on the phone or do we stick with the Windows CE based os?

mcdietz said:
So, the drivers do actually work; it was my computer that was causing the problems, not the drivers. Now that the drivers are installed I think we can use the SDKs provided by Nvidia on the Tegra download page.
If this works, we now have a serious decision to make. Do we try to get android on the phone or do we stick with the Windows CE based os?
Click to expand...
Click to collapse
Personally, I would rather stick with current OS. Just because I don't want to brick my phone. Maybe have some additions to the current OS? Enable hidden features or something? Customizations? etc?

First off, I wanted to thank everyone who is working on trying to develop an update to improve on the Kin Two. I currently am interested in getting the TWOm when my contract expires but there is a dealbreaker for me, which is that the phone does not alert you when you have a missed call. I know there are other annoying flaws (pointed out in details at the verizon forums by fisharefriends), but this is the only flaw I cannot deal with.
I do not know what is possible of being changed/edited, but I think mcdietz should focus on implementing basic functions that are currently not on the Kin Two phone, but are on other simple lower spec feature phones.

zero2duo said:
First off, I wanted to thank everyone who is working on trying to develop an update to improve on the Kin Two. I currently am interested in getting the TWOm when my contract expires but there is a dealbreaker for me, which is that the phone does not alert you when you have a missed call. I know there are other annoying flaws (pointed out in details at the verizon forums by fisharefriends), but this is the only flaw I cannot deal with.
I do not know what is possible of being changed/edited, but I think mcdietz should focus on implementing basic functions that are currently not on the Kin Two phone, but are on other simple lower spec feature phones.
Click to expand...
Click to collapse
Implementing missing features.. That's a good start. Also, would It be possible to make it be USB device (so you can go into the phone and let's say.. change the default themes).

@mcdietz
Humm, i installed all those downloads long time ago (i guess when posted or before), but didnt tested the drivers with the APX connection.
It worked with errors in linux connection to the usb (got device errors while reading from the USB device) and didnt worked with virtual machine (though vmware detected it).
On the other hand, it worked ok in a win7 real machine and got the driver installed.
I tried to flash android on the device, using the provided images (heh, tests...) and nvflash. But you always get an error on the first try and then, in further attempts you get a "Starting flash" message loop which does nothing.
Same results if you try to do "nvflash --get-partitions" (stuck at 2nd attempt).
You may thing that it's a non working thing, but if you dont connect the device, nvflash.exe it outputs that there is no USB device connected.
A little weird...
I would want to have android at the kin (as i think that has more future than our wince version, looking @ tegra forums) and anyway, if we can somehow read/write the phone roms, we can made a backup from the current OS.

Installed the same tools on linux (native, no emulation) and the flash option didnt worked here either (normal / root user).
Code:
./nvflash --getpartitiontable test.log
outputs (if no phone connected)
Nvflash started
no usb phone found
Click to expand...
Click to collapse
outputs (if Kin on APX connected)
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
in the first attempt. Then if called again, seems to get frozen on "Nvflash started" message.
Maybe the recovery has no way to get that data....

Windows Phone Connector?
has anyone tried using the program WP7 connector for the KIN? it works with the zune hd so why not the KIN?

Mmm just to inform....
This is what (physically) happens when the Kin is on the nvflash attempts. Phone must be just booted (not previous nvflash attempt in this boot).
Code:
PC <- Kin: 80 30 18 16 B9 E8 00 00
PC -> Kin: [1028 bytes of data]
Pc <- Kin: 04 00 00 00
PC -> Kin: [39252 bytes of data]
Seems like the response we get (rcm 0x04000000), and the next writing is done with the device autolocked, so last PC -> Kin fails.
Further attempts do not try the same procedure but directly send the last 39252 packet again, failing and getting stuck.
Using some selfmade software (cause no other works so far), i repeated the same procedure, changing the first "byte pack" to send a lame pack, and this is the output:
Code:
# ./kingateway
Opening the controller
Checking for kernel attaching
Claiming the interface
Reading from the Kin.
Received data. 8 bytes. Content:
80 30 18 16 B9 E8 00 00
Writing [02 01 00 00] to the Kin.
Reading Kin response.
Received data. 4 bytes. Content:
08 00 00 00
Writing again to the Kin
KinGATEWAY:: Error while writing to the KIN. Error Code is -9 EXITING.
So in short, fails again (haha, expected...really), but the second response from the kin is not "0400...00" but "08 00 ... 00" meaning a rcm 0x0800..000 or whatever that means.
The above error ("autolock"), tagged as Error code "9" on the program, is a integrity-defense method from the kin, not for the flashing issue but from the "command sent" over usb, which is wrong or unknown on how to operate, and is called "Endpoint Stall". Is a way to express "You'r doing it wrong and i wont hear you again".
One of my ideas is that this version of nvflash is not what was used to operate with the kin and all we get are not errors or devil's corporation actions but uncompatibility protections.
What we need, from my point of view is the Tegra SDK and/or a document where the responses from an APX device are listed (like 0x04000 is "wrong certificate" and 0x08000 is "certificate too short", etc), so we know what it's telling to us. Maybe it's easier to contact nVidia for "old" SDKs than roms...

i hate to be a party crasher but i think this thread needs to be a bumped? why did this thread randomly die? maybe i'm missing something.

I believe it died because johnkussack doesn't have a working kin right now and I don't believe anyone else here wants to try things that may "brick" their phone (I'm one of them). I'm currently trying to buy another kin two (or, uh two), then I'll definitely be digging deeper into those. I may try a hardware route on one and a software route on the other.
This is definitely the most exciting thread the kin two section of xda!

It's been a while but I now have a working KIN device and can continue my efforts. Using the resume mode command to try and force nvflash to write to the kin it displayed a message that said "writing" and then displayed "Failed to perform the following commands: create". It's been a PITA but I feel I will get something written to the device soon.

dezgrz said:
It's been a while but I now have a working KIN device and can continue my efforts. Using the resume mode command to try and force nvflash to write to the kin it displayed a message that said "writing" and then displayed "Failed to perform the following commands: create". It's been a PITA but I feel I will get something written to the device soon.
Click to expand...
Click to collapse
before doing what i lastly underlined, considering what i underlined first... i suggest that you do the reading part, relating to the partition listing.
Just a safe way to find out if the experiments work. Then you can write... with a bit of safety on your side. I mean... you know that testing things writing could not be the best idea on the brikings

WP7 Unlocking, Sideloading etc. Problems and Solutions

Now, I know no-one actually likes reading threads, and would prefer to just post a new question at the end (I'm guessing partly because the threads are so long, but that's because everyone is doing it) so I'm going to try and give solutions to as many of the issues with ChevronWP7, sideloading and anything else that's not quite working.
Note, none of this is to facilitate any kind of software pirating (we will notice if it gets discussed, and it's in the forum rules - and kinda immoral).
Firstly, Windows Vista (I think SP2) or Windows 7 is required, this won't work on XP without a few hacks/tweaks, and it's not worth me writing the whole process out, plus I don't have an XP machine to hand, so I can't try things.
The most common issues can be fixed with just installing the correct software.
You NEED to have the official WP7 Developer Tools installed, they're a free download from Microsoft, and if you're planning on doing development (which is after all part of the reason for wanting sideloading) you kind of need them.
There's a guide on how to install them (provided by Microsoft) here. You only need the basic toolset from here, but installing the October update won't cause any issues.
This should solve the following exception:
Code:
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SmartDevice.Connectivity, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
as well as a few other issues.
When running any of the tools, if you encounter issues, try either running the tool as an administrator or turn of UAC (for both, do a search if you've no idea what I'm on about), this may solve some issues with access rights etc.
Once you've got that installed, Chevron issues are in post #2, sideloading XAPs in #3.

ChevronWP7 Issues
With Chevron, most things are explained well in the opening post of this thread. Read it.
Chevron works by tricking your phone into thinking it's communicating with Microsoft servers, when it's actually just communicating with Chevron, this means certain web based activities may interfere (Skype for example).
The best way of finding out what's going on, is to use the following guide, it should work, if that fails, then post a question.
sushovande said:
Okay so here is *everything* I did to succeed in re-unlocking my Samsung Focus
1. Have Winphone developer tools installed
2. Connect Phone via USB
3. Wait till zune starts and sync completes
4. Verify that zune is not in a guest relationship
5. open a command prompt, type netstat -a to confirm that port 443 is not being used
6. open an admin command prompt, navigate to c:\windows\system32\drivers\etc\ then type notepad hosts and delete any references to windowsphone developer services
7. go to the settings on the phone and turn airplane mode on (so that the phone is forced to use internet via zune)
8. While the phone is still on the settings page, run Chevron with admin privileges
And it worked!
Click to expand...
Click to collapse
There's no way to know whether a device is unlocked or not until you come to sideloading, which is the point where it matters anyway. Nothing (visible) will change on the device, so don't bother looking for any changes.
WP7 devices occasionally phone home (as far as I know they only do so when connected with Zune) to check whether they should be unlocked or not. If not, they quietly re-lock themselves, and non-marketplace apps will say something along the lines of "This application has been revoked". You'll need to try unlocking again with Chevron and possibly reinstall the apps. There's not much that can be done other than legitimately unlocking your devices.
There's a sideload limit of 10 applications, though there's a version of Chevron that has this limit hacked out of it, I just can't remember where it is. For most legitimate uses, this limit should be fine (and is better than the student/DreamSpark limit of 3).

XAP Installation
A first port of call if Toms XAP Installer doesn't work is to use the official one. It does work.
If you've installed the Developer Tools linked to in the first post, you'll have it already, and should be able to sideload, if your device has been unlocked. If it hasn't you'll have issues, and you should take a look at post #2 in this thread.