Database Develop

PLEASE HELP!!! Wont Boot - Red/Green/Blue Screen

Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow

and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows

Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.

Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.

grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?

If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.

GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).

Actually, ill just message you tomorrow or something.
Ive been really busy this week.

well did you get it fixed? what did you do?

Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.

I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it

You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!

this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse

dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse

dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.

GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?

[Q] Continuum, what have I done?

Hi everyone, I'm new to this forum (first post), I've owned my Continuum for a few months now happily with no problems. I actually love the phone! But recently I ran into a pretty big problem...
Let me give you a little background on my phone first, I have used SuperOneClick on it, to grant super user permissions, I've used the program to grant me access to the phone tethering apps that are out (currently using Open Garden), and the AdFree app in the market. I havn't used anything else in regards to 'hacking' my phone so I'm a bit confused as to why I'm getting trouble.
Anyways here's my problem, lol! Well the other day I turned off my phone and tried turning it back on and I would get a grey battery with the spinning disk, and it wouldn't turn on :\! I tried holding all the buttons, for over 10 seconds, no avail. It still turned on to the battery and nothing. I tried taking the battery out for a whiiiile and nothing. Eventually I plugged in my phone to the wall and it magically worked. Actually that's the only way I've been able to get my phone to turn on lately. It works fine once it's on but every time I turn it off the same thing happens .
So that's truly why I'm here... Is my phone 'bricked', or are these some symptoms of being 'bricked'? Are there any fixxes I can go about taking to you know...fix the problem ?
Any help would be Greatly appreciated,
Thanks everyone,
-Matt

Oops, I forgot to mention that my phone has been acting strange sometimes in the sense that I plug it into the wall and the 'Mass Storage/ Media player' option comes up, even though it's not plugged into the computer, just into the wall.
Pretty strange huh?
Anyways thanks again everyone who helps!!!

detex said:
Oops, I forgot to mention that my phone has been acting strange sometimes in the sense that I plug it into the wall and the 'Mass Storage/ Media player' option comes up, even though it's not plugged into the computer, just into the wall.
Pretty strange huh?
Anyways thanks again everyone who helps!!!
Click to expand...
Click to collapse
In short, you're not bricked, but there's obviously some fishy stuff happening. At this point, it would be good to determine whether it's a hardware or software issue. On that note, just a few quick questions:
1. Has anything happened (hardware-wise) recently that you're aware of? E.g. it was dropped, got wet, etc?
2. What sort of charger are you using? Is it the Samsung one that came with the phone?
3. What USB cable are you using to charge the phone? Again, Samsung original or something else?
4. Can you get into any sort of recovery (when booted, hold Vol+, Vol-, and Power at the same time until it shows the AT&T screen twice) or download mode (when off, hold V+ and V-, then insert USB cable)? This may not have anything to do with your issues, but it will help in troubleshooting.

Hello there, I found out that I wasn't supposed to really post this thread here so I went ahead and posted it in the Continuum section, where they had me do as you said, hold the vol- button and turn on the phone. It's currently "Downloading... Do not turn of Target!!!" I'm not really sure what it's doing but that's what it says (it's been doing this for 15 minutes lol). But to answer your questions, I took the phone with me on vacation this past weekend and I had it on the beach in some pretty hot weather, but I always kept it in the shade (I treat my things pretty well) so it shouldn't have gotten too hot, and I didn't drop it or get it wet or anything either! As far as the charger goes, it is the same charger that came with the phone, from Droid. And jsyk I'm with VZW if that changes anything, because I know you mentioned AT&T.
Thanks for the help , I'll let you know what goes on with the phone once it finishes doing what it's doing haha.

detex said:
Hello there, I found out that I wasn't supposed to really post this thread here so I went ahead and posted it in the Continuum section, where they had me do as you said, hold the vol- button and turn on the phone. It's currently "Downloading... Do not turn of Target!!!" I'm not really sure what it's doing but that's what it says (it's been doing this for 15 minutes lol). But to answer your questions, I took the phone with me on vacation this past weekend and I had it on the beach in some pretty hot weather, but I always kept it in the shade (I treat my things pretty well) so it shouldn't have gotten too hot, and I didn't drop it or get it wet or anything either! As far as the charger goes, it is the same charger that came with the phone, from Droid. And jsyk I'm with VZW if that changes anything, because I know you mentioned AT&T.
Thanks for the help , I'll let you know what goes on with the phone once it finishes doing what it's doing haha.
Click to expand...
Click to collapse
Oh, ok. Good luck - hopefully you find what you need in that forum.
(By the way, you'll never see the end of the downloading screen. Unless you're actively doing something to you phone (like flashing a ROM) at that screen, it will just sit there until something tells it to reboot.)

Wow, I feel like a dumbass! I've been waiting for it to do something lmao. No I'm not flashing it with a ROM or anything so should I just hold the power button or something?

detex said:
Wow, I feel like a dumbass! I've been waiting for it to do something lmao. No I'm not flashing it with a ROM or anything so should I just hold the power button or something?
Click to expand...
Click to collapse
Don't feel bad - I'm pretty sure all of us have done that same thing at one point or another.
As long as you just dumped it into download mode with the button combo you mentioned, just pull the battery out and try to restart the phone like normal. Assuming everything is the same as it is on the Captivate, you should be back to where you were.

Alright I pulled the battery out and stuck it back in, and tried turning on my phone normally and it turned on just fine. Pretty funny that it just worked just like that. Thanks lol. Also, any recommendation with what to do with my charger and the USB action it occasionally takes on my phone?

As a test, try turning on USB debugging (Settings-Applications-Development-USB Debugging) and see if you still get that set of options. You could also look on the applications menu for something about having it ask when you insert the cable, and change from that option to the one you use most often.
The only time I've had my phone do that to me in a strictly-charging scenario is when I hook it up to my car USB charger, but that's a non-Samsung charger.

Alrighty, I put it on that setting and I'll leave it that way. Hopefully it doesn't do that again, and if it does I'll try out another charger since I have two that are identical.
Thanks again for all the help,
-Matt
PS. one quick question ! What are mock locations?

You're welcome.
As far as the mock locations go, my understanding is that it lets you tell applications that your phone is a different location than what it actually is (think something like DVD regions). I'm not 100% clear on its use, but my guess would be that it either allows you to see more apps in the market than you normally would, or that you can run apps that are specific to a different region than where you are.

I see, thanks, I've been wondering what that was. See you around!

[Q] I think I've killed it!

I ripped my SD slot out a few months back after getting a card stuck in it, I threw the Nook in a corner in disgust and left it there,
I've tried to get it back up and running over the last few days, I've charged it fully over two days using the wall charger but it refuses to boot - I have nothing at all displayed. when i plug it into my PC I hear the noise it makes when a usb device is plugged in but that's it - nothing..
So with all the methods of restoring it need the SD slot..I guessing it's a gonna??
Any ideas??

Could try to convert back to stock. There is a 3 finger method of restoring your nook back to stock. You can find the link here in XDA right here. http://forum.xda-developers.com/showthread.php?t=1461172
Then you can take it back to B&N for a replacement if its still under warranty. Don't be so hardcore with losing on game-mode next time

I tried that last night but will try again with a fresh head ....

Nope..not having it, Tried everything now, using the three finger method brings nothing up on the nook screen at all - totally blank although the pc ssems to respond by making a couple of bleeps so assumed this was akin to the nook being turned on , tried it eight times and nothing..I really do think it's dead...

There is a program in the sdk (/tools/ddms) that allows you to see what is on the screen (and take screenshots). I believe this pulls from what the system is pushing to the screen (not what is actually on the screen). If that is the case, you can hit the power button like you normally would to bring up the lock screen, refresh using the application and see if it is pushing anything. You'd have to be quick, because if the NC is in standby, it won't show anything.
Also, you may want to try pulling some logcats to see what is going on.

I think the nook should be unplugged from the computer when trying the 8 failed boots. Also make sure to hold down the power button at least 8 seconds to make sure the nook is really off.
Sent from my NookColor using xda app-developers app

Can't seem to get the pc to see the Nook, it asks for OMAP3630 driver??
DDms can't see the nook ..
tried the 8 failed boot method...
All is not well

Its now on a popular auction site for spares..I give in.
new one bought and on its way..

p2daz said:
Its now on a popular auction site for spares..I give in.
new one bought and on its way..
Click to expand...
Click to collapse
PM me... I can either fix it and send it back... or perhaps we can work out a price to buy it from you.

I have the same problem. The only way I could get it to recognize it was by holding power for 8 seconds and then would go away after a ssecond or [email protected]

DizzyDen said:
PM me... I can either fix it and send it back... or perhaps we can work out a price to buy it from you.
Click to expand...
Click to collapse
Thank you for the offer but I've bought another and might as well keep it for spares, the postage to the states and back alone would cost what I've paid for the replacement.
Or you could tell me how you would fix it ;-)

What I would wind up doing depends a lot on what is on it already, and what methods were used... first thing I'd do is modify ROM's to ensure mmcblk0p8 was seen as sdcard... then go from there...
I wish I could give you a definitive "Do this, then this, and finally this" type of answer... but there are so many variables in place there's no way I can without knowing more of what is there...
If you have a custom ROM on it... go to playstore and get adb wireless

[Q] Boot Loop while charging - no charge

Hello, I've had my G Watch R for not quite a full week so far and I've really enjoyed it. Two days ago, I believe that I let the battery die so I placed it on the charger before going to bed. When I woke in the morning i grabbed the watch off the charger without looking at it. Just before i stepped out the door i noticed that it wasn't waking up and It wouldn't even power on. I ran back and slapped it on the charger thinking that it would be more than charged by lunch time. Thats when i noticed the apparent boot issue you can see in the video attached. It hasn't been dropped at all and I have the basic apps installed; facer, watchmaker etc. At this point, Is there anything that I can try short of sending it back?
I've left it on the charger for 24+ hours, it gets slightly warm and stays in the boot loop. As soon as its taken off the charger it has no visible charge and refuses to respond to anything. I purchased it through amazon, so I'm thinking it shouldn't be an issue for me to return it...
http://youtu.be/GgF3iXAhTTI/
Sorry i tried to embed the video but the youtube link for xda seems to be breaking the url somehow

So I have already initiated the return process with amazon and it should be pretty painless. I have almost 3 weeks to send it back, so if anyone has any tips/tricks or ideas I'm more than open to try them....The watch is 100% stock as far as firmware or root is concerned.

Any luck with this? I just got back an RMA for a broken touch sensor, I don't want to have to RMA it again.

try to see if you can get in to the bootloader, and restart the watch from there
i have notice when i charge the watch from empty (so thewatch boots up while charging) it causes problems, usually boot loops as well

I just watched the video (should've done this before hijacking the thread, sorry) and it seems like I'm having a different issue. Instead, mine does the android boot animation, the goes to "Starting Apps" and counting ("x of y Apps"; the y value seems to be different every time), then "Staring Apps" with no count, then it says "Powering Off" and shuts off. But I will post my experience in case someone else with my issue finds this thread.
I'm back up & running today. I got it into the bootloader last night and put it on the charger before I went to sleep (to avoid battery rundown by bootlooping while it charges). I woke up this morning to it bootlooping again. I'm guessing that it restarted itself sometime during the night. I took it off the charger and let it sit for a while (it was pretty warm, so I figured it would be better to let it cool down before trying anything else). I tried to restart it again after about a half hour, but it still only got to "Starting Apps" before shutting off. I reflashed the stock boot, recovery & system images found here: Stock Boot, Recovery and System for G Watch R . I restarted it and completed the initial pairing process (due to wipe when I unlocked it in order to flash system image) and it is now working.
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.

To workaround the bootloop while charging, you can boot into recovery (swipe 10 to 4 a clock while Logo is shown, select and press okay to recovery), than charge battery for a while, after that, you can boot to as normally to AW-system and charge to fully battery!

You can charge with USB on PC, it's work fine for me.

scidon37 said:
I just watched the video
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
Click to expand...
Click to collapse
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.

Have you tried taking it off the charger and booting it? Also are you running custom software?

bricked watch
atmosphrericks said:
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Click to expand...
Click to collapse
Ever find a fix for this? I've been searching like mad the last few weeks. :/

biohazard1150 said:
Ever find a fix for this? I've been searching like mad the last few weeks. :/
Click to expand...
Click to collapse
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!

atmosphrericks said:
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
Click to expand...
Click to collapse
I still haven't found a fix. My charging works fine, but no PC connection. The bootloader/fastboot wont come up, no logo or anything. I'm sure the EMMC chip is fried, it sounds like many are seeing this issue, some with a black screen and some with a snowy screen. I've had several galaxy phones do the exact same so I'm doubting it can be fixed without going to the manufacturer which mine came from redflagdeals and LG wont service the random online store purchases

I had to take the back off and clean and adjust the contacts that make contact through the back panel. Then I could connect via fastboot.

ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This solved my problem. As soon as I plugged it into my PC it booted just fine

ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This works for me too! Thank you!
Sent from my SM-N920C using Tapatalk

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