Homebrew RELEASE Rekado - payload launcher for Android OS

MK73DS · May 24, 2019

mars0124 said:
I'm using an S6 Edge+ with default firmware and rooted. Same thing: my device doesn't even recognize the switch. I know my OTB A to B works for other USB devices (headphones or storage), but connecting a USB C cable doesn't work. FYI, the USB C cable is the same one I use to push Hekate from my PC.

It didn't work on my S7 and my Oreo Note 9 neither. But the Pie update for the Note 9 fixed it, so I think it's related to Samsung Experience (Samsung's OS for Android Oreo)

miraclaime · May 24, 2019

hello, i have an otg and usb c cable and a vivo v11 phone this phone support otg

this is the otg (i try my flashdisk in it and it appear the otg work as intended)

and i can confirm my usb c can send payload flawlessly when i try to inject thru pc

however whenever i try to inject payload using phone it always show the same error code (offset 65536), i also try using nxloader and the error shown the same number 65536
i try using different payloads and still the same error
what does this error offset means, where did my poor phone go wrong pls help!

error ss

OrGoN3 · May 24, 2019

miraclaime said:
hello, i have an otg and usb c cable and a vivo v11 phone this phone support otg

this is the otg (i try my flashdisk in it and it appear the otg work as intended)

and i can confirm my usb c can send payload flawlessly when i try to inject thru pc

however whenever i try to inject payload using phone it always show the same error code (offset 65536), i also try using nxloader and the error shown the same number 65536
i try using different payloads and still the same error
what does this error offset means, where did my poor phone go wrong pls help!

error ss View attachment 168001

That error is almost always when using a bad cable. Perhaps your USB A to C cable is too long or faulty? Here is someone with the exact same issue, using the same OTG adapter https://github.com/MenosGrante/Rekado/issues/12

miraclaime · May 24, 2019

OrGoN3 said:
That error is almost always when using a bad cable. Perhaps your USB A to C cable is too long or faulty? Here is someone with the exact same issue, using the same OTG adapter https://github.com/MenosGrante/Rekado/issues/12

uhh yeah same problem, hmm weirdd i can use my cable just fine when i push with pc jst like he said, soo which cable i should get, i dont understand waht he mean by original cable

mo_v · May 31, 2019

Hey I'm getting an error saying "Sending payload failed at offset 94208"

Menos · Jun 3, 2019

Update 3.0 released!

Changes

Added: Check for the possibility of hacking the console by serial number.
Added: Ability to download payloads from Internet by direct URL (thanks to @ELY3M)
Design improvements.
List of translators moved inside application to toolbar's menu.
Localization process moved to OneSky to easily handle it.

Source code | Download | Support development

ELY_M · Jun 3, 2019

I get my cables from Target. go to target and find very nice colored cables. they work great for me.

Hacktendo · Jun 12, 2019

Menos said:
Yeah, I have already released 1.0.1 update. It contains of hot fix for the bug with the choice of payloads using the standard file manager.

Have a good day!

Using the latest rekado, downloaded it yesterday. For a month or so it will only shoot the payload to my switch like 1/10 times... I bought an USB-C dongle because it actually works 10/10 times.
I'm a GNote9 user.

linuxares · Jun 12, 2019

Remeber guys, I learned from a fellow OnePlus user here. That some phones you need to enable OTG in System Settings of the phone.

Hacktendo · Jun 12, 2019

linuxares said:
Remeber guys, I learned from a fellow OnePlus user here. That some phones you need to enable OTG in System Settings of the phone.

OTG works on most Galaxy phones right out of the box. Hell, since the gs6 or gs7, Samsung even include an OTG adapter in box.

DM1 · Jun 13, 2019

Seeing mixed things about Galaxy S7 working, anyone figure anything out about this?

It supports OTG, mine works fine (tested and used on multiple other devices, with same cable/adapter) but I can't for the life of me get Rekado or NXLoader to pick up my Switch in RCM mode. Even detects my Switch while it's regularly booted/running horizon. I'm not sure what's up with it.

Hacktendo · Jun 13, 2019

DM1 said:
Seeing mixed things about Galaxy S7 working, anyone figure anything out about this?

It supports OTG, mine works fine (tested and used on multiple other devices, with same cable/adapter) but I can't for the life of me get Rekado or NXLoader to pick up my Switch in RCM mode. Even detects my Switch while it's regularly booted/running horizon. I'm not sure what's up with it.

I also own a S7 Edge since it was my phone before I switched to the Note 9.
The same issue I posted the other day here about my my s9 also was the same issue for my S7E.
I think it's an issue with the app because most Galaxy phones come with OTG support straight out of the box.
This is why I bought an usbc RCM loader.
Works 10/10 times unless it's dead.

DDinghoya · Jun 13, 2019

Would you please add Korean language for Rekado on OneSky?

Menos · Jun 13, 2019

DDinghoya said:
Would you please add Korean language for Rekado on OneSky?

Yes, added.

DDinghoya · Jun 13, 2019

Menos said:
Yes, added.

Done!

spotanjo3 · Jun 13, 2019

Menos said:
Rekado is payload launcher written in Kotlin and based on NXLoader injector codebase. Application doesn't require Root on your device. SX Loader, ReiNX and Hekate payloads bundled as default.

Download

The main difference from NXLoader is the ability to quickly change the payloads you need by preloading them. You can choose any needed payload once the USB cable connected to your Switch.

If you will find any issues feel free to report it. Or maybe you have some good ideas, you can also tell me about them.

I am open any kind of pull requests (especially for new languages support).

Source code

Support development

According to this:

SX Loader, ReiNX and Hekate payloads bundled as default.

Why don't you put atmosphere in there as well ? And what about Portuguese/Portugal ??

Akorax · Jun 17, 2019

Hi! Samsung Galaxy S7 here.
Using AutoRCM I can inject the payload just fine with a USB-A to USB-C cable + the microUSB to USB-A adapter that came with the phone.
I also tried a OTG adapter which didn't work. Some people here write about it possibly being a "one way"-adapter and I think that would make sense. (Edit: I later verified this with the clerk which sold it to me)
Right now Atmosphere 0.9.0 isn't booting for me but I recon that's an unrelated issue to this thread.

Edit: It should absolutely be mentioned in the OP and in the guides about OTG-adapters and them being one way sometimes (all times?).
That being said, it's actually pretty much as expensive to buy a "payload sender-3Dprinted USB-C thingie" from the web than these adapters.

miraclaime · Jun 21, 2019

Splendid! i bought new cable and i can inject payload now no more stupid 65536 again.
Maybe the fast charging that comes from the cable is the key here, my old cable seems doesnt support this feature but im not sure because i don't have a way to check.

oh yea for you if you have same problem as mine, im using a less than $1 cheap otg (honestly whichever otg is fine as long as your phone can read it) and vivan bc100 fast charge 3.0 A to type C cable, it cost $3
and dont forget to enable otg in settings

this cable, cheers

EbTar · Jun 28, 2019

I am using the OTG adapter supplied with my Samsung s8 to inject the bundled payload (Hekate; Rekado 3.0)

But I get this error: sending payload failed at offset 61440

The cable I use it the one supplied with my 8bitdo sn30 pro controller. It works perfctly fine injecting payloads from Tegra on PC and the web injector on chrome (MacOS)

Any ideas?

Thanks.

Hacktendo · Jun 30, 2019

People still use this app? It works like 0% of the time.
And yes my phone is OTG ready out of box.
Samsung wouldn't include one in box if it wasn't.

--------------------- MERGED ---------------------------

Akorax said:
Hi! Samsung Galaxy S7 here.
Using AutoRCM I can inject the payload just fine with a USB-A to USB-C cable + the microUSB to USB-A adapter that came with the phone.
I also tried a OTG adapter which didn't work. Some people here write about it possibly being a "one way"-adapter and I think that would make sense. (Edit: I later verified this with the clerk which sold it to me)
Right now Atmosphere 0.9.0 isn't booting for me but I recon that's an unrelated issue to this thread.

Edit: It should absolutely be mentioned in the OP and in the guides about OTG-adapters and them being one way sometimes (all times?).
That being said, it's actually pretty much as expensive to buy a "payload sender-3Dprinted USB-C thingie" from the web than these adapters.

You wasted time. Your adapter works, just the app itself is a POS.

--------------------- MERGED ---------------------------

miraclaime said:
Splendid! i bought new cable and i can inject payload now no more stupid 65536 again.
Maybe the fast charging that comes from the cable is the key here, my old cable seems doesnt support this feature but im not sure because i don't have a way to check.

oh yea for you if you have same problem as mine, im using a less than $1 cheap otg (honestly whichever otg is fine as long as your phone can read it) and vivan bc100 fast charge 3.0 A to type C cable, it cost $3
and dont forget to enable otg in settings

this cable, cheers
View attachment 170759

Fast charging isn't in the cable, it's the block you plug in the wall...

Homebrew RELEASE Rekado - payload launcher for Android OS

Non-commutative algebra

custom themes maniac

Well-Known Member

custom themes maniac

Member

Well-Known Member

Developer

Well-Known Member

The inadequate, autocratic beast!

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

custom themes maniac

Member

Well-Known Member

Similar threads

Popular threads in this forum