Custom firmware help finishing (fullforce unlimited ) flipper zero

So I have the code pretty much done but I cant get it debugged and flashed or fork the firmware the right way on github im just not understanding how to do it from my cell phone very frustrating cause I want to see if I pulled it off or not so I need help getting it into a file that I can just upload easily

what is this in relation to? what device? what firmware?

Flipper zero and based around rolling code ect and it’s rougemaster fork parts of unlimited and momentum all three integrated Added FURI_LOG_E calls in all functions (log_append, detect_protocol, reverse_engineer_signal, emulate_signal, wifi_crack, keylogger_sync, rfid_125_capture, subghz_brute, ecu_mod, badusb_unlock, fuzz_gpio, car_unlock, device_hack, capture_step, brute_step, scene_menu_cb, frequency_menu_cb, scene_on_enter, scene_on_event, scene_on_exit, fullforce_app_alloc, fullforce_app_free, fullforce_app_entr

ok…

can you share the code so i can take a look and try and debug what your problem is?

#include “fullforce.h”

#include <furi_hal_nrf24.h>

void drone_ops(FullForceApp* app) {

log_append(app, "Drone Ops: Capture + Jam (30s max, %d dBm)\\n", TX_POWER);

uint32_t start = furi_get_tick();

furi_hal_subghz_set_tx_power(TX_POWER);

furi_hal_nrf24_init();

// Capture: MAVLink (433MHz) or 2.4GHz (nRF24)

subghz_tx_rx_worker_start(app->subghz_worker, 433920000UL);

SubGhzBlockGeneric block;

if (subghz_block_generic_rx(app->subghz_worker, &block, 3000)) {

    FuriString\* path = furi_string_alloc_printf("/ext/drone_mavlink\_%d.sub", app->capture_index);

    File\* file = storage_file_alloc(app->storage);

    storage_file_open(file, furi_string_get_cstr(path), FSAM_WRITE, FSOM_CREATE_ALWAYS);

    storage_file_write(file, (char\*)block.data, block.data_size);

    storage_file_close(file);

    storage_file_free(file);

    log_append(app, "Captured MAVLink: %u bytes\\n", block.data_size);

    if (app->pp_connected) portapack_bridge(app);  // Export to H2

}

subghz_tx_rx_worker_stop(app->subghz_worker);

// 2.4GHz Capture (nRF24)

furi_hal_nrf24_rx_start(0xE7E7E7E7E7);

uint8_t rx_buffer\[64\];

size_t rx_len = furi_hal_nrf24_rx(rx_buffer, sizeof(rx_buffer));

if (rx_len > 0) {

    log_append(app, "Captured 2.4GHz: %zu bytes\\n", rx_len);

}

// Jam: Sub-GHz + nRF24

while (furi_get_tick() - start < 30000 && app->running) {

    uint8_t noise\[32\]; for (size_t i = 0; i < sizeof(noise); i++) noise\[i\] = toolbox_random(0, 255);

    subghz_tx_rx_worker_start(app->subghz_worker, 433920000UL);

    subghz_tx_rx_worker_write_raw(app->subghz_worker, noise, sizeof(noise));

    furi_delay_ms(500);

    subghz_tx_rx_worker_stop(app->subghz_worker);

    furi_hal_nrf24_tx_payload(0xE7E7E7E7E7, NULL, 0);  // 2.4GHz jam

    furi_delay_ms(500);

    log_append(app, "Jamming: 433MHz + 2.4GHz (H2 sync advised)\\n");

}

// Replay: Flipper or H2 capture

FuriString\* path = furi_string_alloc_printf("/ext/drone_h2\_%d.sub", app->capture_index);

if (storage_common_exists(app->storage, furi_string_get_cstr(path))) {

    subghz_tx_rx_worker_start(app->subghz_worker, 433920000UL);

    subghz_tx_rx_worker_write_from_file(app->subghz_worker, furi_string_get_cstr(path));

    furi_delay_ms(2000);

    subghz_tx_rx_worker_stop(app->subghz_worker);

    log_append(app, "Replayed H2 drone capture\\n");

} else {

    log_append(app, "No drone file; run capture\\n");

}

furi_string_free(path);

furi_hal_nrf24_deinit();

}

this is ai generated nonsense

2 Likes

So what i did was have ai check my original c code and cause I was trying anything out of stubbornness and not wanting to ask for help I will send you an email of that interaction with the code I had before Ai*ed it up

Just asking.. but have you tried getting help from the actual flipper zero forum?

1 Like

Yes before my laptop got taken from my car so now im not under standing the hole github part of forking and making everything into the right file that I can download using this slow ass phone with a 5in screen for everything

omg so you’re doing everything on a phone? yeah firmware development on a phone is not likely to be a good time.

3 Likes