Related
Just want to say how to go to the official ROM from the UNOFFICIAL rom that has been out there. If you download the official, it will say that your phone is already updated. Well, to get around that (that's if you want the additives that AT&T has added like AT&T video/music, etc....) is to double click the .exe file, go to:C:\Documents and Settings\*YOUR PROFILE NAME RIGHT HERE*l\Local Settings\Temp\*SOME ODD MIXTURE OF NUMBERS AND LETTERS*\
once here, open payloads.xml. After you have that open, change the high and low to both: 2.23
If "2.23" doesn't work, that means that you have a different ROM number. to check on your specific ROM number, get on your treo and go to:
start>settings>system tab>about
phone tab> then look for the number near where it says "CNG" or "ATT". Mines showed "2.23" which is why I changed the high and low to "2.23". Go ahead and change it to what your treo reflects. SAVE the payloads.xml file then click Continue or Update on your updater screen.
Enjoy!
you're a lifesaver. I was perplexed by the very problem. I am loading up right now.
Also if you don't want to mess with all of that, download the SD flashing version and put the card in then reset the device while holding down the far bottom left button (under the volume buttons) and then follow the onscreen instructions to flash. This will ignore all version checks and force the install/upgrade.
I seem to be stuck at eth boot loader screen I havent used one of the palm updaters in a WHILE, is this the norm.
I did do the SD update but version remained at 2.23...hmmm.
Never mind Im good just having a bluetooth issue now.
I didn't realize my stupid laptop wasn't plugged in. I got to 19%, and the damn thing went to sleep.
Now, I can get a USB connection that the laptop detects, but activesync doesn't wake up.
Does this mean I'll have to a memory card update?
Crap. I don't have my miniSD adapter. It's at my girlfriend's house. Looks like the phone is hose until I can get ahold of it.
I'm on Fresh Toast 2.1 (official eclair w/ fresh customizations)
When I plug in a USB cable to my phone from any computer, from any OS (OS X 10.5, 10.6 and Win XP/7) I don't get offered the option to mount as a drive.
I looked in the 'Connect to PC' settings and tried it with 'Ask Me' both checked and unchecked. I also tried to make Disk Drive mode the default and that didn't help either. The only way I can mount it the SD as a drive is by rebooting to Recovery and toggling MS.
What a pain! Any ideas?
Are you using the app. Autostarts? I had that exact same problem until I realized that I disabled PC Synchronization (using Autostarts) from starting up when the phone boots. Once I re-enabled it again it worked just fine.
check on the top left of the status bar, if you can see a triangle with charge only, then slide down the status bar and press on charge only... let us know if this works. Also make sure that debug is off, menu> settings> applications> Development
Yeah, I'll bet what you did, dude, is set it to "Always use this option" when you plugged it in one time, maybe on purpose, maybe on accident, but who cares, that's probably what it is. Is that option even existing on certain roms? I just checked, mine doesnt say that. Worth a shot lol.
dametzg said:
Are you using the app. Autostarts? I had that exact same problem until I realized that I disabled PC Synchronization (using Autostarts) from starting up when the phone boots. Once I re-enabled it again it worked just fine.
Click to expand...
Click to collapse
Crap, I think you're right! Trying this now; i disabled everything. Will report back with results.
UPDATE: Nope, that wasn't it. PC Synchronization isn't even an option for me to enable/disable.
SAlpIche said:
check on the top left of the status bar, if you can see a triangle with charge only, then slide down the status bar and press on charge only... let us know if this works. Also make sure that debug is off, menu> settings> applications> Development
Click to expand...
Click to collapse
Not the issue here. I'm not a noob.
But why disable debugging? I've always been able to do both simultaneously without issue. Until Fresh Toast 2.1, that is.
jerry43812 said:
Yeah, I'll bet what you did, dude, is set it to "Always use this option" when you plugged it in one time, maybe on purpose, maybe on accident, but who cares, that's probably what it is. Is that option even existing on certain roms? I just checked, mine doesnt say that. Worth a shot lol.
Click to expand...
Click to collapse
Negative.
Is it possible that it is recognizing it as a charger instead of a computer? Have you tried other cables and/or computers?
scirio said:
Crap, I think you're right! Trying this now; i disabled everything. Will report back with results.
UPDATE: Nope, that wasn't it. PC Synchronization isn't even an option for me to enable/disable.
Click to expand...
Click to collapse
Oh weird. The PC Synchronization shows up in the section called After Startup for me. Hope you get it figured out.
dametzg said:
Oh weird. The PC Synchronization shows up in the section called After Startup for me. Hope you get it figured out.
Click to expand...
Click to collapse
Thanks worked great for me haha first time looking thru the startup programs I completely missed it
Hey guys,
For some reason, I can't mount USB unless I'm in debugging mode.
I plug the cable into my phone. The phone will bleep. I'll see the little USB logo and in the pulldown, under ONGOING, I can see it there, but usually there is two lines of text, but I only see one. When I click on it to be presented with the mount option, I hear the bleep when I click it, but nothing comes up.
Or maybe my PC isn't recognizing it unless in debugging mode? I have all the drivers installed. I'm positive I do, because it was the only way to get the super one click root. I've never had problems mounting.
On a side note, maybe it is relevant, my wifi connectivity has gotten really bad the last few days. My connection has stayed the same, and I've check all the usual PC settings, power cycle, etc. I can't check my Twitter, I can't send emails with attachments. Uninstalling and reinstalling the Samsung drivers didn't work. When in debugging mode, and I plug in, I did notice in the device manager, there would be something "ADB" popup. That's what's not showing itself in non debugging mode.
I'm not sure what I could have done. Any ideas? Thanks!
Go in to settings, usb settings and choose mass storage, if it's set to ask on connection it sometimes doesn't bring up the mount option in the notification bar, you'd think it would mount auto magically but it doesn't.
Edit; sorry didn't read the whole post, sounds like a driver issue..
Sent from my SAMSUNG-SGH-I897
Dani897 said:
sounds like a driver issue..
Click to expand...
Click to collapse
I figured that much. The combination of things I've attempted so far regarding the drivers has not been successful.
Mounting USB on Rogers
Hey there I've noticed the same problem until I actually pulled down the top menu bar at the top where the USB symbol is. You pull that down and look for the USB settings icon tap that and choose MOUNT and or UNMOUNT.
Hope this helps....I only noticed this on Eclair 2.1 and not on Froyo where it actually brings up a dialogue box.
Just a word of advise, when you unlcok it with the unlock software from here beware you might end up with a generic or false IMEI number as I did.
I get the drop down, and I see the USB option, but clicking on it does nothing. The PC won't recognize it.
For those who are having this issue, the only way I've manage to fix this is:
1. Uninstall Samsung drivers and delete extras manually.
2. Restart PC.
3. Reinstall driver.
4. Restart PC.
5. Plug in device and give it a few minutes.
I'm on Windows 7 64bit. I've had to do this twice so far, and it worked both times. Hope it helps.
I had this problem also and after looking around I found several people that suggest switching to a USB port right off the mobo. After doing this it connects every time.
I got my Gear Live off eBay last week. Didn't come with anything but the watch, and just got the cradle from China. And it's definitely Chinese.
It's a third-party cradle, and it lacks USB data. I know this because across three computers, it doesn't detect a device. All I can do is charge this thing, and use 4.4W. I can't force it to grab an update, and because the cradle can't do data, I can't ADB into the recovery when I can force it (I have to route commands through the phone's bridge).
I'm desperate here. Is there ANY WAY to work the Bluetooth ADB and force an update, or at least move an update and flash it manually? I'm seriously low on funds, and this is killing me to not have the software updates.
As a note, I purchased my cradle from this guy here on eBay. If I hadn't instantly given positive feedback, I'd yell about it not supporting data. This is real bull.
EDIT: Seeing as it's a cheap charger anyway, I figured I'd pry it apart to see what actually makes this thing tick, and the results are supremely underwhelming. I've attached photos, but I can't see them being anything more than voltage regulation, to ensure nothing bursts into flames.
Go to https://www.youtube.com/watch?v=x7oRjESQh_o
Follow the video fro unlocking the Gear Bootloader. Make sure to use v2 of his software. v3 is riddled with bugs. Once you unlock the software, use option 8, then reboot. Load back into the flashbooter/recovery menu, then use option 6. Update from there using OTAs.
Read my post. Actually read it.
I CAN'T GET A DATA CONNECTION VIA USB.
UltimaXtreme said:
Read my post. Actually read it.
I CAN'T GET A DATA CONNECTION VIA USB.
Click to expand...
Click to collapse
Have you tried debugging over Bluetooth?
BRANDENDEUCE said:
Have you tried debugging over Bluetooth?
Click to expand...
Click to collapse
It disconnects after rebooting into Recovery. Unless it's possible to throw a flash down while in the OS, I think I'm gonna concede and grab an OEM cradle.
delete
Hello guys!
I have a situation also with a device. I just received today, it has 5.0.1 on it, and i cannot use the tool that is specified in that video + after activating the dev. menu, i dont have the usb option ...
Any advice ?
R3d_Wolf said:
Hello guys!
I have a situation also with a device. I just received today, it has 5.0.1 on it, and i cannot use the tool that is specified in that video + after activating the dev. menu, i dont have the usb option ...
Any advice ?
Click to expand...
Click to collapse
You can force the watch to boot into bootloader mode. Turn off your watch. Press power button and at the same time start swiping from top left corner of the screen to bottom right. (Diagonally) Do it multiple times.
aligatro2010 said:
You can force the watch to boot into bootloader mode. Turn off your watch. Press power button and at the same time start swiping from top left corner of the screen to bottom right. (Diagonally) Do it multiple times.
Click to expand...
Click to collapse
Thanks for your reply aligatro2010, but i decided to return the device and got something else .
Hi guys, been a bit out of the loop (hospital) but bought an Alpha around sep last year...within 2 months i used a official Maze update (OTA) and it then no longer charges...got onto them via facebook (as there were no official threads for this phone back then) and they sent me this to reflash it...
http://www.mazemobile.com/download-center
The ROM used to be there, but they have the ****ing cheek to say "people tried to flash and blamed MAZE" now it was MAZE's update in the first place that buggered my phone.:silly:..i still have the original ROM...
https://drive.google.com/drive/folders/0B8XLZxEJR8albndMcXJhWGtlVDQ
^not sure if that works for you, but basically it was..
:A really crap tutorial
:Maze Alpha flash tool.zip
:Maze_Alpha_V05_20170816
I've followed everything by the letter to no avail???
Now MAZE are bloody useless, can i count on one of you clever chaps to help me out?
P.s it's the 4 gig model.
Many thanks lads...
Any joy?
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
seedaripper said:
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
Click to expand...
Click to collapse
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Cheers...someone lives!
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
lukesan said:
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Click to expand...
Click to collapse
seedaripper said:
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
Click to expand...
Click to collapse
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
Charger you can easily check if you just connect it to another charger or a pc usb port. A PC usb port will only deliver (mostly) max 400mA to 500mA .. meaning it will charge, if it still does, extremely slow. So I would keep it connected to a pc all day long or night before trying to switch it on. Trying to switch it on during charging and batt at low level will probably not work. You could try to power on after 2 or 3 hours or so and if it powers on then I would power it off again to get at least some juice in it to play around.
Cable, I would go fetch another one, they will come in handy in the future too. If it doesn't fit properly because the port is to deep in the Alpha then just take a knife and carefully cut a very small piece of the plastic, just 1mm is enough. I've done this on the 2 extra cables I have here and it works perfectly and I don't even see it aesthetically so no harm done on mine.
Now if that still doesn't work we can try the next step. But be very careful to know that that will delete all data, pictures, etc off of the phone. Because of all my toying with this phone I stuck an sd-card in it and doing a backup before I play with it again.
The manual states that you have to press the volume up button.. Well you can already test that without hurting anything as long you don't press anything on the flashtool. So only volume up and then insert the usb cable to a pc. Now the mistake I made in the beginning was to also push the power button.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
Btw I know about their attitude. Well, as a Chinese company they must understand that by this attitude they will not going to sell any products anymore. I only bought mine because it was a special deal and I wanted to test an MTK chipset. They never replied to me why there is no real fast charge on it etc.
I also very very highly recommend you to invest, well for the price of a sandwich, to buy a usb charging doctor which will allow you to see the voltage and current. You don't need to be a doctor to us it and at least you see something instead of having to guess. Also while you are at it buy good quality chargers and a couple of cables. They will always come in handy and take some of the guesswork away if needed.
Top lad.
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
lukesan said:
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
.
Click to expand...
Click to collapse
seedaripper said:
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
Click to expand...
Click to collapse
Well don't flash it twice. You have to put it in that mode twice to start it to complete the procedure. I do not believe in the wipe it 3 times to be sure, turn around and jump to make it better or faster. Loads of voodoo that is not scientifically proven around. It's all about a 0 and a 1, there is nothing in between that.
But .£60 to send that charger, LOL.
A month ago I bought an Aukey charger that included a USB-C cable for like .£12 including shipping to Belgium. (well just followed the rain and snow and landed here)
Let us know what happens next.
Any update on what you did?
GAH!
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
seedaripper said:
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
Click to expand...
Click to collapse
But what about the drivers etc.... What shows up?
ROM?
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
lukesan said:
But what about the drivers etc.... What shows up?
Click to expand...
Click to collapse
seedaripper said:
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
Click to expand...
Click to collapse
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
seedaripper said:
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Click to expand...
Click to collapse
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
er?
lukesan said:
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
Click to expand...
Click to collapse
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
lukesan said:
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
Can't get my head round multi quote?
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
seedaripper said:
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
Click to expand...
Click to collapse
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
lukesan said:
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
Click to expand...
Click to collapse
Pics ...hopefully...