Hey guys,
I have a very annoying and reproducible problem with my Desire. Everytime I connect the phone via USB (no matter if dock, laptop, wall) it reboots ~2 seconds after removing the USB cable from the phone.
I have had this problem for about 2 weeks now, across 4 or 5 Custom Roms (Sense and Non-Sense) and right now I am on CM6.1 Nightly 214.
It just annoys the crap out of me, for example when I got the Desire in the dock next to my desk and I receive a call, I can only accept the call handsfree, because removing it from the dock would cause a reboot and I would lose the call...
Please give me some kinda advice, I just flashed the latest radio and it worked twice without rebooting and now I'm back to square 1.
All the best,
Paul
Sounds like a faulty battery or some kind of defect at the power supply.
I suggest you try this with another battery, maybe from a friend.
You should check the usb connector on the phone too for some sort of deformation or smudge.
I thought that it could be the usb cable you are using, but since it does the same with the dock, it's not it.
The easiest and the most not likely way to fix it is with the calibration of the battery, if you have luck maybe it's just the OS that errs.
Thanks for your thoughts on my problem. Right now I am waiting for an important call but I got a spare battery from a friend of mine already and will later check and see if the problem occurs with the spare battery as well.
But the other point you mentioned was a calibration of the battery: how exactly do I do that? Just AmonRA Wipe Battery Stats or are you talking about another method?
Cheers for the advice!
this is for the calibration of your battery.
http://forum.xda-developers.com/showthread.php?t=755903
Hi, hope it works with the other battery, otherwise you'll have to send it for repair.
The battery thing I mentioned, has a minimal chance of working, but at least when I am desperate I try things that have even the smallest chance of fixing it. So in essence the process is: charge untill full when powered on; disconnect charger (which will automatically reboot your phone in your case);
don't let it boot, enter hboot for example and turn it off; then charge till full again; now boot into recovery wipe stats; and finally just boot into android.
Another thing worth checking I think is the pins where the battery connects to the phone, they should look clean (I wipe pins with rubber for a pencil) and intact.
Edit:Well seems like Marios already posted a link but mine is specific for your situation
did you solve the problem?
i have the same thing... very strange.
calibrating the battery didn't help.
No, I still haven't found a solution. Strangely though, it doesn't reboot anymore if I charge it via USB on my laptop. On my desktop and via the wall charger it still reboots every time I unplug it. Sorry I can't be of more help
my phone reboots when disconnecting from my laptop too.
even when in recovery, very strange...
have you tried to try the unbricking process with the misc.img?
Actually, I haven't tried that one. Can you give me a link to what you're talking about?
IT WORKED!
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
just flashed the update.zip and i can copy the files to/from my laptop using the usb cable.
and it doesn't reboot when unpluging too
Got the same issue, tried modaco´s workaround, same thing... it started happening after i flashed CWM3.0x wich reovery do u use?
gonna try flashing Ra again and see what happens....
Solved It
Like i said, happened after flashing cw3.x finnaly i got home, flashed RA-desire-v2.0.0-CM again, then flashed update.zip from modaco´s thread, and for now it stoped....
just gonna see what happens when the battery get fully charged....
EDIT: Fully charged 4192mV removed it, and.... nothing happened...
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
congrats
powlemann said:
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
Click to expand...
Click to collapse
NICE....
How did u solved it, u never know.....
I tried all things listed in this thread and some more, too.
But, it still reboots when removing from power supply (pc connection works now).
Perhaps you tried some things not listed here?
I am not sure when the problem started for me.
I installed cm7 nightlies with no reboot-problem, also switched from alpharev1.5 to alpharev1.8 and from cwm2 to cwm3.
All in a few days.
Somewhere along these days the problem appeared.
Btw.:
I got reboots on both kinds of usb connections (PC/power supply).
Debugging connection (adb, fastboot) worked.
Accessing the phone as usb storage device worked, too.
So this may be a little bit different from the cases described in the thread.
To solve the issue, I tried several things:
First I restored older backups (versions of cm7) with no success.
Then I restored my last backup of cm6 nightly from just before cm7, and it didn't work either.
As I was 100% sure that this worked before, I now concentrated on the remaining parts, recovery and boot loader.
So I first tried downgrading to clockworkmod2.
Then I tried updating to a newer alpharev1.8 (as it was a little bit newer than my installed version).
After finding this thread, I became a little happier again...
I applied the fastboot oem ... thingy (hmm, what does it do exactly?).
Then I calibrated my battery, which seemed to work well, as it shows 99% now, which it didn't before.
And at the end I installed the fixmisc-update.zip as linked above.
Between each step I checked if the issue disappeared.
Nothing of those steps completely solved the problem.
However, when disconnecting from PC, the reboots don't appear anymore, so at least something has changed.
So, powlemann, ferreinf and others being successful with the steps above, which configurations do you use now?
Can you tell me which change solved the issue for you?
Do you use alpharev1.5 or 1.8 (and the later from which date) or none of them?
Did you install cwm3 again after solving the problem and did the problem re-appear?
Good News for you, hg42!
I am 99% sure you can fix the problem when first flashing AmonRA recovery and then do Mocados Usb Brick rickrolled.
Do you know how to flash a different recovery?
I fixed it with modaco's zip, that was very annoying!!
Related
Hi,
I had the following issue recently with bootloader:
http://forum.xda-developers.com/showthread.php?t=375685
Thanks to all those of you who replyed.
Well I now have some further info but the problem is slightly different. The fix for my problem last time seemed random, I hooked up to my pc and the phone started booting fine.
So I have been using my phone fine for X number of weeks, no changes software adds updates or anything applied.
I have been using SPB Backup (A+ s/w) to do nightly scheduled backups, followed by a reboot. Two nights ago I found my phone on the bootloader screen !!
I hooked my phone up to my pc ready to re-flash it, and switched it on (the phone). Low and behold the phone booted fine. So off I trundled with a "working" phone.
This morning I woke up to a bootloader screen ! As a side niote the phone is on charge all throughout the night so as I get no issue during backups.
I hooked my phone up to my pc and switched the phone on and voila, it booted. So I set about doing the mtty.exe tasks listed in the above post. I ran "info 8" as suggested in the above thread and my output was identical (barring checksum values) to that described here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Nothing strange that I could see and when I ran "task 2a" it appeared to do nothing.
I have re-flashed my ROM (Schaps 4.31) and the flash worked fine except when it re-booted, it went to bootloader. A quick phoen switch on with it hooked up to the pc via USB and it booted fine.
So quick summary:
Reboot of device causes bootloader screen to appear. Hooking it up to PC via USB and switching it on allows normal boot and the phone is fine then as long as it doesn't reboot.
Anyone have any ideas how I can fix this problem ??
ps Sorry it was a long post, thought I had better explain everything!
Dave
HARDSPL7 Olipro 2.10
HERM 300 - T-Mobile MDA Vario II
Schaps 4.31
Someone else has the same issue on this thread:
http://forum.xda-developers.com/showthread.php?t=381279
But, I think I have solved my problem (not sure if it is permanent) by powering the phone off and on. Not resetting, just a simple power off. I spoke to a colleague who said the way it shuts down is different to soft reset (makes sense) and I haven't powered my phone off properly for a long time.
I have tried soft reset a couple of times since doing this and it hasn't gone to the bootloader screen once.
Maybe this is the simple fix.
I will keep you posted.
My fix didn't work.
Can someone give me some idea what I should see when I run "task 2a" in mtty ? I ran it and it just gave a blank line and then went back to the prompt.
Help
might be dumb question but did you try reinstalling hard spl? might fix. also I would try to reflash to stock rom. wouldnt hurt, then flash to rom of choice. Cheers....
as for mtty it will flash up the bad blocks and tell you if its repaired or not. if there was no response then it means there were no bad blocks...
Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.
I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.
Try reinstall usb drivers, rsdlite, different usb port, and different pc.
@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.
If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.
im having the same issue, did you solve it?
im having the same issue, did you solve it?
try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...
You have tried the McGyver-trick?
I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.
Ok. At least you have the time now to enjoy your sunny weather in Brazil...
RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help
First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx
Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again
i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan
hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..
I was running Leedroid on my Desire and all was fine.
I seen these Sense 2.1+3.0 ROMS and decided to give one a go.
I tried to get into recovery before doing anything to take a NAND Backup, but it just refused to go into recovery. I finally got it in there and tried to apply to update.zip but it kept saying something could not be found, I forgot what, and failed after 10 tries.
I booted mu phone up and I'd lost all my data. It's like the phone had been wiped.
I tried reseating the SD Card and checking it was all ok, but then I got stuck in a bootloop. In the mean time, my Alienware Laptop decided to die, followed by my backup Dell laptop! lol
I messed around for ages trying to get various things to work, but couldn't do it. In the end, I downloaded the old root method and flashed Cyanomod 7 which seemed to work and I got it booted, but I couldn't mount the SD card and it would rarely pick up that the USB was connected.
I then flashed AceSMod007 which also seemed to go well minus 2 things.
The first, Text messages seem to show my contacts picture, but also it only shows their Number rather than the contact name. This is VERY annoying and I can't find a way to resolve it.
The second issue, and possibly the most worrying is that it won't pick up USB connection AT ALL. This includes when it's plugged into the Wall to charge.
I tried the USB Brick fix, but that didn't work at all.
I shutdown the phone, removed the battery, plugged in the charger, inserted the battery and booted up the phone and it started charging, but as soon as I unplugged the charger and put it in again, same problem.
I'm currently trying another ROM to see if that resolves the issue, but I suspect that it won't tbh.
Has anyone came across this before and/or knows how to fix it?
Other things I've tried:
Wiping all data, cache and Battery data.
Using different USB cables
Thanks
UPDATE:
Flashing a different ROM didn't seem to resolve it.
Quick update.
I flashed Insertcoin rom onto the phone and it's resolved my text message issue.
Also, when I plugged the phone into the PC, it didn't give me any options for mount SD or anything like that, but said it was charging. However, an hour later and the battery had only gone down.
Since charging by USB has always been slow for me, I plugged in into the wall socket for an hour but it wouldn't pick up that I'd plugged it in. I turned the phone off and I got the LED to say it's charging.
Left it, then booted it up and still has the same battery level.
I don't expect it's the battery otherwise it would pick up fine when plugging into the PC.
Could be an usb brick:
http://forum.xda-developers.com/showthread.php?t=691639
Cheers mate, but as I mentioned, I've tried the USB Brick fix a couple of times and still experiencing the same issues.
Can you switch on blue tooth? Does it stay on?
Sent from my HTC Desire using XDA Premium App
Actually, no. Its says Turning On... Then just goes back to off.
you DO have USB-Brick
you gotta fix it
if S-OFF do:
fastboot oem enable qxdm 0
fastboot oem eraseconfig
if S-ON there are a few threads on xda on how-to do it, if you still get no USB-connectivity you just didnt do it right
good luck
Ah, I did try it a few times. I'll just keep trying then.
Cheers
Are you S-Off or S-On and are you still ROOTED?
This thread for USB Brick
See for my post here
if you are S-off or tried to flash a RUU and lost ROOT!
This thread has a flasher with built in USB Brick fix
I'd already followed the USB Brick guide and it didn't help.
Now, is I were to have missed the step that says to run '/data/flash_image misc /data/mtd0.img', I'd be a bit of a tit.
So let's just say that I tried the guide again and now I have full USB functionality back
I was going to S-OFF my phone, but I'll hopefully get a Sensation soon and I don't want to fubar anything in the mean time.
Thanks for the help and pointers though guys. It's nice to be a member of some forums that aren't full of people who want to cry at you for not understanding everything 100%.
Cheers again
just use the thanks button
glad we (or at least I) could help.
Hi all,
I was having some random reboots on my HTC desire Z lately and decided it was time to try a custom rom. I followed the right steps to first downgrade to froyo, which was successful and next rooted the phone, which seem to have worked as well.
The next step was to get into recovery mode to install the rom, but I did not get to that. I took out the battery while it was still on to power it off, but then it did not power on anymore. Also connecting the charger has no effect at all, so it sure seems to be bricked.
Does anyone have a suggestion on what I can try, or what happened to it?
The way I downgraded and rooted was by using Strawmetals guide which can be found here:
http://minus.com/mu9vZ3P38
and was suggested in this thread:
http://forum.xda-developers.com/showthread.php?t=1178912
I carefully completed all the steps, checked the MD5's etc. and made sure the notifications/verifications I got back in the process were correct..
Also, I wonder if I would run into problems if I send it back in for warranty. If I can't get it to boot, will they? And next they will probably blame me for rooting, right?
Regards & TIA
Yes they gonna blame you for rooting. I was had a same problem, no boot to recovery. I solved the problem with install 4Ext updater and fromit install 4ext tuch,and now I can flash roms. Try to find a charged battery or put yours into another phone and charge it. If I understand right your battery died?!
Sent from my HTC Vision using xda app-developers app
Sounds like it might be bricked mate, same thing happened to me... 3 times. They probably won't be able to get the phone to boot, where did you buy the phone from? My second one was from Vodafone with a warranty, when it bricked I took it in, they plugged the phone in and left it for a few minutes and tried to power it on, tried a different battery (All things I already tried) to see if the device was showing any signs of life, it wasn't and I walked out with a new phone. I doubt they'd be able to bring it back to life to see that it's been rooted. You COULD connect your phone to a car battery and fry it, tell them you went to sleep and woke up and the phone was very very hot and it burnt your hand and melted the charger cable, not sure if I could recommend this, never done it myself... but if you have no other option.
These were also the options I considered. Got to give it a try with a different battery, if I can find one. If that doesn't make a difference, I'll just hand it in and see what they have to say, as there's nothing else I can do without being able to power on the phone..
All of a sudden the phone started working again . And afterwards I was able to complete the update to Mimicry 1.5.
Strange problem, as the phone seemed to be dead for hours.. Hope it doesn't happen again!
Ever since upgrading to newest firmware using HTC fastboot (even after ruu back to stock) I have been having the weirdest charging issues. These issues occur when on qc 2.0, standard 2.0, or even standard HTC charger, different cables... Well basically my phone is not overheated right now but plugged into the wall and is not charging. I plugged it in last night everything was fine. Woke up today to 50% battery. I tried unplugging, tried powering off then plugging back in, tried booting to recovery plugging in, restarting phone, changing cords, changing power adapter... Just randomly does not want to charge then after a handle full of times just decides it wants to charge. This has happened over the course of this week and is just driving me crazy. I am s off. Rooted. Custom twrp recovery 2.8.7.0. On viper one 3.0. But this issue is persistent even when in the powered off state... I have no idea wtf could be causing this issue. Only thing I can think of is firmware or something. I don't get it. Anyone have any issues similar? Or fix? Only way is to cross my fingers and hope the connection starts a charge after a lot of plugging and unplugging. Please help thanks.
magesticschu said:
Ever since upgrading to newest firmware using HTC fastboot (even after ruu back to stock) I have been having the weirdest charging issues. These issues occur when on qc 2.0, standard 2.0, or even standard HTC charger, different cables... Well basically my phone is not overheated right now but plugged into the wall and is not charging. I plugged it in last night everything was fine. Woke up today to 50% battery. I tried unplugging, tried powering off then plugging back in, tried booting to recovery plugging in, restarting phone, changing cords, changing power adapter... Just randomly does not want to charge then after a handle full of times just decides it wants to charge. This has happened over the course of this week and is just driving me crazy. I am s off. Rooted. Custom twrp recovery 2.8.7.0. On viper one 3.0. But this issue is persistent even when in the powered off state... I have no idea wtf could be causing this issue. Only thing I can think of is firmware or something. I don't get it. Anyone have any issues similar? Or fix? Only way is to cross my fingers and hope the connection starts a charge after a lot of plugging and unplugging. Please help thanks.
Click to expand...
Click to collapse
Sounds like a hardware issue not software. but not sure. just my 02. cents
If running the RUU for 1.33.605.15 doesn't solve your charging issue, my first thought would be hardware.
That said, HTC has definitely been having trouble with charging and battery issues, so we've gotta hope that the final release of 5.1 for us will resolve the problem. The currently leaked 2.6.605.10 is most likely not the version that will be released publicly.
After troubleshooting I think the charging was being stopped due to overheating while charging. In standby. Had a live wallpaper I think was causing the high Temps. Changed to normal wallpaper and disabled all but two cores and Temps have been cool and haven't had any charging issues since (fingers crossed as its only been one day lol)
magesticschu said:
After troubleshooting I think the charging was being stopped due to overheating while charging. In standby. Had a live wallpaper I think was causing the high Temps. Changed to normal wallpaper and disabled all but two cores and Temps have been cool and haven't had any charging issues since (fingers crossed as its only been one day lol)
Click to expand...
Click to collapse
Still doesn't explain off state not charging tho so idk I'll see after a few more days see if it happens again
O had a similar issue, where it would go from charging to not charging every couple of seconds. I have not had these issues with Fluent or Adrenaline. There's a post in the Adrenaline thread about how to calibrate your battery. Try that, also. FWIW, when I installed Viper after being on Fluent, and calibrated the battery, I haven't had any more issues.
I have the same problem since updating to 2.6.605.15. The phone was fine until the update rolled out. After several hours of troubleshooting with HTC I got a replacement from them and am now updating that one to see if the problem remains. What a PIA this is since it takes all day to set up your phone again when you get a replacement.
Tom Huot said:
I have the same problem since updating to 2.6.605.15. The phone was fine until the update rolled out. After several hours of troubleshooting with HTC I got a replacement from them and am now updating that one to see if the problem remains. What a PIA this is since it takes all day to set up your phone again when you get a replacement.
Click to expand...
Click to collapse
Why would it take all day?
Just restore your last backup to your new device with TWRP. :good:
Instantly back to where you were.
Please tell me how to do this.
sdamark said:
Why would it take all day?
Just restore your last backup to your new device with TWRP. :good:
Instantly back to where you were.
Click to expand...
Click to collapse
What is TWRP?
Tom Huot said:
What is TWRP?
Click to expand...
Click to collapse
TWRP = Team Win Recovery Project.
That's your recovery. You do make backups, don't you?
Plug your old device into a computer, copy and paste your latest backup to your computer.
Plug new device into computer, drop backup onto new device.
Boot new device into recovery and restore backup from your old device.
Now you are right where you left off.
Or...
Back up old device in TWRP to external SD card.
Move SD card to new device, boot to recovery, restore backup from external SD.
BOOM done.
Root?
Do you have to root the phone?
sdamark said:
TWRP = Team Win Recovery Project.
That's your recovery. You do make backups, don't you?
Plug your old device into a computer, copy and paste your latest backup to your computer.
Plug new device into computer, drop backup onto new device.
Boot new device into recovery and restore backup from your old device.
Now you are right where you left off.
Or...
Back up old device in TWRP to external SD card.
Move SD card to new device, boot to recovery, restore backup from external SD.
BOOM done.
Click to expand...
Click to collapse
Tom Huot said:
Do you have to root the phone?
Click to expand...
Click to collapse
You need to have s-off and bootloader unlocked. Currently the only way to do this on Verizon is with a clip or a java card. There is a post in general about java cards with plenty of information. Currently there is no way to root without TWRP and thus you need s-off and the bootloader unlocked.
Sent from my HTC6535LVW using Tapatalk