Separate names with a comma.
By Kotomine Kirei, Sep 1, 2018
11,299 34 0
Are there any sites that have the R4S or SX Pro that are entirely in the US?
Its a guitar pick for opening up the kickstand, I got one of those switches where the kickstand takes alot of force to open it.
Nope, seems to be the same.
2 version SX Pro? Wow, I never know that. And I just saw the SX Gear release news here, however, no announcement from TX.
if you already have the SX OS then there is no difference except the size of the r4s dongle is bigger than SX.
and R4S is programmable to use another payload like ReiNX or Hekate.
of course there is a difference in the internals but both does the job.
They use different methods to achieve the same result - the SX dongle is programmed to load a boot.dat on the SD card whereas many other dongles have the payload programmed onto the dongle (I assume this is why ReiNX has self-chainloading now - to update on the SD card without having to reprogram the dongle).
People with an SX dongle can still boot other payloads without having to use the SX payload first, they just have to take a few extra steps.
This will convert any payload to a boot.dat https://gbatemp.net/threads/turn-any-rcm-payload-into-boot-dat-for-usage-with-sx-pro.511052/
Ave's buildbot also has a version of hekate CTC compiled as a boot.dat. I use this to be able to keep using my SX dongle without having to use the SX software.
Larger, heavier, and r4s dongle, it features a propriety format of the CFW. Personally, I will choose SX Gear.
3DS-Flashcard, they keep the SX Pro in USA and EU stock. But they doesn't sell R4s dongle, don't know the reason.
OR , you can just use the boot.dat for Sx gear NOT the one for Sx pro (download on Tx official website) put it on the root of your microsd and use any payload you want (Hekate, Reinx, Rajnx..).
Just rename the payload to »payload.bin« put it on the root of your microsd and it will boot straight to your CFW or else.
The fact is that I don’t find this « trick » very « useful » , except from saving extra steps , as if you buy an Sx pro, you get Sx Os that allow to launch any payload via its boot menu, but well...
What are you talking about? You literally just repeated the exact same process I described.
Nope... you´re talking about converting a payload into a boot.dat to use with Sx pro, and I’m talking about « just » renaming any payload into « payload.bin » and use it with the boot.dat provided by TX for Sx Gear, no converting in this process or use of a «
custom boot.dat »
It’s not the same process
Sorry, I just realised my mistake. I actually described the same SX Gear process in another thread and assumed it was this thread. My bad.
Id go with SX for one reason. Boys keep updating it like its Christmas time
No worries mate...