(adsbygoogle = window.adsbygoogle || []).push({}); I've converted to DEX and I've installed 4.50ITA, when I try to RTM online I can connect in Target Manager. But when I try to attach the process I don't see any processes available in the debugger. I'm using a Debug EBOOT, please help!
(IDK if this is the correct section)

your using the wrong eboot mate debug eboots are for rebug firmware you need a dex eboot for ita cfw

I was on rebug before, but I changed firmware because of a problem with a mod menu.
Can you send me a DEX EBOOT for GTA V?

It doesn't matter what debug eboot you have got, you are just putting it in the wrong folder! Here is what you need to do. Open multiman on your ps3 and FileZilla on you PC/laptop now connect your ps3 with your ip to FileZilla once you have done that head to dev_hdd0 now click game NOT GAMES find your folder for your debug eboot to be dropped in and replace the standard eboot that's in there so it will look something like this: dev_hdd0/game/bl*s/usrdir then your eboot. Once you have done that load the game you want to rtm and wait about 3seconds then open debugger and click auto refresh on the top panel of debugger then your eboot should show, right click and the click attach process and then continue with no symbols now head over to your target manager and under your ps3 ip on the left hand side click the arrow and your list will drop down click on kernel and press the play button once that has done close the debugger and completely exit out of target manager so it's not running at all, now open your rtm tool and click tmapi and connect your ps3 then click attach process and you now should be able to rtm with tmapi if there is anything I have missed out or have any problems please feel free to add me on Skype and I will be happy to help further my Skype name is CHIPPAUK1 hope this guide works for you

Read the comment mate

You can use debug eboot with dex firmware I'm on exactly the same firmware and I always use debug eboots without a problem

Thanks dude, it worked.

I've had exactly the same problem as you dude and I know debug eboots works cuz I'm on exactly the same firmware as you