My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.
They are both different ways to say the same thing. Some places the n9005 is referred to as hlte and some places it's hltexx. Now as for why the roms don't flash and give that error, i am not sure. Ppl have been reporting that on ALL roms but i haven't had any issues, the roms seem to flash fine for me. But others have to edit the updater script, also some reported that flashing via cwm worked for them without editing the updater script and others said switching to twrp helped them... This is the weirdest android phone I have owned.
Sent from my SM-N9005 using Tapatalk
I also want to know this, and how to detect if the one i have is hlte or hltexx
JazonX said:
Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.
Click to expand...
Click to collapse
Can i move the thead myself to the Q and A section?:
hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!
Hakired said:
i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
Click to expand...
Click to collapse
i can also not install the nightly hltexx.
bought my device in germany.
no problem with temasek unoffical and probam.
Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
johanveld said:
I also want to know this, and how to detect if the one i have is hlte or hltexx
Click to expand...
Click to collapse
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
hltexx is product name, hlte is device name
hlte refers to many models, including N9002, N9005, N9006, N9008, N9009
while hltexx is N9005
you can use my app Phone INFO to get more information.
i removed the first line from the updater script and successfully flashed cm nightly in twrp.
johanveld said:
hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!
Click to expand...
Click to collapse
but im already using CWM tho XiaoLu's custom CWM 6.0.4.5 i think
not-i said:
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
have you tried the cyanogen nightly htlexx?
Are you telling me to edit my build prop?
What i was trying to do was dirty flash the Cyanogen Nightly on top of Temasek. I didnt believe a full wipe would help, Do you reckon I should? Just wanted to try out the Cyanogen but im pretty happy with Temasek's
A.N.Droid said:
i removed the first line from the updater script and successfully flashed cm nightly in twrp.
Click to expand...
Click to collapse
im kinda newbie and this seems difficult. No idea what an updated script is. Is that part of the ROM im flashing or within the recovery?
not-i said:
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
My build prop says this.
ro.product.name=hltexx
ro.product.device=hltexx
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.
Hakired said:
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.
Click to expand...
Click to collapse
if it still doesnt work you could do this:
open the cm nightly archive (i use winrar), navigate to \META-INF\com\google\ and extract the file updater-script.
open in a text editor of your choice.
remove the first line and save the edited file. (you dont need to know a thing about programming to realize that this is the device check)
drag and drop the edited file into that folder in the archive and overwrite the old file.
flash. enjoy !
Thanks it worked. Now to see if it's fully functional with my phone.
Hakired said:
Could you send me your updater script file with the deleted line? When i opened it in notepad they were not in lines and it just goes on and on so I deleted some stuff concerning the checks and it looks like this.
|| abort("This package is for \"hltexx\" devices; this is a \"" + getprop("r ...
I get an error status code: 6
but it does not check for the phone model anymore.
Click to expand...
Click to collapse
great that it works for you now !
please do not use the attached file anymore, its outdated !
sermon edgedai
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
Knox bootloader / kernel not compatible
This arrived to me on another device. I tried flash a Rom MJ2 non Knox over a ML1 Knox. The flashing by Odin was good but the Knox bootloader installed not liked it and give me that error at boot, and the phone not started.
I made a Mod Kernel-ML1.tar.md5 to flash by Odin and problem solved. MJ2 worked whit ML1 kernel.
NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
could be that the attached file is outdated. you have to modify it by yourself next time.
can you get into recovery ? if so, wipe and install a rom.
if not, can you get into download mode ? if so, flash stock rom with odin.
if not, pull the battery and try again.
Related
Ok, first of all, my phone model is i9505 (Samsung Galaxy S4 International version).
I installed last week a new kernel: http://forum.xda-developers.com/showthread.php?t=2297379 on my phone.
Today I tried to install the cyanogenmod 10.2, now the recovery edition of PhilZ Touch says everytime that there is a prob i9505G etc, which I don't understand.
I think the kernel changed my phone number to i9505G, someone who can help me with this? Thanks.
tareqnull said:
Ok, first of all, my phone model is i9505 (Samsung Galaxy S4 International version).
I installed last week a new kernel: http://forum.xda-developers.com/showthread.php?t=2297379 on my phone.
Today I tried to install the cyanogenmod 10.2, now the recovery edition of PhilZ Touch says everytime that there is a prob i9505G etc, which I don't understand.
I think the kernel changed my phone number to i9505G, someone who can help me with this? Thanks.
Click to expand...
Click to collapse
Hello mate, try a different kernel http://forum.xda-developers.com/showthread.php?t=2502714 then update your philz recovery to newer. have a nice day.
Repulsa said:
Hello mate, try a different kernel http://forum.xda-developers.com/showthread.php?t=2502714 then update your philz recovery to newer. have a nice day.
Click to expand...
Click to collapse
I'm gonna try this, thanks for the fast answer!
+1 :good:
Ok, tried it but did not work, still getting a whole bunch of errors with getprop I9505G etc..
tareqnull said:
Ok, tried it but did not work, still getting a whole bunch of errors with getprop I9505G etc..
Click to expand...
Click to collapse
Can you give us any information on the phone? such as custom rom, root, bootloader,recovery and such? thanks.
Repulsa said:
Can you give us any information on the phone? such as custom rom, root, bootloader,recovery and such? thanks.
Click to expand...
Click to collapse
Yeah sure, just installed stock firmware 4.3 so nothing editted, PhilZ CWM recovery and that's it.
Since the kernel it won't install cm10.2 anymore so yeh...
Nothing much to explain, I don't know why this happens to me, my model number jftlexx is correct but in recovery it gives a bunch of errors with i9505G and the model name of it, forgot it I think it was like jgdlet or something.
tareqnull said:
Yeah sure, just installed stock firmware 4.3 so nothing editted, PhilZ CWM recovery and that's it.
Since the kernel it won't install cm10.2 anymore so yeh...
Nothing much to explain, I don't know why this happens to me, my model number jftlexx is correct but in recovery it gives a bunch of errors with i9505G and the model name of it, forgot it I think it was like jgdlet or something.
Click to expand...
Click to collapse
i found this after reading cm10 that you need to install a compaltible recovery for this "Make sure you have the LATEST version of ClockworkMod recovery. Other recoveries may work but will not be supported by CyanogenMod" either you use a Clockwork recovery http://forum.xda-developers.com/showthread.php?t=2397108 or you can try it with TWRP http://forum.xda-developers.com/showthread.php?t=2468187 and make sure the file you download is not corrupt, please check the Hashcheck that u got the proper file.
Repulsa said:
i found this after reading cm10 that you need to install a compaltible recovery for this "Make sure you have the LATEST version of ClockworkMod recovery. Other recoveries may work but will not be supported by CyanogenMod" either you use a Clockwork recovery http://forum.xda-developers.com/showthread.php?t=2397108 or you can try it with TWRP http://forum.xda-developers.com/showthread.php?t=2468187 and make sure the file you download is not corrupt, please check the Hashcheck that u got the proper file.
Click to expand...
Click to collapse
Fixed it, just used another recovery, TWRP .
Thanks dude for the extra info.
tareqnull said:
Fixed it, just used another recovery, TWRP .
Thanks dude for the extra info.
Click to expand...
Click to collapse
Im glad that helps have a nice day sir.
Hello there,
My new Samsung Galaxy S5 [SM-G900L] just came in.
It wanted to install custom recovery from TWRP so I could make a backup of my Stock Rom and afterwards could install custom Roms, but there doesn't seem to be any support for the G900L.
I'm quite new here, but is it possible someone can help me with this? So that TWRP will aslo provide support to the G900L.
I'm willing to sent al the necessary files. But you'll have to gide me trough it.
Thanks in advance.
Anybody??
Good luck.. i tried looking for anything related to the 900L model but there's barely any support on it.
chaulklet said:
Good luck.. i tried looking for anything related to the 900L model but there's barely any support on it.
Click to expand...
Click to collapse
Thanks, but yeah, that is why I opened this thread. Because I couldn't find anything about my G900L either
And because I'm new I can't post anything in the development section T.T
I hope someone picks this up though.
Yup I fell ya
/Bump for support
SM 900L Support
Another one for 900L support. Got the phone rooted no problem but failed to install CWM or TWRP yesterday so no custom recoveries available . Got a boot loop for my efforts. Hope there is enough love out there for someone to tweak some of the packages for these phones.
Cheers.
Successfully installed TWRP and CyanogeMmod recoveries on my SM-G900L
Sorry for the very long delay. I only got this mobile last month. I am able to install TWRP recovery by using TWRP manager after rooting (Although his device is not supported officially, the recovery image for the international version (SM-G900F) works really fine. I also successfully flash CyanogenMod (both View attachment Snapshot_recovery.tar and View attachment Nigthy_recovery.tar) recovery images using odin.
sunilpaulmathew said:
Sorry for the very long delay. I only got this mobile last month. I am able to install TWRP recovery by using TWRP manager after rooting (Although his device is not supported officially, the recovery image for the international version (SM-G900F) works really fine. I also successfully flash CyanogenMod (both View attachment 3536028 and View attachment 3536027) recovery images using odin.
Click to expand...
Click to collapse
I have tried many times to use TWRP recovery on G900Lmodel but with no success.
I always end up with "COULD NOT DO NORMAL BOOT".
Also I need one help, I was trying to use this Custom ROM "Insanity S7 edge port", I again get the same message " COULD NOT DO NORMAL BOOT".
Someone told me it's the kernel problem and i have to flash stock kernel after flashing ROM zip. But the thing is I don't have the stock kernel.
Please help.
sachin7825 said:
I have tried many times to use TWRP recovery on G900Lmodel but with no success.
I always end up with "COULD NOT DO NORMAL BOOT".
Also I need one help, I was trying to use this Custom ROM "Insanity S7 edge port", I again get the same message " COULD NOT DO NORMAL BOOT".
Someone told me it's the kernel problem and i have to flash stock kernel after flashing ROM zip. But the thing is I don't have the stock kernel.
Please help.
Click to expand...
Click to collapse
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
sunilpaulmathew said:
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
Click to expand...
Click to collapse
Thank you sunil
I tried the recoveries that you are suggesting, both of them, klte and klteskt from the twrp site.
It seems to work on every other device but mine.
Can't figure what I am doing wrong.
sachin7825 said:
Thank you sunil
I tried the recoveries that you are suggesting, both of them, klte and klteskt from the twrp site.
It seems to work on every other device but mine.
Can't figure what I am doing wrong.
Click to expand...
Click to collapse
Not sure abt the latest versions. can you try the one (klte) linked in my xda thread. and hope ur device is rooted properly...
sunilpaulmathew said:
Not sure abt the latest versions. can you try the one (klte) linked in my xda thread. and hope ur device is rooted properly...
Click to expand...
Click to collapse
yes i will try them, I hope they work on latest MM.
And yes the device is rooted properly with latest CFautoroot for G900L, I even checked it with Root Checker basic.
Anyways, I don't have any special liking for TWRP, I wanted it to flash stock boot.img to make the Insanity ROM work.
I am ok with CWM recovery, but I was told it could not flash .img file and I am not equipped to make my own flashable zip form boot.img.
But now I am planning to use your modded boot.img for Phoneix based MM custom ROMs. I hope that will work.
Btw thank you so much...I checked both of your threads...They are awesome....you seem to be lone warrior for these Korean variants. Not much support elsewhere.
Really appreciate your efforts!!!!
Keep up the good work.
sunilpaulmathew said:
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
Click to expand...
Click to collapse
TWRP worked!!!
Finally..
Thank you so much!!!
Also I tried your kernel with Insanity ROM and it works perfect.!!!
Thank you once again.
ok. so let me list the things i've done so far.
1. i have rooted my phone. Cf-Autoroot using odin.
2. i installed flashify and installed TWRP 2.8.7.0 (LINK TO WHAT I DID WITH TWRP)
3. i downloaded the latest Int'l CM12.1 from here cm-12.1-20150805-NIGHTLY-trltexx.zip
4. rebooted to TWRP.
5.Wiped Data, cache, and dalvik cache
6. selected install, selected my file (cm-12.1-20150805-NIGHTLY-trltexx.zip ) thenproceeded to swipe to confirm.
7.waited for 1 minute or so. and then well it said " E:Error executing update binary in zip '/external_sd/cm-12.1-20150805-NIGHTLY-trtlexx.zip"
so what do i do?
Edit: my note 4 is SM-N910C dunno if that has anything to do with it. but cyanogenmod listed trltexx as Int'l
It fails because it's not compatible with your Note4..
The version that you're trying to install is Official Cm12 for 910F and 910G
gekkehenkie11 said:
Q: Does this work for 910C, 910U, 910T or whatever other variant ?
A: No. This ROM is only for 910F and 910G. Some other Snapdragons like the 910T have a ROM out, but check those forums. Exynos users like 910C are still out of luck although someone is working on a very early alpha ROM for it: http://forum.xda-developers.com/note-4/orig-development/n910c-cyanogenmod-12-sources-t3015717
Click to expand...
Click to collapse
_mone said:
It fails because it's not compatible with your Note4..
The version that you're trying to install is Official Cm12 for 910F and 910G
Click to expand...
Click to collapse
I see. thank you very much for your reply. i restored it to stock for now. and i hope he can get it done. or atleast a 5.1.1 rom will come out for the 910c
ProjectX01 said:
I see. thank you very much for your reply. i restored it to stock for now. and i hope he can get it done. or atleast a 5.1.1 rom will come out for the 910c
Click to expand...
Click to collapse
You can install the ROM from Team EOS.
The last build has only one issue (video record is not working right now).
Hello,
I need some help. I am using a Samsung Galaxy Tab 4 10.1 LTE SM-T535 and I want to flash a custom rom, but it is not working. If I want to flash http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906 or http://forum.xda-developers.com/tab-4/development/rom-pac-rom-lp-mr1-beta-3-sm-t530-531-t3216682 everything looks great and the tablet restarts. Then the following error appears:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
Does this mean there is no kernel or what? I flashed the openrecovery-twrp-2.8.7.0-SM-T5XX-150810_matisse_wifi_3g_lte and wiped everything before flashing the ROM.
Please help me
Cololand said:
Hello,
I need some help. I am using a Samsung Galaxy Tab 4 10.1 LTE SM-T535 and I want to flash a custom rom, but it is not working. If I want to flash http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906 or http://forum.xda-developers.com/tab-4/development/rom-pac-rom-lp-mr1-beta-3-sm-t530-531-t3216682 everything looks great and the tablet restarts. Then the following error appears:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
Does this mean there is no kernel or what? I flashed the openrecovery-twrp-2.8.7.0-SM-T5XX-150810_matisse_wifi_3g_lte and wiped everything before flashing the ROM.
Please help me
Click to expand...
Click to collapse
You have completed all the prerequisites before flashing (i mean 5.0 stock) ? And TWRP better to use https://www.androidfilehost.com/?w=files&flid=40746 .
Forgot text is correct , dont worry .
repey6 said:
You have completed all the prerequisites before flashing (i mean 5.0 stock) ? And TWRP better to use https://www.androidfilehost.com/?w=files&flid=40746 .
Forgot text is correct , dont worry .
Click to expand...
Click to collapse
Thanks, for the fast reply.
sub77 said:
Download official Samsung Lollipop Rom and flash with odin if you are coming from KitKat
Click to expand...
Click to collapse
Do u mean this step? Where do I get this ROM? I searched everywhere and I don't find it.
Cololand said:
Thanks, for the fast reply.
Do u mean this step? Where do I get this ROM? I searched everywhere and I don't find it.
Click to expand...
Click to collapse
If you have still 4.4.2 firmware you can select in this thread http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844 suitable for you firmware ( i mean region) and flash via Odin .
repey6 said:
If you have still 4.4.2 firmware you can select in this thread http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844 suitable for you firmware ( i mean region) and flash via Odin .
Click to expand...
Click to collapse
Thanks, you saved my day. I installed the CM ROM. But one more Problem: When I reboot this message still appears:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
and Apps are getting optimized. After that, everything is working fine. Is this normal?
By the way: The statusbar is very small and a few texts are not in german, but I think this is a ROM bug.
Cololand said:
Thanks, you saved my day. I installed the CM ROM. But one more Problem: When I reboot this message still appears:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
and Apps are getting optimized. After that, everything is working fine. Is this normal?
Click to expand...
Click to collapse
Yes it is . But CM13 much of raw else as for me . BlissPop and PacRom are more better .
Can any one help me try to get cm11 on my verizon note 3. I have TWRP and Unlocked Bootloader with root running CM13 but I still want to run cm11 and when I tried to flash the rom, it gave me a updater 7 error. If you know a way to fix this please tell me.
lootrooter said:
Can any one help me try to get cm11 on my verizon note 3. I have TWRP and Unlocked Bootloader with root running CM13 but I still want to run cm11 and when I tried to flash the rom, it gave me a updater 7 error. If you know a way to fix this please tell me.
Click to expand...
Click to collapse
Error 7 is typically a mismatch condition between the fingerprint of the recovery in use and the model of the phone the ROM is intended for - the ROM author puts an "assert" statement in the installer script to prevent dummies from flashing a ROM from the wrong device to a phone.
Assuming you didn't make a mistake downloading the wrong cm rom for the SM-N900V Note 3 this could be a "hlte" vs "hltevzw" issue depending on which TWRP version you have installed.
You can work around this by unpacking the ROM .zip file, deleting the offending "assert" line in the installer script, and red zipping the ROM.
bftb0 said:
Error 7 is typically a mismatch condition between the fingerprint of the recovery in use and the model of the phone the ROM is intended for - the ROM author puts an "assert" statement in the installer script to prevent dummies from flashing a ROM from the wrong device to a phone.
Assuming you didn't make a mistake downloading the wrong cm rom for the SM-N900V Note 3 this could be a "hlte" vs "hltevzw" issue depending on which TWRP version you have installed.
You can work around this by unpacking the ROM .zip file, deleting the offending "assert" line in the installer script, and red zipping the ROM.
Click to expand...
Click to collapse
It was just a "hlte" vs "hltevzw" error, thanks
Did you get CM11 working?
Sent from my SM-N900V using Tapatalk
Old 4.4 rom on new vzw bootloader
bishop0114 said:
Did you get CM11 working?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I did and c-rom. Which i love. But with both of them lte data goes in and out. I've tried a bunch of things but can't figure it out. It's weird editing apns causes them to be deleted. Any ideas anyone?
how to install
themrgoats said:
I did and c-rom. Which i love. But with both of them lte data goes in and out. I've tried a bunch of things but can't figure it out. It's weird editing apns causes them to be deleted. Any ideas anyone?
Click to expand...
Click to collapse
can tell me how did u installed it? i am getting ERROR : 7 in TWRP , cm-11-20160612-NIGHTLY-hltevzw.zip (223.82 MB)
Rooted 0B6 then Unlocked Bootloader.
dat ka said:
can tell me how did u installed it? i am getting ERROR : 7 in TWRP , cm-11-20160612-NIGHTLY-hltevzw.zip (223.82 MB)
Rooted 0B6 then Unlocked Bootloader.
Click to expand...
Click to collapse
TWRP error 7 typically means you're trying to install the zip onto the wrong device.
Sent from my SM-N900V using Tapatalk
Yes if you are using the hltevzw twrp then just flash the hlte generic twrp and u can flash roms that don't require the hltevzw twrp to see the right rom is version is being flashed.
One more question , i am running JasmineRom its 5.0.x CM 11 is 4.x.x Will it work? if i install it?
dat ka said:
One more question , i am running JasmineRom its 5.0.x CM 11 is 4.x.x Will it work? if i install it?
Click to expand...
Click to collapse
I don't think so but was wondering since we have an unlocked bootloader, can we downgrade to a developer 4.4.2 rom and then install the cm11?
Sent from my SM-N900V using Tapatalk