Develop Bugs

not able to create EXT2 partition in Ubuntu

hello peoples
well i m new here but using android like a month. today i thought why not give a try to the new Cyanogen build . well i m not that good with ubuntu i downloaded the newest version of ubuntu and followed the same steps as mentioned in thread .. well i m stuck with the ext2 partition ... i have 2gb microSD card i created 3 partitions
1 FAT32
2 EXT2
3 LINUX-SWAP
now i m able to mount the fat32 partition and not able to mount ext2 as show in the pic . please help me ..
Thankyou

I really don't think you needed to start a whole new thread for troubleshooting when one already exists for neopeek.
HOW TO: Ask A Forum Question.
This is where you should have posted, just in case you got confused.
http://forum.xda-developers.com/showthread.php?t=741955

Reefermattness said:
I really don't think you needed to start a whole new thread for troubleshooting when one already exists for neopeek. ]
Click to expand...
Click to collapse
mate i followed the steps as mentioned my neopeek... but i got error in ubuntu not i the device and i was not able to find the solution at his website ..if you know where i can fix this it would be great help for me...if u know the link plz share
Thanks

android-lover said:
mate i followed the steps as mentioned my neopeek... but i got error in ubuntu not i the device and i was not able to find the solution at his website ..if you know where i can fix this it would be great help for me...if u know the link plz share
Thanks
Click to expand...
Click to collapse
You don't think you can find the fix by asking in the thread in which you got the build you are using? Neopeek's build is the only build that requires multiple partitions, so his thread, since he is the developer for that system, should be the one you are asking.
Use GParted to create the partitions. It should be as simple as clicking the GUI. I never had any mount problems when testing this neopeek build, or the XDAndroid multiple partition setup, nor did any of the other testers that I talked with. I dont know if you are trying to manually mount that drive, but for me it always did it automatically when i put the SD card into my card reader. Perhaps I would start from step 1, and take them very slowly 1 at a time. Its usually something very small you overlooked.

Reefermattness said:
You don't think you can find the fix by asking in the thread in which you got the build you are using? Neopeek's build is the only build that requires multiple partitions, so his thread, since he is the developer for that system, should be the one you are asking.
Click to expand...
Click to collapse
well thankyou Reefermattness for your reply i really liked your build ...i was using it for like 2months and runs very good for me .... and your build was like piece of cake installation i just want to try this new neopeek build.the problem was in the card it self... now i changed to my 16Gb card and this works...anyways thankyou so much

AMSS, Bootloader Questions

Hi.
I've played short with amss.bin and changed 1 Byte somewhere in "useless" Text.
Multiloader seems to check this manipulation...
Any idea where in file is CRC, Hash or something like that?
Also any idea if RSA 2048 is activated for Bootloader or AMSS?
Best Regards

i have heard that in bada 1.2 roms its activated but the old ones...

Some packages include more then 2 files:
dbl.mbn
boot_loader.mbn
In T-Mobile Firmware I found also few ELF files...
decrypted_boot_loader.bin is decrypted with PSAS.
Best Regards

I think there are 3 Boot Loader.
We know only 2 files:
dbl.mbn----------------> human readable (find Text like Qualcomm)
boot_loader.mbn--------> encrypted (decrypt with PSAS for instance)
DBL------> Device Boot Loader
FSBL-----> Fail Safe Boot Loader
OSBL-----> OS Boot Loader
Check out Qualcomm manual in QPST... see Screenshots.
Check out above post from me... there are ELFs included...
Maybe start with:
BL3_univ_s.elf
If you wish Android porting.
If I'm wrong, please correct me.
Best Regards

And if wwe would dual-boot android then wich loader would we need to edit. and how would we disassemble it?

And if wwe would dual-boot android then wich loader would we need to edit. and how would we disassemble it?
Click to expand...
Click to collapse
As I saw on S8000 project it seems they "only" change boot_loader.mbn.
But it seems it was not encrypted.
This time on S8500 it is encrypted...
As we can not encrypt them, decrypt is not problem... also enough ELF files are floating around.
First Question is. How write not encrypted boot_loader.mbn to S8500 without killing the handset.
This is the very, very basic Question. Long time before """IDA"""...
So again.
RIFF Box JTAG could help to understand, if Security is low enough to write modified Bootloader back to handset.
All other things are dreams.
Best Regards
Edit 1.
But it could be, that dbl.mbn prevent modification of boot_loader.mbn.
Or other Checks are integrated to prevent easy Bootloader change.
For JTAG user... Is it possible to erase NAND from 0 to 20000 (first 2 MB).
Attention! Not best idea as much harder to write then... also with JTAG.
But is this area protected by something? RSA Keys?
Nand write protection?
Edit 2.
S8500 is 5 x bigger then S8000 boot_loader.mbn
300 KB against 1600 KB
So I'm pretty sure Samsung integrated more Security...

Hi All.
Now i playing with porting android to my s8500.
I see that the Korean m130k very similar to our S8500(shw-m120s),
see pics files from FCC site.
and now I'm looking for bootloader files for m130k.
Also, I have Riff box

@ oleg_k
Thank you very much for these interessting infos.
I will contact you later via PM as I have several Questions...
I found this:
http://www.gadgetfolder.com/samsung-galaxy-k-shw-m130k-android-smartphone.html
Best Regards

Adfree,
will be interesting to talk with you.
Regards

I've investigated JTAG dump...
First 4 MB in 2 GByte moviNAND looks like that:
Code:
000000-16BB0E Boot boot_loader.mbn (not encrypted)
16BB10-1BFF7F 337 KB 0000 (empty) part of Boot
1BFF80-1BFFFF ??? 128 Bytes (RSA ???)
1C0000-1FFFFF 256 KB FFFF (empty)
200000-244B27 DBL dbl.mbn
244B28-3FFFFF 1,7 MB FFFF (empty)
400000 AMSS amss.bin
Now I spent some time to find used boot_loader.mbn and dbl.mbn to be sure that not additional Data is written... this takes some time...
Edit:
In this Dump Version S8500+XX+JD9 is used. I hope I will find Firmware with Bootfiles for compare...
Edit 2.
S8500XXJD2.zip no Bootfiles
S8500XXJD3.zip no Bootfiles
S8500XXJD4.zip no Bootfiles
S8500XXJDA.zip no Bootfiles
S8500XXJDB.zip no Bootfiles
I found 4-5 packages with XXJDx in name... now I will download them all. Hopefully I find Bootfiles that matches S8500+XX+JD9
Edit 3.
Found only XXJDx without Bootfiles...
Last try for today is S8500XXJDZ.zip, but I have download problems... need more then 2 hours...

Good work adfree. You are great.
This seems more interesting than anothers ports.

Okay, I found in S8500XXJDZ.rar
S8500+XX+JD9
dbl from JTAG Dump is 100 % identical.
Last 1024 Bytes are not written into memory...
dumped DBL = dbl.mbn
But dumped boot_loader(.mbn) is with Changes... later more.
0-1FFFF identical
20000-??? long, long empty... FFFFFF
More infos will come later.
Best Regards

It seems much easier as I thought.
No private Data like IMEI... if not removed from JTAG Dump (first 4 MB before AMSS).
In Bootloader part is only once written Block with FF (empty). So
128 KB Block is empty.
boot_loader.mbn is split into 2 parts...
I will make JTAG template for XXJL2 as example.
This I can upload.
Best Regards

adfree said:
It seems much easier as I thought.
No private Data like IMEI... if not removed from JTAG Dump (first 4 MB before AMSS).
In Bootloader part is only once written Block with FF (empty). So
128 KB Block is empty.
boot_loader.mbn is split into 2 parts...
I will make JTAG template for XXJL2 as example.
This I can upload.
Best Regards
Click to expand...
Click to collapse
keep it up buddy.

Okay. Based on my knowledge and JTAG dump...
I have prepared template for JTAG based on XXJL BOOTFILES.
Last 1024 Bytes of decrypted files are NOT written into moviNAND, I cut them:
boot_loader.mbn_part2.bin
dbl.mbn_part2.bin
boot_loader.mbn_PART1 is filled with 1 Block FF (128 KB) at 0x20000
Result is 4 MB file... 0 - 0x400000... Bootarea before AMSS.
Position 1BFF80-1BFFFF looks really like RSA 1024...
Check first 16 Bytes of boot_loader.mbn_part2.bin
Maybe this is the MD5 Hash which should be in the Signature?
Maybe someone knows the Cert or public Key to decrypt the Signature...
XXJB6 has no Sigs...
Anyway.
Without Test if 0 - 0x400000 can replaced via JTAG, we have no progress.
Best Regards
ATTENTION! Please NOT use these files to flash with Multiloader!
You will brick your handset.
Edit.
Added S8500 XXJB6...
Added S8530 XXJK2

Hi adfree good work here!!
Sorry I can't help you, it's over my knowledge
Keep going dude

adfree said:
Last 1024 Bytes of decrypted files are NOT written into moviNAND
Click to expand...
Click to collapse
Just a correction here - the last 1024 are not encrypted in the same way as the rest of the file and they are in fact written, but to a different location
adfree said:
Position 1BFF80-1BFFFF looks really like RSA 1024...
Click to expand...
Click to collapse
I stand corrected if I'm looking at the wrong place, but it doesn't look much like a RSA key to me - it's not odd, so it's not a private exponent and MSB is not set, so it's not a modulus.

is there any easy task in this
i want to help but i am not a programmer
so what can i do????

Just a correction here - the last 1024 are not encrypted in the same way as the rest of the file and they are in fact written, but to a different location
Click to expand...
Click to collapse
Yes, interesting. Like an Log file/Flash history... if I search for tktoolver...
This is far after 500 MB...
I hope this is not relevant for Boot.
Position 1BFF80-1BFFFF looks really like RSA 1024...
Click to expand...
Click to collapse
I think this is the Signature... maybe. So boot_loader.mbn is signed by RSA 1024.
Only an idea, but I could be wrong. XXJB6 has not such 128 Byte Block.
There are also more different boot_loader.mbn possible.
Ehm, JE7 has different... called XX+JEE
I will compare few, but between JL2 and JDZ whole 128 Bytes differs...
I know this only from RSA 2048, where 256 Byte Signature for BenQ Qualcomm handsets...
Best Regards

At the moment I try to find matching Bootloader from S8530... for S8500+XX+JL2
Or other matching combination.
S8530XEJL2
S8530+XX+JK9
S8530XEJL4
S8530+XX+JK9
Maybe with S8530+XX+JL1 more luck...
I hope I will find combo, in same month. Maybe minor differences...
Best Regards
Edit.
Hmmmm, strange S8530 Bootloader most older then S8500...
S8530+XX+JK2
S8530+DD+JK3
S8530+XX+JK9
S8530+XX+JL1

FLOCK - unlocking/unfreezing S8500/S8530 for free could not be any easier!

This is the solution for unlocking Wave phones.​Big thanks goes to mijoma.
All you do and enter into your phone you do at your own risk. Nobody else but you take whole responsibility for what happens to your phone!
Remember than flashing of phone is a little risky, however if performed properly, risk of damaging anything is very low.
If your phone locked-up all of the sudden - be sure to read this thread aswell: http://forum.xda-developers.com/showthread.php?t=1787648
Most of bada 1.2 and 2.0 final-release (not ones from beta releases) bootloaders should be supported.
You need some knowledge about flashing.
How to check what lock do you have?
Enter *#7465625# code, you will see list of active and inactive locks.
What do you need?
Wave 1 or 2 phone with bada 1.2 or 2.0
For Wave I with bada 1.2 - FLOCK_S8500_b1.2
For Wave I with bada 2.0 - FLOCK_S8500_b2x
For Wave II with bada 1.2 - FLOCK_S8530_b1.2
For Wave II with bada 2.0 - FLOCK_S8530_b2x
Flash the right FOTA file. Turn off the phone, wait few seconds, and then turn it on holding CALL (so you have to press CALL and ENDCALL, 2 keys) key until white screen with red texts shows up. Release keys.
Be patient, FOTA module is calculating 3 codes (Subset lock, Netlock, Unfreeze) for your phone, it can take up to 10 minutes. After you get the code you are interested in you can turn off the phone.
Write down the codes you need. Turn off the phone by holding power button for 15 seconds or taking off battery.
After obtaining code, do procedure below:
[Netlock], 2 ways:
1. Insert an unsupported SIM card, start phone and after being asked about "Network Lock" enter Unlock Code you had written down.
2. enter #7465625*638*Unlock code# <thanks to homelessghost for tip>
[Freeze]
1. Insert any SIM card, start phone and after being asked about "Freeze" make call and enter code you had written down.
[Subset]
Can anyone provide guide?
That's all - enjoy unlocked phone!
Troubleshooting:
Instead of white screen with red texts, usual booting logo appears and then Bada starts, what am I doing wrong?
Make sure you flashed right FLOCK without errors. If you did so, first - flash APPS from the same bada version, but from ROM that does contain .fota (certain APPS versions can have locked FOTA module), second - if it doesn't work - update your bootloader to some newer/another one and write post here containing information what version of bootloader (bootloader, not bada) you had before that was not working.
Important: Be very careful when writing down and entering unlock code.
If you got any other questions - please ask in this thread.
It is possible that some phones are not unlockable this method. Then the code wouldn't show up.
General method concept (if you are really interested in sources or way how it works - please PM me or mijoma) should work for most of "Samsung 3G" phones - like JET, Wave3, Monte. If you are owner of locked phone of this class and you are able to do dumps of memory - please contact with me.

Hi,
Thanks a lot for your job, you're my god
Here's my Hash: C7 2D C4 73 07 18 FA 2B 15 7E 29 07 3F BD 04 2E C7 4C 82 E6
Thanks

Thanks so much Rebellos! My phone has been network-locked since I got it and always unable to update with Kies, so I've been stuck on a May 2010 Bada 1.0 firmware forever. Looking forward to being able to flash it
Speaking of which, I've always read that you can't flash anything to a locked phone. Is flashing the bootloader and FOTA alright though? And will the bootloader be compatible with my firmware? It's S8500NEJE6/S8500H3GJ7.
If that is fine, then I'll send you my hash. Thanks so much for doing this!

Thanks a lot, Rebellos!
Here it is my hash code (I only have the network lock):
01 6C 99 C4 BF DC 57 72 B1 23 2E 0B 4C 71 C8 0E C7 DC 79 47
Thanks again!

Very interesting your project but there is a problem.
In Latin America can not change firmware and than through KIES .. we can not use the "Multiloader" because we have the code "SUBSET [ON]" and if we have the code that the [ON] and flash our phone freeze only makes our telephone and so we are unable to use your tutorial.
You know any way to change the code first "SUBSET" to [ON] [OFF] and by doing so Latin American users can use "Multiloader" how many times we want.
I hope your answer and relied heavily on his wisdom!
Already many thanks! Greetings from Argentina!

Phone can be flash-locked - then bootloader will deny any attempt of flashing, though I can't promise I haven't ommited some malicious procedure allowing something like bootloader upgrade but refusing firmware upgrade and refusing bootloader downgrade, causing kinda brick.
Is it a rule that phone flashing is locked always when its [ON] SUBSET Lock?
I will try to look into it.

HandzUp! said:
Hi,
Thanks a lot for your job, you're my god
Here's my Hash: C7 2D C4 73 07 18 FA 2B 15 7E 29 07 3F BD 04 2E C7 4C 82 E6
Thanks
Click to expand...
Click to collapse
25957353
Please let me know if it works.
homelessghost said:
Thanks a lot, Rebellos!
Here it is my hash code (I only have the network lock):
01 6C 99 C4 BF DC 57 72 B1 23 2E 0B 4C 71 C8 0E C7 DC 79 47
Thanks again!
Click to expand...
Click to collapse
code not found
Sorry, I'm looking for other ways of unlocking too.

Works Perfectly, my Wave S8500 is now Unlocked, THANKS A LOT !

Rebellos said:
Phone can be flash-locked - then bootloader will deny any attempt of flashing, though I can't promise I haven't ommited some malicious procedure allowing something like bootloader upgrade but refusing firmware upgrade and refusing bootloader downgrade, causing kinda brick.
Is it a rule that phone flashing is locked always when its [ON] SUBSET Lock?
I will try to look into it.
Click to expand...
Click to collapse
Does that mean it's safe for me to flash bootloader and FOTA if my phone is only network-locked?

dixter said:
Does that mean it's safe for me to flash bootloader and FOTA if my phone is only network-locked?
Click to expand...
Click to collapse
I won't bet my hand for that it is in all cases. But I'm pretty certain it is.

Rebellos said:
I won't bet my hand for that it is in all cases. But I'm pretty certain it is.
Click to expand...
Click to collapse
OK, thanks. Presumably there is no way to obtain the hash without flashing? I suppose it should be fine since those who have already given you hashes must have flashed their network locked phones with no problems.

In "theory" there AT Commands and/or Dev Commands... in combination with WinComm to see result.
Theory because not my business and I have no locked device for tests.
Anyway.
It is ever interesting, how many ways exists to disable Security.
@ Rebellos
Maybe you can teach me how to copy/find "SIMSecure" area in JTAG dump.
Then I could check if my theory is bull.shi.t.
Thanx.
My hints NOT for public... only for my little brain.
Best Regards

Ok, thanks anyway

If we who possess a Wave in Latin America we have all the [ON]. The only problem is the SUBSET flash. If we have the SUBSET in [ON] the phone freezes (unnfreeze mode) after using Multiloader.
It would be good to try to change the way SUBSET to pass it to [OFF] and so test any firmware.
Thank you very much for your response. I hope you find some solution for us because we feel like slaves and prisoners of samsung and has forgotten us regarding updates and all you have to do with the Wave.
Thank you very much! Greetings from Argentina!

dixter said:
OK, thanks. Presumably there is no way to obtain the hash without flashing? I suppose it should be fine since those who have already given you hashes must have flashed their network locked phones with no problems.
Click to expand...
Click to collapse
The hash is generated from IMEI somehow. But I don't know how yet. I flashed my networklocked wave like hundreds of times with no problems. Even updated it from 1.2 to 2.0 while it was still netlocked.
@adfree:
These data are encrypted with SEED algorithm using key generated from oneNAND serial number. Are you able to obtain it?
@elkpojlb
It needs some work but can be done. Though I'm out of time for next few weeks.

Well no problem friend .. long time and we hope some solution so that we do not do anything but wait a bit! Thank you very much and I hope they can do!
Greetings friend!

Rebellos said:
The hash is generated from IMEI somehow. But I don't know how yet. I flashed my networklocked wave like hundreds of times with no problems. Even updated it from 1.2 to 2.0 while it was still netlocked.
@adfree:
These data are encrypted with SEED algorithm using key generated from oneNAND serial number. Are you able to obtain it?
@elkpojlb
It needs some work but can be done. Though I'm out of time for next few weeks.
Click to expand...
Click to collapse
Wow, that's news to me, I've never flashed because I heard it'd brick a locked phone. Now the noob question, which checkboxes should I tick in Multiloader for just flashing bootfiles and FOTA? Boot Change, Full Download or nothing at all? Or does it require one flash for bootfiles and another flash for FOTA? Sorry - the next post from me should contain a hash!

homelessghost said:
Thanks a lot, Rebellos!
Here it is my hash code (I only have the network lock):
01 6C 99 C4 BF DC 57 72 B1 23 2E 0B 4C 71 C8 0E C7 DC 79 47
Thanks again!
Click to expand...
Click to collapse
03935173 - say kudos to mijoma, he found my mistake in code founder.
dixter said:
Wow, that's news to me, I've never flashed because I heard it'd brick a locked phone. Now the noob question, which checkboxes should I tick in Multiloader for just flashing bootfiles and FOTA? Boot Change, Full Download or nothing at all? Or does it require one flash for bootfiles and another flash for FOTA? Sorry - the next post from me should contain a hash!
Click to expand...
Click to collapse
Boot Change, then select directory with bootfiles and file with FOTA. Try to find some tutorial before you do it.

Czesc to mój Hash
A9 67 68 7D DC DB 43 BD 77 18 97 CA FD 09 A4 2E 33 17 44 5E

marcin205 said:
Czesc to mój Hash
A9 67 68 7D DC DB 43 BD 77 18 97 CA FD 09 A4 2E 33 17 44 5E
Click to expand...
Click to collapse
93819157
Cheers

[Q] SM-N7505 Help with Heimdall Root Ubuntu/Linux OS

Hello
I have a SIM unlocked Samsung Galaxy Note 3 Neo SM-N7505 here in Germany. I use Ubuntu OS and have installed Heimdall to do the root but unsure of how to repackage the data in the firmware .zip I got here
http://www.sammobile.com/firmwares/database/SM-N7505/DBT/
I extracted this but it seems that N7505XXUCNG5_N7505DBTCNG1_N7505XXUCNG2_HOME.tar.md5 is a Odin type of update.
Can someone point me to where I can find the Firmware below that I can use with Heimdall or help me convert the one I have?
UPDATE:
Read my reply below or above this one.
Firmware for GALAXY Note 3 Neo LTE SM-N7505
Model SM-N7505
Model name GALAXY Note 3 Neo LTE
Country Germany
Version Android 4.4.2
Product code DBT
PDA N7505XXUCNG5
CSC N7505DBTCNG1

Still await a helpful persons support...
I was able to Odin flash it , but I still am wanting a linux/unix way to admin my firmware or ROMs. Any help would be awsome.

Note 3 neo forum is here: https://forum.xda-developers.com/note-3-neo
Did you try flashing cfautoroot with Heimdall?
https://autoroot.chainfire.eu

Re: Still await a helpful persons support...
audit13 said:
Note 3 neo forum is here: https://forum.xda-developers.com/note-3-neo
Did you try flashing cfautoroot with Heimdall?
https://autoroot.chainfire.eu
Click to expand...
Click to collapse
I am not fully able to. Most of them will not work. I download it. I am able to hook up my phone all good ready to go. Can copy and make a PITT file of my phones drive layout. All systems go. As soon as I load the new ROM or Firmware to root the phone. I get a error that either the file is not compatable with Heimdall or I get this file is missing the Android Meta xml Heimdall needs for setting up the permissions and configurations.
It really gets me since I am pretty technical and write code i am at a loss why this file is always missing. Why fail to put a file in that is that important? Then you read on that and find 10,000 ways to write one. Alas not one are specific and if they are so easy to whip up one yourself why dont any of the 10,000 simply write one and spend their time teaching how to write hard scripts and code. Also not B*ching just really tired of the same old various types of info sprinkled with vauge and unclear steps or actual files to use as guides.
When I write a tutorial or a walkthrough its very clear. When I read most of the rooting or dealing with Heimdall and phones its like trying to locate that ring Frodo sought-after for so long.
I really appreciated that you responded. If you can maybe help me it would be great if I located a way to root my phone without a computer at all. I really think since everyone pretty much can root or unlock the damn things the phone would just have a option with a popup that you agree voids the warranty and poof its rooted...
lol
Thanks for taking time to message me!
:good:
Scott

Unfortunately, I do not use Linux so I am not sure what else to suggest other than possibly loading a temporary Windows installation onto your computer to flash cfautoroot via Odin.

Hi ScottsDesk
In the end, did you reach to root your phone from Ubuntu ? This is exactly what I want to do : when I've understood which will be the first way I'll choose to use a free'd phone, I want to walk this path with Linux. I can't understand why all the guys here being fans of free devices can even think to use Windows to gain control over their android : it is a shame (I must admit I'm a 0-skilled dev, so I can even allow myself to find strange there is so much Java therein Android ).
But ATM, I don't even know if I'll use CF-auto-root or if there exists a custom ROM that is running bug-free our device after days and days parsing this forum. The sad thing is I don't feel skilled enough to dig in the most serious solution (ChainFire's abandonned Unofficial CM12.1 for SN-M7505) to see if NFC is still really KO (ATM I have to remember some reported bugs have easy workarounds : lockscreen lag : disable Aquarell &/| wavelets effect and lowen swappiness from 130 to something around 50 (I'd try even far less, like on SSDs), and a delay in video recording sound : disable the "Google OK" thing).
I hope you'll read this
PS : it seem heimdall has what what we need (--no-reboot argument to follow what the guys say at some point to not reboot, instead remove battery).
I just gave try, just to see, but it fails and don't know what yet :
Code:
sudo heimdall print-pit --verbose
[sudo] password for me:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
libusbx: error [op_set_interface] setintf failed error -1 errno 71
ERROR: Setting up interface failed!
Releasing device interface...
Also, did you understand this strange advice ? : some advise to make a backup (boot.img above all) before we do anything else : but I booted the phone in recovery mode and I can't see nandroid backup option...

WP backup file of cancelled prototypes made by Nokia/Microsoft

NOTIFICATION : DONT FLASH,RESTORE EMMC BACKUP FILE OF PROTOTYPE TO YOUR RETAIL DEVICE. IT VERY DAMAGE
Rx112: https://onedrive.live.com/?authkey=!AMMXWNS0CVaIx7A&id=9BEC8AA0062F7BD6!141944&cid=9BEC8AA0062F7BD6
Rx100 : https://forum.xda-developers.com/windows-10-mobile/wp8-0-rx100-t3954941
Rx130: https://mega.nz/#F!mGQ3kYCD!PYYx6Y8FtnRHDMzxX16SUw
win10mobie arm64bit: https://forum.xda-developers.com/windows-10-mobile/arm64-uefi-rx130-t3778025
converted to 950xl fw: https://drive.google.com/file/d/1oRwZvXYxAKiN9xCSdYG-69PPylM6GUt6/view?usp=sharing
920 b1 : https://drive.google.com/file/d/1peKXuSPcr9Hn8TdPkKxoP0RDd5AVedO-/view?usp=sharing
650xl : https://drive.google.com/open?id=1SThRj7QsX9KsjUUUUl0EECP4NKyARsY1
950 b1: https://mega.nz/#F!zCQGkawI!Iau0OKKY02HjXy2r56iW-Q
Goldfinger : not public
McLaren:
I cant share it without permission of guy have it
435/532
android:
435: https://mega.nz/#!zZlmTYgK!o8w3tGd3_OtiqNtX5A620Nleg8apPVqeYVGo6JliPPQ
532: https://mega.nz/#!WE9m3K5S!AnuCmmizOAhqB6JuEvGbmmyVj9bwpAybDQVPOZRtMBA
WP :
532 4gb : https://drive.google.com/file/d/15Gz6IfBPL1LiJcphQbEEVYIqX7uwl1Se/view
532 8gb: https://drive.google.com/open?id=1WvLnf3vkYo86bMsm_NQTF1nKWxvIoCfV
435 8gb: https://drive.google.com/file/d/1U0QyJH3cugct2D79wcHjmI_V-u9VDize/view?usp=sharing
Clippr will meltemi os: https://mega.nz/#F!Z55gGSiC!eBFE3nNLwcP62v2YIPHVrQ
...

If someone have prototype with incomplete system. Try found at here and flash it. Dont forget backup special partition via win32disk image,partition guru,winhex,etc.

dont try install win10mobi arm64 for rx130.very early, make damage for hardware

For ffu of goldfinger,i will upload tomorrow

updated ffu file for goldfinger

Updated full emmc backup of rx112 midas- first 3d touch prototype of nokia

I will update
Full backup + ffu of
Rock Alt 530 5 inch
Saimaa CDMA
Fame 4GB

Hi, I didn't know that you have an archive for prototype firmware here! Good Job!
Well, the McLaren though, it seems to be quite tricky. But we will see...

mivas said:
Hi, I didn't know that you have an archive for prototype firmware here! Good Job!
Well, the McLaren though, it seems to be quite tricky. But we will see...
Click to expand...
Click to collapse
Haha
For mclarne gdr2. I waiting another friend,guy installed it on his phone
But i busy

link for rx112 not work, can you reupload? thanks.

thinhx2 said:
Haha
For mclarne gdr2. I waiting another friend,guy installed it on his phone
But i busy
Click to expand...
Click to collapse
ok good! :good:

Today i got news from my friend:
That person likes to display information with various models
At the same time, it also provides high paid flashing and upgrading services.
So i will remove gild finger firmware

thinhx2 said:
Today i got news from my friend:
That person likes to display information with various models
At the same time, it also provides high paid flashing and upgrading services.
So i will remove gild finger firmware
Click to expand...
Click to collapse
Hi, I just saw this post... (I don't get email notifications although I choose to be informed immediately...)
So, this is the same for the McLaren as well? ffu conversion is not available?

mivas said:
Hi, I just saw this post... (I don't get email notifications although I choose to be informed immediately...)
So, this is the same for the McLaren as well? ffu conversion is not available?
Click to expand...
Click to collapse
sorry, i cant make ffu for it, it have journal bug when convert to ffu, i dont know why

thinhx2 said:
sorry, i cant make ffu for it, it have journal bug when convert to ffu, i dont know why
Click to expand...
Click to collapse
ok... Still, the aim is to push it to W10M, so if you manage to get an image with W10M, even without touch, I would be interested in that image instead.
Then, maybe we find a way to get the standard touch back, perhaps with newer W10M updates (eg tricking it as a different device, thus restoring the "normal", non-3Dtouch updated files) or in the worst case, we could perhaps find a workaround with the drivers...