Related
Is there an app available to flash .img files
Thanks in advance.
Sent from another galaxy using Tapatalk 2
Odin prefered
or ROM manager or the CWM app perhaps (personally prefer non-App methods so...)
mobile Odin
slaphead20 said:
mobile Odin
Click to expand...
Click to collapse
How do you flash an .img with mobile Odin?
Sent from another galaxy using Tapatalk 2
What .img are you trying to flash? I flashed a recovery image by just putting it in recovery on MO
slaphead20 said:
What .img are you trying to flash? I flashed a recovery image by just putting it in recovery on MO
Click to expand...
Click to collapse
Yes it's a recovery.img I'm trying to flash can't work out how to do with mobile odin
Sent from another galaxy using Tapatalk 2
Click on recovery, browse to the .img and select, then flash, having said that,I just tried that and my mobile Odin isn't seeing the files at all, haven't used it for a while, but it worked last time I used it, but I'm running dual boot so it might not work! Confused!
slaphead20 said:
Click on recovery, browse to the .img and select, then flash, having said that,I just tried that and my mobile Odin isn't seeing the files at all, haven't used it for a while, but it worked last time I used it, but I'm running dual boot so it might not work! Confused!
Click to expand...
Click to collapse
I'm not dual booting and it does nor recognize .img files.
Sent from another galaxy using Tapatalk 2
Since you're dealing with a recovery.img: http://teamw.in/project/twrp2/114
Thanks for help, if anyone knows how to flash .img files please post app name
Sent from another galaxy using Tapatalk 2
briandevlin said:
Thanks for help, if anyone knows how to flash .img files please post app name
Sent from another galaxy using Tapatalk 2
Click to expand...
Click to collapse
I think you can flash .img with heimdall but I have never used it myself
briandevlin said:
Thanks for help, if anyone knows how to flash .img files please post app name
Sent from another galaxy using Tapatalk 2
Click to expand...
Click to collapse
Fair enough, I guess I should've read your OP more carefully. I was able to use dd to switch to TWRP recovery fine...
The Play Store page for Mobile ODIN says, "Separate files (named after the partition) as well as .tar and .tar.md5 files are supported." If I'm reading it correctly, renaming your img file to recovery.img exactly and then using the Open File button should work (or if not, perhaps the Recovery button)
If that still doesn't work, you can get twrp-sgs3.zip from here, replace the twrptr6.img file inside the ZIP with your recovery.img (keeping the twrptr6.img name) and then install it with CWM (this will essentially do what that dd command on the TWRP site does)
rename file to recovery.img and use mobile odin select recovery option and navigate to .img and flash
sitimber said:
rename file to recovery.img and use mobile odin select recovery option and navigate to .img and flash
Click to expand...
Click to collapse
I have Odin 3.09, I don't have a "recovery" button to flash the image file of CWM 6.0.4.6.... -_-
You can use terminal emaluator.
Google it.
If i remember correctly the heimdall utility can flash .img files. It's command line though, but i'm sure it wont be a problem for you.
the only way is to convert .img to stupid .tar.md5 to flash via odin, I think....
velizarcho123 said:
the only way is to convert .img to stupid .tar.md5 to flash via odin, I think....
Click to expand...
Click to collapse
You're both replying to people that posted years ago. As if answering now helps anyone or as if they'll actually be able to see and use your responses.
benvaj said:
If i remember correctly the heimdall utility can flash .img files. It's command line though, but i'm sure it wont be a problem for you.
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk
Is it specific for each device? Or does it depend only on finding the correct partition/block to be extracted?
Could you point me to further readings about that?
Thanks.
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
DopeyTheOne said:
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
Click to expand...
Click to collapse
Well, that link is to proceed AFTER you have boot.img at hand. I want to find a way to extract it from my phone (assuming default.prop can be changed in there).
Thanks.
When you make a back up with CWM, you have a copy of your bootimage in the clockworkmod map, not?
That's the thing ... I am trying to figure out how to get that backup in hand at first.
Currently, following the method in http://droidcore.blogspot.com.br/2012/12/how-to-edit-initrc-in-android.html
It seems to use the same scripts as cited in your link.
Will post results afterwards.
Don't make things more complicated as they are. If you just install CMW recovery (or TWRP for that matter) for your device, you have your full backup in minutes, including one of your bootimage, then use the script from my first post.
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
MrCabana said:
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
Click to expand...
Click to collapse
I used a CWM image to root my device. Booted up with that image, and flashed SU....after that you can use su, and apparantly, with the changes you made with your bootimage...you'll be like God on your phone
Sent from my S500 using xda app-developers app
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Click to expand...
Click to collapse
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
bromeara said:
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
Click to expand...
Click to collapse
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Alright thank you. I'm fairly new to the android ecosystem and to boot I'm working on a Fire tablet so its running fireos and amazon doesn't really make it easy to touch their code
think he is facing the same situation as mine, for hk version of htc u12+, its hard to find the proper RUU or firmware from internet. Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Vita.T said:
Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
dano.556 said:
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
Click to expand...
Click to collapse
Ok....
I am assuming that the op has a samsung device....
Same Problem
Loku_kika said:
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Click to expand...
Click to collapse
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Lloydster said:
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Click to expand...
Click to collapse
just google "Latest Software Version for OPPO OPPO AX7" and go to the Software Updates page on oppo-uk.custhelp.com. Download 2.4GB ozip file (like CPH1903EX_11_OTA_0210_all_oStq7F7jxqfF.ozip) and unpackit with 7zip program. You'll find boot.img inside .ozip file.
I do not have root, there is no recovery or rom for my phone, Can I extract the boot.img from my phone storage, to patch it with Magisk?
Hi,
I was trying to flash twrp to my friends s3, and we did everything correctly. Using Odin we flashed the .img file. But it didn't work. Having some previous experience with this, I tried flashing an older version of twrp, but it still didn't work. If anybody has any ideas on how to get it onto his phone, please respond.
Thanks.
@Chattamax: for Odin, you need tar-file, of course.
rp158 said:
@Chattamax: for Odin, you need tar-file, of course.
Click to expand...
Click to collapse
.img and .tar both work. The main download on twrp website also is an .img
@Chattamax: you can't flash an img by Odin. On TWRP for i9300 you get each version as tar-file, too.
(img are for updating within TWRP or installing from command line)
Ah, I see.
So I just flash the .tar instead.
Ok I'll try that, thank you.
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.
Hey guys,
I've tried to update my Nord 2 to the newest software (A.12) but every time I try it, it just reboots after a couple seconds and displays an error message:"Verification error". I've tried rebooting it multiple times, without any success. It is rooted with magisk and the bootloader is open, but I don't have TWRP installed. Could you guys hook me up with a solution?
Regards
Take a look: https://forum.xda-developers.com/t/...rooted-nord-2-any-incremental-update.4347813/
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
AdamBarath said:
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
Click to expand...
Click to collapse
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Raygen said:
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Click to expand...
Click to collapse
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
AdamBarath said:
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
Click to expand...
Click to collapse
Yup, the order is:
Backup EVERYTHING.
Flash stock boot image for your current version (A.11)
Flash update.zip via recovery
Flash patched vbmeta via fstboot
Re flash TWRP via fastboot
Reflash magisk:
Flash the .zip it via recovery (not reccomended). OR,
Download and flash an already patched boot image for the updated version (A.12). OR,
Extract your stock updated boot image (A.12) with adb shell and dd (or download it), boot into system, patch the image with the magisk app, flash the patched boot image in recovery.
If during one of these steps you get back the stock recovery, just boot into fastboot and reflash twrp. Without magisk installed the rom tends to restore the stock recovery by itself.
Thank you for your help!
Worked like a charm!