Related
I downloaded Mcnut R13 and unzipped it. Where do I find the pit file and the tar file for PDA using Odin?
You dont unzip it, and you dont need odin to flash mancut, download rom manager and flash it with rom manager.
Sent from my SGH-T959 using XDA App
I see. But is there a way to flash it using Odin? I would like to learn how to use it in case I soft brick it.
So I do have Rom Manager installed already but never used it. It doesn't need to be unzipped?
And how do I change kernels using Rom Manager and Odin?
Please read my sticky's before you continue and mess up your phone.
I've read this guide already. It doesn't really explain how to use Rom Manager. And if it somehow it does and I missed it I apologize.
I'll keep searching in the Q&A forum.
It has the steps to rom manager step by step... not trying to sound rude, just making sure you do not F up.
Check your PM
s15274n said:
It has the steps to rom manager step by step... not trying to sound rude, just making sure you do not F up.
Click to expand...
Click to collapse
My apologies. Instructions are there and I read them last night. I just didn't remember reading anything about if the file containing the rom needed to be zipped or unzipped. Unless it was in one of the videos...
Just tried to install from the internal SD card. I placed the unzipped folder in the internal SD under a folder named R13. Then I checked the option to backup the rom but not to wipe data.
Long story short, installation aborted. Message was: Can't open /sdcard/sd/Mcnut_R13.Zip (No such file directory)
Someone told me it had to be unzipped first. But if it's looking for a file that ends in .Zip, maybe this is wrong.
no you don't unzip it at all...
download rom
put it on root of sd card (i.e. not in any folder)
boot into clockworkmod recovery via rom manager
if you get booted into stock recovery just keep choosing 'reinstall packages' until you get into CWM
make a backup of your current rom in case things go wrong
once thats done, choose 'install zip from sdcard' (4th option)
choose 'choose zip from sdcard'
navigate to preferred rom to install and push the power button to flash it
wait for it to finish and then reboot your phone
enjoy
I got clockworkmod working fine, but I am unable to loan ROMs. Whenever I downloand a ROM it opens in muiltiple files and it also happens with TNT, Thi is where Im stuck
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped, Clockwork will install it from the .zip file as is). trying to get VEGan 5.1 final
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
I cant fiqure how to get the update.zip. When I do open the files i get 3 files
META_INF,boot, and system. I tried to copy and paste all three files in the ROMs, but it never show the update.zip
You don't need an update.zip with clockworkmod recovery... you just need the rom that is zipped and can be named anything.
Stop unzipping the rom you are downloading and just copy it to your device. Install that with clockworkmod recovery.
Sent from my Viewsonic 10" GTab...
novicexda said:
I got clockworkmod working fine, but I am unable to loan ROMs. Whenever I downloand a ROM it opens in muiltiple files and it also happens with TNT, Thi is where Im stuck
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped]/B], Clockwork will install it from the .zip file as is). trying to get VEGan 5.1 final
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
I cant fiqure how to get the update.zip. When I do open the files i get 3 files
META_INF,boot, and system. I tried to copy and paste all three files in the ROMs, but it never show the update.zip
Click to expand...
Click to collapse
you've answered your own question, the rar or zip file you downloaded might be in diff names, but always leave it in zip format. if in rar, unrar and the zip file should be in it.
in clockwork recovery, you can update by update.zip or choose your own zip
tcrews said:
You don't need an update.zip with clockworkmod recovery... you just need the rom that is zipped and can be named anything.
Stop unzipping the rom you are downloading and just copy it to your device. Install that with clockworkmod recovery.
Sent from my Viewsonic 10" GTab...
Click to expand...
Click to collapse
That is my problem, if automaticly unzips when it downloads. I am not sure if its my windows setting becaue I am unable to download TNT lite because I keep getting " windows can no opem" message. Is there a way i can prevent it from unzipping? Thanks BTW
maybe use a diff browser to download or right click on link and "save as"
You might be hitting open instead of save ...
down load it direct to your Gtab
Download the file directly to your tab. Use ES file explorer to move it to your SD card if necessary. Reboot in to clock work - choose file from SD card-select it and install.
My Galaxy S2 has been rooted for about 2 months now and has been running on the Lightening ROM no problem, but last night when i tried to install a new ROM through CWM it wouldn't let me. I tried to install Villianrom and Cyanogen mod and both failed. Both ROM s were shown on my SD card as zip files and when i tried to move them they failed to get a signature and now when i boot into CWM neither of the ROM s show anywhere it just says NO FILES FOUND. Luckily i had a titanium backup of my Lightening ROM that i could revert to but i am puzzled as to why these ROM s wont install.
Any help would be appreciated
You are not supposed to extract them. They are supposed to be left as "zip" files.
They are getting left as zip files. All i do is download the RAR file and drag it onto sd card and there is nothing showing on the sd card i done all the necessary wipes and then when i try to select a rom off sd card this is what i get:
Android/ Attachments/ DCIM/ Download/ GOLauncherEX/ Galaxy_S_Unlock/ GoStore/ LOST.DIR/ ScreenCapture/ ShareViaWifi/ Sounds/ TitaniumBackup/ Wallpapers/ WhatsApp/ bluetooth/ burstlyImageCache/ clockworkmod/ data/ external_sd/ media/ openfeint/ samsungapps/ usbstorage/ zedge/ update.zip
But never a ROM to select from!!
kerriannec31 said:
They are getting left as zip files. All i do is download the RAR file and drag it onto sd card and there is nothing showing on the sd card i done all the necessary wipes and then when i try to select a rom off sd card this is what i get:
Android/ Attachments/ DCIM/ Download/ GOLauncherEX/ Galaxy_S_Unlock/ GoStore/ LOST.DIR/ ScreenCapture/ ShareViaWifi/ Sounds/ TitaniumBackup/ Wallpapers/ WhatsApp/ bluetooth/ burstlyImageCache/ clockworkmod/ data/ external_sd/ media/ openfeint/ samsungapps/ usbstorage/ zedge/ update.zip
But never a ROM to select from!!
Click to expand...
Click to collapse
is it zip or rar?
Sent from my Transformer TF101 using Tapatalk
Its says that it is a WIN RAR ZIP archive. Villianrom 2.4.2 from the villian website. At first you could see the file but it failed to get a signature and when i booted out and back in to CWM there was nothing and i can no longer see any files.
(I am using linux on my pc not windows.)
kerriannec31 said:
Its says that it is a WIN RAR ZIP archive. Villianrom 2.4.2 from the villian website. At first you could see the file but it failed to get a signature and when i booted out and back in to CWM there was nothing and i can no longer see any files.
(I am using linux on my pc not windows.)
Click to expand...
Click to collapse
What is the exact error of the "fail to get signature"? You said that you see "update.zip", is that the rom? Also, have you tried a new sd card?
Theonew said:
What is the exact error of the "fail to get signature"? You said that you see "update.zip", is that the rom? Also, have you tried a new sd card?
Click to expand...
Click to collapse
Really sorry but not sure of the exact error message that came up it was late last night and its not coming up with that now. I have tried a new sd card didnt make any difference. I tried the Update.zip and all i get is (replacing stock recovery with clockwork mod recovery) and then its stuck at the screen loading bar doesnt move at all.
I have even tried it with ROM manager and left it sitting for over an hour and still didnt do anything
kerriannec31 said:
Really sorry but not sure of the exact error message that came up it was late last night and its not coming up with that now. I have tried a new sd card didnt make any difference. I tried the Update.zip and all i get is (replacing stock recovery with clockwork mod recovery) and then its stuck at the screen loading bar doesnt move at all.
Click to expand...
Click to collapse
That means the update.zip file is ClockworkMod Recovery. Have you tried downloading the roms via Rom Manager then trying to flash them?
Theonew said:
That means the update.zip file is ClockworkMod Recovery. Have you tried downloading the roms via Rom Manager then trying to flash them?
Click to expand...
Click to collapse
Yes tried ROM manager and left it sitting for over an hour and it still didn't do anything
kerriannec31 said:
Yes tried ROM manager and left it sitting for over an hour and it still didn't do anything
Click to expand...
Click to collapse
Have you tried downloading the rom straight from the web onto your device via your device's browser?
kerriannec31 said:
Yes tried ROM manager and left it sitting for over an hour and it still didn't do anything
Click to expand...
Click to collapse
Just tried rom manager again and this is what came up:
--Installing package. . .
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:failed to seek in /cache/update.zip (Invalid argument
E:signature verification failed
Installation aborted
Theonew said:
Have you tried downloading the rom straight from the web onto your device via your device's browser?
Click to expand...
Click to collapse
Dont see how this will make a difference as i have tried downloading if through 3 different laptops and through rom manager
kerriannec31 said:
Dont see how this will make a difference as i have tried downloading if through 3 different laptops and through rom manager
Click to expand...
Click to collapse
What option do you select in CWM Recovery when you are flashing the rom?
Theonew said:
What option do you select in CWM Recovery when you are flashing the rom?
Click to expand...
Click to collapse
Chose zip from sd card and there is nothing showing up it says NO FILES FOUND
kerriannec31 said:
Chose zip from sd card and there is nothing showing up it says NO FILES FOUND
Click to expand...
Click to collapse
When you use a file explorer and look on your SD card, do you see the rom file?
Theonew said:
When you use a file explorer and look on your SD card, do you see the rom file?
Click to expand...
Click to collapse
I have just this minute flashed it back to stock and i am about to root it again and try to install villianrom. If it doesnt work this time i am just going to leave it stock. Will let you know how it goes.
Thanks again
Hi just to let you know phone is now rooted and has villianrom installed without a glitch. Dont know what the problem was but seems to have fixed itself now.
Thanks
I also had this issue early when I got my sgs2. Here is how I fixed it. I used the "unbrick" method, http://forum.xda-developers.com/showthread.php?t=1286432
So flash the package in pda that contains stock kernel and rooted rom or stock rom doesn't matter, then flash the code works kernel that contains cwm again, then you can boot into cwm and flash roms again. Not sure what the root of the issue was, I just know that this fixed my problem. Make sure that if you are flashing via cwm your are installing a .zip and not a .tar or other extension as the .tar are for odin. Let me know if this doesn't fix your problem I'll be happy to help dig a little deeper although I would bet that this will fix it
Edit: looks like you got it working while I was writing this
xx_bluedev_xx said:
I also had this issue early when I got my sgs2. Here is how I fixed it. I used the "unbrick" method, http://forum.xda-developers.com/showthread.php?t=1286432
So flash the package in pda that contains stock kernel and rooted rom or stock rom doesn't matter, then flash the code works kernel that contains cwm again, then you can boot into cwm and flash roms again. Not sure what the root of the issue was, I just know that this fixed my problem. Make sure that if you are flashing via cwm your are installing a .zip and not a .tar or other extension as the .tar are for odin. Let me know if this doesn't fix your problem I'll be happy to help dig a little deeper although I would bet that this will fix it
Edit: looks like you got it working while I was writing this
Click to expand...
Click to collapse
Yeah got it fixed i flashed the stock kernel in and then re flashed it with cf root then re installed villainrom and seems to be working fine so will see how it goes.
Hi just a quick question. When i install new firmware should i have to back out and reboot system once install complete or should the phone do it by itself??
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
What type of zip file is it?
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
markdexter said:
Used dsixdas Rom kitchen.
Built my own Rom using rogers stock RUU
starts to flash, then I get, error in sd card installation aborted
(status 0)
the last thing it was doing
minzip: extracted file "system/cuE:Error in /sdcard/marksrom
any takers??!!
Thanks guys
Click to expand...
Click to collapse
markdexter said:
its just the one that dsxidas tool spits out, although I did notice some differences.
If i click on the Rom.zip file, go to properties, then security. The only 2 that where check-marked was "modify" and "read & execute" So i compared that to a Rom that works on my device and noticed that in that same box they where all checked. - full control
modify
Read & execute
Read
Write
Special permissions
I changed those in my Rom so there all checked,however cant flash till tonight.
Just wondering if that could possibly be an, or the, issue
Not sure how to check what type of .zip file it is??
Click to expand...
Click to collapse
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only other common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
joeykrim said:
Lol .. the "check boxes" you're referring to only indicate the access permissions for the specific .zip file. When in recovery mode, everything runs as root. If there is any read permission on the file, recovery should be able to acces it without any issues. Further, you mentioned above the recovery was in the process of flashing the file indicating the recovery has no issues accessing the file.
If the recovery has no issues accessing the file, there shouldn't be any issues with the specific permissions of the ROM .zip file on that specific file system in recovery mode.
As a ROM developer, the next step to troubleshooting and understanding errors when flashing a ROM is by becoming familiar with the custom recovery error log.
The custom recovery shows very limited information on the display, but in the log shows much more detail. The logs are generally kept at /tmp/recovery.log and /cache/recovery.log.
The best process is to process the .zip file and when the recovery errors, open up the recovery log. If you can paste back here the few lines before the error occurred including the error we can start working on the issue.
We might need a copy of the .zip file to match up with the recovery log to understand how much progress was made in order before the error occured.
The only common place for ROM flashing errors when developing a ROM will be in the updater-script file. Might need a copy of this posted also.
In summary, the two most common places for issues occur either in the file name/structure of the .zip or in the updater-script.
Hope that helps! Good luck!
Click to expand...
Click to collapse
Amazing answer, thank you so much for taking your time with me, appreciate it, I'll try the recovery log, see what I get, as you can tell I'm pretty new to this, everyone has to start somewhere!
Thanks again buddy
Sent from my HTC EVO 3D X515a using xda premium
I have a Samsung Tab 2 with TWRP 3.3 installed. I wanted to try out some old jellybean roms but they didnt support my device codename so i edited updater-script to fix the issue. I did the same thing a year ago using winrar to make it into a zip again and the edited rom flashed with no problems but now trying the same thing with winrar or 7-zip doesnt work and gives me the "Invalid Zip File Format" error. Any way to fix this?
You try to flash the ZIP-file via ADB Sideload option from TWRP's Advanced option?
If you are facing this TWRP invalid zip file format issue, then by unpacking and re-zipping these zip files could simply fix your issue instantly.
jwoegerbauer said:
You try to flash the ZIP-file via ADB Sideload option from TWRP's Advanced option?
If you are facing this TWRP invalid zip file format issue, then by unpacking and re-zipping these zip files could simply fix your issue instantly.
Click to expand...
Click to collapse
No i copy them to my sd card and flash them from there
jwoegerbauer said:
You try to flash the ZIP-file via ADB Sideload option from TWRP's Advanced option?
If you are facing this TWRP invalid zip file format issue, then by unpacking and re-zipping these zip files could simply fix your issue instantly.
Click to expand...
Click to collapse
still doesnt work. then can i change my device codename so i dont have to edit updater-script?
Having the same problem here... fairly reputable zips Magisk and Flashify. Tried sideload and repakaging, no joy
I have the same problem in my Samsung J5 (2016).Model J510F.
I have the same problem "invalid zip file format" with Xperia Z2 and Resurrection Remix 10.
I found some possible help here. They recommend to unpack and repack the zip or install with ADB Sideload, too. Instructions for using ADB Sideload are also included.