Related
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
akashastrega said:
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
Click to expand...
Click to collapse
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
peter petrelli said:
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
Click to expand...
Click to collapse
I had at least 80 percent battery. I cannot get into the tri-color screen. Tried holding camera and soft reset, tried comm, camera, power, tried talking sweet to it...it just goes to splash screen each time. HELP!!!
This is a G3 wiza200 IPL/SPL 2.26 and it IS unlocked.
Thanks in advance
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
peter petrelli said:
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
Click to expand...
Click to collapse
Yeah, I know...in theory it SHOULD, it's not, hence the freaking out. I am attempting to charge it on the main plug, but it begins to charge then dies. I did have a loose usb port, which I thought got fixed, as my phone charged fine last night, and sync'd fine today. I'm not a pro, but not a noob either...so I am getting frustrated because trying the things I do know, aren't producing the results they should.
**The splash screen is one I made, independent of an OS...after any rom change, I flash my custom splash screen...it has always worked...however, it is making me think that it is the ONLY thing on the MDA, and any signs of a rom were somehow killed by my kids flashing the phone with a very incomplete kitchen rom.**
I will try again. Any help that can be offered would be MUCH appreciated.
PS---I LOVE Heroes!!
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
peter petrelli said:
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
Click to expand...
Click to collapse
I can get brief and random orange lights (my phone was not 100% but at least 80% when I first began)...it takes a lot of sweet talking though to get it to connect to charge. I tried a backup battery as well. Pushing the camera and soft reset either produces my custom splash, or nothing at all (no boot whatsoever). I am truly stumped.
EDIT
I am not aware of the SD card method. I do have an SD, but if I need a special program, I do not have it.
The fact that no light remains on when you connect usb or mains plug makes me think that the usb socket is loose again. In which case I'm doubtful that you can flash via bootloader mode.
The fact that you cant get into bootoader mode suggests that it was somehow corrupted when the flashing process was interrupted. This could be unrecoverable.
From here I'd suggest you investigate the sd card method. I've never relied on this method so this is uncharted territory for both of us.
Read this thread here and here. I think we're running out of options...
Semi success, I got into the quad colored boot (white bottom)...but cannot get it to recognize the usb. I am getting an error message about an unrecognized device, so I will try to fix active sync first...any suggestions for me now that I am at least in a bootloader screen
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
peter petrelli said:
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
Click to expand...
Click to collapse
it shows usb in the corner, however it is not producing any charging light, nor does my pc recognize the usb. So...I don't know if this will matter, but as I said...I have the RGB + white bootscreen with usb in the corner...is there still a chance????
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
peter petrelli said:
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
Click to expand...
Click to collapse
wcescomm.exe is NOT showing in Task Mgr...I will try to flash anyway. I killed the firewall and the sd had been removed already. Any other suggestions??
EDIT
ruu error 260 update error
It cannot connect, please check to make sure it is cradled blah blah blah
Thats ok. I forgot that the previous flashing attempts would have killed it off anyway.
So I get ruu error 260
I have rebooted my pc, deleted any connections in active sync (leaving only guest)...
UgggH
It is NOT recognizing the usb
the usb port is as tight today as it was last night after my hubby repaired it...I'm backed to stumped
EDIT**
I had to reboot MDA, now I have lost the little corner usb...but I still have the quad bootscreen
This is progress at least, 1 hour ago we didnt even have bootloader mode. Perhaps you could try flashing another rom, but I think if error 260 keeps appearing then something is wrong with the USB socket.
somehow i lost bootloader again...
this is driving me insane!!!
am trying again, will update momentarily.
************EDIT*****************
Finally got it back into bootloader, but it will not read the usb. keep getting that stupid error message that it doesn't recognize the device, and if I try to flash it with a stock rom, I get error 260.
I have closed the wcescomm.exe
I have killed my firewall
I have rebooted my phone, my pc...everything a few times
I have deleted any connections in active sync
I have unticked allow usb in active sync
WHAT AM I MISSING???
The usb port on the phone does not feel loose again...could it have got fried somehow? I feel as if I can get the damned usb to be recognized, I can save my precious MDA.
Please...any other suggestions, brainstorms, whatever???
THANK YOU
I had a little problem with theloons kitchen doing the same thing to me last week where it would give me the 260 error. I'll upload a ROM flashing file for you to try. Probably the best thing to do right now would be to take the nk.nbf file from an official ROM and stick it in this file and then run the RUU in it. After that you should be ok again to try your luck at cooking with theloons kitchen again although you may want to wait 'til the kids are at school or something before you try it.
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
mestrini said:
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
Click to expand...
Click to collapse
absolutely right while in bootloader mode it wont charge,but to charge or verify status of usb connectivity,while in bootloader mode push power off button,it'll go in sleep mode but lights will show charging if usb cable is charging
usb cable might be charging but mini usb port of the phone has many connectors I think 9 connectors,I'm not sure,may be the connector for making connectivity relation with phone and pc is damaged.
try with another usb cable if possible,if the connectivity with usb is established than method in the link provided by 'mestrini' is a good option,good luck
My Verizon Wireless Droid 3 stopped booting normally on Tuesday evening. It has not been rooted or anything like that. When I boot it now, once the boot sequence has finished instead of displaying the home screen it stays stuck on the red animated boot screen for a little while and then goes completely blank. I cannot do anything with the phone - none of the buttons work. I can hear some audio notifications however so it seems to be booted completely, but locked to any user input. I get the same behavior when booting it in safe mode. If I call my cell phone from a landline, it receives the call, displays the incoming call on the screen, and I can accept or reject it using the normal screen swipe motions. When the call is answered, I can talk/hear as well as use the in-call dial pad. I cannot, however, use any of the 4 buttons at the bottom of the phone or access the notification bar at the top of the screen. As soon as the call ends, the screen becomes unusable/blank again.
Once booted in this state, after a couple of minutes it sort of resets, in that it sounds/displays the "Droid" message, followed by the red animated boot screen. However, if connected to my computer when this happens, the two external drives do not disappear, which seems to indicate that the phone is still at least semi-booted during this time? If left alone, that cycle repeats and repeats (every few minutes it sounds/displays "Droid" then the red animated boot screen).
When I connect a USB cable to my computer while the phone is up in this state, it displays two empty external drives.
Through research on this forum and others I have downloaded/installed adb and the Android SDK. I cannot get adb to recognize the phone, presumably because I'm quite sure USB Debugging was not enabled on my phone before it started acting up.
When booting via FastBoot and connecting via USB it recognizes a "Android ADB Interface" device in device manager, however adb itself still does not recognize the device.
Doing a factory reset is not an option at this point due to encrypted files/photos on the phone/sd card. I had to turn encryption on in order to use my corporate e-mail on the phone.
The boot menu gives me these options:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools
Can anyone give me some advice on gaining access to the phone via adb or anything else? I've seen mention of Early USB Enumeration on some other androids, but am not seeing this option on my phone anywhere.
Forgot to mention that I also tried wiping the phone's cache via the recovery menu, but to no avail.
jessman1128 said:
My Verizon Wireless Droid 3 stopped booting normally on Tuesday evening. It has not been rooted or anything like that. When I boot it now, once the boot sequence has finished instead of displaying the home screen it stays stuck on the red animated boot screen for a little while and then goes completely blank. I cannot do anything with the phone - none of the buttons work. I can hear some audio notifications however so it seems to be booted completely, but locked to any user input. I get the same behavior when booting it in safe mode. If I call my cell phone from a landline, it receives the call, displays the incoming call on the screen, and I can accept or reject it using the normal screen swipe motions. When the call is answered, I can talk/hear as well as use the in-call dial pad. I cannot, however, use any of the 4 buttons at the bottom of the phone or access the notification bar at the top of the screen. As soon as the call ends, the screen becomes unusable/blank again.
Once booted in this state, after a couple of minutes it sort of resets, in that it sounds/displays the "Droid" message, followed by the red animated boot screen. However, if connected to my computer when this happens, the two external drives do not disappear, which seems to indicate that the phone is still at least semi-booted during this time? If left alone, that cycle repeats and repeats (every few minutes it sounds/displays "Droid" then the red animated boot screen).
When I connect a USB cable to my computer while the phone is up in this state, it displays two empty external drives.
Through research on this forum and others I have downloaded/installed adb and the Android SDK. I cannot get adb to recognize the phone, presumably because I'm quite sure USB Debugging was not enabled on my phone before it started acting up.
When booting via FastBoot and connecting via USB it recognizes a "Android ADB Interface" device in device manager, however adb itself still does not recognize the device.
Doing a factory reset is not an option at this point due to encrypted files/photos on the phone/sd card. I had to turn encryption on in order to use my corporate e-mail on the phone.
The boot menu gives me these options:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools
Can anyone give me some advice on gaining access to the phone via adb or anything else? I've seen mention of Early USB Enumeration on some other androids, but am not seeing this option on my phone anywhere.
Click to expand...
Click to collapse
Since you said you can receive calls, during a call, place in speakerphone mode and hit the HOME button. It should background the call to the notification bar and unlock sliding down the notification bar and take you to the home screen. (using AT&T I can do this to stay in call and browse/do whatever on data while in a call).
Have someone (or you) call the phone, press home, then hit Menu > Settings > Applications > debugging and enable USB debugging. This should get you ADB, do NOT hang up during this just in case.
Skreelink said:
Since you said you can receive calls, during a call, place in speakerphone mode and hit the HOME button. It should background the call to the notification bar and unlock sliding down the notification bar and take you to the home screen. (using AT&T I can do this to stay in call and browse/do whatever on data while in a call).
Have someone (or you) call the phone, press home, then hit Menu > Settings > Applications > debugging and enable USB debugging. This should get you ADB, do NOT hang up during this just in case.
Click to expand...
Click to collapse
I can place the call in speaker mode, but the home button (plus the other 3) still do not work, nor does the notification bar (although I can see the notification bar). At some point it did delegate the call to the notification bar (although not immediately after placing it in speaker mode), but at that point the rest of the screen went black and only the notification bar was visible (but not accessible). I did receive a message this time, right before answering the call, that process Home Screen was stuck or something and it prompted me to either force close or wait. I told it to wait. And now it just initiated a partial reboot, even though I was still in-call.
Also, in case it's relevant, I am using LauncherPro as my home screen.
jessman1128 said:
Also, in case it's relevant, I am using LauncherPro as my home screen.
Click to expand...
Click to collapse
Sounds like something may have happened to LauncherPro, and since it's your default launcher, the home button isn't going back to regular motorola home. Try booting the phone and (hoping) if it has a data connection, on your PC go to https://play.google.com/apps login, it should display your devices, click on your Droid 3, find LauncherPro, and uninstall remotely. It should be the small trash-can next to where it says 'installed'
OR you can try installing another launcher, such as ADW, Go Launcher, etc. and remotely installing it, then hitting home, which SHOULD reprompt for default launcher/home.
Maybe do a combination of the two, just to insure you're not stuck without a launcher at all, though not rooting, MotorolaHome shouldn't have been affected.
Skreelink said:
Sounds like something may have happened to LauncherPro, and since it's your default launcher, the home button isn't going back to regular motorola home. Try booting the phone and (hoping) if it has a data connection, on your PC go to [] login, it should display your devices, click on your Droid 3, find LauncherPro, and uninstall remotely. It should be the small trash-can next to where it says 'installed'
OR you can try installing another launcher, such as ADW, Go Launcher, etc. and remotely installing it, then hitting home, which SHOULD reprompt for default launcher/home.
Maybe do a combination of the two, just to insure you're not stuck without a launcher at all, though not rooting, MotorolaHome shouldn't have been affected.
Click to expand...
Click to collapse
You are a lifesaver. You rock. You are awesome. I'd click Thanks on your post one thousand times if it would let me. I have my phone back!
I followed both suggestions - I loaded the Play store on my computer and installed ADW as well as removed Launcher Pro plus a few other apps. It took I think 3 boot cycles before it finished making all of those changes on my phone (because it would only stay up for 1-2 minutes each time), but once it was done I had my phone back.
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
In recent weeks I've been kicking around the idea of rooting my phone and installing a custom rom. Thinking this might be a good time to try it now that I have everything copied off of my phone now. I don't know much about custom roms though. Do you happen to know if any of the available ones for D3 will support corporate e-mail?
jessman1128 said:
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
Click to expand...
Click to collapse
Good news. But, do yourself a favor - try activating a service that automatically uploads all photos, such as Google+ or Dropbox or Sugrasync. That way if you ever get to a point where you need to factory reset you'll have copies of your photos somewhere else.
jessman1128 said:
You are a lifesaver. You rock. You are awesome. I'd click Thanks on your post one thousand times if it would let me. I have my phone back!
I followed both suggestions - I loaded the Play store on my computer and installed ADW as well as removed Launcher Pro plus a few other apps. It took I think 3 boot cycles before it finished making all of those changes on my phone (because it would only stay up for 1-2 minutes each time), but once it was done I had my phone back.
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
In recent weeks I've been kicking around the idea of rooting my phone and installing a custom rom. Thinking this might be a good time to try it now that I have everything copied off of my phone now. I don't know much about custom roms though. Do you happen to know if any of the available ones for D3 will support corporate e-mail?
Click to expand...
Click to collapse
Most likely any roms that are built on the D3 source will unless they stripped it. I use Maverick rom 4.0 myself, it is based on 906 with enhancements, debloat, themed, etc. There are still many bugs to work out on AOSP built roms (cyanogenmod, aokp, etc. Any ics/jb roms). I would suggest sticking with a stable gb rom if it is your business phone.
doogald said:
Good news. But, do yourself a favor - try activating a service that automatically uploads all photos, such as Google+ or Dropbox or Sugrasync. That way if you ever get to a point where you need to factory reset you'll have copies of your photos somewhere else.
Click to expand...
Click to collapse
That sounds like a good idea. I wonder, though, if those services would upload the encrypted or decrypted version of the photos. I'll have to test it and see.
Skreelink said:
Most likely any roms that are built on the D3 source will unless they stripped it. I use Maverick rom 4.0 myself, it is based on 906 with enhancements, debloat, themed, etc. There are still many bugs to work out on AOSP built roms (cyanogenmod, aokp, etc. Any ics/jb roms). I would suggest sticking with a stable gb rom if it is your business phone.
Click to expand...
Click to collapse
Hmm, ok. I'll have to give it some more thought then. It's my personal phone, but I do have my work e-mail setup on it and access it fairly regularly. I don't absolutely need to have my work e-mail on my phone, but it's certainly very helpful to have it setup there.
I've also been thinking about doing a factory reset, as the phone in general has gotten progressively slower as time goes on. Thinking the factory reset might help in that regard. I wonder if there's any way to remove some of the stock Verizon apps I never use when doing a factory reset. I'll have to look into that. I guess I should go search these forums again!
jessman1128 said:
That sounds like a good idea. I wonder, though, if those services would upload the encrypted or decrypted version of the photos. I'll have to test it and see.
Click to expand...
Click to collapse
I setup FolderSync to upload my photos to Google Drive and it is successfully uploading them in decrypted form. Thank you for the suggestion!
So I was on my phone this morning and the screen kinda froze, so I force rebooted [hold power for 10 sec] and when it turned back on this is what I saw instead of the motorola logo. After this, the screen goes black and I can't do anything on my phone. I know the phone is working because I have a Pebble and I still get notifications on it and I can control my music, but that's about it.
Any ideas?
Attached is a picture of the screen when the moto logo should be showing. Also there is an IR light to the left of the speaker (or below the speaker grill?) that is flashing that I noticed when I tried to take this picture, but the camera I used couldn't catch it in a picture.
You could try taking all your personal data off the phone and then reflash if you can get into the bootloader.
You may want to contact Motorola or your carrier, though
dier325 said:
You could try taking all your personal data off the phone and then reflash if you can get into the bootloader.
You may want to contact Motorola or your carrier, though
Click to expand...
Click to collapse
Not sure how I could take my data off. I can't connect via USB unless I unlock my phone at least once, and I can't reboot into the bootloader/recovery to backup anything. I'll probably contact Motorola just to be safe.
iSecks said:
Not sure how I could take my data off. I can't connect via USB unless I unlock my phone at least once, and I can't reboot into the bootloader/recovery to backup anything. I'll probably contact Motorola just to be safe.
Click to expand...
Click to collapse
Hm, my X automatically mounts on my computer so I can browse my ondevice files.
As for rebooting into recovery, you can do so in ADB/Fastboot. But you probably need to enable developer options.
Well, I guess you're outta luck.
Have you tried holding the power button and volume down to get into fastboot.
sent from "my kungfu is stronger then yours" XT1080
iSecks said:
Not sure how I could take my data off. I can't connect via USB unless I unlock my phone at least once, and I can't reboot into the bootloader/recovery to backup anything. I'll probably contact Motorola just to be safe.
Click to expand...
Click to collapse
You should be able to restore to stock w/o USB debugging via fastboot/mfastboot, even though you loose data.
http://forum.xda-developers.com/moto-x/development/script-adb-fastboot-mfastboot-directly-t2817544
&
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------
Try not erasing user data.
Well someone on Reddit solved my issue, posting it here in case someone else runs into the same problem:
I've had the exact same problem occur every few weeks on my 9-month old Verizon model--from the frozen screen to the confetti garbled display on reboot--and I've come up with a reliable, if inelegant, solution.
It usually happens after dropping or jarring my phone or excessively flexing the charging cable, which led me to suspect that there's a problem with the physical connections in the device, maybe a loose display cable.
To fix it--and this has always worked--I hold the phone in one hand and whack the back repeatedly against the heel of my other hand. It's taken several minutes and a few dozen whacks in the worst cases, but it hasn't failed me yet. Sometimes I'll see the display flicker back on only to garble again, so I continue. Shouldn't require a reboot, either; the display should instantly come back to life once it works.
EDIT: I should add that even when I'm experiencing the problem, I can still boot into recovery mode and see that screen without any issues. Not sure how that reconciles with the physical connector theory, but the whacking clearly works.
Click to expand...
Click to collapse
It's so weird that this would work. It's probably some connector issue because otherwise it makes *no* sense.
iSecks said:
Well someone on Reddit solved my issue, posting it here in case someone else runs into the same problem:
It's so weird that this would work. It's probably some connector issue because otherwise it makes *no* sense.
Click to expand...
Click to collapse
You still might want to get a replacement so this won't happen again.
Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)
Phenitei said:
Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)
Click to expand...
Click to collapse
Not realla an idea, but maybe a little help. In the attachement you find a pdf. (Working Instructions for Assembly and Disassembly the phone). Hope, it helps a little. Good luck :fingers-crossed:
Thanks mate! Will look at it this weekend
One of the first thing you should try is to access fastboot. For this you have to hold volume down button while plugging it in to the computer. If the phone is a Xperia SP your led should be blue then (I'm not sure you have this model regarding the description you gave). If this works then we make a small step !
Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!
Phenitei said:
Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!
Click to expand...
Click to collapse
:highfive: Bravo man! As pecOra said, you hae done a grat step - the phone is alive! LED blinking red then green, means, that´s ready for flashing a rom with Flashtool! The problem now is to clarify, what Xperia-model it is, after this you can seach in the right thread for a Rom to flash it on the phone with Flashtool
Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable
[UPDATE] : if, while connected to a computer, the up-volume button is long pressed, then the del becomes a stable and unchanging blue!
Phenitei said:
Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable
Click to expand...
Click to collapse
STOP! Flashing a Rom ALWAYS deletes all data on the internal SD. In the current situation you can make again a functional phone. To readout the data from the SD is an other thing. For this experiment I am to less competent. Maybe another member is smarter than I am, sorry.
No probs! That's also my experience with my phone (wiping I mean), and is why I asked why I would want to flash a ROM. No worries, we all have different skills[emoji41] . I'll help you the day you mess up a samsung [emoji6]
Thx for trying!
Phenitei said:
No probs! That's also my experience with my phone, and is why I asked why I would want to do that. No worries, we all have different skills. I'll help you the day you mess up a samsung
Thx for trying!
Click to expand...
Click to collapse
:good: hope, pecOra can help you!!! He is a great man.
Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?
pec0ra said:
Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?
Click to expand...
Click to collapse
:good: +1
Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.
Phenitei said:
Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.
Click to expand...
Click to collapse
Mmmh this is not good. The solutions use adb so you must have it enabled but that's not really a problem because if your phone boots until adb mode, it will probably boot until usb storage mode too. So if you don't have usb storage when booting, you probably won't have adb mode either.
The second solution was to use adb (or usb storage) in another environment which is much less complex and easier to flash without losing any data : the recovery. The problem is that you can only flash a recovery with fastboot when your bootloader is unlocked. The other ways to flash it use adb and as we've seen we don't have it.
I'm pretty sure you can't access any partition from fastboot if your bootloader is unlocked because otherwise it would open easy exploits to gain root without losing your warranty unlocking your BL.
Now what you still have available is flashtool. This is the (copy of the, with more possibilities) official way to flash firmwares. You use it from your computer when your phone is in the mode with the green light. The problem is that with this you can only flash official firmwares. They might still repair your phone depending on the problem but you must be careful not to erase the data. If you want to try this I can help you in the procedure (you can even pm me en français if you want)
By the way, are you trying to access data like app data/ contacts / messages or data of the external storage?
I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
---------- Post added at 01:07 PM ---------- Previous post was at 12:40 PM ----------
reinipic said:
I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
Click to expand...
Click to collapse
Edit:
btw. when you are opening the flashtool and connect the phone with the pc, than you can see in the flashtool, which Xperia Model it really is, then you can search for the right stockrom and ... buuuuuum :laugh:
Right thanks a lot! I'll take the time to document my self a bit on all that and then I'll be happy to accept your proposal. Merci!
put it in a box of rice 4 days without touching.... you will see the results.
Kmiloxdxd, thanks for your proposal, I'll try! But as I said in the question, I got the phone at least a week after it fell into water, maybe more (up to 3 max) As such, I'm quite sure it's too late for that kind if trick... (which did save a few phones and watches of my own ^^)
You have 2 options..the first one is to reflash stock rom via flashtool without wiping data and the other one which requires a recovery, you can move this zip (http://forum.xda-developers.com/showthread.php?t=1646108) to your sd and move files from internal to external memory.
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...