yashsingh1/xdaforums huggingface dataset:
[Vibrant General] i900:
I had the update with OCLF installed and it worked fine until I decided "accidentally" (very very regretful now) to install Voodoo from the OCLF app. Then the phone went into a soft reset and got stuck at the Vibrant screen.

Since then I've tried to select "install packages" or "reboot system" options in the recovery mode, but it showed only a partial progress bar at the bottom, then it got stuck at the Vibrant screen.

I gave Odin a try but the app does not see any com port after use ADB reboot or recovery commands.

Btw I did NOT select USB debugging mode before installing voodoo. I did install the USB driver for the Vibrant but am not sure it even works because the Odin app did not see any com port.

Any help is appreciated! I don't want to loose data and files in the internal storage. This is kinda urgent because I need to use phone.
[Vibrant General] quest4fire:
The same thing happened to me. I even posted it yesterday to warn people to be careful with RYANZA Voodoo and I got flamed and insulted. Basically you fried your kernel. I tried different things and what worked for me was ODIN the JI6 back. Go to Vibrant Directory Bible under Samsung Vibrant--Android Development and find that thread. Go to the ODIN section and download the JI6 package. You will need to get into 'Download" mode on your Vibrant for ODIN to work. You need to have the phone plugged into computer via USB, hold down both volume buttons and the power button at the same time. When the screen becomes black, release only the power button and download mode will pop up. Then bring up ODIN and make sure the yellow com message pops up. With ODIN it will work right away (like 2 minutes). If you see it hanging then you need to try it again. When you get your phone back up you need to disable voodoo. Good luck. Know that the Vibrant is almost impossible to kill, you will be able to bring the phone back to life.

here's the link: http://xdaforums.com/showthread.php?t=771111

instructions here: http://forum.cyanogenmod.com/topic/...r-vibrant-and-return-to-stock-phone-pc-error/
[Vibrant General] rgoyena:
I tried flashing it using odin but the phone would start, show the tmobile thingy and just turns off. Is there any way around this?
[Vibrant General] i900:
Thank you for your prompt reply

I'll give it a try later. Is there a good link to download the USB driver? I did but am not sure it will work with Odin. I also forgot to release the pwr button only when the Vibrant screen came on. You said release it at the black screen.
[Vibrant General] krackers:
Theres voodoo on the oclf app? Where do you download it? When I downloaded it from the market it wasn't there. Do I need to install a supported kernel before it shows up?
[Vibrant General] i900:
Another thing is the phone is not in USB debugging mode before. Is this needed for Odin to work?
[Vibrant General] i900:
It is in OCLF app

I don't remember exactly how it looks but the app has like 3 tabs: 2nd is available, 3rd unavailable or vice versa, 1st is probably the voodoo one. BE CAREFUL, read the kernel instruction first! I am sure they are not compatible. It should be disabled one or the other so users wouldn't get hacked:mad:.
[Vibrant General] i900:
ok the 3 button procedure got the phone into Recovery mode like this screen with yellow text:

--------------------------------------

Android system recovery <2e>

reboot system now

reinstall packages

--Appling Multi-CSC

Installing Multi-CSC

------------------------------------

Selecting either "reboot system now" or "reinstall packages" gives this screen:

----------------------------------------

Installing from sd card completed

rebooting..

Phone reset done

-----------------------------------------

The phone now got stuck at the Vibrant screen!

How to get into the download mode?
[Vibrant General] i900:
Holding vols up down with battery in and then plug in the USB cable, the Downloading screen came up with the digging icon and a message "do not turn off target" but it just got stuck there. I typed in the adb reboot download under the folder containing the adb files but it said "error no device found". I installed both drivers, one from Samsung site and one x86 from Softpedia site. Is it time to get a new one?
[Vibrant General] AustinKnight45:
Try this.

Click HERE FOR ODIN 1.30

Samsung USB Drivers MS Windows 64bit HERE 32bit drivers HERE pick the drivers that work with your pc I have windows 7 so I use 64bit.

Step 1. Download the 512 PIT file HERE this file needs to be un rared with Winrar its a free program its HERE.

Step 2. Download the T959UVJFD.tar HERE

Step 3. Get your phone in download mode try just holding the volume up and down at the same time then plug the usb in, you might have to pull the battery and then put it back in the phone then hold volume up and down at the same time then plug the usb in it should go into download mode.

Step 4. Open Odin 1.30.

Step 5. Load the 512 PIT file you extracted with winrar into Odin 1.30 PIT section of Odin

Step 6. Load the T959UVJFD.tar you downloaded into Odin 1.30 into the PDA section of Odin.

Step 7. Click the Star button in Odin.

Step 8. Let it do its thing.

Step 9. Thank me

Step 10. Hope this helped it really doesn't get much easier then what Ive given you in this list.
[Vibrant General] i900:
Will the pit file WIPE the data (photo..)?

Somewhere in the forum said that selecting the pit file will wipe all data. Is that true because I so want to keep EVERYTHING intact! Just got back from a short vacation in Waikiki:D

I got the PC to see the Vibrant now with Odin but I downloaded the newer tar file T959UVJI6 (2.1 updated ver) but can not see it from selecting PDA button, it can only see the old T959UVD (stock 2.1). I am at the no point of return now so within 15mins if there is no answer then I must get going.

Thanks again!
[Vibrant General] i900:
Never mind guys! my bad did not unrar the tar file..going to download it now..wish me best of luck!
[Vibrant General] i900:
ok downloading now... it is a nerve wrecking experience comparing to WM6.1 custom rom flash which was very smooth going. I still miss the original i900 Omnia. I am going to be late for the church but God please forgive me! Oh it passed the downloading and got the S logo..
[Vibrant General] i900:
it booted up but stuck at black screen with all soft keys lighted up, tried the install packages in recovery mode again..
[Vibrant General] i900:
I guess I need to download the pit file? Will this wipe out all data?
[Vibrant General] krackers:
I don't have voodoo... where did you get your oclf app from? Is it not showing because I have stock JI6 kernel?
[Vibrant General] AustinKnight45:
Did you follow my to-do list to the T?

this might help

you need to flash this PDA file with odin EUGENE373_SamsungS_Froyo_PDA along with the PIT 512 you should still have from the unbrick instruction odin forum then after you flash those files you need to let it do its thing it will prob take you to recovery just long press the power button and when it turns off put the usb back in the phone to get it into Download mode(just get back into download mode any way you know how) and then follow those instructions you did earlier with the unbrick instructions forum just flash the Eugene373 SamsungS Froyo PDA file first then after you flash it get right back into download mode and flash stock vibrant rom through odin.
[Vibrant General] mikeyinid:
Odin in eugenes froyo that doesnt brick.Make sure you use the 513 pit file that comes with it. When its done, pull the battery and odin the jfd. Use the 512 pit file with jfd. Check the repartition box for this one. You will be back to stock and all the lag fixes will be gone. This process works to save your vibrant from ALMOST everything :D

^^^oops, didnt make it to your post...just tryin to help
[Vibrant General] i900:
OCLF from the market by Ryan

But use it with extreme CAUTION at your own risk. Don't brick it like mine:p
[Vibrant General] i900:
Again guys thanks for your time and help but just one more time, I am still a bit confused, can you list exactly what files to download in order to get the phone back alive without loosing any data and files?

Download 512 or 513 pit first? Do it together with the tar file (check both boxes in Odin)? I understand 512 pit go with JFD (stock 2.1 rom before the update). How about the latter one? It goes with JI6? Now I got only the JI6 in the phone without the pit file. Should I download 512 with JFD first then do the latter one with JI6, and all data still remain intact?
[Vibrant General] i900:
Found this that said "uncheck" pit select to save all data

http://forum.cyanogenmod.com/topic/...r-vibrant-and-return-to-stock-phone-pc-error/
[Vibrant General] i900:
Why flash Eugene rom with 512 first? Then what is the stock rom? Are they the JFD (2.1 before update) and the JI6 (the 2.1 update)? Why can I just flash the JFD first? Will this wipe the data?

After downloading Eugene with 512, and the sd/sim cards removed, the recovery screen said "E:copy_dbdata_media:Can't mount SDCARD" in red and "your storage not prepared yet, please use UI menu for format and reboot action" in yellow, and "copy default media content failed" in red. Selecting either reboot system or install update.zip with power button did not do anything.

Tried it again with the sd card inserted and the same error messages came?!?

Any ideas?
[Vibrant General] i900:
Good news is the phone now alive. Bad news saved data gone. End of the sad story, damn you Ryan with the voodoo crap
[Vibrant General] AustinKnight45:
Happy to see that you fixed it
[Vibrant General] quest4fire:
Glad to see you fixed it, I told that Vibrant is almost impossible to kill. Always back up data before trying new things like voodoo, new roms, etc. Also Google "Android commander" and download it to back up apps and data.
[Vibrant General] i900:
Thanks for your support. I use Titanium free ver and it seems to do its job but is it better than Android cmdr? I prefer quality over quantity for the market which should be completely over hauled big time to screen out redundant and crappy apps.
[Vibrant General] jrizk07:
You were warned about dragons in every walkthrough about voodoo. Looks like they won.

on a side note Ryan's OCLF is not voodoo, not quite sure why people get these confused.
[Vibrant General] Chalup:
What's that verse in Matthew about having a personal relationship with God and not having to go to church... ?

Anyways, good luck. As a word of advice backup everything before you mess with the phone.
[Vibrant General] super g:
because there's a voodoo kernel flash function within OCLF. on the main page hit the menu button on your phone, pull up the kernel tab and it gives you options for kernels available to your phone.

i was curious about using their voodoo kernel thing-a-majig...now i'm convinced it's a bad idea. is there ANYBODY who has used this option successfully??????
[Vibrant General] kwag:
I screwed up my Vibrant with the voodoo crapola. The option in OCLF kernel menu.

And to make things worse, it seems I now have a bad USB on the phone, because even though I managed to get to Download mode, the device is not recognized. Tried three different cables.

The Samsung USB drivers are installed correctly. As a matter of fact, tried on a second PC too! Both Windows XP.

On my Arch Linux machine, a "dmesg" reads:

ehci_hcd 0000:00:1d.7: port 3 reset error -110

hub 1-0:1.0: hub_port_status failed (err = -32)

hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?

hub 1-0:1.0: unable to enumerate USB device on port 3

hub 3-0:1.0: unable to enumerate USB device on port 1

etc, etc, etc...

So I believe now I have a "Solid Brick" :D

If anyone has been able to recover from something like this, please share it!

Cheers,

-Karl
[Vibrant General] bricked vibrant:
cannot unbrick with Odin after VooDoo

ok guys, i have unbricked my vibrant before after the OTA update about 5 weeks ago. i am pretty new at this smart phone stuff, but was pleasantly surprised i was able to get odin to fix the brick. about an hour ago i launched the stupid VooDoo in the OCLF app and the phone now will go as far as the animated galaxy "S", then go blank. i attempted the Odin flash about 5 times now with the same result each time, just boots up past the vibrant screen to galaxy S then goes blank. when the phone restarts or reboots after the odin flash a message in red reads DATA WIPE FAILED between a few yellow text lines. when i try to reinstall packages through boot screen i get the same message i got after the OTA brick, E:Can't open /sdcard/update.zip now the phone was rooted with the OCLF before i launched VooDoo. can somebody help me out?!?
[Vibrant General] chalz:
Alright, I loathe responding to these types of threads, as I know it always comes off as a "Help! I'm a drowning noob!" but I really have no choice left. (Aside from attempting to become comfortable with a $600 paperweight)

My problem arose after attempt to revert to my backup after installing Obsidian. It went smoothly until the reboot, and now no matter what I do I get stuck at the Android System recovery, and the finall message is always:

--Appling Muti-CDC...
Installing Muti-CSC

I've attempted to revert to my backup multiple times and it always get stuck at this screen when it goes to reboot. I attempted to reinstall Obsidian and it always takes me back to the same screen.

Most recently, I've done exactly what has been suggested in this thread (and many others) by using Odin3 to install JI6.

I followed the instructions perfectly multiple times. At the end of the flash it goes to reset, states a "Pass!" The phone reboots and loads a few things, then reboots a second time and always takes me to this screen:

-- Movie_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation

-- Movi_check already executed!!...

-- movie_checking done!...
update media. please wait
update media. finished
# MANUAL MODE #

-- Appling Muti-CSC...
Installing Muti-CSC...

I don't know if this even makes sense, but it seems like it keeps forcing itself into manual mode, regardless of what I do...and I'm at a loss.

Does anyone have any ideas? I've seen a few people post up similar problems, but it seems the issue has stumped a lot of people who would normally respond.
[Vibrant General] chalz:
I should also add that I know the "Eugene's Froyo that does not brick" rom can be used in place of the standard JI6 rom for this problem, but it seems that rom is no longer supported, and I cannot find a download for it.

EDIT: And I figured out the problem here...it doesn't look like I correctly disabled the lag fix. Fffffffff...
[Vibrant General] chalz:
Got it back. The "Original" TAR file in the "All In One" package was the ticket. (For those who are looking for a replacement to Eugene's file, this will work)
[Galaxy S I9000 Q&A, Help & Troubleshooting] vferriag:
When shooting with the camera when you reach the stop key accidentally shooting back without saving what you shot

Can anything be done about it? I guess that is a bug that did not thought this is a drawback if the shooting.
[Desire HD General] Kelthizar:
Hi,

ive read that when u remove system Apps u cant use the OTA-Updater anymore.

Does anyone have the RUU_O2-germany Rom that I can reinstall the Rom cause I really want to use this option.

Dont want to unroot my DHD just now.

Thx in advance
[Desire HD General] Joshua03:
You can use this one.

http://xdaforums.com/showthread.php?t=809746

The 1.32.207.1 ROM is the latest at the time.
[Desire HD General] Kelthizar:
Thx and sorry for asking.

Stupid me, didnt check the other pages... :D
[Desire HD General] NeoS:
Solution found.

Message to the OP: Please ask these questions in the General forum in the future.

Thank you.

Moving this to general.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vladikox:
Hi,

I'm using a Tmous HD2, Energy for WM, shubcraft 1.5 for Android.

G-sensor worked fine in both OS, until one day I got stuck with the rain without the raincoat and my HD2 was wet a little bit. I dried it for one night. Everything still works ok but the G-sensor in Android.

I checked it again in WM. There's no problem with G-sensor (I can play games with it or rotate the pictures in gallery tab), but when I turned back to Android the problem still there so I assumed that it should be software's trouble. I booted again into WM, tried to do the callibration, turned on and off the G-sensor. Android's g-sensor kept not working. Home screen (Launcher Pro), browser, games, etc. can't use it either.

After that I downloaded another ROM of Android (JDMS 1.5), erased the old one, hard reset WM's ROM, installed JDMS 1.5: it didn't work as well.

What I haven't tried yet is trying another WM's ROM or re-installing Hard SPL.

So what do I need to do now?!
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vladikox:
Can any one help me?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vladikox:
already reinstalled HSPL 3, nothing happened.
[HD2 Android Q&A, Help & Troubleshooting and Genera] jmmmmm:
Did you try having Android build a new data.img just to test default settings?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vladikox:
I have deleted all of Android's files in SD card, then copy the original one --> problem not solved.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RenaissanceMan:
I am having the exact same problem. The G-sensor works in WinMo but not Android. I've tried re-formatting the SD card and doing a fresh Android install.

Were you ever able to find a solution or does anyone else have any other ideas of things to try?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vladikox:
My problem has been solved few weeks ago.

At that time I was going to lose hope and came to a decision of giving up trying and willing to say good bye to Android's g-sensor. I turned off the auto-rotate in Android for (about) a week. One early morning waked up, turned it on again and a wonderful thing happened: it was in land-scape mode.

In next few days the sensor was not working so well (but at least it worked). Now it run smoothly and I don't get trouble with it anymore.

Wish you can fix it successfully!
[HD2 Android Q&A, Help & Troubleshooting and Genera] pvdw50:
I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.

In winmo it's working great though.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RenaissanceMan:
Yeah, I don't get any variables in sensordebug either.

Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.

As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.

I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?
[HD2 Android Q&A, Help & Troubleshooting and Genera] AvRS:
I've also got this issue after installing a new kernel and no matter what combination I use now it won't work again. I've tried all of my previous working combinations and none of them have fixed this, I've tried turning off auto-rotate and on again but again nothing happens. This is pretty useless if it's stopping on multiple people for no reason.

Anyone know the script in g-script lite to enable and disable the g-sensor to see if this works as I've used this in the past on one of darkstone's builds but don't have the script anymore?

Thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] pvdw50:
I'm using Sergio's core droid V0.8 desire wich is very stable and the camera is working, but I tried many others and I never had any BSOD's.

Can anyone tell us where the G-sensor hardware is located in the HD2? there should be a logical explanation to this problem.
[HD2 Android Q&A, Help & Troubleshooting and Genera] AvRS:
Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RenaissanceMan:
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.

Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.
[HD2 Android Q&A, Help & Troubleshooting and Genera] AvRS:
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.

Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.

Hope this helps.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RenaissanceMan:
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.

Where does that file come from/where can I get it?

thanks for the help!
[HD2 Android Q&A, Help & Troubleshooting and Genera] pvdw50:
Up .......
[HD2 Android Q&A, Help & Troubleshooting and Genera] AvRS:
I've never seen any files called that on my device so what I'd try is first make a backup of that file then rename it to sensors.qsd8k.so and then restart. All of my files in that folder are all .qsd8k. With some builds/kernels they name things differently and say to rename according to your device for example when you get lights.htcleo.so which you need to rename to lights.qsd8k.so to make it work. If this doesn't work definitely try a different build to see if it's working in that and if it is try going back to your one you're on now and maybe it'll wake it up again.
[HD2 Android Q&A, Help & Troubleshooting and Genera] pawlish:
Hi, I have same problem with sensors on my HTC HD2.

A downloaded Sensor Test app from Marketplace and it give me this values:

Accelerometer (BMA150)

Accel X Waiting... M/S

Accel Y Waiting... M/S

Accel Z Waiting... M/S

Magnetic Field (AK8973)

Mag X Waiting... Deg

Mag Y Waiting... Deg

Mag Z Waiting... Deg

Orientation (AK8973)

Az Waiting... Deg

Pitch Waiting... Deg

Roll Waiting... Deg

Proximity (CM3602)

Near/Far Waiting... Prox

Light (CM3602)

Light Waiting... Lux

Battery

Charge 94 %

Temp 35 Deg

Voltage 4.1 V

It looks like a problem with some communication bus or something like that. Can someone try Sensor Test app and check values.

All of these sensors are not working and I dont know how to fix them

Last edited by pawlish; Today at 02:57 PM..
[HD2 Android Q&A, Help & Troubleshooting and Genera] johnnyham89:
I'm in the same boat as yall. Sensor works in WM 6.5 and even Windows Phone 7, but still no Android. I have also noticed that the proximity sensor isn't working as well. Do yall think the 2 might be related?
[HD2 Android Q&A, Help & Troubleshooting and Genera] crackster:
Ok i can get wifi on it and download stuff. but when i disable wifi and try to just use the internet it wont connect to any thing.. any ideas? thanks