I installed for first time AXURA rom with Vodoo Lagfix..
It booted fine, and everything was good (sign, data, fast, stable)
But I always like to format both my internal and external SD Card when I flash a new rom, so I did.. and also I went to recovery and wiped all user data.
Now when I turn on the Vibrant, it shows the initial screen (Vibrant - Samsung) and then it load the boot up animation, but anything more happens...
Is normal to have to wait, was good to format and wipe having Voodoo Lagfix enabled? or did I mess everything? I can get to recovery mode.. But I want to learn if I did something wrong? What should I do now
ivan0550 said:
I installed for first time AXURA rom with Vodoo Lagfix..
It booted fine, and everything was good (sign, data, fast, stable)
But I always like to format both my internal and external SD Card when I flash a new rom, so I did.. and also I went to recovery and wiped all user data.
Now when I turn on the Vibrant, it shows the initial screen (Vibrant - Samsung) and then it load the boot up animation, but anything more happens...
Is normal to have to wait, was good to format and wipe having Voodoo Lagfix enabled? or did I mess everything? I can get to recovery mode.. But I want to learn if I did something wrong? What should I do now
Click to expand...
Click to collapse
did you wipe/format before or after flashing??
TopShelf10 said:
did you wipe/format before or after flashing??
Click to expand...
Click to collapse
I did it after flashing...
ivan0550 said:
I did it after flashing...
Click to expand...
Click to collapse
it certainly sounds like wiping with voodoo running may have caused it, but im not entirely sure.
thats the only downside to running voodoo, is that its so damn touchy. ive learned (the hard way, many times) to pretty much disable voodoo before doing ANYTHING on my phone, in order to avoid problems like this.
you are going to have to reflash Axura and start from scratch. if that doesnt work, youll have to ODIN back to true stock 2.1, and then flash your ROM of choice.
Dont mess with Voodoo magic..........
TopShelf10 said:
Dont mess with Voodoo magic..........
Click to expand...
Click to collapse
This should have an "IF" at the end of it. Because you SHOULD mess with the voodoo if you want a faster phone. You just need to play carefully with it and disable before flashing (unless what you are flashing is also voodoo).
ivan0550 said:
I did it after flashing...
Click to expand...
Click to collapse
If you wipe after flashing it's not doing anything for you especially since Axura wipes during install. If anything, by not wiping first there may be something still stuck in there that affected the flash of the Rom.
I would boot into CW and re-flash Axura. When it's done just hit reboot and wait for it to load up.
Related
I just download roms directly on my phone, go to rom manager, install rom from sd card, check wipe data and cache, and reboot. everything has worked fine so far, I've installed 3 different roms every since I started and am currently running nero v3 with voodoo enabled.
You want to odin back to stock as I understand it roms can leave behind traces of themselves or not be compatible with new ones so it's best to use odin to make sure that nothing is left of them
willsnews said:
You want to odin back to stock as I understand it roms can leave behind traces of themselves or not be compatible with new ones so it's best to use odin to make sure that nothing is left of them
Click to expand...
Click to collapse
ahhh ok. damn I need to install windows on my latop asap. thanks.
junglerumble said:
I just download roms directly on my phone, go to rom manager, install rom from sd card, check wipe data and cache, and reboot. everything has worked fine so far, I've installed 3 different roms every since I started and am currently running nero v3 with voodoo enabled.
Click to expand...
Click to collapse
The way you download roms and flash them is a very easy way to do it. BUT, seeing as you are using a rom that has voodoo embedded, learning how to properly use odin is very important. All is well, until you forget to disable voodoo and flash something else and your phone gets hung up in the boot screen.
I stayed away from odin for as long as I could. Flashing thru CWM was far too easy. That was until I did exactly what I just mentioned and forgot to disable voodoo. Then I had to learn quick, fast, and in a hurry.
Take my advice. Read up on odin as much as you can to save yourself some trouble later on. Do yourself another favor and download all the necessary tools for it, as well.
is using odin on ubuntu ok? I got odin running through wine but I don't wanna brick my phone thinking everything will work properly lulz.
I have been having this problem even after doing everything correctly:
I wanted to try this ROM here:
http://forum.xda-developers.com/showthread.php?t=1195912
So I went back to stock using the ODIN files from here:
http://forum.xda-developers.com/showthread.php?t=734475
Then used the GB bootloaders from here:
http://forum.xda-developers.com/showthread.php?t=1117990
Installed CMW recovery. Once done, I used the zip to install the rom.
Now the phone boots up, goes to the bullet screen after sometime boots up again. Any idea guys?
go back into cwm and wipe data/fact reset
wipe cache
reboot system now
While in your bootloop get back into recovery and reflash the rom (I had to do this on Miui and Simply Honey when I first installed them)
why would they do that though? ^^^
vabeachfc3s said:
why would they do that though? ^^^
Click to expand...
Click to collapse
I don't know why it worked but it worked for me
Sent from my SGH-T959 using XDA App
Tried both the methods. Nothing seems to work.
I tried disabling vodoo and re-flash. The problem I have then is it just loops. When vodoo is enabled it goes to data parition not enough space issue.
Any help anyone?
Did you wipe date/factory reset, wipe cache, and wipe dalvik before flashing rom then wipe cache and dalvik and fix permissions before rebooting?
EDIT: Also I would backup everything on your SD cards. I got that not enough space on partition before and it ended up wiping my sd cards.
Sent from my GingerZen Vibrant using XDA Premium App
yes I did. Well looks like vodoo lagfix did its number on me. The internal data has been cleaned up , I am having MBR checksum errors and still doesn't work.
Also you can try this instead of odining back to jfd stock. It's worked really well for me when I've had major problems. Cleans everything up really good.
(QUOTE=Br1cK'd;16231313]Themes
I have posted about it in several threads, including my own, so I figured I would finally put it in a central location. This is my FTDNB method for starting with a fresh, clean phone, without any ghosts of roms past popping up to cause you issues.
Download this first, and flash through Odin with your standard 512 pit file
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Then when it reboots to the recovery screen, pull your battery, reinsert it and boot up to dl mode, and flash the following, with your same pit file, and selecting repartition in Odin this second flash only:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
The first link there is Eugene's Froyo That Does Not Brick, but it doesnt work that well as a driver. As an eraser its great though! The second link is the Froyo JK2 leak, with fixed recovery and already rooted. If the first one didnt, the second flash will definitely put you back on Froyo bootloaders.
Thats my whole secret to keeping a clean phone and wiping out any ghosts. You can proceed from there in your desired direction (back to ZD or GZ preferrably) in a safe manner. Its always worked for me to clear up any oddness, and literally takes 15 minutes tops once you have the files downloaded.[/QUOTE]
Sent from my GingerZen Vibrant using XDA Premium App
Hey guys.
Using Samsung Galaxy S Froyo 2.2.1 I9000
Was installing CM7 today through CWM in Recovery Mode, at first it wouldn't work, threw me an error about signature verification, found it was because of 3e verification on zip files, so flashed the kernel with Odin to 2e.
After installing the kernel, ran the CM7 again and it ran fine, followed the instructions, wiped before installing CM7. The install looked like it ran fine, phone rebooted no problem, but it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Anyway, there's no GMail app, and only Market, and Market wont let me add a Google account even if I say yes to the prompt. Looked round the SGS forums, didn't see anything like this.
I'm guessing I did something wrong, help someone?
Belahzur said:
it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Click to expand...
Click to collapse
What do you mean by this?
Theonew said:
What do you mean by this?
Click to expand...
Click to collapse
I can only describe it as once I got to the step of rebooting the phone, it didn't load CyanogenMod, I was expecting the CM animation but I got my normal Froyo screen, does that make sense?
Probably a bad download. Delete the download and do it again. But just a word of advice...ROM's come with kernels, so if you flash a kernel first and then a ROM, you are going to lose the first one you flashed.
Thanks lowandbehold, one problem though.
I wiped the phone following the instructions, so I don't have ROM Manager anymore and can't open the Market, it asks me if I want to sign in with a Google account, I hit yes and nothing happens.
Ideas?
Sorry for double post, looks like I made some progress possibly.
Got the CM7 animation on boot, but doesn't go any further.
Got Clockworkmod recovery up though, flashed speedmod kernel, and CM7 initial kernel through ODIN.
Now in recovery mode when I go to install "update-cm-7.1.0-GalaxyS-signed.zip" I get an error about assert failed, error in the zip, status 7 and aborts.
Did you make a nandroid backup of the stock ROM before you flashed? If so, try to revert back to that. If you didnt make a backup, do a full wipe...wipe data/factory reset, wipe cache, and go into advanced and wipe the davlik cache. Then go to install zip from SD Card and select the CM7 zip. You should also check the md5 sum of the zip file to see if it matches up to make sure the download was good. You will be able to figure something out, as long as you can get into recovery and not getting crazy cache errors your phone should be 100% recoverable. Maybe even try something that is not CM7...just keep at it.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
Also, standby on the kernel for now. Get CM7 up and running on the kernel it provides you with and then make a backup in CWM. Then you can try to change the kernel...if you have issues then you can just go to your CM7 backup.
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Belahzur said:
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Click to expand...
Click to collapse
No, it's in recovery/backup on the clockword recovery screen.. personally, I like Amon Recovery a lot better than CM. Clockwork doesn't wipe the cache as well good luck! Hope you get it working
Sent from my Evo 4G using Tapatalk.
kendallc123 said:
Clockwork doesn't wipe the cache as well
Click to expand...
Click to collapse
Fixed your spelling (bold). Anyways, do you have proof of this?
Theonew said:
Fixed your spelling (bold). Anyways, do you have proof of this?
Click to expand...
Click to collapse
Thanks haha, went back and fixed it too. I don't have solid facts about it, but I have read in multiple threads that
1) People love Clockwork
2) People say Clockwork doesn't wipe the Dalvik cache thoroughly and sometimes causes boot loops (I've never had one)
I have had some problems with Clockwork personally. But, this is just my opinion. Also, Clockwork doesn't recognize some zips that I try to flash while Amon does. Anyway, it's all your opinion, whatever feels better to you.
Hi, I'm pretty new at this. I managed to odin to JFD, and flashed Toxic Crazy8 which I really love. I've been using it for most of this week. Tonight I decided to flash the Carbon Fiber Blue theme for it. So I followed the instructions in the dev thread - booted into clockwork recovery, wipe cache partition, flash theme, wipe dalvic, fix permissions, reboot.
At that point, it hung on the spinning Samsung animation of the bootup and would go no further. So, I went back to recovery, and restored to my latest nandroid backup. (wiped dalvic, fixed permissions, reboot) Now its stuck on the Bali startup screen with the palm tree and will go no further.
Advice please? So sorry I messed with it when it was working so well.
Best way is to go into download mode and flash back to JFD
Thanks. I'm at work right now so will have to wait till I get home to hook it up to the computer to use odin. Is that the only way? Could I just flash the Toxic 8 rom or will that mess things up worse?
Go here and download the Revert package. Flash it and then reflash the Carbon if you want or leave it at stock. I ran into this a few times. Something about the themes.
A nice theme is in that same thread. It is a Gingerbread theme. I used it for a long time.
Recovery
Wipe Cache and Dalvik
Flash Revert
(if you want to flash another theme, here is where you want to do it).
Wipe again for good measure
Fix permission for good measure
Reboot. This will take up to 5mins but should do the trick.
Woodrube said:
Go here and download the Revert package. Flash it and then reflash the Carbon if you want or leave it at stock. I ran into this a few times. Something about the themes.
A nice theme is in that same thread. It is a Gingerbread theme. I used it for a long time.
Recovery
Wipe Cache and Dalvik
Flash Revert
(if you want to flash another theme, here is where you want to do it).
Wipe again for good measure
Fix permission for good measure
Reboot. This will take up to 5mins but should do the trick.
Click to expand...
Click to collapse
Thank you. I think I will leave at stock I don't need these messes. But now that I'm stuck at the Bali boot screen, how do I load that revert file onto the phone? I'm having a brain cramp here probably because I worked all night.
What I think you can do is, if you can get into recovery with the button combo, do that. Hopefully you have either the original ROM zip on your SD card or you can get into your backups.
It really all depends on what you have on your internal SD since right now it is un-usable as-is.
A. Boot into recovery, wipe and flash your backup.
B. If this doesn't work, then flash the original ROM. Let it boot. Once that is done then you should be able to reflash your backup or at the very least reinstall XDA app and go to this thread and download the revert package and reflash.
C. Wait until you get home and Odin and then reflash your backup.
Sucks I know and especially being "trapped" at work.
Ok, got it into red recovery. I'm home now. I tried downloading the AIO Vibrant toolbox program, but it keeps freezing on my computer.
When you say "wipe and flash your backup" I want to make sure I understand what wipe you're talking about. Wipe cache? or wipe data/factory reset ?
I do so appreciate the help. I learn by making mistakes and man, I've learned so much the past couple of weeks messing with this phone.
Edit: I managed to mount the usb storage in recovery, so copied the revert file to my sd card.
I wiped cache and dalvik, flashed the revert, wiped again, fixed permissions, and rebooted. Still stuck at the Bali screen.
knitten2000 said:
Ok, got it into red recovery. I'm home now. I tried downloading the AIO Vibrant toolbox program, but it keeps freezing on my computer.
Click to expand...
Click to collapse
Don't forget to download the .net files too.
When you say "wipe and flash your backup" I want to make sure I understand what wipe you're talking about. Wipe cache? or wipe data/factory reset ?
Click to expand...
Click to collapse
Wipe cache and wipe dalvik-cache. Don't Factory Reset unless you are doing a clean install, otherwise you'll wipe out the nandroid you just restored.
I do so appreciate the help. I learn by making mistakes and man, I've learned so much the past couple of weeks messing with this phone.
Click to expand...
Click to collapse
We have all been there. Don't let this scare you off though. Use what happened and learn from it. When theming though, always look for a revert package and download that before flashing any themes.
Hey you knew rule #1 though. "Always make a backup". Good luck and try the Gingerbread theme. It is refreshing as opposed to the stock Black that came with the ROM.
I edited my last post as you were replying. I wiped, flashed the revert, and now stuck at the Bali screen again.
Keep trying. IIRC i had to do it a couple of times for it to stick. Remember it takes a bit to rebuild the Dalvik after a wipe.
If you keep trying and it doesn't work, the since you can get into red recovery, maybe flash fresh ROM and once it boots up and settles down, maybe try restoring you back up then.
Ok, I'm searching for info on restoring the backup. Do you just use the backup and restore menu in recovery? Or do you somehow flash the backup file in a different way?
Just use Restore/ Backup in the recovery. There is an advanced part of it too. Try just restoring the /system part only as it holds the Framework-res.apk and Services.jar files that the themes use. Hopefully that will do the trick. If not then you can restore all and it should be fine.
Well after trying the revert twice, I flashed the Toxic Crazy 8 zip instead. It's alive!!! Thank you so much!!
This stuff is not for the faint of heart I can see. So glad for the help here.
Will be putting it aside for now and getting some sleep.
Since you'll be essentially starting from fresh, you should flash Deranged9 (also from JCC with equally great battery life) and a nice blue theme (RC3 is the one now).
Or try Fish's redux of Bionix' 1.3.1
My daughter has this phone and looking to root it but I see many pole getting stuck. I think ill wait on doingthat
Rooting is easy. Just go to the Noob guide stickied up in Q&A and scroll down to Option A. Download that, put it on your internal SDcard, reboot into recovery, reinstall pacakages (will have to do this twice) and reboot.
ROOT does not do anything but give you permission to the internal Adroid O/S. It is usually the mods that you do after the fact that can/will screw things up. Rooting doesn't change o/s, doesn't affect battery life, doesn't make your phone not send data,...all it does it give you access (and probably void your warranty).
guys i have a funny issue wonder if i can get some help. I flashed FlappJaxx Beta 3 and had a bad down load or something so anyway tons of reboots and nothing just the non stop vibrate.. well i i finally got it back to the down load screen after pulling the battery several times. and got it Odin back to unrooted and turn on followed the unroot instruction well i left it stock and have had same issue where i click something and it flashes and just vibrates over and over until i pull battery.. well is this phone dead is there a fix?
I odin back again and same thing im going to odin back to stock again then do a stock root and flash another room but its doing the stupid reboot over and over vibrate thing even with the non-rooted stock rom. i just can't seem to find any direction on how to fix this or is it just a lost cause. wanted it to hold on till Note 2 hit shelves but looks like a s3 in my futures.
OK didnt work still FC and boot looping this time i installed Kies and put in download mode and updated the firmware and im getting same thing. GOSH DOGGIT hahaha.. Yea i need some advise i tried everything ive read i must be missing something somewhere.
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
walkerkd said:
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
Click to expand...
Click to collapse
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
walkerkd said:
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
Click to expand...
Click to collapse
What language are you using here? I have no idea what you are saying.
kmacsouris said:
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
Click to expand...
Click to collapse
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
gregsarg said:
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
Click to expand...
Click to collapse
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
walkerkd said:
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
Click to expand...
Click to collapse
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
gregsarg said:
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
Click to expand...
Click to collapse
oh really? wow i didnt even think about that im wiping again and flashing odin to stock but this time after it boots i will wipe factory reset. then root factory reset and fix permissions. thank for the help!
Always welcome ....
Fixing permissions is overlooked a lot ...
And the wrong permissions will cause FC's all over the build ..
I always fix permissions after any flash or modification ....it's just a good habit to get into ...IMHO ...g