Develop Bugs

flashing error

i didnt see anyone having this problem but got my gn and unlocked it yest, i came fr evo3d and we used to wiping everything n cache n dalvik so i tried to flash my first rom and im getting error " error in /sdcard/toro_aokp_b8.zip(status7) installation aborted assert failed:getprop(ro.product.device==toroII
i thought it was that rom but i tried flashing another rom and getting same message , if someone can help i appreciate it, i came fr the evo3d left sprint after 11yrs and woow what a difference in network, awesome network but im spoiled with rooting my ogevo n evo3d lol i love this phone hope i can fix this issue

Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?

RTContent said:
Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?
Click to expand...
Click to collapse
k first rom i tried AOSP 4.0.3ANDROID OPEN KANG PROJECT-TORO BUILD8 so i wiped data factory reset and cache n dalvik and flashed the rom, it looks like it starts to flash but aborts with the message above, then i restored my nan backup rebooted and went back to cwm to reflash the second time around i only wipe data factory reset cuz thats what the op says to do on his thread so i only wipe data factory n flash the rom still same error, so i went to try another rom GUMMYNEX 0.2.3 and i did the same process with both im following the steps their stating in the op in have cwm

From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?

RTContent said:
From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?
Click to expand...
Click to collapse
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve

Flip35 said:
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve
Click to expand...
Click to collapse
sure you are using the lastest CWM???
sure you are rooted??
did you try downloading the files from another puter??

i think i might know what the problem is my cwm says 5.5.0.2 and im looking here at somebody posted in the development section for a cdma cwm and it says 5.5.0.4 could that be the problem? if so how do i redo my recovery, follow the same steps i did my first one, i downloaded and extracted the files to my c drive and opened cmd and typed the commands, can i do that again while having already cwm to flash the new cwm on top of the old one? if thats the problem

Download rom manager. Then you can flash it while your booted in android.

RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
how ive never flashed cwm using rom manager, u meand download the file of cwm5.5.0.4 putting in the root like i do any rom and go into rom manager and install?

No just download the app Rom Manager. It will download the latest version and flash it with a single click within this app!

RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
wooooord, aight RTcontent good looking out, i guess when u said it looks like it sound it was reading my phone wrong was right, i had a gms cwm, thanx man used rom manager and since i put the new cwm in my root of sdcard when i press install cwm it automatically update it without even booting into recovery but just finished intalling a rom and IT WORKED!!!! UR DA MAN im excited thanx

Need help with CM10 install

Ok so it's been a while since I've done any new ROMs or anything, mainly did things on my GS2 but now going with the GS3 and have been for a little bit now. It's all rooted and everything fine, but I decided to finally install the CM10 ROM and am having a difficult time. I finally got it to install and boot up (had a slight issue with the boot loop which I got passed) but now my home screen says Sprint on the bottom. Maybe I downloaded the wrong CM10 zip? Or maybe they're all like this but I didn't think it was. On to the bigger problem, no mobile connection. I'm able to restore to my backed up status so that's what I'm going with for now but I'd really like to get this working. Any suggestions? Have I supplied enough info. Any help would be greatly appreciated, thanks to anyone that can give me some direction here.

You flashed the wrong zip.
for AT&T you need d2att http://get.cm/?device=d2att
If you need a different carrier then ATT try checking the CM10 thread http://forum.xda-developers.com/showthread.php?t=1778270

Randomacts said:
You flashed the wrong zip.
for AT&T you need d2att http://get.cm/?device=d2att
If you need a different carrier then ATT try checking the CM10 thread http://forum.xda-developers.com/showthread.php?t=1778270
Click to expand...
Click to collapse
Thank you for that! Will that solve the network problem too? Seems like something like that would solve my problem all together. Anything else I should know?

Imnice777 said:
Thank you for that! Will that solve the network problem too? Seems like something like that would solve my problem all together. Anything else I should know?
Click to expand...
Click to collapse
yeah it should if not go back to complete stock and try again.

If none of that works check in settings, about phone and make sure your imei number is still intact (not showing zeros).

Ok so my IMEI is still intact but that zip for AT&T didn't work, I got an error. I cleared cache and user data and chose it from my internal memory, not sure what the issue is except maybe my CWM is outdated? Wasn't sure if it'd be a problem but maybe that's it. Any other suggestions?
Sent from my SAMSUNG-SGH-I747 using xda premium

Might be an APN issue. Try adding the APN for your carrier and see if your data works. What error are you getting when you try to flash the at&t version?

jethro650 said:
Might be an APN issue. Try adding the APN for your carrier and see if your data works. What error are you getting when you try to flash the at&t version?
Click to expand...
Click to collapse
The error reads "asset failed: getprop("ro.product.device") == "d2att" l l getprop(("ro.build.product") == "d2att" E:error in /emmc/cm-10-20121024-NIGHTLY-d2att (1).zip (Status 7) Installation aborted."

Update your recovery.
Sent from my iPad 4

Update CWM recovery to latest version.

And you can get a newer version here. http://forum.xda-developers.com/showthread.php?p=28611956
Official ClockworkMod Recovery Images for AT&T

Ok so I figured it out and fixed it! All I had to do was update my CWM with ROM Manager like I thought I might have to do. I saw another thread with a similar issue, too so I guess this is somewhat common. Gotta update everything when it comes to this stuff. Thanks for all the responses though, I appreciate it.

Somehow I didn't see the replies telling me to update CWM before I.posted that I figured it out. Either way, I'm currently running it and all is awesome so far. If anyone has suggestions on specific things to do now?
Sent from my SAMSUNG-SGH-I747 using xda premium

please help
Hi there, i've been having issues trying to install cm10 since last week and it's been frustrating. After doing hours of search I found a thread that says I should reinstall cwm recovery. I've tried doing this with rom manager from google play but it didn't work. It says, make sure you have stable internet connection and that your sd card is installed and working. Now, do have to Odin again to flash the newest clockworkmod recovery. If not how do I do then cuz I keep getting aborted and every time have to restart system and set it up all over. by the way my phone is a galaxy s3 i747 android 4.0.4 rooted cwm 5.5.0.4. thanks

androidehca said:
Hi there, i've been having issues trying to install cm10 since last week and it's been frustrating. After doing hours of search I found a thread that says I should reinstall cwm recovery. I've tried doing this with rom manager from google play but it didn't work. It says, make sure you have stable internet connection and that your sd card is installed and working. Now, do have to Odin again to flash the newest clockworkmod recovery. If not how do I do then cuz I keep getting aborted and every time have to restart system and set it up all over. by the way my phone is a galaxy s3 i747 android 4.0.4 rooted cwm 5.5.0.4. thanks
Click to expand...
Click to collapse
Download this cwm 6.0.1.4 http://db.tt/te3vInsu , reboot into recovery and flash it, reboot recovery and flash cm10.

tonymtl said:
Download this cwm 6.0.1.4 http://db.tt/te3vInsu , reboot into recovery and flash it, reboot recovery and flash cm10.
Click to expand...
Click to collapse
that's not the problem, I already have the file. it's kind of my question, I keep getting aborted from the process of flashing. no errors, only aborted

androidehca said:
that's not the problem, I already have the file. it's kind of my question, I keep getting aborted from the process of flashing. no errors, only aborted
Click to expand...
Click to collapse
If that's the case I'd probably completely go back to stock and root with the updated CWM. Kind of a pain but might be your best bet. Updating for me was the solution. Try that and let me know how it goes.
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Cannot flash anything

T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.

moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium

soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.

moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium

Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?

Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.

OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place

moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.

meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...

moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.

i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem

meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?

Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?

moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.

I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418

Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.

moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.

moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium

went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?

moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium

[Q] Wind SGH-T999V CM Help

Okay, I'm new to Android and I heard this is the go-to spot for help. Anyway, this is what happened to my Wind SGH-T999V. Mind you i'm VERY new to this rooting thing
I rooted my S3 by using TWRP 2.6.3.0 and i used odin3 v1.85 and it worked. I downloaded a root checker and it said i'm rooted. Then i put CM 10.1.2 on my sd card and wanted to install it via TWRP recovery but it gave me an error that said "No MD5 filed found" or something along those line.
I then tried to use different versions of twrp ( twrp 2.6.1.0) and a different CM (10.1.1) but i still got the same "no Md5 found" error. So, a friend then told me to ditch twrp all-together and download CWM instead. So, I download recovery clockwork touch 6.0.3.7 and put it on my phone.
THEN, i tried to go back to the recovery boot place, but after that small blue font saying "recovery boot", my phone goes black. I dont see the old twrp recovery or the clockwork one.
I just really want to have Cyanogenmod on my phone, i've been having a hard time. Help please?

Just disable the md5 check, most or the ROM files are not going to include a hash file, but will flash fine. TWRP or CWM will error out if the flash fails.
Also, it sounds like your recovery install failed, just reinstall using ODIN and a file from @DocHoliday77 (I recommend TWRP over CWM, but it is just preference)

It's already unchecked.

Install TWRP and try again, should work without issue. Also, redownload the ROM file, preferably the latest version, 10.1.3RC2 (I think)
Sent from my T-Mobile T999L using TapaTalk 4 and delivered by Planet Express.

Can you link me the most STABLE CM that works with my Wind SGh-T999V?

qasde455 said:
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
Click to expand...
Click to collapse
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.

http://get.cm/?device=d2tmo&type=stable
"Stable" is relative, the RCs are just as good.

Aerowinder said:
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
Click to expand...
Click to collapse
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install

qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
You need to edit the install script because your device isn't supported. Or you can download Doc's version.

Actually I'm pretty sure cm includes the T999V, but I'm betting the firmware needs to be updated.
Look in Aerowinders Sig for the links to the firmware. In that OP you should find a link to the thread with the T999V firmware.
Or, you can go to my T999L thread and get the Rom there. But w/o updated firmware it may be buggy.
Sent from my SCH-I535 using Tapatalk 4

It's already unchecked.

qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
CM10.1.3 is now Stable and will be the last 4.2.2 build. It should has the all of the Asserts, including the MB7 one. Also, update your TWRP, the current is 2.6.3.0.

I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..

malibu.barbie said:
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
Click to expand...
Click to collapse
You should read the sticky threads, and use xdas search for terms or definitions anytime you run into stuff you aren't familiar with.
Sent from my SGH-T999V using Tapatalk 4

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.

You need to give more info on the error
Sent from my SGH-M919 using Tapatalk

serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.

Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app

spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.

Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?

Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.

Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.

Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?

So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.

Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.

To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.

Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.

Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3

I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?

Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something

Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement

GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)

My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.

You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.