i need super.img backup file, the device stuck at fastboot, you can backup using this tool (root needed) https://forum.xda-developers.com/t/tool-root-adb-partition-backup-restore-tool-for-windows.4512231/
Download the firmware files from redmagic's support site and use Fastboot Enhance to flash the payload
Bricked my phone couple of hours ago fixed this way
Related
Hello all,
I really need, for a commercial project, to flash a great number (>100) of Galaxy Camera 2 (EK-GC200() device, all with the same firmware, rooted and modified as I need.
I have to flash boot.img (modified by me) and system.img (rooted).
I have now to root the camera, then start the system, enable developer options, enable adb debug and at the end flash a new boot.img, and the system.img itself (adb shell, dd ...).
This is time consuming, and error prone.
I'm sure the boot.img & system.img are correct, cause I can flash them without error (and they work fine) with dd from the internal emulated sdcard.
I can see two viable alternatives:
1. A custom recovery, from where I could make a nandroid backup, which I can use later on to update all the rest of the cameras.
But:
I tried to port the EK-GC100 cwm recovery, I've been able to boot it up, but the touchscreen is unusable and I got a lot of error coming from the file system.
Please help me! Any suggestion, half project, everything is really appreciated!
2. To create an Odin package, using the .img files I can optain with dd from a ready camera.
But:
I tried all I can do to build a Odin package, but every time I got an error (Odin Fail) when I try to flash system.img.
I tried to build a package containing recovery.img + boot.img, and that works.
I tried to build a package containing only system.img, and it doesn't work, every time I got a Fail from Odin.
I tried manual compression (tar + md5sum on Linux), and automated scripts you can find on XDA, both under Linux and Windows.
Why is system.img impossible to flash?
What am I missing?
Thank you in advance.
Ciao,
Giovanni
HELLO GUYS AGAIN
TODAY IM SHOWING YOU HOW TO ROOT MICROMAX C1 2018
XDA AND IM NOT RESPONSIBLE ANY KIND OF ISSUE WITH YOUR PHONE SO DO IT YOUR OWN RISK
1--DOWNLOAD MAGISK MANAGER APK
2--DOWNLOAD C1 boot.img IMAGE
3--DOWNLOAD SCATTER FILE OF C1
A--COPY BOOT.IMG IN INTERNAL STORAG
B--INSTALL MAGISK MANAGER APK AND OPEN
C--CLICK INSTALL
D--THEN CHOOSE PATCH BOOT IMG
E--CHOOSE INTERNAL STORAGE AND TAP boot.img
F--ZIP FILE DOWNLOAD AND FLASH PROCESS AUTOMATIC FLASH
G--THEN CLOSE IT
H--NOW OPEN FILE MANAGER----MAGISK FOLDER
J--THERE U SEE PATCHED BOOT.IMG FILE
K--RENAME IT ONLY boot.img
l--NOW COPY BOOT.IMG AND SCATTER FILE ON PC MAKE NEW FOLDER {PLACE BOT FILE TOGETHER}
M--OPEN SP FLASH TOOL
N--CLICK SCATTER LOADING OPTION AND SELECT C1 SCATTER
O--ON SP FLASH TOOL U SEE ONLY BOOT OPTION TICK
P--POWER OFF PHONE AND FLASH IT AND REBOOT
Q--NOW YOUR IS ROOTED INSTALL ANY ROOTED APK AND CHECK
watch video
MOD Edit -Links Removed & closed.
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
boot image
http://www.mediafire.com/file/yr81q4u0c7ql1jj/boot.img/file
scatter file
http://www.mediafire.com/file/idukqwbu9i3don7/MT6737M_Android_scatter.txt/file
Actual steps
I am not running the default version of Micromax c1 it is a developer ROM meaning it does not have root access but it allows me root access through adb
So according to your post to root the device I am supposed to get the boot image of the device to create a patched version of it using magisk and flash it in the boot partition
am I right?
I did that everything is running normally now no root access but magisk won't start now that the only difference
here is what I did
used adb shell to locate the boot image
copied the boot image physically from the device using adb pull
got it patched in magisk
got into fastboot
used "fastboot flash boot boot.img"
this one was the patched file
however, I observe no changes
I cannot use the SP flashtools as in the developer ROM the mt scatter file is different and I get the PMT error or partition error as some call it
do you have any other way to root this device
I made several backups of the boot images just in case and still have a way to flash ROM through fastboot and SP flash tools but I prefer fastboot
if possible I would like to avoid getting my phone factory reset in process of rooting it
I can flash the later Micromax C1 ROM then use your method exactly but I would rather not since it will ease my data on phone and since I have no root access I cannot make a complete backup
This process is very time consuming and tedious, you will need to use both windows and linux for this process and you will need to have patience as well as general information from Hovatek.
YES your bootloader MUST be unlocked first.
you need need to download RD tool app and stock oem firmware for the device.
extract the vbmeta-sign.img then extract your vbmeta-keys with extractor and place all keys in 'keys' folder.
patch oem boot.img with magisk and unpack it with android image kitchen, and repack, this will generate a smaller boot.img that is normal.
use avbtool command python avbtool add_hash_footer to sign and inflate your small patched boot.img to normal size.
use avbtool command python avbtool make_vbmeta_image to generate your custom-signed-vbmeta.img file will only be 16kb that is normal.
use vbmeta_pad.py command to inflate custom-signed-vbmeta.img file back to 1024kb stock size.
Once you have generated all your modified files its time to flash via RD tools
load the stock oem .pac firmware and under settings only select FDL1 and 2 , vbmeta and boot. double click to look for your custom vbmeta and boot-patched.img and flash it.
You will most likely be in a non booting state with only a quick boot logo flash then a black screen.
Now close RD tools and reload it again and this time select FDL1 and 2, and select your stock oem vbmeta-sign.img only and flash.
you will boot into android with magisk root.
If you flash custom files and fails to boot after flashing stock oem vbmeta-sign then flash all stock oem files to return to a factory state and retrace any errors or missed steps. read and re-read all steps to get a better understanding and double and triple check linux commands.
AVB_tools
avbtools.7z
drive.google.com
I have a alldocube smile 1 (t803), but I have no ability to do all the repacking of root.img. However, rooting is necessary to install the tool such as XX-net. Will you send me the two magisked images and the tool to flash them back. Thank you. My gmail: wu.gt.kent
Hello Guys Presenting unbrick tool for Realme GT Neo 2..
Feature:
wipe data (bypass pattern lock)
firmware flash via edl
Steps:
Download attached file
extract zip
Install qcom 9008 EDL driver on your computer
Run tool, Connect phone in EDL Mod
once com detected click Connect device by selecting any one method
then use Factory Reset button for Pattern wipe and Download button for firmware flash, for firmware flash locate extract ofp folder then click download button
Note:
you have to merge super.img using simg2img.exe
if header data of super image is not valid it will reject it in this condition use twrp dumped super image or from OTA
don't flash full firmware because it will wipe IMEI too, to fix bootloop edit rawprogram from extracted ofp and keep these partitions boot, recovery, super, vbmeta & dtbo, save modified file, delete all other rawprogram & patch files from firmware folder and load it in tool..
I am not responsible for any nvdata loss, process only after efs and qcn backup
Alguém sabe como fazer root no oneplus 9 Android 13.1?
First of all, please write in English. This is an English-only forum.
You can root the latest 13.1 firmware the same way you root others. I assume you already have the bootloader unlocked, proper drivers installed on your PC, and basic know-how of fastboot/adb commands. Here is the process:
You need to get the boot.img of your current firmware. You can extract it through MSM Tool's Read Back feature. In case you don't know about MSM, I have attached the boot.img for latest OOS13.1 firmware LE2115_13.1.0.500(EX01). Download and extract zip file and you will have boot.img. Copy this boot.img to your phone. Next you need to download/install Magisk v26.1 on your phone. Open the app, click Install and select that boot.img. Magisk will patch that boot.img and create a new patched_boot.img in your phone's Download folder. Copy that patched_boot.img to your PC. Reboot your phone to bootloader mode. Run this command to temporarily boot the patched_boot.img:
fastboot boot <your_patched_boot.img>
Note that this command is to boot it temporarily. It DOES NOT flash it. Ok, so once your phone boots up, open Magisk app again, click Install and select Direct Install. Now Magisk will root your current firmware permanently.
By this method of temporary booting and then rooting with Magisk's Direct Install method, Magisk will backup your original boot.img. So whenever there is a new software update, you can go to Magisk, select Uninstall, choose Restore Images, and Magisk will revert your original stock boot.img from it's backup. Then you can proceed with system update. Otherwise, without restoring original boot.img, the system update will fail because of patched_boot.img.
Here is the zip attachment. Make sure to extract it.
Thank you friend
shadabkiani said:
First of all, please write in English. This is an English-only forum.
You can root the latest 13.1 firmware the same way you root others. I assume you already have the bootloader unlocked, proper drivers installed on your PC, and basic know-how of fastboot/adb commands. Here is the process:
You need to get the boot.img of your current firmware. You can extract it through MSM Tool's Read Back feature. In case you don't know about MSM, I have attached the boot.img for latest OOS13.1 firmware LE2115_13.1.0.500(EX01). Download and extract zip file and you will have boot.img. Copy this boot.img to your phone. Next you need to download/install Magisk v26.1 on your phone. Open the app, click Install and select that boot.img. Magisk will patch that boot.img and create a new patched_boot.img in your phone's Download folder. Copy that patched_boot.img to your PC. Reboot your phone to bootloader mode. Run this command to temporarily boot the patched_boot.img:
fastboot boot <your_patched_boot.img>
Note that this command is to boot it temporarily. It DOES NOT flash it. Ok, so once your phone boots up, open Magisk app again, click Install and select Direct Install. Now Magisk will root your current firmware permanently.
By this method of temporary booting and then rooting with Magisk's Direct Install method, Magisk will backup your original boot.img. So whenever there is a new software update, you can go to Magisk, select Uninstall, choose Restore Images, and Magisk will revert your original stock boot.img from it's backup. Then you can proceed with system update. Otherwise, without restoring original boot.img, the system update will fail because of patched_boot.img.
Click to expand...
Click to collapse
Thank you for the specifics. I haven't decided whether or not I will modify my OnePlus 9 but I will keep this in mind.
Get token.
Flash token.
Enable unlock bl in dev options.
Install Magisk inside Andoid.
Congrats you did it.
Is there a boot img for LE2115_13.1.0.101(CN01)?
oneplus 9 LE2115_13.1. colorOS
ahumzert said:
Is there a boot img for LE2115_13.1.0.101(CN01)?
Click to expand...
Click to collapse
You can use MSM Tool to extract the Boot.img file, this is how most of use get our hands on the image files. I have provided a guide below on how to do this.
MSM Download Tool Read Back Mode: Create OnePlus Backup!
In this guide, we will show you the steps to take a backup of all the partitions on your OnePlus device via MSM Download Tool Read Back Mode.
droidwin.com