Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
|
14-02-2024, 14:35 PM,
Post: #1
|
|||
|
|||
NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
Problem:
I bought NBT EVO from MINI, HW 5.1, Data 20/21 with GPS. Working on a bench. The display lights up "No signal". E-Sys Read (ECU) - device is available. Reading the VIN gives [яяяяяяя]. (screenshot in the tab). Femtoevo gives a similar result. There is no CAfd file. "Detect CAF..." says swfl_00002716-007_021_003 is missing . Goal: Revive the device for F15/F85. Can anyone help me by suggesting an algorithm of actions? Do I understand correctly that we need to start by lowering i-Step to the level of 17/07 - 18/03 from BMW? respects r respects espects |
|||
|
![[+]](https://cartechnology.co.uk/images/CarTechnologyTheCure/collapse_collapsed.png)
|
14-02-2024, 14:53 PM,
Post: #2
|
|||
|
|||
|
RE: NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
Do not even think to downgrade. Clearing v850 using the known method will brick this unit type. You need the correct FA to detect matching CAFD.
EntryNav2, MGU, Evo - carplay with or without ATM, full fsc, component protection and more.
NCD 2.0 secure coding - typeschlussel (typecode) change, region change  Press rep & thanks if I you found this useful. PM if you need more help. |
|||
|
|
|
14-02-2024, 16:50 PM,
Post: #3
|
|||
|
|||
RE: NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
(14-02-2024, 14:35 PM)ppbarsrd Wrote: Problem: Either flash to newest ilevel without doing anything strange or use MINI fa to code, then use BMW (the one you trying to fit it) FA and code it. Will work just fine. Coding 2.0 File Service - Region Change/Typekey - SFA iDrive 8.5 REGION CHANGE
BMW Full FSC Set + CarPlay - NBT EVO ID4/5/6/ENTRYNAV2 (CP REMOVE/PATCH) MGU CARPLAY/ANDROID AUTO Activation / MGU PATCH/CP REMOVE (EU service) ISN RESET Remote F/G series BMW KAFAS 2/4 FSCs(7E/BE/BF - 11F/13E/13F) BMW KAFAS4/MRR/RAM Virgin / VIN FSC Matching |
|||
|
|
|
14-02-2024, 17:47 PM,
(This post was last modified: 14-02-2024, 18:01 PM by ppbarsrd.)
Post: #4
|
|||
|
|||
RE: NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
(14-02-2024, 14:53 PM)jb2005 Wrote: Do not even think to downgrade. Clearing v850 using the known method will brick this unit type. You need the correct FA to detect matching CAFD. Did I understand correctly that it is necessary to prepare FA from MINI 21 with the corresponding Typschlüssel and Zeitkriterium (for example Typschlüssel=YW73 and Zeitkriterium=0721)? (14-02-2024, 16:50 PM)dasi Wrote: Either flash to newest ilevel without doing anything strange... Those. I take psdzdata 4.38.30 and reflash it with the same or a larger i-Step? Which Fa should I collect? |
|||
|
|
|
15-02-2024, 22:53 PM,
Post: #5
|
|||
|
|||
|
RE: NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
Just reflash with bmw firmware. The MINI one is different.no need for upgrade. Calculate tal with F15 with recent daten and flash.
Also, 5.1 will never work with apix1 screen from nbt. So you will need the apix2 screen. |
|||
|
|
|
15-02-2024, 23:58 PM,
(This post was last modified: 16-02-2024, 00:01 AM by BugFix.)
Post: #6
|
|||
|
|||
|
RE: NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
The HWEL_00003A0A_001_005_001
for the main series: I001, RR21, S15A, F056 you can update it as you like. NBTEVO, ENAV2, MGU - CP OFF, Navi , APPS , Carplay, AA
MGU ID-8-9-10 Cars - Full Region change NCD Secure Coding 2.0 |
|||
|
|
|
16-02-2024, 06:21 AM,
Post: #7
|
|||
|
|||
|
RE: NBT EVO from MINI, HW 5.1, Data 20/21 with GPS
Remove 650 from your VO and run tal calculation again and see if it is all ok then.
Successfully retrofit on BMW F30 335xi 248,302,3AG,430,5AG,5AS,6NS,8TH,IHKA3
|
|||
|
|
|
« Next Oldest | Next Newest »
|
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Return to TopReturn to Content
