Related
Stuck at "Samsung Galaxy" boot screen, cant get into bootloader, computer wont detect
Hey everyone this has been a huge hassle for me for the last few days and was hoping someone could help me. I have had to resort to using my HTC Legend...which I love but it doesnt have what I need.
I was in recovery the other day trying to load a custom rom through the CWM and I went through and accidentally hit "format system". I couldn't cancel the process so I knew something bad was going to happen....I reboot the phone and for the last 3 days I have had it plugged into the Usb charger with no luck of booting, it has been stuck at the "Samsung Galaxy S 19000M" boot screen and no further. I took the battery out and tried rebooting it after a few minutes. No luck with this either, still stuck at the Samsung screen. I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button).
I have put it into download mode and and plugged it into the computer (I am running Windows 7 64-bit) and it will not detect it. I have all of the correct drivers, I know this as I have a friend who owns the exact same phone and my computer detects it just fine. Odin nor ADB will detect that there is anything AT ALL plugged into the computer. It does not even come up as, "android device", or "storage", there is nothing, nota, it is as if the phone isn't even plugged in. It will not detect in "download mode" nor while its stuck at the "Samsung Galaxy S" screen, and yes I have tried a different USB cable, and still nothing..
I am quite capable with electronics but I cannot find anything on the internet as of what to do. Is there anything that I could load on an external SD card that would force the phone to flash a ROM with new kernal and modem? I think the phone is empty that is why it is not booting, as if there is nothing to load on the phone. Is there anything at all that anyone can think of??? I am completely stuck. I wanted this phone to last until the Samsung Galaxy S 2 was released here lol.
I'm with Virgin Mobile Canada. Thanks!
Cant you get it into Recovery mode?
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Herman76 said:
Cant you get it into Recovery mode?
Click to expand...
Click to collapse
Hey herman, "I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button)."
profalbert said:
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Click to expand...
Click to collapse
Hey, I will search for that right away and let you know how it turns out. Thank you!!
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
azzledazzle said:
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
Click to expand...
Click to collapse
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Galaxy19000M said:
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Click to expand...
Click to collapse
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
azzledazzle said:
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
Click to expand...
Click to collapse
I have tried, uninstall-re install of kies, run odin as admin, alternate usb port, anddd I tried plugging it into my laptop...no luck...this absolutely driving me nuts because I know the phone cant be bricked, if I can get into download mode I SHOULD be fine but for some strange reason the phone seems to be undetectable...ahhhhhhhhhhhh if only there was just some way to access the internal storage or a program that would force a flash through an external SD....
I am going to try loading Ubuntu on my computer on one of my HDD and see if it will detect the phone. I am assuming this is my last option and I have high hopes as Ubuntu detects almost anything...I will update...if it doesnt work I might be looking into taking apart the phone its self and intalling a new USB plug in on the phone motherboard...
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
Click to expand...
Click to collapse
yeah lol like I said in the first post I tried a different USB cable all together.
I have two HTC Legends, tried both cables from them, plus the OEM cable that came with the SGS
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
Click to expand...
Click to collapse
I dont know if it has been opened already by someone else. I bought the phone for $180 CAD from a sort of "2nd turn" site. As in it was being sold as is. The phone problem reported by them was that the USB connectivity was not working. When I originally got the phone from them everything was working correctly, except the USB connectivity like it stated. It came ROOTED and loaded with the leaked version of Froyo before it was out so I automatically assumed that was causing the USB problems. I got around to changing the ROM with a reported working USB using CWM. But, still no luck with USB connectivity. I just dealt with the problem and flashed everything through CWM. Which led me to this...ugh
Is there supposed to be a warranty seal behind the battery cover? Over the screws like there usually is? Cause I see nothing..
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
azzledazzle said:
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
Click to expand...
Click to collapse
Well thank you for all the help. I am going to try installing Ubuntu first and see what happens, I have never had any driver issues with that OS EVER so if its detectable, Ubuntu will be the one to detect it. If that doesn't work I might take my chances and send it in. And if like you said that one person decides to screw me over, they at least have to send it back to me, in which case I will just open it myself and change the USB plug in like I said. (which might not even be the problem...)
Is there anyway to tell on the out side without opening it if it has indeed been opened before???
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
azzledazzle said:
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
Click to expand...
Click to collapse
Well I sent my phone in to Samsung last week and I just got it back today! I opened it up and I guess the problem with the phone was pretty bad lol they just gave me a new phone, I was thinking it was refurbed but it said right on the repair receipt "condition=NEW" I am extremely happy.
That aside, do you know if you can use the SGS II if it is unlocked in Canada?
I'm so aggravated right now. Been trying a ton of methods, I have a jig that only puts me back at the Phone ! PC screen, can't get into download mode, the PC doesn't recognize my friggin device, I have Odin 3 (which I can't use because I can't get the PC or my Laptop to recognize the phone, and I've tried the button combos a bunch of times. I'm a pretty pc literate/tech savvy guy and I'm trying to help my friend fix his phone.
This all happened because he was doing the 2.3.5 update and it got stuck at 84%. He said it sat there for about 2 hours without progressing, so he pulled either pulled the battery, or USB or something out (I wasn't there, and I forget his explanation) and not I'm at this Phone ! PC Screen, and I'm ready to throw the phone lol. Please help me if you can, I'm really getting frustrated...
Thank you so much.
Breathe.
Go read this post and try some of the tricks in there. Technically you're in download mode. I have flashed from that screen many times. I would guess that you might want to try reinstalling the drivers. If that doesn't work, go grab one of the Heimdall one-clicks. Heimdall uses different drivers that may help get you back to stock.
Here is the post that contains the one clicks.
Good luck and remember to breathe.
First thing: Thank you for responding, and trying to help.
Secondly: I can confirm that I did reinstall the Samsung Drivers twice, but still no recognition of the USB Device... I have a stock cable, and the cable for my HTC, so I've tried both. No luck... Heimdall gives me an error basically saying that it doesn't see the device. I'll check that thread out though, and see if there is something new that maybe I haven't done/seen... (Breathing...)
I know this will sound strange, but have you tried gently wiggling the plug? It may be that the USB port on the phone is starting to go bad. That would explain the sudden loss of connectivity.
Sent from my SAMSUNG-SGH-I897 using XDA App
Have you tried using a different USB port?
Another thing that has worked for me is uninstalling the USB drivers then running kies and allowing it to reinstall them for you. Not sure why it worked for me but it did once.
Sent from my SGH-I897 using xda premium
Hey, appreciate the suggestion.
I have tried diff ports, but I'll attempt to let Kies to do it again in a few mins. Thanks
Haven't tried that, currently fixing my laptop that some stupid walk through had me do, which screwed up my laptops drivers... ugh. So at the moment, I'm performing a restore. 6 hours and counting of working on this thing... good thing he's my best friend, or I'd tell him to burn it.
(this is in response to "have you tried wiggling the plug)
I was in a similar position so out of frustration I held power, volume +/- buttons until it booted a couple times. For some reason my laptop recognized the phone after that. It may not do anything for you but it can't hurt at this point.
Sent from my SGH-I897 using xda premium
1 click unbrick. if I was not on my phone, I would have linked you.
[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 ladies and gents,
I've been on a mission to root my Note 5 N920I for months now.
My problem is no computer will read/recognise the device. The Mac's seem to not even recognise it's plugged in, with Windows, no matter which driver I install it keeps telling me the "device descriptor failed blah blah blah". I managed to root my S4 very easily on Mac with Jodin3 so I know that it ain't no user error.
I've Googled and Googled ways to root without a computer or installing a custom recovery without root, but from what I understand I can't flash TWRP as recovery without a computer and therefore cannot root without a custom recovery.
I've Googled ways to fix the USB issue by making the xml file and putting it into the correct folder, but for that I need to be rooted. Right?
When she's plugged into a computer with USB debugging on or off nothing comes up in my notifications except for charging. I tried using the toolbox which I found on here (sorry can't remember the name) though it seemed like I was getting close, I couldn't get close enough before my temper got the better off me.
If my memory serves me correctly the OTG function worked when i first got the phone but didn't after the first update. My mate's Note 5 also has the same issue. I Googled it and seemed it was common issue on these phones.
I've tried to learn some Terminal/Command Prompt to see if I can fix it that way through Debian or whatever, only got as far as understanding it, kind of. Big ups to all you coders/programmers out there it really is an artform.
So PLZ PLZ can y'all help me, there has to be a way aside from setting this thing alight and getting a new phone.
My next mission, which I only embarked on a couple nights ago is unbricking my dad's Note 4 (N910G) that just hit the **** one day after spazzing out for a few days then would not turn on. I'm getting close though I haven't put much effort into that yet.
Any advice will be greatly appreciated, thanks in advance. ?
Forgive me if I've posted this thread in the wrong area
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...