Okay, so I warrantied another m7 last week or so, and the replacement is now having one of the issues I got rid of the old one for.
I flashed the nusense 7 lp, and really enjoyed it, but like the last phone, about 3-4 days after it was up and running, any web pages I try to go to will time out after a couple of minutes of tether being on. Even without tether it won't connect to websites (using mobile data, the whole time) it also drops calls after a few minutes of talking. I've tried the steps listed in the FAQ thread to no avail, twice now. I tried another rom as well, thinking it might be that, no dice. Any idea what's going on or how to fix it?
I don't know if this helps any, but the first time it does this, windows complained about an IP address conflict. Even though tether worked great for 3 days straight.
Interesting development, I tried re-flashing nusense with the verizon kernel option selected today, and when it booted it said "this isn't a verizon sim card" or something to that effect, with no data or anything. So I went to a verizon store and got a new sim card, which solved nothing. Still no network connection (4g or otherwise) so I flashed candycat which brought back my data and everything seems to work. I don't know how long it's going to last, but I wonder if it would be safe to try reflashing nusense at some point?
Also, I wonder if I followed the (vague) steps correctly when I tried to repair this the first time. Assuming it was the corruption issue that the FAQ thread talks about, nothing I tried fixed it. That thread also says that it's a rare issue, but I had it happen with two separate phones, so does that mean there is something wrong with nusense? On my old phone I had been running a different rom for quite a while, but wanted to try out the newest android version. Unfortunately when I got my replacement phone, I had to use it for internet right away, so the only rom I still had on my computer was nusense. I don't know if there is something wrong with that build, but I am always careful to do MD5 checks.
Anyway, for now the phone seems stable, though I wish I had a less barebones rom on my phone. I'm just afraid it's going to start messing up if I flash something else. I also might switch from CWM recovery to TWRP, since I always had better luck with it.
All of Santod's roms recommend twrp. If you are flashing with cwm, that could be the issue. I suggest flashing the recommended recovery in the Rom thread if you decide to run nusense again.
Edit: nesense7 thread recommends the below linked twrp 2.8.3.0
http://forum.xda-developers.com/showthread.php?p=57813724
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
All of Santod's roms recommend twrp.
Click to expand...
Click to collapse
To be honest, I can't even remember why I didn't use it to begin with. Are these issues possible symptoms of that do you think?
Though I'm a little dubious that this is the cause, since I used TWRP on my old phone and updated it before I installed that rom. But I will definitely CWM cause I don't like it.
It could have caused the issue. If you feel adventurous, you can try flashing with the recommended twrp and see if that works.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
It could have caused the issue. If you feel adventurous, you can try flashing with the recommended twrp and see if that works.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I'm dumbfounded. So when I install nusense with the verizon kernel selected as an option, my phone breaks, either it won't fully boot, or if it does it doesn't recognize the sim card. However, if I then install another rom (or I'm guessing the same one, but without the verizon kernel) it works perfectly for a few days, I can tether, I can browse the web, I can reply to you. But it still breaks after a few days, and I need to "break" it again to fix it.
squat251 said:
I'm dumbfounded. So when I install nusense with the verizon kernel selected as an option, my phone breaks, either it won't fully boot, or if it does it doesn't recognize the sim card. However, if I then install another rom (or I'm guessing the same one, but without the verizon kernel) it works perfectly for a few days, I can tether, I can browse the web, I can reply to you. But it still breaks after a few days, and I need to "break" it again to fix it.
Click to expand...
Click to collapse
And this is flashing with the recommended twrp? How did you flash the recovery?
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
And this is flashing with the recommended twrp? How did you flash the recovery?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
adb.
squat251 said:
adb.
Click to expand...
Click to collapse
Are you on the latest firmware? Sorry for to my through the basic questions, just want to make sure everything is set right. I know you posted you got a replacement phone, but sometimes they can come with older firmware. Do a fastboot getvar all and be sure your firmware version is the latest from santod's thread of flashable firmwares.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Are you on the latest firmware?
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.13.41.0702
version-cpld: None
version-microp: None
version-main: 5.28.605.2
Correct recovery, correct firmware... Only other thing I could think of is bad download, but you said MD5 was good... I am stumped. Maybe @dottat or @santod040 would know another avenue to see why you are having issues with just one Rom.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Correct recovery, correct firmware... Only other thing I could think of is bad download, but you said MD5 was good... I am stumped. Maybe @dottat or @santod040 would know another avenue to see why you are having issues with just one Rom.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
No no, see I'm having trouble with every rom, that's the issue. I don't mind swapping to something else, but it's the same story no matter what I do. It will work fine for a week or so, but if I leave my house it will tether for about 5-10 minutes, then everything times out. Some times if I'm on like youtube, it will still load videos, but other times it won't. It doesn't matter what rom I'm running, this has been happening. And now I can't even fix it to work. This is driving me nuts.
As far as I know, it's not a defective phone, since the symptoms are the same between this refurb phone and the one I sent in. The issue only started after I installed nusense.
Related
Hey guys I was using mobile odin pro, getting ready to go back to stock but staying rooted. So i downloaded stock rooted rom and went to mobile odin. In mobile odin there is an option to wipe cache and dalvik cache so I checked them and hit wipe. I was on about 26% and it warned me that when flashing anything it's recommended to be atleast 50%. I continued anyway cause I was simply wiping cache. It began loading then said rebooting into recovery and never turned on. From what I see it looks like it might be hard brick (won't boot into download mode or recovery). I was wondering have any of you experienced this and is it stay repairable without jtag or do I have to send it to MobileTechVideos (again)?
Hope you guys can help, kinda ironic since I was trying to revert back to stock and stop flashing different roms all the time.
Wow I guess no one else has ran into this issue. Or maybe you guys are tired of so many bricked questions, as so am I, but I thought my case was different since it was from using mobile Odin app instead of the usual "accidently flashed an international rom, now won't boot" thread.
Sent from my PC36100 using xda app-developers app
Edit: Can a mod please delete thread if possible. Will just send in for repair, couldn't find fix anywhere.
re: your issue
Cyphers23 said:
Wow I guess no one else has ran into this issue. Or maybe you guys are tired of so many bricked questions, as so am I, but I thought my case was different since it was from using mobile Odin app instead of the usual "accidently flashed an international rom, now won't boot" thread.
Sent from my PC36100 using xda app-developers app
Edit: Can a mod please delete thread if possible. Will just send in for repair, couldn't find fix anywhere.
Click to expand...
Click to collapse
Your case is not that different than all the other cases similar to yours, you
either did not read all the instructions or you decided not to follow them.
Misterjunky said:
Your case is not that different than all the other cases similar to yours, you
either did not read all the instructions or you decided not to follow them.
Click to expand...
Click to collapse
Yeah maybe possible but they were rather shorts steps, I think they were about 6. Simply written too, don't think I missed anything. After reading online some, I've found that mobile Odin has been known of causing bricks on certain devices. Though the op of the thread said it worked perfect on his. It's ok though I'm just going to get it jtagged, then only rooting it on stock. Well until when TW 4.2 is available to us that is .
Sent from my PC36100 using xda app-developers app
possible option
You may be able to use a USB jig to get it into download mode to attempt to flash it back to working order. You can get them fairly cheap on ebay and i know you can make them if you have a little skill with a soldering iron and find the right thread. otherwise it's probably a no go....
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
It is a rooted samsung galaxy s4 M919 from t-mobile
is it stock rooted or what ROM are you running ?what kernel? what settings ? what mods? we need some detail sir but for starters if you can get it to boot try *#2263# and if its not set to automatic try clicking your options auto is the default setting
bobolinko said:
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
Remove your sd card sim card and battery let set 10 minutes put back in see if the message is still present if so you might need a new sim card.
Click to expand...
Click to collapse
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Might just be a lemon. I would just flash back to stock then take the phone and get a replacement.
bobolinko said:
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Click to expand...
Click to collapse
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
tylerholbrook said:
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
bobolinko said:
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
Click to expand...
Click to collapse
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
tylerholbrook said:
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Glad I could help. The modem isn't in your back up that's why back ups won't fix this problem. As for apps, it's from syncing your Google account. Aloha
Sent from my SGH-M919 using xda app-developers app
bobolinko said:
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Click to expand...
Click to collapse
If you chose to have Google back up and restore your apps, it will do just that.
This problem suddenly came out of nowhere.
I've had the same rom (paranoid android 3.99 RC2) running on my phone for 6 months and everything works perfectly until one day as I'm driving home the GPS goes wonky.
I restart my phone and then boom, no cell service on my phone.
I tried to:
wipe cache, dalvik
shutdown and reboot multiple times,
install a fresh copy of the rom,
tried other roms,
made sure i wiped system and storage when flashing new rom,
and tried to insert, reinsert sim card multiple times.
Strangely enough when this problem happens, the home button laso seems to act like its unlocking the device...
What do you guys think?
I'm thinking maybe I got some water on my device and ended up having it seep into the home button and the back of the device.
Sounds like a modem issue, might just need updating to the latest for you device...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
MiuKing said:
This problem suddenly came out of nowhere.
I've had the same rom (paranoid android 3.99 RC2) running on my phone for 6 months and everything works perfectly until one day as I'm driving home the GPS goes wonky.
I restart my phone and then boom, no cell service on my phone.
I tried to:
wipe cache, dalvik
shutdown and reboot multiple times,
install a fresh copy of the rom,
tried other roms,
made sure i wiped system and storage when flashing new rom,
and tried to insert, reinsert sim card multiple times.
Strangely enough when this problem happens, the home button laso seems to act like its unlocking the device...
What do you guys think?
I'm thinking maybe I got some water on my device and ended up having it seep into the home button and the back of the device.
Click to expand...
Click to collapse
Agree with the updating modem?
Have you popped open the phone and checked the water indicators ? Check for water invasion, that would answer whether it's a factor or not.
dicksteele said:
Agree with the updating modem?
Have you popped open the phone and checked the water indicators ? Check for water invasion, that would answer whether it's a factor or not.
Click to expand...
Click to collapse
I flashed to the stock rom and unrooted, which flashed the UCALJ2 Modem. It's working fine now on Paranoid 3.60.
I downgraded to that one since I never had any troubles with that rom, I kinda liked that version anyway,
but if I get any issues I will post here again.
MiuKing said:
I flashed to the stock rom and unrooted, which flashed the UCALJ2 Modem. It's working fine now on Paranoid 3.60.
I downgraded to that one since I never had any troubles with that rom, I kinda liked that version anyway,
but if I get any issues I will post here again.
Click to expand...
Click to collapse
Good deal.. I didn't mean to have a ? after Agree with flashing modem......
BTW, Baja has a great thread here....
http://forum.xda-developers.com/showthread.php?t=1987541
It has just the flashable modem zip's in there also.
dicksteele said:
Good deal.. I didn't mean to have a ? after Agree with flashing modem......
BTW, Baja has a great thread here....
http://forum.xda-developers.com/showthread.php?t=1987541
It has just the flashable modem zip's in there also.
Click to expand...
Click to collapse
That thread doesn't get updated often these days,
I317UCAMH3 , is the latest right?
MiuKing said:
That thread doesn't get updated often these days,
I317UCAMH3 , is the latest right?
Click to expand...
Click to collapse
That part is. MK6 is latest from ATT 4.3 OTA
Sent from my GT-N7105 using XDA Premium 4 mobile app
MiuKing said:
That thread doesn't get updated often these days,
I317UCAMH3 , is the latest right?
Click to expand...
Click to collapse
That's possibly because I have a lot going on. And I try my best to have it UPDATED with the latest stuff.
You wanna know when the last time I updated, then look at the top of the OP page. Updated yesterday btw
Modems are updated to the latest one....
dicksteele said:
That part is. MK6 is latest from ATT 4.3 OTA
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1:thumbup:
Sometimes we all ASSUME
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I'm on 100% stock. just rooted. the boot times are really long. I got really worried, so I flashed firmware and everything 100% back to stock. But the long booting times are still there. Just to be sure, I tried rebooting even before rooting (in case rooting was the cause :silly: ) but that wasn't the case. And yes, I have fastboot on.
Other than that, there is no anomaly, phone is working 100% fine, no overheating, no battery drain, nothing. I only had the phone for nearly a month before getting the update, so it might be just me not noticing reboots took this long before too?
Anyone else experiencing it?
Not sure if it's the same thing but I seem to have very long boot times now aswell. I was testing a GPE Rom for a while and went back to sense. Booting now takes at least 5 minutes. Just sits at the white HTC bootscreen until screen turns off and then it works fine. Going back to a GPE Rom seems to fix the problem
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Update your firmware and it should work. I have sprint so i was able to find the updated firmware through their forums. I originally thought they were bad flashes, but let it wait one time, it took almost 5 mins to load up. After I updated my firmware to the latest, it worked normally again with fast boot up. On a side note on 4.4.3 roms, I used to think my old bluetooth keyboard didnt work on aosp or gpe roms, and only on sense. Once I updated my rom to a 4.4.3 sense rom, the bluetooth keyboard stopped working on that too. Getting a new bluetooth keyboard today so I will test it out.
duckysempai said:
Not sure if it's the same thing but I seem to have very long boot times now aswell. I was testing a GPE Rom for a while and went back to sense. Booting now takes at least 5 minutes. Just sits at the white HTC bootscreen until screen turns off and then it works fine. Going back to a GPE Rom seems to fix the problem
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same here. I don't think its a problem related to hardware or software. Just, the boot time is longer. Just that. It is a very huge relief to know that someone else is experiencing it too. I've checked everything I can, and there seems to be nothing wrong while it takes long to boot. It doesn't effect the usage at all too. It isn't a bug, just a little annoyance in case you like devices to speedily boot up.
@memekmek Did that too. I flashed firmware, and everything thoroughly checking my procedure. Nothing seems to be broken anyway, I just wanted to check if others have it too or is it me?
Jamal Ahmed said:
I flashed firmware, and everything thoroughly checking my procedure. Nothing seems to be broken anyway, I just wanted to check if others have it too or is it me?
Click to expand...
Click to collapse
How do you flash firmware when you're not S-Off and do you already have latest firmware for your region (vodap something as I read in other thread)
ckpv5 said:
How do you flash firmware when you're not S-Off and do you already have latest firmware for your region (vodap something as I read in other thread)
Click to expand...
Click to collapse
I used the firmware provided by mike1986 in this thread http://forum.xda-developers.com/showthread.php?t=2696282 ... It said that if I have S-ON, I should at least not be able to brick my device...
[I'm actually a 1000% noob in tech, and wrote only what I thought I was doing. I'm sure I must've been wrong. your reply just actually makes sense!]. I didn't want to ask each question on each step, and not bother with my lack of knowledge so I tried to write as much as I understood myself.
I guess it means that my firmware flash was a failure, and that itself is the culprit That clears out a million of my worries.
A little selfish favor to ask of you. Can you kindly direct me to any carrier-specific firmware download place (If there's any!). I'll check it whenever vodap001 firmware comes.
Thanks
First off, I will say that I am basically new to using stock ROM's and such, though I have previously successfully flashed another phone which worked until the experimental ROM became unstable after a few days, with reflashing yielding the same result.
To the point, using ODIN, I flashed TWRP onto my T999 (after heimdall kept failing for me), and I performed a back up and then proceeded to flash CM 12.1 nightly onto my phone. The nightly worked great other than giving me an error of "SIM card missing" in the setup screens. This of course is a deal breaker for me as this is the phone I wish to use daily. I did my research and found that for many people this was the case, however the network would still work despite the phone's status saying otherwise, though my phone would neither receive nor send texts/calls let alone find any network operators. (I also tried different releases)
I then tried to flash multiple CM 11 official releases but kept receiving "assert failed getprop( ro.bootloader)..... " I even tried the ol' "delete that line of the script" troubleshooting, however the installation would then abort just the same without stating the error.
After both of these failed, I tried recovering my previous back up however it failed every time.
I currently am running PAC ROM's 5.1.1 which yields the same issue as stated above concerning the nightlies.
I have also tried updating my modem as I found under troubleshooting that fixed what seemed to be the same issue for others, yet it never worked for me.
Any advice would be great. I'm sure you'll need more info, so let me know what you need.
reserved
What is important here is going to be the base firmware. We need to know what build you are currently running.
To get this, open terminal emulator and enter this:
getprop ro.bootloader
Let us know what it returns. I really have a feeling this will be the root of all your problems. You need to be running on a matched, 4.3 bootloader and modem. Otherwise the rom will not work right (hence the asserts in the updater-script). If you gave a mismatched modem, none of the radio related functions will work.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
What is important here is going to be the base firmware. We need to know what build you are currently running.
To get this, open terminal emulator and enter this:
getprop ro.bootloader
Let us know what it returns. I really have a feeling this will be the root of all your problems. You need to be running on a matched, 4.3 bootloader and modem. Otherwise the rom will not work right (hence the asserts in the updater-script). If you gave a mismatched modem, none of the radio related functions will work.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks for getting back so quickly!
the terminal returned T999UVUEOH1
Ok. Since that's the latest available, you are going to be limited to only that build. (If you try to downgrade the bootloader it'll hard brick.)
My best suggestion would be to reflash the Full OH1 firmware via Odin, and then factory resetting from the stock recovery. (This will wipe all user data including the internal sdcard.)
Once you are fully stock, I'd the problem continues you can be pretty sure it's going to be hardware related. If that is the case, go to a t-mobile store and ask them to test a new one in your device. (They'll often replace it free if the Sim is the problem. )
Hopefully, everything will be working again though, and then you can try again to flash your rom if you so choose.
Sorry I don't have an easier/better suggestion. Let me know if you have any questions though. (You can get the firmware from my thread stickied at the top of the development section.)
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Ok. Since that's the latest available, you are going to be limited to only that build. (If you try to downgrade the bootloader it'll hard brick.)
My best suggestion would be to reflash the Full OH1 firmware via Odin, and then factory resetting from the stock recovery. (This will wipe all user data including the internal sdcard.)
Once you are fully stock, I'd the problem continues you can be pretty sure it's going to be hardware related. If that is the case, go to a t-mobile store and ask them to test a new one in your device. (They'll often replace it free if the Sim is the problem. )
Hopefully, everything will be working again though, and then you can try again to flash your rom if you so choose.
Sorry I don't have an easier/better suggestion. Let me know if you have any questions though. (You can get the firmware from my thread stickied at the top of the development section.)
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I took your advice and used your download links, using https://www.androidfilehost.com/?fid=23329332407581038 as was linked to UVUEOH1 on the firmware page and followed your guide .
The phone has now been on the Samsung bootloop for 10 minutes after rebooting it while it was in bootloop for 30+. Any suggestions?
Did you factory reset? You always have to when going to/from TW/CM because their data is not compatible.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Did you factory reset? You always have to when going to/from TW/CM because their data is not compatible.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just realized that I skipped that part and it is currently rebooting! I'll let you know what happens!
EDIT: Thank you so much! Is there a particular rooting guide that you recommend? And also, from there, should I be able to flash the ROM normally?
So the network still isn't working, however my SIM works in another phone that I've been using in the meantime. Do you still then suggest that the SIM could be the in error, or would it be software at that point?
Does it see any networks or show any signal with the Sim removed? It should allow for emergency calls only at least.
If it does, go to T-Mobile and test another Sim. If it does not, it's probably a hardware problem.
Sent from my SGH-T999 using Tapatalk