Database Develop

[Q] Stuck booting into Download mode

Okay, so as far as I am able to find... This problem is pretty unique...
I'm running Cognition 4.5.3 with no software issues. I have had this problem since Cog 3...
Most people have trouble getting their phone to boot into download mode, but NOT ME!
My phone randomly (I can find absolutely no cause or trigger and I'm not really a novice at Android) will shut itself off. Now normally I would not have an issue with this, but when I go to turn the phone on... it boots straight to download mode, and no key combo or anything will avoid it. So I have been testing this out and I can reboot the phone from the enhanced power menu, I can boot into Recovery from enhanced power menu... But when the phone shuts off or when I shut it down, the ONLY way that I can get it to power on correctly, is to plug the phone in and wait for it to show that the phone is charging. Then I can power it on normally...
Now, this issue arose the same time that my phone began to refuse to be recognised when plugged into a computer via USB... and at times the USB debugging and USB connected notifications will remain in the notification bar until I reboot the phone...
Naturally, my first instinct was to try and restore to stock... But since no computer will recognize my phone (even with fresh drivers installed) I cannot use odin to flash to stock.
So to summarize my problems:
1. My phone will not be recognized by a computer. (USB device not recognized)
2. My phone randomly shuts itself off. (Not a big deal, I can live with that)
3. My phone ONLY boots into download mode unless plugged into the charger (Incredibly frustrating when I am not at home or I don't have my car charger)
4. USB debugging and USB connected notifications stick around until phone is rebooted. (Using enhanced power menu. Again, I can live with this minor annoyance)

have you tried reflashing that rom...or trying another?
it could be the random shutdown issue that some cappys have paired with a failing usb port.
try changing roms.

studacris said:
have you tried reflashing that rom...or trying another?
it could be the random shutdown issue that some cappys have paired with a failing usb port.
try changing roms.
Click to expand...
Click to collapse
Hehe... I tried a different rom for two weeks and had similar and/or more problems...
Reflashing doesn't help either.
I've tried my best to troubleshoot this on my own, so I'm not shutting down your attempt to help. Just letting you know I have tried it.
I hadn't heard about a failing USB port problem... I'll read up on it.
Thanks for your help!

Atleast you dont have to worry about soft bricks if it auto boots into download mode

d34thp1ng said:
Atleast you dont have to worry about soft bricks if it auto boots into download mode
Click to expand...
Click to collapse
Actually I do...because USB still won't interface...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

like i said could be a short or something in the usb port...or somewhere in the hardware. if you experience this problem across different software then it has to be a physical defect someplace. cause if it were software related it would fix once you flashed something different...
you can try for a warranty replacement, that requires a little loose morals. you will have to do something to cause it not to boot, or only boot to the at&t screen otherwise they will have proof of root and/or custom rom and void your warranty. once thats accomplished mention some crap about kies failing and they should replace it.

studacris said:
like i said could be a short or something in the usb port...or somewhere in the hardware. if you experience this problem across different software then it has to be a physical defect someplace. cause if it were software related it would fix once you flashed something different...
you can try for a warranty replacement, that requires a little loose morals. you will have to do something to cause it not to boot, or only boot to the at&t screen otherwise they will have proof of root and/or custom rom and void your warranty. once thats accomplished mention some crap about kies failing and they should replace it.
Click to expand...
Click to collapse
Hmmm... a few months back my original USB/Charging cable broke and for a couple of days I was forced to use a generic MicroUSB cable to charge my phone... Could that have cause a short/damage to the port?
My phone does not have warranty as I bought it refurbished. :'(
(Plus my morals aren't that loose.)

Had a similar issue, eventually determined that it was a short in this usb port and did a warranty return. (Only when plugged in could I turn on, etc.)
If that isn't an option for you, you could try flashing CM. For some reason, the cyanogenmod build won't let the phone charge when off. ( Automatically powers back up once the juice flows.)
I flashed a nightly and somehow, magically, my phone would power back up normally ( but wouldn't turn off, unless plugged in without power. So strange!)
Even more weird? I flashed back to stock and the new powering and rebooting stuck. The short wasn't fixed, my phone simply seemed to reverse the problem.
Plus, you would be using cm.
Sent from my SGH-I897 using XDA App

tbrass said:
Had a similar issue, eventually determined that it was a short in this usb port and did a warranty return. (Only when plugged in could I turn on, etc.)
If that isn't an option for you, you could try flashing CM. For some reason, the cyanogenmod build won't let the phone charge when off. ( Automatically powers back up once the juice flows.)
I flashed a nightly and somehow, magically, my phone would power back up normally ( but wouldn't turn off, unless plugged in without power. So strange!)
Even more weird? I flashed back to stock and the new powering and rebooting stuck. The short wasn't fixed, my phone simply seemed to reverse the problem.
Plus, you would be using cm.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks! You guys have pretty much answered my questions...
I don't want to leave my nice DG Rom though.
Since I have determined that it is a hardware problem... I think I'm just going to live with it for a few more weeks until I can afford to go ahead and buy the newer build of the Cappy... (Might even wait until the SGSII comes out.)

You should be able to get warranty replacement, just make sure the device is in a stock condition when you take it in!

tbrass said:
You should be able to get warranty replacement, just make sure the device is in a stock condition when you take it in!
Click to expand...
Click to collapse
Even though I purchased the device as a refurbished device?
The only problem is that I can't Odin back to stock...

Cease1 said:
Even though I purchased the device as a refurbished device?
The only problem is that I can't Odin back to stock...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=995143&highlight=safely+to+stock
this will get you to stock then look in forums for how to change boot animation change that to stock boot logo and your good to go i did read some were you could do boot img all on phone i belive. i cant find thats up to u

Okay so I called them and let them know what the phone was doing and they tried to send me to samsung to have them repair the phone...

I now hold in my hands a shiny new 1102 build Cappy... Took it to my local device service center and explained the random shutdowns and the booting into download mode and they replaced it no questions asked!
Now to get Cog 5b2 on here.

[Q] No USB after TWRP install

My phone isn't seen by any computer (drivers installed and up to date, it worked right before I installed) after installing TWRP. I used the app from the Play store and said yeah to the memory patch thing, then updated TWRP to 2.8.4. I plugged it into the computer, nothing. Other computers, other drivers, other cables, nothing. I undid the patch from the app. Nothing. I tried mounting storage in TWRP. Nothing. Any ideas? Thank you in advance.

Jonathan_A said:
My phone isn't seen by any computer (drivers installed and up to date, it worked right before I installed) after installing TWRP. I used the app from the Play store and said yeah to the memory patch thing, then updated TWRP to 2.8.4. I plugged it into the computer, nothing. Other computers, other drivers, other cables, nothing. I undid the patch from the app. Nothing. I tried mounting storage in TWRP. Nothing. Any ideas? Thank you in advance.
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showpost.php?p=58297902&postcount=2

Hey, thanks, I forgot to mention it's not showing up in device manager either. Nothing showing here, no sound that it's connected, no indication I've plugged it in at all.

Jonathan_A said:
Hey, thanks, I forgot to mention it's not showing up in device manager either. Nothing showing here, no sound that it's connected, no indication I've plugged it in at all.
Click to expand...
Click to collapse
is this happening when the phone is booted up, or in the bootloader, or in recovery ?

All of the above. Charges fine, but is not seen through USB at any point.

Jonathan_A said:
All of the above. Charges fine, but is not seen through USB at any point.
Click to expand...
Click to collapse
first of all make sure your using the original HTC cable as all cable don't come with the 2 required Data+ or Data- wires inside.
Boot your phone up, plug it into your computer, then check the USB settings on the phone itself by pulling down the notification bar.
These are things I would just try myself, never experienced this issue before, but really the first thing I would do is uninstall anything I installed after it went wrong, I was going to say manually flash a recovery, but that's not much help if your phone isn't being seen in the bootloader either, in all honesty, it sounds more like a hardware problem to me than software.

Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.

Jonathan_A said:
Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.
Click to expand...
Click to collapse
im sorry but ive tried to replicate this problem but messing with settings in recovery and the bootloader and cant, its sounding more like a hardware problem to me, im at a loss, hopefully someone else can shed some light on the situation.

Jonathan_A said:
Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.
Click to expand...
Click to collapse
Have you tried connecting it to a different usb port on your pc? You could also try booting your pc to safe mode and uninstalling "USB Host controller" then reboot and reconnect. I had a similar issue the other day after switching from twrp to cwm to use a cwm nandroid.
After flashing recovery my computer would not detect my phone at all. Simply moveing to a different port fixed it for me. Although when I connected to the original port, that port still would not detect my phone. Reinstalling the USB Host controllers fixed that though.

Well, I plugged it into the charging port on my laptop with a random cable the other day, and it just worked. I have no idea how or why, but it seems to work no matter what now, on all the ports and cables I thought I was having problems with. I guess I'll file this under "user error - anomaly." Thank you guys for your time.

Jonathan_A said:
Well, I plugged it into the charging port on my laptop with a random cable the other day, and it just worked. I have no idea how or why, but it seems to work no matter what now, on all the ports and cables I thought I was having problems with. I guess I'll file this under "user error - anomaly." Thank you guys for your time.
Click to expand...
Click to collapse
Happy Days

Connect TF701 to PC

Hello,
I unlocked my device by using ASUS unlock tool. Everything went well. I also can see the message "Device is unlocked".
Then I tried to connect my tablet with my computer to install TWRP and further a cutom rom, but this is not possible. If I connect my tablet with my PC nothing is happening at all, means tablet is not recognized at all. I'm using Windows 10. Anyway, my mobile phone is recognized. I already tried to set it back to factory settings, flashed the latest Asus ROM, but nothing helped.
The other curios issue is that the tablet is not able to recognize that the battery is charged. LED is lightning and battery is charged, but tablet says power adapter is not connected.
Any idea? Could it be the cable? I already tried to connect the table over the dock, but same behavior. Dock LED is lightning as well.
I'm really frustrated. Hope anybody can help. I really need to establish the connection to my PC to go ahead.
5.11.15 - Update:
I realized that it seems to be an issue with USB. As mentioned above USB to tablet is not working (no PC can recognize it). If I connect the keyboard no USB device will be found. Charging the tablet is also not working, except I connect the power adapter and cable directly. Any idea?
Thank you.

Hi, I am having the exact same issue with my TF701. Were you able to resolve yours?

Duchman said:
Hi, I am having the exact same issue with my TF701. Were you able to resolve yours?
Click to expand...
Click to collapse
Duchman or Dutchman? I'm having again exactly the same symptoms. Tried 3 different USB cables too. Dit yóú manage to get this sorted? I know it was 4 years ago but my TF701T is still working properly, for the most part.
FireStorm75 said:
The other curios issue is that the tablet is not able to recognize that the battery is charged. LED is lightning and battery is charged, but tablet says power adapter is not connected.
Click to expand...
Click to collapse
That is exactly the same behavior. Best for now is to charge with the device powered down. I'm about to open up mine to doublecheck if the USB connector is seated properly.
Weird thing is that the keyboard also fully works which should not be possible if the USB port on the tablet was malfunctioning right?
I'm having a lot of apps not displaying anything anymore so was going for the KisKatt rom to see if that fixes the lot. Also I see after some time some apps keeping the device awake all the time so battery is always drained when tablet is closed.

sebastiaanmeloen said:
Duchman or Dutchman? I'm having again exactly the same symptoms. Tried 3 different USB cables too. Dit yóú manage to get this sorted? I know it was 4 years ago but my TF701T is still working properly, for the most part.
Click to expand...
Click to collapse
My TF701T is sitting disassembled in one of my drawers after an unfinished screen replacement attempt. I did manage to install TWRP on it, however, I don't remember what I did exactly to accomplish that.
I might have used one of those shady rooting apps that I'm not sure if I'm allowed to mention here. Then I probably flashed the TWRP with Flashify. Basically, circumvented having to connect the device to a computer up to the point where I had a working recovery on it.
Don't ask me for the exact steps because I wouldn't be able to remember anyway. I'll lay out a basic plan of action:
1) Find an app that lets you root your device without connecting it to a computer. Be warned, those more often than not come bundled with malware, so exercise caution. I'd back up all the important files and information and do a factory reset before attempting this if I were you.
2) Install Flashify, grant root access, download TWRP zip on your tablet, flash. Do some research on how Flashify works and how to use it before you attempt this.
Good luck, and if anything comes out of this, be sure to come back here and report on what you did in case some other poor soul wants to install a custom recovery on their 7 year old tablet without using a USB cable.

I just had mine crap out for some reason and needed to reformat everything and re-install. Connecting the USB to my PC, the PC makes the connected sound but no drive or anything showed up. I couldn't be bothered to figure out why so I just used adb to put the files on the tablet.
adb push yourfile /sdcard

USB port problem?

My T810 has stopped fast charging and is no longer connecting when plugged into a computer. But is does charge. Have tried several USB cables and chargers that work with other Samsung tablets.

Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Because the device is not rooted, I can't use WakeLockDetector to find the specific reason. The ADB workaround also does not work, because USB connection fails.

Have you tried to hard reset?

meawww said:
Have you tried to hard reset?
Click to expand...
Click to collapse
Not yet. I first try to find a solution without setting up everything again. Without root unfortunately I can't use TitaniumBackup. Without USB I unfortunately can't root.

android.outliner said:
Not yet. I first try to find a solution without setting up everything again. Without root unfortunately I can't use TitaniumBackup. Without USB I unfortunately can't root.
Click to expand...
Click to collapse
If you have twrp i think you can root your device with chainfire su

meawww said:
If you have twrp i think you can root your device with chainfire su
Click to expand...
Click to collapse
I wanted to wait until end of warranty. So no TWRP as well.
There is an older thread with a slow charging issue. A hard reset solved it in this case and it was thought that a vpn client was the reason. I use 'Block This!' and already updated it to the latest version and also disabled it and rebooted. No success up to now.

android.outliner said:
I wanted to wait until end of warranty. So no TWRP as well.
There is an older thread with a slow charging issue. A hard reset solved it in this case and it was thought that a vpn client was the reason. I use 'Block This!' and already updated it to the latest version and also disabled it and rebooted. No success up to now.
Click to expand...
Click to collapse
Yes i was also on that thread because i have 2 tab s2 1 with broken screen and 1 with charging problems too so i did is swap the mobo to get a 100% working tab. I never tried to hard reset the defected mobo because i cant remove the working lcd again because of the adhesive of the hw buttons which is hard not to break when removing screen. Hope you find solution to your problem and incase you do pls share the info mabe i can recover the other mobo, its always better to have extra item for future repair

android.outliner said:
Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Because the device is not rooted, I can't use WakeLockDetector to find the specific reason. The ADB workaround also does not work, because USB connection fails.
Click to expand...
Click to collapse
I want to add, that Odin does not see the device in download mode.
I slowly begin to assume that I have a broken USB and the WakeLocks are not connected to the issue. Or maybe Android tries to access the Port and does not find it and for that reason stays awake. Does that make sense?

android.outliner said:
I want to add, that Odin does not see the device in download mode.
I slowly begin to assume that I have a broken USB and the WakeLocks are not connected to the issue. Or maybe Android tries to access the Port and does not find it and for that reason stays awake. Does that make sense?
Click to expand...
Click to collapse
My other tab was not even showing in computer only charging with red X when connected to pc, while in normal usb charger it takes forever to charge. ive tried to chage the port with my other tab too and nothing changed

meawww said:
My other tab was not even showing in computer only charging with red X when connected to pc, while in normal usb charger it takes forever to charge. ive tried to chage the port with my other tab too and nothing changed
Click to expand...
Click to collapse
So in your case it was a motherboard failure and not a broken USB? The 'red X' and 'charging takes forever' sound familiar.

android.outliner said:
Not yet. I first try to find a solution without setting up everything again. Without root unfortunately I can't use TitaniumBackup. Without USB I unfortunately can't root.
Click to expand...
Click to collapse
Smartswitch mobile, backup to sdcard.

android.outliner said:
So in your case it was a motherboard failure and not a broken USB? The 'red X' and 'charging takes forever' sound familiar.
Click to expand...
Click to collapse
Sorry for late reply im deodexing the android 7 and de-knoxing for my tab, Yes was a faulty mobo (not sure) because i havent tried the hard reset like the dude said in the other thread.. The X in the battery is only connected to pc if i connect to normal charger it has no X but charge super slow

android.outliner said:
Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Because the device is not rooted, I can't use WakeLockDetector to find the specific reason. The ADB workaround also does not work, because USB connection fails.
Click to expand...
Click to collapse
I now tried a hard reset. Unfortunately nothing changed.
I made an OTA update to Android 7.0. Unfortunately nothing changed.
So I assume a broken motherboard or a broken USB port.
I also tried a backup/restore with Samsung Smart Switch to an external SD card. It doesn't backup the App databases/settings and just more or less random SD card folders. It does backup the APKs. You can't rely on it but it's better than nothing if you don't have an USB port. Some Apps like Nova and Solid Explorer provide backups of their settings. Use it in addition to Smart Switch and manually backup your internal card.
Thanks for your comments.

android.outliner said:
Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Click to expand...
Click to collapse
Eventually I sent the device to repair. They changed the motherboard and everything is fine now. Warranty covered the repair, fortunately.

for people have this usb port problem, I had this too before,
what i did to fix it is to use hair dryer, dry usb port for 30 secs, rest for 10 secs, dry 30 secs again, then let it cool down for 3 mins , that's it , it fixed.

kevinchg said:
for people have this usb port problem, I had this too before,
what i did to fix it is to use hair dryer, dry usb port for 30 secs, rest for 10 secs, dry 30 secs again, then let it cool down for 3 mins , that's it , it fixed.
Click to expand...
Click to collapse
Interesting technique Kevin. Any idea how this fix worked?

**Help needed with no charge and the lacklustre help not given via MAZE(Alpha 4gig)**

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...