yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Duke12:
Bob

Seems the same. Same CPU, platform, Specs etc. I think being a "VW Golf Passat Jetta" model from Joying it probably has some firmware in it to pick up your particular car's Bluetooth connections. The front surround looks like it has been added to my "Universal" type to fit neatly into your dashboard. The case and rear connections are identical. I see they have added a CanBus box which my car did not need but looks like yours does. There is probably a harness with it to fit your wiring loom.

if you run a lot of apps at once there is some lag not bad though. Like if you had the radio on and the GPS on and DVR the traffic then that's a pretty big load so then there is some lag but you get used to it. You might have to wait a second before an icon or screen switch becomes available. When running only a few apps at once there is no lag issues.

I like mine a lot, would not replace it with the OEM.

The problem mentioned below is one with my car only. My car's remote console jacks for the AUX and USB have their own preamp so I have by passed them and put in a aftermarket remote Aux USB and that works ok.

I am half way through doing a write up on the modifications and install if anyone is interested.

Duke
[Android Head-Units] lbus9168:
Hey mate, does it run Android auto? Trying to figure out which units can and can't. Looks like any running Android 5 can but trying to figure it out. Thanks!
[Android Q&A, Help & Troubleshooting] ACanuto9:
For some stupid reason I tipped in adb shell rm 25 rm 26 and now my internal sd card doesn't mount.

On CWM appears the following error E:stat: Error 1 on file /dev/block/platform/msm_sdcc.1/by-name/grow.

I'm unable to mount /sdcard and /storage/sdcard0.

The system storage appears to be fine since I can still access cm 12.1.

Any thoughts on how I should resolve this issue?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] diehard2013:
looks like we're stuck with lolly 5.02...
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] -CALIBAN666-:
At first bro: its a CUSTOM ROM or COMMUNITY BASED ROM.

Second: its 5.0.2 Lollipop.

At last: just wait,the problem is your device variant,but u can do it by urself,i mean rom devwork.

Or u wait until anyone here with knowledge cook a MM based rom.Good Luck.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] diehard2013:
l'm not your bro, my friend. . . :)

your suggestion of Rom devwork. .. I like.

.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] diehard2013:
kamerade,

it's MM 6.0.1 now!!!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Awesomeslayerg:
Im on safestrap and i kinda deleted the stock amazon fire os and i dont know what bootloader i am on. How do i check it?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
You can't. If running Safestrap v4 bootloader can not be unlocked (although SS v4 can be installed on a device with previously unlocked bootloader).
[HTC 10 Questions & Answers] nofroyo:
So Its been a long time since I used a HTC devices such as HTC Sensation 4G, HTC Amaze & HTC Evo 4GLTE phones. Switched to Samsung for the Note 2 and haven't used another device besides samsung for a while now. Used to odin and all that jazz, I do recall the days of getting unlocked bootloader token from HTC dev, s-off and installing roms. If my memory recalls I do recall in order go back to stock I had to flash it via RUU file i think.

So after samsung burned the dev community of locked bootlader for S7 on Tmobile I abanden samsung and had high hopes that T-Mobile would release HTC 10 so I could move to it. Luckily enough they did and I just mine today so im like super stoked to get back into HTC groove. So my question is before rooting and all that fun stuff I did read all the FAQs and guides, but something is kind of unlcear for me at the moment.

I found this:

http://xdaforums.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297

So my question which file do I use for my stock in case I need to return to stock for any reason?

any help would be much appreciated
[HTC 10 Questions & Answers] squ89r97:
Welcome back to HTC, the 10 is a great phone to make your move from Samsung to. With regards to your question, it all depends on your CID, MID and firmware version.

Find out what you have and match them up to what's available on that thread.

You should make a back up of your own too.
[HTC 10 Questions & Answers] nofroyo:
where would I find this information for my device?
[HTC 10 Questions & Answers] rowbaggie22:
Go 2 App Store and type in simple cid getter and install
[Windows 10 Mobile] TristanLeBoss:
I was searching for the "ffutoraw.exe" file referenced in the "rawprogram0.xml" file from the Xiaomi Mi4 Windows Mobile 10 ROM when I discovered a small tool which can also do the work.

Here is the eMMC DL tool v2.15 from Qualcomm. This tool is publicly available. It's part of the "DragonBoard Update Tool" (dragonboardupdatetool_x64.zip or dragonboardupdatetool_x86.zip) available on this webpage: https://developer.qualcomm.com/hardware/dragonboard-410c/tools Once installed, you will find the file in "C:\Program Files (x86)\Qualcomm\DragonBoardUpdateTool".

This small EXE actually has 3 useful functions regarding FFU file:

- "Create rawprogram0.xml for a FFU file; need -o"

- szOutputFile = rawprogram0.xml

- "-splitffu szFFUFile -o szOutputFile"

- "Split FFU file into partition binary chunks; need -o"

- szPartName = partition name or "all" to extract all partitions

- szOutputFile = destination folder for bin files

- "-dumpffu szFFUFile szPartName -o szOutputFile"

- "Download FFU file to device in emergency download; need -o and -p"

- "-ffu szFFUFile"

(I tried the rawprogram0.xml creation with the Xiaomi Mi4 Windows Mobile 10 ROM and the produced file was exactly the same as the one included in the ZIP file.)

Launching the EXE from the command line will echo an help screen:
[Windows 10 Mobile] nate0:
Does the tool only work on a device if it is in EDL mode? Thanks for posting this as I would like to try to find a way to build or flash a compatible rom for a non-windows based smart phone. This helps...
[Windows 10 Mobile] TristanLeBoss:
This indeed helps a lot. If I refer to the name of the tool, it probably only works on phone in EDL mode. What do you want to do exactly?
[Windows 10 Mobile] nate0:
I'm interested to see how difficult it is to compile a Windows Mobile Build, at least a test build, since Production builds require specific vendor signing. Microsoft offers all the resources much like Google for doing this, yet some of them do require subscriptions for access. If this tool is able to formulate the xml for partitioning from a ffu then theoretically building this xml from another rom that is designed for 32gb partitioning could lead to a flashable solution on a device other than the mi4 or other 16gb android phones. I am still reading and researching much, but with the resources now it should not be hard to accomplish this.
[Windows 10 Mobile] TristanLeBoss:
Yes, you can give any FFU file to this program and it will give you the corresponding rawprogram0.xml file. You need to use the "-splitffu" option for that.

I think this option is available so you can flash the FFU (using the rawprogram0.xml file) with a program like "QFIL" (part of QPST).

emmcdl -splitffu wp8.ffu -o rawprogram0.xml

But you can also directly flash the FFU file to your phone: you just need the FFU file and the Firehose flasher for your phone (it's a MBN file which has a name looking like "prog_emmc_firehose_8909_lite.mbn"). To proceed, you need to use the "-ffu" option:

emmcdl -p COM8 -f prog_emmc_firehose_8994_lite.mbn -ffu wp8.ffu

You won't be able to generate a Windows Mobile image from scratch because neither the BSP package or the WMAK kit have been leaked*. The Windows ADK contains all the tools needed to create and flash a ROM but without the CAB files from the Qualcomm BSP package and the Microsoft WMAK kit, you won't be able to do anything.

* Windows Phone 8.1 AK have been leaked (the install program is in the "\WPBLUE\Blue_9651.12393_ProdSigned_OEM\WPAK" folder of the 7Z file available on this page: http://xdaforums.com/windows-phone-8/development/tools-wdk-wpak-wpdk-cabs-building-wp8-t3183972)

Windows 10 IoT AK have also been leaked (you need to find either "en_windows_10_iot_core_version_1511_updated_feb_2016_x86_arm_dvd_8369778.iso" or "en_windows_10_iot_core_version_1511_x86_arm_dvd_7226982.iso")

I managed to create a small script which recreate the CAB files from a FFU file. Even if they were exactly the same as the originals, they lacked the Microsoft signature so I am unsure the ADK tools can use them.
[Windows 10 Mobile] TristanLeBoss:
Oh, I forgot to add that - to my knowledge - this tool doesn't implement the image integrity validation (signature check [embedded catalog] and hash check [embedded hash table]).

Would be interesting to find out what happen if the stock 950 FFU file is flashed as-is to a Nexus phone...

There is 3 problems I can think about:

- UEFI: the phone may need to have a Microsoft key in its "db" store to authenticate the Windows Mobile bootloader.

- Partitions: does the layout need to be exactly the same as the Android version?

- Drivers: even if the SoC is the same, they may be some tweaks...
[Windows 10 Mobile] nate0:
I'm going to look into this further. Thank you. What's stopping us from using a Lumia ffu for an identical soc and storage size of another device? I've been contemplating this and since all the drivers and cabs are signed already might be possible. Also with your script what's stopping you from signing those files yourself and making a test build image?

---------- Post added at 07:52 PM ---------- Previous post was at 07:44 PM ----------

Good points. Much deeper than I was thinking but along the same lines. I would think the partitioning needs to be identical the 950 rom since that's how it was built. But it might not matter since ffus blank the entire storage in the process of flashing you can technically partition it however you want but then your building that configuration from scratch. How difficult is it to dump the partitioning of a 6p? I'm still looking but that's the next best candidate being unlockadble in seeing if this is feasible. Sorry for any typos,sending these last two from my phone.
[Windows 10 Mobile] TristanLeBoss:
I added another reply before seeing yours. It contains 3 thing that may be a problem: UEFI, partition layout and drivers.

UEFI: Windows Mobile is said to require Secure Boot. This is not a problem because Nexus phones support it. The problem I see is more with the signature check on the bootloader: the 'Microsoft Windows Production PCA' and 'Microsoft Corporation UEFI CA' keys should be in the "DB" store for the Windows Mobile bootloader to be accepted by the UEFI bios of the Nexus. The worst thing that can happen is the Nexus displaying a message complaining about the bootloader.

Partition layout: Flashing a new image will probably change the partition table. I don't know if it can be a problem.

Drivers: SoC contains most if not all the required systems of a phone so the drivers should work but they may need per-hardware "customatisation".

The problem is that we hear about people succeeding but not about failures: has someone already tried to flash a FFU file to a Nexus? Maybe no one ever tried... and maybe it's working.

I don't think you can really brick a phone by doing so because the Qualcomm 9008 mode is not something that is part of the image.
[Windows 10 Mobile] TristanLeBoss:
The FFU file basically contains a disk image with a GPT partition table. When you will flash the FFU, the eMMC memory will be erased and a new partition table will be installed along with the new partitions. On this forum, there is a tool which convert FFU to VHD: http://xdaforums.com/showthread.php?t=2066903 (On my computer, the conversion works but the mounting fails. You can find the resulting VHD file in your Windows profile TEMP directory.). There is also one Python script available to create a RAW disk image from a FFU file but I HIGHLY DON'T RECOMMEND IT as it doesn't implement the whole FFU specification so it will likely create corrupt disk image.

The thing I don't know is if the partition layout of a phone can be changed: you can of course change it but will the phone still operate? I mean maybe each partition need to start at an exact sector (LBA) [I don't think so but without trying...]
[Windows 10 Mobile] nate0:
Have you validated the keys exist on current windows phones and if so maybe replicate or extract from one. I own an m8 for windows and am thinking the bootloader being unlocked is the only way of getting near the secureboot partition. Also if the nexus support secureboot most of it might be built in. See requirements. Here. https://msdn.microsoft.com/windows/hardware/drivers/bringup/uefi-requirements-specific-to-windows-mobile
[Windows 10 Mobile] TristanLeBoss:
No, I have no Windows Phone ;)

Maybe the Secure Boot is just a requirement but it may not be mandatory to boot.

It's also possible that a retail ROM check for it but that a production ROM may not check for it. ( https://cms-images.idgesg.net/images/article/2015/03/uefi-secure-boot-windows-10-100574859-orig.png )
[Windows 10 Mobile] TristanLeBoss:
Okay, I have more information: it seems that on mobile phones, the SecureBoot keys can be stored in a partition from the emmc. This partition name is RPMB for Replay Protected Memory Block.

This partition is encrypted with the PK key which is burnt into the chip.
[Windows 10 Mobile] TristanLeBoss:
It seems booting an unverified bootloader is possible on Nexus phone :D

http://android.stackexchange.com/qu...ot-img-to-nexus-5-when-secure-boot-is-enabled

Q: "As I understand, if secure boot is enabled, the bootloader will verify the boot.img when booting.

Obviously, my custom kernel cannot pass the verification.

In such a case, how to correctly flash my own boot.img?"

A: "This doesn't imply that you cannot boot into the Android with your custom kernel. When the verification would fail, your device would warn you about that and you would be given the choice to continue the boot process or not."
[Windows 10 Mobile] nate0:
Correct. It warns of this after unlocking the boot loader. Need to acquire an mbn for this phone to boot the rom in question.
[Windows 10 Mobile] TristanLeBoss:
I attached the one I have but don't know if it's the one to use for this phone.
[Windows 10 Mobile] nate0:
Did you generate this mbn or locate it elsewhere? I am trying to understand how the mbn file fits into the picture. Is it generated based on the FFU image or generated by the OEM?

I was able to create the program xml from a lumia FW of another 800 SoC (Lumia ICON). With the files and tools gathered I want to just test this flash process by flashing a different Windows ROM designed for the Lumia onto my Ativ SE. I think I have a way of getting the mbn for this phone with samtools which I found in another forum thread, but I will have to double check. The ATIV SE is also the 800 but not designed for this specific Lumia rom or the rom designed for it, however you look at it. I am willing to do this since the ATIV SE has a bad sim slot anyway.
[Windows 10 Mobile] TristanLeBoss:
I think "MBN" doesn't mean anything: it's just an extension. I found MBN files containing basically any type of file. The MBN file I attached and which is needed by the emmcdl.exe program should be an ELF (Executable Linkable Format, the EXE files of Linux ;) among many uses ). Open it with an hex editor and it should start with "ELF".

The file I provided has been found by myself. I have not yet any idea if it's possible to generate them. Firehose is the name of one of the many protocols which can be used to talk to a device in emergency mode. I think it only depends on the SoC.
[Windows 10 Mobile] TristanLeBoss:
There is another tool from Microsoft dealing with FFU: ffutool.exe

https://msdn.microsoft.com/en-us/library/windows/hardware/dn789235(v=vs.85).aspx

It's part of Windows Assessment and Deployment Kit (Windows ADK) which is publicly available ( https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx ).

NOTE: This program has been coded using C# so it can easily be decompiled back to its source code using ILSpy ( http://ilspy.net/ ). It uses the following assembly: 'FFUComponents, Version=8.0.0.0, Culture=neutral, PublicKeyToken=5d653a1a5ba069fd' which may contains interesting code.

I'm not sure it's useful as it seems to enforce integrity check and platform check.
[Windows 10 Mobile] TristanLeBoss:
The last tool which deals with FFU files is thor2.exe

It's also publicly available: just install the Microsoft Windows Device Recovery Tool ( http://go.microsoft.com/fwlink/p/?LinkId=522381 ) and you will find it in this folder: C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
[Windows 10 Mobile] TristanLeBoss:
It seems that there is different Qualcomm protocols to download an image:

- Sahara: Sahara Protocol works a lot differently than the regular software download described below. In Sahara, the download is driven by the device itself, so the device starts of by sending a Hello command to the PC.

- Streaming: Used to put the phone in download mode. Requires an HEX file and a MBN file containing the GPT + the boot partitions.

- DMSS: Outdated protocol.

- Firehose: ...

The 2 tools I talked about support different protocols:

thor2.exe

------------

-protocol

sahara

streaming <default>

emmcdl.exe

---------------

-protocol

firehose <default>

streaming
[Windows 10 Mobile] nate0:
Lumia phones use a different download mode than HTC or Samsung or at least all 3 OEM's go about it differently. As far as testing the flash process of a ffu to a phone of a same soc hw Thor2 should be equipped to handle my m8 since the windows device recovery tool supports it, but the ativ se is not.

I'm searching for a used nexus currently if found would it matter the storage size whether 32 or 64 gb?

---------- Post added at 05:52 PM ---------- Previous post was at 05:41 PM ----------

Isn't Sahara native for lumias? There is a way to gain access to contents of the Sahara files/folders on a limited amount of Lumia devices that can be unlocked via wpinternals, I was looking at this last night.
[Windows 10 Mobile] TristanLeBoss:
Windows Device Recovery Tool simply checks on a server to know which files and protocol to use with thor2. Exemple for the Lumia 640 :

https://repairavoidance.blob.core.w...gencyFlash/RM-1077/emergency_flash_config.xml

Replace "RM-1077" qith any hardware model (I think you can find the "Model" in the "About" screen of your Windows phone.)
[Windows 10 Mobile] augustinionut:
Ok folks, how to skip id platform check?
[Windows 10 Mobile] TristanLeBoss:
Method 3.1.1 of this post ( http://xdaforums.com/showpost.php?p=67045151&postcount=18 ) bypass platform check.

dism.exe also allows to skip platform check using the "SkipPlatformCheck" argument.

thor2.exe also allows to skip platform check using the "skip_id_check" argument.
[Windows 10 Mobile] TristanLeBoss:
Precautions

If you plan to play with FFU files, be sure you have your phone's programmer file for the Streaming or Firehose protocol. This file will be needed in the last resort if the phone fails to boot into USB download mode and instead goes into Qualcomm 9008 mode. Even if Windows Mobile doesn't do a complete boot, you may be able to reach the USB download mode and so reflash your original FFU or original image.

So also be sure to have the stock image of your phone (Android or Windows Mobile).
[Windows 10 Mobile] augustinionut:
Thor2 error:

FlashApp returned reported error in SecureFlashResp!

Status: 0x0012, Specifier: 0x00000004

FA_ERR_AUTHENTICATION_REQUIRED

0xFA000012: Authentication is required to be able to skip integrity and/or signature and/or platform ID check.

If i brick my phone wdrt will be able to flash ?

Tristan, no usb mode on lumia 640 xl dualsim.
[Windows 10 Mobile] TristanLeBoss:
The Platform ID check is done by the phone itself. For this reason, no unsigned/unvalid code can be flashed. Also, because Secure Boot is enforced on your phone, even if you reach 9008 mode, you won't be able to flash something that's not signed by Microsoft.
[Windows 10 Mobile] TristanLeBoss:
You may want to unlock your phone by registering it as a development phone: https://msdn.microsoft.com/en-us/library/windows/apps/ff769508(v=vs.105).aspx

Maybe the error message just means the only way to flash an unsigned/unverified image is to have a development phone (who is unlocked).

You will need Windows Phone 8.1 (not 8.0): http://stackoverflow.com/questions/30121983/developer-unlock-windows-phone-8-error-code-0x64
[Windows 10 Mobile] nate0:
Would there be a way to capture the packet/transfer stream in fiddler or another agent to authenticate outside the phone on it's behalf? Similar to using fiddler when the GUI Windows Recovery Tool is used to give it the Model ID you would like to force download a different FFU than what is for the phone you are flashing. EDIT: Actually scratch that. Fiddler may not use the correct protocols. I know it has access to http and https traffic. Not sure what type of protocol is at the phone <=> FFU image level.

---------- Post added at 04:20 AM ---------- Previous post was at 03:59 AM ----------

This is interesting. Injecting and removing cab files for the needed qualcomm chip. Has this been successful from your end TristanLeBoss? BTW I will be picking up a Nexus 5x tonight after work, I am hoping to find time in the next couple of days to use some of the insight here to attempt an ffu flash.
[Windows 10 Mobile] TristanLeBoss:
You will not encounter the problem faced by augustininout: he just have this problem because the Lumia 640 XL is a well locked phone ;)

I don't really know what this authentication is (the search for both the error code, ID or message doesn't get a lot of answers on Google). I guessed it may be the fact that the phone is not a developer phone.. We just need to wait for the poster to let us know what happened after he registered it.

People already tried to fake the conversion from a retail phone to developer phone: unfortunately, the phone only accept command signed with a Microsoft certificate. Lumia phones are well secured to prevent flashing and execution of any invalid or uncertified code. Actually, all the checks are done by the phone flash program and the PC only sends the FFU file. When an error like this one occurs, it's the phone who send it. So, we have no real way to bypass this.

A FFU file contains a platform ID but if you change it, the hash table will be incorrect and so will be the catalog file which signs the hash table.

I don't think the method to test will work (the one with ImageApp.exe sure do) but it's worth the try. Indeed, WIM files which can be normally used with theses commands only contain one partition. A FFU file, like a VHD file, contains a whole drive image. I suspect Dism.exe doesn't (yet ?) support multiple partition. Because Windows Mobile have packages which can be installed on any partitions, it can't install them.

Maybe we can explode a FFU file into WIM files (one per partition) and try to deploy the packages this way. Once done, we remerge the WIM files into a FFU file :D
[Windows 10 Mobile] TristanLeBoss:
It's better to get a Nexus 5X because it looks like there is a way to rescue the phone from the infamous 9008 mode:

http://xdaforums.com/nexus-5x/help/req-help-to-unbrick-t3251740

I think the first thing you will want to do is to disable Secure Boot.
[Windows 10 Mobile] lukjok:
Maybe this can be helpful [MENTION=269273]TristanLeBoss[/MENTION]

Enabling Secure Boot and BitLocker Device Encryption on Windows 10 IoT Core
[Windows 10 Mobile] nate0:
To disable secure boot do you mean deleting sbl1? I am not aware of a easy way to disable this on a mobile device. Also is the flash programmer for the 5x msm8992 out there anywhere? Having a hard time finding.