Extremely laggy on Nero V5 - Vibrant Q&A, Help & Troubleshooting

I flashed Nero v5 and it went bizerk on me. These are the steps I performed that got me here
1. Rooted my phone from stock
2. Flashed Clockwork recovery via Rom manager
3. Flashed Nero V5 with voodoo.
4. Didn't like it so I disabled "voodoo upon next boot" and wiped data and cache then flashed Axura 2.2.6
5. Now pressing the menu button is weird and unresponsive at times and using swype to type gives me crazy vibration feedback.
6. So I Odin'd to Eugene's SamsungS Froyo and pit
7. Then I Odin'd to JI6 and its still buggy.
What happened?!!

Wipe everything and install Axura again. Keep voodoo enabled. Stick with JL5

Unfortunately with these leaked ROMS you sometimes get some buggy action. Every time I try a new ROM out I Odin to stock, root, cwm then flash.
One thing I have also found in my flashing is that some of the backed up apps I have titanium restore cause some bugs so I had to narrow down what apps were doing it by installing one by one.
Also, most of the developers suggest letting your phone sit after initial boot up for 10-20 minutes. I have found this to really make a difference. I am on Nero V right now and it's blazing through everything.

What????
beeroatsnp90x said:
I flashed Nero v5 and it went bizerk on me. These are the steps I performed that got me here
1. Rooted my phone from stock
2. Flashed Clockwork recovery via Rom manager
3. Flashed Nero V5 with voodoo.
4. Didn't like it so I disabled "voodoo upon next boot" and wiped data and cache then flashed Axura 2.2.6
5. Now pressing the menu button is weird and unresponsive at times and using swype to type gives me crazy vibration feedback.
6. So I Odin'd to Eugene's SamsungS Froyo and pit
7. Then I Odin'd to JI6 and its still buggy.
What happened?!!
Click to expand...
Click to collapse
What does you recent problem have to do with Nero?
You are three flashes past that now. You went through two different roms from stocK, then Odin'd twice, and you're wondering why it's buggy?
If you didn't like Nero then fine, but before you go to another developers rom, you should have odin'd back completely to stock.
I happen to have had no bad experience with TW roms, and I did try the Axura rom, It was nice, and smooth, very responsive, but it just felt heavy for some reason, so I odin'd back to stock and then went to Nero 4.1, (I'm on v5 now) It really does come down alot to personal prefference on these roms. And if you don't like the TW roms, that's fine, but don't start a thread stating "laggy on Nero 5" when your lagging now three flashes later.
Take it for what you will.

Your problem is that you went from a modded I9k froyo Rom to an "incomplete" vibrant Rom.
Odin to jfd WITH reparation checked. Jfd is a "complete" Rom, unlike ji6 (which is an upgrade Rom)
Once that is done, then see how your phone handles.
"if you amplify everything, nothing is heard"

beeroatsnp90x said:
I flashed Nero v5 and it went bizerk on me. These are the steps I performed that got me here
1. Rooted my phone from stock
2. Flashed Clockwork recovery via Rom manager
3. Flashed Nero V5 with voodoo.
4. Didn't like it so I disabled "voodoo upon next boot" and wiped data and cache then flashed Axura 2.2.6
5. Now pressing the menu button is weird and unresponsive at times and using swype to type gives me crazy vibration feedback.
6. So I Odin'd to Eugene's SamsungS Froyo and pit
7. Then I Odin'd to JI6 and its still buggy.
What happened?!!
Click to expand...
Click to collapse
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
this will fix your problems lol. Gosh this link is the savior to many lost souls indeed.

always rooy back to stock before flashing a new rom.

geoffcorey said:
Your problem is that you went from a modded I9k froyo Rom to an "incomplete" vibrant Rom.
Odin to jfd WITH reparation checked. Jfd is a "complete" Rom, unlike ji6 (which is an upgrade Rom)
Once that is done, then see how your phone handles.
"if you amplify everything, nothing is heard"
Click to expand...
Click to collapse
+1
"if you amplify everything, nothing is heard" Damn...... I amplify everything, so nothing is heard NOW that's how you play politics

cjggilbert said:
What does you recent problem have to do with Nero?
You are three flashes past that now. You went through two different roms from stocK, then Odin'd twice, and you're wondering why it's buggy?
If you didn't like Nero then fine, but before you go to another developers rom, you should have odin'd back completely to stock.
I happen to have had no bad experience with TW roms, and I did try the Axura rom, It was nice, and smooth, very responsive, but it just felt heavy for some reason, so I odin'd back to stock and then went to Nero 4.1, (I'm on v5 now) It really does come down alot to personal prefference on these roms. And if you don't like the TW roms, that's fine, but don't start a thread stating "laggy on Nero 5" when your lagging now three flashes later.
Take it for what you will.
Click to expand...
Click to collapse
I'm not bashing TW or Nero ****boy. I am a fan of theirs and have always preferred their roms. What I was saying is that I had not had problems with any of their roms ever before flashing Nero 5. Get your **** straight before trying to flame someone.

Related

[Q] Phone doesn't boot, sits at black screen after boot animation

So, I messed up. The plan was to uninstall RyanZA's lagfix, then flash JAC's new OC/UV kernel with Voodoo. I got distracted, and didn't uninstall the lagfix before flashing (through Clockwork, if that matters). My phone didn't boot after an hour, so I figured I'd nandroid back and not be so stupid this time. When I tried, I found that I couldn't because of the change to the /data from Voodoo. So then I figured I'd just use Odin to go back to stock, I've done it a couple of times before. That didn't work either, Odin went just fine, but it still doesn't get past the black screen. I read the Voodoo thread, and saw the "disable-lagfix" thing you can do, but now I can't mount my sdcard, and when I try to push it with ADB, it says permission denied. How can I fix this? Also, as an aside, since I flashed the stock back on, with the T-Mobile boot anim and all that, will I be able to get it replaced, if need be?
Flash this first:
http://forum.xda-developers.com/showthread.php?t=740558
Then flash back to stock with odin, worked for me.
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Zaphodb2002 said:
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Click to expand...
Click to collapse
Yeah, I soft bricked my phone yesterday and couldn't get it back up and running with the stock rom until after I flashed eugenes froyo rom first. My guess is that because eugene codes his roms to automatically format your OS drive it clears everything out and sets a fresh slate so you can than flash the stock rom back without issues.
Pure speculation on my part though. Glad you got it fixed.

really unhappy with ji6... downgrade question

I am unhappy with ji6, my gps and compass no longer work and i've had nothing but problems since the update. also the call waiting dial screen lag sucks. I would like to go back to my previous rom which was basically stock rooted with ji2 gps fix and accurate battery mod. I have this saved as a backup, but I am afraid to flash it. When I flashed the new ota update it bricked my phone. I was unble to load my previous backup through clockwork recovery. I had to completely wipe my data and start over. any advice on the safety of trying to flash back to my backup rom, will it conflict with the ji6 framework?
Thanks
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
yeah, maybe i'll try bionix first, It's just that I was really happy with the way it ran before this stupid update.
I also was fond of my setup before the update. Bionix made it better again. Hope you like it, worst case go back to stock.
I will say I would make sure you can revert to stock from bionix. I have seen a number of posts with issues, but that may be from people who had the oc kernel? I can't say with certainty.
Same here, i flashed bionix (first time using bionix) I flashed bionic 1.7 w ji2 modem oc/uv no voodoo and this thing flies! Gps is fine, navigation is usable.
s15274n said:
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
Click to expand...
Click to collapse
I tried flashing back to my backup...(stock, rooted with bat mod and ji2 gps fix) and it got stuck in the vibrant startup screen, same as when I ran the ota. I guess my previous setup is no longer an option. Before I try another rom and have to redo all of settings and apps again, I would like to try to at least get the gps working on the ota ji6. Any advice on how to do that would be appreciated. So far I have tried all of the things I was able to find in other threads...deleted gps data, made sure lbstest settings are stock, turned off wireless, etc. I still get no locks at all.
Is bionix really that good? I'm considering it. I'm on my stock rom, stock kernel.
I think i'm going to try it out.

Want to try other Roms

Hello guys. I currently have Eugene Gingerbread Clone R2 Rom with JL4 Voodoo Lag Fix on my Vibrant.
I want to try other roms for fun. I have some apps and my contacts and stuff backed up and also the entire rom itself. i also have the Stock (Rooted) Backed up as well. My question is how do i go about going back to the "Stock Rooted" safely without using the odin program.
Born2rade said:
Hello guys. I currently have Eugene Gingerbread Clone R2 Rom with JL4 Voodoo Lag Fix on my Vibrant.
I want to try other roms for fun. I have some apps and my contacts and stuff backed up and also the entire rom itself. i also have the Stock (Rooted) Backed up as well. My question is how do i go about going back to the "Stock Rooted" safely without using the odin program.
Click to expand...
Click to collapse
Well, assuming you have ALL of your apps and data and contacts and such backed up with Titanium Pro (make sure, you don't want to lose this stuff!), just reboot into clockwork recovery.
NEXT DISABLE VOODOO OR DIE.
I'm also assuming you made a backup of your "stock rooted rom" with Clockwork Mod Recovery? Now, just reboot into that green clockwork recovery and go to nandroid or backup and restore and click RESTORE.
Yes i have my stock rooted backed up and also my gingerbread rom backed up as well and also some of the important apps and my contacts backed up.
I will give it a try now.
I don't think it worked lol. Screen shows "Searching"
Sweep screen to unlock but screen is black and i cannot do anything.
cannot seem to get back to recovery either
Bob forgot a very important step, flashing a 2.1 kernal...
Best way out is to just flash another Froyo rom through clockwork since you don't want to mess with Odin.
I recommend Axura 2.2.5.7 as well as Nero V3. Go get those and see what you think.
*Edit* just saw your post 1min before mine. You may be using Odin after all.
Ok Thx. Makes sense lol
Nah i only use Rom Manager.
Ok i'm back to my Gingerclone.. I'm going to find Eclair 2.1 kernel, i assume thats the one i need to get and yes i will make sure to disable voodoo before i flash the 2.1 kernel .
Thx.
Born2rade said:
Ok i'm back to my Gingerclone.. I'm going to find Eclair 2.1 kernel, i assume thats the one i need to get and yes i will make sure to disable voodoo before i flash the 2.1 kernel .
Thx.
Click to expand...
Click to collapse
If you just want to flash other roms, you don't have to return to 2.1 IMO.
Just backup everything (Titanium/Nand/Launcher Pro if used), then clear data and cache in clockwork. After that go to install zip from SD and select the new Rom which should be sitting on your internal 16g memory and let it do it's thing.
Ok well i tried other roms. I tried Nero V3, That one was bad, internet was uber slow and Gps doesn't work.
I tried Axura 2.2.5.7, Worked very well except Gps also does not work.
Right now i'm going to stick with my Gingerbread R2 as for everything works extremely well.

[Q] Did I Just Experience Kernel Panic?

Was originally typing this in the Nero thread but didnt wana add clutter..
Ok, so I've been running Nero with voodoo enabled for a little over a week with no issue. ROM was smooth and battery life was solid. Then yesterday for the sake of a little more battery life I disabled voodoo and flashed the Super IO kernel to see how it would be in this ROM. Everything was fine for a while but then they phone would freeze everytime I ran GPS Test Plus. Only thing it would respond to was hitting the power button to put it to sleep and from that it would not wake (sleep of death). I proceeded to pull the battery. Immediately after the phone fully booted I began getting endless force closes from what seemed like every single all on the phone. Pretty sure this was kernel panic yes?
So I reflashed the JL5 Voodoo kernel (posted in the Nero OP) thinking that would fix it. the force close storm stopped but the phone was still acting up freezing and still wouldnt wake from sleep. I decided then backup, factory reset, wipe cach and dalvik cache, and reflash Nero. I thought all was well but to my surprise after being on the charger all night I arrive to work to find that my battery was at 74% O_O. This is shocking due to the fact that the phone had only been off the charger for about 45 minutes and had not been used AT ALL during that time.
So my question is... Did I just have a bad flash or did flashing the Super IO kernel do some unseen damage? Checked the battery info in Spare Parts and nothing looked out of order.
I would recommend, going back to stock and reflashing nero 3 and retrying the Super IO kernel. Hope that fixes the problem.
Will do when I get home. I assume this will unroot me, right?
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Same thing happens to me when i touch Eugenes work. Thought I was the only one
Sent from my SGH-T959 using XDA App
Br1cK'd said:
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Click to expand...
Click to collapse
regP said:
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Click to expand...
Click to collapse
I was only successful with Super IO when I flashed it after a clean rom install. It sucks, but........
This is interesting, I experienced the same type of battery loss upon flashing Nero V3 for the first time. But, I did not flash eugenes super io kernel. I just stuck with the JL5. Although, Once I did a good recondition on my battery, Things seem to be much better. I'm a stickler when it comes to battery life though lol. Whens the last time you reconditioned the battery and wiped the stats via recovery?
I wipe the stats after every flash. I don't recondition unless the battery meter is trippin because I use 3 different batteries. 2 of which are knockoffs but they last about the same as the original. I factory reset, wiped caches again and then flashed the latest Axura. To my surprise after flashes and restoring data I booted into recovery to find the jl5 voodoo kernel was still there.. so I flashed Eugene's eb-productions stock kernel and everything seems to be fine.
What happened with the fc storm WAS kernel panic right?
I spoke too soon. Battery is still draining like a mofo and now I know why. Checked spare parts battery history and it reports that the phone wont go to sleep. Ill have to try to Odin back to stock when I get home
I have a few questions though because I've never done this before.
1. I downloaded Eugene_E2_JK2 from the Bible. Is that one fine or should I flash back to a stock 2.1 ROM
?
2. Will this process unroot my phone?
3. How is flashing the stock rom with odin any different than doing a factory reset and flashing with clockwork? I'm just worried that since flashing in clockwork didn't work odin wont either.
Vibrant via XDA App
So I odin back to JK2 then flashed a fresh installation of the latest Axura. Everything went fine as far as the flashing but after first boot I went back into recovery and i think the voodoo kernel from nero was active because I had the red letters and an option to enable voodoo O_O. WTF? I disabled voodoo before i did odin. I'm pretty sure Axura doesnt come with the voodoo kernel so how it was there after i came from stock is beyond me. So I flashed the EB-Productions stock kernel which i have used on Macnut and Axura and gotten great battery life before going to Nero. The battery still seems to be draining faster. Spare Parts reports that the "time spend without sleep" is about 10 minutes less than the phones boot time. I havent touched the phone since it booted so i dont see how thats possible.
I have no idea whats going on... Any help would be greatly appreciated. Im about ready to pull my hair out..
Just ODIN back to shipping rom (remember to use pit file and check repartition) It is better to do that everytime you are changing roms with kernel......
What difference would odin to stock 2.1 make over stock 2.2..?
regP said:
What difference would odin to stock 2.1 make over stock 2.2..?
Click to expand...
Click to collapse
The stock 2.1 is the official t-mobile software as it came from the factory. Any 2.2 we have is leaked, there is no official 2.2 for us yet. Although the 2.2 you said you flashed is as close as we got to a stock froyo rom. Flashing one of the two should get you back to stock, but the 2.1 is accepted the official base by many to start from, square one so to speak. After flashing stock, before any other roms are applied, you shouldn't have the red voodoo cwm anymore.
If you do still have voodoo after flashing stock, search for Eugene's Froyo that doesn't Brick. Flash through odin with the 512 pit file, you will reboot to a recovery that doesn't work, pull your battery, set up odin with either stock 2.1 or leaked 2.2 and the pit file, boot back to download mode, and flash the stock rom, being sure this time to select the repartition check box in odin. This will remove voodoo, and is the fix for times when voodoo goes bad. After this you will be as stock as you can get, and if you need a link to the froyo that doesn't brick, let me know I'll post it.
Ginger Clone's of the World Unite! Via the XDA App
What's the difference between reconditioning and just wipeing the stats. I've wiped it through clockwork before however what's reconditioning?
Sent from my SGH-T959 using XDA App
Reconditioning is charging your battery fully then letting it run down until the phone turns off then charging it back up again. The purpose is to make the battery reading more accurate if it seems to be inaccurate.
In other news... I odin back to stock 2.2 AGAIN then reloaded Axura. All is well now. Still bugs me though that voodoo was still there after the first odin. Just dont see how that was even possible.
Thanks for all the help!
The latest axura rom comes with the voodoo kernel, so if you flashed it, you will have, or should have, voodoo recovery. That was my point about checking recovery after flashing stock to verify it was removed, if that was what you were trying to do.
Ginger Clone's of the World Unite! Via the XDA App

Can't figure it out.

Tried to flash a custom ROM for the 15th time or so, with the same result. E: Can't Symlink /system/bin/su
Failure at line 16
Have researched this error, thought I had it figured out. Obviously not. Feel like an idiot. I never had any problems loading custom ROM's on 2.1.
BTW, I am rooted thru S1Click, have backed up thru nandroid and Titanium, have installed 3e custom recovery, everything I have read I could be doing wrong I have changed. I have tried different makers- Bionix, Axura, Eugene, all with hte same errors, so I know it's not just the ROM file.
What am I doing wrong here?
I don't know.. but let's save everyone the trouble of answering this and let you odin back to stock.
It might be something you flashed etc..
tried that too. tried loading these ROM's right after rooting and adding ROM manager. It's just weird that know one can answer a specific problem like "failure at line 16". Surprised there isn't an answer to look up based on the Line 16 error.
I'm not pointing any fingers, because I don't know the answer either. Just know that if you you give me one of the basic replies, like try ODIN to stock, I've probably tried it.
What are you odining to? I've always had success going to back to jfd. Doesn't seem to be any issues with rooting or rom manager.
Trigger + Overstock = Awesomeness
yep. Odining to jfd.
One thing is that I always install 2.2 via mini-kies before attempting to install custom ROM. Reason being that for whatever reason, the super one click just does not want to install on 2.1. Could that be part of the problem?
Here's what I do and it works every time for me.
1. Odin to jfd
2. Root then install rom manager
3. Flash clockwork recovery
4. Download rom of choice to internal sd
5. Flash rom thru clockwork
6. Enjoy
That has never failed me.
Trigger + Overstock = Awesomeness
Check This Out....Tell me If It Helped You
http://forum.xda-developers.com/showthread.php?t=848737
I did it. FINALLY.
Loaded Simply Honey 2.5, and this thing is FAST and awesome. Such a cool ROM. I was so pumped when it actually worked. Thanks for all the help, guys. And all the great developers that put in hte time and work to make our phones what they should be. Good job, guys.
Glad you got it working. The first flash is pretty awesome.
Trigger + Overstock = Awesomeness
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Br1cK'd said:
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Click to expand...
Click to collapse
This is the safest way and the best way.

Categories

Resources