Related
So for some reason, I catch an error everytime I try to flash a rom to my phone. Then I am forced to restore my backup.
I have it rooted with CWM v5.5.0.4.
i747.
Not sure what other information you guys would need to assist. Would I need to re-root it? Different version of CWM?
Are you wiping data before you flash any new roms? That could be it..
Yep, always wipe data/factory.
.... i'm pretty sure that telling us what the error message says would help, too....
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
jethro650 said:
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
Click to expand...
Click to collapse
Agreed, almost undoubtedly...in every recovery flashable .zip there is an update-binary file which is the actual executable that is commanded by the update-script on what operations to perform. The newer versions of this binary are incompatible with older versions of the recoveries. This effect is not necessarily one way either, an older recovery trying to flash a new .zip or vice versa can produce this error but as a general rule using the newest recoveries should minimize this problem. The only time the reverse is a problem is when there is an update to the recovery api and there hasn't been an updated update-script built into a .zip. The easiest way to check is download the appropriate rom manager for your recovery, Clockwork Rom Manger for CWM or Goomanager for TWRP.
Been a while since i updated my device so i wanted to try out the new 4.4. I see that i needed CWM 6.0.4.3 and i only have 6.0.3.0. I downloaded Rom manager and installed the update that way and Rom manager says its is running the 6.0.4.3 but when i go to the recovery it says the old version is still running and gives me the expected error when i try to flash the 4.4 ROM. I also tried to download the the update file and flash that in recovery and it didn't work either.
Any help would be greatly appreciated. It probably something simple and i will feel like an idiot when someone chimes in........
guttus said:
Been a while since i updated my device so i wanted to try out the new 4.4. I see that i needed CWM 6.0.4.3 and i only have 6.0.3.0. I downloaded Rom manager and installed the update that way and Rom manager says its is running the 6.0.4.3 but when i go to the recovery it says the old version is still running and gives me the expected error when i try to flash the 4.4 ROM. I also tried to download the the update file and flash that in recovery and it didn't work either.
Any help would be greatly appreciated. It probably something simple and i will feel like an idiot when someone chimes in........
Click to expand...
Click to collapse
I updated mine yesterday from the rom mananger and had no problems.
1 thing you should know before you go and try the 4.4 kitkat is that sd card isnt showing. I love the rom but cant get to anything on my sd card.
Good luck.
@guttus
Just a Rule of Thumb. It is advisable to flash Recoveries with ODIN. I am very well aware you can use Rom Manager or Goo Manager, but this is just a thumb rule for flashing the Recovery Partition.
Also note, flashing wrong Recovery can cause hard brick.
recoveries in my sig.
odin and recovery flashable versions
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Hi all. I'm on the i9305 and want to flash latest recovery for kitkat. I'm on philz recovery and wondered if there was one of his I could use. I searched xda but I couldn't find anything. Also I couldn't find an Odin (tar) file for normal cwm. Omni and cm only have the zip and IMG files.
Perseus71 said:
@guttus
Just a Rule of Thumb. It is advisable to flash Recoveries with ODIN. I am very well aware you can use Rom Manager or Goo Manager, but this is just a thumb rule for flashing the Recovery Partition.
Also note, flashing wrong Recovery can cause hard brick.
Click to expand...
Click to collapse
I did do this update via oden. Also flashed Phil's recovery from there. This is where i tried to flash the 4.4 gapps to fix the issue with no luck.
Please post a log of the error when you tried to flash CM Kitkat. If you can't pull the log file, take a photo.
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
shaunjohn said:
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
Click to expand...
Click to collapse
What are you trying to flash?
And which recovery VERSION are you using?
Model aand name of rom
Which model do you have?? and what is the rom's name?
210r
ive tried
philz recpvery
cwm
twrp 2/7 and 2/8
ive tried
cm11
rocket
swat(name may be wrong)
kids
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
A friendly reminder - please keep all question threads in the Q&A board. Android dev is only for posting releases, not questions.
Thanks!
Same Result
ruzell said:
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
Click to expand...
Click to collapse
same result, error opening zip file
Did you ever figure this out? I"m having the same issue.
Can't flash a ROM on Tab 3 7.0 t210r
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
starmaha said:
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Click to expand...
Click to collapse
bierma32 said:
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
Click to expand...
Click to collapse
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
starmaha said:
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
Click to expand...
Click to collapse
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
bierma32 said:
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
Click to expand...
Click to collapse
To clarify, when I initially rooted, I used Odin to flash recovery and root.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
At first we are turn us i The circle,but now we can come to your prob.
Flash a Rom and make a picture and post that here. So we can See The error message and your Recovery.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
Sounds like the rom download is bad. Check the md5 of the rom before trying to install.
Kind of success. I downloaded the same version of PhilZ, for Odin, on my laptop.
I put the tablet in download mode and flashed the recovery with Odin.
I downloaded the ROM again (http://forum.xda-developers.com/gal...m-stockrom-kitkat-version-16-08-2014-t2849742). This is one I had tried before. This time to my laptop and copied it to the tablet. The other times, I had downloaded the ROM directly onto the tablet.
While it was in the process of flashing, there were some video anomolies.
I rebooted the tablet into recovery and flashed the ROM. It hung on SAMSUNG for a very long time after the flash and reboot. I powered it off and rebooted. It booted completely this time, but not without some issues. The first thing was when the message pops up that Android is optimizing apps. That bar was all screwy looking, snowy. (see attached image)
Once I got to the lock screen and entered the pin, the screen "fractured", pieces shifted around, and the tablet locked up. I wish I had taken a picture of it. Never seen anything like it.
I had not done a data wipe yet. I did a data wipe, rebooted, entered the pin, tablet locked up again.
I then was going to restore the backup I made before the flashing. It wouldn't restore because of an MD5 mismatch. I had restored this backup previously with no problem.
I restored an older backup and then spent a couple of hours getting everything back to the level of the now broken backup.
Flash nolekat and all went fine.
I've had problems as well. I normally flash via a recovery. At times I'll have an md5 mismatch or it just doesn't work; I've even backed up a working ROM only to find out I can't restore the same backup. Seems like a hit or miss with me
I tried flashing NoleKat and it failed on me too.
[/COLOR]
bierma32 said:
At one of your post you write after flashing you must put in the Pin?
So you have make not a clean install or factory reset, you done a wipe cache and wipe dalvik.
You must do a clean install if you come from different Roms or Version.
Click to expand...
Click to collapse
Please post a picture from your Recovery with the error message.
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
barrack1 said:
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
Click to expand...
Click to collapse
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
presetz said:
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
Click to expand...
Click to collapse
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
barrack1 said:
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
Click to expand...
Click to collapse
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
presetz said:
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
Click to expand...
Click to collapse
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
barrack1 said:
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
Click to expand...
Click to collapse
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
presetz said:
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
Click to expand...
Click to collapse
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
barrack1 said:
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
Click to expand...
Click to collapse
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
presetz said:
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
Click to expand...
Click to collapse
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
barrack1 said:
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
Click to expand...
Click to collapse
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
presetz said:
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
Click to expand...
Click to collapse
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
barrack1 said:
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
Click to expand...
Click to collapse
sorry my mistaken, thought that my problem was the same with yours with no changed kernel after flashin custom kernel while back at cm12
and no, i didnt need to flashed boot.img first before custom kernel ever since cm12.1 clean install
Managed to instal AT&T v20 stock kitkat and sb told me to:
use towelroot to root the device then install gpro rec.apk and flash rec but do not reboot to rec then install busybox and freegee-i DID THAT-was easy I quess
NOW I DON'T GET THIS:and perform cwm action after this reboot to rec and flash phillz rec and reboot again to rec and full wipe then flash any rom u want.
Help?
kamolinkaaa said:
Managed to instal AT&T v20 stock kitkat and sb told me to:
use towelroot to root the device then install gpro rec.apk and flash rec but do not reboot to rec then install busybox and freegee-i DID THAT-was easy I quess
NOW I DON'T GET THIS:and perform cwm action after this reboot to rec and flash phillz rec and reboot again to rec and full wipe then flash any rom u want.
Help?
Click to expand...
Click to collapse
Okay, first, you may want to try flash the v10g version of the stock ROM because it's the best starting point for flashing the custom ROM on lg ogp device. Follow the instructions in the link below and you should be good. I don't know why someone would tell you to use the towel root with the stock v20 rom because a lot of time it doesn't root properly. The instructions you were originally gave were to root with the towel root and then install the busy box so you can use the freegee. With the freegee you can install either cwm or twrp custom recovery. Once you have the custom recovery, reboot into the recovery and then flash philz custom recovery because it's better than the freegee's. Philz recovery is optional if you don't feel like you need it, it just has more bell and whistle, that is all. You can flash the custom ROM with either custom recovery, philz or freegee. However, I'm more concern with you trying to root with the v20 stock ROM, because you will likely run into many issues. So be sure to read the guide I give you first.
[http://forum.xda-developers.com/showthread.php?t=285432
x
Hey! thanks for the replay! I just got one helper because the rom guy didn;t want to help me so the others.Only 1 guy wanted to give me hints and I managed to install this stock rom.
So you're saying that I have wrong rom installed?
Do I have to really instal other rom or can I do it on mine but in other way to root it and process it so as to install http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779 or not?
I'm all confused,just wanted to install http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779
but whole day passed and nothing was done U.Ux
Read the guide I give you.
Managed to root my phone by iRoot.
Now I tried install busybox but after I hit install: "it looks like the instalation of busy box was not successful try installing to different location that may resolve the issue"....
any tips?
If you can't install the busy box, that usually has something to do with the root. That's the reason I said not to use the v20 stock ROM as the starting point. The only reason you need the busy box is the freegee, you can install the recovery without using freegee, but you have to search around XDA first because freegee opens up the boot loader, which is also the reason you can't just flash the recovery with the lg flash tool. You may have to flash v10g version of the stock ROM.
Ok I'm in philz menu.Someone said that all I need is to install(ANY) rom and kernel-how I do it? I want http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779
Have you used a custom recovery before? Down load both rom and kernel installing files to a directory that you prefer, usually some where on your external sd disk. Once you get the files, go to philz recovery and press install zip, find the directory where the installing files are located, press on them, and it should install the rom. If you have never done this before, remember to factory or clean install the rom. On philz recovery, there is a function call installing a new rom under factory reset section, use that every time you're installing a new rom.
hawkwind212 said:
Have you used a custom recovery before? Down load both rom and kernel installing files to a directory that you prefer, usually some where on your external sd disk. Once you get the files, go to philz recovery and press install zip, find the directory where the installing files are located, press on them, and it should install the rom. If you have never done this before, remember to factory or clean install the rom. On philz recovery, there is a function call installing a new rom under factory reset section, use that every time you're installing a new rom.
Click to expand...
Click to collapse
PLEASE HELP!
Installed CM12.1 on my e980. And now the wifi isn't working at all. Have searched and tried some fixes but to no end. Any suggestions?
D Sami said:
PLEASE HELP!
Installed CM12.1 on my e980. And now the wifi isn't working at all. Have searched and tried some fixes but to no end. Any suggestions?
Click to expand...
Click to collapse
Have you tried clearing Cache from Recovery?
khan.orak said:
Have you tried clearing Cache from Recovery?
Click to expand...
Click to collapse
Yup, I advanced wiped my phone (TWRP) and cleared cache, dalvik and system
What's Wi-Fi doing? I notice there are issue with the modem on cm12.1 based custom rom. During the boot up, it would spent long time searching for the signal, but I never have problem with the Wi-Fi though, then again, I'm not using cm12.1 but vanir instead. However, somewhere I remember reading that someone else is having a issue with the Wi-Fi on cm12.1, and he fix it temporarily by setting up the Wi-Fi each time.