Database Develop

[Q] Sprint Hero boot problem

Does anyone have any idea why a Hero would for no apparent reason while sitting on a charger go into a reboot cycle only bringing up the htc sign and then the phone with triangle and exclamation point and do nothing else? the phone has never been rooted or anything just did that on its own.
Would running the Regawmod rooter exe possibly fix this?
Also i have another Hero i was given that i have tried to run the rooter on but everytime i do i get the error "Necessary HTC drivers are missing".
i have tried three different versions of HTC sync since i don't know where to get the drivers seperately. all with the same result. any help will be greatly appreciated.
Thanks in advance

Tap my avatar or search the hero dev section for my thread on how to install adb. Try those drivers and see if they work for you. If they do then try the hero rooter or run the ruu.
#Root/Hack-Mod_Always*

no luck. still have the orange triangle and exclamation point, tried the ADB thing and its not recognizing that the phone is there. but when i plug the phone into the computer it acts as though it is mounting as an external drive but when i click the drive letter it says to please insert a disk.
when i try holding the home and power button i get an error at the bottom of the screen that reads "E:Can't open /cache/recovery/command"

Tuvan03 said:
no luck. still have the orange triangle and exclamation point, tried the ADB thing and its not recognizing that the phone is there. but when i plug the phone into the computer it acts as though it is mounting as an external drive but when i click the drive letter it says to please insert a disk.
when i try holding the home and power button i get an error at the bottom of the screen that reads "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
Ok what steps did you take?? Details please?? And when you setup adb did you type adb devices??? And how did you go about setting up adb???
#Root/Hack-Mod_Always*

i went through the steps in your post minus the mobile stream tether and i can't enable usb debugging because the phone will not boot up at all. it has been this way since last night. was just sitting charging and then went into a reboot cycle only bringing up the HTC logo then after awhile of that ended up at the screen its at now with the phone with the triangle and exclamation point.
i did type adb devices but it didn't come up with anything in the list of attached devices.
Edit: i did put the easy tether on the computer but since i can't access the usb options on the phone i can't set up the debugging. i don't know whats up with the phone

Tuvan03 said:
i went through the steps in your post minus the mobile stream tether and i can't enable usb debugging because the phone will not boot up at all. it has been this way since last night. was just sitting charging and then went into a reboot cycle only bringing up the HTC logo then after awhile of that ended up at the screen its at now with the phone with the triangle and exclamation point.
i did type adb devices but it didn't come up with anything in the list of attached devices.
Click to expand...
Click to collapse
The mobile stream steps were the android drivers I originally suggested you to try. So try those drivers and see if they work for you. I posted that thread for users who were having trouble with the htc drivers
#Root/Hack-Mod_Always*

ok well i hooked up the working hero so it would install the drivers, which it did, then i hooked up the hero that is stuck for no apparent reason on the error screen and i was finally able to run the regawMOD rooter but i guess because it doesn't have usb debugging enabled it won't allow anything to happen.
just trying to sort out what happened to this phone for it to be stuck at this error screen. nothing has ever been done to it just happened last night while it was charging

Tuvan03 said:
Does anyone have any idea why a Hero would for no apparent reason while sitting on a charger go into a reboot cycle only bringing up the htc sign and then the phone with triangle and exclamation point and do nothing else? the phone has never been rooted or anything just did that on its own.
Click to expand...
Click to collapse
What you're seeing is the stock bootable recovery image. Pulling the battery and powering it on again should make this go away. Have you already tried that?

jasonmaloney said:
What you're seeing is the stock bootable recovery image. Pulling the battery and powering it on again should make this go away. Have you already tried that?
Click to expand...
Click to collapse
yes have already tried this a couple times, now it just sits at the phone with triangle and exclamation point. won't do anything else

well took the phone to sprint and they deemed it unsalvageable so i guess this is moot. he tried all the standard resets etc. so thanks for all the help but guess the phone is a brick now. wouldn't replace it because the moisture indicators had been tripped.
youd think there would be a way to reforce the OS onto the phone to try to get it going again.

If it was sitting on the charger and went bad, perhaps your charger fried it in some way. Sorry to hear your loss, but look it as an opportunity to get an better phone

[Q] Galaxy Nexus COMPLETELY DEAD. Does not boot into ANY mode.

Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.

wrong forum mate...if you go to this link, they might be able to help you there
http://forum.xda-developers.com/forumdisplay.php?f=1431

hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse

onlinemoon said:
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
Click to expand...
Click to collapse
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
i have same problem. can you fix it now?

adesos said:
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
i have same problem. can you fix it now?
Click to expand...
Click to collapse
Well done for not reading the thread and realising you were asking the question in the *wrong forum*!

Hey man I have the same problem and my phone is also from UAE. Did you figure it out??
Sorry posting here.

WTF are these guys for real? This thread should have been deleted the day it was started!!

This is posted in wrong section.
**Reported**

Thread Closed​
This forum is for the galaxy note, please post in the correct forum​

Qhsusb_dload?

Is there a novacom command to correct this?

Okay, I've got the Qualcomm QHSUSB driver loader. Anyone know how to reset with QSPT?

I'm not sure what you're asking. What are you trying to do?

I'm trying to get it out of download mode. I'm trying to awaken it.

pworcester said:
I'm trying to get it out of download mode. I'm trying to awaken it.
Click to expand...
Click to collapse
Where are you getting this message? Are you plugged into your computer? Are you trying to transfer files or what? What were you doing before this error occurred? What is download mode? Awaken what, the Touchpad?
We need a lot more detail than what you've given us to help you.

This was my son-in-laws tp. He powered it off and now it will not power on. When connect it ot my windows 7 pc it is recoqnized as QHSUSB_DLOAD. This is a special
Qaulcomm mode.

pworcester said:
This was my son-in-laws tp. He powered it off and now it will not power on. When connect it ot my windows 7 pc it is recoqnized as QHSUSB_DLOAD. This is a special
Qaulcomm mode.
Click to expand...
Click to collapse
Try holding power and home down for about 15 seconds at the same time while connected to the PC. If it doesn't work the first time, try a few more times.

tried it. nothing

pworcester said:
tried it. nothing
Click to expand...
Click to collapse
Sorry, then I have no idea. Hopefully someone else will know.

thanks

I had this problem... and fixed it
... however I cannot guarantee this will work.
Your TP is very VERY low on juice and using the A/C adapter will not work. Power management is not running and trying to charge your TP without power management will not work. You need to trickle the power into the TP, either with the wireless touchstone or using the USB cable plugged into your PC to the TP.
I had the same issue and left my TP on the touchstone for one solid week. After that, I began playing with all the various combinations of button holds (power and Home, solid hold; power and home with my pulsing the home button 10-15-20 times; power and volume up (or down), etc...) and within a few minutes I had the red low battery icon on the display. At that time I jumped to A/C power and let it charge for several hours.
I suffered no loss of data, only had to reboot into CM9 and I was golden.
I hope this helps. And as always, "past performance is not a guarantee of future returns" so while this worked for me, I cannot promise anything.
Good Luck!
---------- Post added at 04:10 PM ---------- Previous post was at 03:42 PM ----------
Check this thread for more information.
http://forum.xda-developers.com/showthread.php?t=1740408&highlight=screen+dead

Thanks. I gave it back to my son-in-law. He's going to send it to HP and hope the doctor it which will blow away moboot.

I got the same issue. I tried the power + home + down volume connected to pc, then I tried the power+home and now is charging.

Possible QHSUSB_DLOAD solutions/fixes.
For anyone who's watching this thread, I have a few possible solutions.
I'm assuming you have the WiFi-only Touchpad (HSTNH-I29C), not the 4G version, although the bootloader should be the same.
First of all, it seems your Touchpad's booted into OMAP Download mode.
You might be able to reset a boot flag and get past this, by doing the following:
Plug in a USB charger for several minutes
While holding Power, quickly click the center home button ten times.
If that fixed it, great. If it recurs, you might want to consider backing up your device and running WebOS Doctor.
If this doesn't work, then bootie might be corrupted, the boot partition is boogered up, tokens may be misset, or the NAND is damaged, and is throwing you into this mode.
If bootie's corrupted, you can fix it, but it's involved, and explained below. If the NAND is damaged, it's time to RMA.
If you have a Linux PC, and feel comfortable building the tool, you can do the following OMAP bootstrapping, paraphrased from http://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery#OMAP_boot_Procedure.
($> is not meant to be typed, but is the prompt.)
Install libusb. On Debian-likes (Ubuntu, Mint et. al) the package is libusb-dev and can be installed with
$> sudo apt-get install libusb-dev
Download the following:
View attachment omap3_usb.tar.bz2, the OMAP USB download client
View attachment boot-topaz.zip, containing the bootloader​ and extract them to a new directory. Put the boot-topaz.bin in the same directory as the omap3_usbload file.
Now that it's all extracted, open a terminal to the directory containing the Makefile, and just run
$> make
You should have an executable named omap3_usbload now.
Now run
$> sudo omap3_usbload boot-topaz.bin
which should show a row of dots.
While it runs, plug in the device. It should say found device! then download ok.
Your Touchpad should be booted.
If it shows a USB logo, you may need to manually back it up through recovery and/or booting the kernel through novacom, and re-doctor it. It's a bit involved, but I can step you through it if that does happen.
If it boots, great.
If, after rebooting, this happens again, I'd advise you to back up and doctor unless you don't mind booting like this every time
If anything needs explaining, feel free to ask in this thread or PM me.
If you think this is helpful, thank Rod Whitby and webos-internals. They're the real brains.

How could you use a software (omap3_usbload) built for Texas Instrument Omap CPU on a Qualcomm SnapDragon ?
Have your tried ?

dadwarf said:
How could you use a software (omap3_usbload) built for Texas Instrument Omap CPU on a Qualcomm SnapDragon ?
Have your tried ?
Click to expand...
Click to collapse
I believe, I have completely derped up. It was 3AM on no sleep. The OMAP was on the Pre, wasn't it?
I feel like a grand fool.

Just need overnight charge with correct A/C adapter, not with PC.

TPdebrick004 Ping Check Issue

My HP Touchpad used to show signs of charging, but it did not respond to anything else, i have tried pressing and holding all kinds of buttons and nothing has worked. I recently tried using tpdebrick 004, and unfortunately it did not properly finish.
http://i.imgur.com/BNyH0Oq.png
i have tried tpdebrick 004 countless times, and it always stops at the same point. I also want to mention when the touchpad is plugged in now, the charging lights on the home button dont light up anymore, after using tpdebrick 004. I just wanna know if I CAN do anything else to save this touchpad, or should i just set the arrangements for a proper burial. You are all invited D=

Disconnect your network card manually before launch script

Had the same issue. I just used Ubuntu 12.04.5 and got it to work.

carnage017 said:
..... , or should i just set the arrangements for a proper burial. You are all invited D=
Click to expand...
Click to collapse
Well? Did you resurrect it? Here's hoping you did...
I got to remember that disconnect network, I always forget...

Thank you for your responses guys. I disabled both wifi and ethernet and the same error on the screenshot appeared again.
I will download the old version of Ubuntu and try that later...

Ok, i got good news and bad news.
The good news is that lesbehonest was correct, and by running 12.04 ubuntu linux and running tpdebrick from there it works. I also noticed the charging blinking lights came back as before when charging. The bad news is that the touchpad still dead, it keeps charging and shows no signs of booting up.

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