yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] oldnoob:
I don't really know, but I would try finding an Odin image with a separate known working PIT file.

Edit: Never mind, I see you are already trying that in another thread.
[Samsung Captivate Glide] Litatus:
weird..

I'm not finding it... I even have a friend who has the z3x box, and they only provide the one package md5 to flash.

I've been asking here in the forum, but just one person gave me a pit file, unfortunately it doesn't work for me.

I've been google it for about 4 days now. =(
[Samsung Captivate Glide] dbrannon79:
for what it's worth, have you tried flashing with a different usb cable? maybe there is a bad connection.

also is kies installed on your pc? if so uninstall it. there may be conflicts with drivers. how did you get partition errors? you didn't have the box checked in odin that repartitions the device?

if all that is ok one last thing to make sure of that its not a problem in your pc. try using another pc, maybe a friends or neighbors. windows pc's are known to pick up bugs and malware undetectable by virus scanners which could have messed with drivers and other processes in the software. one of the reasons I stick to Linux, preferably ubuntu while when needed I run a virtual windows machine!
[Samsung Captivate Glide] Litatus:
still with errors...

I use ubuntu... i installed the heimdall 1.4... but the pit file still gives me error... is really weird...

I've tried to use the nvflash, but I don't know if I'm making something wrong or it just doesn't work... the heimdall gives me "usb write failed", and then I have to disconect the cellphone and take the battery out in order to try again...

you can check the pictures...
[Samsung Captivate Glide] dbrannon79:
I don't think heimdall is compatible with our glides! Make a vm with Windows xp and install Odin!
[Samsung Captivate Glide] hazard1nc:
I have tried to use Linux and my glide was never able to talk to my computer, I use debian and opensuse, so I had to reinstall over opensuse, so it works now with windows 7.
[Samsung Captivate Glide] Litatus:
odin 3.07

well.. I've downloaded the 3.07 version of the odin... I saw in a snapshot that it had the box for "ERASE NAND ALL"...

well, I checked that box, the odin started to flash, but it got stuck a few seconds after the start...

Somehow it seems it did something, now I am able to flash any rom, I mean that the odin finishes the flashing process without any error, BUT....

But still stuck in the samsung logo... =(
[Samsung Captivate Glide] dbrannon79:
now that you have odin working, try flashing the official UCLJ3 update that contains the bootloader. I posted a guide for updating that. if not go back to gb and try the official gb update! most of the roms here don't include the bootloader and some don't have the modem or kernels! can you flash CWM recovery and boot it? if so, you might try booting recovery and wipe data, cache and format /system. then try one of the official updates! if none of that works, your best bet would be to hit Dman3285 up with a pm, maybe with a small donation he could get your phone going again! he's one of our best devs here.

Hope this helps.

Thanks
[Samsung Captivate Glide] roothorick:
Waitasecond... Ubuntu...

PLEASE tell me you're not running Odin in a VM. PLEASE PLEASE PLEASE.

Strike what I had here before. Now that Odin is working, flash the PIT *first*. Make sure it's an untouched PIT dumped from a working Cap Glide. (If you need one, walk me through it and I'll dump mine.) Then do the UCLG9 oneclick (not UCLJ or UCLH). If it fails, do a battery-pull reset and try again. That *should* get you back to a functional device, and you SHOULD at that point be safe to flash UCLH or CM10/PACman.

And DON'T use Wine or a VM for Odin. It NEEDS a real Windows machine. I almost bricked my Glide trying to use a VM.
[Samsung Captivate Glide] Litatus:
no VM...

No, I have different partitions for Ubuntu and Windows 7... I'm running Odin on Windows 7...

About the PIT. I have two pit files from two members of the forum... Both of them gives me error. Check this picture: http://xdaforums.com/attachment.php?attachmentid=1558361&d=1355347858

That's the error I get.

Please, dump yours and I will try that one... Both pits gives me the same error when I flash any of them...

To dump your pit, you should be on linux, download the heimdal 1.4 RC from here: https://github.com/Benjamin-Dobell/Heimdall/archive/master.zip. The 1.4 is only available for linux at the moment and It seems that previous versions doesn't supports the Samsung Glide.

Here you have the compilation procedure: https://github.com/Benjamin-Dobell/Heimdall/tree/master/Linux.

After that, you need to put your phone into download mode, and then run the following command in the terminal:

heimdall-frontend

This will run the graphic mode of the heimdall. Go to UTILITIES complete the pit's file name and dump it.

Hope you make it.
[Samsung Captivate Glide] roothorick:
Shooting in the dark here...

You do have "Re-Partition" checked when you do the PIT, right?

Maybe if they were dumped with heimdall, you should try writing them with heimdall. Who knows, might be some file format shenanigans.

Can you flash the CWMR zip with Odin? It might get you recovery back, if nothing else, and then we could do some more advanced poking or dd'ing via ADB.
[Samsung Captivate Glide] Litatus:
yes..

I do have checked "Re-partition" and I get "FAILED" in Odin, and this error in the Glide's screen: http://xdaforums.com/attachment.php?attachmentid=1558361&d=1355347858

When I try to run heimdall to re-partition and flash the recovery at the same time, I do this command:

heimdall flash --repartition --pit sghi927-orig.pit --SOS SOS.img

Here I get a weird error. It says something like "not such partition named PIT"... It seems like it takes the parameter "--pit" as a partition name. If I try just to re-partition, I get the same error. I don't know if this is a software error or I am the one who is doing something wrong.

I can flash through Odin and heimdall. Both finishes, but I don't know if they do something or not, because nothing changes, I just get the samsung logo, and no recovery.

The same with the CWMR with Odin, It goes through all the process, but nothing.

What do you mean with "poking"?

How can I get connected via ADB?
[Samsung Captivate Glide] roothorick:
You can't get into CWMR so it doesn't matter.

Give the UCLG9 oneclick a spin, who knows, it might work.

Though, I'm starting to think that your download mode stuff is itself corrupt. You're probably gonna have to get nvflash working. Did you try that strace thing I mentioned in the other thread?
[Samsung Captivate Glide] Litatus:
me too...

I think that my download mode could be corrupted too.

I tried to use the nvflash, but everytime I tried to run the ./flash with any option in the terminal, I get "USB Write failed", and then I have to reset the phone taking out the battery. Maybe I'm doing something wrong, but I don't have any tutorial or something to know exactly how to use, because in another thread I've read that the nvflash could be locked, and you need to do something extra to bypass that.

What did you tell me in other thread? What do you mean with "strace"?

Any ideas?
[Samsung Captivate Glide] roothorick:
Literally just

strace -o nvflash-strace.txt {nvflash command}

With any luck it'll be a misconfiguration on your computer.
[Samsung Captivate Glide] Litatus:
results..

Well, I did you told me to.

Attached you will find the file. I get this in the screen:

root@litatus-VGN-NS110E:/home/litatus/nvflash# strace -o nvflash-strace.txt ./nvflash --getpartitiontable pit.txt
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
root@litatus-VGN-NS110E:/home/litatus/nvflash#
[Samsung Captivate Glide] roothorick:
The strace is a bit weird, apparently libusb doesn't strace well. But this is the only problem I could see:

ioctl(5, UI_DEV_DESTROY or USBDEVFS_BULK or USBDEVFS_BULK32, 0xbfbf1bbc) = -1 ENODEV (No such device)

Sounds like nvflash can't actually see your phone. Do you get the same error if the phone is not connected?

I might play around with nvflash myself if you can't figure it out.
[Samsung Captivate Glide] roothorick:
I was screwing around with nvflash and it doesn't work on my (fully functional) device, and I KNOW my environment is sane. I think Samsung locked it with their own SBK, which odds are we will never figure out.

I've got one last shot in the dark for you though, which is why I'm-a-bumping. But first I need to double-check something

Run this:

heimdall print-pit

And post the output here.
[Desire HD Q&A, Help & Troubleshooting] joelcutinho:
Hi,

The ROM Sabsa Prime v10.1 | 4.0.4 | Sense 4.1 is working perfectly fine except the Bluetooth Stereo Headset, There is no issue in connection or listening to Music via Bluetooth Headset. The issue is with the calls there is no sound heard and voice propagated .

I am using Sony Ericsson MW600 with HTC Desire HD, I have tried almost every XDA Rom and it is working fine. I love Sabsa Prime the most but the issue with calling feature via Bluetooth Stereo Headset is bugging me.

The Bluetooth once connected to phone also shows - "Connected to Music" & "Connected to Phone". So there is no issue there. Please help/fix this issue.

Thanks.
[Desire HD Q&A, Help & Troubleshooting] kevintmr:
I commiserate with you. I have viper rom 1.1.0 on my inspire 4g and a blueant q2. Same issue with this setup
[Desire HD Q&A, Help & Troubleshooting] bestfil:
Wierd... My car speaker set has no problem with bluetooth connection... Nokia CK 200.

Look deeper in the forum, once I've found the solution.
[Desire HD Q&A, Help & Troubleshooting] soyeltano:
Same problem with the same headset and HTC Inspire 4G.

My car Bluetooth (VW) works, though.

Thanks.
[Desire HD Q&A, Help & Troubleshooting] bestfil:
Solution:

http://xdaforums.com/showthread.php?t=2039142
[Desire HD Q&A, Help & Troubleshooting] soyeltano:
Applied p2jack's v3.0.55 and v0.1 mod, and now I can answer and finish calls, and get calller info in the display, but still no voice heard in any of both ways.

I'm with Sabsa Prime v10 and tried with my Sony Ericsson MW600.

Hope somebody can fix this issue.

Thanks in advance.
[Desire HD Q&A, Help & Troubleshooting] gpa_76:
I have old Nokia HS-4W with Hands-Free Profile (HFP), it works fine.

Instead of my new Jawbone ICON with Headset Profile (HSP). I can't hear the voice of my friend. But can hear the sound of the phone like a ring etc through Advanced Audio Distribution Profile (A2DP).
[Desire HD Q&A, Help & Troubleshooting] joelcutinho:
Sabsa Prime 11 is released, let me try it and see if Sony Ericsson Bluetooth calling voice feature works fine or not.
[Desire HD Q&A, Help & Troubleshooting] gpa_76:
No, it's not working too... :(
[Desire HD Q&A, Help & Troubleshooting] joelcutinho:
HI Guys,

I have emailed Ali Raza about this issue, lets see what he has to say.
[Desire HD Q&A, Help & Troubleshooting] gpa_76:
Has he answered something?
[Desire HD Q&A, Help & Troubleshooting] serhius:
Oh, no! I tryed to use my blutooth headset and found such problem... :(
[Desire HD Q&A, Help & Troubleshooting] gpa_76:
You are not alone. I'am with this problem from august. Nothing happend from that time. Now I'am using Sense 3.6 and wait for solving.
[Desire HD Q&A, Help & Troubleshooting] joelcutinho:
No, he hasn't answered yet.
[Desire HD Q&A, Help & Troubleshooting] gpa_76:
I think here is solution of our problem, we should change file AudioBTID.csv in Sense 4 by the same from Sense 3.6 http://www.droidevs.com/showthread.php?t=420&p=7329&viewfull=1#post7329

This is /system/etc/AudioBTID.csv from Pacha Nero 2.2, could somebody check it on Sense 4?
[Desire HD Q&A, Help & Troubleshooting] gpa_76:
Yes! It works. My Jawbone ICON works fine on Sabsa 11 with AudioBTID.csv from Sense 3.6
[Desire HD Q&A, Help & Troubleshooting] joelcutinho:
Here is the List that i am currently having in SABSA Prime 12 Final. The Bluetooth I use is listed in the list i.e. MW600 Sony Ericsson. But still the issue persists.

HEADER,Villec2_HTC_20110422,

Default,1001,1101

Default Car-kit,1201,1301

Jabra Wave,1401,1501

Motorola H790,1402,1502

Jabra EasyGo,1403,1503

245Plantronics,1404,1504

Jabra EXTREME,1405,1505

PLT_M1100,1406,1506

PROPlantronics,1407,1507

HM1000,1408,1508

Jabra Stone2,1409,1509

VBT3050,1410,1510

Jawbone ICON,1411,1511

9XXBackBeat,1412,1512

Jabra Clipper,1413,1513

Jabra SP700,1414,1514

Jabra Halo,1415,1515

Motorola Finiti,1416,1516

Jabra Cruiser2,1417,1517

LG HBS-700,1418,1518

LG HBM-800,1419,1519

BlueAnt Q2 V1.1,1420,1520

Blueant V1 V5.3,1421,1521

VH700,1422,1522

MW600,1423,1523

BHM400,1424,1524

BHM300,1425,1525

Nokia BH-505,1426,1526

Motorola S10-HD,1427,1527

JAMBOX by Jawbone,1428,1528

Samsung HM-3500,1429,1529

Motorola Roadster,1602,1702

Motorola T605,1603,1703

BMW,1604,1704

FORD Sync,1605,1705

Denso 03,1606,1706

JCI Honda,1607,1707

JCI Mazda,1608,1708

Luxgen Pilot,1609,1709

Parrot MK9000,1610,1710

Porsche-HFP,1611,1711

Audi BTA0626,1612,1712

BMW Combox,1613,1713

JVC KW-XR 810,1614,1714

FORD Audio,1615,1715

END,,
[Desire HD Q&A, Help & Troubleshooting] gpa_76:
You should delete your headset from the list. I deleted my jawbone icon, and then it work perfectly!
[Desire HD Q&A, Help & Troubleshooting] Dzkiller:
use ViperDHD
[Android Software/Hacking General [Developers Only]] arcusmedia:
I have Searched and Searched and no one can provide a Answer...

I have the ZEKI TB782B FID:CF tablet and would LOVE to have google play on it...

Everything I have tried has bricked the thing...

So Does anyone have the answer on how to flash the market on the ZEKI TB782B FID:CF?

I would greatly Appreciate it!

:angel:
[Android Software/Hacking General [Developers Only]] mrleroybrown:
Zeki 4.04 Tablet TB892B FID: CF

Same here. I bought a Zeki 4.04 Tablet TB892B FID: CF and I am dying to get google play on it but it seems like I am the only person with the 8" Zeki...I can't find anything on it. Ugh. I recently rooted my ZTE Warp Sequent but I haven't had any luck with this Zeki Tablet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Google Wallet Installer for Verizon, AT&T, T-Mobile, and US Cellular Samsung Galaxy S3.

Requires ROOT, an UNLOCKED BOOTLOADER, and BUSYBOX!(A deodexed ROM is just recommended)

My newest project, RemoteFlash, was just released! Take a look and give it a try!

Wallet Installer Is Now Available For Free To All Supported Carrier Models On XDA! (Donations Appreciated)

My application, "Wallet Installer", will install Google Wallet on almost any US based Samsung Galaxy S3. It simply edits your build.prop and then places the correct modifications into your system. It downloads all the files from my personal server, which is pretty quick. Just select the appropriate Rom type: AOSP, JB Touchwiz, or ICS TouchWiz, and then your carrier: Verizon, AT&T, T-Mobile, or US Cellular. I also added a restore option for your build.prop, so you can restore it after you setup Google Wallet. Hopefully this helps you out and makes the process easier!

Wallet Installer has been updated on the server side. The credit goes to Paul Obrien for the new version! To install it, simply reset Google Wallet, delete it, and then rerun Wallet Installer! Make sure to also have BusyBox installed/updated!

Please donate if my work helps you : )

V3: No Recovery/More Stable

Original Thread: Here

And as always: I take no responsibility for bricked devices, whether a soft brick or a full on brand new coffee coaster.​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rozzco:
This sounds great except for the recovery flash. Does the app offer to skip this step so we can keep whatever recovery we may already have installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Unfortunately, no. It has to use an open, unencrypted recovery to flash the files. I would allow use of CWM if it was unencrypted, but it's not. An option I am planning on adding in the future is the option to backup your current recovery and flash it after TWRP has been used.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Just tried it and it boots into twrp but nothing happens.

Sent from my Black Jelly I747 by graffixnyc theme by wanam ported and tweaked by David Dee ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
It sounds like you had a bad download. Go under your /sdcard partition and look for files like: "Wallet.zip", "recovery.img", "Fix.zip" and delete them(they shouldn't be there if they flashed correctly). After deleting those files, try again. Make sure you have a good data connection. Preferably WiFi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Also, make sure you have busybox installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
That's what it was...needed busy box installer. Worked great. I had the apk and files for libs but that was much better. Thank You, and nice work.

Sent from my Black Jelly I747 by graffixnyc theme by wanam ported and tweaked by David Dee ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
No problem! I just hope more people give it a shot! It won't disappoint.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mdwbeex:
as soon as the recovery issue is ironed out, I'll give it a spin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Technically the open recovery isn't an issue, at least not development wise. I use it because there are different versions of CWM rolling around, and they aren't all capable of the same things. This way, with an open recovery flash, I greatly reduce the chance of bricking/other issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobnddl:
Recovery Return Question

Thanks for putting this together.

After flashing this, can users return to the recovery of their choice, or are we locked in to TWRP 2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
You can go to whatever recovery you like! TWRP is only used for safety reasons during the flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dB Zac:
It's not working for me. It reboots into recovery but doesn't do anything. Then the phone doesn't boot into the room and I have to re flash the rom

Edit: I to, did not have busybox installed. you may want to put a warning on the app

---------- Post added at 10:26 PM ---------- Previous post was at 10:03 PM ----------

Also, if the build prop was edited to SPH-710 the Samsung voice program would still work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterDecker:
EXACTLY what I was looking for. I saw the entire post about getting it working, and just didn't feel that I was "qualified" enough to do what was required. I bought the app and figured I'd give it a try. It took a bit longer to download from the Play Store for some reason, but once it was done, it installed rather quickly.

I then ran the program, and selected as it was instructed. POOF it started installing, and then the phone rebooted into TWRP (I already use TWRP anyway), and all went well. I set up my account and that too went well. I tested it as I could and it works, then I decided to restore my build prop, after that again the phone rebooted, and then tested out wallet. It too works again.

Now then the only thing I am thinking about is automatic updates. I have to have that for another program for my work. I've seen the other post that you do not want the auto updates on. If on the next auto update it causes a problem I will report that here, but I think that just re running the program letting it do the build prop again, get it working, then restoring the build prop should be an easy fix for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
So you got it working? Sorry for overlooking busy box in the OP. Hope everything worked out okay.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Glad it helped you! Also, thanks for the thorough post, It's really appreciated. I leave my auto-updates on, but I haven't had any issues. If you were to have issues, you can just reset wallet, restore built.prop(if you haven't already), and run Wallet Installer again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njinstantkarma:
Rom Updates

What happens after you install this get it working then flash a new version of a rom... Im currently using Tasks aokp jellybean rom. Do I need to do this everytime I update a rom or just do it once nad it's done, Also Task has 4.2 available does this matter once I update to his 4.2 releases
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Every time you want to flash a new ROM, you have to reset google wallet. Then you can use my app again, after the new ROM flash, and you'll have wallet again. When it comes to 4.2 in specific I can't give you a straight answer, since I don't have access to a 4.2 ROM. My guess is that it will work fine, but it's never been tested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njinstantkarma:
If I just update a new version of a current Rom as I do weekly doing a dirty flash or not wiping just clearing dalvic cache etc, would I still need to re-install the app. Or only on a full wipe or a new Rom would I need to start from scratch? .

Another question if I re-install the app would I need to setup the payment every time and add new funds or cards or would all that information be available in the account
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
If you're dirty flashing, you should be fine leaving Wallet as is, but if you need to do a wipe, you should really reset Wallet. All of that information is saved on Google's servers, so it will be there next time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
same thing

same thing happend to me i had wallet running on 4.1 good made a purchase and everything the the next day i decide to install a 4.2 rom wow,had al kinds of problems so i decided to redo the entire phone,i still chose to put a 4.2 rom so same thing happend installed version 3 of this and when i installed wallet it said u need nfc go to the settings not there so,i retired my backup and went into the build prop manually and changed the three things u need to change it rebooted i went to the play store and it let me dl wallet and it let me activate it but im stuck at adding my card its been adding for like 20 mins now ill see what happens
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Sorry for the wait everyone! I can start supporting users again. Thanks for the wait while I was on holiday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
This doesn't yet support 4.2. I may add support for it when more people start using those builds, but until then I'm going to continue trouble shooting issues on ICS and JB 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evoguy404:
Sometimes I get unknown transaction when using wallet....I've tried today at McDonald's but would not go through. ...is this a glitch on Google Wallet part or on my side?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
4.2

i cant belive it took me all god dam day but i got it working on 4.2 haven't tried it in store but the card is added whewwwww
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
It was a glitch on Google's server. Should be fixed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElKompaAndres:
I get this message after trying to add my account. I'm running a 4.1.1 JB TW ROM. any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
Did you use Wallet Installer V3? That was an issue in V2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElKompaAndres:
yes sir
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prl91:
I would recommend restoring your build.prop and trying it again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evoguy404:
Thanks dude i figured it was something on Google's side....

Thanks

This is the best thing going on my S3:beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 65coupei6:
Install works perfect on UCDLK3 & ATT! I already had a card added using Google Checkout so setup was fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
Everything worked, added cards. On CM10 Stable. Yet to try out a purchase.

Sent Using Galaxy S3 AT&T - CM10 Stable - XDA App