3 days, still not installed hardspl - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

Guys,
3 days after my first attempt to flash a rom (beside the beatiful palms very long ago).
My first attempt stuck at 19%. After that I stuck in the three color screen. I thought it was a brick now. After searching the forum I could give my kaiser a second live through mtty and 2 commands. yeeh.
But after that every new attempt to flash the three color screen did not appear. When I forced a three color screen (through the camera button) I of course got a connection error.
I'm sure that I'm do something wrong, but I can't live (as a meaning, not for real )with the Idea I cannot put another rom on my kaiser.
I also tried jumpSPL.156, but that won't start on my device (complaining about certificates and or missing components, but in dutch language)
device information
vario iii
rom 1.56.114.4
date 9/1/07
radio 1.27.12.11
bootloader
KAIS130
SPL-3.03.0000
CPLD-8
Hope someone can tell me the right direction.
Regards
Chris Gradussen
These

from the jumpspl 1.56 thread:
jockyw2001 said:
Notes:
1. if when running a JumpSPL an error is shown try to application unlock your device first with SDA_ApplicationUnlock (you must run this on PC with an activesync connection via USB cable). If you still get errors you need to hard reset your device (power off, keep both left and right navigation keys pressed and power on)
Click to expand...
Click to collapse

I hope u'll find a solution in this link:
http://forum.xda-developers.com/showthread.php?t=354061

Thanks,
The hard reset solved evertything!

Related

Help

I did upgrade in my O2 Neo, but after upgrade rom i´ts don´t turn on
What i cam do ?
O2 Neo is not a Magician, it is a Prophet (I think)
Anyway, we need more infor. What you do use to upgrade, where did you get it from, how do you perform your upgrade, any error message during upgrade, what's the sign now, all dark, hang on a particular screen, etc.
My Pocket is PM300 HTC
I did upgrade, and this show 100% and reset the pocket after upgrade, by this dont work, the screen splash blink only and turn off.
The led Red and Blue is blinks.
I used RomUpdateUtility HTC and the rom image i used Xda_Minis_Upgrade_v2.21.4.101
You used the ROM of a XDA-miniS (aka `Wizard`) to upgrade your `Prophet`. You are seriously screwed. You may have made yourself the most expensive paper weight you ever had.
Anyway, try see if you can boot into bootloader mode (3 colour screen). If you can do that, there are still hope.
My Pocket is PM300 HTC died
This show
IPL 2.21.0001
SPL 2.21.0001
and turn off i can´t update the rom.
What can i do ?
gmarcel said:
This show
IPL 2.21.0001
SPL 2.21.0001
and turn off i can´t update the rom.
What can i do ?
Click to expand...
Click to collapse
I need more details. That do you mean by `This show`? Where is these information shown? in the bootloader (3 colour screen) or the initial screen where your phone freeze. If you were able to get into the bootloader, you might able to get your Prophet ROM into it. Just start on bootloader mode, and plug in the USB. Activesync will not tell you anything, but you ought to able to still upgrade/refresh a Prophet ROM into it (eg running those ROM with EXE).
Can someone confirm if the ROM he used has IPL/SPL in or not?
Mod, can you move this to Prophet section.
More detail
These information shown in the bootloader (3 colour screen)
the initial screen show only O2.
i cant get bootloader, the Prophet only flashes.
The Activesync not tell anything.
I need move this for Prophet ?
gmarcel said:
These information shown in the bootloader (3 colour screen)
the initial screen show only O2.
i cant get bootloader, the Prophet only flashes.
The Activesync not tell anything.
I need move this for Prophet ?
Click to expand...
Click to collapse
Your statements are contradicting. You said you get these information from bootloader screen but you said you can get bootloader?
Anyway, if can get the bootloader screen. Just stay there. Connect it to your PC. And choose a *Prophet* ROM with EXE extension to run on your PC. It works most of the time. For step by step instruction, do a search here. I bet there are lots of similiar cases.
I can´t get bootloader
The screen with three coulours show about 3 seconds and this turn off.
I hope I'm wrong, but if your bootloader is gone, you device is gone. Hope others can help.

i think i have brick my dopod 818pro.. Please help

i think i have brick my dopod 818pro
have follow the step 1 and install without any error.
then installed the Cert_SPCS.cab and EnableRapi.cab.
then installed the Prophet_4.0.0.0.1_PV rom by running Upgrade_ROM.bat from the computer.
after that restat the device.
AND the phone boot after the HTC Innovation screen and stay at the loader screen.
NOw my screen only showing :
IPL 2.15.0001
spl 2.15.0001
gsm 02.69.21
os 4.0.0.0
and wouldn't boot in ???
anyone here please help
tq
finnally manage to boot in.
redo the step 1 in boot loader mode.
then installed the pdaviet 4.0.0.0.1 from pc
and it is done.
very nice screen
will try it out n c .
tq very much
Hi, how did you manage to solve the issue?
My situation is a little different.
-Load Step 1... ok Successful
-Load Upgrade_Rom.bat... completed
But when I reboot the PDA I just get this screen!!!
Nothing is responding.
PC cant detect the device.
Hard reset also get back to the same screen.
Please help
reboot your device into the bios screen (reset while holding camera button)
at that point i usually just put on the default WM5 comming from QTEK to reestablish operations.
i am using the prophet touch series from gullum and for that i do the following steps after having reestablished the WM5.
Put on PDAViet_TEMP
wait until phone restarts and shows 'Touch to get started'
Put on the Prohvet Touch (VIII or IX Beta)
Hard Reset (Com and Cam button, wait for the message asking to confirm afetr you release the reset button but hold on to com and cam buttons until message pops up) Confirm Hard Reset
So far i repeated this process about 6 times and it works every time
best of luck
need explanation
im planning to buy a dead prophet.....as the seller states...when he posted the pic, it still enters bootloader mode...but it shows
IPL: 1.00
SPL: 2.20.0001
Can this still be repaired? and is this possible? how can i repair it...it is being sold at a very cheap price
I've had similar issues and by just putting the original rom or the WM5 if you can enter bootloader mode thenit comes back to live. Once WM5 which is very stable is loaded, you can upgrade to the WM6 roms. Has always worked for me but it is a bit nerve racking to see the thing frozen. The key when upgrading is to use than WM5 rom and upgrade from there.

Help with a "Bricked" Tilt!

Any Help Appreciated. Anyone ever seen this type of "Brick"?
After flashing a new ROM (Tilt XDA-Live v1.0 - fully flashed to 100% and said finished), the device won't boot. It just gets stuck in an endless loop. It trys to boot, shows the AT&T screen, then reboots/resets back to the beginning before getting to the Windows mobile screen.
The only way to get it to stop the loop is to pull out the battery. Put the battery back in and power on and you get the loop again.
I have loaded HARD SPL (1.0.OliPof).
I can get into Bootloader mode by pressing power/camera then reset.
In this mode, I can get it to reflash the ROM (and even other ROMS) but it still ends up in the same loop.
I have tried flashing the Official ATT WWE ROM from this thread but it still loops at boot.
I did the "original/problematic" flash using Vista. Could that be the issue? I have done subsequent "recovery" flashing using XP to no avail.
I have flashed several ROMs to my Tilt in the past (Mostly Dutty ROMs).
I had a Hermes before and flashed that a million times no issue so I'm not a complete noob.
Any ideas? I'm stuck with a brick!
Thanks in advance.
I'm in the same boat. I've flashed over and over (with different ROMs) and am still stuck. But I did every flash from MicroSD card. Did you get any help?
No input yet.
What ROM did you flash that started the problem for you?
dutty's touchflo rom beta for the tilt. i was on dutty's hybrid rom version 3. after flashing the OEM at&t ROM, i'm out of ideas. stay in touch if you find a fix. i'll keep searching.
- J
Bump...
Anyone else seen the issue with a Tilt stuck in a "boot loop" after flashing (see first post)?
Paypal reward for anyone who helps me recover - otherwise I'm going to have to go buy another Tilt (which I could live with but worse yet, I may be stuck with the stock ROM because I'm too gunshy to go back to my flashing ways)
Tried all day to find a fix. Think I made things worse. Read up on some threads using the mtty tool and ran a command (task 2a) that cleared the flash. But now it doesn't even boot to a splash screen, and I can't get back to bootloader mode.
This might sound a bit stupid, but I have taken note that my device upon flashing the new at&t rom actually held some of the information, you would think that a hard reset is performed after a rom flash, but that just wasn't how it worked out for me, anyway I had a radio that wouldn't come up, but would after a hard reset, this was directly after flashing my tilt...
?Glitch
Glitch,
Yeah, I have heard in several places that you need to hard reset after a flash to clear out all the settings from the old ROM. Seems odd since you just overwrote ROM - I think of it as a format (HDD mindset) but I guess it's not a clean format.
Jerich007,
Sorry to hear you went backwards. I stopped flashing my Tilt for the same reason - worried about getting farther in the hole without some expert advice. My next step was to try the MTTY tool just as you noted. Guess I'll go that route as a last resort. If it's any consolation, I seem to remember reading about plenty of people recovering from a "brick" that won’t go into bootloader mode.
Hopefully someone trolling the waters will see this thread and take up the offer for a Cash Reward (Paypal) for help recovering this Brick!
ill put up some paypal $$ for a fix as well. i'm at the end of my rope on this one. i'm subscribed to some other threads so hopefully we'll get some feedback.
It is not so serious as you think! Try the following way:
1- Download the original rom from AT&T (the 1st rom was installed on your device)
2- Turn your bricked Tilt to bootloader ( http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets )
3- Start flashing your Tilt with the above AT&T rom.
Evething should be OK after that! (but your device need to be installed Hard-SSPL before!!!)
try...
try this link
http://forum.xda-developers.com/showthread.php?t=286755
and maybe these
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=334693&highlight=how+to+unbrick
http://forum.xda-developers.com/showthread.php?t=344402&highlight=how+to+unbrick
don't forget that some of this info isn't for the tilt...
good luck, and be careful
This ROM solved my issues
try this thread
http://forum.xda-developers.com/showthread.php?t=327482
and DEFINETLY download the ROM, flash it. Once it's flashed,then ya can reflash any ROM ya want. Get the newest stock ROM from the sticky and reflash it (if ya want the ATT ROM)
That will fix it.
(I reflashed Tilt XDA-Live v 1.0, and it's working GREAT.)
I did the same thing to my Tilt.
That ROM saved me.
Alemaker
Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.
...
Hate to say it, but if after hours of searching on the forum you can't find an answer, i'd pm a pro like pof. I don't know if that will work, but their advice is the only thing i'd listen to.
Don't forget to give a lot of detail and maybe mention what you've tried.
Thanks. I've already PM'd pof and olipro. Hopefully they can come up with something.
jerich007 said:
Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.
Click to expand...
Click to collapse
****, I should have replied after someone posted all those links to Hermes unbrick procedures, to never do a task 2a from hardSPL. It reformats entire flash including SPL and the problem with hardSPL is that you can't flash another SPL, even if you would have tried before rebooting
Anyhow, your only chances to unbrick your device are to try to enter radio bootloader (there is a radio bootloader running on the mARM (ARM9)) and then to flash it. However, only service centres have such flashx utilities I'm afraid. Furthermore I'm not sure if radio bootloader can be entered directly, usually you can enter it via the normal CE SPL. You can try to first connect USB and then press reset with the stylus while holding the Voicecmd key. If you are in XP, then three new devices should be found (composite USB, a modem and a diagnostics port). Download the Motorola "Q" usb drivers, these will work just fine. In this mode you will have to authenticate to the radio bootloader before you can start entering commands. We'll get to that if you manage to connect. Your other chance to unbrick is via JTAG. I know the kaiser has JTAG points scattered on PCB.
Ok, thanks, I'll search for those drivers and let you know. By Voicecmd key do you mean the push-to-talk key along the side or the talk key with the green phoneset icon?
The top button at the left hand side
Ok here's what happens:
1. downloaded Motorola USB drivers (32-bit) from their site, installed and rebooted.
2. plugged in Tilt via usb cable, 'found new Hardware wizard' starts.
3. clicked next to auto-search for drivers, but the wizard fails with 'cannot install this hardware' message. I have 3 yellow question marks in Device Manager for 'Data Interface' devices.
4. held down Push-to-talk button and hit soft reset. No change, no leds are lit, screen is off.
Did I grab the right drivers?
Not bad at all. Apparently your phone is in Qualcomm DIAG mode, probably as a consequence of task 2a Now you can forget about rebooting with Voicecmd pressed.
Either you've got the wrong drivers or you don't install them in the correct way. Go in device manager, right click one of the 3 and update driver, then 'install from a list or specific location (Advanced)', then check 'Include this location in search' and enter the driver path. I'll take a quick look if I can find the drivers for you, I vaguely remember they were on mobile-files dot com.
EDIT: found the drivers, attached. The VID and PID of the found usb devices should be VID_05C6&PID_6000. Take a look in the device's advanced tab in device manager.
PS: Although diagnostics mode sounds great, I haven't yet found a way to flash the device. Perhaps it works with that Hermes radio flasher MaUpgrade_NoID.exe
Guys with a working SPL can enter radio bootloader DIAG mode via "rtask b", exit MTTY and install drivers. It would be great to know if someone has a htc/qualcomm radio flash utility (perhaps MaUpgrade_NoID.exe is what you need)

ERROR 262 - Bricked phone with Radio Rom Upgrade - SOLVED -

Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBH​KAIS 1*0
SPL-1.56.0000
CPLD-8
USB​
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!
I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.
Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen
Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.
http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...
i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?
like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results
The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.
I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.
Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.
Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse
Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.
pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....

Another tri-color screen issue

Hi Guys,
First of all, I would like to apologize in advance for making a double post if this is one. But after spending over an hour reading the search results I gave up.
This is the deal:
I upgraded my ROM not to long ago after I got my kaiser back from repair (display was cracked). I installed the dutch shipped HTC ROM. All was working fine except I had some performance issues.
Well, anyway, I didn't have any connection with my provider when I woke up this morning. So I tried to switch off the phone, took the battery out and put it back in again and tried to start up the damn thing.
And now it's stuck in the bootloader with the following message:
----------------
KAIS130 MFG
SPL-1.0.lipof
CPLD-8
SERIAL
----------------
When I connect my phone to my computer the SERIAL message turns into a USB message.
I tried to connect with mtty.exe but it cannot open the USB connection.
Can you flash another ROM (Cooked or Shipped, doesn't matter) when your at the bootloader (tri colour) screen?
Thanks
Dave
Thanks for your reply!
I did this already, I tried to install another HTC shipped ROM. After upgrading, wich went smooth, it freezes again in de tri-color screen.
I'm afraid I'll just use up all the battery power cuz the indicator that the batt is charging also wont lit up.
So to answer your question, yes I can
Hi, Try hard SPL 1st and reinstall thsoe fine cooked rom. as long as your device is able to lunch tri-color screen. it is not a brick at all!
Taken from pof.
1. Download mtty.exe
2. Disable activesync (connection settings -> uncheck "allow usb connections")
3. Connect your Kaiser to PC using USB cable.
4. Open mtty, select USB port and click OK.
5. Hit ENTER twice, you should see the "Cmd>" prompt.
6. Type the command "boot", you should see something like this:
EDIT:
@k2againstmachine: HardSPL is installed, his SPL version is SPL-1.0.OliPro
EDIT 2:
Failing that do and "info 8" in mtty and then contact GSLEON3, He'll probably be able to help you, if you buy him a beer
Ta
Dave
Thanks Dave,
I did this, and well, it now gives me a white screen and every now and then the tricolor screen appears and disappears again.
See my EDIT2 point.
This is the limit of my knowledge. Post you info 8 here any how, just incase it rings any bells.
Also, have you tried this? http://forum.xda-developers.com/showthread.php?t=371154
Ta
Dave
Hmm, just a hickup I think. I tried it again and now it will start!
I can't thank you enough Dave. And ofc pof
No probs, just searching an best guess work on my part
Dave
did you try to plug the usb before turning it on ?
it works on mine...

Categories

Resources