Develop Bugs

Error 7 Fix for TWRP 2.3.0.0 and T&K's 10/11 AOSP d2att ROM

If you're trying to flash Task & Ktoonsez excellent 10/11 AOKPJellybean 4.1.2 ROM for the SGS3 AT&T/Rogers using TWRP 2.3.0.0 and it bombs with Error 7, you can:
Copy the zip to a Linux box (this is important!)
If you're using something modern, like Ubuntu 12.04, open the zip and replace the update-binary file as described on the TWRP 2.3.0.0 page h t t p : / /teamw.in/project/twrp2. Sorry, I'm a n00b and can't post links yet. The info is listed under the "What's new in 2.3.0.0" section, about a page length's down.
Try to flash again
I'm betting that you could also extract the zip, replace the file and rezip without a problem, but I didn't try it. I was successful doing this using Ubuntu 12.04 x64 but I'm also very sure you could do this in about any distro.
Good luck!

m3741 said:
If you're trying to flash Task & Ktoonsez excellent 10/11 AOKPJellybean 4.1.2 ROM for the SGS3 AT&T/Rogers using TWRP 2.3.0.0 and it bombs with Error 7, you can:
Copy the zip to a Linux box (this is important!)
If you're using something modern, like Ubuntu 12.04, open the zip and replace the update-binary file as described on the TWRP 2.3.0.0 page h t t p : / /teamw.in/project/twrp2. Sorry, I'm a n00b and can't post links yet. The info is listed under the "What's new in 2.3.0.0" section, about a page length's down.
Try to flash again
I'm betting that you could also extract the zip, replace the file and rezip without a problem, but I didn't try it. I was successful doing this using Ubuntu 12.04 x64 but I'm also very sure you could do this in about any distro.
Good luck!
Click to expand...
Click to collapse
This actually works for cwm as well and any rom that throws that error when flashing and doesn't need to be done on a linux box. The way I do it, is open the zip using winrar, don't extract it, navigate to the updater-script and open it with Notepad++, notepad or wordpad messes it up, but Notepad++ preserves the linux stuff so you can still flash it. Edit the file and remove the first line that says "assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");" without the quotes. Save and Close the file and it will ask if you want to update it in the archive, say yes. That's it, just transfer it to your phone and voila!
Hope this help some others out there!

majorassface said:
This actually works for cwm as well and any rom that throws that error when flashing and doesn't need to be done on a linux box. The way I do it, is open the zip using winrar, don't extract it, navigate to the updater-script and open it with Notepad++, notepad or wordpad messes it up, but Notepad++ preserves the linux stuff so you can still flash it. Edit the file and remove the first line that says "assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");" without the quotes. Save and Close the file and it will ask if you want to update it in the archive, say yes. That's it, just transfer it to your phone and voila!
Hope this help some others out there!
Click to expand...
Click to collapse
Nice! I'll give this a shot when I get home. I always love knowing little tidbits like this as I'm sure it'll save me in the future sometime too.

[RECOVERY][Unofficial] TeamWin Recovery Project - 2.8.4

TeamWin Recovery Project ​
Restore in the old 2.4.1 version doesnt work for me. I build from source, now it works, I share.
Download
http://dualhoki.vim.hu/bubor/dev/twrp-i927/
http://rpi.bubor.hu/bubor/dev/twrp-i927/
Current Issues:
display timeout blank screen disabled
Issue report:
Give everything I need to reproduce the problem (logs, guide, dumps etc), I wont reply useless reports.
Changelog:
Changelog can be found : http://www.teamw.in/project/twrp2
2.6.1 wipe data make smaller data partition, that need for encyption. Encypt mount support.
2.6.3 removed superuser, compiled with cm-10.2
2.6.3-2 add fuse, it should support extfat
2.6.3-3 remove encypt, puth superuser (Rooting)
2.6.3-4 put security fs, selinux, it will need for flash cm-11.0
2.6.3.1 update twrp from git (actually its 2.7.0, but you will see 2.6.3 in the corner)
2.7..1: update twrp, compiled with cm-10.2
2.8.4: compild with cm-11.0, fix MTP
Credit:
Terinfire(Source)
Dman(Source)
thegreatergood
TWRP TEAM
Install
Install zip from TWRP or ClockworkModRecovery
Put device to download mode ( power on, while hold volume up, hit volume up again when asked to do ), and use odin (included in the zip, browse to pda, dont flash other)
Changelog: http://www.teamw.in/project/twrp2
You may want to install older rom, you must change assert tag in rom zip file META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "i927" || getprop("ro.build.product") == "i927" ||
getprop("ro.product.device") == "SGH-I927" || getprop("ro.build.product") == "SGH-I927" ||
getprop("ro.product.device") == "SGH-I927R" || getprop("ro.build.product") == "SGH-I927R" ||
getprop("ro.product.device") == "SGHI927" || getprop("ro.build.product") == "SGHI927" ||
getprop("ro.product.device") == "SGHI927R" || getprop("ro.build.product") == "SGHI927R" ||
getprop("ro.product.device") == "n1" || getprop("ro.build.product") == "n1" || abort("This package is for \"i927,SGH-I927,SGH-I927R,SGHI927,SGHI927R,n1\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

Awesome! Thanks so much for fixing this for Team Glide!
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 CM10.1 & TWRP 2.4.4.0 using xda-dev app.

They just released a newer version 2.5.0.0
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 & TWRP 2.4.4.0 using xda-dev app.

*thanks bubor for keeping twrp up to date.
*please keep twrp up to date since it can then use rom manager to do all the wipes, flash and install roms and gapps package an dother patches along he way.
*can the img extension just be use through adb to get that to the phone or not?
*how is this done and steps pleas?

dd if=recovery.img of=/dev/block/mmcblk0p8
You can find recovery.img inside the zip.

update to 2.6.1

Oh my...
I think this is one of the best finds for the Cappy Glide since CM10.1...
Thank you! Thanks SOOOOO MUCH!
I was about fed-up with CWMR, having to spam the volume buttons, but now with touch controls, I mean, COME ON! How much better could it get to flash and recover and restore and backup stuff! Thank you! BIG THUMBS UP!
:good::good::good::good::good:

great thanks, its time to udate it. i see we have a version from odin and one to flash via CWMR.

Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2

AndyYan said:
Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.

Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.

amppcguru said:
Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.
Click to expand...
Click to collapse
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.

TWRP 2.6.3 bu failure
bubor said:
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.
Click to expand...
Click to collapse
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0

amppcguru said:
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0
Click to expand...
Click to collapse
try to rename TWRP to TWRP2,and lets it creates new one.

2.6.3 backup unable to create folder
bubor said:
try to rename TWRP to TWRP2,and lets it creates new one.
Click to expand...
Click to collapse
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!

2.6.3
Doesn't seem capable of mounting 64gb exfat formatted SDXC card.
Just says failed to mount or something along those lines, mounted a 8gb FAT32 card, wouldn't mount an old FAT 512mb card.
I know for a fact the 2.6.1 is capable of mounting the 64gb exfat card. Flashed back to it and no issues.

amppcguru said:
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!
Click to expand...
Click to collapse
I had the same error, so i just downloaded nandroid backup from the play store, and it works wonders if you choose TWRP as your recovery.
Sent from my SGH-I927 using XDA Premium 4 mobile app

I also had the same problem, but with d2att - changed the auto generated backup name and it worked (also fixed permissions but not sure if it was necessary to or not).

bubor said:
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.
Click to expand...
Click to collapse
Went to older recovery, still not able to flash.
WTF?
Sent from my SGHI927 using Tapatalk

Changing the auto-generated name fixed for me too.

Problem when i want flash my custom rom

Hello everyone i want create my custom rom(zenitude) with other developers and when i want flash the rom i have that " Updating IFWI"....With twrp it's very very very long ...
I try to flash with adb sideload and i have this message too.. it work...but it's very very very long...1hour and it's flashed at 51%...
What is the problem?? thank

quadeur06 said:
Hello everyone i want create my custom rom(zenitude) with other developers and when i want flash the rom i have that " Updating IFWI"....With twrp it's very very very long ...
I try to flash with adb sideload and i have this message too.. it work...but it's very very very long...1hour and it's flashed at 51%...
What is the problem?? thank
Click to expand...
Click to collapse
Unmount /system. I recall running into that too. Pretty sure making sure system was unmounted solved the issue.
Code:
ifelse(is_mounted("/system") == "/system", unmount("/system"));
Drop that above your package_extract_file("ifwi.zip", "/tmp/ifwi.zip")
Then of course mount it again before extracting your /system.

Harfainx said:
Unmount /system. I recall running into that too. Pretty sure making sure system was unmounted solved the issue.
Code:
ifelse(is_mounted("/system") == "/system", unmount("/system"));
Drop that above your package_extract_file("ifwi.zip", "/tmp/ifwi.zip")
Then of course mount it again before extracting your /system.
Click to expand...
Click to collapse
I wiil try thank

Can't BOOT CyanogenMod

EDIT: I fixed it, I tried to install again with MODEM and success .
I had CM13 and wanted to upgrade version. Removed this version and tried to install newest version. It gave me an error ("It appears you are running an unsupported baseband") and i found this solution and did it:
Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:
1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.
2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)
3. Open the extracted files folder
4. Open "META-INF" ==> "com" ==> "google" ==> "android"
5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.
6. Delete this line of code:
assert(getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "vs985" || getprop("ro.build.product") == "vs985" || abort("This package is for device: g3,vs985; this device is " + getprop("ro.product.device") + ".");
assert(g3.verify_baseband("35B:MPSS.DI.2.0.1.C1.13 .4-00005") == "1");
7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.
8. Overwrite the edited "updater-script" back to it's directory (the android folder)
9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))
10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"
11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)
12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"
13. The edited one^ is the only one you need now, and is the one you will be flashing
14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.
Click to expand...
Click to collapse
After that i installed and opened it. It started to give me ''Google Play services stopped'' error. I tried to install again and after that it didn't boot. I learned that there is a problem with this version. After this i tried to install 03.23 (3 days later -they said that it's best stable version at now-) version but it didn't boot again (i saw LG logo and after that black screen). Tried to install CM12.1 but same happend again.
I'm waiting your helps!

10+ eXYNOS BOOTLOADER REMOVED

First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing

link is restricted

Bro. Share file pls on your googledrive. We cantdownload it

Flar4eg said:
Bro. Share file pls on your googledrive. We cantdownload it
Click to expand...
Click to collapse
Excuse me, is that I uploaded the files to my google drive cloud and I detect a dll, or part of the flashtool as a virus, now I upload it again and put the link

https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI

multiuploader error: WinDNWApi.dll file could not be found.

Skyfall191299 said:
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Click to expand...
Click to collapse
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing

Skyfall191299 said:
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
Click to expand...
Click to collapse
getting error that el3mon_dram not found. can you help me?

Hello someone has the files ? The download link is inactive

The download link is inactive, please active or reupload please.

Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
good jod
im follwed to this instruction but all links not woriking
pla give me ur telegram or whtas app
and upload files to the new link plz

eldon301 said:
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Click to expand...
Click to collapse
how to create with hex bro ?

links not woriking

link isn't working please fix

akbarshoxdedamirzayev said:
how to create with hex bro ?
Click to expand...
Click to collapse
Find the exact firmware that’s currently in the device, extract sboot from the firmware. You need to find correct location of bl1 bl2 el3 and others, names correspond to which is cut. You need 5 files from sboot. Am stuck on the forth file failing and I still don’t understand how to find them. What I did was follow others with exactly the same problem to see and understand how they got there’s and then tried it on my sboot. I am failing on part4 don’t even know how to make a cfg but from what I understand e for exynos and the number after so mine is e7885. Still not sure like I said

http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip/file download link

Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
Can you check the addresses and lenghts of the partitions cut out of sboot?
I think you've made a mistake.
Can give me the precise partition details?
Are you 100% positive that this is valid at least for most devices of the same chipset?
I'd like to try to make an automated script or a tool of some sort.
Also when I was dividing my A515F U5 sboot I've spotted some long breaks in data which I assumed were empty blocks at the end of partitions.
What confused me about it is that I didn't find those where you said partitions are ending.
Can you demonstrate graphically your partitions in a linear projection?

It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares

eldon301 said:
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
Click to expand...
Click to collapse
I'd like to help

NonStickAtom785 said:
I'd like to help
Click to expand...
Click to collapse
Hello my friend I am try to get life back into a A750G, it’s completely hard bricked showing exynos usb in device manager. Can i direct message you or should I keep it in the forums. I was falling on part 4 off the files needed to create, I didn’t even know if my cfg file was correct but I tried my best at understanding the creation of the files. Plz help my brothers