yashsingh1/xdaforums huggingface dataset:
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Hey man, ntrw just copies every bit of your sd in one image. You can cut it around 64MB, look for the same pattern as in the dumped roms found on the ftp.

When you flash it back your bootloader will know what to do.
[JAM, MDA Compact, S100 Software Upgrading] Riel:
Aha.

Euh, how can I cut is 8)

Not very good with pc's ...

I can only follow instructions and understand then what I am doing.

So I don't have to use nbfdec to do something? Coz in instructions the say name the file Backup.nb1 so I guessed it has to be encrypted first.
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Riel what the hell are you trying to do :?: Sorry for sounding rude, but I guess you're mixing things up. Check-out this link http://wiki.xda-developers.com/index.php?pagename=MagicianRomUpgrade for instructions regarding upgrades. Or give me pm & we do it in Dutch.

Cheers, M
[JAM, MDA Compact, S100 Software Upgrading] unsated:
Hi,

I just found a file on FTP location (ftp://xda-developers.com/Magician/Shipped_ROMS/) which seems like have been recently uploaded. Filename is WWE_11300_550_11200.zip. Can someone tell me what ROM is this i.e. is it from tmobile etc. I own a I-MATE Jam and would like to update my rom. Current Rom i have is 1.12 with radio 1.12.10. Now is the above mentioned file a PROPER imate jam update file.

By proper I mean can i just execute the Setup.exe etc. and let it run ?

Last time for my update i got a ROM from URL http://www.clubimate.com/support/JAM/ROM/JAM_WWE_11200_128_11210_ship.exe

Will this behave the same way ?

Thanks in advance.

Cheers !!
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Sounds like a decent rom, you'll never know untill you tried whether it's working :-( Probably it's TMO & still suitable for your jam when you follow the description from the wiki http://wiki.xda-developers.com/index.php?pagename=MagicianRomUpgrade. It contains a direct link to TMO's 1.13WWE as well.

Succes, M
[JAM, MDA Compact, S100 Software Upgrading] elcaro:
It works!!

Thanks a lot mate. I used your method to upgrade my Magician to 1.13 ROM from Qtek ( with ext-Rom ver 550 ) . I like BigStorage ...
[JAM, MDA Compact, S100 Software Upgrading] mc_oliver:
Thanks oltp. Being on dial-up really sucks and I can't log in to the forums as much as I want to. :(
[JAM, MDA Compact, S100 Software Upgrading] neo999:
Help, error while doing ROM upgrade!!

Hi bros,

I have a O2 XDA mini with ROM 1.11.922 WWE and I've read the instructions for using the NL 1.13 ROM but each time I run the MaUpgradeUt_noID.exe, I get error 150.

Here is the ruu.log:

14:58:52:371 [msg] : Version : [1.5.0].

14:58:52:381 [msg] : Config Info : [776571],[1],[1],[0].

14:59:15:303 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.

14:59:19:640 [msg] : Disconnect ActiveSync .... [2]

14:59:19:800 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.

14:59:54:830 [msg] : Device BL VER : [] [].

14:59:54:830 [err] : Device CID Error.

14:59:54:830 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]

15:00:21:198 [msg] : Check Ac in BL mode. AC : [1]

15:00:22:700 [msg] : IsBL. BL : [1]

15:00:22:951 [msg] : =============================================

15:00:22:951 [msg] : START UpdateRadio !

15:00:23:131 [err] : Check SecurityPassword Error.

15:00:23:131 [msg] : START UnInitialization !

15:00:23:141 [msg] : END UnInitialization !

15:00:23:361 [msg] : IsBL. BL : [1]

15:00:23:381 [msg] : START BackCEMode !

15:00:23:381 [err] : BL Set BackCE Flag Error.

Greatly appeciate your help.

Thanks
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Hi,

Upgrading with maupgradeut_noid you've got to do it twice. Have you done that?

Regards, M
[JAM, MDA Compact, S100 Software Upgrading] neo999:
Hi Oltp,

Great to hear from you, the expert. Yes I've run MaUpgradeUt_noID.exe twice. Indeed I've repeated this process several times with same outcome.

Note that I did the deviceid header update in the nk.nbf as well as tried it without updating it.

Do you think that correction of the deviceid header must be done in all the three nbf files i.e. nk, radio and ms ?

Thanks
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Hi,

I don't think you need to update the radio.nbf & ms.nbf too. The nk.nbf is the ce image. 'Funny' thing is that when you got this: ERROR 150: ROM UPGRADE UTILITY I think you're not having a magician but another device. Correct me if I'm wrong on this subject, cause I don't no how to avoid error 150. Have you ever done an upgrade by shipped-rom before.

Last resort can be the SD upgrade method, there are some dumped rom on the ftp, even a 1.13WWE BIG Storage rom (I know the one who dumped it, you can trust it ;-) )

Regards, M

PS all error codes:

Error codes:

ERROR 100: MODEL ID ERROR

Definition: ROM image is not design for the device you are upgrading. It happens when you try to use Himalaya's ROM image into other HTC like Magician, Blueangel or Alpine

Solution: Use appropriate ROM Upgrade image for your Device, no two device can share the same ROM

ERROR 101: CONNECTION

ERROR 102: CE IMAGE FILE CHECKSUM

ERROR 103: ROM IMAGE FILE NOT FOUND

ERROR 104: CANNOT OPEN ROM IMAGE FILE

ERROR 105: OPEN PORT FAILURE

ERROR 106: EXECUTE REMOTE COMMUNICATION PROGRAM FAILURE

WARNING 111: POWER ADAPTER NOT PLUGGED IN

ERROR 112: CE ROM UPDATE

ERROR 113: EXTENDED ROM UPDATE

ERROR 114: RADIO ROM UPDATE

ERROR 115: INVALID VERSION OF ACTIVESYNC

ERROR:116 GENERAL

ERROR 117: INVALID MODEL ID

ERROR 120: COUNTRY ID

ERROR 121: LANGUAGE ID

ERROR 122: EXTENDED IMAGE FILE CHECKSUM

ERROR 123: RADIO IMAGE FILE CHECKSUM

ERROR 130: CREATE CE ROM IMAGE

ERROR 131: ALLOCATE MEMORY

ERROR 132: WRITE DATA

ERROR 133: COMMUNICATION

ERROR 134: READ CE ROM IMAGE

ERROR 135: COMMUNICATION

ERROR 136: COMMUNICATION INTERRUPT

ERROR 137: COMMUNICATION

ERROR 150: ROM UPGRADE UTILITY

ERROR 200: WRITE EXTENDED ROM FAIL

Error 201: GET DEVICE DATA ERROR

This error is a bit misleading. The BAUpdate tool is trying to switch the phone into bootloader mode, and the phone for some reason is being uncooperative. This happens to me from time to time. The best, and quickest way around this is to force the phone into Bootloader manually. By pressing the record button, while doing a hard reset (Power + Reset) your phone will enter bootloader mode. You can verify this as the screen will say, Serial, and change to USB when you cradle it.

Once you cradle your phone, Windows will detect it as new hardware, and take a minute or two configure the right driver(Microsoft USB Sync). Once this is complete, you can run the BAUpgrade utility again, and this time you should get past error 201.

Error 202: READ IMAGE

ERROR 210: CREATE EXTENDED ROM IMAGE

ERROR 211: ALLOCATE MEMORY

ERROR 212: WRITE DATA

ERROR 213: COMMUNICATION

ERROR 214: READ EXTENDED ROM IMAGE

ERROR 215 COMMUNICATION

ERROR 216: COMMUNICATION INTERRUPT

ERROR 310: CREATE RADIO ROM IMAGE

ERROR 311: ALLOCATE MEMORY

ERROR 312: WRITE DATA

ERROR 313: COMMUNICATION

ERROR 314: READ RADIO ROM IMAGE

ERROR 315: COMMUNICATION

ERROR 316: COMMUNICATION INTERRUPT

ERROR 317: COMMUNICATION
[JAM, MDA Compact, S100 Software Upgrading] neo999:
Hi oltp,

Thanks for your support.

Actually I did an upgrade from 1.03 to 1.11 last year from the shipped rom obtained from the O2 website.

I have not dared to upgrade via SDCARD yet but I guess that's the last resort.

One thing that troubles me is that after all these unsuccessful attempts, I tried to reflash with the shipped rom I used successfully last year and surprise ! ....I constantly get error 120 (country id).

So that thing scares me as I fear that if I do upgrade via SDCARD I may end up with a dead Mini.

Lastly I would appreciate if you can let me have the exact link to the 1.13 BS rom and also confirm if I have to change the device headerid in this rom before I upgrade.

Cheers
[JAM, MDA Compact, S100 Software Upgrading] oltp:
This is f....g irritating. Seems almost like the id has been changed now & the rom isn't fully loaded. Does your device boot normally or haven't you tried it yet?

Did you try to flash that 1.11 with the maupgradeut_noid to avoid error 120? It worries me too that you got this errot now. Which maupgradeut_noid are you using, is it the one from page 1 of this thread?

Since we're worried about your Device_id a SD upgrade might give you simular probs when you use the original rom dump. Best way to check the id is dump your again & view it with a hexeditor.

Cheers, M
[JAM, MDA Compact, S100 Software Upgrading] neo999:
Hi oltp,

Guess what ... I finally got it to work. After so many days of fiddling about, I came to the conclusion that my downloaded rom files and tools cannot be wrong so I decided to uninstall ActiveSync and clean all temporary folders on my PC.

Then I upon my first reflash it worked !!! I now have an updated ROM with big storage too. ( I did have a heartstopping moment when the hardreset took a hell of a long time before the Windows setup starts.)

Thanks for your advice and support brother.

Cheers
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Nice to hear that, I really didn't think of that solution. Must remember this, sometimes life can be so simple.

Enjoy your new device & all the best, M
[JAM, MDA Compact, S100 Software Upgrading] siemens man:
xda mini dead

hi guys

where i can find english lang. with rom v1.13??? help me

thank you
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Check out this http://wiki.xda-developers.com/index.php?pagename=MagicianRomUpgrade & it should all be explained.

M
[JAM, MDA Compact, S100 Software Upgrading] barisg:
Installed Radio 1.13, but havent seen any significant improvement on gsm voice quaility or on bluetooth.

What is the use of this Radio?
[JAM, MDA Compact, S100 Software Upgrading] yeoruss:
Hi All,

Need some advice on a problem i had here http://xdaforums.com/viewtopic.php?p=277438#277438

Been stucked on this cor some time. Anyone had the same problem?

Regards
[JAM, MDA Compact, S100 Software Upgrading] kuya84:
Hello, Try this one

I think if you get problem with the SD card, you can use Mr. OLTP ways.

First open this :

http://wiki.xda-developers.com/index.php?pagename=MagicianRomUpgrade

then

downloadls all the tools you need, from the site.

1. Unzip NL_11300_131_11200.exe (or any other shipped-rom) to get all the .nbf & enterbl.exe . click right your mouse and chose extract to NL_11300_131_11200\

then you must copy all the file from NL_11300_131_11200 folder to c:

ex: c:\temp (make a new folder "temp", and copy the file from the NL_11300_131_11200 folder).

2. Put NBFDEC in the same directory = open nbfdec folder, you will find release folder in there, open the relase folder and copy 2 file to c:\temp.

3. open the temp folder and find getdevicedata.exe, Copy the getdevicedata.exe to your Magician and execute it (it will not provide any gui displays or feedback whatsoever), open the windows in my device(in your PDA), search for getdevicedata.txt. then copy to your desktop, and open with notepad.

4. To decode nk.nbf -> nk.nb1 start a command window, go to the directory where you stored nbfdec & the other files & type: nbfdec -d nk.nbf nk.nb1

this isi the ex:

in cmd

c:\documents and settings\frans>cd c:

c:\documents and settings\frans

c:\documents and settings\frans>cd ..

c:\documents and settings>cd ..

c:\>cd c:temp

c:\temp>nbfdec -d nk.nbf nk.nb1

this will convert nk.nbf to nk.nb1

don't close the CMD windows

now open the Hexeditor (must use the newest version V3.x)

open file/nk.nb1

then klik replace button , in the upper insert 02 00 00 80 00 20

in the lower 02 00 00 b8 01 20

replace all, enter.

save file in same name.

then back to the CMD window

c:\temp>nbfdec -e nk.nb1 nk.nbf

and

close the CMD windows.

open the temp folder, plug your PDA to USB,

On your PDA press power,camera and reset to bootloader mode.

clik maupgradeut_noid.exe on the temp folder.

and follow the instruction. if shows error 120. repeat again clik maupgradeut_noid.exe this will start to instal your OS

FINISH

thanks to MR. AMPDA, MR. OLTP and Mr. SEAN

for helping me.
[JAM, MDA Compact, S100 Software Upgrading] Lupusic:
I tried to install this rom on my vodafone vpa compact.

"This is not for your device" was the message.
[JAM, MDA Compact, S100 Software Upgrading] Lupusic:
NOW WWE_11300_550_11200 worked on my vodafone vpa compact device.

I managed, now it works very well. HEYOOOOO

Very EASY

Here how I did it in 5 steps. (I learned this method from

ampda_How_To_PPC_Upgrades_V 1 file, THANKS to THE WRITER. GOD bless him.

1-Downloaded : WWE_11300_550_11200.zip FROM ftp://xda-developers.com/Magician/Shipped_ROMS/

2-Opened RUU.CONF by using notepad program and inserted this pharese as first line :

[CHECKCEID_TYPE]=1

3-By pressing Camera-Power and Reset buttons at the same time, entered bootloader mod.

4-Unchecked Activesync USB connection and connected device to PC

5-Started MaUpgradeUt_noID.exe .

NOW it's time to have a BIG STORAGE.

Do you recommend it, should I transfer to big storage.

Help needed.

Kind Regards
[JAM, MDA Compact, S100 Software Upgrading] oltp:
I like them BIG

Storage
[JAM, MDA Compact, S100 Software Upgrading] Lupusic:
Heyooo,

It's BIG now...

This was the method. Again in 5 steps...

1- I decoded nk.nbf to nk.nb1 by using nbfdec.exe

2- Using a hex editor, I opened nk.nb1 and found the value 02 00 00 80 00 20

3- In this value I changed 80 00 to b8 01.

4- I decoded nk.nb1 to nk.nb1fby using nbfdec.exe again

5- Finally in bootloader mode I run maupgradeut_noid.exe

After finishing everything, my device didnt hard reset and I was in panic for 10 minutes. I tried over and over but didnt hard reset and didnt open the device. There was just a screen showing version numbers.

If this thing happens to you, do not panic, just wait. It opens itself eventually and ofcourse with 26 MB of STORAGE...Nice, isnt it.

Now I see that , I did two installments and this is not necessary.

I learned it by doing it. Ideal method would be this:

1-Get this ROM: WWE_11300_550_11200.zip FROM ftp://xda-developers.com/Magician/Shipped_ROMS/

2-PROCESS OF RUU.CONF file in this zip file.: Open RUU.CONF by using notepad program and inserted this phrase as first line : [CHECKCEID_TYPE]=1 and save it.

3-PROCESS OF NK.NBF file in this zip file.: Decode nk.nbf to nk.nb1 by using nbfdec.exe. Than, using a hex editor, open nk.nb1 and found the value 02 00 00 80 00 20. In this value change 80 00 to b8 01. And finally decode nk.nb1 to nk.nbf by using nbfdec.exe again

4-BACKUP OF EXTENDED ROM : Easy and necessary process. Hard reset your device, when it says "Tap your screen to use" tap and in 3 seconds reset your device. Very important, dont miss this 3 seconds. When your device opens you'll see a folder EXTENDED ROM and some cab files in it. Backup this folder to your SD or MMC card. That's it.

5-INSTALLING THE NEW ROM: By pressing Camera-Power and Reset buttons at the same time enter bootloader mode. Unchecked ActiveSync USB connection box and connect device to PC. Run MaUpgradeUt_noID.exe

Kindest regards from a HAPPY MAN...

P.S.: Every file and information I used was found on this web site. Thanks everybody.
[JAM, MDA Compact, S100 Software Upgrading] Lupusic:
A question:

These files were in my EXTENDED ROM.

Does anybody know which is for what?

CAB: \Extended_ROM\Delete_vdisk_shortcut_WWE.sa.CAB

CAB: \Extended_ROM\Caller_ID_Magician_Generic_WWE_RC13.CAB

CAB: \Extended_ROM\SmartDialing_Magician_Generic_WWE_RC13.CAB

CAB: \Extended_ROM\PhonePad_Magician_Generic_WWE_RC12.CAB

CAB: \Extended_ROM\CV2.41.386_WWE.CAB

CAB: \Extended_ROM\JMM101257_WWE_1004.CAB

CAB: \Extended_ROM\Version.sa.CAB

CAB: \Extended_ROM\Customize.sa.CAB
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Delete the shortcut to loadvdisk to hide ext-rom: \Extended_ROM\Delete_vdisk_shortcut_WWE.sa.CAB

Caller id app, for photo contacts: \Extended_ROM\Caller_ID_Magician_Generic_WWE_RC13.CAB

unsure: \Extended_ROM\SmartDialing_Magician_Generic_WWE_RC13.CAB

phonepad: \Extended_ROM\PhonePad_Magician_Generic_WWE_RC12.CAB

unsure: \Extended_ROM\CV2.41.386_WWE.CAB

Probably Java: \Extended_ROM\JMM101257_WWE_1004.CAB

Unsure could be only a reg.key with version info: \Extended_ROM\Version.sa.CAB

Unsure: \Extended_ROM\Customize.sa.CAB

To view them use WinCeCabManager (10 trial start of the program)

& visit the wiki for all docs (about rom upgrading too)

M
[JAM, MDA Compact, S100 Software Upgrading] Lupusic:
Thank you,

and the others I could find till the moment :

phonepad cab is installing the input method of phonepad

smartdialing cab is installing smartdial program (finds the person when you start writing his/her name in dial pad, namely, I touch 2-2-6 to find person CAN. very usefull)

Best regard
[JAM, MDA Compact, S100 Software Upgrading] c_shekhar:
Re: it seems easier just to decode nbf, make bigstorage patc

I have down loaded the nbfdec folder successfully. The folder containd the nbfdec.exe file inside another subfolder named release. There are several .C and .H files what are they meant for??

2. I kept the downloaded nk.nbf file inside the folder \nbfdec\release and run the command as advised. I always get crc fail error. I have tried on 2-3 other nk.nbf it always gives the crc fail error. where am I going wrong????? Any suggestion???
[JAM, MDA Compact, S100 Software Upgrading] oltp:
Which OS are you using? I got absolutely no problems on XP SP2

M
[JAM, MDA Compact, S100 Software Upgrading] c_shekhar:
I am also using Windows Xp pro with SP2 with firewall turned off. The file system is NTFS.

2 Even the 113WWE_BIG_Storage_Shipped_rom.zip downloaded from ftp \upload\magician if loaded to device using ROMUpgradeUt.exe I notice again checksum error on all the three i.e. radio,CE image,as well as ms.nbf. I dont know what is happening. I think the something is wrong with nbfdec.exe.(Pl no offence be taken). Is there any improved version of nbfdec.exe available???????
[JAM, MDA Compact, S100 Software Upgrading] oltp:
You won't be able to offend me in this. Strange you got these problems, besides I mostly used it on a fat32 FS & haven't tried on NTFS we're using the same OS oh & I have a third party FW turned on.

There must be either something with your copy of nbfdec or with your setup, but I can't figure what. PM me your e-mail & I'll mail you the pack. BTW did you try the ftp lately? The newest upload ftp://xdaupload:xda@xda-developers.com/Magician/ seems to have worked & download is possible.

M
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] thekyguy11:
I've had my Note 3 for about 24 hours, and I'm having two issues with the lock screen. I use swipe to unlock, like I always used on my Note 2, and I don't know if this is a bug, or normal.

1) I've had the phone unlock in my pocket several times. Once it even posted a mood face to my G+ account, lol.

2) I can access the notifications from the lock screen, but I can't tap them and bypass the lock screen, like I could on my Note 2.

Any idea's?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] thekyguy11:
I noticed the home button sticks up a bit, compared to the Note 2, which was flush with the display. Is this to compensate for screen protectors? In still waiting for mine in the mail, so I don't yet know if that will affect my issue #1 listed above.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] derrtydee:
many of us preordered screen protectors and other cases and accessories long before we got the phone. just an FYI :)

as for your phone unlocking, do you have the extra sensitivity enabled?

Settings > Display > scroll to bottom and see if "increased touch sensitivity" is checked.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] thekyguy11:
Thanks for the tips. I disabled the "increased sensitivity" option, we'll see if that solves the problem.

Still can't figure out why notifications aren't actionable from the lock screen, even though I am not using a pin, pattern, or password.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] jmorton10:
I thought it would be kind of cool, so I went through the programming and set it up for my LG V and my time warner high def cable box.

Everything seemed to work, but now all it will do is change the channel on the box. The volume doesn't work, and if I go to turn off the TV it comes up with a screen asking which device I want to control but won't let me select either one.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] TomN:
I'm using it on a Samsung tv and a Comcast set top box, and it's working great for me.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Chocu1a:
ILO tv & comcast box. works great.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] darrbeck:
Lg and Panasonic tvs, both with com cast boxes are a no go.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ikithme:
Comcast box and Hisense tv, working.

Also have tvs at work, LG, all working (Around 10) with the same code sent on one of the tvs.

Pretty happy with this as now I can control my work TVs without having to fumble around with remotes.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] edwmsjr:
Two different Samsung TV models & two FIOS Multi-Room DVR's...all working great. Volume doesn't work, but that's because it's controlled by my surround sound system.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] ginger man:
Mine's the same way. Got cable working but now no volume.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Cauchon:
It works with my LG TV. I have a Comcast X1 and am able to change channels, but a lot of other buttons like menu and DVR don't work. Going to give the setup another go tomorrow.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] derrtydee:
I actually disabled it. I never used the app but apparently it was running in the background and I kept getting force close messages.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] billymaloney3:
I can get everything to work beside the volume on my Demon AV receiver. I can get it to turn on and off but not the volume. Can anyone give me advice on doing this?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Ibkevin:
Try again man but this time instead of picking comcast for the brand of set top box, go to other brands and scroll to find the actual company who made the box. For example I have comcast xfyinity cable as well and my 1st set up failed selecting "comcast" as the brand so I looked at my receiver and it was made by Scientific Atlantic or some shat like that lol. But it worked choosing it that way. Hope this helps u?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] jmorton10:
That's what I ended up doing too....
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bskarpa:
Mine works just as good as my s4 which was awesome
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Gvaz:
Works fine for me.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] rsohne:
Mine works fine but the ir seems very week.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] buzzdroidx:
I have a samsung tv and motorola box through cox. The tv works, but choosing motorola will not.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] wrichards2009:
Yeah my blaster only works about 7-8 get from the tv
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Han Solo 1:
Sharp Aquos and TiVo, working great