ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
matthewjulian said:
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
Click to expand...
Click to collapse
I haven't had this problem, but is the driver installed for when it is in the bootloader screen?
Another way you could try is flashing it from bootloader mode. Just go into bootloader mode then plug it into your comp and run the romupdate utility.
Odd
Never personally ran into it but check your USB cable. Try a different cable. Try a different USB port. I had some issues with them being a little touchy.
I dont know if anyone cares, but I figured it out. I am using a Early 2010 Model MacBook Dual Core running Parallels instead of dual-booting Win XP.
When I am in Windows XP, OSX is running in the background, when the rom update utility turns the phone off then on into the bootloader, the phone is off for that split second and parallels cant keep up with it, and the Mac trys to grab the USB connection in that split second before Win XP says "No, thats my connection", so in that split second exchange the connection with Windows and the RUU gets droped! Kind of simple once you know whats happening. No matter, I used my brother in-laws Vista Toshiba( infected with viruses to the max), it worked fine and I am now running Moonscapes 1.6 with android as well! Thank You to the people who took the time to help!! Remember guys this is a community, it doesnt work unless people respond, without participation we may as well be talking to our dogs!
You never mentioned you were doing something crazy like trying to flash your phone from a virtual machine. That never works, because the usb passthrough driver doesn't detect the windows low-level bootloader mode. How are we supposed to help you when you don't provide details?
Lol, my bad, I got sloppy!! My son dumped a Sonic drink on my dell so all I could work with was my trusty Mac, I am going to dual boot it later today. I have to say after a day with Moonscapezx's 1.6, I like WM, dont know if I like it enough to swap it out for good, I still love my Hero(at least for another 3 months when I get an upgrade, EVO!!!). Ok, well Thank You again guys, I love XDA, you guys are great
Related
Earlier today i was on the samsung website to download some drivers which i think was needed to speed up the boot on of my samsung nc10 netbook. This was mainly because after downloading windows 7 yesterdayi i had a lot of drivers to re-install from the samsung download centre. I noticed during the booting up my laptop that it delayed pn a black screen for a VERY long time before entering into the desktop. I spent hours trying to fix this in device manager, command prompt etc. Nothing worked. When i read on a forum that bios updates might be needed to help windows 7 run better i chose to download one. As the bios update was downloading from the samsung website, after about five mins i noticed the computer had frozen. tried moving the mouse, ctrl alt etc. but nuthing worked. I was very worried when i pressed the power button and the computer did not go off. As i proceeded to take out the battery from the bank i muttered 'nice knowing you laptop' cos i kinda sensed it was a very bad thing about to happen. Took out the battery for a few mins and put the computer back on but it would not switch on. It just showed a blue indicator light and it hasn't come on since then. I can't help but wonder if those 20 delayed seconds during boot was really that intolerable, i should have just left well alone. The poor baby is only a few weeks old and already its met the end. Does anyone know if a laptop can be recovered from an error during bios update? thanks for ur help
I have never seen a laptop that has been able to recover from a Bad BIOS flash, and unlike a Desktop PC it is a bit harder to open it up and change the BIOS ROM chip (containing the EEPROM). Some laptops and computers have the BIOS chip soldered onto the motherboard so you can't just change it (grr).
I would advise you take it back to where you bought it, but be careful with what you tell them happened. Sometimes businesses like to charge you if you were the one that played about with the BIOS, which is kind of annoying since its not exactly you that wrote the BIOS flashing software..
U're very right about not being to quick to state i'd be downloading software. I noticed there is a disclaimer on their website stating they are not liable for any issues caused by changing software. Nice to have seen that cos when i rang them up i just said the laptop won't turn on for some strange reason They agreed to book it in to their service center
you are correct!
if you search in the web of american megatrends maybe you can found a DOS app called something like low application that can helps you to restore a corrupted bios.
My jobs pc has the bios corrupted because of a worm its a vaio so... al the drivers needs to read the model ID and... the model has beendeleted! unbelievable but true the IT technician tells me that he needs time to try that app cause he never do it but he say it will makes the trick.
Try it you cant loose anything more... or take it to the seller and ask him for the service center.
If it uses Phoenix BIOs then you can use an emergency flash disk. I've successfully used it to recover my HP DX6000 after I borked a bios hack to remove a WiFi whitelist.
Long story short, I've been about to flash a couple custom ROMs, but I understand that the safest way to do so is to first flash back to the stock ROM using Odin. That's where I hit a dead end.
Now, I've rooted my Captivate, but done practically nothing else.
When I plug my phone into my computer (both my desktop and my laptop- W7 Ultimate x64 and Professional x86 respectively), I get a rather long message about how the device has malfunctioned and basically cannot be worked with (poor wording, apologies).
I have installed the proper (x64/x86 on their respective OS's) samsung drivers, and I have tried connecting my phone from within the booted Android interface, as well as download mode (which I have little to no problem getting into).
I have also tried checking the 'debug mode' box within the phone's settings.
I'll concede that I'm no pro when it comes to this level of phone-play. I've built many a computer, and solved many a software problem, but this has me stumped.
I've thought about doing a master reset of some sort, but don't know if that would solve it.
I'd appreciate any and all advice, so thank you in advance.
[Oh, and I sincerely apologize if this was posted in the wrong section. It is, quite honestly, the first thread I've started.]
Try plugging it into another usb port. I have seen windows continue to say a device is not working even after installing the drivers if you had already plugged it in.
I am at a complete loss for words.
I'll at least make it clear right now that I think my problem is solved.
I had been plugging the phone into one of the usb ports located on the actual chassis, and took your advice and instead plugged it straight into my mother board (the back).
B
I
N
G
O
Windows auto-detected it and installed two sets of packages (drivers, I assume).
I feel like a fool, but in an odd, good sort of way.
Thank you, brother.
Not a problem glad I could help.
Absolutely! Me too, bro!
Thanks again.
[Q] Yet another "I'm stuck at the AT&T screen and I it's not recognized" thread
Greetings, all
I've been trying to figure this out, off and on, for 2-3 weeks. I could use some help.
Originally, I was running Cognition, but I can't even remember what I was trying to flash because I've tried so many things... The bottom line is that I'm at the download screen, but all the PC's I have (win 7) don't recognize it. I'm convinced that if I can get the PC to recognize it, then I could reload i897uckk4. But...
Things I have done:
- Rebooted, switched cables, turned everything off and on, tried on different machines, all the hardware easy stuff.
- Uninstalled drivers, tried other drivers, uninstalled Odin, Heimdall, Kies, rebooted and tried only one at a time.
- Tried all the USB ports on all the PCs
- Different phones are seen from the 2 cables I've been using.
This phone worked and was recognized on this machine before I screwed it up. I don't see how it's a phone hardware issue. Sure, it could be, but I really don't think so. That leaves drivers for Win 7, 64-bit. I've tried these files as Administrator:
- usb_drivers_GalaxyS_x64
- Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
I've even tried these for kicks:
-SAMSUNG_USB_Driver_for_Mobile_Phones_x86
- SGH-i897_Captivate_USB_Drivers_5_02_0_2
Now that I've tried all I can find, I think the ones I want to keep are the "usb_drivers_GalaxyS_x64"
Thing is, it worked before "The Big Hose of 2014". It should have been recognized, but it stopped being recognized after an unsuccessful attempt at flashing back to stock, after an unsuccessful attempt at Cyanogen. The only thing I can think of is that I tried to flash the wrong ROM version, or something like that, and the phone is in a state where it's not sending the proper handshake.
The error I'm getting is classic, and all over these forums:
- I've tried to manually load "Samsung Android USB Composite Device" driver - Device can not start. Code 10
- All devices like WMC, Mobile Modem, ect - Code 10
- A few others result in the Code 10, too.
I've tried to find the GUID for it in the Registry to delete the Upper and Lower Filters.
What's left? I'm sure it's a small thing. I could use a few more hints.
Two last questions:
Will doing the unbrickable mod help, or is it too late?
Does it charge while in download mode, or if the star like circle is not spinning?
FEF said:
Greetings, all
I've been trying to figure this out, off and on, for 2-3 weeks. I could use some help.
Originally, I was running Cognition, but I can't even remember what I was trying to flash because I've tried so many things... The bottom line is that I'm at the download screen, but all the PC's I have (win 7) don't recognize it. I'm convinced that if I can get the PC to recognize it, then I could reload i897uckk4. But...
Things I have done:
- Rebooted, switched cables, turned everything off and on, tried on different machines, all the hardware easy stuff.
- Uninstalled drivers, tried other drivers, uninstalled Odin, Heimdall, Kies, rebooted and tried only one at a time.
- Tried all the USB ports on all the PCs
- Different phones are seen from the 2 cables I've been using.
This phone worked and was recognized on this machine before I screwed it up. I don't see how it's a phone hardware issue. Sure, it could be, but I really don't think so. That leaves drivers for Win 7, 64-bit. I've tried these files as Administrator:
- usb_drivers_GalaxyS_x64
- Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
I've even tried these for kicks:
-SAMSUNG_USB_Driver_for_Mobile_Phones_x86
- SGH-i897_Captivate_USB_Drivers_5_02_0_2
Now that I've tried all I can find, I think the ones I want to keep are the "usb_drivers_GalaxyS_x64"
Thing is, it worked before "The Big Hose of 2014". It should have been recognized, but it stopped being recognized after an unsuccessful attempt at flashing back to stock, after an unsuccessful attempt at Cyanogen. The only thing I can think of is that I tried to flash the wrong ROM version, or something like that, and the phone is in a state where it's not sending the proper handshake.
The error I'm getting is classic, and all over these forums:
- I've tried to manually load "Samsung Android USB Composite Device" driver - Device can not start. Code 10
- All devices like WMC, Mobile Modem, ect - Code 10
- A few others result in the Code 10, too.
I've tried to find the GUID for it in the Registry to delete the Upper and Lower Filters.
What's left? I'm sure it's a small thing. I could use a few more hints.
Two last questions:
Will doing the unbrickable mod help, or is it too late?
Does it charge while in download mode, or if the star like circle is not spinning?
Click to expand...
Click to collapse
You probably already saw this thread, but in case: Captivate - PC Connection Issues, Download Mode and Recovery Mode Help
As for what is left, trying on another pc could be a good idea. If the drivers aren't already installed on it, even plugged in download mode, it should install drivers.
BWolf56 said:
You probably already saw this thread, but in case: Captivate - PC Connection Issues, Download Mode and Recovery Mode Help
As for what is left, trying on another pc could be a good idea. If the drivers aren't already installed on it, even plugged in download mode, it should install drivers.
Click to expand...
Click to collapse
I've already tried the stuff in the link. I did that first.
I have 7 computers, all running Win 7. This Captivate is not recognized my any of them.
Looks like I'm headed to the unbrickable mod. I'll have to dual boot to Linux for these fixes.
http://forum.xda-developers.com/showthread.php?t=1242466
If worse comes to worse, looks like I have a soldering iron and guitar pick in my future.
https://www.youtube.com/watch?v=frn9o03DHsE
http://www.xda-developers.com/android/the-unbrickable-mod-and-beyond/
Looks like I bricked it good. It's time to work on the hardware, I guess. It would be fun, if I hadn't already screwed up my phone. I bought another Captivate off eBay for $50, so at least I'll have a phone.
This story has a twist for an ending. I thought I'd post just in case someone else is thinking about getting out the soldering iron.
The funny thing is that after my new (old) phone (a nice one too) I bought from eBay showed up, I started flashing and generally screwing around. Both phones look the same so I couldn't tell exactly which one was which, so I plugged them both in, thinking that I'd fine the one that was responsive. They both went into the Ginger Bread funky "Firmware Upgrade Failed" screen. This was a head scratcher, indeed. I read a while back about how build dates are important when flashing soft bricked Captivates.
One of the phones has a build date of 1007. Since is well before 1010, I looked around for the Eclair Stock ROM and found it here.
http://forum.xda-developers.com/showthread.php?t=731989
It appears that the early Captivates are very particular about what you flash when going back to stock. I couldn't tell you why the old phone started working. Maybe because I used a JIG then pulled the battery out for a few days? It's possible. All I know is that "I897UCJF6-final-OCD-REV0" one-click has them both up and running.
At least now I know what I can call my "reset". I'm going to flash GB, then see if I can get to Cognition again, and try "cm-10.2.1-captivatemtd". If they bomb out, I feel real good that I have a way to bring them back.
I hope this can help someone along the way. With the Captivate selling for about $50, albeit 3G, it's not a bad phone at all.
Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...
Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.
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...