Who can help me to create an update.zip to my phone after OTA file checksum verification uptate without applications?
post OTA update.zip that i want to change updater script.
me gives me two errors when checking the phone's software.
phone manufacturer does not want to upload the full firmware flash.
phone is a yezz andy a5qp
I cannot help you for technical or support, but I can give two guides which can help you:
[TUTORIAL] Create your own UPDATE.ZIP
[GUIDE] Creating Rom Update.zip
Good luck
I do not know how to update the script not to verify checksum
Have you actually read my links ?
because my second link is a guide for creating an update.zip for your rom !!!
I don't understand what you need more ?
I understood that you don't want to verify checksum,
but with these links, you don't verify checksum.
Both links it's for create a simple UPDATE.ZIP to flash on your Android phone, in recovery mode.
I read all about create updater script, but i need help to edit actual updater script. Not create other. Thanks. Please download update.zip and then wait your opinion.
As I've wrote to my 1st answer, this forum is not a support forum, that's why I gave you two links for sending your request for help or more technical infos.
I add some links for other devices, maybe it will helped you:
- [GUIDE] introduction to edify updater script (installer zip)
- Chef Central > Android > [HowTo] Intelligent EDIFY updater-script - (Decides things during flash)
- How to edit an Updater Script to use an Rom as Second System
- [TUT] [for NOOB] editing updater-script for noobs!
I will closed this thread because I've provided you links for more support about your request.
Good luck
Related
Hello Guys,This is an updated guide for creating an update.zip for your rom.I know that there are a few guides out there but i think my guide is a bit simpler and straight forward.
Step 1:
Download AutoUpdateCreator_V1.1
Step 2:Extract file and click on "CreateUpdateZip.exe"
Step 3: You can either drag your created zip file or press ENTER (If you did not compress your rom yet)
Step 4:Now drag & drop your ROM Folder in the program
**NOTE** Structure of ROM folder should be as follows:
ROM FOLDER(Containing)
---System
---Data
Note: If you get an error it means that your ROM Structure is incorrect!!)
Step 5:Now that everything is done,zip is signed go to GENERATED ZIPS in autoupdatecreator folder.
Step 6:Copy your update-script in your generated zip file at /META-INF/COM/GOOGLE/ANDROID/
(Do NOT replace Update-binary file!)
Other Notes:
(Update Script must be created,there are templates available)
(Editing Update Script with normal windows text editor will cause Status 6 Error)
(Adding an incorrect or non existing file in update-script will also give you a Status 6 Error)
Cheers
Thanx for work.means now i can convert .tar files into zip?and can flash from cell
not working in last cwm
switch to Edify error
Hey man, i guess you can help me. I have a samsung double time and it can't be flashed via odin, my wifi and all connections, except mobile data are not working. So i have the .tar firmware extracted. Is there any way to create an update.zip file from this firmware.
Stavr0s91i said:
Hello Guys,This is an updated guide for creating an update.zip for your rom.I know that there are a few guides out there but i think my guide is a bit simpler and straight forward.
Step 1:
Download AutoUpdateCreator_V1.1
Step 2:Extract file and click on "CreateUpdateZip.exe"
Step 3: You can either drag your created zip file or press ENTER (If you did not compress your rom yet)
Step 4:Now drag & drop your ROM Folder in the program
**NOTE** Structure of ROM folder should be as follows:
ROM FOLDER(Containing)
---System
---Data
Note: If you get an error it means that your ROM Structure is incorrect!!)
Step 5:Now that everything is done,zip is signed go to GENERATED ZIPS in autoupdatecreator folder.
Step 6:Copy your update-script in your generated zip file at /META-INF/COM/GOOGLE/ANDROID/
(Do NOT replace Update-binary file!)
Other Notes:
(Update Script must be created,there are templates available)
(Editing Update Script with normal windows text editor will cause Status 6 Error)
(Adding an incorrect or non existing file in update-script will also give you a Status 6 Error)
Cheers
Click to expand...
Click to collapse
The Download link is offline
first off if this is a wrong place than sorry but ....i wanted to know how to add device support to the kitchen?? my device is GT-S6012 galaxy music duos) rooted .......does it use yaffs file system..........if anybody could suggest me a method ...........i also want to know the procedure to port cm or any othe custom rom as i am using the stock rom right now .....any help would be appreciated !!!! :good:
omkar333 said:
WARNING: If your device is not listed in post #1 of this thread, and it does NOT use a 'YAFFS'-based filesystem (e.g. usually only low-end devices use YAFFS), do not attempt to flash a ROM that you built with this kitchen. Instead, you must do the following if your device is NOT listed:
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
NOTE: This method does not guarantee your device will work with your custom ROM, however. Some devices may require more steps than just the edify_defs file, but the procedure is outside the scope of this FAQ. Ask around in the XDA sub-forum for your device if you need further help.
Click to expand...
Click to collapse
You can find it in third post:@ here
Thank's to this forum I have phone with 16gb memory, fastboot , TWRP and rooted - this is really great, thank you!
There is new update for 6039H - - 010 07p ~55Mb the of size, waiting for installation.
1st - where is this the file? Where "System updates" app is hiding it?
2nd - should we check update.zip somehow before flashing or just modify, flash and see results.?
Thank you.
Sent from my 6039H using Tapatalk
Just found where is ota hidden : /data/data/com.tcl.fota/.fotadownload
You need to have "Show hidden files" enabled in file manager to see/find it.
I tried use ota_modifier.sh get error:
ota_modifier.sh update.zip
The provided file is not a zip file!
then:
file update.zip
update.zip: Java Jar file data (zip)
In my system LXLE 14 witch is actually Ubuntu there is "zip" not a "Zip" witch is expected from script. I had to change this - editing script. One letter - big difference for linux.
Flashing update_modified.zip filed...
"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip .... [path to my modified zip]
Error flasing zip [path]
[edit]
If you see this error reason is - root. Need to be fully unrooted!
Now everything went fine. Flashed thru TWRP, rerooted. Whole process takes quiet of time be patient.
Hello,
Issue:
I receive a "Footer is wrong and Signature Verification failed" error when installing a Cross Compiled kernel through "adb sidechannel"
Question/help:
How do I properly install the newly cross compiled kernel on my rooted Samsung Tab 4 - SM-T230NU. I am stuck at this point. A step by step guide is GREATLY appreciated.
What I have done so far:
1. Downloaded what I hope is the right kernel from opensource.samsung.com
2. Cross compiled the kernel using toolchains recommended in the README file. I Cross Compiled on an Ubuntu system
3. I then downloaded AnyKernel and placed the zImage and a wifi kernel module in the appropriate location in the AnyKernel.zip file using "Archive Manager"
4. I received my error after I uploaded the AnyKernel.zip using adb sidechannel. Error was "Footer is wrong and Signature Verification failed"
Steps I have taken to troubleshoot or workaround thus far:
1. Install ClockWorkMod Recovery from the PlayStore but it does not support my tablet.
2. Reinstall AnyKernel and try again but it fails
3. tried AnyKernel2 but that fails as well.
4. Some tutorials teach the manual way (without Anykernel) but they all instruct one to get the boot.img. I could not locate the boot.img file so I got stuck.
Can you please provide some guidance?
Thank you,
sandmann76 said:
Hello,
Issue:
I receive a "Footer is wrong and Signature Verification failed" error when installing a Cross Compiled kernel through "adb sidechannel"
Question/help:
How do I properly install the newly cross compiled kernel on my rooted Samsung Tab 4 - SM-T230NU. I am stuck at this point. A step by step guide is GREATLY appreciated.
What I have done so far:
1. Downloaded what I hope is the right kernel from opensource.samsung.com
2. Cross compiled the kernel using toolchains recommended in the README file. I Cross Compiled on an Ubuntu system
3. I then downloaded AnyKernel and placed the zImage and a wifi kernel module in the appropriate location in the AnyKernel.zip file using "Archive Manager"
4. I received my error after I uploaded the AnyKernel.zip using adb sidechannel. Error was "Footer is wrong and Signature Verification failed"
Steps I have taken to troubleshoot or workaround thus far:
1. Install ClockWorkMod Recovery from the PlayStore but it does not support my tablet.
2. Reinstall AnyKernel and try again but it fails
3. tried AnyKernel2 but that fails as well.
4. Some tutorials teach the manual way (without Anykernel) but they all instruct one to get the boot.img. I could not locate the boot.img file so I got stuck.
Can you please provide some guidance?
Thank you,
Click to expand...
Click to collapse
Hi sandmann76
Thank you for using XDA Assist
Our experts at the below forum should be able to help you. Please be welcome to ask in there.
Galaxy Tab 4 Q&A, Help & Troubleshooting
Nice regards.
.
**Currently this method only works for Oneplus 7 beta.**
You can install Magisk using this method if you or on Oneplus 7 beta 5/6 and have an unlocked bootloader.
Please make a backup before using this. There is a stock boot.img pulled from each release zip in my Gdrive folder if you forget to back yours up.
Make sure you have updated Fastboot from here before flashing.
Downloads: Android 10 Images.
Note:- Currently only for O2 beta 5 and O2 Beta 6 i.e. android 10 beta 5 and beta 6. Try it on your own risk if you do it for other versions. And I can assure you something will break if you are not on these versions.
Code:
1. Download the patched boot.img from the link above
2. Using CMD or Powershell flash the image with this command:
fastboot flash boot magisk_patched.img
3. Reboot to os.
4. Install Magisk Manager Apk after booting to os.
5. (Optional) To flash [URL="https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943"]TWRP[/URL] grab the latest installer and flash it as a module in Magisk Manager reboot to recovery and install Magisk 20 zip.
7. To return to stock boot image "Non" rooted either grab your own backup boot.img download the stock boot.img from the link above and run this command:
fastboot flash boot boot.img
*Please do this if you are not on beta 5/6*
If you are unable to this, backup your boot.img and send it to me OR if you can do any of this contact me I will find some way
Instructions to patch your own images.
Code:
1. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
2. Extract your payload.bin from the stock ROM zip and copy it into the payload_input folder.
3. Run the payload_dumper exe.
4. When it's finished open the payload_output folder and copy the Boot.img to Desktop keep it there as a backup.
5. Copy the same boot.img to your internal storage on your phone.
6. Install the Magisk Manager Apk from here: [URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk Manager[/URL]
7. Open Magisk Manager and go to settings and change Update Channel to Beta and go back to the main screen and choose to install and select "Select and Patch a file"
8. Navigate to where you copied your boot.img on the phone.
9. Once it's patched you'll have a magisk_patched.img on your phone in the folder it says on the screen when done.
10. Copy that image to your Fastboot folder on your PC and flash it with
fastboot flash boot magisk_patched.img
Done!
As the great XDA people's saying goes '' I'm not responsible for any issues nuclear attacks or massive explosions from your device."
*Updated for beta6*
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64
Why exactly does this have a poll and what are we supposed to vote on???
Not sure why this thread was needed at all, the regular root method from the guide still worked when I rooted my OP7 last week
THREAD CLOSED! If interested in the subject please follow this already existing thread:
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
@DevilDipan
XDA Forum Rules (excerpt):
...
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.
...
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
...
Click to expand...
Click to collapse