Develop Bugs

Unable to start Wi-Fi / stop Wi-Fi

Ever since updating to JoeyKrim 1.0.8 I have had an issue where my Wi-Fi status shows up as "Unable to Start Wi-Fi" or "Unable to Stop Wi-Fi". I also applied to patch to disable Wireless-N, but to no effect.
Have already wiped data & dalvik cache. Any other ideas? If it is related, I am finding that Titanium Backup is backing up all items to zero file size.
Any suggestions?
[Running full NAND unlock, if it is worth anything...]

Did you by chance deny Wireless Tether in SuperUser on accident? Do you have SuperUser installed?
I'm not familiar with that ROM but I do assume SU comes installed.

Harfainx said:
Did you by chance deny Wireless Tether in SuperUser on accident? Do you have SuperUser installed?
I'm not familiar with that ROM but I do assume SU comes installed.
Click to expand...
Click to collapse
Negative - just doublechecked, and Wireless Tether is not even installed anymore.
I found a few other threads on other forums that this happened a lot on the G1, but have not been able to turn up any other EVO users with this issue. This really sucks, especially with the shortage of devices, even trying to get this replaced will suck.
Any suggestions of things to try, folks?

I think it's been implied but not stated, but you've tried other ROMs right?
Try going back to stock and if it still does it take it to a Sprint store, see if they can get it working or replace it?

Sirchuk said:
I think it's been implied but not stated, but you've tried other ROMs right?
Try going back to stock and if it still does it take it to a Sprint store, see if they can get it working or replace it?
Click to expand...
Click to collapse
Correct - have tried various ROMs. Going to try unrooting it back to stock .6 OTA version and see if that flies. As much as I hate to say it, I'd rather have functional Wi-Fi than root access.

Just wanted to tie this one up with a bow - never posted my resolution to this. Installing Fresh EVO 0.3 at the time fixed it, so I'm guessing it was a bad .rc file permission in some version of jk's ROM that bit me.

[Q] ADB Not working on Sense Roms

I've run into a very strange issue where ADB isn't functioning properly in two of the sense Roms I've tried recently, both Fresh 3.5.0.1 and the newest Evio Rom by Caulkin, 1.8 I believe.
I can't get the phone to go into USB debugging mode, although it works just fine in CM7 and another gingerbread rom I tried yesterday.
Here's some of the things I've tried, give me something I haven't tried, I dare ya!
Wiping properly in recovery (with Amon Ra 2.3, 1.8.0, and clockwork recoveries 3.x and 2.5.x)
Using Caulkin's Format All in recovery
my golden nandroid backup of Fresh didn't work, neither did a fresh fresh install
ADB works in fastboot or recovery, but not in the ROM
ADB works just fine in CM7 and non-sense ROMS (tried 2)
I tried going back to the roots by flashing my post nand-unlocking PC36img.zip and it worked fine, new fresh 3.5 install, borked.
Different USB ports
Different USB cables
Different Android SDKs
Different Android USB Drivers
My wife's HTC Hero works fine on those same ports on the same machines
two machines, one XP 32 bit and one win7 64 bit, wifes works on both, my evo works on neither.
doesn't work on stock fresh kernel, doesn't work on netarchy custom kernel.
Used to work, because I use my Evo for a test device on my apps, but I can't remember if it has ever worked on Fresh 3.5
Tried formatting my SD just to be sure there wasn't a remnant on it.
And oh yes, I made sure USB Debugging was checked.
As you can see I tried a lot. I'm very familiar with ADB and its nuances. This is genuinely stumping me, as I feel I've eliminated nearly all variables and tried nearly all configurations.
Any ideas, or anyone have something similar happen?

Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.

trimeijer said:
Not sure if this is it, but could it be something to do with boot.img.
http://modmymobile.com/forums/403-m...x-remount-failed-operation-not-permitted.html
I have the same problem. Mine is a stock rom thats been rooted by unrevoked but I haven't flashed anything on it yet. Apparently there is a line in default.prop for ADB and if it is deactived some features do not work well. You can change it but the only way to get it permanent is to edit the default.prop in boot.img.
Not sure if this is remotely the case because these are custom roms ... but its worth getting it out there because I never knew this before.
Click to expand...
Click to collapse
I'll flash back to Fresh tonight and check the build.prop to see if you're right.
I did notice that Flipz said he took the debug message out so it shouldn't pop up, but maybe that meant he disabled those lines in the build.prop. I would think he would know better than to do that, though, as that would disable ADB altogether, something he surely would see. It's totally possible though.
is there any way that mine could have gotten modified or something I wonder? I'd think no, because that would have to come from his install, especially on my new installs I did. Weird.

Unfortunately, my default.prop is the same as in the correct version in the link you posted. I'm literally at a loss of what else to try. Hoping some more pop in to share as I doubt we're the only two with this or have experienced this before.

I think I've figured out what's going on, now I just need to figure out how to fix it.
Like this post below, I think that the ADBD process isn't running because I couldn't find it in my process list. They used one from another build image and replaced their current one.
http://code.google.com/p/android/issues/detail?id=9437
Anyone done this before or could provide some guidance in addition to that thread?
I'd really appreciate the help.

My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc

trimeijer said:
My problem is that I can't write to /system but I think that might be something wrong with my root, even though I have s-OFF and I did flash a rooted rom ... not sure whats going on. I can only write to it in recovery.
Other ADB things work for my, like writing else where, shell, logcat ..etc
Click to expand...
Click to collapse
Have you tried the "adb remount" command prior to trying to write to system? That will get you sometimes.

I pulled the boot.img from CM6 and replaced the /sbin/abdb process with the one from CM6 inside the Fresh boot.img. When I repacked, everything looked good, I installed Fresh Rom, and then it won't boot. Not at all. Wish I knew more about how to do that. I think I'm going to try again, but was following the perl scripts he posts on this page:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I had to suppress a message in one of them because there was a fourth file, and it says it was not created to be able to handle those. Read on another forum to comment it out. Anyway, it didn't work but I'm going to keep trying.
Installed CM7 again, and there it is as a process, /sbin/adbd. That's got to be the key.

Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.

trimeijer said:
Yeah adb remount doesn't do anything for me. Still errors.
I looked for my processes using ps ux and got nothing. Then in my default.prop is a line
"persist.service.adb.enable=0"
which they said was a problem and it sounds like my/our problem of there being no service. So i'm going to try another stock rom. I am using the OTA from teshxx but when I tried to modify it in the kitchen it said it had no boot.img (which could be why the setting is disabled and I don't have 'root adb'.)
@kmartburrito sounds like a signing issue right? I mean I messed with stuff like that before but I could never get it to boot properly after editing anything. Never really pursued it too much though. Read through the guide and it doesn't really have anything to do with signing ... but i know the space allocated for each section of the RAM is very specific so maybe there was a mismatch.
Click to expand...
Click to collapse
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.

kmartburrito said:
Yep, I'm betting that's your problem. My line with that has a value of 1, so I'm not going to be any help from that standpoint. However, when you remount your filesystem as writable, you can modify that default.prop file and it SHOULD stick, in case you hit that same issue on your next rom.
I'm still trying to figure out what the hell is going on with my situation. I talked to another guy in a different thread and he explained that he is able to ADB in froyo sense roms, so even though I'm getting the same issue in multiple roms and not in non-sense roms, there's another person somewhere without the problem, so it logically can't be the ROM, unless it's a per-rom basis, and I've just hit the wrong rom three times in a row. Who the eff knows! This is really frustrating, but I guarantee you I will figure this out soon. I need to continue working on my app, so this needs to get fixed. Soon.
Click to expand...
Click to collapse
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.

From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.

JusticeAA said:
Have you tried the SprintLovers Rom? It is the closest to Stock you can get and it has regular updates. If that works maybe you can examine the difference with Fresh.
Maybe a logcat would help.
Click to expand...
Click to collapse
Hey, trying this now, will let you know what I find. Thanks for the idea!
gpz1100 said:
From a # prompt try the following
stop adbd
setprop persist.service.adb.enable=1
start adbd
Then try connecting via usb/adb shell.
Click to expand...
Click to collapse
Unfortunately, this is already set as such in my properties. I tried it anyway though on Mikz rom, and ADBD still isn't starting or working afterwards.
You know what it seems like? It seems that this is an issue with the HTC Kernel after one of the first versions that they released after FroYo. I say that because it works on Fresh's 3.1.0.2 rom which was one of the first FroYo builds, and it doesn't really work after that, which was a newer base build and newer Kernel. Doesn't work on really any other sense-based ROM for me either.
It DOES, however, work on any AOSP rom (which also uses a diff kernel) Which is one thought as to why it might not be working for me. The strange thing is though that this is somewhat isolated to my Evo. Maybe I have a lot of bad blocks or something, but something's fishy in that it works with early FroYo roms and any AOSP roms consistently, but not new Sense roms. So, either the majority of Sense devs are using Fresh's stuff as a base, or the problem is a bigger one related to the base build or Kernel itself.
I tried using the old HTC Kernel on a new build of Fresh, and found that the ADBD process did in fact appear when using a ps command, but it still did not function properly.
And furthermore, there is absolutely jack **** on documentation out there on what makes ADB work, or what could make it not work.

Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .

gpz1100 said:
Since you mentioned kernels, have you tried a different one than what's in fresh?
I'm using the net's latest cfs kernel, and was using the previous 4.3.2 before. I'm not a big fan of the #15 kernel as it breaks the processing of scripts in init.d .
Click to expand...
Click to collapse
Yep, several versions of Netarchy's kernel, several HTC, no dice. I suppose that should rule out the Kernel and point to the base build. What is really weird though is that it's happening mostly just to me, although there are a couple others for the Evo I'm sure (many might not even know it) and there are definitely others affected like I am on different devices.
Hardware 002 and rooted using part 1 and part 2 of toast's method.

[Q] Is the system update ok to install over Root?

Ok. So I see there is a system update. I wanted to make sure if there's anyway I can check to see that it's ok that I install this update. Will it interfere with anything? Mainly pertaining to my root and unbrickness of my phone.
Will I lose root? Will I become bricked? (Though I doubt the later) I just wanted to know are we in the clear on installing this.
Sorry, but this is the first time this has happened to me, being rooted with some type of OTA.

you know... i flashed the updated tar file using mobile odin and 1) kept the root and super user 2) gained the stock boot screen again but lost clockwork 3) didn't lose any of my apps or data.
so it's a mixed bag and from my experience i wouldn't recommend it because it replaces the kernel and you'd lose clockwork. i think there may be a version floating around that you can flash though.

btate0121 said:
you know... i flashed the updated tar file using mobile odin and 1) kept the root and super user 2) gained the stock boot screen again but lost clockwork 3) didn't lose any of my apps or data.
so it's a mixed bag and from my experience i wouldn't recommend it because it replaces the kernel and you'd lose clockwork. i think there may be a version floating around that you can flash though.
Click to expand...
Click to collapse
So... shouldn't I update through the OTA, loose my kernel, use ODIN to flash back my CWM and kernel? That sounds like a viable solution.

Sounds about right to me but I would probably wait for someone more learn-ed to chime in. Your mileage may vary using the method I used.. which admittedly is probably very noobish. I didn't have any problem flashing a CWM kernel through odin though. Here's the funny thing.. i kept reading that the stock kernel would "unroot" your phone.. but for a few days I actually kept the stock kernel and was still fully rooted (super user kept asking permission for a few things like widget locker and titanium... and they worked perfectly *shrug*).
It may be that I just don't understand it fully yet but it worked out fine for me.. but again.. your mileage may vary.

btate0121 said:
Sounds about right to me but I would probably wait for someone more learn-ed to chime in. Your mileage may vary using the method I used.. which admittedly is probably very noobish. I didn't have any problem flashing a CWM kernel through odin though. Here's the funny thing.. i kept reading that the stock kernel would "unroot" your phone.. but for a few days I actually kept the stock kernel and was still fully rooted (super user kept asking permission for a few things like widget locker and titanium... and they worked perfectly *shrug*).
It may be that I just don't understand it fully yet but it worked out fine for me.. but again.. your mileage may vary.
Click to expand...
Click to collapse
Alright, that sounds like a safer route. Ima go check around the ROMS. Maybe they've added the update as part of their ROM.
Expecting this update to fix many of my problems.

[Q] Finally Flashed!!! (This Is Gonna Be Long...)

When last Feb. I finally switched from my iToy to my N7100, I thought that 'flashing' was something that some perv did while wearing a raincoat.
(Hey, I'm pushing 70)
I Finally got my device rooted. I know that it's rooted because while using CF Auto, It wanted me to flash a Triangle Away update, and my binary count went down from 22 to one... so I know at least that worked.
Overjoyed that in Odin, when flashing I first got the notice "Reset!" and then after a few minutes and a restart, I got the "Done" notice (or whatever it said) as I never unplugged from the USB as it says you're supposed to. I just forgot.
Prior to "upgrading" to 4.3 Indian version, I had the stock Rom 4.1.2 running the Perseus Kernel... loved it, but upgrading to 4.3 has turned out to be the worst decision so far.
I still have a lot of Root apps on the phone but they don't work, but as I said, Triangle Away did work.
Should I uninstall the existing ones like Tit. Backup Pro and a few others and re-download them?
Does CF Auto Root automatically install SuperSU? Or should I uninstall that and re-download that too?
One last question....
Assuming that I do have Root, and I'm able to get Titanium Backup Pro working and am able to freeze and/or uninstall the Knox files... What about the ODEX files with Knox.
On this site, I have heard both pieces of advice... Delete and not delete the ODEX'd files.
What is it?
Nobody ever comes up with a definitive answer on this site... it's just a bunch of opinions, usually with the disclaimer, "Worked for me", or something like that... combined with the fact that I really hate working with the Windows partition on my Mac to do the flashing.
Oh, one more thing.
I'd like to go back to the Perseus kernel which somebody mentioned here on XDA.
Are there any kernels for the N7100 that are only useable with 4.1.2 that I should NOT use with 4.3, or does it matter. In other words, would it work with 4.3 as it did with 4.1.2?
Too bad that I don't have somebody like ChainFire living next door. Haha!
I have to thank the XDA site for most of my knowledge since last Feb. when I thought that rooting had something to do with digging up a tree in my front yard.
One more thing (again), I just got an update for Rom Manager Premium and it looks like I can download a CM stable release, which I'm gonna do as soon as I get some of these things ^^^Above answered and ironed out.
I'd like to stick with AOSP as opposed to AOKP but I'll do anything to get away from this current ROM.
Thanks in Advance to anyone who can answer some of these Noob questions.

1-ok i think that you have a custom recovery now, i had these issues a lot on 4.3, if you have custom recovery TWR or CWM you can install any rooted 4.3 rom, but before you do so make sure you backed up your efs folder (VIP you will lose signal if this folder corrubted), after a clean install of any rooted rom, just install ur apps again, if you don't have custom recovery you will need to flash any recovery from Odin, if you can't install recovery from odin so this will be bec. of knox, report back bec. this is another story.
2- some kernels works fine with 4.1.2 or 4.3, and some old ones are only 4.1.2, so make sure that you will flash the right kernel (e.g. devil, AgniPure Stock, ....)
3- don't try to update to CM now, frist make sure that you have a fully working rooted rom with custom recovery install, i also don't recommend flashing roms using any app (rom manager fore example), i think the best flash is the one you do from recovery with clean flash

Just A Follow-Up...
Hey, thanks, evaworld!!!
UPDATE:
I decided to try Root Explorer again (It never worked before to delete anything before this time) and do a search for anything with Knox in it.
I found everything Knox and checked all the boxes except for the ODEX'd files, hit the trash can and wow... it asked for Root privileges. I gave it, and everything was gone in a flash (Pun intended).
Then I tapped on Ti Backup Pro and got the dreaded 'Android device I.D. changed' message so I came back here to XDA and read literally every post on it (Again, opinions are divided) and decided to ignore.
After that, nothing was working for me in Google Play, so I just deleted the data in Google Play Services, Google Play Store, and now I'm waiting for it to take effect in Google Play... whenever I did that in the past, it usually took a couple of hours for it to register. (?)
Now, all of my Rooted apps that I've tried so far are working, but somewhere along the line they pushed Samsung Link on my phone even though I've had Samsung Apps disabled since day one.
The funny thing is that with a Binary Count of 22, I did absolutely nothing differently than this time (Except for an abortive try with Philz_Touch that I don't particularly like the GUI in P_T)... same USB cable, same port, same Windows partition on my Mac, etc. etc. it took this time and I'm pretty overjoyed!
I'll follow evaworld's advice on the ROM... better not throw too much into the mix until I decide that everything is all ironed out.
And, yes, I did click the "Thanks" button for you.

Very good that you have root, but also note that your setup isn't so stable (besides the fact that 4.3 isn't very stable with root apps e.g. I always have problems with titanium and Super and alot of other apps that requires root) , so just clean install a good 4.3 app (I recommend DN3), and after that you are free to do whatever you want (don't forget efs backup in sage place).
Sent from my GT-N7100 using XDA Premium 4 mobile app

My telephone is now rooted, but will not install CM Mods...

Hello, this is my first, and most likely stupid post...
I rooted my Epic 4G last night (amazingly) but now when I try to follow numerous guides and discussions on how to update my OS (I have the last gingerbread version) which is the MAIN reason I wanted to root my telephone, it stubbornly (or more likely, I STUPIDLY do something wrong) and it refuses to flash or install any of the CM Mods that I see EVERYONE else is running just fine on their Epic 4G!
I've installed ROM toolkit which LOOKS like it should easily install whatever ZIP file I've DL'd onto my SD card. But in every case with different mods, it comes back with the same error when it tries to install, which is 'Cannot mount the SD card', but it is mounted and seen just fine and it is mostly empty.
I followed these steps with the exception of using the PC interface, instead trying ROM toolkit to flash it which is found here;
http://forum.xda-developers.com/showthread.php?t=2540250&page=77
But, I get the same error when it goes to install. I MUST be doing something wrong. I am really VERY much a newbie, but unless I need to go about this differently, I am REALLY stumped after trying and reading for many hours now.
I would sure appreciate a nice, SIMPLE way hopefully to upgrade my OS from Gingerbread to whatever I can use (I see others saying they are running KitKat just fine!)
Thank you so much!
________________Latheofheaven

I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.

ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Oh, hey, I am SO glad that you took the time to answer me, thank you!
See, I TOLD you guys that I am not really conversant with this. I figured that I was doing something wrong. I absolutely PROMISE that I have been reading about this and trying to figure it out for like 2 full days STRAIGHT!
Would you mind, please, terribly just listing the basic few things that I have to do? I REALLY am confused by this. Are you saying that I need to install clockworkmod first? What version will my Epic 4G take? All I have installed now that seems related to this is the ROM toolkit PRO and ROM Manager. When I DID try to use ROM Toolkit to install this Rom, I got a long prompt how I didn't HAVE Clockworkmod, but I thought that it came with one of the others, I guess.
Could you PLEASE list precisely what I need to do? Could you kindly list the links for ANY pre-rooted ROM that you would recommend, or ones that work on my Epic 4G? Once I understand the steps, then I probably will know what to do if I want to try others, but I am kind of stumped as to exactly what to do now. I didn't even KNOW that that was an Epic Touch ROM! I'm surprised that I was able to follow the steps just to root the dang thing!
Dude, if you wouldn't mind taking pity on me and show me what I need to do, that would be super nice. It SOUNDS from what you said that I need a version of clockworkmod and I just need the RIGHT Rom and just how to do it, I guess...
Thank you so much for your time and any help that you can give!

Ah, got Clockworkmod!
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Hey, I DID actually get a version of CWM. I installed ROM Manager and then it prompted me to 'update' CWM. Now, I had installed RM before and HAD tried to update CWM, BUT... it never allowed me to do that. However, THIS time, it DID! And now it continued and asked me if I wanted to flash CWM, and I said 'DO I?!!!' And it did. Now, I have a whole new option screen which I haven't looked at yet.
Soooooo, I'm kind of HOPING that now all that I will need is to be pointed toward a rooted ROM for my Epic 4G and just the steps how to do it.
I was TRYING to do this through ROM Toolbox Pro b4, but no go...
Thank you kindly again for whatever help you can give me!

Trying to get rooted ROM for Epic 4G...
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Okay, I am now DLing this file:
cm-10.2-20131125-UNOFFICIAL-epicmtd.zip
Which from the page LOOKS like it is for my Epic 4G. I will TRY to see if I can transfer it to my telephone's SD card. Then, I will TRY to, what, 'Flash' it...? ... using CWM that I THINK is now on my telephone?
Anyway, I didn't want you to think I'm being a deadweight. I AM trying to figure this out
Thanks!

Tried, but no go...
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
Okay, the good news is that this time when I tried to install this package that I mentioned above, at least I didn't get the SAME error about not being able to mount the SD card, so that is SOME progress, I guess.
However, this time as it opened and tried to 'verify update package' it came back with an 'e-Signature verification failed'
Soooooo, did I indeed choose the WRONG ROM again...?
I will wait to hear from you when you have time.
Thank you kindly again!

Naaaa, I think I'm gonna frigg'n give up...
ernest-sora said:
I don't get what you are doing. Why are you trying to install that rom? That is an epic touch rom! Not an epic 4g rom, that's why you're getting errors. Just install any pre-rooted rom with clockworkmod, I usually use FC09 pre-rooted, and from there you can install cyanogenmod or a slimrom.
Click to expand...
Click to collapse
sigh... well... I think I'm gonna give up. I DLed yet ANOTHER seemingly official rom FOR my device, it appears, from this site on this page:
http://download.cyanogenmod.org/?device=epicmtd&type=stable
The one at the top: cm-10.1.3.1-epicmtd.zip
It says 'STABLE', but it could not verify the signature again.
So, until SOMEONE has mercy on me and tells me what the hell I'm doing wrong, I guess I will give up.
Thanks anyway...

IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.

Mr_You said:
IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.
Click to expand...
Click to collapse
Thanks kindly. I saw that many others were having similar troubles.
I will give it a try. And THANK YOU for the link!
Cheers!

Mr_You said:
IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.
Click to expand...
Click to collapse
My CWM is not Premium, so I don't think it has the option about signature verification. I did see on another thread that a fellow couldn't do it through ROM Manager because he kept getting the signature verification error. So, he was ultimately able to do it through Odin 1.85, which I have. The only thing is that the ROM is a Zip file and Odin will only flash Tar files because I've tried to do that before.
At least now I KNOW that I have a good link for the ROM itself, thank to you!
Now, all I have to do is figure out how to install it. I sure hope that I don't also have to buy ROM Manager Premium, because I just paid for ROM Toolbox Pro, which you would THINK would be powerful enough to do this, but I guess not...
Thanks though...

Mr_You said:
IIRC you have to turn off signature checking in CWM. It's a menu option. I would recommend installing v11 M12.
Click to expand...
Click to collapse
Heh... I guess I haven't QUITE given up yet...
Anyway, I thought that you should know that through ROM Manager my telephone is NOT booting into CWM's boot recovery. When I choose to boot to CWM recovery it ONLY boots to the stock Android recovery showing a little Android figure with an error sign and then in yellow letters below it says 'Manual Mode'
That may also indicate that something else is wrong...

Got it!
FINALLY! ...after reading about MANY different approaches for other people with different issues, it occurred to me to try using Odin to 'Flash' the actual CWM recovery program since it never seemed to update or EVER back up to it no matter how many times I tried. FINALLY... by holding down the 3 buttons immediately after flashing CWM recovery, it FINALLY actually booted up into the CWM recovery mode! THEN... and only then could I properly install the CM11 version and it all went great!
Now, the only thing I'm trying to figure out is how the hell to sync my Google contacts to get them all back!!! :laugh:

latheofheaven said:
FINALLY! ...after reading about MANY different approaches for other people with different issues, it occurred to me to try using Odin to 'Flash' the actual CWM recovery program since it never seemed to update or EVER back up to it no matter how many times I tried. FINALLY... by holding down the 3 buttons immediately after flashing CWM recovery, it FINALLY actually booted up into the CWM recovery mode! THEN... and only then could I properly install the CM11 version and it all went great!
Now, the only thing I'm trying to figure out is how the hell to sync my Google contacts to get them all back!!! :laugh:
Click to expand...
Click to collapse
Ahhhh... I didn't have ANYTHING Google, and then I remembered from what I read that in just about every case where someone installed a ROM like this one, they also mentioned a GAPPS file! DUH!!!!
So, I'm going to try to find the right one.
Also, something really weird... the Play store says that I already have some apps installed like ROM Manager and ROM Toolbox and others, but darned if they DON'T show up in my apps on my telephone. I wonder where the hell they are...???!
Thanks!

latheofheaven said:
Ahhhh... I didn't have ANYTHING Google, and then I remembered from what I read that in just about every case where someone installed a ROM like this one, they also mentioned a GAPPS file! DUH!!!!
So, I'm going to try to find the right one.
Also, something really weird... the Play store says that I already have some apps installed like ROM Manager and ROM Toolbox and others, but darned if they DON'T show up in my apps on my telephone. I wonder where the hell they are...???!
Thanks!
Click to expand...
Click to collapse
I'm glad that you made it. Never give up on flashing. About playstore it shows, under all apps, ALL apps that has been installed using that account. It's been so long since I rooted my epic, like 4 years ago, that I don't remember how I did it. It's a really strong phone.
I personally prefer slimrom jellybean, with kitkat you will have few storage left and you will have to use app2sd.

ernest-sora said:
I'm glad that you made it. Never give up on flashing. About playstore it shows, under all apps, ALL apps that has been installed using that account. It's been so long since I rooted my epic, like 4 years ago, that I don't remember how I did it. It's a really strong phone.
I personally prefer slimrom jellybean, with kitkat you will have few storage left and you will have to use app2sd.
Click to expand...
Click to collapse
Yep, I've definitely already run into the storage thing. There is only like 500 Megs of internal storage. I already tried 'Move to SD card', but I'm not sure that is the same one. I really couldn't move that much to the SD card, at least from that app.
Basically, after installing the Google Keyboard (to get the voice-input for messages) I THINK I'm done for now
BTW, thanks for the suggestion about Slim Jellybean!
Thanks mate!