Really screwed things up

[truslide]

hit me up on gtalk if it doesnt work and you wanna keep trouble shooting it. i'm about to be offline for a few hours...

 

[PreGk]

Thanks, I am going to perform a full erase.

Sent from my PC36100 using Tapatalk

 

[PreGk]

I wiped dalvik and cache and did a data reset in AR 1.8....Flashed Vaelpak 2.3 and guess what? Still getting permissions errors when trying to fix permissions in RM...I just nandroided back to a backup I made before resetting.

 

[Jerzyiroc]

Gonna hit up Vaelek about this. This is the first time I've heard of anyone having this problem after using VaelPak settings.

 

[vaelek]

Unless I'm missing something in here, it sounds like the problem at this point is you get an error when running fix permissions in rom manager? I'm wondering what the reason is that you are trying to run fix permissions? Is there something else that is not working?

If there is more to it than that, then what would be the most helpful is if you were to do whatever it is that is not working, and then launch CatLog, hit menu and save, and send me the file. JimAtVaelekDotCom

 

[PreGk]

Yea, I was trying to fix permissions bc of the FC on WT...I also cant flash other clockwork recoveries.....Still dont understand why kernel 11 screwed everything up.....I'll do a catlog soon. Thanks for the great support.

 

[vaelek]

Oh crap dude you know what. I need to get that out of there. The #11 kernel was from the last ota, which if I'm correct here, contained the framework part of the ota as well. If that's the case, then that is almost definitely the cause of any problems you might have had afterwards.

Edit: The plot thickens.. it seems the link for #7 was actually put in for #11

 

[PreGk]

Vaelek that definitely has to be it..everything was great until I flashed #11....any fix for this?

 

[vaelek]

I will have to make a flash zip specifically for this scenario. I should be able to get you back in working order. I hope to have something for you in 30-60 minutes.

 

[vaelek]

Ok I think this should undo any damage that the htc kernel flash did.

If you are still on that kernel, I would highly recommend flashing a different one after flashing this.

I think it is too big to attach here, so I uploaded it here

 

[truslide]

i bow to you. so glad you chimed in... i will donate again...

 

[PreGk]

Ok I flashed .zip. scrolling seems smoother and I'm running pretty well....still got the Rom manager problems....oh well. Vaelek, what's your paypal? Id like to buy u dinner to show my appreciation.

 

[vaelek]

At least it did some good I suppose. I haven't checked my mail yet but if you haven't, feel free to still send me that log and I'll see if I can't figure out what else is going on there.

If you wish to donate, go to Vaelek.com and the donate box is on the lower right. And thank you in advance!

 

[truslide]

do your best to get a log. If vaelek can't fix it, then it can't be fixed... Sorry I couldn't help man, I'm not as savvy with this stuff, not like Vaelek, I'm still learning the ropes at that level. I know basics to say the least.

 

[PreGk]

Thought all was working...but gmail won't send any emails now and my battery is draining like crazy. just gets stuck on "sending"

 

[truslide]

what kernel are you running?

1. flash new kernel
2. wipe battery stats

see what happens. try a netarchy kernel. they are very compatible with Vaelpak 2.3

what does the log say when you try to send an email? does it give any info other than the standard?

 

[PreGk]

I just flashed netarchy with HAVS. GMAIL is working now. Still having RM problems ...guess its not a big deal though....Vaelek, are you going to add the stock Vaelpak kernel to the setting apps? Thanks.

 

[PreGk]

Here's my clockwork recovery log:
Starting recovery on Thu Nov 18 15:02:53 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=ECLAIR
ro.build.display.id=koush_supersonic-eng 2.1-update1 ECLAIR eng.koush.20100714.213746 test-keys
ro.build.version.incremental=eng.koush.20100714.213746
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Jul 14 21:38:26 PDT 2010
ro.build.date.utc=1279168706
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=HTC Evo (US)
ro.product.brand=generic
ro.product.name=koush_supersonic
ro.product.device=supersonic
ro.product.board=supersonic
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=supersonic
ro.build.description=koush_supersonic-eng 2.1-update1 ECLAIR eng.koush.20100714.213746 test-keys
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT0A7HL14623
ro.bootmode=recovery
ro.baseband=2.15.00.09.01
ro.carrier=COMMON
ro.bootloader=0.76.2000
ro.hardware=supersonic
ro.revision=3
init.svc.recovery=running
init.svc.adbd=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Set boot command ""

 

[truslide]

thats your recovery log. we need the catlog. if you dont have it its in the market... "Catlog". once you have it, start logging by opening the app>menu>start log. then do whatever it is you were trying to do when you got the error. meaning, recreate the error. once you've done that. open catlog>menu>stop recording. it will save automatically. send the catlog to vaelek via email

 

[PreGk]

Sorry for the confusion , I thought the recovery log was intetesting...I sent the catlog to vaelek last night but will send again bc of gmail issues I had.