When i flash .zip file i have some problem. So how to uninstall flashing zip..please help me.. in my Nexus 5 Mobile
You can't uninstall a zip.
You'd either restore your nandroid backup which you should take before flashing the zip, or flash a zip depending what your original zip was. For example, flash a system mod, reflash your ROM.
What, specifically did you flash? Some mods will have a revert zip to uninstall it the OP. If there isn't one, you can always dirty flash your ROM again. More details would help.
Related
So I got a phone with cryogen7 or whatever from my friend. I want to make it completely stock again. I dont have his sd card. so I just have mine from another phone. I downloaded the stock g2x gingerbread file, but when I try to restore it, i get a md5 mismatch or something. I saw a thread on that but I dont know how to write code. just hoping someone could help me out. thank you.
Download it again, also try another browsee
Sent from my LG-P999 using Tapatalk
Download the V21E nandroid from this thread:
http://forum.xda-developers.com/showthread.php?t=1196019
Then use your computer to extract the folder from the zip file you download. Copy that folder to the sdcard on your phone, and place it in the ./clockworkmod/backup directory. Then boot into clockworkmod recovery and select backup/restore > restore and then choose the backup folder you just copied to your sdcard. Make sure to do a full wipe/factory reset from within clockworkmod before you reboot or you might get a bootloop.
If you want stock recovery then use tga gunmanns one click app in the development section to restore stock recovery. Then you'll be 100% unrooted stock again.
IF the name of the zip has spaces in it it wont flash
Mister Hat said:
IF the name of the zip has spaces in it it wont flash
Click to expand...
Click to collapse
Nandroid backups aren't flashable zips. With the files from the thread i linked to, you have to extract the backup folder from the zip before you restore it. But yes, you are correct that spaces in the name of the backup create issues.
Did you figure it out yet?
Sent from my LG-P999 using XDA App
it freezes on "checking md5 sums"... don't know what to do
Are you using your computer to extract the V21E folder from the zip file? Ive used my phone before to extract it before and gotten the md5 mismatch error, and then used my computer to do it and it worked fine.
are you sure the rom your using is for your phone?
New to the forums and flashing ROMs in general, so please forgive my n00b-fail. (I did, at least, search the forums for an answer first. )
Samsung Infuse 4g
AT&T
Was running stock ui, rooted
Was able to flash and restore to factory using Odin (following Jordan's http://forum.xda-developers.com/showthread.php?t=1318160)
Took file DarkROM_JVR_Infuse_10.3.rar and unpacked
Repacked using .zip format
Placed .zip on internal SD
Rebooted to CWM Recovery and wiped data/factory reset as well as cache
Selected install from zip on sd card
Selected DarkyROM_JVR_Infuse_10.3.zip
Screen currently says:
"ClockworkMod Recovery v2.5.1.3 - Voodoo lagfix
-- Installing: SDCARD: DarkyROM_JVR_Infuse_10.3.z
ip
Finding update package...
Opening update package...
Installing update..."
Been stuck like that for the past hour. Have I bricked my phone? Should I go back and follow the "UnBrick the UnBrickable Infuse4g" thread?
Thanks.
Umm....darky rom. Rar? ??? I did not pack it in rar or tar format...that's your prob....its pack as a cwm flashable zip
Sent from my SAMSUNG-SGH-I997 using xda premium
Thank you for your response.
I'm now aware that, as you put it, "...that's my problem."
I'm not sure why the file downloaded as a .rar file. Is there a specific extension to the package process that changes the code? Would not unpacking and repacking as a zip do the same thing?
After "playing with it," I got the phone to launch back into the stock ROM. So. Thanks to myself, on that one.
Problem solved.
Are u sure the file u downloaded was a .RAR file ? or it looked like pile off books that why u calling it a .RAR file ?
If you want I recreated DarkyRomV10.3.zip which is of course flashable in CWM, It has 2 fixes that the original DarkyRom doesn't have.
Darky Rom Fixes:
Dman's Build.Prop Fix
Bigfau's Battery Notification Fix
-------------------------------
Installation:
1 DOWNLOAD DARKY ROM
2 BOOT INTO CWM
3 WIPE DATA, CACHE, DALVIK CACHE
4 FLASH DARKY ROM
5 REBOOT
6 ENJOY
DarkyRomFix
Download Here: http://www.multiupload.com/3Y0BREZCFT
Inorder to fix the Superuser Update you will need to flash the SU Binary Update Fix
Download Here: http://www.multiupload.com/RIAHB3BS8C
@rkkaranrk - Very good idea, but no. I actually didn't have a program that could decompress .rar files on the system I was using. I downloaded a copy of WinRAR specifically for that.
@Axiomkid - Thank you. I'm going to try it when I get home. Now that I've had the oportunity to play around with some of the backup apps, I'm much more confident to try new ROMs.
@Axiomkid - This is a silly question, I'm sure, but how do I flash the superuser update? Do I need to?
.icereach said:
@Axiomkid - This is a silly question, I'm sure, but how do I flash the superuser update? Do I need to?
Click to expand...
Click to collapse
Flash in CWM. You should flash it as it will keep superuser up to date.
Sent from my SAMSUNG-SGH-I997 using xda premium
Winrar makes the zip file looks like RAR so the file u downloaded was very much a zip file.
What is the proper method of "returning to stock"?
I see a note in the Hydra Rom installation section that says returning to stock will delete clockwork recovery so I'm ASSUMING "returning to stock" means more than just flash a stock rom because simply flashing a "stock rom" wouldn't affect recovery, would it?
EDIT: So I found my answer, to return to stock you simply need to download the appropriate firmware package from the ASUS website, extract the zip inside of the zip it downloads as, then flash the extracted zip. It returns you to stock ROM and after a reboot, stock recovery.
shrumhead said:
EDIT: So I found my answer, to return to stock you simply need to download the appropriate firmware package from the ASUS website, extract the zip inside of the zip it downloads as, then flash the extracted zip. It returns you to stock ROM and after a reboot, stock recovery.
Click to expand...
Click to collapse
Hi everybody,
I'm in the same situation of the author (but for me is CM9).
Like him, i've downloaded asus firmware, extract the zip but i don't understand the step in red bold.
Anyone can explain how to "flash" ?
Thanks in advance (and sorry for my poor english)
if you like to flash stock from recovery. You extract the dl file one time.
You now have a zip file which contains a blob.
Put this zip file to your internal sd.
Goto recovery and choose instal zip, then choose zip, then go to the zipfile and select it, then choose yes and flash it.
After this you are back to stock.
Best doing it with CWM, cause some users like me had problems doing this with twrp
So I think I made a stupid mistake.
I was trying to reset google wallet and It hung at 97% and wasn't able to reset. I used the google wallet installer to basically change my build prop to the nexus build prop. I figured it would just overwrite my original wallet app anyway, and once my build prop was changed to the nexus build prop I could simply reset the app from there.
Anyways, phone rebooted and it's stuck in a bootloop and isn't getting passed the boot animation screen. I can get into recovery mode and download mode just fine. I tried restoring a backup I had with CWM and it says "md5 mismatch error". I really have no idea what to do at this point, and would rather not go completely to stock since I know my data is still there. Also I'm concerned to even restore a backup because i'm pretty sure my build prop was changed. I'm also wondering if it would be possible to simply factory reset and flash a new rom on top of it.
Any help would be greatly appreciated.
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Khizar Amin said:
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Click to expand...
Click to collapse
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
BadUsername said:
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
Click to expand...
Click to collapse
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Khizar Amin said:
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Click to expand...
Click to collapse
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
BadUsername said:
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
Click to expand...
Click to collapse
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Khizar Amin said:
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Click to expand...
Click to collapse
Restoring my system partition only from advanced restore worked perfectly. All my apps stayed how they were and I didn't have to update all of my apps after I restored. Way better than doing a full restore in this case.
Thank you for this advice, this will be a very helpful method to me if I make any mistakes while messing with anything in my system folder. And yes, it was certainly an experience for me.
Sent from my SCH-I535 using Tapatalk 2
I have a gapps package for 5.1 and it refuses to flash because gapps already exist on my phone. But the gapps on my phone don't have trusted face. I will modify the gapps with trusted face so it installs even with gapps already on my phone.
I want to know if flashing a zip file with a file that already exists will overwire the existing file with the one in the zip? This is so I know that already existing gapps will be replaced with the new ones.
janekmuric said:
I have a gapps package for 5.1 and it refuses to flash because gapps already exist on my phone. But the gapps on my phone don't have trusted face. I will modify the gapps with trusted face so it installs even with gapps already on my phone.
I want to know if flashing a zip file with a file that already exists will overwire the existing file with the one in the zip? This is so I know that already existing gapps will be replaced with the new ones.
Click to expand...
Click to collapse
Yes, but most GApps zips are configured to interrupt it's installation if another version of GApps was detected (like TK-GApps detects Delta GApps was installed when doing an installation). So I highly recommend to wipe /system partition and flash another GApps zip if you want to switch between GApps zips.