yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] straygecko:
Mighty shiny cannonball you got there Renate. One more spot I see you could polish is to check existence of all the files up front before you do anything. I fat finger a lot.

This version had some oddness. I ran it twice in a row and although the device booted fine both times I got a slightly different display. No changes were made to any files inbetween.

C:\temp\usbrec_nst2>omaplink omap3_aboot.bin u-boot-ng2-exp-v05.bin uImage uRamdisk-cwm-exp-v00
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v05.bin, 175100 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER, Android Fastboot???????????????
???????, ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... 2080:0003, NOOK SimpleTouch??????????????????????, ok
Version: 01000000, payload: 4096, type: recovery

C:\temp\usbrec_nst2>omaplink omap3_aboot.bin u-boot-ng2-exp-v05.bin uImage uRamdisk-cwm-exp-v00
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v05.bin, 175100 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER, Android Fastboot, ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... 2080:0003, NOOK SimpleTouch, ok
Version: 01000000, payload: 4096, type: recovery
[Nook Touch General] straygecko:
Another try for ADB

Alright, I've stripped out all of the display initialization out of the CWM ramdisk and added a mount of the internal disk as a UMS device to windows ala noogie. I hope this eliminates any display interference with ADB. If not maybe we'll get the drive to mount and we can start looking at things.

The attachment has two ramdisks to try. One is the stripped down CWM. IF you don't get ADB or a disk mount try the second - a straight noogie ramdisk. Noogie is about the most basic we can get. All it does is mount your internal flash disk as a UMS device so you can get at it from your PC.

Now if you get a disk mounted it should show up as boot since that is the first partition. Don't change anything at this point. Copy uImage, uRamdisk, uRecImg and uRecRam off, zip them up and post them - they may help getting adb to work. The other partitions on your NG2 will be available but Windows won't show them as it only likes one partition on a removable device plus they are linux formatted. For the more adventurous you can load DiskInternals Linux Reader on your PC and try to copy factory.zip off the factory partition. I have trouble reading large files like factory.zip over USB like this so it may not work. When I try it on my NST about 90% of the way through it locks up and my NST ends up rebooting itself. But factory.zip would be real nice as its the full firmware for the device.

OK, so when you have the attachment unzipped first try:

omaplink omap3_aboot.bin u-boot-ng2-exp-v05.bin uImage uRamdisk-cwm-exp-v00

If that doesn't work try:

omaplink omap3_aboot.bin u-boot-ng2-exp-v05.bin uImage uRamdisk-noogie

Happy New Year to all.
[Nook Touch General] usenothing:
Hi, I do a try just now,

First, try with uRamdisk-cwm-exp-v00 , and here is the process:

Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v05.bin, 175100 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER瀀, Android Fastboot, ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4016128 bytes... ok
Waiting for disconnect... ok
Waiting for ADB...^C

then, try it with uRamdisk-noogie ,and got :

Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v05.bin, 175100 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, ok
Error 00000002 sending getvar, sent 0 bytes

I have been trying from experiment8. and there are always "7 volumes" in the led panel, never changed between the test process...
[Nook Touch General] Renate:
Oops, sorry about that. :o

I was running out the door and I didn't check things as thoroughly as I should have.

The program worked, it was only the tail end of the device names that got screwed up.

Here's a fixed version.

(I will add the startup file checking tomorrow.)

My question: I can't boot to my stock using the bootloader, fastboot sequence.

If I specify copies of the current uImage, uRamdisk then it stalls then reboots normally.

The thing is, I can see the bootloader led flashing.

This means that my fastboot fails and it's the normal boot sequence that takes over.

The previous error messages that I got trying to do this indicate that when I fastboot off uImage, uRamdisk it doesn't know where to look for /system.

Are there more kernel args to specify this?

I want to be able to fastboot then have it load the rest of the system off the flash.
[Nook Touch General] jwxuan:
The bad news

I just try exp12 with uRamdisk-cwm-exp-v00 and uRamdisk-noogie，the omaplink turned to 7 from 5 when I connected NG2, but nothing news! A little strange thing is like bellow：

Microsoft Windows XP [版本 5.1.2600]
(C) 版权所有 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>f:

F:\>omaplink.exe omap3_aboot.bin u-boot-ng2-exp-v05.bin uRamdisk-cwm-exp-v00
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v05.bin, 175100 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER, Android Fastboot, ok
product 3621GOSSAMER
version 0.5

F:\>

You can see there is no ”waiting for ADB……“，it just skipped to “F:\>”，then I when I ran devmgmt.msc，the pc display “Android FastBoot Interface”.After disconnected the usb, the NG2 just stopped at boot surface，and you can't put n button to make it boot，you have to put power button for 8 seconds and then release it，and then power on to reboot it！

Of course，exp12 with“ uImage-ng2-130-evt1b-exp-v00 uRamdisk-cwm-nst-rc2” still like before！
[Nook Touch General] shanks7777:
Cause you didn't input enough args.

You missed uImage.
[Nook Touch General] straygecko:
Try adding root=/dev/block/mmcblk0 to your kernel args
[Nook Touch General] jwxuan:
The good news

Microsoft Windows XP [版本 5.1.2600]
(C) 版权所有 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>f:

F:\>adb kill-server
* server not running *

F:\>omaplink.exe omap3_aboot.bin u-boot-ng2-exp-v05.bin uImage-ng2-130-evt1b-exp
-v00 uRamdisk-cwm-exp-v00
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v05.bin, 175100 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER, Android Fastboot, ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4016128 bytes... ok
Waiting for disconnect... ok
Waiting for ADB...

，then there is a new disc which never displayed before，which name is “boot” is 67M，and I can opent it！

View attachment 2489403，but I still can't see android adb interface，maybe my adb installing is wrong or something！
[Nook Touch General] straygecko:
No that's not right - still on my 2nd cup of coffee and this stuff is a little foggy to me anyway. The nook runs with the ramdisk as the root file system and mmcblk0 isn't even a file system. Try root=/dev/ram0 so it doesn't try switching to a real root fs.
[Nook Touch General] jwxuan:
So I run with uRamdisk-noogie，but the result is exactly the same，just a new boot disc emerge.
[Nook Touch General] Renate:
Success!

We can get to the boot partition.

A minimal root involves editing init.rc & default.prop in uRamdisk to enable ADB.

Please do:

fc /b MLO x-load.bin

Edit: The noogie ramdisk substitution is also good.

It's simpler, let's use that.

Also: Copy romrestore.zip to a safe place (or burn a CD).

This has your Nook's personalized settings.

Don't post it here.
[Nook Touch General] jwxuan:
How？

How？ When I open the file “uRamdisk-noogie”，I can only see “'V}v匨铄 ? b?3 ? 頜 鋧……”

You mean open another C command window and run “fc /b MLO x-load.bin”，I got this

“ ……

0000411C: AC 88

0000411D: B4 94

00004120: DC 00

00004121: 98 00

00004122: 20 00

00004123: 40 00

00004124: 88 01

00004125: 94 00

00004126: 20 00

00004127: 40 00

0000412A: 00 50

0000412B: 00 80

0000412C: 01 80

0000412D: 00 08

0000412E: 00 50

0000412F: 00 80

00004130: 00 80

00004131: 00 08

00004132: 50 51

FC: MLO 比 X-LOAD.BIN 长”，the last sentence means ”MLO is longer than X-LOAD.BIN“
[Nook Touch General] straygecko:
Woo hoo! We got something. I'm puzzled too about adb. Try this.

With your nook disconnected go into device manager and click on the view menu and and click on Show hidden devices. Look under any sections ADB Interface, Android Device or Android Phone for an Android Composite ADB Interface device. Check the hardware ids and if it is USB\VID_2080&PID_0007 delete it. Then under the Universal Serial Bus controllers section look at all of your USB Composite Device and USB Mass Storage Device entries and check the hardware ids. Delete any that show USB\VID_2080&PID_0007.

Now try omaplink again and let the devices reinstall.

---------- Post added at 09:37 AM ---------- Previous post was at 09:28 AM ----------

Renate means to boot your NG2 using the uRamdisk-noogie then when the boot disk shows up make a copy of romrestore.zip to your PC just like you would copy any file. This contains stuff like keys for talking with B&N that identify your personal NG2. If things ever go seriously wrong and you need to or accidentally completely wipe your NG2 this is a key file for getting it back to working. As its specific to your personal NG2 don't post it here. Just keep a copy safe on your PC.
[Nook Touch General] Renate:
No, I meant the uRamdisk in the boot partition on the Nook.
[Nook Touch General] jwxuan:
Sure，I post the code，and it displayed like before ＂........MLO is longer than XLOAD", do you want the entire information?
[Nook Touch General] Renate:
No, I just wanted to see if they were different.
[Nook Touch General] jwxuan:
Thank you very much, but with my nook disconnected with USB, there is nothing show USB\VID_2080&PID_0007.
[Nook Touch General] straygecko:
Did you check on Show hidden devices? There has to be something with USB\VID_2080&PID_0007 or you wouldn't have the Nook disk drives showing up.
[Nook Touch General] Renate:
The noogie uRamdisk that straygecko posted does not have ADB enabled in it.
[Nook Touch General] straygecko:
Right. When trying to get ADB going you need to use uRamdisk-cwm-exp-v00.
[Nook Touch General] Renate:
Yeah, but let's skip that and go straight to rooting.

Let's mod the init.rc & default.prop in the uRamdisk on the boot partition.
[Nook Touch General] straygecko:
You're right it makes sense to get the root done first. We'll still need to get ADB working but taking the USB boot out of the equation is a better first step. But I'd also like to get a good backup. I can't get a backup over USB with a USB booted noogie. The USB boot is definitely introducing some problems as I can boot noogie off an SD card and get a good backup over USB. I have the same problem with either a 1.2.0 or 1.3.0 u-boot. I'm puzzled by it. But maybe we'd be better off replacing uRamdisk on the device with a noogie ramdisk then backing up?
[Nook Touch General] jwxuan:
Disconnect with what?

Sorry，my English is very poor！Do you mean disconnect the NG2 from the PC，or just disconnect the omaplink with “Ctrl+C”?
[Sprint HTC One (M7)] :
Im not sure if this has been addressed already, sorry if has but are there any kernels for 4.3 roms that dont break tne camera???
[Sprint HTC One (M7)] elvisypi:
Nope, source code isn't yet released by HTC
[Sprint HTC One (M7)] :
Okay thanks, wasn't too sure.
[Sprint HTC One (M7)] DJMaj07:
Sorry to dig up an old thread, but I was going to ask a similar question so I figured I'd continue this conversation.

HTC released the kernel source for the GPE 4.3 sometime ago, is that not usable for Sense kernels or, at the very least, AOSP 4.3 kernels? I'm looking for a kernel with S2W on 4.3 but haven't seen any... So not possible yet?
[Galaxy S 4 Q&A, Help & Troubleshooting] JustSueMe:
Ok a couple of questions;

1. Possible to extract kernel I have so i can reflash with recovery if need be ?

2. I need a kernel for cm10.1

2a. Where is the best one to use?

2b. Id like to grab the source code

2c. Id like source code to have configuration set for daily use as I only want to make a few changes of my own and don't want to be working out every needed feature.

3. Does kernel compiling create a boot.img ?

Thanks in advance

This is for GT-I9505 jfltexx
[Optimus L3, L5, L7 Themes and Apps] Wehrmatch:
This is a newversion of*CWM.

version6.0.4.5

Added someoptions andwhen installingsome.Ziponlyhas an option of YES and NO

IS FOR LG-E612-610

enjoy

View attachment 2440099:cool:

:cool::cool:
[Optimus L3, L5, L7 Themes and Apps] Tupic Perez1:
This recovery is for...? What device?

Enviado desde mi LG-E612 usando Tapatalk 2
[Optimus L3, L5, L7 Themes and Apps] dkdkdk07:
Which device and touch or non-touch? Tnx.

Sent from my LG-P705
[AT&T HTC One (M7)] ck4794:
i need some help. i just bought my htc one tonight, and of course the first thing i want to do after i turn it on is root. but i can't get fastboot to recognize it. i've reinstalled the drivers a few times, googled my heart out, and can't seem to come up with an answer.

now before a lynch mob starts, please, i'm very frustrated, and i'm fighting the urge to just throw the phone into the wall. (at this point i think it's the only thing i haven't tried).

i read somewhere about firmware and windows 8.1 (which i'm on). my phone is still on 4.1.2. i think i read 4.3 is the only one that works with windows 8.1. but there are no updates available to me.

i greatly appreciate any help here. it's such a let down to get a shiny new phone, and being stuck... once i figure out the fastboot problem i should be good to go. i want to say i had this problem a while back with my htc one x, but it was so long ago i don't remember how i fixed it. in the middle there i switched to the s3 and that rooted without a hitch.
[AT&T HTC One (M7)] ck4794:
i don't know what i did but the phone magically decided now it wants to do the att update, it's downloading pretty slow but i'll see what happens.
[AT&T HTC One (M7)] GalaxyUser50:
Im sure you did this, but did you make sure in HBOOT its highlighted in red "FASTBOOT USB"? And you are in the platform tools folder of the android sdk? How about ADB? Does "adb devices" (Without quotations) work?

Let me know.
[AT&T HTC One (M7)] ck4794:
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
[AT&T HTC One (M7)] GalaxyUser50:
Are you trying this on wifi or data?
[AT&T HTC One (M7)] clsA:
you need to s-off your phone before taking that update !!!

and you need a windows 8 or windows 7 PC ... you'll never get fastboot on windows 8.1 and hboot 1.44.000 might as well give up on that.
[AT&T HTC One (M7)] ck4794:
no that seemed to do the trick. installed the update this morning. the phone is now on 4.3 and fastboot works just fine.
[AT&T HTC One (M7)] clsA:
ok good ...try rumrunner if you want s-off
[AT&T HTC One (M7)] ck4794:
thanks. it's been a hot minute since i've had an htc phone, can you remind me why i would want s-off after i already have the device rooted?
[AT&T HTC One (M7)] clsA:
This pretty well sums it up
[JAMin, XDA Neo, S200 General] aj0s:
I've been using Dopod 818 pro since the end of December 2005. A week ago, a problem suddenly came up. The speaker of this PPC does not work anymore.

I tried to play music using windows media player, or real player -> Does not work

I tried to use the speaker phone -> Does not work

I can't even hear anything when I make a call or receiving a call

It works when I plug in the headset. everything works perfectly.

It plays the ringtone when someone call me. (Very soft sound)

Is this a hardware problem? or is there anyway that I can do to fix it.

I bought the phone overseas (I'm located in Australia now). It takes a lot of effort to send it overseas for warranty.

Thank you
[JAMin, XDA Neo, S200 General] universaldoc:
Do a soft-reset. If that doesn't help, do a hard-reset. If that doesn't work , do a ROM re-install. If it still doesn't help, then you have a faulty unit.
[JAMin, XDA Neo, S200 General] aj0s:
I've done soft reset

I haven't done hard reset

->haven't had any backup program.

Is there any free solution for backup software?

Thanks
[JAMin, XDA Neo, S200 General] MobilZone:
i ve solution

well for this solution u must disassemble the phone. look at the handsfree jack and apply a jumper to the two front points of the connector. it will solve ur problem
[JAMin, XDA Neo, S200 General] gunggu:
I've had this problem, what I did was play music using headphone and suddenly unplug the jack. The Speaker works again like charm.

Cheers!
[JAMin, XDA Neo, S200 General] rcnomad:
dopod 818 pro speaker issues

I have run into the same issue with my 818 pro and my Himalaya...The fix is always uninstalling one or more applications that may be causing the problem. I assure you it's very unlikely that it is a hardware issue...Uninstall all applications and you should get the sound back..
[JAMin, XDA Neo, S200 General] bjrmd:
I have the same problem with my 818 pro. I have already done the hard reset-no change, tried blowing air in and out through the headphone jack, silicone spray and playing with the plug. It appears to be a hardware issue with the sensor mechanism inside so it always thinks it has a headset connected--poor design.
[JAMin, XDA Neo, S200 General] ganglion5:
Did anyone else figure out a solution for this (other than returning for repair?) This happened to me this weekend. Suddenly happened after I was using the headphone for an hour while I was rollerblading. Now I can't answer any calls without either the bluetooth or standard headphone. I can hear the ring go off, but just can't use it as a regular handset. I'm sure everyone agrees that this is a hardware issue with a poorly built headphone jack. But while I'm waiting for the retailer to restock the dopod 818 and send me a replacement, does anyone know of a hack that would allow the phone to activate the headphone AND the phone speaker simutaneously? The reasoning is I think the phone currently thinks there is a headset constantly being plugged in, so it deactivates the loud speaker as well as the phone speaker. But if there is a hack that lets WM5 to use the handset speaker and the headphone jack simutaneously, then at least I can answer phone calls without having to use the headset. Of course, this won't be a permanent solution, but it may bridge me through these tough times with the dopod.

I have to say, I still love this phone, but my patience is wearing a bit thin. First, it's the disappearing SD card (which I'm not even sure if it's solved yet), then I was having some problems with sending MMS messages, now this. :x
[JAMin, XDA Neo, S200 General] Matterhorn:
I had the speaker problem with my Jam. It is apparently a common problem with PPC phones, the mechanical switch in the headphone jack gets stuck. I was able to get mine to work again by plugging in the headphone jack a few times. If that doesn't solve the problem...well you know the drill :(
[JAMin, XDA Neo, S200 General] bjrmd:
There is nothing to do but exchange it--I was never able to find a work around either. Sorry.
[JAMin, XDA Neo, S200 General] hanmin:
I had problem the speaker on my HTC Charmer. I send it for repair and they replaced the speaker, with in like a week+.

However, now there are some other problems. It seems that when I try to use the speaker (play songs, phone, games, etc), the battery drain like mad and the unit gets very hot. The unit drain so much energy that the battery will die off even if I had the unit on AC power. Going to send it back to repair AGAIN!
[JAMin, XDA Neo, S200 General] tegomouse:
I had the exact same problem and suddenly unpluging the jack works for me.. ;)
[JAMin, XDA Neo, S200 General] X_Farhad:
this "sudden unplugging" thing won't work with Prophet, the Prophet's buzzer(speaker) problem is very common, the same thing happened to me, cost me 12$ in iran to change that part
[JAMin, XDA Neo, S200 General] tal_bendoli:
818pro speaker problem Hardware related

I had the same problem.

Speaker unit in phone burns out very quickly.

If you have warranty - your lucky.

In my case since I bought in Singapore and Use in Israel, I had to fork out 50USD to get a new speaker unit.

Tal
[JAMin, XDA Neo, S200 General] marvsipaski:
What you do is open the Comm Manager, tap the "phone" icon to set to flight mode. Then, turn on again.... that should do the trick
[JAMin, XDA Neo, S200 General] TheBrit:
I don't know what planet most of you guys are on. :(

The Prophet has a common problem with the rear speaker - it's a hardware issue as X_Farhad has pointed out.

There's no need to hard reset, and what's the crap about flight mode?

Yes, some can have a problem with the headphone socket and the solution for that is in this thread.

Mostly it's the speaker itself. The solution is here: http://xdaforums.com/showthread.php?t=281331

I've found a bit of sponge works better than paper - to see what I'm on about - go to the thread I've posted here.
[JAMin, XDA Neo, S200 General] sameerhere:
Speaker issues and phone hangs

I also have similar issues with my Xda Neo. The speakers stops responding when i get incoming call. I mean the phone dosent ring. Then if i try any music player or ringtons, there is no sound. I have to soft reset. Sometime when i get incoming call, it dosent ring and it also hangs the phone. Then i have to hard reset. I had to use that sponge over the speaker and then the speaker works. But sometime it still hangs. Looks like either HTC or Windows Mobile has major issues. I dont know how long this sponge thing will work. Are there any solutions..

sameer:mad:
[JAMin, XDA Neo, S200 General] dotandru:
Tal,

I have dopod 818 pro and having the same phenomenon like others, now I'm abroad and can not check the thing with the headset.

Can you tell me please where can I get service in Israel (I bought mine in Thai).

Many thanks

Dotan