yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario General] truxntrax:
Hope someone can help. I am evaluating 2 devices (Qtek 9100 with a standard UK Vodafone Rom and a UK Orange M600). On the M600 when using Tomtom I get the option to connect an Other NMEA GPS receiver I have the option to select "Serial on USB". However on the Qtek 9100 this option is not available.

Can anyone advise if this is a limitation of the Qtek 9100 or is it a limitation of the ROM I have installed.

Thanks
[8125, K-JAM, P4300, MDA Vario General] Beeble:
AFAIK you cant connect a serial USB to the Wizard.

I dont believe this is a ROM issue but a hardware one.

Hope it helps :)
[Sony Xperia Z Ultra] beerope:
How can i get the camera to be as good as the first 2 roms ever released?
[Xperia Tablet Z Q&A, Help & Troubleshooting] Avishay.a:
Hi all,

I have Sony Xperia Z Tablet which I want to gain root access for.

Device details:

Model number: SGP311

16GB

Android 4.3

Build Number: 10.4.B.0.577

Not sure if relevant, but the tablet was bought in USA.

I'm pretty much a newbe here, so I would like, if possible, to get a link for a simple tutorial how to root my device.

10'x! :)
[Xperia Tablet Z Q&A, Help & Troubleshooting] Felimenta97:
If only there was a search button...

http://xdaforums.com/showthread.php?t=2588442
[Xperia Tablet Z Q&A, Help & Troubleshooting] Avishay.a:
Hi Felimenta97,

Thanks for your reply.

I have seen the post you've linked here before I've posted my question (I definitely know how to use the search option :cowboy:) but its seemed somewhat complicated/Indirect way compare to the simple ways of rooting I'm used to from my 2 other devices (SGS3, Nexus 4)

Is there any simpler/straightforward way?

Thanks in advance!
[Xperia Tablet Z Q&A, Help & Troubleshooting] Felimenta97:
Nope. There is no current exploit in 4.3 Sony firmware. So, you either unlock your bootloader, or do that process.
[Xperia Tablet Z Q&A, Help & Troubleshooting] Juampo-CHILE:
Wait till 4.4!

If I was you, I'd wait till KitKat upgrade comes out! after that I'd root my tablet :p
[Xperia Tablet Z Q&A, Help & Troubleshooting] Avishay.a:
Why? :confused:
[Xperia Tablet Z Q&A, Help & Troubleshooting] Avishay.a:
What about Kingo App?

You think it might do the work?

www .kingoapp.com/?utm_source=Android%20ROOT
[Xperia Tablet Z Q&A, Help & Troubleshooting] Juampo-CHILE:
Because You'd lose the root if an incoming update comes :p
[Xperia Tablet Z Q&A, Help & Troubleshooting] Avishay.a:
Isn't that almost always the case with updates?

Anyway, has anyone tried to root this tablet on 4.3 with Kingo App or VROOT?

10'x all for your help!
[Xperia Tablet Z Q&A, Help & Troubleshooting] Juampo-CHILE:
I tried with VROOT, but seems like there's no update yet. Was researching about 4.3 root methods, there a few, most of them you have to go back to 4.2 and then upgrade, but a direct root, no, I haven't found one yet :good:
[Xperia Tablet Z Q&A, Help & Troubleshooting] Avishay.a:
Is there any simple way to root this device?
[Xperia Tablet Z Q&A, Help & Troubleshooting] Rootk1t:
Use EasyRootTool v12.1
[Xperia Tablet Z Q&A, Help & Troubleshooting] MikeViller:
sorry wrong firmware version I am on 4.4.4
[Xperia Tablet Z Q&A, Help & Troubleshooting] Rootk1t:
http://xdaforums.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
[Verizon Samsung Galaxy S III] Whisk_33:
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.

What wont work: Flashing to CM11 does not change the issue.

Disabling Voice+ does not change the issue

Factory Reset does not change the issue

Workarounds: Toggle Airplane mode

Switching Mobile Network to CDMA only (not permanent)

Change your number to a different area code

Going back to a Touchwiz based ROM

The Solution

Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
[Verizon Samsung Galaxy S III] jugsins:
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.

Stock 4.3 is kind of lame:

-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.

-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.

-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.

Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already :(
[Verizon Samsung Galaxy S III] Whisk_33:
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://xdaforums.com/showthread.php?t=2654822

It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...

Edit: And another thread http://xdaforums.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.

edit2: and another thread http://xdaforums.com/showthread.php?p=50627899
[Verizon Samsung Galaxy S III] S52Stu:
Just looking for more info
[Verizon Samsung Galaxy S III] Whisk_33:
SO this is the current status that I know.

The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).

Current Workarounds:

Switch to TouchWiz based Roms

Switch your radios to be CDMA only

Call verizon and switch your number to a different area code

I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
[Verizon Samsung Galaxy S III] S52Stu:
I'm 717
[Verizon Samsung Galaxy S III] Whisk_33:
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.

And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
[Verizon Samsung Galaxy S III] S52Stu:
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
[Verizon Samsung Galaxy S III] DreamFX:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://xdaforums.com/showthread.php?t=2662658
[Verizon Samsung Galaxy S III] Whisk_33:
Godspeed my friend.
[Verizon Samsung Galaxy S III] DreamFX:
Anyone try aosp to see if fixed yet?
[Verizon Samsung Galaxy S III] capt730:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
[Verizon Samsung Galaxy S III] DreamFX:
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
[Verizon Samsung Galaxy S III] capt730:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
[Verizon Samsung Galaxy S III] Obaterista93:
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
[Verizon Samsung Galaxy S III] capt730:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.

*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
[Verizon Samsung Galaxy S III] Obaterista93:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
[Verizon Samsung Galaxy S III] capt730:
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
[Verizon Samsung Galaxy S III] Whisk_33:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.

I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
[Verizon Samsung Galaxy S III] Obaterista93:
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.
[Verizon Samsung Galaxy S III] net-cat:
Yes. The ROM I linked is just a normal recovery-flashable ZIP file.

Doing that worked for me, but I lost my GPS when I did that.

It is, and I thought that too. But I've had subtle issues come up when I switch modems. (The most obvious one being losing GPS.)

The important steps here seem to be "flash to a stock rom and radio, then go through the provisioning process." After that's done, you can flash to any ROM you please.

The root66 flash worked, but left you with a very old radio (VRALF2.) It also locked your bootloader again.

Since using root66 and updating to VRBMB1 cause other issues, I started looking for a stock ROM that originally shipped with VRBMB1. I stumbled on Scott's stock ROMs, which contained bare minimum customization. (Essentially, stock 4.3/TW with root built in.) It was a hell of a find, too. I could do the procedure without changing my recovery or relocking my bootloader.

The problem seems to come up with VRBMF1 radios. (Though I guess people have had issues with older ones. I was actually on VRBMB1 when the issue first appeared. VRBMF1 seems to be fairly common.)

I would be curious to see if provisioning from a stock ROM running a VRBMF1 radio and then switching to CM11 would still have issues.
[Verizon Samsung Galaxy S III] dmginc:
All you need to do is Odin to the root66 ROM, provision the sim card, then take the OTA's to 4.1.2. From there it's gravy. Root it, unlock boot loader, and flash cwm via the casual one touch method (then you MUST update cwm to the latest). Install whatever ROM you want, the latest gapps, and then the AIO firmware provided by Invisiblek. The sim provision fix will carry over through ALL of this.
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
There have been many people who have stated that MF1 or even MB1 do not work with this fix and the problem returns before long. I myself have tried MF1 with no luck, the problem returned and I had to re provision again to get texting back.
[Verizon Samsung Galaxy S III] dmginc:
Returns after flashing a nightly of something?
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
Returns after flashing ANY aosp rom. No issues with tw as usual. :eek:

have you had luck with it staying fixed on mf1 or mb1? if so, what method did you use?
[Verizon Samsung Galaxy S III] Whisk_33:
Follow the method listed in the OP. Once you are finished you can upgrade to MB1. This fix should stick through reboots and AOSP rom changes.

For some reason some people have problems on the MF1. Don't flash it.
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
thanks sir ill have to try this when i get some time. So just follow the op directions then? Backup, flash mb1 aio and then flash 4.3 stock rom? seems too simple ....lol
[Verizon Samsung Galaxy S III] Whisk_33:
If you like, I can post my older more complicated method... This appears to be all that is necessary. Flashing MB1 takes gets rid of the MF1 package which is causing the problem. Flashing back to a TW rom and letting it boot up will re-provision the signals/codes/magic and unicorns.

Then you can go back to a CM rom. It seems to stay fixed as long as you don't flash MF1. Let us know if you run into problems.
[Verizon Samsung Galaxy S III] Foy1der:
The link for the radio download doesn't work for me. I get a 403 error. Do you perhaps know if registration at rootzwiki is required in order to fetch the file?
[Verizon Samsung Galaxy S III] buffal0b1ll:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
[Verizon Samsung Galaxy S III] Jaggar345:
This issue is also happening with the HTC Droid DNA for people loving in VT and PA so it's something with the network in those areas. In the DNA forum the only option to fix it is running the stock rom. I believe Verizon is finally cracking down on users who modify their phones. Thank God I'm leaving as soon as my contract runs out. I have a feeling they will be slowly implementing this in all of the United States.
[Verizon Samsung Galaxy S III] Whisk_33:
The fix for the GS3 seems to suggest that the issue might lie in the MF1 AIO. Try and follow the direction listed OP and see if you can modify the method to fit your phone. That would be much more valuable to the community on both forums.
[Verizon Samsung Galaxy S III] Supercutetom:
Personally I hope more devices get hit with this issue so we can gather more attention and hopefully a fix from someone who has more expertise! I don't want a new phone. I love my GS3 and this gal has plenty of life left in her, yet.
[Verizon Samsung Galaxy S III] mdphoenix:
This is such horse****. I hope everyone gets hit with it as well. I'm so fed up with the "It's our way or else" mentality.

WTF is it hurting them if we modify our phones? Next we won't be able to install third party apps on our laptops using FiOS?

Eff this.
[Verizon Samsung Galaxy S III] johndiblasi:
I took the plunge and moved to a touchwiz rom . When I did that I updated to the latest modem. When I got tired of it so I flashed an aosp rom. SMS fail after one text. I have a 570 number and a 717 Google voice number. Frustrated I moved back to my touch wiz rom.

FIX:

What worked for me. While I was still on touch wiz I downloaded the MB1 modem from buffal0b1ll's post. Boot into recover, flashed modem, wiped cache and dalvik and rebooted back into my touch wiz rom. Sent 3-4 text to my wife and myself. Went into maps and had it lock my location. Rebooted into recovery wiped data/factory rest, flashed my new aosp rom and gapps then rebooted.

3 days strong with no issue. Sms has been working fine. On a personal note don't flash anything higher than MB1. It will bork. The best part is I didn't have to Odin anything back to factory.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Just making you aware, wiping is unnecessary when installing modems or firmware. Wiping does not reach the partitions that are updated when installing firmware.
[Verizon Samsung Galaxy S III] johndiblasi:
I understand that. But moving from one rom to another should always have a full wipe
[Verizon Samsung Galaxy S III] NeoMagus:
Well looks like I ran into this situation as well, gave my wife my S3 after moving to the Note and shes on a d2vzw cm11 build 2/8 and texts apparently stopped working after the first text is sent in stock sms app. Following the method in this thread I:

Flashed MB1 firmware ( was on ML1)

Backed up current CM11 build with a nandroid.

Wiped data/cache, then restored to my original TW nandroid ( this was not 4.3, it was my original nandroid from when I first got the phone, and switched over to CM)

Booted into TW, and sent a few texts to confirm it was working.

Started Recovery, Wiped data/cache, then restored my CM11 nandroid.

Booted back into 4.4.2, texts seem to be sending and working normal again.

Just wanted to say as long as its a TW rom you go back to looks like it will do the trick as my nandroid was from the original TW (LG1) that came with my phone when it was released
[Verizon Samsung Galaxy S III] :
I cant seem to figure out what i am doing wrong

I can not get any TW rom to flash my original recovery image the rom OP used nothing
[Verizon Samsung Galaxy S III] Whisk_33:
I'm not clear on what you are saying. ROMs don't flash ROMs recoveries do. If you have a nandroid backup you can restore that via what ever method you like. The ROM listed in the OP is if you do not not a nandroid already. You should be able to flash that ROM and follow the directions in the op to fix the issue. If you have any specific questions please ask.
[Verizon Samsung Galaxy S III] :
I have a Flashable image of my stock Rom and a nandriod as well as the Rom op suggested they all get to the splash screen before the boot animation no further

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] gt43aw:
I've been on tw for the past month or so since this issue started to affect me. I haven't had time or desire to nerd out and try to fix. So last night I broke and flashed mb1 aio on the tw ROM. Rebooted. Then rebooted again into recovery and flashed cm11 m6. Texting works great now. None of the odining stuff. I haven't bothered flashing another modem. Inclined to stay where I'm at. Just wanted to report to contribute!
[Verizon Samsung Galaxy S III] Whisk_33:
It sounds like you are having issues loading ROMs. You'll have to get that straightened out before fixing the text issue.

Once you get back on TW get to flashing the mb1 modem and you should be good to go.
[Verizon Samsung Galaxy S III] capt730:
I can confirm that for me, flashing the MB1 AIO on a TW Rom (I was on Alliance 23) and then flashing AOSP rom (PacMan) that texting works as it should. Haven't had time to try another AOSP rom yet. So nice not to have to go through all the ODIN'ing etc...
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I've done the everything up to rebooting into the stock rom...however it is hanging for me a the Samsung Galaxy S III screen. Any ideas on what to do???
[Verizon Samsung Galaxy S III] Shakes The AssClown:
So I fixed my issue...I made a nandroid backup of SlimKat. I downloaded the BMB1 image. Flashed it with Odin...rebooted...rooted with Casual...downloaded ROM manager and updated to the latest CWM..went into CWM...restored my backup...been texting with no issues.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I did mostly the same thing and I have been issue free on SlimKat for the last couple weeks. I have clean flashed SlimKat 4.8, 4.9, and 5 with no sms issues since I installed the VRBMB1 firmware. I opted to avoid Odin route, didn't feel like digging out my Windows machine :laugh::laugh::good:
[Verizon Samsung Galaxy S III] capt730:
I did the same thing here. On a TW Rom (I was on Alliance), dl the MB1 aio and flash in recovery. Rebooted into my TW rom and sent/received multiple sms/mms. I have since tested CM11, Pac-Man and C-Rom and all have worked flawlessly. It was nice to not have to Odin anything. :good::good:
[Verizon Samsung Galaxy S III] TotallyAnxious:
So I might have found another fix.

Starting from ML1 on 4.4.2 C-rom I did this

1. Reflashed ML1. Reboot. Still just one text.

2. Flash MF1. Reboot. Still just one text.

3. Flash MB1. Reboot. Still just one text.

4. Reboot. Texts work on LTE.

I don't know if all these steps are needed, but this is what I did, and it's fixed. :P

I might see if reversing the order works to get back to MF1 or ML1 later this week. But I might not lol

I'm using Textra, if that matters.
[Verizon Samsung Galaxy S III] plyduster73360:
same issue

hey guys im also having the same issue it has to be the network i live in augusta wv and work in winchester va when im roaming at my house i cant text all i want but the min i come in contact with verizon network it lets me send one then i have to reboot my phone to get it to work again im running pac rom 4.4.2 from may 19 been having the same issue with any rom i have flashed i just wanna know if its just samsung phones that are having the issue or if its all types o by the way im on a 240 area code
[Verizon Samsung Galaxy S III] Whisk_33:
Read the OP. Follow the directions. The problem only exists on cyanogen roms, what you are reporting sounds different. IF you are having the same problem it will be fixed if you stay on the MB1.

The problem is mostly on GS3. Some other phones have retorted similar issues. No one is positive. It is NOT geographically/local network related.
[Verizon Samsung Galaxy S III] plyduster73360:
Thank you whisk it fixed my problem it must be the new radio
[Verizon Samsung Galaxy S III] esjames:
I'm making a stab into the dark here,

Can someone give this a test while using the ML1 with aosp rom that was having the sms issue and report back and if it works with CDMA only or with LTE enabled.

http://buzzmobile.us/verizon-apn-settings-verizon-mms-settings-android-phones/

After doing this I can send sms using MF1 on cdma only route so far.

Please keep in mind your results may vary ;)
[Verizon Samsung Galaxy S III] dns2k:
I am currently manually set to LTE APN to have decent data(no voice) but earlier it would only connect to CDMA. This happened to the G next but I upgraded to the s3 and never solved it either. Going through threads now. But manual APN selection was only way to restore LTE. mf1 on PA 4.3 beta 7.

---------- Post added at 01:24 AM ---------- Previous post was at 12:59 AM ----------

A bunch of new APN settings posted across the net in march. Vzw I think tried to fix their issues with sim validation and because of that it broke us modders because every cm asop non validation baked in ROM didn't validate our connections and wither LTE or 3g broke with handoff. It became an either/or situation rather than an if/than one. So that's why we all felt the pain after the gnex users did.

---------- Post added at 02:01 AM ---------- Previous post was at 01:24 AM ----------

Also the Scott ROM link is dead be only goes back to mf1 now. Can anyone dropbox/mega a link to the ml1?

---------- Post added at 02:23 AM ---------- Previous post was at 02:01 AM ----------

http://www.androidfilehost.com/?a=show&w=files&flid=512Going to try BeansTowns106s roms. He seems to be the only one with links still working. And he seems to have it all. Props to him.