Trying to flash CopperheadOS with multirom on N6P.
But I can't flash the image in TWRP so I'm trying create a flashable zip.
But problem is all the guides and tutorial are very outdated (with most of them mentioning "Android Kitchen")
Where should I go to find help for this?
/Omen
If you are on the latest TWRP, you can flash an image file to the system partition by clicking the Install Image button when selecting a file to install.
nathanchance said:
If you are on the latest TWRP, you can flash an image file to the system partition by clicking the Install Image button when selecting a file to install.
Click to expand...
Click to collapse
That way doesn't work because I use multirom, it has a modified TWRP (it's still the latest version doh)
Sorry for shameful bump but I can't find an answer whatsoever
nathanchance said:
If you are on the latest TWRP, you can flash an image file to the system partition by clicking the Install Image button when selecting a file to install.
Click to expand...
Click to collapse
In what I have been able to find there was a META-INF folder that was a part of the back-ups now all I see from my stock backup is .win files, not tar.md5
Now I can guess that the naming is still similar so can you compress the system.ex4 files and have the same process with a file format change.
Related
For some reason I am not able to load the recovery images so that I can flash the rom to Madaco's ui.
When I download the recovery image it downloads as a .IMG I have unzipped it and put in in my superboot folder, run command and find the folder, but it does nothing.
Is there a special application to download .IMG? I have tried winzip a few others.
I have also used the Terminal Emulator and placed the file directly on my SDcard and opened the file from there, but nothing happens.
Any Suggestions???
Thanks in advance.
wrong place to ask a ?
you are really totally wrong here. also, if the *.img file is in a *.zip file it probably means it has been made into a update.zip that can be flashed... i can be wrong though...
in general, nothing here that has *.zip extension is generally to be opened with WinZip... the *.zip files here are update zips that can be flashed (e.g. a ROM, a radio, etc.).
best advice would be to guide you to Amon_Ra's recovery image thread (first page of Nexus One Android Development).
you can also search "Amon_Ra"
there is the topic recovery image
Everything you need is in this thread.
http://forum.xda-developers.com/showthread.php?t=611829
Hey all, long story short I need to find to the Nougat vendor.img. The link to it from the debloated ROM page appears to be down, so if anyone else has a link to the .IMG file that would be helpful. In the WETA ROM thread, the dev said you go extract it from the .zip but I have no idea where it is/how to flash it in fastboot if it's not a .IMG file. Thanks.
Sent from my Nexus 6P using XDA-Developers mobile app
If the file icon looks like a page with a cd/dvd on it, that is an .img file. Or just right click and look at the properties.
Eric214 said:
If the file icon looks like a page with a cd/dvd on it, that is an .img file. Or just right click and look at the properties.
Click to expand...
Click to collapse
In the zip, the vendor file has a .new.dat extension. Would I change that to .img and flash it in fastboot? Or would that be a mistake?
if the dev says the vendor.img file is included it should be in there, your have to dig through the compressed folder to find it, its usually named vendor.img you might have extensions hidden, or if you have a known .img file elsewhere it will likely have the same icon next to it in the file tree.
you can just extract it and rename the file with a straight ".IMG" prefix and flash that from your ADB folder or using your chosen tool
hutzdani said:
if the dev says the vendor.img file is included it should be in there, your have to dig through the compressed folder to find it, its usually named vendor.img you might have extensions hidden, or if you have a known .img file elsewhere it will likely have the same icon next to it in the file tree.
you can just extract it and rename the file with a straight ".IMG" prefix and flash that from your ADB folder or using your chosen tool
Click to expand...
Click to collapse
So that didn't work (phone wouldn't boot past splash screen) but I did flash this .img file https://www.androidfilehost.com/?fid=24651430732236715 and it worked
RollTribe said:
So that didn't work (phone wouldn't boot past splash screen) but I did flash this .img file https://www.androidfilehost.com/?fid=24651430732236715 and it worked
Click to expand...
Click to collapse
What issue were you having that you needed the vendor image, if you mind me asking?
Was your phone stuck in the splash screen loop?
defcondev said:
What issue were you having that you needed the vendor image, if you mind me asking?
Was your phone stuck in the splash screen loop?
Click to expand...
Click to collapse
I had an old version of TWRP (wasn't aware that there was one that worked with Nougat) and needed to flash an old vendor to get it to work, then a newer one to get my phone to boot. I flash the DP5 vendor and the phone booted just fine, but there was a warning message and I figured it would be better to get the updated vendor.
Kinda makes this noob sick. I just got a new Moto G4 X1625 (not Amazon). Next came the steps to unlock the bootloader with Motorola and to install TWRP. Everything had gone so easily by following some how-to steps I jumped to the next step of installing SuperSU without doing a backup – thinking it was simply adding an app. Big mistake! Reboot and now always stuck on the logo boot animation.
Okay, so I found and tried use TWRP to install ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip in an attempt to get back to stock. No luck there since install always aborts with a "Could not find 'META-INF/com/google/android/update-binary' in the zip file."
I checked a couple of other ROMs and that META-INF directory doesn't seem to be included in them either.
What do I need to do just to get back to normal eliminating the effects of that SuperSU install? Help greatly appreciated.
That file you downloaded is not a flashable file.
Instead, read this linky
Thanks for the helpful clue @t0mm13b. I followed the approach at <http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/> and executed the listed commands from my MacOS Terminal. They did the job resulting in a fresh install after bootup.
2-1/2 questions…
1. Are flashable ROM files readily available? The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
2. Is TWRP not useful for these stock ROMs?
The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
Click to expand...
Click to collapse
As a general rule of thumb, read the accompanying text to the link of the download, on a web page where you find one. It will tell you if it's flashable or not.
Factory images, just like what you had to carry out previously, never have, and do not have the `META-INF` directory. They usually contain img files that requires `fastboot flash`.
On the other hand, OTAs and flashable zips will have that in their respective zip file.
Thanks again @t0mm13b for the clarification. I often didn't see info about whether a ROM is flashable in link or web page text, but it may have just been assumed based on being aware of what the zip contains.
Hey all, I've looked all over an can't find the answer to this... I have a NAND backup I made using TWRP, however, I had the problem many have had with getting errors when trying to restore it. So I thought I'd try a different way by creating a TWRP flashable file from the NAND files. I have taken the files from the backup and extracted them using CYGWIN. I read a thread here:
https://forum.xda-developers.com/showthread.php?t=2746044
But I'm stuck on a couple of things... First, the part about using the META-INF folder from another ROM... I've checked the files in in the META-INF folder and notice that the updater-script is what loads the files and directories. But none of the META-INF files I have found matches my backup files.
The files I want to flash are the complete system folder, complete data folder and the boot.img file. Is it possibly to flash these with TWRP without the META-INF folder/files? If I have to use the META-INF how do I make sure all the files and folders are flashed?
Would it be better to create an ODIN flashable file and just use Odin to do the flash? If so should I put the system and data folders into one file and then use the boot.img (or would I put the boot.img finle into a tar) in the Bootloader spot in Odin?
Thanks in advance.
I need a zip firmware file for nokia 6 TA 1021. Because my nokia 6 can not flash with OST. However, I can flash the zip file by recovery 3.2.1. Thanks.
P / s: My English is very bad. sorry
letgol said:
I need a zip firmware file for nokia 6 TA 1021. Because my nokia 6 can not flash with OST. However, I can flash the zip file by recovery 3.2.1. Thanks.
P / s: My English is very bad. sorry
Click to expand...
Click to collapse
I already shared the firmware here: https://forum.xda-developers.com/showpost.php?p=75076587&postcount=7
This is the September version. In order to get to the newest version of Nougat, you have to install the update zips one by one. They are on the forum too.
Happy flashing
ZeroPointMax said:
I already shared the firmware here: https://forum.xda-developers.com/showpost.php?p=75076587&postcount=7
This is the September version. In order to get to the newest version of Nougat, you have to install the update zips one by one. They are on the forum too.
Happy flashing
Click to expand...
Click to collapse
Now I have to flash 7z file by recovery?
letgol said:
Now I have to flash 7z file by recovery?
Click to expand...
Click to collapse
No, unzip the archive and then click on Edit phone Information on OST. You can do this while the archive is extracting to skip some wait time. Then open your favorite terminal program and flash the img files from the archives like this: (example with the included fastboot-android.exe on Windows)
fastboot-android.exe flash x x.img. X is the filename of the img file. You can look into my linked article to see which partitions you have to flash for a complete system reinstall. Note: if you flash recovery, your twrp will be replaced by the stock recovery.
ZeroPointMax said:
No, unzip the archive and then click on Edit phone Information on OST. You can do this while the archive is extracting to skip some wait time. Then open your favorite terminal program and flash the img files from the archives like this: (example with the included fastboot-android.exe on Windows)
fastboot-android.exe flash x x.img. X is the filename of the img file. You can look into my linked article to see which partitions you have to flash for a complete system reinstall. Note: if you flash recovery, your twrp will be replaced by the stock recovery.
Click to expand...
Click to collapse
Thank you. I will try
ZeroPointMax said:
No, unzip the archive and then click on Edit phone Information on OST. You can do this while the archive is extracting to skip some wait time. Then open your favorite terminal program and flash the img files from the archives like this: (example with the included fastboot-android.exe on Windows)
fastboot-android.exe flash x x.img. X is the filename of the img file. You can look into my linked article to see which partitions you have to flash for a complete system reinstall. Note: if you flash recovery, your twrp will be replaced by the stock recovery.
Click to expand...
Click to collapse
Thank you. I did it
letgol said:
Thank you. I did it
Click to expand...
Click to collapse
:good: