Hello!
Is it possible to substitute PhoenixSuite under linux for .img flashing to Android device (Chuwi V99 QuadCore A31)?
So need tools or method for flashing .img (for PhoenixSuite) to Android device from linux(Ubuntu).
Tnx!
Related
Hi!
I update the Idol suite for 4.7 6039 phone version, it is a Windows tools ( sorry).
Log:
It use ADB tools
Can unlock bootloader
Flash TWRP 3.0.0-0 for Idol 4.7
Backup yur phone ROM (need root)
Can boot in bootloader mode
Can reboot from bootloader mode
Can boot in to recovery
Can simply reboot the phone
Can extract the files from a ext4 image, like system.img
Can flash a single image
Can pull to edite the build.prop file and create a flash zip for it
Can boot in to twrp 3.0.0-0 with out flashing ( useful to recover the phone)
Can pull the apks from system and create a flash zip ( If you want to change something in apps or change a pp for another than you want to flash it again )
Can edite the apk files and create a flash zip
Can create a new Splash image and a zip to flash it
It have idol drivers for windows
NOTE:
Some tools are not mine, I simply put everything together in one place!
I am not responsible for any damage they may cause to your device.
Use it at your responsability
Extract the folder from zip in to descktop and execute the Idol_Suite_V3.exe file.
New_Idol_4.7_Suite.zip
Any issue please tell me!
Enjoy it!
The tool is update:
Now you can modify boot and recovery to.
thank you dude.
You can upload the file again
Thanks!!!
Hi Persona78, first can i say what a fantastic job you have done, most of my research on the idol 3 4.7 points back to you, hats off sir!
I'm still having a problem and i'm really at a loss here after about a week of no returns.
adb refuses to recognise my 6039y when in bootloader so i cannot flash recovery, or ROM, or any command. I have all drivers installed correctly, vendor id of 0x1bbb is set in a.ini file in adb_usb.ini, i keep search for different approaches but turning up nothing!
Are there anything to suggest? I would be most appreciative!
Thanks, Marlin
Hi guys, I am just trying to build my own kernel so i can make some modifications later (coming from Linux desktop dev experience). I have successfully built it and I have the Image and Image.gz, but also all of these DTB files. It seems like things have changed since 32-bit Android 6.x, where I could just do abootimg -u boot.img -K IMAGE to the stock boot image to replace the kernel image and then flash to the device. Now I just get an error that the remote dtb file is missing (if I try doing the abootimg command), or it just boots up my old kernel if I do fastboot boot newimage. Can anyone provide me any documentation or quick example how to boot a new kernel made from source? Thanks
EDIT: figured it out: for anyone who stumbles upon this message: you have to do fastboot boot Image.gz-dtb (I was trying to boot the non-dtb one)
Im wondering if a custom GSI installation is possible
Checking the app "Treble info" says the phone supports the modern version of project treble
And im wondering if anything else has to be done for a GSI to work (for example flashing another file before the GSI)
or just simply flash it via twrp or ADB?
and if its possible, The installation of an android 12 GSI would be possible?
Generic system images | Android Open Source Project
source.android.com
Well you need to flash a vbmeta.img, with a special command. Details are in the link above.
Vbmeta.img is usually available in the stock ROM, but if it fails or does not exist, use the Google official vbmeta. https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Hi,
Why I cannot see the scatter loading file on the linux version?
Thanks
Hello everyone
I have a rooted (with Magisk) Samsung Galaxy S20 Ultra 5G (G988B) device with TWRP installed in recovery partition.
Stock kernel version: 4.19.187-20291612
Build number: G988BXXU5CTKG
My purpose is to have a custom kernel which is identical to stock kernel except for configs for ftrace and kgdb (can be changed in defconfig before compilation)
Steps I've performed to flash a custom kernel for the given device:
1) Downloaded Linux Kernel for the given device from https://opensource.samsung.com/ SM-G988B_RR_Opensource.zip according to the above mentioned build number
2) Used https://github.com/kdrag0n/proton-clang toolchain to build the kernel
3) Used Android Image Kitchen to generate a new boot.img in the following way:
* Extracted boot.img from the device via dd utility (100% correct, I've reflashed the extracted image for the sake of validation and had no problems)
* ./unpacking.sh original_boot.img
* Replaced original_boot.img-kernel file in /split_img directory with custom_kernel_root_dir/arch/arm64/boot/Image
* ./repacking.sh
* Got image-new.img which must contain a bootable custom kernel
4) Rebooted into TWRP and flashed the image-new.img in Boot and then rebooted into System
After that, the device is stuck (NOT bootloop!) in warning screen (device logo + name and warning about an unlocked bootloader warranty void) forever. Luckily, I am able to reboot to TWRP and reflash the previous boot.img in order unbrick the device and be able to boot into the rooted device again.
During unpacking and repacking it seems that the original and the custom boot.img files have the same values for kernel base, offset and other values.
So what's the problem? Can toolchain be problematic/unsuitable even though I was able to compile the kernel with it?