quearos hartwill nicholle

0 views
Skip to first unread message

Valorie Carlee

unread,
Aug 2, 2024, 8:44:48 PM8/2/24
to riurownbuthe

Created by XDA Senior Member huskydg, Magic ToolFlash is a unique take on the Android flashing mechanism. It's a command-line flash tool that works without a custom recovery environment. All you need to do is download a flashable ZIP on your device. Next, call the tool through any terminal emulator app with root privilege to execute the flashing operation.

Aside from creating an isolated namespace for the sake of security, Magic ToolFlash also shows the detailed flash log to the end-user. You can flash different Magisk modules, the Magisk app itself, as well as other mod ZIP files right from a CLI window on your phone using the flash command after installing this Magisk module. However, the tool can't be used to install a ROM from a running Android system yet.

Keep in mind that the /tmp directory does not exist on the Android root filesystem. As a result, you might need to modify the updater script and use /dev/tmp as the temporary directory while using Magic ToolFlash. Moreover, if the target flashable zip contains hardcoded /sbin command, it might fail on Android 11 and above operating systems.

If you are a developer and want to explore the codebase of Magic ToolFlash, then take a look at the project's GitHub repository. A ready-to-use Magisk module version is also available for download under the Releases section of the repo.

Hi, we are using LPC4367 controller in one of my development. for development we are using mcuxpresso IDE and in that we are using GUI flash tool for programming above mentioned controllers, I query is , do we have separated exe of GUI flash tool similar to flash magic tool in order to program the controllers ( LPC43XX, LPC546XX, MKE04 and MK22 series)? since we need this for our programming purpose where we will be programming multiple controllers and it will be better to use just a tool instead of a complete IDE to just program the controllers. Please let me know so that i can down load the same and test the same at my side.

[0000.305] I> Welcome to MB2(TBoot-BPMP) (version: default.t194-mobile-f46b9673)
[0000.306] I> DMA Heap @ [0x526fa000 - 0x52ffa000]
[0000.307] I> Default Heap @ [0xd486400 - 0xd48a400]
[0000.308] E> DEVICE_PROD: Invalid value data = 70020000, size = 0.
[0000.313] W> device prod register failed
[0000.317] I> Boot_device: SDMMC_BOOT instance: 3
[0000.321] I> sdmmc-3 params source = boot args
[0000.327] I> sdmmc-3 params source = boot args
[0000.330] I> sdmmc bdev is already initialized
[0000.338] I> Found 21 partitions in SDMMC_BOOT (instance 3)
[0000.345] I> Found 41 partitions in SDMMC_USER (instance 3)
[0000.346] W> No valid slot number is found in scratch register
[0000.351] W> Return default slot: _a
[0000.354] I> Active Boot chain : 0
[0000.367] E> HeaderMagic Invalid
[0000.367] I> 馃?馃?馃?馃?馃?馃?馃?馃? execution failed
[0000.368] I> 馃?馃?馃?馃?馃?馃?馃?馃? execution failed
[0000.372] E> Top caller module: LOADER, error module: LOADER, reason: 0x02, aux_info: 0x00
[0000.380] I> AB warm reset

seems the flash tool and MB2 used the different SBK key, so the header magic generated by flash tool cannot be recognized during boot up.
any help or hint are highly appreciated.
Thanks.
Willian

[0000.055] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[0000.063] I> MB1 (prd-version: 2.2.0.0-t194-41334769-3540ffaa)
[0000.068] I> Boot-mode: Coldboot
[0000.071] I> Platform: Silicon
[0000.074] I> Chip revision : A02P
[0000.077] I> Bootrom patch version : 15 (correctly patched)
[0000.082] I> ATE fuse revision : 0x200
[0000.086] I> Ram repair fuse : 0x0
[0000.089] I> Ram Code : 0x2
[0000.091] I> rst_source: 0xb, rst_level: 0x1
[0000.096] I> Boot-device: SDMMC (instance: 3)
[0000.112] I> sdmmc DDR50 mode
[0000.116] I> Boot chain mechanism: A/B
[0000.120] I> Current Boot-Chain Slot: 0
[0000.123] W> No valid slot number is found in scratch register
[0000.129] W> Return default slot: _a
[0000.134] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0000.139] I> Temperature = 36000
[0000.142] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.147] W> Skipping boost for clk: BPMP_APB
[0000.151] W> Skipping boost for clk: AXI_CBB
[0000.155] W> Skipping boost for clk: AON_CPU_NIC
[0000.159] W> Skipping boost for clk: CAN1
[0000.163] W> Skipping boost for clk: CAN2
[0000.167] I> Boot-device: SDMMC (instance: 3)
[0000.176] I> Sdmmc: HS400 mode enabled
[0000.180] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.187] W> Thermal config not found in BCT
[0000.195] W> MEMIO rail config not found in BCT
[0000.217] I> sdmmc bdev is already initialized
[0000.262] W> Platform config not found in BCT
[0000.296] I> MB1 done

\0?鄊ain enter
SPE VERSION #: R01.00.18 Created: Jan 29 2021 @ 14:18:27
HW Function test
Start Scheduler.
in late init
?
[0000.305] I> Welcome to MB2(TBoot-BPMP) (version: default.t194-mobile-f46b9673)
[0000.306] I> DMA Heap @ [0x526fa000 - 0x52ffa000]
[0000.306] I> Default Heap @ [0xd486400 - 0xd48a400]
[0000.307] E> DEVICE_PROD: Invalid value data = 70020000, size = 0.
[0000.313] W> device prod register failed
[0000.316] I> Boot_device: SDMMC_BOOT instance: 3
[0000.321] I> sdmmc-3 params source = boot args
[0000.326] I> sdmmc-3 params source = boot args
[0000.329] I> sdmmc bdev is already initialized
[0000.338] I> Found 21 partitions in SDMMC_BOOT (instance 3)
[0000.344] I> Found 41 partitions in SDMMC_USER (instance 3)
[0000.345] W> No valid slot number is found in scratch register
[0000.350] W> Return default slot: _a
[0000.354] I> Active Boot chain : 0
[0000.366] E> HeaderMagic Invalid
[0000.367] I> 馃?馃?馃?馃?馃?馃?馃?馃? execution failed
[0000.367] I> 馃?馃?馃?馃?馃?馃?馃?馃? execution failed
[0000.371] E> Top caller module: LOADER, error module: LOADER, reason: 0x02, aux_info: 0x00
[0000.380] I> AB warm reset
\0\0

I set up a source compile environment already so I thought no need to untar the Jetson_Linux_R34.1.0_aarch64.tbz2 and Tegra_Linux_Sample-Root-Filesystem_R34.1.0_aarch64. That means step 2 was skipped.
step 1,3,4 was followed. and I rebuild the dtb before flash the image.
will this trigger the issue?
Thanks.
Willian

Hi Wayne,
seems there was something wrong with my previous kernel compile environment, I followed the overlay readme process it was ok, and I rebuild the kernel and dtb, everything fine now, sorry for disturbing.
Willian

Upgrade your engine performance with Magic Tuner Flash Tool v2.1. This powerful tool enhances engine efficiency and improves fuel usage. It is compatible with various engine systems, including Maxxforce, Detroit, Paccar, Volvo, and Mack engines. The installation process is hassle-free, with quick remote installation service and comprehensive technical online support. Rest assured with our after-sales support and refund policy. Unlock the full potential of your engine with Magic Tuner Flash Tool v2.1 from ecmtrucks.com.

With this tool you can flash the blocks through the diagnostic connector so as not to remove the block, not to open, not to connect Ktag or Kess or other programs, but simply flash the block with a binary using any adapter, for example Nexiq.

Experience next-level engine performance with Magic Tuner Flash Tool v2.1. This powerful software allows you to make custom adjustments to your engine management system, optimizing its performance for maximum power and efficiency. Unlock the true potential of your engine and enjoy improved acceleration, smoother operation, and enhanced overall performance.

Magic Tuner Flash Tool v2.1 is fully compatible with Maxxforce engines, offering custom adjustment options and enhanced performance. Experience optimized engine settings without the need for manual intervention. Unlock the true potential of your Maxxforce engine with this versatile tool.

Equipped with advanced features, Magic Tuner Flash Tool v2.1 is designed to work seamlessly with Detroit engines. Improve fuel efficiency, maximize power output, and fine-tune engine parameters for optimal performance. Elevate your driving experience with the power of the Detroit engine and Magic Tuner Flash Tool.

With its comprehensive compatibility, Magic Tuner Flash Tool v2.1 caters to Paccar engines as well. Enhance the performance and efficiency of your Paccar engine by customizing various engine management settings. Unlock the potential of your Paccar engine with ease and precision.

Magic Tuner Flash Tool v2.1 provides seamless integration with Volvo and Mack engines, allowing for personalized adjustments to achieve superior engine performance. Unlock hidden capabilities, optimize fuel consumption, and take control of your Volvo or Mack engine using this powerful tool.

Our Magic Tuner Flash Tool v2.1 comes with a convenient and efficient remote installation service. Our expert technicians will guide you step-by-step through the installation process, ensuring a hassle-free experience. By utilizing secure and reliable remote access software, we can remotely access your computer and install the tool, saving you time and effort. Our technicians will ensure that the installation is completed correctly, so you can start optimizing your engine performance without any delay.

We provide comprehensive technical online support to address any inquiries or issues you may encounter while using our Magic Tuner Flash Tool v2.1. Our dedicated support team is available during business hours to assist you with any technical questions or troubleshooting needs. Whether you need assistance with software configuration or encountering compatibility challenges, our knowledgeable technicians will provide prompt and effective solutions to keep you on track.

Customer satisfaction is our top priority. We offer a clear after-sales support policy to ensure your peace of mind. If you encounter any difficulties or concerns after purchasing our Magic Tuner Flash Tool v2.1, our support team will be readily available to address them. We pride ourselves on providing excellent customer service and will work diligently to resolve any issues you may have promptly.

c01484d022
Reply all
Reply to author
Forward
0 new messages