Related
This was featured on the XDA Homepage a few days ago, but the developer just confirmed that it should work for any flashable zip, and *should* work on any phone.
Thought I would give the heads up here.
Could fix random Force Closes/Bootloops that people get even when they had wiped multiple times before flashing a new ROM.
Original Thread: http://forum.xda-developers.com/showthread.php?t=765989
Edit: See post 3 in this thread for my results.
This should save a few headaches, but I think most issues are caused with people not wiping....this wont be able to fix that.
Well, I finally put this utility to the test and here are my results.
Wiped Data/Cache/Dalvik, flashed BakedSnack 1.6 and immediately ran FixFlash. Here's my output:
Code:
E:\aEVO\android-sdk-windows\tools>adb shell sh /sdcard/FixFlash.sh
* daemon not running. starting it now *
* daemon started successfully *
FixFlash - Flash Verify and Repair Tool by SavvyX4
Gathering verification data...
Mounting phone file systems...
Extracting file information from flash log...
Verifying file integrity...
Hash mismatches detected: 13
Bad files...
/system/app/EPST.apk
/system/app/HTC_IME.apk
/system/app/IQRD.apk
/system/app/PCSCII.apk
/system/app/RSS.apk
/system/customize/CID/cidProfile1.xml
/system/customize/CID/cidProfile2.xml
/system/customize/CID/default.xml
/system/customize/COMMON.xml
/system/customize/MNS/default.xml
/system/etc/TPA2018.csv
/system/etc/WPDB.zip
/system/usr/keylayout/AVRCP.kl
Replacing bad files...
Verifying replacement file integrity...
All hash mismatches repaired!
So, it definitely does work for the Evo.
nice find... i'm sure my phone could use this!!
Are you a Cyclops?
Philosuffer said:
In my eye, it is a must use tool now.
Click to expand...
Click to collapse
Awesome tool btw, thanx for posting this!
ok I dont understand this
3. Copy both the original .zip file and the extracted folder of the .zip to the root of your sdcard
???? what is the extracted folder? theres multiple folders inside a rom zip?
rjmjr69 said:
ok I dont understand this
3. Copy both the original .zip file and the extracted folder of the .zip to the root of your sdcard
???? what is the extracted folder? theres multiple folders inside a rom zip?
Click to expand...
Click to collapse
Say your rom is BakedSnack1.6.zip, extract the contents to a folder called BakedSnack1.6 and place that folder on the root of your sdcard.
Make sense? Not sure how else to explain it.
I'm looking for a guide which tells how to make a own custom ROM from another one
I mean:
1. How to add/replace/remove apps in /system/app/?
1. a) Do they need to have special permission?
2. How to replace boot screen?
3. How to add custom kernel?
4. How to add Desire lockscreen/flip clock?
5. How to add transparent notofication area?
6. How to add Power menu?
I've been serching forum, but didn't find such tutorial. Would be very thanful to get this knowledge.
I think that will be very useful for maaaany android maniacs
1. Simple delete/copy apks in .zip file using 7-Zip or any other.
2. I belive you need to put bootanimation.zip in /data/local/ folder.
3. Idk
4. For Desire lockscreen you need edited HtcLockScreen.apk; for flip clock - HtcClockWidget.apk
5. Edited /system/framework-res.apk or /system/framework/com.htc.resources.apk. I'm not sure
6. You need edited /system/framework/android.policy.jar
69. Resign your zip file using Auto Sign
Attachment doesn't load, but I know about resigning ROM after everything is done
Ad. 1. As I thought, but do the need special permissions? And I also wonder one thing. Are they installed while flashing? Cuz they need to be in system registry, I think...
I have found this: http://wiki.android.com.pl/wiki/Kon...iana_instalowanych_aplikacji_razem_z_systemem
No any permissions etc.
Found this, too. Thanks.
to add a custom kernel you have to unpack the boot image and edit the ramdisk manually, although i think there is an option in dsixda's kitchen to unpack and repack the boot.img
I've got two more questions:
1. When signing, three files are created in folder META-INF: CERT.RSA, CERT.SF, MANIFEST.SF. But in other packages I see also com/google/android/update-script in META-INF. How to make it? Is it necessary?
2. If I want to make only flashable update file which changes one app or another file, eg. framework-res.apk, I have to create folder structure: system/framework/framework-res.apk, add it to zip archive (no compression?) and sing using Auto-sing. Am I right?
Edit:
Found nice guide there: update-script syntax
tomekk_nt said:
I've got two more questions:
1. When signing, three files are created in folder META-INF: CERT.RSA, CERT.SF, MANIFEST.SF. But in other packages I see also com/google/android/update-script in META-INF. How to make it? Is it necessary?
2. If I want to make only flashable update file which changes one app or another file, eg. framework-res.apk, I have to create folder structure: system/framework/framework-res.apk, add it to zip archive (no compression?) and sing using Auto-sing. Am I right?
Click to expand...
Click to collapse
The most important part of a recovery update zip is the update script. It will tell the recovery what to do. If you want an example of a basic update package, which replaces one file in the /system/framework (although a different one) can found here. Open this and read the META-INF/com/google/android/updater-script (or whatever its called). The syntax is pretty straight forward and I think its easiest to learn from the examples of updater scripts found here on XDA. For the simple case, of only replacing/adding files to the /system partition you can leave the updater script from the above example as is and only change the files under the /system directory in the zip.
Note, that the above example uses the newer upader-script (I hope I am writing this correctly, I am writing from memory) which also has a binary file in the same directory. Some update zips use the older "update-script" lone text script. For these kind of scripts, you can find a guide here.
Personally, I use RA recovery, and for this recovery you need to sign the update zips (last thing you do of course). At least for RA recovery, both the older "update-script" and the newer "updater-script" work fine, so its up to your personal preference which do you prefer.
Thanks. Found a guide you mentioned a couple of minutes ago and read it.
The more I know, the more questions it brings So one more thing. If I'd like to use the newer version of syntax: "updater-script", I need also to put this binary file in this folder. But I create/edit only "updater-script", binary file is the same for all packages, or do I need to edit it, too?
I built a kernel tool long time ago, very easy to use (only for linux)
1: unzip the file, place it where you want it eg your desktop
2: place boot.img in the working directory
3: double-click the menu icon or launch from terminal
4: it creates a new directory named BOOT-EXTRACT,edit what you want in there or change the kernel etc.. and repack it again via the kernel tool
see screenshot. here for those how want the tool >>> http://www.elelinux.se/tools/kernel_tool.zip
Edit: Only for Hero
tomekk_nt said:
Thanks. Found a guide you mentioned a couple of minutes ago and read it.
The more I know, the more questions it brings So one more thing. If I'd like to use the newer version of syntax: "updater-script", I need also to put this binary file in this folder. But I create/edit only "updater-script", binary file is the same for all packages, or do I need to edit it, too?
Click to expand...
Click to collapse
Only the updater-script. The binary is a replacement of the script-interpreter I think, but thats just an assumption.
elelinux said:
I built a kernel tool long time ago, very easy to use (only for linux)
Click to expand...
Click to collapse
And that's a good reason to install newest Ubuntu Thanks!
riemervdzee said:
Only the updater-script. The binary is a replacement of the script-interpreter I think, but thats just an assumption.
Click to expand...
Click to collapse
That's mine assuption, too, but would like to know it for 100%
Edit: I see you use it in your kernel update package. So you write only updater-script and place also update-binary next to it?
LOL, you've got help from every well known hero dev on xda, I'm sure you'll have all the info you need now to start building rom's. Good Luck!
Found an app called Easy Flashable zip Builder on this thread. Will test it soon.
tomekk_nt said:
Found an app called Easy Flashable zip Builder on this thread. Will test it soon.
Click to expand...
Click to collapse
But it is for MS Windows, or saw I wrong ? I have also built a tool to javasign files,but should probably write a manual first,it is easy to use but some dependencies maybe not so easy for a beginner with Linux.
tomekk_nt said:
That's mine assuption, too, but would like to know it for 100%
Edit: I see you use it in your kernel update package. So you write only updater-script and place also update-binary next to it?
Click to expand...
Click to collapse
Correcto
I'm getting an error when I try to install a .zip file through CWM recovery.
I get an error saying : E: Can't Open /sdcard/x (No such file or directory exists).
I've looked around and have learned that my best bet is to format my SD card. I can do that just fine, but I don't want to lose my data. I'm not flashing a ROM, it's just a custom lockscreen clock. If I format, I'll have to redo everything and lose all my data, apps, and system files (I'm running CM7 off of my SD card). But I need that for my zip to even be worth it.
I'm running a nightly build. Is there any possibility/plausibility that this could be a ROM-specific bug?
Is there any advice as to what I should do?
Thanks in advance.
SacTappingUni said:
I'm getting an error when I try to install a .zip file through CWM recovery.
I get an error saying : E: Can't Open /sdcard/x (No such file or directory exists).
I've looked around and have learned that my best bet is to format my SD card. I can do that just fine, but I don't want to lose my data. I'm not flashing a ROM, it's just a custom lockscreen clock. If I format, I'll have to redo everything and lose all my data, apps, and system files (I'm running CM7 off of my SD card). But I need that for my zip to even be worth it.
I'm running a nightly build. Is there any possibility/plausibility that this could be a ROM-specific bug?
Is there any advice as to what I should do?
Thanks in advance.
Click to expand...
Click to collapse
If you are running CM7 on SD you do not flash zips to it with ordinary CWM. Ordinary CWM will flash things to emmc. But maybe that is what you are trying to do. You do not say what you have on emmc.
If you want to flash the zip to the SD installation, make sure the zip file starts with update- and put it in the boot partition just like you do for roms. Then boot to SD recovery and the script will install it to SD.
An alternate way to flash things to SD installed CM7 is to use a special CWM modified for use on SD installs. You can read about and get it by looking at my tips thread linked in my signature. Item B5.
If you want to flash to emmc, make sure you are using an ordinary SD to put the zip on. Ordinary CWM always looks for partition one on the sd for the zip file. On your CM7 SD, the file is on partition 4 so CWM cannot find it.
So I'm trying to flash a new clock for my NC's unlock screen. The zip is called HoneyCombClock.zip. So do I just rename it to update.zip? That's not going to mess anything up?
Also yes, I booted into boot menu and selected emmc recovery. I thought that I needed to do CWM recovery.
I'll try the proposed method when I get a confirmation that it's not going to mess up my NC.
SacTappingUni said:
So I'm trying to flash a new clock for my NC's unlock screen. The zip is called HoneyCombClock.zip. So do I just rename it to update.zip? That's not going to mess anything up?
Also yes, I booted into boot menu and selected emmc recovery. I thought that I needed to do CWM recovery.
I'll try the proposed method when I get a confirmation that it's not going to mess up my NC.
Click to expand...
Click to collapse
You need to find out if it is a flashable zip... or if it is an app that has been zipped... I'm betting on the latter.
SacTappingUni said:
So I'm trying to flash a new clock for my NC's unlock screen. The zip is called HoneyCombClock.zip. So do I just rename it to update.zip? That's not going to mess anything up?
Also yes, I booted into boot menu and selected emmc recovery. I thought that I needed to do CWM recovery.
I'll try the proposed method when I get a confirmation that it's not going to mess up my NC.
Click to expand...
Click to collapse
If it is a flashable zip like Dizzy pointed out, you should rename to update-HoneyCombClock.zip. But I agree with Dizzy that it is probably a zipped apk file, not a flashable zip. Try looking at it with a zip program and see what you get.
It is indeed a flashable zip. I extracted it to make sure.
Also, I'm curious as to what you (leapinlar) meant when you instructed me to put the zip in the boot partition. From what I understand, that's the root of the SD card, right? Or has it changed?
SacTappingUni said:
It is indeed a flashable zip. I extracted it to make sure.
Also, I'm curious as to what you (leapinlar) meant when you instructed me to put the zip in the boot partition. From what I understand, that's the root of the SD card, right? Or has it changed?
Click to expand...
Click to collapse
Yes, it is what shows up on your PC when you take the card out of the nook and put it in the PC. Copy the zip there, rename it like I suggested above, put back in nook. When booting hold the n key until the boot menu comes up. Select SD and recovery and finish booting. The recovery script will install the zip.
I'm doing it and I'm not getting any errors, but when I boot into recovery, it runs through and shuts down without installing the zip. I don't understand what I could be doing wrong.
SacTappingUni said:
I'm doing it and I'm not getting any errors, but when I boot into recovery, it runs through and shuts down without installing the zip. I don't understand what I could be doing wrong.
Click to expand...
Click to collapse
And you renamed it like I said with update- on the front? (Don't forget the dash and no spaces.)
The file name is "update-HoneyCombClock". That should work right?
Sorry about these extended questions.
SacTappingUni said:
The file name is "update-HoneyCombClock". That should work right?
Sorry about these extended questions.
Click to expand...
Click to collapse
and .zip at the end?
It's automatically recognized as a zip file. If I put .zip at the end, it will show up on my tablet as "update-HoneyCombClock.zip.zip" Nevertheless, I'll try it and see what I get. I'll laugh if it works.
SacTappingUni said:
It's automatically recognized as a zip file. If I put .zip at the end, it will show up on my tablet as "update-HoneyCombClock.zip.zip" Nevertheless, I'll try it and see what I get. I'll laugh if it works.
Click to expand...
Click to collapse
Even if you get it flashing with your SD setup... it may not work if it requires honeycomb and you're running gingerbread.
It's meant for cm7. Here's a link to the thread I got the zip from: http://forum.xda-developers.com/showthread.php?t=959602
SacTappingUni said:
It's automatically recognized as a zip file. If I put .zip at the end, it will show up on my tablet as "update-HoneyCombClock.zip.zip" Nevertheless, I'll try it and see what I get. I'll laugh if it works.
Click to expand...
Click to collapse
What does the script say when it boots to SD recovery? Does it say install zip not found? And when you take it back out and look at it in the PC, is it still there? If it installed, the script will remove it. I know you can have your PC set to not show known extensions so it looks like it is missing. Temporarily disable that so you can really see the name. The script requires that it be named precisely, update- at the beginning, .zip at the end and no spaces.
The script doesn't mention any .zip installation. The zip file stays on my sd card root after recovery.
I just set my computer to show extensions. I'll retry the installation and make sure that every detail is perfect.
I remember doing something similar when I flashed a nightly on my nook. It was a .zip file. It wasn't flashing, so I looked around and got the impression that it would only instal if it had "update-" at the beginning. So I renamed it and it installed. I don't know what's up with my NC now. Is there any possibility that this could be a bug with the nightly? Or are installations not affected by ROM's.
SacTappingUni said:
The script doesn't mention any .zip installation. The zip file stays on my sd card root after recovery.
I just set my computer to show extensions. I'll retry the installation and make sure that every detail is perfect.
I remember doing something similar when I flashed a nightly on my nook. It was a .zip file. It wasn't flashing, so I looked around and got the impression that it would only instal if it had "update-" at the beginning. So I renamed it and it installed. I don't know what's up with my NC now. Is there any possibility that this could be a bug with the nightly? Or are installations not affected by ROM's.
Click to expand...
Click to collapse
No the existing rom will make no difference. It could be the zip itself. It has to be structured like a rom zip. It needs a /system directory with the files you want to flash. And it needs a META-INF folder with the script file buried in it. Where did you get the zip? Maybe I could look at it for you.
EDIT: I just downloaded and looked at it. It is just adding a single font to your /fonts folder. Nothing else. You can do that manually with root explorer. Just extract the font from the zip and copy to /system/fonts.
I got the zip from here: http://forum.xda-developers.com/showthread.php?t=959602
The clock can be flashed on any device with the following zip in recovery just like before.
http://www.mediafire.com/?b6xpw0pda671ujm
Click to expand...
Click to collapse
The zip has a font file and a meta-inf folder.
Look at my edit above
I replaced the file, but now I'm in an infinite bootloop.It just keeps doing the skateboarding android animation. Please tell me this isn't a problem with permissions. I don't know if I can even edit permissions now.
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.
I had 50pc japan version of s5(sc-04f), installed rom 'G900F.STOCK.FOR.SCL23.FULL.MINHQUAN'. The downside of this rom is that its pre-rooted. I managed to unroot it by goin in supersu & click 'full-unroot'. But i had multiple devices to flash, so is there a way for me to re-pack this firmware again after i unroot it? So that i could flash it to my other devices without root.
wee2000 said:
I had 50pc japan version of s5(sc-04f), installed rom 'G900F.STOCK.FOR.SCL23.FULL.MINHQUAN'. The downside of this rom is that its pre-rooted. I managed to unroot it by goin in supersu & click 'full-unroot'. But i had multiple devices to flash, so is there a way for me to re-pack this firmware again after i unroot it? So that i could flash it to my other devices without root.
Click to expand...
Click to collapse
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
ok done, thx 4 the info
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
wee2000 said:
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
Click to expand...
Click to collapse
Should we search for this firmware or you can provide a link to its thread?
the link is here : https://choimobile.vn/threads/6-0-1-scl23-stock-rom-g900f-full-port-v3-by-huaminhquan93.37412/
wee2000 said:
the link is here : https://choimobile.vn/threads/6-0-1-scl23-stock-rom-g900f-full-port-v3-by-huaminhquan93.37412/
Click to expand...
Click to collapse
Generally, if it's 6.0.1 and rooted systemlessly, you need to replace boot.img with a stock one and remove SuperSU app from system.img.
This ROM intended to be flashed from TWRP, so it's an ext4 image.
You can mount it to a linux system on your PC and remove anything you want.
I havent done anything like this before. Could u give me some links or guides? My PC is running Windows 10.
wee2000 said:
I havent done anything like this before. Could u give me some links or guides? My PC is running Windows 10.
Click to expand...
Click to collapse
Ok, here' a simpler way:
1. Make changes on one phone.
2. Make a TWRP backup of boot and system partitions.
3. Restore this backup on other phones. They must have TWRP installed, a 6.0.1 bootloader and modem.
You'll have to rename backup's folder path and to wipe cache/data/system before restore.
can i use winrar to extract & compile the rom, without linux? So that i will have a much faster flashing process for all other units..
wee2000 said:
can i use winrar to extract & compile the rom, without linux? So that i will have a much faster flashing process for all other units..
Click to expand...
Click to collapse
Ok, I've managed to download that ROM at last.
The things look even simpler.
To prepare an "unrooted" ROM:
1. Download the zip form this post and unpack updater-script somewhere.
2. Make a copy of V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip, open it with Windows Explorer and replace V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip\META-INF\com\google\android\updater-script with the file you've unpacked from the attachment.
3. Try to flash ans see if it's what you need.
thx so much, already passed all units to the buyer. ill try that on next batch restock, may iknow if there's a way to get the service menu shortcode *#0*# to work again? This rom doesn't has the service menu.
bbsc said:
Ok, I've managed to download that ROM at last.
The things look even simpler.
To prepare an "unrooted" ROM:
1. Download the zip form this post and unpack updater-script somewhere.
2. Make a copy of V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip, open it with Windows Explorer and replace V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip\META-INF\com\google\android\updater-script with the file you've unpacked from the attachment.
3. Try to flash ans see if it's what you need.
Click to expand...
Click to collapse
I've replaced the updater-script in the zip file, but supersu is still there