I am trying to put a ROM on the TF300. I have Unlocked the tablet and installed the ADB driver. When I boot into recovery and the USB icon it asks for a driver for fastboot. I can't seem to get that anywhere. I have the Android SDK installed and java etc. Where is the driver located? I look in the USB driver folder but its not in their...
If you need just fastboot, use this guide, that you will find in the index for tf300 (General & Dev forums)
HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ ]
commands:
update reflash device from update.zip
flashall flash boot + recovery + system
flash [ ] write a file to a flash partition
erase erase a flash partition
getvar display a bootloader variable
boot [ ] download and boot kernel
flash:raw boot [ ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s specify device serial number
-p specify product name
-c override kernel commandline
-i specify a custom USB vendor id
-b specify a custom kernel base address
-n specify the nand page size. default: 2048
And if you have some problems with your drivers, you can use this : How to install Universal Naked Drivers
Sent from my N7 3G with DroiDevs premium between sky and earth.
I got it to work thanks!
Hello
i want to create custom rom boot image .but how i solve this error
step 1:i go to advanced options
===========================================
Android Kitchen 0.194 - by dsixa <xda-developer.com>
===========================================
0 = ADVANCED OPTIONS
step 2: repack the boot.img
so i choose
20 = Tools for boot image (unpack/re-pack/etc.)
step 3:extract kernel and ramdisk
w = Extract kernel + ramdisk from boot.img
step 1 to 3 is very convenience but press W and
enter Extract kernel and ramdisk it show like this
Working folder found
Kernel found at offset 2048 in boot.img
Making folder BOOT-EXTRACTED
Extracting kernel...
Extracting ramdisk...
Error: NO ramdisk folder found!
Press Enter Continue
how i pass this step and how i make ramdisk folder
no one here ? i have this problem toooooooooooo
A youtube video on this guide
Watch video
Hello guys,
I rarely write guide and tutorials .so neglect my typos and gramatical mistakes
Today im gonna show you how to unpack sparsed system.img files (system_1.img+system_2.img+............+system_*.img)
supports system / cache / userdata / persist / vendor / cust / odm /oem partitions from QFIL firmwares
Lets get started
LINUX
Things Needed:
1) Packsparseimg
2) Imgextractor.exe -Need wine for this
Procedure:
1) First of all extract you device firmware in which you have sparse system.img files in a folder.
(folder path ex:~/Desktop/firmware)
2) Copy the downloaded packsparseimg_v1.1 and Imgextractor.exe in the same folder where you extracted your firmware
(ex:~/Desktop/firmware)
3) Open terminal and enter below commands.
4)
Code:
chmod 0755 packsparseimg_v1.1
5)This command will pack sparse system_1.img....files to system.raw
Code:
./packsparseimg_v1.1
you can use these commands to pack sparse cache and userdata persist,vendor,cust,odm partitions
Code:
Usage of ./packsparseimg_v1.1:
-o string
output dir path (default "./")
-t string
image to unsparse: system / cache / userdata / persist / vendor / cust / odm / oem (default "system")
-x string
xml file to load (default "./rawprogram_unsparse.xml")
6) After joining of sparse system.img's finishes you will get system.raw file
7) Use below commands to unpack system.raw to system folder
Note: You need wine on your linux to run imgextractor.exe
Code:
wine imgextractor.exe system.raw
8) Hell Yeah! you have successfully unpack those system_1,2,3,4....imgs
now you can make your own stock deodexed rom
Downloads For linux:-
[MOD EDIT: URL REMOVED]
Password:innfinite4evr
Imgextractor.exe
WINDOWS
Things Needed:
1) packsparseimg_v1.1
2) Imgextractor.exe
Procedure:
1) First of all extract you device firmware in which you have sparse system.img files in a folder.
(folder path exesktop/Myfirmware)
2) Copy the downloaded packsparseimg_v1.1 and Imgextractor.exe in the same folder where you extracted your firmware
(exesktop/Myfirmware)
3) Open Command Prompt (cmd.exe) and enter below commands.
PS: you can open command propmt by any of these methods. Here method 1 is preferred
Method 1: Most suitable method for this guide
hold down shift key while pressing the right mouse onto the folder you want to open "command prompt" then a new menu item will appear in your context menu offering you exactly that: "open command prompt here" select it and command prompt will open.
Method 2:Search is very helpful. In Windows 7, open the Start Menu and type command or cmd. Then, click or tap the Command Prompt
Method 3ne of the quickest ways to launch the Command Prompt is to use the Run window (press Win+R on your keyboard and type cmd and press enter to open it).
i guess three methods are enough for windows users
4) AFter command prompt opens enter below comamnds to proceed further
5)This command will pack sparse system_1.img....files to system.raw
Note default is "system"
Code:
packsparseimg
you can use these commands to pack sparse cache and userdata persist,vendor,cust,odm partitions
Code:
Usage of packsparseimg:
-o string
output dir path (default "./")
-t string
image to unsparse: system / cache / userdata / persist / vendor / cust / odm (default "system")
-x string
xml file to load (default "./rawprogram_unsparse.xml")
6) After joining of sparse system.img's finishes you will get system.raw file
7) Use below commands to unpack system.raw to system folder
Code:
imgextractor.exe system.raw
8) Now you will get unpacked system folder
Hell Yeah! you have successfully unpack those system_1,2,3,4....imgs
now you can make your own stock deodexed rom
Downloads for windows:-
Imgextractor.exe
Password:innfinite4evr
[MOD EDIT: URL REMOVED]
Changelog:-
in update v1.1
now supports system / cache / userdata / persist / vendor / cust / odm /oem partitions from QFIL firmwares
Credits:
kidd for initially making packsparseimg binary
@and_pDA for imgextractor,exe(Based on sources ext4_unpacker)
@Innfinite4evr for testing this method and write this guide
Great work bro :good: Nice job and thanks for this
great work man. thanks
can you share code?
There is another way to unpacj that instead of using wine.
Code:
mount -o loop -t ext4 system.img [path]
Replace:
[Path] with path to the output directory you want (ex: ~/sys-img)
ext4: This might be different, check it by yourself, but most device now using ext4
Thanks for the info, btw
Please can somebody tell me how to revert the process? To create again sparse images and flash via qfil? Thanks in advance!
cofface said:
can you share code?
Click to expand...
Click to collapse
only prebuilts
cofface said:
can you share code?
Click to expand...
Click to collapse
only prebuilts
I get this error on Ubuntu:
bash: ./packsparseimg: cannot execute binary file: Formato eseguibile non valido
What is the procedure to do the reverse?
How to repack as parts
sir i was trying to repack system folder to system_1.img system_2.img etc.
is there any way for that?
i need to repack and flash to my phone
Doesn't seem to work for Oreo a/b system
@Innfinite4evr Hi there, can you add vendor, cust and odm support ?
AL_IRAQI said:
@Innfinite4evrHi there, can you add vendor, cust and odm support ?
Click to expand...
Click to collapse
Yes there is.
Im thinking to update this stuff
AL_IRAQI said:
@Innfinite4evrHi there, can you add vendor, cust and odm support ?
Click to expand...
Click to collapse
Ive updated the tool, maybe you can try for odm partition.
Innfinite4evr said:
Ive updated the tool, maybe you can try for odm partition.
Click to expand...
Click to collapse
I've try to buy, with all my2 credit card (master card and american express)
I was addebited 1€ in my mastercard, but it always give me error and I can't download the program.
I do not want the refund, I'd like to have the tool!
Samuele Bonzio
I give you my phone number by PM if that need!
Thank you!
Thread closed. PM me when you have download links that don't require payment to be added to the OP.
I've unlocked bootloader, got boot.img(hashes match in update.zip and my boot.img + it boots fine), patched it and vbmeta in tar by magisk 24.3, but when i flash new boot.img, it throws me "SECURE FAILED: BOOT" error on watch and system doesn't boot, flashing unpatched boot.img gets watch to work again. Why does it happen and is there any fix? SM-R860
Files:
files.zip
drive.google.com
Sounds like Samsung baked in something to keep it from being rooted
I wrote Conversation aka PM to you...
Best Regards
sermister1 said:
I've unlocked bootloader, got boot.img(hashes match in update.zip and my boot.img + it boots fine), patched it and vbmeta in tar by magisk 24.3, but when i flash new boot.img, it throws me "SECURE FAILED: BOOT" error on watch and system doesn't boot, flashing unpatched boot.img gets watch to work again. Why does it happen and is there any fix? SM-R860
Files:
files.zip
drive.google.com
Click to expand...
Click to collapse
Magisk patch is not enough to achieve root. You need to flash the stock boot image in order to fix that.
janjan said:
Magisk patch is not enough to achieve root. You need to flash the stock boot image in order to fix that.
Click to expand...
Click to collapse
My sm-r860 boots fine only with stock boot.img, how can i get magisk to work?
Wrong posting...
Example of vbmeta from Combination Firmware...
SM-G991B Android 11
Code:
COMBINATION_FAC_FAR0_G991BXXU1AUA3_FAC_CL20796681_QB37484630_REV01_user_mid_noship_MULTI_CERT.tar.md5
Summary for my tiny brain...
A
Magisk patch vbmeta.img only 1 Byte at Offset 0x7B
00 into 03
B
In attached "Combi Example" vbmeta have more Bytes changed in Header... and Offset 0x7B is:
01
C
Some Google search findings...
What is 02 in the magisk patched vbmeta.img?
According to the Additional Info given for rooting the Android device that doesn't have ramdisk but can be rooted via recovery: we need an empty vbmeta.img and I am trying to check what it actually
android.stackexchange.com
XDA search...
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
Dear janjan
Please share full info/instruction for Rooting GW4 via USB.
Thanx in advance.
Best Regards
adfree said:
Dear janjan
Please share full info/instruction for Rooting GW4 via USB.
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
@janjan hopefully he'll get this sent alert!
adfree said:
Dear janjan
Please share full info/instruction for Rooting GW4 via USB.
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
Dear adfree,
I am still working on it. I don't own the USB myself to share any knowledge about that. But I will ofc share my work whenever I have time. I just build a kernel and I will ofc share when I finish uploading the source to GitHub. Thank you for understanding.
galaxys said:
@janjan hopefully he'll get this sent alert!
Click to expand...
Click to collapse
I will ofc share my work when I finish uploading the source to the GitHub. Work in progress. The goal is to achieve root through Netodin and as you already know it is not a easy task. It takes time. Thank you for understanding
sermister1 said:
My sm-r860 boots fine only with stock boot.img, how can i get magisk to work?
Click to expand...
Click to collapse
I tired different magisk to patch the stock boot.img but it doesn't work.
I will compile a kernel for your device. I am still waiting for Samsung to share latest source. Seems the old source doesn't work with D4 unfortunately.
janjan said:
I tired different magisk to patch the stock boot.img but it doesn't work.
I will compile a kernel for your device. I am still waiting for Samsung to share latest source. Seems the old source doesn't work with D4 unfortunately.
Click to expand...
Click to collapse
if you're talking about evd4, currently i have fvc8 rom
And can't use usb bcs i don't have triple screwdriver.
Caution! Warning!
Own Risk!
SM-R860 FVC8 Kernel
For study...
Idea is to improve our Log files...
RDX Tool is confirmed working with GW4 connected with USB cable:
Upload Mode
There are several modes that Wave bootloader supports for certain purposes. The normal mode and low power mode just start the Nucleus kernel. I'm also pretty sure everybody knows what a DOWNLOAD MODE is (one with the red letters, but if initiated...
forum.xda-developers.com
Files are based on first post...
And idea about Values came to me after this:
Rooting Galaxy Watch4
I've unlocked bootloader, got boot.img(hashes match in update.zip and my boot.img + it boots fine), patched it and vbmeta in tar by magisk 24.3, but when i flash new boot.img, it throws me "SECURE FAILED: BOOT" error on watch and system doesn't...
forum.xda-developers.com
Tasks...
A
Create TAR files for netOdin/Odin...
I have simplified to see difference in files...
boot.img not changed... it is the Magisk patched FVC8 from first post...
B
Now IMHO 3 times flashing with Odin (we will start with USB, so we can use RDX Tool)
Round 1
Flashing
1_magisk_patched-24300_oLqH6
Then RDX dump for Log
Round 2
2_vbmeta_01
Then RDX dump for Log
Round 3
3_vbmeta_02
Then RDX dump for Log
With these 3 Logs and from Original Stock Booting... so 4 RDX Dumps...
IMHO maybe visible where exactly it fails...
Best Regards
edit 1.
Additional Control Step to be sure Knox is still alive... or dead...
Code:
D:\Android\ADB>adb shell getprop ro.boot.warranty_bit
0
Here are the RDX Screenshots... taken few weeks ago... SM-R860 FVC8...
RDX shows something like:
Code:
summary.html
auto_comment
extra_info
debug_history
boot_reset
acpm_dump
header
kernel
platform
kevents
s2d
arrdumpreset
arrdumppanic
MFC-log-mem
MFC-sfr-dmp0
LPD-log-mem
LPD-srm-dmp
SM-R860 connected via USB cable and RDX Tool 6.1.4
Upload Mode
There are several modes that Wave bootloader supports for certain purposes. The normal mode and low power mode just start the Nucleus kernel. I'm also pretty sure everybody knows what a DOWNLOAD MODE is (one with the red letters, but if initiated...
forum.xda-developers.com
Best Regards
Code:
[0: 4.451206 ] Footer.magic : AVBf
[0: 4.451210 ] Footer.version : 1.0
[0: 4.451214 ] Footer.original_image_size : 0x2f6330
[0: 4.451217 ] Footer.vbmeta_offset : 0x2f7000
[0: 4.451220 ] Footer.vbmeta_size : 0x840
[0: 4.451223 ] get_original_image_size: Found Footer Info for BOTA, original size: 0x2f6330
[0: 4.451228 ] Verify_Signature_Ecdsa 0xa3e80074 3105584, 0xa4176194 512
[0: 4.473469 ] check_signature (BOOTLOADER) valid.
[0: 4.483628 ] Check DRAM STORE training data..
[0: 4.483632 ] ACPM magic code: 0xAC8338A9
[0: 4.483636 ] Write magic code: 0xF67038A9
[0: 4.547556 ] Restore DRAM training data..
[0: 4.558104 ] _sbl_bota_update: BOOTLOADER Update Completed.
[0: 4.558111 ] _sbl_bota_update: tzar.img(6292240) -> TZAR(9) Update Start.
[0: 4.558122 ] avb_footer.c:41: ERROR: Footer magic is incorrect.
security_core.c:1358: ERROR: BOTA: Error validating footer.
BOTA : Error validating footer.
[0: 4.558138 ] Verify_Signature_Ecdsa 0xa4280098 6292240, 0xa4880198 512
[0: 4.588086 ] check_signature (TZAR) valid.
[0: 4.760372 ] _sbl_bota_update: TZAR Update Completed.
[0: 4.760379 ] _sbl_bota_update: tzsw.img(1572864) -> TZSW(8) Update Start.
[0: 4.760396 ] Footer.magic : AVBf
[0: 4.760400 ] Footer.version : 1.0
[0: 4.760403 ] Footer.original_image_size : 0x100310
[0: 4.760407 ] Footer.vbmeta_offset : 0x101000
[0: 4.760410 ] Footer.vbmeta_size : 0x840
[0: 4.760413 ] get_original_image_size: Found Footer Info for BOTA, original size: 0x100310
[0: 4.760418 ] Verify_Signature_Ecdsa 0xa48803cc 1049360, 0xa49804cc 512
[0: 4.777709 ] check_signature (TZSW) valid.
[0: 4.823222 ] _sbl_bota_update: TZSW Update Completed.
[0: 4.823231 ] _sbl_bota_update: uh.bin(276120) -> UH(15) Update Start.
[0: 4.846012 ] _sbl_bota_update: UH Update Completed.
[0: 4.846020 ] _sbl_bota_update: up_param.bin(706560) -> UP_PARAM(13) Update Start.
[0: 4.871416 ] _sbl_bota_update: UP_PARAM Update Completed.
[0: 4.871425 ] _sbl_bota_update: vbmeta.img(9744) -> VBMETA(23) Update Start.
[0: 4.871435 ] avb_footer.c:41: ERROR: Footer magic is incorrect.
security_core.c:1358: ERROR: BOTA: Error validating footer.
BOTA : Error validating footer.
[0: 4.871451 ] Verify_Signature_Ecdsa 0xa4af02d0 9744, 0xa4af26d0 512
[0: 4.886209 ] check_signature (VBMETA) valid.
[0: 4.899964 ] _sbl_bota_update: VBMETA Update Completed.
[0: 4.932208 ] s2mpw03_get_vbat: vBAT=4183mV
[0: 4.932309 ] s2mpw03_get_soc: capacity (0xec0:9218)
[0: 4.959070 ] sys_restart ('N':fota_up)
[0: 4.959074 ]
[0: 4.959077 ] [SECD] clear_debug_flags: Clear DINFOM and RAMBASE
[0: 4.959082 ] set_minform_magic: before: 4e4e0000 (type: 1, magic: 4e)
[0: 4.959090 ] set_minform_magic: after: 4e4e0000
[0: 4.959095 ] set_minform_magic: before: 4e4e0000 (type: 3, magic: 0)
[0: 4.959102 ] set_minform_magic: after: 4e4e0000
[0: 4.959107 ] set_minform_magic: before: 4e4e0000 (type: 2, magic: 0)
[0: 4.959114 ] set_minform_magic: after: 4e4e0000
[0: 4.959119 ] display_drv_clear was called
[0: 4.959123 ] panel_exit +
[0: 5.079213 ] dsim_set_panel_power off +
[0: 5.091298 ] MMC0 PON set in mmc_power_off_notification
[000.000000] NOTICE: EPBL Self Decryption success
[000.046719] NOTICE: SecureBoot: [BL2] Check digital signature and RP count success
I am looking through my old Debug Logs...
Search text string:
vbmeta.img
According to filename something taken in EVB4... dumpState...log
I am unsure if fail is because vbmeta.img is invalid... maybe patched boot.img is the problem...
Maybe also procedure is incorrect or incomplete...
According to fastboot hints... unlock not at same time with boot.img...
Example what I mean
Installation
The Magic Mask for Android
topjohnwu.github.io
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
And info fastboot not working...
??
This means the unlock Command not work?
Or all known Fastboot Commands not work?
Will try to find easy test...
Code:
D:\Android\ADB>fastboot
fastboot: usage: no command
D:\Android\ADB>fastboot -help
usage: fastboot [OPTION...] COMMAND...
flashing:
update ZIP Flash all partitions from an update.zip package.
flashall Flash all partitions from $ANDROID_PRODUCT_OUT.
On A/B devices, flashed slot is set as active.
Secondary images may be flashed to inactive slot.
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
basics:
devices [-l] List devices in bootloader (-l: with device paths).
getvar NAME Display given bootloader variable.
reboot [bootloader] Reboot device.
locking/unlocking:
flashing lock|unlock Lock/unlock partitions for flashing
flashing lock_critical|unlock_critical
Lock/unlock 'critical' bootloader partitions.
flashing get_unlock_ability
Check whether unlocking is allowed (1) or not(0).
advanced:
erase PARTITION Erase a flash partition.
format[:FS_TYPE[:SIZE]] PARTITION
Format a flash partition.
set_active SLOT Set the active slot.
oem [COMMAND...] Execute OEM-specific command.
gsi wipe|disable Wipe or disable a GSI installation (fastbootd only).
wipe-super [SUPER_EMPTY] Wipe the super partition. This will reset it to
contain an empty set of default dynamic partitions.
boot image:
boot KERNEL [RAMDISK [SECOND]]
Download and boot kernel from RAM.
flash:raw PARTITION KERNEL [RAMDISK [SECOND]]
Create boot image and flash it.
--dtb DTB Specify path to DTB for boot image header version 2.
--cmdline CMDLINE Override kernel command line.
--base ADDRESS Set kernel base address (default: 0x10000000).
--kernel-offset Set kernel offset (default: 0x00008000).
--ramdisk-offset Set ramdisk offset (default: 0x01000000).
--tags-offset Set tags offset (default: 0x00000100).
--dtb-offset Set dtb offset (default: 0x01100000).
--page-size BYTES Set flash page size (default: 2048).
--header-version VERSION Set boot image header version.
--os-version MAJOR[.MINOR[.PATCH]]
Set boot image OS version (default: 0.0.0).
--os-patch-level YYYY-MM-DD
Set boot image OS security patch level.
Android Things:
stage IN_FILE Sends given file to stage for the next command.
get_staged OUT_FILE Writes data staged by the last command to a file.
options:
-w Wipe userdata.
-s SERIAL Specify a USB device.
-s tcp|udp:HOST[:PORT] Specify a network device.
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
--force Force a flash operation that may be unsafe.
--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
--set-active[=SLOT] Sets the active slot before rebooting.
--skip-secondary Don't flash secondary slots in flashall/update.
--skip-reboot Don't reboot device after flashing.
--disable-verity Sets disable-verity when flashing vbmeta.
--disable-verification Sets disable-verification when flashing vbmeta.
--unbuffered Don't buffer input or output.
--verbose, -v Verbose output.
--version Display version.
--help, -h Show this message.
Edit 1.
IMHO easiest Fastboot command to check if Fastboot is working...
Code:
fastboot devices
Tiny heartattack after stupid test in FVD4:
Code:
D:\Android\ADB>adb shell
freshbs:/ $ reboot fastboot
Leads to black screen...
I remember in older Firmwares red text fastboot...
Few attempts to leave failed...
Hold both keys for few seconds make Reboot Menu accessable...
But no Kernel boots... only black screen... both in normal and Recovery...
I was able to leave the black screen massaker by entering Download Mode USB... and here I pressed both Keys few seconds...
Then normal Booting possible.
I will search the old fastboot info... IMHO Picture postet or something like this...
Best Regards
Edit 1.
fastboot visble in Recovery Mode...
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
Edit 2.
Oh, found my old attempt:
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
Here I tried:
reboot bootloader
Ah okay. Tested now on FVD4 and i see in tiny red text:
Fastboot Mode..
If I hold both keys for seconds... can normal boot again.
Short summary about Upload Mode for RDX Tool aka Ramdump aka Kernel Panic...
A
This is Samsung only stuff since yearS...
B
For GW4 it looks like this on Watch... See Photo left:
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
We see UPLOAD MODE in red
C
At the moment I know only this way to make it visible on FVD4... FVC8 Firmware...
For USB connection
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
Only as info...
Best Regards
Preparing to compare what Magisk did to FVC8 Kernel...
First Step with imjtool...
Code:
[email protected]:~/imj$ ./imjtool stock.img extract
Boot image version 2 for OS version 0x16000163 (11.128 Patch Level 2022-3) detected (1660 byte header)
Part Size Pages Addr
Kernel (@0x0000800): 25194512 12303 0x10008000
Ramdisk (@0x1808000): 743485 364 0x10000000
Device Tree(@0x18be000): 110416 54 0x10000000
MAGIC: 0x1eabb7d7
Extracting dtbo
Found [email protected]
AVB0 (@0x18da000): 2112
AVBf (@0x23fffc0):
Tags: 0x10000000
Flash Page Size: 2048 bytes
ID: c769e71ef5bec23438102c4a3af78e13dcd7d587000
Name: SRPUC03B001
CmdLine:
Found GZ Magic at offset 14333096
extracted/kernelimage.gz:
gzip: extracted/kernelimage.gz: decompression OK, trailing garbage ignored
-81.8% -- replaced with extracted/kernelimage
Extracting kernel
Extracting ramdisk
Searching for DT at 0x18be000
MAGIC: 0x1eabb7d7
Extracting dtbo - exists so renaming to _dtbo
[email protected]:~/imj$ ./imjtool patch.img extract
Boot image version 2 for OS version 0x16000163 (11.128 Patch Level 2022-3) detected (1660 byte header)
Part Size Pages Addr
Kernel (@0x0000800): 25194512 12303 0x10008000
Ramdisk (@0x1808000): 1252029 612 0x10000000
Device Tree(@0x193a000): 110416 54 0x10000000
MAGIC: 0x1eabb7d7
Extracting dtbo
Found [email protected]
AVB0 (@0x1956000): 2112
AVBf (@0x23fffc0):
Tags: 0x10000000
Flash Page Size: 2048 bytes
ID: 5477904380525186fa9fdb5eaf7863be8e37af2d000
Name: SRPUC03B001
CmdLine:
Found GZ Magic at offset 14333096
extracted/kernelimage.gz:
gzip: extracted/kernelimage.gz: decompression OK, trailing garbage ignored
-81.8% -- replaced with extracted/kernelimage
Extracting kernel
Extracting ramdisk
Searching for DT at 0x193a000
MAGIC: 0x1eabb7d7
Extracting dtbo - exists so renaming to _dtbo
hello evry one
I am having a problem and I want to solve it
Install nding update package ... ening update package ... / udisk / X96 - Mini_S905W_Update Android 20200000.zip ... rifying update package ... date package verification took 25.7 s ( result 0 ) . stalling update ... rning : No file contextsE3004 : This package is for " ampere " devices ; this is a " p281 " .E : Error in / udisk / -Mini_S905W_Update_Android_9_20200620.zip No command tatus 7 ) stallation aborted . failed to mount / sdcard ( No such file or directory ) failed to mount / sdcard ( No such file or directory ) No package file selected .