Hacking Problem using app2USB : "The defined MOUNT_POINT is incorrect"

[Gingerz]

I formatted a 4TB usb drive on Mac but when running app2USB I keep getting this error:

"The defined MOUNT_POINT is incorrect. MOUNT_POINT=0 is defined but the drive is mounted to USB1"

I now get the same error when formatting the same drive on my PC.

Any solutions?

 

[Gingerz]

Just to clarify, I wanted to use the HDD to run fake PKG files I had downloaded, and had my INI file set up accordingly.

 

[KiiWii]

Plug it into a different USB socket (right is 1, left is 0 iirc), or better use HEN 2.1.1 and extended storage rather than App2USB.

 

[Gingerz]

I was sincerely hoping that it was something as simple as the USB port, but alas it's not.

Does Hen 2.1.1 allow you to use fake PKG files?

And how would I do that? Please excuse my ignorance here.

 

[webslingr]

Hey Gingerz...u ever figure this out ? I have the same error...also 4tb external formatted on my MacBook.
I've tried every usb slot....what gives ??

 

[Leeful]

Just change the MOUNT_POINT number in the AppToUsb.ini in the PS4 folder on the USB.

 

[webslingr]

Hey Leeful. Hate to be an idiot here...but could you explain further....or point to another guide. I used Modded Warfares vid. is it dated?
I don't have any ini files in the PS4 folder...just one on the root....and I don't see a mount point number in the file ??
Thanx much

 

[Leeful]

The AppToUsb.ini file should be in the PS4 folder on your USB drive not on the root.
If you get an error saying that the mount point is incorrect like it says in the OP change the MOUNT_POINT=0 value in the ini file to MOUNT_POINT=1

Make sure you are using the latest version of AppToUSB the ini file should look something like this:

To skip copying pkg files to this hdd uncomment the line below.
be aware when using this if your usb mount points switch it will break the links and the games will not load until you plug the drives back in the correct order.
//SKIP_DRIVE

When using skip drive and mulitple drives at the same time you need to specify the intended mount point of the usb hdd.
your first drive should be 0 and second drive should be 1 ending at a maximum of 7.
this will prevent the payload writing usb0 links to the usb1 drive if the mount points switch on the console.
MOUNT_POINT=0

To check the usb root for the pkg file to save time copying from the internal ps4 drive then uncomment the line below.
but remember this will move the pkg from the root directory to the PS4 folder.
//CHECK_USB

To rename previously linked pkg files to the new format uncomment the line below.
//RENAME_APP

To disable the processing of icons/art and sound uncomment the line below.
//DISABLE_META

To leave game updates on the internal drive uncomment the line below.
//IGNORE_UPDATES

To move DLC to the usb hdd uncomment the line below.
MOVE_DLC

To use this list as a list of games you want to move not ignore then uncomment the line below.
MODE_MOVE

Example ignore or move usage.

CUSAXXXX1
CUSAXXXX2
CUSAXXXX3

 

[webslingr]

Update: Found the new AppToUsb file on git...but same thing. Tried changing the mount point in the doc...and on ps4...but kept geting same error. So not sure whats up....may just have to go with the Extended storage option ?? Kinda liked the idea of being able to use the drive for multitask...but maybe not in the cards. On another note, Al's 6.72 JB on DNS host has been really stable for me last couple days

 

[Leeful]

Update: Found the new AppToUsb file on git...but same thing. Tried changing the mount point in the doc...and on ps4...but kept geting same error. So not sure whats up....may just have to go with the Extended storage option ?? Kinda liked the idea of being able to use the drive for multitask...but maybe not in the cards. On another note, Al's 6.72 JB on DNS host has been really stable for me last couple days

Have you tried formatting the USB drive to exFAT on the PS4 itself. Go to Settings>Devices>USB storage Devices and when you select your USB press options and select Format as exFAT.

Maybe whatever method you are using to format it as exfat is not partitioning it correctly.

 

[webslingr]

Have not tried that Lee. Its a drive I had formatted exFat on my MacBook year or so ago. Makes me wonder tho...cuz the other guy with this error was on a mac as well. Lot of packages on it right now as that was the drive I was using to load my PS4. So, if i re-format...its gonna take some time...gotta find a temp placeholder for a couple tb....alll my devices will be loaded with fpkgs for a couple days

 

[Leeful]

Maybe the mac is creating an extra blank partition at the start of the drive. This might be what the problem is. Doing it on the PS4 is the best way to ensure compatability.

 

[webslingr]

Yeah...thinking something like that. I'll report back if I re-format...thanx for giving it a look.

 

[webslingr]

Another weird detail....after it fails and I check the PS4 folder contents, there is always another .ini file present...but it is spelled app2usb.ini. Obviously, the app creates this folder. Why...I'm not sure? And, it's odd that the process starts, finds the PS4 folder, creates the new .ini file, and then fails? Unforunately, I don't know enough about how the app works to know how that is possible...but that may be a clue to the underlying problem??

 

[qamartheone]

link to latest app2usb.ini file for 5.05?

 

[Leeful]

Another weird detail....after it fails and I check the PS4 folder contents, there is always another .ini file present...but it is spelled app2usb.ini. Obviously, the app creates this folder. Why...I'm not sure? And, it's odd that the process starts, finds the PS4 folder, creates the new .ini file, and then fails? Unforunately, I don't know enough about how the app works to know how that is possible...but that may be a clue to the underlying problem??

I've looked into it and I've found out what the problem is.
The original AppToUSB by Stooged uses AppToUsb.ini but in the one made by Al Azif (Scene Collective) has changed the name in the source files to app2usb.ini

So if you are using the Original by Stooged it must be named AppToUsb.ini but if you are using the ported one that works on 6.72 by Al Azif it must be named app2usb.ini

 

[COLDfiction]

Leeful,
Is there a guide that explains App2Usb in further detail for either Stooged or Al's? I can't get the new 6.72 exploit to launch any FPKG files that worked on my previous 5.05 exploit via external USB or internal memory from 2 years ago. When trying to launch each FPKG file from home screen I get the message 'Cannot use the content' or trying to launch in library the same file with return message 'Update the system software to use network features'. I can only launch FPKG files that were installed recently after updating to 6.72 and installing via debug/game/package installer.

I believe I used stooged version 2 years ago to move all the FPKG files that I installed to internal PS4 HD to external USB that previously worked on 5.05. I then backed PS4 folder from that external USB with all the CUSAxxxxx files to another external USB HD in the same format which I am using now(original USB bricked). I updated FW to 6.72 and then ran your v5 and v6 exploit + HEN with success but the new external USB with CSAXXXX files doesn't launch any files in library.

I was thinking it was an issue with my profile, database or the link associated with each file when first installed and transferred to USB that is preventing this. I was hoping to fix these issues by running apps2usb again but hoping to skip having to install all of the FPKG files again. I followed moddedwarfares probably dated guide which states to drop ini file in root of external USB. I filled out the below ini and dropped it in the root of my new USB and ran App2USB payload from your exploit menu. It says it completed but still no files launch and like previous user webslinger i noticed another file was created by apps2usb in the PS4 folder.

To check the usb root for the pkg file to save time copying from the internal ps4 drive then uncomment the line below.
but remember this will move the pkg from the root directory to the PS4 folder.
CHECK_USB
To rename previously linked pkg files to the new format uncomment the line below.
//RENAME_APP
To disable the processing of icons/art and sound uncomment the line below.
//DISABLE_META
To leave game updates on the internal drive uncomment the line below.
IGNORE_UPDATES
To move DLC to the usb hdd uncomment the line below.
//MOVE_DLC
To use this list as a list of games you want to move not ignore then uncomment the line below.
//MODE_MOVE
Example ignore or move usage.
(all FPKG files in new external USB HD in PS4 folder in CUSAXXXXX format)

 

[Leeful]

Leeful,
Is there a guide that explains App2Usb in further detail for either Stooged or Al's? I can't get the new 6.72 exploit to launch any FPKG files that worked on my previous 5.05 exploit via external USB or internal memory from 2 years ago. When trying to launch each FPKG file from home screen I get the message 'Cannot use the content' or trying to launch in library the same file with return message 'Update the system software to use network features'. I can only launch FPKG files that were installed recently after updating to 6.72 and installing via debug/game/package installer.

I believe I used stooged version 2 years ago to move all the FPKG files that I installed to internal PS4 HD to external USB that previously worked on 5.05. I then backed PS4 folder from that external USB with all the CUSAxxxxx files to another external USB HD in the same format which I am using now(original USB bricked). I updated FW to 6.72 and then ran your v5 and v6 exploit + HEN with success but the new external USB with CSAXXXX files doesn't launch any files in library.

I was thinking it was an issue with my profile, database or the link associated with each file when first installed and transferred to USB that is preventing this. I was hoping to fix these issues by running apps2usb again but hoping to skip having to install all of the FPKG files again. I followed moddedwarfares probably dated guide which states to drop ini file in root of external USB. I filled out the below ini and dropped it in the root of my new USB and ran App2USB payload from your exploit menu. It says it completed but still no files launch and like previous user webslinger i noticed another file was created by apps2usb in the PS4 folder.

To check the usb root for the pkg file to save time copying from the internal ps4 drive then uncomment the line below.
but remember this will move the pkg from the root directory to the PS4 folder.
CHECK_USB
To rename previously linked pkg files to the new format uncomment the line below.
//RENAME_APP
To disable the processing of icons/art and sound uncomment the line below.
//DISABLE_META
To leave game updates on the internal drive uncomment the line below.
IGNORE_UPDATES
To move DLC to the usb hdd uncomment the line below.
//MOVE_DLC
To use this list as a list of games you want to move not ignore then uncomment the line below.
//MODE_MOVE
Example ignore or move usage.
(all FPKG files in new external USB HD in PS4 folder in CUSAXXXXX format)

1. The ini should be in the PS4 folder not the root. (thats why it created a new one there)
2. Looking at the source code of SceneCollective 6.72 port of AppToUsb again I think there is a problem. I'll fix it and recompile a new payload.
To test it, do you know how to to send bin files to your PS4 using BinLoader? This would make my life a lot easier.

EDIT: As a tempory work around on 6.72 put 2 identical ini files in the PS4 folder. Name one version AppToUsb.ini and name the other app2usb.ini
Make sure they are named exactly as above as they are case sensetive and make sure they contain the same settings you want to use.

 

[COLDfiction]

1. The ini should be in the PS4 folder not the root. (thats why it created a new one there)
2. Looking at the source code of SceneCollective 6.72 port of AppToUsb again I think there is a problem. I'll fix it and recompile a new payload.
To test it, do you know how to to send bin files to your PS4 using BinLoader? This would make my life a lot easier.

EDIT: As a tempory work around on 6.72 put 2 identical ini files in the PS4 folder. Name one version AppToUsb.ini and name the other app2usb.ini
Make sure they are named exactly as above as they are case sensetive and make sure they contain the same settings you want to use.

I'm not familiar with sending files to PS4 with BinLoader but I'm sure I can get versed rather quickly. I will follow your instructions for 2 identical ini files right now that I will place is PS4 folder in the interim since that is just case sensitive renaming to see if one catches and fixes the problem.

Thanks for the incredibly fast reply/instruction. I just didn't understand the fpkg file install/transfer structure and wasn't sure should I delete all previous debug installs from 2 years ago from library and reinstall which would be a colossal waste of time and then use the ini and payload to transfer to usb and leave the fpkg in root of usb to save the time of transferring from ps4 to usb.

 

[COLDfiction]

It's working for new debug installs now(6.72 fpkg). It still isn't linking previous 5.05 installs. Should I delete 5.05 fpkg files from internal and debug reinstall from usb root and then use app2usb again with fpkg on root to at least skip ps4 to usb transfer time? If so, is there a way to debug install mass batch faster? I think you previously posed transfer speeds of different methods I may need to read through again. Also once app2usb is complete and fpkg is working from usb how do i delete the original file from internal? System Storage/Applications/Select File/Options/Delete? I thought I read that deletes the initial install.