So, i had to revert to stock everything, even had to go s-on and reset all flags. Then, i decided to download a rom and try it, upon going to recovery, my phone displays a triangle with an exclamation mark in it. I am fairly certain this means i deleted my recovery, so i flashed several recoveries (philz, twrp, stock) and none work, same problem. I tried flashing an RUU, but i think you need s-off for that, so it wont go pass the security check. I tried using firewater, but i got the whelp message, even though my phone previously went s-off with firewater - so that makes no sense.
Can anyone help? Or know of anything i can do?
Ark1406 said:
So, i had to revert to stock everything, even had to go s-on and reset all flags. Then, i decided to download a rom and try it, upon going to recovery, my phone displays a triangle with an exclamation mark in it. I am fairly certain this means i deleted my recovery, so i flashed several recoveries (philz, twrp, stock) and none work, same problem. I tried flashing an RUU, but i think you need s-off for that, so it wont go pass the security check. I tried using firewater, but i got the whelp message, even though my phone previously went s-off with firewater - so that makes no sense.
Can anyone help? Or know of anything i can do?
Click to expand...
Click to collapse
Are you on 4.4.3? Im having similar issues I think HTC patched some of the exploits.
phlypoc said:
Are you on 4.4.3? Im having similar issues I think HTC patched some of the exploits.
Click to expand...
Click to collapse
Yes, I am. I'm on stock everything currently.
Ark1406 said:
Yes, I am. I'm on stock everything currently.
Click to expand...
Click to collapse
You need sunshine now to s off. Install and pay the $25 to pass go then get your flash on.
dottat said:
You need sunshine now to s off. Install and pay the $25 to pass go then get your flash on.
Click to expand...
Click to collapse
Yeah that's what I thought, thanks man
Ark1406 said:
Yeah that's what I thought, thanks man
Click to expand...
Click to collapse
BTW... When the red triangle appears press volume up and of power together to enter stock recovery. Verizon made it difficult for vzw users to get to stock recovery.
Make sure you have fastboot off in the power menu as well.
dottat said:
BTW... When the red triangle appears press volume up and of power together to enter stock recovery. Verizon made it difficult for vzw users to get to stock recovery.
Click to expand...
Click to collapse
It worked.. If I replace stock with twrp, will this work?
Ark1406 said:
It worked.. If I replace stock with twrp, will this work?
Click to expand...
Click to collapse
If you are unlocked or s off you will be able to.
Custom recoveries don't require the extra button presses though. When you select recovery from bootloader it just goes straight there.
Related
I flashed AOKP 1.4 earlier today coming off of TN Special Edition, but decided i didnt like it. I then did a factory reset and flashed Cleanrom 5 and SP1, but my phone just boots into the cleanrom boot screen, says no signal, and thjen flashes pop-ups such as "com.android.phone has stopped" and "android.process.acore" has stopped" before continuously rebooting. The RUU would not work. Please help, I am panicking!
Gosfgiants said:
I flashed AOKP 1.4 earlier today coming off of TN Special Edition, but decided i didnt like it. I then did a factory reset and flashed Cleanrom 5 and SP1, but my phone just boots into the cleanrom boot screen, says no signal, and thjen flashes pop-ups such as "com.android.phone has stopped" and "android.process.acore" has stopped" before continuously rebooting. The RUU would not work. Please help, I am panicking!
Click to expand...
Click to collapse
did you ever take the 2.20 update?
If so did you remember to flash the boot.img in fast boot?
If that's not the problem maybe a bad flash? go to recovery again and re-wipe then reflash
gunnyman said:
did you ever take the 2.20 update?
If so did you remember to flash the boot.img in fast boot?
If that's not the problem maybe a bad flash? go to recovery again and re-wipe then reflash
Click to expand...
Click to collapse
No i never took an OTA update, but i am on 2.29 instead of stock 1.85. In the aroma installer in Cleanrom i did click flash boot.img ( or i think i did anyway, i clicked "Yes") How do i boot into fastboot? I usually use the extended power settings, but it reboots before i can do that. Also when flahsing the RUU, it says failed, but it also says that i should be at the HTC screen with exclamation points in each corner, but those exclamation points dont appear.
Gosfgiants said:
No i never took an OTA update, but i am on 2.29 instead of stock 1.85. In the aroma installer in Cleanrom i did click flash boot.img ( or i think i did anyway, i clicked "Yes") How do i boot into fastboot? I usually use the extended power settings, but it reboots before i can do that. Also when flahsing the RUU, it says failed, but it also says that i should be at the HTC screen with exclamation points in each corner, but those exclamation points dont appear.
Click to expand...
Click to collapse
just ref lash it. You never took the OTA which means your HBOOT is still the old one. I bet you didn't say yes to boot.img
gunnyman said:
just ref lash it. You never took the OTA which means your HBOOT is still the old one. I bet you didn't say yes to boot.img
Click to expand...
Click to collapse
Are you talking about Cleanrom or the RUU? It reboots into the set up screen whenever i try to boot into bootloader (By holding power and the volume rocker), but that quickly crashes and reboots into the same screen again, so i don't know how i would be able to reflash it. If you are talking about the RUU, I have tried reflashing it three times, and every time it says "Utility can not update device"
Gosfgiants said:
Are you talking about Cleanrom or the RUU? It reboots into the set up screen whenever i try to boot into bootloader (By holding power and the volume rocker), but that quickly crashes and reboots into the same screen again, so i don't know how i would be able to reflash it. If you are talking about the RUU, I have tried reflashing it three times, and every time it says "Utility can not update device"
Click to expand...
Click to collapse
hmm
so you can't get into the bootloader at all?
which RUU are you trying to run?
gunnyman said:
hmm
so you can't get into the bootloader at all?
which RUU are you trying to run?
Click to expand...
Click to collapse
I cant figur eout a way too, and i am trying to flahs the 1.85 RUU,which i have used before.
this happened to me yesterday going from TN SE 3.7RC1 to the stable 3.7. I was able to get into recovery though, wipe everything, and get back up and running (but did not run a TB beforehand :crying Don't know what caused the bootloop though.
Gosfgiants said:
I cant figur eout a way too, and i am trying to flahs the 1.85 RUU,which i have used before.
Click to expand...
Click to collapse
ok so your phone powers up into a bootloop is that right?
Do you ever see a screen after the HTC screen with the red writing on it? If you do, plug in the phone and open a command prompt. I assume you have ADB installed. If you don't see the link to ADB/Fastboot in my signature.
Anyway, when you see the screen after the HTC screen with the red warning on it, type adb reboot recovery. THAT should get you back to twrp and let you ref reflash.
gunnyman said:
ok so your phone powers up into a bootloop is that right?
Do you ever see a screen after the HTC screen with the red writing on it? If you do, plug in the phone and open a command prompt. I assume you have ADB installed. If you don't see the link to ADB/Fastboot in my signature.
Anyway, when you see the screen after the HTC screen with the red warning on it, type adb reboot recovery. THAT should get you back to twrp and let you ref reflash.
Click to expand...
Click to collapse
Alright, i am donwloading the SDK. Is there anyway to make it go faster i am installing the 4.03 and 4.1 using the SDK manager, and it is taking a while. Or is there a way to just download ADB? I have an old script called ADB that i used to root with.
Gosfgiants said:
Alright, i am donwloading the SDK. Is there anyway to make it go faster i am installing the 4.03 and 4.1 using the SDK manager, and it is taking a while. Or is there a way to just download ADB? I have an old script called ADB that i used to root with.
Click to expand...
Click to collapse
Look at my thread. There's an attachment with all you'll need
gunnyman said:
Look at my thread. There's an attachment with all you'll need
Click to expand...
Click to collapse
Ya i see that now, sorry about that. whenever i try to run ADB, it juts rapidly runs a script and shuts down though.
Gosfgiants said:
Ya i see that now, sorry about that. whenever i try to run ADB, it juts rapidly runs a script and shuts down though.
Click to expand...
Click to collapse
adb is a program that needs a command
adb reboot recovery for example.
gunnyman said:
adb is a program that needs a command
adb reboot recovery for example.
Click to expand...
Click to collapse
Yes! thank you so much! I was able to rbeoot into recovery! so now just reflash Cleanrom?
Yep.
gunnyman said:
Yep.
Click to expand...
Click to collapse
Gunny, you're a smart guy. Please, please help me out here. I'm offering a literal cash reward for help with this.
http://forum.xda-developers.com/showthread.php?p=31365825#post31365825
Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.
What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!
LifeAsADroid said:
What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!
Click to expand...
Click to collapse
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.
LifeAsADroid said:
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.
Click to expand...
Click to collapse
once the bootloader is unlocked, it cant be locked back.
Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.
LifeAsADroid said:
Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.
Click to expand...
Click to collapse
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.
so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
RikRong said:
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.
Click to expand...
Click to collapse
peladoro said:
so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
Click to expand...
Click to collapse
Yes, but you won't be able to unlock if you're system version is newer than May.
hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
RikRong said:
Yes, but you won't be able to unlock if you're system version is newer than May.
Click to expand...
Click to collapse
peladoro said:
hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
Click to expand...
Click to collapse
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.
hehe...ok thanks again!!!
RikRong said:
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.
Click to expand...
Click to collapse
RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Hello
Please can you explain step by step how to install a cwm ? (i just unlock the bootloader)
Do i have to root the phone to do that ?
Thank you
I rooted my phone and used firewater to get S-OFF (a lifesaver), then unfortunately installed a TWRP recovery that has completely messed up the device. It wouldn't respond at all and I was lucky enough to flash CWM when I got it back to bootloader. Now, at least I do have a recovery to work from.
I can't do a factory reset (just goes back to recovery), can't sideload a new ROM, and tried to flash a new boot.img and system.img from here:http://forum.xda-developers.com/showthread.php?t=2706233
None of these have worked and I'm at a loss in terms of what else I can do to get the phone working again. Any ideas????
Alex
Bump
Sent from my HTC One M8!
U WOT M8?
AP26322 said:
I rooted my phone and used firewater to get S-OFF (a lifesaver), then unfortunately installed a TWRP recovery that has completely messed up the device. It wouldn't respond at all and I was lucky enough to flash CWM when I got it back to bootloader. Now, at least I do have a recovery to work from.
I can't do a factory reset (just goes back to recovery), can't sideload a new ROM, and tried to flash a new boot.img and system.img from here:http://forum.xda-developers.com/showthread.php?t=2706233
None of these have worked and I'm at a loss in terms of what else I can do to get the phone working again. Any ideas????
Alex
Click to expand...
Click to collapse
Have you tried pushing back the stock recovery and then doing a factory reset?
droidkevlar said:
Have you tried pushing back the stock recovery and then doing a factory reset?
Click to expand...
Click to collapse
I have not. Where can I find the stock recovery?
AP26322 said:
I have not. Where can I find the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2708291
Stock recovery, boot and hboot are in there. I would start with the boot, then recovery, and then factory reset.
droidkevlar said:
http://forum.xda-developers.com/showthread.php?t=2708291
Stock recovery, boot and hboot are in there. I would start with the boot, then recovery, and then factory reset.
Click to expand...
Click to collapse
Thanks so much. Installed the boot, then recovery and it's back to working like a charm. Great to know all of these .imgs are in one place, too. You're a lifesaver!
http://forum.xda-developers.com/showthread.php?t=2708291
Try it.
AP26322 said:
Thanks so much. Installed the boot, then recovery and it's back to working like a charm. Great to know all of these .imgs are in one place, too. You're a lifesaver!
Click to expand...
Click to collapse
NP
Well, like some of the others I applied the OTA from Verizon today without thinking....I have S-Off, and a rooted stock rom. So yeah, I did the dumb thing of accepting the OTA. :crying:
The device restarted, and hung at the red Verizon screen. Plugging the phone into my computer I was able to use adb to get into recovery. I did a couple things: 'Cleared cache', then rebooted into recovery, then cleared my data/factory reset. Unfortunately, after the reset, I can't get my device to show up in adb anymore. Not listed under the fastboot devices either.
Anyone have any ideas?
Fixed.
Finally got adb/fastboot to connect again. Was able to flash newest firmware, twrp, and stock 5.0.1 again. Now just gotta reinstall everything O.O
care to share how you got it fixed? Have the same issue and can't get adb to see device
Flash the RUU that dottat made.
andybones said:
Flash the RUU that dottat made.
Click to expand...
Click to collapse
Kinda hard to flash anything when you only get a red verizon screen. or when i try to go into recovery i get hboot telling me i have a update, do i want to install and to select yes or no. no matter which choice i make it always goes back to the verizon screen, no options for recovery because its always telling me to choose to update. nothing else.
cmay227 said:
Kinda hard to flash anything when you only get a red verizon screen. or when i try to go into recovery i get hboot telling me i have a update, do i want to install and to select yes or no. no matter which choice i make it always goes back to the verizon screen, no options for recovery because its always telling me to choose to update. nothing else.
Click to expand...
Click to collapse
Um, remove your SD card(which sounds like it has a firmware or ruu file on it)?...boot to hboot, run ruu, or boot to recovery and sideload a rom.
andybones said:
Flash the RUU that dottat made.
Click to expand...
Click to collapse
santod040 said:
Um, remove your SD card(which sounds like it has a firmware or ruu file on it)?...boot to hboot, run ruu, or boot to recovery and sideload a rom.
Click to expand...
Click to collapse
Now i feel stupid. Thanks. It's my wifes phone. and I'm so use to my nexus phones not having sd cards didn't even think of that.
cmay227 said:
Now i feel stupid. Thanks. It's my wifes phone. and I'm so use to my nexus phones not having sd cards didn't even think of that.
Click to expand...
Click to collapse
No need to feel stupid, now you know and are therefor smarter now...
Hope that gets it going for you/her again at least. [emoji106]
Sent from my HTC6525LVW using Tapatalk