Hi All,
My wife's phone (stock Pixel 3 - not rooted) updated to the July security release last night and since then, the phone keeps shutting down after 30-60 seconds. I've performed a factory reset and it's stable all through the setup process until it updates what looks like the play libraries. Any thoughts on how to keep it stable? Thanks in advance, I've been on XDA for a while and the forums have been awesome.
rbillings said:
Hi All,
My wife's phone (stock Pixel 3 - not rooted) updated to the July security release last night and since then, the phone keeps shutting down after 30-60 seconds. I've performed a factory reset and it's stable all through the setup process until it updates what looks like the play libraries. Any thoughts on how to keep it stable? Thanks in advance, I've been on XDA for a while and the forums have been awesome.
Click to expand...
Click to collapse
Is her phone bootloader unlocked (or capable of being unlocked)? If so, you can do a flash-all of the factory image (you can edit the flash-all batch file to get rid of the -w and retain apps/user files or leave the batch file as is and do a full reset). https://developers.google.com/android/images Otherwise, possibly the best place to start (and it can be done without unlocking the bootloader) would be to sideload the July OTA. https://developers.google.com/android/ota
sliding_billy said:
Is her phone bootloader unlocked (or capable of being unlocked)? If so, you can do a flash-all of the factory image (you can edit the flash-all batch file to get rid of the -w and retain apps/user files or leave the batch file as is and do a full reset). https://developers.google.com/android/images Otherwise, possibly the best place to start (and it can be done without unlocking the bootloader) would be to sideload the July OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
Thanks - I'll start with the sideloading of the July OTA. I've tried unlocking the bootloader, but it seems the refurb phones I purchased came from Verizon stock, so the setting to allow the bootloader to be unlocked is grayed out (unless there's another way - flashing unlock_critical or unlock_bootloader isn't supported).
rbillings said:
Thanks - I'll start with the sideloading of the July OTA. I've tried unlocking the bootloader, but it seems the refurb phones I purchased came from Verizon stock, so the setting to allow the bootloader to be unlocked is grayed out (unless there's another way - flashing unlock_critical or unlock_bootloader isn't supported).
Click to expand...
Click to collapse
Unfortunately, there is no other method to unlock. The Verizon units are locked down very hard. The OG Pixels from Verizon had an exploit found early on that was patched immediately and another that was found right as the Pixel 2 was coming out. The Verizon Pixel 2 never got exploit unlocked nor has the 3 in almost a year of various peoples' attempts. In reality, there is little incentive for anyone with the necessary skills to crack it since Google sells the version that is unlockable.
Good luck with the sideload. Keep in mind that the sideload will install to the other slot and then reboot to the sideloaded image (in case you have more issues). If you continue to have issues, the dreaded factory reset is the next step.
sliding_billy said:
Unfortunately, there is no other method to unlock. The Verizon units are locked down very hard. The OG Pixels from Verizon had an exploit found early on that was patched immediately and another that was found right as the Pixel 2 was coming out. The Verizon Pixel 2 never got exploit unlocked nor has the 3 in almost a year of various peoples' attempts. In reality, there is little incentive for anyone with the necessary skills to crack it since Google sells the version that is unlockable.
Good luck with the sideload. Keep in mind that the sideload will install to the other slot and then reboot to the sideloaded image (in case you have more issues). If you continue to have issues, the dreaded factory reset is the next step.
Click to expand...
Click to collapse
Sadly, that didn't work, and I've already done the factory reset mode, since that was the only way to get into the phone originally. I'll keep playing, I have some logcats, but I'm not seeing anything out of the ordinary, except previously, once all of the the software finally got reloaded from the backup (multiple reboots) it shutdown at a similar point.
I'll update with results after I try a few other things. Thinking possible HW issue, but strange that it was working until yesterday's update...
rbillings said:
Sadly, that didn't work, and I've already done the factory reset mode, since that was the only way to get into the phone originally. I'll keep playing, I have some logcats, but I'm not seeing anything out of the ordinary, except previously, once all of the the software finally got reloaded from the backup (multiple reboots) it shutdown at a similar point.
I'll update with results after I try a few other things. Thinking possible HW issue, but strange that it was working until yesterday's update...
Click to expand...
Click to collapse
Possibly hardware, but too hard to diagnose that. The only thing I would say is to not restore any backed up apps or anything. They will be in your library if you need to install them. Just keep it as stock as possible after the factory backup until you have at least had a chance to put it through its paces for a little while.
Related
Hi guys,
i have a pixel and i want to enrrol to the beta program, i just done the process but it seams that update is not arriving, its posible that verizon pixels can't enroll to beta program?
http://www.droid-life.com/2017/01/30/android-7-1-2-beta-download-update-nexus-pixel/
Regards
You can download the full image here
I dont have oem unlocked. I can sideloade it?
Yea even i didn't get it. I guess it not for the verizon phones.
Can anyone who has upgraded to 7.1.2 let us know if it appears stable enough for a daily driver and have they noticed any differences ? Thank you.....
Another locked bootloader VZW customer here who enrolled and is waiting for OTA. I think we'll get it, just have to wait for OTA's to start. Google let us enroll, and we seem to have gotten updates from Google and not VZW so far. I think it'll just take a day or 2 to start rolling.
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
I am a non VZW pixel user (Koodo - Canada) and have not received the OTA after signing up yesterday. They note that it may take 24 hours and looks like it's going to for me.
k.s.deviate said:
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
Click to expand...
Click to collapse
I know that the bootloader is what loads the Android filesystem to the boot image, I wonder if it can somehow be manipulated to unlock and root since you mention that the boot image is different? Does anyone know? Thanks
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
farfromovin said:
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
Click to expand...
Click to collapse
Signed up yesterday for both my Pixel (VZW sim) and Pixel XL (Project Fi sim) both bought direct from Google. Pixel XL rec'd update almost immediately not yet on Pixel so far.
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Sent from my Pixel using Tapatalk
joshw0000 said:
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Click to expand...
Click to collapse
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Nope it's exactly that. Just remove -w so it doesn't wipe the device. It's how I update my Pixel and 5X since I'm impatient waiting for OTAs.
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Sent from my Pixel using Tapatalk
joshw0000 said:
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Click to expand...
Click to collapse
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
OTA hasn't rolled for the pixel yet, likely "soon", my guess is today or tomorrow at the latest since XL has gone out. I am on project FI and got the pixel through the play store fyi
murryrulz said:
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
Click to expand...
Click to collapse
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
I am also in the waiting for the OTA camp and use an unlocked Verizon Pixel and PIxel XL. I have had better luck using the TWRP sideload method and it installing to the other slot with each subsequent sideload appears to me a more consistent way to keep everything updated in the same way that the system OTA works.
joshw0000 said:
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Get rid of windows, use Linux, no messing around with anything, it just works ?
-------- runs -----_ducks_---- runs ----
Sent from my Pixel using XDA-Developers Legacy app
So I was away from my computer when the January Security update came out so Im on the December update.
I would like to know can I just jump straight to the Feb update when its available or do I need to do Jan first then Feb?
im unlocked, rooted, ex kernel, google store phone. thanks.
You can just jump.
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
kidhudi said:
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
Click to expand...
Click to collapse
I think downgrading via OTA it's quite impossible.
You have to wipe and flash the full factory image.
damn it thats what i was afraid of.
thanks
kidhudi said:
damn it thats what i was afraid of.
thanks
Click to expand...
Click to collapse
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
TonikJDK said:
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
Click to expand...
Click to collapse
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
kidhudi said:
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
Click to expand...
Click to collapse
Time to start clearing data on the dialer related apps, or reset the phone. I am hopeful that will help you. If it was soley update related the forum would be blowing up with complaints.
Now did something go wrong with your update... I'll buy that.
i just assumed it was the april security update it started acting up around the same time. i thought maybe a crappy download
i already did a few factory resets. tried third party dialers. everything i could think of.
what really sucks is i am 3 months out of the 1 year google warranty. so i am pretty much screwed.
thanks for your help bro
i will try to sideload the latest ota.. if it is still jacked up then it is probably hardware related
what sucks is i am still paying it off and it is virtually unusable lol.. at least i can text
Hey all,
I've restored my girlfriends pixel using the original android 8 image. (It was using PureNexus before). However, she just got the update notification (september update?) but it doesn't do anything when she taps it. The phone should not be rooted, as I used the original clean factory image.
Any suggestions? I've looked at this thread https://forum.xda-developers.com/pixel/help/taking-september-security-update-rooted-t3672586 and so am prepared to download the latest update and remove the "-w" part, but shouldn't it allow her to take the update anyway? Am I going to have to always do this every time they release an update?
Thanks!
It should work, so long as you restored everything to stock - system, bootloader, recovery (dunno if radio matters).
If it's not working most likely there's something custom hanging around somewhere...
I believe it will also fail to update if the bootloader is unlocked. Not sure if you have a VZW device but that's how it works for them. I just update by flashing the full factory image, not an OTA file. Removing the -w will retain user data.
FernBch said:
I believe it will also fail to update if the bootloader is unlocked.
Click to expand...
Click to collapse
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
jss2 said:
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
Click to expand...
Click to collapse
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
joeyfeffer said:
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
Click to expand...
Click to collapse
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
TonikJDK said:
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
Click to expand...
Click to collapse
Oh gotcha gotcha.
Weird issue though I couldn't get update to the latest image. I was only able to flash the bootloader and radio. When I tried updating the image it said it couldn't find some of the files. Do I still need to keep the line as "fastboot -w update" when updating the image? won't the "-w" do the wipe?
Nevermind I figured it out. I guess I was inputting the wrong command.
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
u found any way to unbrick your phone?
yuva_cool said:
u found any way to unbrick your phone?
Click to expand...
Click to collapse
Nope. The RMA was approved and I'm using a new (refurbished) device.
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
yuva_cool said:
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
Click to expand...
Click to collapse
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
computerslayer said:
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
Click to expand...
Click to collapse
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
robocuff said:
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
Click to expand...
Click to collapse
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
computerslayer said:
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
Click to expand...
Click to collapse
If that's the case, it's a certainty that that's the cause of your problem. You have to be completely stock when you relock it. Flashing the factory boot image should take care of that if all you have done is installed Magisk. That said, I'd still flash the factory image and let it do the wipe, just to be sure.
computerslayer said:
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
Click to expand...
Click to collapse
I have this issue and now my pixel 2 cant boot. It stuck. Cant enter fastboot. This is my last experience with pixel series devices. Its expensive phone, but its too sensitive to brick. I dont know why, an update or a flashing stock rom can make your phone totally unuseable. I just cant accept it
I had exactly the same issue. just keep holding the power button with or without the vol- for a good 30~ seconds or so (it will restart several times) but keep holding.
and make sure you are connected to the PC until you hear the ding that the phone got recognized, then the phone will accept fastboot commands.
This worked for me before I was going to throw the phone in the garbage!
Hey everyone,
I have the following issue with my recently purchased Google Pixel smartphone. The other day I was trying to update to the Android Q Beta, but in the middle of the process the phone turned off.
All I have now is a phone with a locked bootloader. I cannot neither unlock the bootloader nor sideload any OTA (when I try doing so I get a "no devices/emulators found" message). I tried unlock the bootloader with the Unified Anroid Toolkit, but no go because of the same message.
Any thoughts how to revive it?
To get more, better answers. Full battery?, what was working system, unlocked?, update Q well exactly how, ota? Verify cables, different pc, verify drivers? When described as brick= what, how, display?. No matter what you will need bootloader to get working. Then factory images flash.
kkjb said:
To get more, better answers. Full battery?, what was working system, unlocked?, update Q well exactly how, ota? Verify cables, different pc, verify drivers? When described as brick= what, how, display?. No matter what you will need bootloader to get working. Then factory images flash.
Click to expand...
Click to collapse
It bricked while installing the beta and simultaneously charging approximately at 60% battery. Prior to trying to install the latest beta 3 I had the beta 2. Updated the system officially via Settings. Unsure if it was unlocked and I'd just bought the Pixel and randomly decided to update it.
The usb-c cable is fine and is working with other devices. It's also the same with other PCs.
All I have is a bootloader with some options - Start/ Restart Bootloader/Recovery mode (it won't load)/Barcodes.
So when using adb "fastboot devices" command do you get your device number returned? If so, was the data important to keep not wiped? Because a factory images flash is next. Or can look search on manually flashing bootloader or recovery or twrp recovery too. Data most likely gone with Q beta 2 but you may get it back. I would factory flash since you have fastboot available... Best so all of memory is correctly wiped, flashed.
kkjb said:
So when using adb "fastboot devices" command do you get your device number returned? If so, was the data important to keep not wiped? Because a factory images flash is next. Or can look search on manually flashing bootloader or recovery or twrp recovery too. Data most likely gone with Q beta 2 but you may get it back. I would factory flash since you have fastboot available... Best so all of memory is correctly wiped, flashed.
Click to expand...
Click to collapse
Yes, I get a device number with this command. I usually back up all the necessary data, so I don't really need what's on the phone and I can wipe it.
How can I do a factory image flash?
Best case then is to flash factory image, download either Q beta 3 or May stock image. Completely wipes and starts from scratch. Look at the many instructions, if need more guidance under flashing factory images. Q beta 3 is good, but if you flash Q through this process can't OTA to next version. So if that's a issue do May image then go back to ota through as before.
kkjb said:
Best case then is to flash factory image, download either Q beta 3 or May stock image. Completely wipes and starts from scratch. Look at the many instructions, if need more guidance under flashing factory images. Q beta 3 is good, but if you flash Q through this process can't OTA to next version. So if that's a issue do May image then go back to ota through as before.
Click to expand...
Click to collapse
But as far as I understand, I can't flash a factory image with a locked bootloader, can I? Also I don't have OEM unlocked
Correct. When you got the device number back from fastboot I guessed it was authorized. Which means OEM unlock. So I am at a loss at how much more to "help". Is your pixel unlockable in the first place? Verizon or carrier locked?
kkjb said:
Correct. When you got the device number back from fastboot I guessed it was authorized. Which means OEM unlock. So I am at a loss at how much more to "help". Is your pixel unlockable in the first place? Verizon or carrier locked?
Click to expand...
Click to collapse
Well, I have no idea if it's unlockable. I'm from Russia, so it's not Verizon or any other.
Pixels have unlockable or not bootloaders. Carrier sim lock (Verizon us carrier) have a exploit to unlock. In your case, if I have it right- accepted ota
Update to Q beta. As first post. So when failed, and would not boot to G screen. Power off then on if you hold down power + volume get bootloader. Now options are limited to restart bootloader, off, start, recovery. Tried and nothing, then went to recovery....got android icon laying down with red warning. So when you have that screen a different set of button pushes will give more options. So search how to factory erase through recovery. Hopefully will wipe bad q and return to before system...the one that was running correctly before last accept ota q.
kkjb said:
Pixels have unlockable or not bootloaders. Carrier sim lock (Verizon us carrier) have a exploit to unlock. In your case, if I have it right- accepted ota
Update to Q beta. As first post. So when failed, and would not boot to G screen. Power off then on if you hold down power + volume get bootloader. Now options are limited to restart bootloader, off, start, recovery. Tried and nothing, then went to recovery....got android icon laying down with red warning. So when you have that screen a different set of button pushes will give more options. So search how to factory erase through recovery. Hopefully will wipe bad q and return to before system...the one that was running correctly before last accept ota q.
Click to expand...
Click to collapse
Recovery mode is not working for me either. Any chance to factory erase it any other way?
https://www.androidexplained.com/pixel-factory-reset/ explains hard factory reset with bootloader. If still can't reset through that method, then I believe no options. I would search pixel threads with "hard brick" or "soft brick" and see if any other way.
im in the same boat. bootloader locked, can not access recovery. OEM-Unlock from system unchecked. fastboot commands needs unlocked bootloader. no idea what to do.
kkjb said:
https://www.androidexplained.com/pixel-factory-reset/ explains hard factory reset with bootloader. If still can't reset through that method, then I believe no options. I would search pixel threads with "hard brick" or "soft brick" and see if any other way.
Click to expand...
Click to collapse
Unfortunately, it explains the reset only in case a pixel can be turned on or factory mode is available.
wahur1 said:
im in the same boat. bootloader locked, can not access recovery. OEM-Unlock from system unchecked. fastboot commands needs unlocked bootloader. no idea what to do.
Click to expand...
Click to collapse
Just checked your thread and all I have to say I'm in a completely similar situation.
Might be a longshot but I remember a few people saying about using the fastboot continue command to get a soft bricked pixel booted. Not sure on their mileage using it but worth a punt.
junglism93 said:
Might be a longshot but I remember a few people saying about using the fastboot continue command to get a soft bricked pixel booted. Not sure on their mileage using it but worth a punt.
Click to expand...
Click to collapse
Yeah, I tried this one, but still no go. Thanks.
mighty_ok said:
Just checked your thread and all I have to say I'm in a completely similar situation.
Click to expand...
Click to collapse
I guess its a paperweight now.