yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Q&A, Help & Troubleshooting] abdel12345:
This might be better in the nexus 4 thread since that's where the data actually comes from so someone from there might be able to help better. I don't use tethering much but maybe you can try one of the tethering hotspot apps?
[Nexus 10 Q&A, Help & Troubleshooting] mark manning:
Possibly but from what I understand tmo blocks it server side these days therefore something on the N10 will have to be changed

Sent via mobile
[Nexus 10 Q&A, Help & Troubleshooting] mark manning:
You were right... I think. Has something to do with APN setting in kit kat

Sent via mobile
[Galaxy S III Q&A, Help & Troubleshooting] migasbr:
Hey guys!

I'd like to ask a question... I recently got a Samsung SIII, which I have rooted already and installed S4 Glance ROM, which takes quite a bit of the internal SD card, so I decided to buy an external SD, just to find out thar it's rather difficult transfer the Apps over there!....

One of my Apps is Ndrive and I have 2 maps installed, which take together about 500Mb.. So, my question is: Since I have purchased the External SD card, is there any way of putting the maps in that card and make Ndrive to find it?..

If You can help, I really appreciate!! :cool:
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Ask in the NDrive support/ forum . Many map apps do not allow transfer .
[JASJAR, XDA Exec, MDA Pro General] thefixer:
:cry:

I've had my Qtek 9000 for a week. I've spent most of that week installing software, and getting it setup (using a lot of useful info from this site).

This afternoon it locked up, and wouldn't respond to any button presses (including the on/off button)

Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text.

Eventually, I tried a hard-reset. Same thing happens - process goes ok until it displays the ROM version, when it just sits there. I've tried removing the SD card and SIM card and hard-resetting. No Joy.

I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence (surely a hardreset should fix anything bad that happened there?)

I hadn't at any point played with the ROM.

What should I try next?

And, does anyone know if I'm going to be able to get support for this in the US from Qtek? (I bought it in the UK), new

Thanks in advance.

-Steve
[JASJAR, XDA Exec, MDA Pro General] FOSA:
RE

Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?

It may work :D
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Re: RE

Unfortunately, no such luck :(

I'd tried that before, but the battery was only out for a short time. This time it was been out for at least 15 minutes.

Does anyone know if there's any kind of hardware or diagnostic test mode it can be booted into?

-Steve
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
How about updating/upgrading thr ROM?

This might work. you'll have to reinstall everything again, though
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Thanks - I may try that tomorrow. However, I'm a little concerned that updating it with a new ROM might invalidate the warranty (especially if it's not a QTEK ROM)

I was hoping that there was some kind of hidden 'diagnostic mode' I could try first, before taking that step. I've also been looking everywhere on the web, and I can't find anyone else that this has happened to. This makes me think it may be a hardware problem, though the way it just 'happened' seems more like s/ware.

Anyway, I'm out today so this will have to wait until tomorrow. My biggest concern at the moment is how I'm going to get any warranty support in the US. All I have at the moment is a very expensive brick!

-Steve
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
Have you tried entering bootloader mode?

BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE

Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:

__ + __ + RESET HOLE

Hope this helps. WHat's your ROM verison/language anyway?
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.

Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?

R 1.03.00

G 42.36.P8

D 1.13.64 WWE

Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!

-Steve
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Jorgee,

I notice (in the HTC 'confidential' manual I just downloaded) that there is a diagnostic program. Apparently, I put it on an SD card, and do Power+Backlight+reset to invoke it.

Do you know if that diagnostic tool is available anywhere on here, or elsewhere on the web?

Also - I wqas trying to find exactly how to enter 'bootloader' mode (after I have the 'serial' screen). Should it boot differently from here when doing a hware reset (_+_+reset)?

Regards

Steve
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?

Do the following once you get the SERIAL ON THE SCREEN:

1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.

2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.

3. Run the ROM Upgrade (whichever it is you chose).

This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.

If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Hi Jorgee,

I'd prefer to go for the QTEK Rom (I'm assuming, from the info I posted above that I currently have 1.13.64 WWE). I'd like to go for the same or later version of this, but looking on the ftp site here I can't see ay QTEK ROM upgraders.

I have checked that when I plug in the USB I get 'USB' appearing on the screen, so I'm hoping that a ROM upgrade will at least work, even if it doesn't fix my problem.

One other thing that concerns me. When I plug into USB (with either a PC or the AC charger) the LEDs aren't lighting to indicate it's charging. Obviously, when during the flash upgrade I should make sure I have a reasonably charged battery. However, I don't know if I do (or even if it's currently charging).

-Steve
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.

ftp://xdaupload:xda@ftp.xda-developers.com/Universal

Under Shipped ROM's you should see the QTEK.

If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Thanks - I'd already found it on the devbuzz site, and am currently giving the unit an hour or two's charge before trying this. Wish me luck!!

-Steve
[JASJAR, XDA Exec, MDA Pro General] thefixer:
OK, here's what happened when I tried to update with the same Qtek firmware:

Initial dialog (that shows old and new (to be installed) firmware versions had blanks for all three firmware versions currently installed.

Started the upgrade, and left it running (couldn't bear the tension of watching!). Came back, and found the following error message displayed:

"Error 113: Extended ROM Update Error"

The update tool indicated that I should 'try again'. I'm currently re-charging the unit, and hoping (against hope) that this error was caused by insufficent battery charge.

-Steve
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
[JASJAR, XDA Exec, MDA Pro General] thefixer:
:cry:

No luck.

I've also tried re-flashing a second time, but this time I watched it to see what happens

As the radio firmware is flashing, a message to that effect is shown on the Qtek screen. Once that is finished, the upgrade tool starts the extended ROM flash. At that time the Qtek's screen goes completely blank. The, after a minute or two, the upgrade tool reports that the extended ROM failed to upgrade.

I am assuming that normally, while flashing the extended ROM, there's a message on the phone's screen to say what's going on?

I'm also wondering whether to have a go at flashing the ROM in one of the other ways?

-Steve
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:

Radio : radio_.nbf

OS : nk_.nbf

Ext : ms_.nbf

I just rename/move/delete the MS and NK files then run the update
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Thanks Jorgee. Still no real success, but I think I might be getting closer.

I've tried the above (using both the original romupdate_ut.exe and MaUpgradeUt_noID.exe - same results with both).

I've tried each of the three files individually (using the ones from the shipped ROM, as downloaded above)

radio_.nbf always seems to flash ok

ms_.nbf always fails right at the start, and nothing appears on the phone's screen

nk.nbf almost worked. It started, and got up to 87% (tried this 3 times), with the update showing on both the phone screen and PC. Then it failed with error 112, leaving the '87% complete' message on the phone's screen.

Soft or hard reboots still result in us just ending up 'hung' at the boot screen.

Once again, thanks for your help so far. However, I am beginning to give up hope!

-Steve
[JASJAR, XDA Exec, MDA Pro General] truongia:
I have the same problem with my Dopod 900 at post http://xdaforums.com/viewtopic.php?p=207524#207524

But mine is no problem with EXTRom Upgrade

Waiting for your advise!

Thanks
[JASJAR, XDA Exec, MDA Pro General] thefixer:
I wish I had a solution!!! I've spent about 20 hours trying to get this thing to boot!

One question though - how did you get the 'boot option' menu up (allowing you to clear the registry etc). I might try that on mine (I had assumed that a hard reset ALWAYS cleared the registry.

Given that I was playing around with ozvga before this happened, there's a small chance that might help (though I think not; as I can't see how that would also stop the flash update working)

-Steve
[JASJAR, XDA Exec, MDA Pro General] damianbyrne:
@ TheFixer

I have the same problem with a Vodafone branded device (v1640), I have tried everything to no avail, I have spoken to Voda who are arranging a warranty swapout. If your device is under any kind of warranty (and it should be), I dont think they will be able to determis which ROM you had installed.

DB
[JASJAR, XDA Exec, MDA Pro General] thefixer:
I think that with the Universal, they would know.

Currently, when it (tries) to boot it always 'hangs' at the boot screen, which shows the Qtek logo (and also the ROM versions). I'm assuming that if I managed, even half successfully to flash someone else's ROM (e.g. JasJar) that logo would change - which (if it didn't fix the problem) would leave me with a warranty issue. I have, I admit, been tempted to try someone elses firmware just to see what happens...

One thing that is puzzling me, and might even be a clue

The boot screen still shows the ROM versions (as red text) when it hangs.

When I use the flash upgrader, it shows blanks for the currently installed firmware (all three files), and following last night's experiments I would have thought that I probably didn't have anything meaningful in the extended or OS ROMs - but the boot screen still shows the same versions.

I'd also like to try doing an install from SD card, but am nervous of doing that when I'd have to 'handcraft' the files on the card.

Does anyone know if there's a file set (zip/rar) that I could put onto an SD card that is effectively the original (or perhaps later) QTEK ROMs? (I've been unable to find one). Perhaps someone (with a working Qtek9000) could do that, and post the zipped fileset online?)

(Where's buzz_lightyear when you need him?!?)

-Steve
[JASJAR, XDA Exec, MDA Pro General] Moandal:
I think you're wasting your time trying to fix this. I had exactly the same problem and we're not the only ones. It looks like a fault with the Universal hardware. I got mine exchanged under warranty and the replacement has behaved itself perfectly. Also I had done almost no customisation on mine when it croaked after less than a week.

See the following topic:

http://xdaforums.com/viewtopic.php?t=34912
[JASJAR, XDA Exec, MDA Pro General] Urban Strata:
Sorry to hear about your troubles, thefixer. :(

I had this same problem within 4 days of owning my first Qtek 9000. I had to send it back under warranty (Dead On Arrival) and got a new one. The replacement has functioned perfectly now for almost two months.
[JASJAR, XDA Exec, MDA Pro General] thefixer:
I'm beginning to see a pattern here!!! (looking at the posts above)

I notice your in NYC (I'm in CT, but bought my unit in the UK over Xmas). Where did you send your unit to? (Would Qtek support you directly in the US?)

-Steve
[JASJAR, XDA Exec, MDA Pro General] truongia:
I read HTC_CONFIDENTIAL_-_UNIVERSAL_SERVICE_MANUAL.pdf it show me as following:

System hang at booting - System boot up but lock on LOGO screen

Solution is

1. Reset the device

2. Re- flash Software

3. Main Board defects

Truongia think the defects is RAM (DiskOnChip) so the last solution for truongia and Thefix is try to Reflash back to Origin Software for warranty.

Have fun.
[JASJAR, XDA Exec, MDA Pro General] thefixer:
I never had SO MUCH fun <g>

Thanks for the suggestion, but unfortunately I can't flash new firmware. The radio firmware will flash ok, the extended ROM won't (at all) and the OS will flash to 87% then fail every time.

I am going to try the Softreset+light to clear registry etc in a moment

-Steve
[JASJAR, XDA Exec, MDA Pro General] Urban Strata:
I purchased my device through MadMonkeyBoy (David Weineger) in New Jersey. I sent the faulty unit back to him, and he sent it on to Sound Solutions in Nevada for reconditioning. David had a brand new Qtek 9000 in my hands the very next day.

I was one happy customer! :D
[JASJAR, XDA Exec, MDA Pro General] hdubli:
I too have sama kind of problem....But it occurred after 4 months of use..I trieds all...my device even gets flashed...but it stucks at the I mate boot screen...It seems that as per the Manual...I hv the Main board problems....but I don'nt see any...I am totally disappointed..
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Wow - sounds like perfect customer service. I'm beginning to regret having bought mine while in the UK over Xmas (I'd wanted to touch/feel one before I bought, and once I had it in my hands, I couldn't resist...

However, I've dispatched it back to them today, and we'll see how it goes...

-Steve
[JASJAR, XDA Exec, MDA Pro General] Urban Strata:
Perfect customer service? Yes! Buying my Universal from MadMonkeyBoy was one of the easiest / cleanest / most seamless online purchases I've ever made. Amazon.com and Target.com have something to learn from David Weineger as far as customer service is concerned.

I've said it before, and I'll say it again, MadMonkeyBoy is the way to buy Pocket PC Phone Edition devices if you're in the U.S.! See his feedback on HowardForums here: http://www.howardforums.com/showthread.php?t=528018&highlight=madmonkeyboy

And no, I'm in no way paid by MadMonkeyBoy / David Weineger. I'm just a guy who's so happy with his purchase and the customer service that he wants his reseller to have great future success. Cheers!
[JASJAR, XDA Exec, MDA Pro General] thefixer:
Well, I wish I'd known that before purchasing - but there again, I'm sure you understand that feeling that comes over you when you've got the new toy in your hand!

Incidently, I notice you're on T-Mobile. Although I'm based in CT, I travel a lot to some of the more remote places in the US (KS, OK, TX - basically anywhere there's oil or gas). Looking at T-Mobile's coverage, I'd decided that Cingular was the only way to go (though I liked T-Mobiles prices). Have you had a chance to try it in the sticks? (I'd wondered whether it just roamed (with no extra charges) onto Cingular anyway, so there's no real difference)

-Steve
[JASJAR, XDA Exec, MDA Pro General] Urban Strata:
I actually switched from Cingular to T-Mobile for the Universal, and I've been extremely pleased with the decision. I find T-Mobile's coverage and reception to be better than Cingular's despite what everyone says. It's crystal-clear in Manhattan, and I've had no problems when traveling to San Francisco (including San Mateo and San Jose), Atlanta, or a small town south of St. Louis called Imperial, Missouri. In fact, my reception in rural Missouri was actually better than when I had Cingular!
[JASJAR, XDA Exec, MDA Pro General] xp:
...

I have the same problem with my T-mobile MDA Pro!!! But for sales returns of Universal I need an original ROM from deutschland T-mobile MDA Pro, but I can not find it.. :evil: I don't know what can I do now.. :oops:
[JASJAR, XDA Exec, MDA Pro General] tomsyota:
Guess it's a little late now that you've already sent it back but I've had problems when doing radio upgrades with the device hanging in the bootloader mode and the ROM Upgrade Utility giving me all sorts of errors. What I did to fix it was:

1. Try to install the upgrade normally.

2. When the ROM Upgrade Utility gave me errors, I soft reset my device (and it promptly entered the bootloader mode again).

3. I deleted all the files on my desktop PC that the ROM Upgrade Utility had installed, redownloaded the ROM/Radio Upgrade, and ran the utility again.

4. It would display [blank] and [blank] for the "current version" "upgrading to" versions but when I clicked next it would install the new ROM or Radio upgrade just fine.

5. Soft reset (for radio only upgrades) or hard reset (for ROM upgrades) the device and hopefully it will work.
[JASJAR, XDA Exec, MDA Pro General] zwuncki:
i tried everything from flashing new radio (failed first from there on i couldn't get beyong the qtek bootscreen. second try worked but still no change), complete new rom (worked too). HR, SR. charging (no LED), removing the battery for several hours.

still nothing (german Qtek 9000), now do i really have to get it exchanged for a new one (2 days old)? damn, no other solution? :(
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
Just curious, do you enter bootloader mode BEFORE you did all of the above updates? This is the screen that says SERIAL/USB on the screen but there is no backlight.
[JASJAR, XDA Exec, MDA Pro General] zwuncki:
yes.
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
How about flashing to IMATE or O" by using the 55+MB exe file?
[JASJAR, XDA Exec, MDA Pro General] zwuncki:
I tried the german mda pro update exe which failed because of ID error. don't know about the others because I don't think german language is included. shall i really try? if so country error ID will definetly be a problem again. can't use the MAupgradenoID.exe cause all the stuff (imate, mda pro etc.) are exe files.
[JASJAR, XDA Exec, MDA Pro General] Jorgee:
These exe files CAN be uncompressed/extracted to a directory using winzip, then copy the MAUpgradenoid to that directory and run it from there :D
[JASJAR, XDA Exec, MDA Pro General] zwuncki:
thx, i'll try some different roms but from what I've read here i don't have much hope for my qtek to not be exchanged.
[JASJAR, XDA Exec, MDA Pro General] zwuncki:
tried many roms, none worked.
[JASJAR, XDA Exec, MDA Pro General] BeAsT:
I've only just aquired one of these devices and was gobsmacked when my system crashed and hung at the boot screen. I read through all the forum posts in an effort to get my o2 XDA Exec up and running again. Most of the posts here left me baffled as to what the hell to do next :?

I d/loaded xda_Exec_LaunchROM_v113139 from this site. I didnt have my IMEI number to obtain access to the o2 site :( and did a normal rom instal without flashing anything- just a straight install. After a hard reset it booted up fine!!

Once i had access to my XDA i went to the o2 site and obtained the latest ROM and installed that.

Up and running without having to edit anything with other software etc. (and yes the o2 GPRS monitor works with the new ROM :lol: )

This worked for me .... so i hope it might help someone else...

Regards :lol:
[Galaxy S 4 Q&A, Help & Troubleshooting] uberto.costanzo:
hi after official update Samsung kies no work, does not recognize phone. why ? is normal? any help please. thanks fo reply
[Galaxy S 4 Q&A, Help & Troubleshooting] danum:
Are you still using version 2?

I had to update to version 3.
[Sprint HTC EVO 4G LTE] Dom42:
sup, so I can swap my current htc sensation for the evo lte for a small fee, im short of cash so newer ones like the One or Note 3 are out of my possibilities for the moment and others either dont have microsd slot or have onscreen buttons (N4) or have amoled which I dislike (S3 Note 1/2) or are a step backwards in general. The evo lte is very tempting for me right now, awesome screen, microsd, ok performance considering im happy now with my senny and the evo is faster, capacitive buttons, and its actually cheaper than the One X, also im tired of the mediocre 3g gsm support in my country and i´ve heard very good things about cdma carriers here.

What I love about my current phone is the still active dev community, removable battery, how easy it was to unlock and s-off, perfect size not too big not too small, durablity (I have dropped it countless times, the metal back does help) .What I never liked was the so-so screen and meh performance until 4.2, the deathgrip and bad battery life.

I have some questions.

How easy is to properly s-off this phone?

How´s the dev support? I know this one has 4.3 and 4.4 already but how well do they work?

What are some pros and cons that are rarely discussed in your opinion?

Deathgrips or anything like that?

Any known bug bricks like some samsung phones?

Is it easy to unlock?

thanks in advance :good:
[Sprint HTC EVO 4G LTE] iandmacdonald:
I've had four of this phone since its release. Great phone, fast for an everyday phone. I don't game or anything, so can't speak for that. I have a lot of apps and Viper for my rom, and my phone is not far from having all of it's memory used up. There are tricks of swapping the sd card for internal, etc. Easy phone to root and s-off. Get the Otterbox Commuter and enjoy the phone.
[Sprint HTC EVO 4G LTE] premo15:
I've been pretty happy with mine, but keep in mind that this phone is nearing end of life. We're supposed to get an official OTA with 4.3 and sense 5 in the next couple of months (January last I heard), but that will likely be the last.

Unlocking is pretty straight forward, but getting s-off somewhat depends on which hboot version you have. I believe there are currently methods for all versions, but that may change after the next OTA.

The dev scene is still kicking, so there are plenty of stable 4.3 roms out there already if you don't want to wait for the official. CM 11 (4.4) is in the works but not quite a daily driver yet from what I hear.

My only complaint is with the cell radio strength. I get pretty bad reception most of the time unless I'm in a big city...It's more a problem with Sprint in general but plenty of people have reported getting stronger signals on Samsung phones sitting right next to the evo lte.

Sent from my EVO LTE