[Q] deleting Voodoo Lag fix but can get phone to load completely - Fascinate General

hello everyone. i think i just bricked my phone. im trying to go back to stock mode. i have tried everything on the thread on here and androidcentral.com forums but the problem is i can only get into the Samsung Recovery Utilities menu. My phone was stuck on the Samsung load screen. I installed the voodoo lag fix and im trying to get rid of that so i can go back to stock but i can get my phone to boot up. its just freezing at the samsung load boot screen. please help me...post the files if u can thanks.

http://forum.xda-developers.com/showthread.php?t=804784

MOD EDIT - I've moved this thread to General section due to it not being related to development. Please post all queries in this section in future if you cannot find your answer first by searching

I did the same, finally after sever hours I found this thread. It's the one you want.
http://forum.xda-developers.com/showthread.php?t=867648
You'll have to install odin but it works like a charm.

Kristopherr said:
I did the same, finally after sever hours I found this thread. It's the one you want.
http://forum.xda-developers.com/showthread.php?t=867648
You'll have to install odin but it works like a charm.
Click to expand...
Click to collapse
plus one+! just saved me (again)

Related

need serious help ASAP! Please!

Tonight I decided to mess with my phone. I flashed eugene's new r13 rom, got it working fantastic. Then. I decided to try a lagfix. I heard of one in the market so i searched and found an "unofficial" app that applied the voodoo lagfix. needless to say it messed up my phone big time. At first, it restarted and some voice said "converting partition........not enough space on partition." So reboot into recovery mode and to my surprise its a diff, voodoo, version of clockwork recovery. I look at the voodoo options, cant find anything. found the area to partition the sd card. I partition 512mb i believe with no sway (i think). phone restarts. freezes on galaxy S screen. try booting into recovery. will not work. tried 10 times. tried to reboot into recovery via adb, phone is recognized and reboots but doesnt get to recovery mode, just galaxy S screen then freezes. I have NO idea what to do! Please help!!! if i left out any info, please ask!!!
first restore back to stock via Odin.
second, root and install roms again.
third, use your newly working device to read the post about non-development stuff going in the Q&A section.
adb reboot download and use odin to flash back to stock (froyo or eclair) there are plenty of threads on how to do this method. Best of luck
Use ODIN to go back to stock. no?
Umm, calm down, i think you will be fine.
Although some people are going to scream at you for putting this in the developers section.
Can you get to download mode? Turn phone off, hold down volume up and volume down at the same time, but don't touch the power button. Then, with your usb cable connected to your computer, plug the usb into your phone, while still holding down the volume buttons.
If you can get to download, then can't you just put your phone back to stock using ODIN?
I'm not an expert, but I'm assuming that should work for you.
edit:
I just uploaded odin, and the tar and pit files you need to get back to stock JFD.
I found all these files in xda originally, but didn't feel like finding each thread individually, so uploaded them on sendspace for you, much faster than searching the forum for each of these.
ODIN latest version:
http://www.sendspace.com/file/o0ivp2
Pit file:
http://www.sendspace.com/file/j9ytb3
JFD tar file:
still uploading...will post soon. ...nevermind upload taking too long, found the download link providing by justanotherdev
http://www.justanotherdev.slackdev.com/T959UVJFD.tar
I'm not an expert, but maybe you should ask everyone else if it is safe to ODIN to stock once you have messed with a lagfix and partitions.
good luck
Sounds like a trip down the "odin" lane to JFD is in order for ya. Go to the vibrant bible sticky, grab odin 1.70 and the JFD stock ".tar" file. Follow the tutorial posted, should get you back up and running.
p.s. wrong section...
EDIT: This should help you out
http://forum.xda-developers.com/showthread.php?t=810130
SamsungVibrant said:
Umm, calm down, i think you will be fine.
Although some people are going to scream at you form putting this in the developers section.
Click to expand...
Click to collapse
Correct. I'm not going to scream, but it's generally bad for to post "help me help me" threads in the development section. Either post them in the appropriate ROM thread (in your case, the thread for R13) OR in the Q&A section. Otherwise, you'll get posts just like mine that probably wont be as nice.
As for your issue, you have a soft-brick. Download ODIN, download the correct PIT and TAR files, follow the instructions in the ODIN thread to flash to stock and start over. Thats the only way you're going to fix your phone at this point.
im sorry if i placed this thread in the wrong place, im kind of new here. Guys, i really appreciate the help! can someone point in the direction of how to use odin? I have literally no idea what it even looks like or how to install it.
Also check the bible
the Vibrant and gallagherm1993 guys are right, but when you have flashed 2.2 it is safer to use the disable voodoo lag first (may not work cause you are saying it some hack version) but I d go that way first then flash the eugenes froyo that does not brick.... no repartition (do not check that box) reboot back to recovery then flash back to stock when going back to stock, you do check the repartition...from there, you can do anything you want
There is in the 1st page a thread that has a complete zip but not the froyo that does not brick you will need to get that from the bible sticky
good luck
http://www.youtube.com/watch?v=uGMDycXJ2i0
wolf3142 said:
im sorry if i placed this thread in the wrong place, im kind of new here. Guys, i really appreciate the help! can someone point in the direction of how to use odin? I have literally no idea what it even looks like or how to install it.
Click to expand...
Click to collapse
hey wolf...look up a couple posts, i'm putting all the files you need there.
The only way to fix this is to use odin. Are you familiar with odin? You better be! Since you played with VooDoo without really knowing what you got yourself into, you need to do this.
You will lose all of your data!
First ODIN Eugenes froyo that doesnt brick. Search for it here on xda. Get used to using the search feature. Then after that you can odin back to jfd and work from there. If you read enough, there are ways to work through this. Good luck and if you still dont get it, PM me.
what is the point of eugenes froyo that doesn't brick?
jdkackley said:
The only way to fix this is to use odin. Are you familiar with odin? You better be! Since you played with VooDoo without really knowing what you got yourself into, you need to do this.
You will lose all of your data!
First ODIN Eugenes froyo that doesnt brick. Search for it here on xda. Get used to using the search feature. Then after that you can odin back to jfd and work from there. If you read enough, there are ways to work through this. Good luck and if you still dont get it, PM me.
Click to expand...
Click to collapse
Why does he need "eugenes froyo that doesn't brick" ???
I was Running Axura 2.0.5, and used ODIN today to go straight to stock JFD.
Then I flashed the leaked JK6 froyo.
what is the point of "eugenes froyo that doesn't brick" ?
if you flash a rom without disabling voodoo, the partition stays as ext4 eugene's froyo that does not brick reformats that partition. JFD doesnt work the same way.
Follow this guide, if it doesnt work look at the other tutorials in the BIBLE section in Development.
Follow exactly no skipping steps.
http://forum.xda-developers.com/showthread.php?t=799105
byt3b0mb said:
if you flash a rom without disabling voodoo, the partition stays as ext4 eugene's froyo that does not brick reformats that partition. JFD doesnt work the same way.
Click to expand...
Click to collapse
Ohhh I get it. So people who f*cked up their partition or messed around with a lagfix, should use eugenes froyo that doesn't brick first. BTW eugene seems to have pulled everything off xda, I can't find that in the search.
Your phone is totally dead... give you $20 for it.
I'm all for lending a helping hand, and it's clear that all the relevant information has already been posted, but it still amazes me how often people will attempt to modify their device without doing their homework first and then freak out when things go awry.
I know I've f-ed up my phones plenty of times either by bad builds or not paying attention to details, but I've never thought the best fix would be to start a new thread on a forum under the assumption that I'm the first to have this problem or to avoid having to search for a resolution.
We all start somewhere and are always learning as we experiment with new tricks, but jeebus cripes people, why would you install something risky without having a backup plan in case something goes wrong?
Ah well, whatever. Sorry for a useless response.
SamsungVibrant said:
Ohhh I get it. So people who f*cked up their partition or messed around with a lagfix, should use eugenes froyo that doesn't brick first. BTW eugene seems to have pulled everything off xda, I can't find that in the search.
Click to expand...
Click to collapse
if you need eugene's stuff go to his forum located here
Froyo that doesn't brick is under vibrant android development.

Touchwiz Update bricked my non-rooted Tab (static lines across screen)!

I decided to go ahead with the TW firmware upgrade. Everything seemed to be going fine until I tried to install it and it told me there was an error and I needed to hook it up to Kies first. I had already been using Kies with it on my Macbook for a couple weeks now so I went ahead and plugged it in. Kies recognized it as usual and all the information came up.
So I went on and tried to install again and it said it needed to reboot.
It reboots and comes to the Samsung Galaxy Tab 10.1 screen like normal (right before it starts the galaxy animation). Next thing I know it comes to a screen that looks like the attached images! I immediately unplugged it from Kies and shut it down. Every time I start it back up it does the same thing. I honestly have NO idea what to do. I can't even return it as it's past the 14 day period and I (stupidly) didn't buy Staples' bogus $160 insurance.
I was not rooted before. This was a stock tab that I bought at staples. It had the firmware 4.24 when I bought it, I think.
Please, any help is appreciated. I tried doing firmware recovery in Kies but the pop up comes up in Korean and I have no idea what it says...
Edit: More info. I'm not the only one with this problem. Two other people have posted on AndroidPolice about this. http://www.androidpolice.com/2011/08/04/samsung-galaxy-tab-10-1-wifi-touchwiz-ux-update-is-now-live/
The software is definitely running underneath all that mess but it's literally impossible to see what is going or to touch anything.
I guess this thread is about the same issue
http://forum.xda-developers.com/showthread.php?t=1203610
Thanks, I'm checking the thread out now. I probably should have searched more than just Google before posting but I freaked out when it happened.
No need to freak out . we have xda and dev to solve all our problems
i have exactly the same problem as you... what should i do now?
I get the same screen but after rebooting! pfft it's making me really sad :\
I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\
And now I did a wipe and the stripes are gone, but the screen is black instead :\ still not working. Please help me!
Are you sure you didnt sit on it?
Amal Kadi said:
I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\
Click to expand...
Click to collapse
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM
tonyurquiza said:
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM
Click to expand...
Click to collapse
So I need to follow all the steps for rooting except the last one which is the actual rooting? Great thanx! Do I need to use Kies? My current computer is Mac but I guess I need to download those things to a Windows machine to make it work, right?
Thank you very much
I had the same problem. I upgraded the update on my non-rooted tablet and got the funked up video mess. Per instructions from Samsung support, I hard booted to the recovery menu (power+vol down, then power up, down on download screen) and did the factory wipe. After that I ended up with the black screen. I could tell things were working in the back but couldnt see a thing. I figured I would throw it on the Kies and it saw that there was a factory upgrade so I let the Kies run through it and it works fine now.
Dont know if this will help w/other but it worked for me.

[SOLVED] Vibrant Root Concerns

Hey there. I rooted my Vibrant successfully, but realized I left some important things out. I used this guide to root my Vibrant: http://forum.xda-developers.com/showthread.php?t=723479
The problems:
1) I can't nandroid (not that I need to, I only have 4 apps)
2) I would like to install either Miui v4 or CyanogenMod 9 but cannot as my recovery screen does not show me the options to do so (I only get the 4 options you normally would get unrooted, such as "Reinstall Packages"), so I'm stuck with the lame default homescreen.
3) I'm currently on 2.1-update1; should I upgrade to 2.2? If so, must I unroot to upgrade, and then reroot? And if this were the case, how do you unroot, and can I reroot using the same method in the link above?
Also, I was looking at this guide: http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery
and noticed the line "This guide assumes the Samsung Vibrant already has Android 2.2 build UVKB5 already installed on it."
Does this mean 2.2 is required to install the CWM Recovery?
Thank you.
I'm not sure how you don't have CWM recovery if you followed the guide as it is written. Maybe its because the 2.1 is updated? I would do the following and see if that's all it takes. You definitely don't want to update to stock 2.2 via Kies or anything of that nature.
Worst case scenario, we can have you Odin back to stock JFD. You'll be smooth sailing from there.
Search the forums and find the update.zip for CWM for our Vibrant.
Put that on the lowest level of your INTERNAL storage. Not your microsd card. For example f:\update.zip
Now go to your boring 4 option stock recovery and select reinstall packages. It will reboot to the same boring screen. Select reinstall packages again, and it will reboot into Clockwork Mod Recovery.
Let me know if that does anything for you. Also what version of stock recovery do you have?
Toast6977 said:
Search the forums and find the update.zip for CWM for our Vibrant.
Click to expand...
Click to collapse
Can pull that directly from my signature, if OP wants. (Only works on Eclair [JFD] build btw)
Also OP, You will have to have a ROM that you are going to want to flash saved on your Internal SD card. Jsut download it, put in a folder and follow the ROM OP's instructions. Since you are fresh and new, I would NOT suggest flashing anything of ICS or JB until you get the hang of things first.
Read, read and then read somemore. When it comes time to flash ICS or beyond, there is a guide in my signature. Good luck and make sure to hit Toast's "Thanks" button. He is a good asset to have around here.
Wow! I was hesitant to even check today, let it alone this early! Did not think that I would have two very useful replies waiting for me. Thanks guys, much appreciated!
I'll try the Odin thing out first before I even try to flash (you need root first before flashing, I'm assuming). Just out of curiosity, what is JFD and Odin? I'm still gonna try it out using the guides found here, but just curious.
EDIT: Damn, it worked like a charm! Now I have CWM. The mistake I made was that I only installed the Superuser/ROOT and not both. Gonna play with it for a bit now
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Toast6977 said:
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Click to expand...
Click to collapse
Thank you for teaching me the etiquette around here as well

[Q] How to restore stock recovery?

I thought the GPS issue I was having was app related as it seemed to smooth out but it's once again popped up and I need to return this sad S4.
I've searched and read the threads and have only found how to unroot the phone not restore the stock recovery. Am I missing something simple like "duh, just remove twrp"?
As always your guys help is appreciated!
thepktrckt said:
I thought the GPS issue I was having was app related as it seemed to smooth out but it's once again popped up and I need to return this sad S4.
I've searched and read the threads and have only found how to unroot the phone not restore the stock recovery. Am I missing something simple like "duh, just remove twrp"?
As always your guys help is appreciated!
Click to expand...
Click to collapse
Flash the stock firmware through ODIN and then do a factory reset.
Or you can use Kies to do an emergency firmware restore, but it doesn't seem to be an option for every one. You can use the "search" function to help answer any questions you have about either method.
Thanks!...I'll give them a shot later today.

[Q] S4 stuck on Downloading mode..pls help

Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo
shpack said:
Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo
Click to expand...
Click to collapse
You need to properly install the correct drivers on your PC. There should be no reason that ODIN doesn't see your phone if they are installed correctly. A quick search of the forums should get you the proper drivers to install. You can also try Kies emergency recovery, but it is hit and miss. Good luck.
+1 if you can get into download you can Odin. Use the usb ports in the back of the pc. You might have to use a different computer also. For the life of me I can't get Odin on my pc to recognize the device but I have no problem with my laptop.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?
TheAxman said:
Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?
Click to expand...
Click to collapse
That's the thing, these exact same types of threads just keep rolling through one after the other...people don't search and they don't read. That's the reason they are in the situation they are in to begin with and it seems they just don't learn.
Fortunately, the AT&T S4 forum has come far enough along that the sticky threads and the threads like your guide can be linked for these people to put a little time into finding a solution for themselves. Most of them don't like it (they want it done for them), but if it is all they get, they will finally have to do something the right way on their own.
Actually, a few people are thankful for being pointed in the right direction, but most are still pissed because it means they have to do what they should have done in the first place...follow XDA rules, use the search function, and read. If you don't do everything for them and hand it to them on a plate they call you names and say you are a ****, unhelpful, etc... I just laugh about it because it becomes clear why their phone is F'ed up in the first place. The thing is, sometimes you just can't help people. Just every now and then, someone comes along that needs help and is willing to do things the right way.
You can NOT have kies drivers and samsung drivers loading at the same time, I do not use kies at all, and my pc has NEVER gave me a issue yet using odin, including in my G3 days. uninstall that worthless kies and proceed. If you have to use kies, load it as needed then remove it.
And as always with the lovely microsoft windows, after you un-install anything you have to reboot, for it to work properly.
Linux is my BUD!

Categories

Resources