yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] puneet_champ:
Hi,

I was trying the Gingerbread CynogenMod 7 and I think i have bricked my captivate. It does not start .. Any help is appreciated..

This is what i did:

I followed these steps :

Download the initial package: cm7-captivate-initial-package-XXXXXXXX-XX.zip (link below)

Extract it

Copy following files to your internal sdcard

- captivate-efsbackup.zip

- cm7-captivate-initial-XXXXXXXX-XX.zip

- cm7-captivate-radio-XXX.zip (pick the one you want, I use JK4)

Flash a Kernel that contains Clockworkmod recovery 2.X or 3.X using odin (e.g. I had http://xdaforums.com/showthread.php?t=914284 )

!! Don't use "reboot recovery" command or other shiny things to do the step below !!

Reboot into recovery using 3-button-combo and apply captivate-efsbackup.zip.

Flash cm7-captivate-initial-kernel.tar as pda using odin without auto-reboot

Reboot into recovery using 3-button-combo

Choose "mounts & storage" and format system, data, cache

Apply zip from sdcard: cm7-captivate-initial-XXXXXXXX-XX.zip

Do a wipe!

Apply zip from sdcard: cm7-captivate-radio-XXX.zip

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

All this while it gave me an error : E: no misc partition found..

Then next step was to Copy Gapps to your internal sdcard and apply zip (link below)

Then i realised i forgot to copy this zip .. I was stuck.. So decided to revert back .. Restored the Nandroid partition which i had done earlier.. This was a Froyo Nandroid! Obviously it failed and now the phone is bricked!!!!!!!!!!

This is the first time i hve bricked my phone and I am freaking out! PLease help!
[Captivate Q&A, Help & Troubleshooting] JRd1st:
You could start by reading one of the 5000000 other threads just like this one.

I'm not trying to get on your case specifically, but there's only a few answers to this problem and I don't understand the need for a new thread every time.

Good luck :)
[Captivate Q&A, Help & Troubleshooting] crystalhand:
Not sure why you extracted the zip file you can just flash that through clockwork. Try getting into download mode with the 3 button method to flash back to stock with odin

Ya never restore a nandroid backup if you are not on the exact same rom and version as the backup
[Galaxy Tab General] silvatyrant:
I was wondering if anyone else is experiencing what I am w.r.t. videos freezing on the Tab.

I've got a couple of videos ripped from the web (HD - 720p & 1080p) in mp4 format. Sometimes when I watch them either using RockPlayer or the OEM player I get sound but frozen video from some older video that I've played. No matter what video I play, I see the same image, but the sound is from the file which I'm currently trying to watch.

A soft reset seems to sort out the issue. But any ideas as to why this is happening? And what I could do to sort it out (besides rebooting)?

P.S. I notice that when I turn off hardware decoding in RockPlayer the videos play, but obviously due to the fact that they don't have dedicated VPU power they stutter and play in slow-mo. Will try with an SD file and edit this post with my findings. Still...Will be interesting to see if anyone else is experiencing the same shizznit.
[Galaxy Tab General] omer04:
I have got the same problem and believe me we are not the only people who has the same problem! its a bug that most the galaxy tab has it! the only solition is soft reset!
[Xoom General] Morkai Almandragon:
Does it exist on tis tab?

how about on

http://www.sierrawireless.com/Newsr...Wireless_4G_LTE_Mobile_Broadband_Network.aspx

which may be the card going in the xoom?

Lastly if the hardware exists on an lte device, should it be possible to make calls work by switching the sim card with a lte phone sim?
[Xoom General] youngproguru:
I think that if you would like to place phone calls with your Xoom using the cell radio its possible to find a way. Verizon might not be happy with it.

However, Its the hard way to place calls.

Sigh up with a VoIP provider, and use a SIP Client.

I like a provider named Vitelity. You can port your number to them if you would like. They are very inexpensive, and very reliable. (or use Skype, or anyone else.)

Then, use a SIP dialer and a Bluetooth headset on your Xoom. I am doing just that using Verizon 3g and it works great.
[Xoom General] Morkai Almandragon:
I have signed up for skype and have a number, but skype seems to have no interest in real BT support, neither does Google. If I could force Skype to use the mic on a BT< I could likely live with it, but AFAIK that is not possible.
[Xoom General] youngproguru:
This all be in another forum, however I am using CSIPSimple and it supports my plantronic BT voyager 510, (on Honeycomb)

http://www.plantronics.com/us/product/voyager-510&skuId=sku4610016

And, CSIPSimple opens the default Android Dialer (Which is in Honeycomb) to send and receive calls.
[Xoom General] Morkai Almandragon:
Would you mind testing it to be sure?

If so, place a call, leave your pad and walk like 15 feet and see if you are still heard.

Please don't be offended, I have just had WAY to many people say the same thing as you, only to find out A2DP let them hear, and they were using the tab mic without knowing it.
[Xoom General] youngproguru:
Hmmm.. I will check later tonight. That is a good question.
[Xoom General] Morkai Almandragon:
Thanks young... anyone else use csip too?
[Xoom General] ernie one:
The hardware is capable, the problem is with the provisioning. Verizon adds feature codes to block voice and SMS on their tablet data plans.
[Xoom General] Morkai Almandragon:
what stops us from switching sims later to make our tablets look like a phone?
[Xoom General] bwcorvus:
There is no sim to switch.
[Xoom General] funkatiko:
So then? Any tablet outside of the us ( or Verizon) is able

To standard phonecalls?

I'm in the uk and I was planning to buy the 3g version but if I still have to carry a phone to txt or call, i'll choose the WiFi one, save 200 bucks, and tether with my nexus when needed although I'm not very happy with the idea of carrying multiple devices...

Btw , 3g version has been priced in.....600 pounds! What are they playing at? If I finally choose wifionly I'll buy for sure in the US, screw carphone and pcworld..
[Xoom General] youngproguru:
I think you are asking a question that no one can answer at the moment.

LTE does use a SIM card, but, NO devices are currently available on Verizon's LTE network yet, so no one knows what happens if you switch LTE SIM cards between devices.

I also think that LTE devices use a VoIP type of voice connection, something different then how voice is done on CDMA. This new type of connection allows data and Voice to operate at the same time. This functionality, this Software dialer stack would need to be included in Honeycomb, which is not a phone Android distribution.
[Xoom General] Morkai Almandragon:
Young dud you test the bluetooth mic with csip?
[Xoom General] youngproguru:
Yes. I I have found is that I do have two way audio, all on the Bluetooth headset using csip, I walked around my house, leaving the Xoom several rooms away.

While in WiFi, Bluetooth audio was sketchy at best. For most calls, I could not get the headset in engage for the call. While in the call I would press Bluetooth on the dialer, and nothing would happen, or the audio would cut in and out, before engaging, or a few times I would have to press 'Speaker", then Bluetooth, then Speaker again before it would engage. When it would engage in WiFi I did have two way audio.

While in 3G, with WiFi Off, the connection with Bluetooth was perfect every time. No issues. The call call quality overall was a bit less then with WiFi, however Bluetooth worked correctly.

UPDATE: I just had a bad Bluetooth connection issue on 3G. So, it is spotty. It might be because CSip uses the default Android dialer which might be incomplete in some way on Honeycomb.

I should try another SIP app. But Bluetooth does have two way audio when I can get it to connect.
[Desire General] cardiak:
Hi,

Sometimes my gallery thumbnails kinda merge into half of one another. IE for one thumb, its made up of 2 pictures that seem to overlay one another. Its no biggy but annoying, does anyone know what I mean or know of a fix I can do?

Thanks for your time.
[Desire General] th3:
Heh. So do mine in both the 2D and 3D on CM7 RC1. I haven't found a fix yet...

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

- Sent via HTC Desire -
[Desire General] dgrouch:
It's probably your microsd card. Those things only happened to me wayyy back in my SE k800i with class A microsd. If it doesn't happen to the photos stored in your internal mem, it's probably the corrupted microsd.
[Android Software Development] KruseLudsMobile:
I use verizon droid x, have a stock rom, and want to use my device as a router for my notebook. Verizon haas a solution but they charge for it. I can't find an app on the android market for this. Anybody know of an app that can connect free?
[Android Software Development] 3rdstring:
Wireless Tether for Root Users
[Android Software Development] cmoney12051:
You are going to need to root to use the wireless tether. Or if you don't want to root you can use pdanet or easytether but they are not wireless. You have to plug your phone in with usb to the computer and use their computer programs to connect. If you choose to root so you can use wireless tether check out z4root.
[Adam General] bharadwajh:
I ordered an Adam and was wondering if all of you are using the same screen protector that comes with the Adam. Are there any that reduce reflections inside with backlight turned on?
[A7 General] JustJackie:
Elocity just out of box yesterday & first time shutting off last night woke up screen still frozen. What can i do because anxioius to use it. Need to get it up & running so buying wifi router & case any ideas? First time using wireless wifi connection so keep it basic please. Thanks
[A7 General] netstat_EVO:
if it seems locked up, holding the power button until it completely shuts off will do the trick (15 seconds I think)

Edit: or the reset switch (little pin hole on the back in the center of the shiny part) should do the same.
[Fascinate Android Development] gunnermike:
How to UnVoodoo

How to UnVoodoo

The key to uninstalling voodoo is Red CWM. To be specific you don’t uninstall voodoo, you disable the lag fix. Once that’s done you can flash a new non-voodoo kernel.

1. Boot into recovery. You should be in Red CWM.

2. Select “voodoo”.

3. Select “disable lag fix”.

4. Press soft menu button.

5. Select “reboot system now”

6. Wait.

7. Wait.

8. Wait.

9. Wait. Just like during the install, this will take 2-15 minutes, while its reformatting your internal SD card.

10. Your phone will then restart. At this point you still have a voodoo kernel, the lag fix has just been disabled. Red CWM is now broke. No biggie.

11. Re-flash Red CWM with Odin.

12. Reboot into recovery.

13. Flash non-voodoo kernel of your choice.

Note: If you are flashing from one voodoo kernel to another, you do not need to disable lag fix.

Just a couple notes to the first timers: (The credit for this clairifacation goes to GizmoDroid)

1.Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.

2.Currently, in the newest RED CWM, there are two enable options in the voodoo menu:

•"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition

•"/system lagfix" - this converts your "system" rfs partition to ext4

You will need to hit both of them for full optimization.

After selecting "enable lagfix", the text at the bottom will change to:

Code:

Voodoo lagfix is actually: disabled

next boot: enabled

Options:

/system lagfix conversion: yes

debug mode: no

Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.

Hopefully this will get fixed when a new version comes along.
[Fascinate Android Development] gunnermike:
OOPS!!!!

Trouble Shooting.

In order to trouble shoot i had to create some trouble to shoot. So i decided to break the rules.

Rule # 1. Dont panic. I started with rule number one because that seemed the logical place to start. However i had nothing to panic about, so i just looked silly. We wont talk about that.

Rule # 2. Dont flash a non voodoo kernel over a voodoo kernel without disableing the lag fix first. I got some results out of this. I bricked my phone. As I have done this 5000000000 times before, I still had no luck with rule number one. My phone how would no longer boot past the Samsung screen. so i rebooted into recovery, and got blue CWM. I tried to apply update.zip and got E:fail blah blah blah.

The reason for this is the filing system is still EXT4. A non voodoo kernel does not know how to talk EXT4, it only speaks RFS. In order to fix the brick we have to do the missing step, disable lag fix.

1. Put the phone in download mode and flash Red CWM.

2. Reboot into recovery. You should now have Red CWM.

3. Select "voodoo"

4. Select "disable lag fix"

5. When you return to the menu, press the menu soft button

6. Reboot. Again this will take 2-15 minutes as the filing system is converted from EXT4 to RFS.

Thats it. That is the only problem I could make happen related to voodoo. I am having a hard time believing its that easy, but it is.

It is often asked "How do I know if I have voodoo?" The simplest way is to run an app called Quadrent. Quadrent is a benchmark app. Scores above 1000 means you have voodoo. Quadrent is not the proper way to check. The more I think about this, the more I think you should learn the proper way. It will give you a greater understanding of what is going on with your phone.

The proper way is to use a terminal emulator and type "mount".

You will see this:

mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 rw,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc

the ext4 is what you are looking for. If you see RFS in any of the 4 locations you dont have voodoo or just one of the partitions has voodoo.
[Fascinate Android Development] Zacisblack:
Wow, good job spelling this out. I'm not on voodoo yet but when I feel I'm ready I'll be heading to this thread to make sure I don't screw anything up.
[Fascinate Android Development] gunnermike:
hope it helps. just ask if yuou have questions.
[Fascinate Android Development] onemotodroid:
You did a really GOOD JOB in spelling out voodoo / non voodoo.

Thanks
[Fascinate Android Development] Benew0:
I was under the impression that the new versions of Voodoo only had the lagfix for EB01 and DL30 because we didn't have a source kernel from Samsung for the Fascinate. I know I haven't been able to access voodoo sound yet and am really anticipating that feature, but if I'm behind or missing something that I can do to get that feature PLEASE let me know.
[Fascinate Android Development] gunnermike:
I made a note regaurding that. When I get to a computer I will make it bold.
[Fascinate Android Development] Nobody Important:
Whenever I boot the phone I get the electronic female voice telling me "Convert data partition: System not available. Convert system partition: System not available." What am I doing wrong?

Never mind. It wasn't working under SC 2.7.1, but after flashing to 2.8 it converted and seems to be working.
[Fascinate Android Development] GizmoDroid:
Just a couple notes to the first timers:

Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.

Currently, in the newest RED CWM, there are two enable options in the voodoo menu:

"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition

"/system lagfix" - this converts your "system" rfs partition to ext4

You will need to hit both of them for full optimization.

After selecting "enable lagfix", the text at the bottom will change to:

Voodoo lagfix is actually: disabled
next boot: enabled

Options:

/system lagfix conversion: yes
debug mode: no

Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.

Hopefully this will get fixed when a new version comes along.
[Fascinate Android Development] gunnermike:
Thanks for the clairification. i will update the OP as soon as i get back back from fixing this ladies internet and replaceing a DVR.
[Fascinate Android Development] john122675:
good job explaining voodoo. i love the extra it gives i have been using voodoo for months since i got this phone. this would have been helpful then cuz man i cant tell you how many times i cranked up odin because of voodoo. but i have to say i wont be without voodoo on my phone.
[Fascinate Android Development] harpdoc:
I just upgraded to from non-voodoo SuperClean to voodoo SC2.8 with eb01 radio. I've enabled voodoo/lagfix several times from clockwork but only get Quadrant scores in the 900's. Any idea if something is wrong?
[Fascinate Android Development] gunnermike:
which cwm are you using?
[Fascinate Android Development] harpdoc:
The latest Red one
[Fascinate Android Development] gunnermike:
ok. first are you sure that you dl'ed the the voodoo version?

if so reflash the rom. restart the phone. reboot to recovery. enable lag fix.
[Fascinate Android Development] harpdoc:
It's called super_frankenclean_2_8v_final.zip, so I think it's the right one. I reflashed it but no change. Just to be safe I'm re-downloading the rom and will try again. Strange.
[Fascinate Android Development] 420fan:
I didn't hear a females voice. I went from 2.8nv to 2.8 V following this verbatim, with the exception of the blue CWM, instead of red, but I fixed that. I scored a 926. I'm a little nervous to do much, because my phones my internet. I brick it, I wait....

thanks for any advice

EDIT: 2nd try, i get quadrant score at 946, but the phone feels a lot faster. took about 2 mins to reboot and still no female voice.
[Fascinate Android Development] GizmoDroid:
For those that didn't hear a robot voice, and getting low quadrant scores: I'm sorry but you haven't successfully activated the lagfix... but it might not be your fault (maybe :p).

Right now, there seems to be something not working for some people. I haven't had any problems myself, but several are not able to trigger the data conversion. Adrynalyne has posted the EB01 voodoo kernel to flash after sc2.8, if you are having problems.

The actual way to test to see if you have the lagfix enabled is not quadrant, but to open up adb or a terminal emulator and type "mount".

This is what a successful lagfix enabled system looks like:

mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system [COLOR="Red"][B]ext4 [/B][/COLOR]rw,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020
,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

If you run "mount" and it says "rfs" where the red is above, then you do not have voodoo lagfix successfully enabled.
[Fascinate Android Development] 420fan:
I just reflashed the EB01 Voodoo kernel, enabled lagfix, and rebooted. Wallah, I have the lady robot voice! I can't wait for my phone to reboot and get my first taste of Voodoo! Thanks to everyone for the help!
[Fascinate Android Development] gunnermike:
quadrent is proper way but it is the simplest way for folks who have never used terminal. i was debating on wether or not to include this. but since you have, then i will put it in the the trouble shooting post.

thanks again for all you help. you have made some really good points of clarifacation.
[Fascinate Android Development] harpdoc:
Switching to eb01 kernel worked! Thanks for your help gizmo and gunner.
[Fascinate Android Development] onemotodroid:
i am ready to convert my phone to voodoo. I am currently running SC2.4 nv

Under cwm (red)

How are the backup and restores done?
[Fascinate Android Development] gunnermike:
in recovery, you go to backup, and select backup or restore.

you may want to flash sc 2.8 voodoo.
[Fascinate Android Development] onemotodroid:
My question is do you have to disable voodoo before doing a backup?
[Fascinate Android Development] gunnermike:
a back up only backsup your rom. not your kernel not your modem. so to answer your question, no.
[Fascinate Android Development] finakechi:
*redacted*
[Fascinate Android Development] nirmdroid:
I've stayed away from voodoo until now, but with this guide I think it's time to try it out. First of all, thanks for simplifying voodoo for the rest of us. Secondly, I was wondering, does voodoo improve/hurt battery life in any way?
[Fascinate Android Development] Juno_Reactor:
There's another method without breaking Red CWM. This worked for me just fine.

1. I reverted back to DI01 from DL09 by odin flashing Adrynaline's DI01 recovery tar file.

2. I used z4root for root access, odin flashed old CWM tar file, flashed recovery using rom manager, and made DI01 nandroid backup.

3. Using green CWM recovery, I flashed froyo super clean+voodoo combo rom, navigated to SD Card and deleted old update.zip, odin flashed EB01 radio, wiped cache and installed new update.zip using CWM recovery.

4. And then, I used rom manager to reflash froyo super clean rom to wipe out trace, and enabled voodoo kernel.

=> this will allow you to flash any kernel without breaking CWM, therefore no need to reflash Red CWM using odin.
[Fascinate Android Development] gunnermike:
Glad to help. Voodoo will have no effect on battery life.
[Fascinate Android Development] vlucchetti:
I also did my first jump into voodoo doing this. Got the lady, and now I ask, what did you do to my phone to make it so much more responsive?

My 2.8nv wEB16 was quick, but this 2.8v with EB01 Kernel is really fast.
[Fascinate Android Development] GizmoDroid:
The main appeal/danger/only current feature that has been ported from the the voodoo project is the file system conversion. Instead of your phone having to jump through a proprietary and inefficient RFS filesystem in order to write data, it can now write all the data in beautiful, open source ext4.

Lots of other goodies will come once we have a working kernel from source.