Greetings!
First of all, a *HUGE* thank-you to bert_747 for his outrageous article on unbricking a Zenpad Z8.
(Viz.: https://forum.xda-developers.com/u/repair/hard-brick-asus-zenpad-s8-z580ca-z580c-t3465203)
One interesting thing with the Asus Flash Tool. It really, really, REALLY wants a zip file. Of course, you can override it but it originally expects to find a zip file.
My problem is that when I pick a valid zipped firmware file, it always fails with an "Unable to open zip file such-and-so - and it always fails regardless of the file.
The downloaded image/raw file (which is a zipped file anyway. . . .) worked like a Thing of Beauty. I was ultimately able to update to the latest firmware by copying it to the root of the internal drive.
Bizarre behavior. . . Anyone have any idea why?
Jim "JR"
Related
Credits for finding/pointing to this solutution go to AirwolfUK.
This is also hidden somewhere in a thread, but I think it deserves it's own thread. We (G4 owners) don't need to flash all our roms in Italian language. In stead of copying all the Update Utility files just copy "ROMUpdateUtility_Wizard_NoID.exe" and it will stay in English.
So if you get this error on you're G4:
ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA phone. Please get newer Update Utility
Just replace the "ROMUpdateUtility_Wizard_NoID.exe"! (I'll attach it too)
If you want to turn an already Italian installer into English replace all the files from "English Update Utility Files G4.zip".
Great! Thanks a lot for these! Hepled me a lot
Guess it should be a sticky, as not many people know where to find these things.
I've tried ROMUpdateUtility_Wizard_NoID.exe but keep getting
"Error 208: File Open.
The update utility can not open the requested file. Please check your update utility".
Anyone got any ideas what I am doing wrong?
maybe you're not with the utility and the nk.nbf in the same folder(all in the root of the folder).
Thank you so much...this just saved my otherwise bricked phone!
thx worked perfect in flashing the radio rom on my g4 to 2.19 uk!
I can't figure out how to upgrade my rom. I keep getting the dreaded Error 300.
Can somebody provide instructions on how to run this?
How?
How do I do this?
What should I replace?
Where should I put the "ROMUpdateUtility_Wizard_NoID.exe" file?
I just normally run the updateroom from a folder on my laptop, so where should I place "ROMUpdateUtility_Wizard_NoID.exe"?
I am attemping to flash Superrom
orelse4054 said:
How do I do this?
What should I replace?
Where should I put the "ROMUpdateUtility_Wizard_NoID.exe" file?
I just normally run the updateroom from a folder on my laptop, so where should I place "ROMUpdateUtility_Wizard_NoID.exe"?
I am attemping to flash Superrom
Click to expand...
Click to collapse
If the rom is one exe file, unpack it first with winrar. You'll see the file afterwards.
Yes I knows it becomes a exe file after I have zipped it.
Ok here it goes:
I run a normal ROM update exe file, I get the
"ERROR[300]: INVALID UPDATE TOOL
This Update Utility cannot be used for your PDA phone. Please get newer Update Utility"
Then what shall I do with the "ROMUpdateUtility_Wizard_NoID.exe " if I just run this one the message: ""Error 208: File Open."
Can someone set up a step by step guide please?
Seems you haven't upacked the rom executable. You should have multiple files afterwards (e.g. ROMUpdateUtility_Wizard_NoID.exe and nk.nbf). Just replace the ROMUpdateUtility_Wizard_NoID.exe! The file error tells it can't find your nk.nbf.
Damnnnnn Vippie Rocks!!!!!!!
How to do it ..
is it just click and run ROMUpdateUtility_Wizard_NoID .. and the application will do all .. or we just need to but all stuff in unpack flash ( any flash ) and install it to firmware ??
thanks allot in advanced
help still not working
I got the ROMUpdateUtility_Wizard_NoID.exe and I run it in the same folder as the rest of the files from the program and I STILL get error 300
Thanks Wes
Thank you men !!!
Thank you very much men, you saved my life !!!
Ok this file just bricked my MDA !
deathblooms237 said:
Ok this file just bricked my MDA !
Click to expand...
Click to collapse
Impossible.... it's you who did something wrong.
vippie said:
Impossible.... it's you who did something wrong.
Click to expand...
Click to collapse
No... I think your half-ass instructions confused everyone! you posted the update utility yet did not instruct that it should have been extracted in the same folder as the new ROM of the user's choice.
If you were to create a folder then extract the utility to that folder, then click on the extracted file, then for sure you will get the error msg.
Download first the ROM you want in a folder, All New ROMs will extract to two files. One of those files is the rom update utility file that you will need to replace with the Update Utility exe file in this post. To do this just extract the update utility tool ( posted here ) in the same folder of the downloaded and extracted ROM folder. You will then be up and running. Follow the instructions.
To follow up with my previous post, I would suggest you start with the 'Wizard_Love rom or the Button Rom as basis. This will reset your download prompts on your device to accept any Wizard compatible ROM of your choice. After the first update most likely you will not need this utility to update your favorite rom onto your device.
asfoor said:
No... I think your half-ass instructions confused everyone! you posted the update utility yet did not instruct that it should have been extracted in the same folder as the new ROM of the user's choice.
Click to expand...
Click to collapse
And even than it wouldn't brick the device. So your "no" should be "yes, you're right vippie"!
Did you notice the "developers" in the websites name? What are people doing on this forum if they don't know how to REPLACE a file. It isn't necessary to spoon-feed people.
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
Hello,
I'm very close to insanity now with trying to install cybermaus' custom rom for the A789 for the past 6 hours. I followed the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=1874403
The first thing it tells you to do is read another guide here, which I have read countless times:
http://bm-smartphone-reviews.blogspot.nl/2012/05/mt6575-flashing-tutorial.html
I have installed the drivers fine. I have two issues (so far) which are driving me insane:
1. Where on earth am I supposed to be getting this scatter file from? I have downloaded various versions from here there and everywhere over the internet. There is also one in the TWRP_recovery_v2.3.1.1_for_A789.zip file (which is with the ROM file on cybermaus' Dev-Host page) which I have tried (by the way that zip file is mentioned no where in any of these guides so god knows if that is involved or not). Where does the scatter file need to be placed in relation to the rom? When I load the scatter file into Flash Tool I either get all the file locations blank, and all the memory region address, begin address and end addresses all blank as well. Or if I extract the contents of the ROM zip file (A789_ROW_S107_cybermaus_ICS_v3.21.zip) and put the scatter file (one that I found on GSM Forums) into the same folder with the extracted rom contents I get ONLY the BOOTIMG with a location but still no memory addresses and it doesn't work anyway. I cannot get it to find a location of everything in the "Names" column (ie PRELOADER, DSP_BL, MBR, EBR1 etc) as it shows in the guides.I am following the guides exactly and have tried so many things to attempt to do this!
2. How, in gods name, does the A789_ROW_S107_cybermaus_ICS_v3.21 file get flashed at all according to these guides? Is it just me or does the actual ROM not get mentioned at all anywhere in both guides?? I CLEARLY DON'T UNDERSTAND THIS PROCESS and I don't want to be unfair but I don't feel like it's been explained very well !! Is the scatter file supposed to somehow tell the Flash Tool where the ROM is?? Do they have to be in the same folder?? Does the ROM have to be extracted or it remains as .zip?? Cybermaus himself in another post about scatter files says "I have seen several people asking 'where to find the scatter file'. Well, it comes with the ROM you want to flash. If your ROM file does not come with a scatter file, then is not a ROM file that can be flashed with the flash utility, but with an open recovery." O K, so, where is the one with his rom?? Am I stupid or is it not there?
I have flashed other phones successfully in the past with CWM where the guides had clear instructions on how to download and install CWM, then download the .zip file of the rom and then boot to CWM and install it, however this phone has none of that and I just can't see how this is supposed to work. Other people have clearly been able to do it!
Please can someone guide me a bit and explain to me what I have to do, considering I have followed the guide exactly a billion times and it does not work (for me anyway). Usually I find getting the drivers to work the annoying bit but this whole scatter file thing, WTF???
I would appreciate any help!
Please can someone who has a copy of A789_ROW_S107_cybermaus_ICS_v3.21.zip that THEY KNOW WORKS please upload it to somewhere and please post the link. There seems to be a problem downloading the version that is in the guide in Cybermaus' DevHost site, it downloads extremely slowly and then at the end files are missing every time, I have tried to download it many times on different days, the scatter file and lots of others are missing and sometimes it stops at around 150MB but says it is 100% done.
Please help, this might be what's preventing me from following the guide.
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk
Hi. I am a newbie in flashing phones. I am having a Lenovo A850. I was planning to flash it to Android Marshmallow (CynogenMod) . It was really hard to find the ROM. Somehow I managed to find one here: https://forum.xda-developers.com/le...rom-unofficial-cyanogenmod-13-lenovo-t3724018 . Once I downloaded it, I noticed that it is in RAR format. I tried entering CWM in my phone, and the RAR file doesn't show up. CWM probably does not support flashing RAR files.
What should I do now?
Maevinarsh said:
Hi. I am a newbie in flashing phones. I am having a Lenovo A850. I was planning to flash it to Android Marshmallow (CynogenMod) . It was really hard to find the ROM. Somehow I managed to find one here: https://forum.xda-developers.com/le...rom-unofficial-cyanogenmod-13-lenovo-t3724018 . Once I downloaded it, I noticed that it is in RAR format. I tried entering CWM in my phone, and the RAR file doesn't show up. CWM probably does not support flashing RAR files.
What should I do now?
Click to expand...
Click to collapse
What you do for a quick fix is to open the .rar file on your computer using a software like winrar, or 7zip. Then compress it using the software as a .Zip file then you can flash it easy as that.
Doing this is changing the file format all correctly with correct conversions so it should be alright. But be aware that this is a quick fix which I use and have success with. Not sure if it would work for you But it should, if it doesn't don't hit me ~ QAQ
Note that this is possible as well on phones using file manager with inbuilt rar,win support