Acer Liquid E3 Brick? - Android Q&A, Help & Troubleshooting

Greetings,
I'll start by giving you a rundown of my device. It is a Acer Liquid E3 running on Android KitKat 4.4.2, kernel 3.4.67. It uses an MTK mt6589 processor. It is pretty much stock apart from the fact it is rooted. The problem started when I attempted to backup my device in ClockworkMod, I was naming my backup and proceeded and then instant black screen. The device will not turn on full stop. I have tried connecting it to my PC but it doesn't recognise it, when trying to boot via adb I get device not found. Same story goes for Flash Tool. I even downloaded OneClick Unbrick as a last hurrah but supposedly no device was connected.
The last time my phone was connected to my PC it recognised it, it was only plugged in for charging though. Therefore I believe my USB drivers are working. USB debugging was also checked as I've never turned it off since first turning it on. Pretty much the only sign of life is the blue LED that comes on when charging. Worst case scenario at least I'll have a brick that shines some light.
On a serious note I would appreciate some advice on the matter. I haven't been in this position before so it may be something simple that I'm overlooking. Thank You for reading and I'm looking forward to your advice!

Related

[Q] Many and strange problems. help pls.

I have several problems with my Razr MAXX which I'm sure are related.
First one day I erased the CID of the phone without having made a previous backup, therefore I lost him irremediably. This by itself is not supposed biggest problem that I must to boot the phone in BPHW Diag & Boot AP mode.
To correct this I install Safestrap and then I install CM11 in another partition. In this way the phone worked perfectly.
First one day I erase the CID of the phone without having made a previous backup , therefore I lost him irretrievably . This in itself is not supposed biggest problem that I must to boot the phone in BPHW Diag & Boot AP mode.
To correct this I have installed Safestrap and then I Install CM11 in another partition . In this way the phone worked perfectly .
Suddenly one day phone was turned off and not turned on again , then I had to re- flash a stock ROM and then rooted it again to install Safestrap.
Here is when my problems really start.
I boot the phone in FlashBoot mode and install the stock ROM without problem.
Then I boot the ROM (in BPHW Diag & Boot AP mode) and when I am gping to connect the phone to PC by USB to root , but the PC does not detect that the phone is connected .
Another symptom I see is that the phone is not charging the battery despite being connected to the PC. Then I connect the phone to the wall charger and I notice phone don´t charge neither.
Because this, I´m not able to root the phone. The all rooting methods I know implies USB conection with PC.
Before continuing I want to clarify that I have already made all the more obvious tries:
I tried on 3 different pc. In which I did not have any problems before.
I tried with 3 different USB cables, which I used before with no problem.
I've tried different chargers.
I tried 5 different stock rom I had previously always worked well, among them that of Rogers.
And of course I always did the relevant wipes.
Retaking the thread, I have to say that Another issue that I have with the phone is that it does not work the 3g data line. This only occurs whit the stock ROM, because when I use CM11 rom then 3g is working. And this closes the circle of problems that I have:
Resuming, I can´t use 3g because I can´t install CM11, and I can´t install CM11 because I can´t install Safestrap because I can´t root the phone because Pc don´t detect it when I connect the phone with USB...
The only way I have to charge the phone is booting in normal mode.
Remeber that if I don´t boot phone in BPHW Diag & Boot AP mode then it don´t works.
When I boot in normal mode first Motorola logo appears and then the screen goes completely black, but if I look closely I notice that if the phone is on.
When the phone is in this state I can connect it to the mains and then the battery is charging. I know this because if I leave it for several hours and when I turn the phone battery is at 100% capacity.
Another interesting thing is that when the phone is in this state, I connect it to PC and then it is recognized, but this does not allow me rooting the phone because Android not is on.
This invite me to thing that it isn´t a hardware mistake.
If I do the necesary actions to boot Android, then Pc don´t detect again.
It should be mentioned that when I connect the phone via USB, the PC actually detects something, but then it tries to install some drivers that I don´t not know, but finally fails.
The mentioned drivers are this:
DIAG INTERFACE
MODEM INTERFACE
MUX INTERFACE
NMEA INTERFACE
TCMD INTERFACE
I hope someone can help me understand what happens.
I've already tried everything, and I have asked many people, but so far no one has been able to help me.
I think I have not forgotten to mention anything.
Please excuse my bad English.
I hope I have explained in an understandable way, but it's hard to explain it in my native language. Explain this in English is a challenge for me.
Best regards.
Have you tried re-installing the MOTO drivers.?
DROID RAZR with Tapatalk 4
neo.ank said:
Have you tried re-installing the MOTO drivers.?
DROID RAZR with Tapatalk 4
Click to expand...
Click to collapse
Yes. I have tried installing, uninstalling, reinstalling,... on different Pc´s and different operating systems...

[Q] Eken A90 (rooted) showing UNWANTEDLY as ABD

Hi guys, I hope you can help.
I'm tech savvy, but this has been driving me bonkers.
I bought a cheap EKEN A90 (Allwinner A10) from China - I can't remember what version of Android it had, but it was a slow and clunky as hell.
To cut a long story short, I tried flashing it with CM9 and CM10 and managed to brick it, only being able to bring it alive with the lovely and helpful people here using livesuite and a custom firmware A90sun4i_crane_t05a_mma7660_20120614-.img and gapps etc etc....and actually works SO much smoother!
Anyway, BEFORE, when I plugged in the USB, it would show up in My Computer (I'm on Windows XP) as 'CRANE' or something like that and was easy to transfer files between my PC and tablet.
Since the new firmware, when I connect to my PC, it comes up as an ADB device, installs drivers (something like WdfColnINstaller or something) and then says it's a Samsung phone! Which I don't want! I just want it to show up in My Computer like it did before!!!
I used to have Kies installed as I have a Galaxy S2, but have since installed it. (btw my phone comes up as a portable device, which I would love the tablet to do!!)
I've tried loads of things; changing cables, USB debugging mode on and off (there's no MTP option on the tablet btw) uninstalling the ADB thing in PC Device Manager, but nothing has worked and it's driving me bonkers!
I've even looked into changing the tablets Device ID (USB\VID_18D&PID_0002) because apperently that notifies Windows that it's an ADB Instance.
Many thanks

[Q] Another Security Error [P769]

Hello to all since this is my first post on these forums! And to just say thank you to everyone who will respond to me if I don't say it.
I rooted and installed CWM 6.0.1.8 on my phone about a year ago. I did not unlock the boot loader, because I didn't want to have any custom ROMs on my phone. Now just recently I was looking at android 4.4 and thought that this is a good update for any phone. So, I started to do my research for what to do to flash a ROM. I downloaded CWM 6.0.4.5 on my micro SD card and used "[ROOT]Recovery Tools - Flasher". Now this is where everything goes south...
I went through the app, found the CWM file to flash, and then I got the security error... After researching why this happened it was because of not unlocking the boot loader which was a huge mistake that I forgot to do.
I have searched on here a lot. I found a lot of great and useful information, but I can't try any of the suggestions yet. Not until my computer can recognize my phone. I know before this all happened, I had debugging enabled on my phone. I do not have fastboot installed on my computer anymore (reformatted a long time ago). I do have B2CApp.exe installed so I could try to do a factory reset on my phone. I have installed the driver for the phone from the LG program and from their website.
But like I said before, when I plug in my phone to my computer, the computer does nothing. It doesn't recognize that there is even a device there, but there is power getting to it. How I know is because I took out the battery and "S/W Upgrading" could be enabled.
If I can get past this, I'm 100% positive I can fix it then. If anyone has some sort of useful information about my computer not recognizing my phone, please share it! Also, for context, my computer is a windows 7 x64.
Thank you for your time and your responses!
Paul
Well I haven't heard from anyone yet and I've been still digging around. I might know why my computer doesn't discover my phone. I think it has to do with the charging port. It makes sense since that is where the connection lies. And I already know that my cords are all good as well as my computers. But anyways, I have bought a replacement part and hopefully that fixes the issue.
I'll post my results as soon as I replace the part. Wish me luck!!
Paul

Ematic EGS-102 stuck on logo screen; computer doesn't see it when connected with USB

Hello,
I have a rooted Ematic EGS-102. Following some instructions to swap my internal sd with the external one (as the memory where the apps' data get downloaded to was only 500MBs), I believe I have typed something incorrectly inside the vold.fstab file, because after rebooting my tablet it's forever stuck on the logo screen. This is my first android tablet so please bear with me. The solution that comes to mind is to open the root files by some program on my PC and edit the vold.fstab file back (I even have a backed up version of it from a few weeks earlier), or even flash a new ROM. Now, the problem is, my computer cannot see my tablet when I connect it through USB. At all. Back before when the tablet was fine, I could use the USB to transfer files to and from my computer, but after I killed my tablet, my computer doesn't even make the sound which indicates that a USB device has been connected.
I have tried changing the USB cable and the port where I connect it to (never mind that the same cable and port work with other devices), to no avail. Having given up on the USB method working, I decided to follow some instructions on installing a custom ROM that has worked on EGS-004, and according to the one who posted that, would work on other variants such as EGS-102. Basically It was steps to installing the ROM from the external card through Recovery mode, which I followed thoroughly to no avail. The tablet still gets stuck on the "ematic" logo start screen.
I've noticed that in the Device Manager my tablet is displayed as "USB Device(VID_1f3a_PID_efe8)" with a yellow triangle mark indicating that it's not working properly (code 10). I tried searching that error code and trying all the solutions I found to no avail, including updating the driver (just refuses to update and keeps telling me that my driver is up to date.)
Sadly all the other methods that would have a decent shot at working (Root explorer on PC, android recovery program, even a flash EGS-004 firmware method on ematic's website) requires USB. I'm out of solutions, and unless I can get the USB to work somehow, or find out why the ROM method didn't work, my tablet would officially be dead. I'm utterly miserable that such a stupid mistake on my part ruined my tablet, and I have no way of buying another (broke student here) or returning it (out of warranty and I'm pretty sure I voided it anyway). I would absolutely appreciate any help, and thanks in advance.
Edit: It's stuck on logo screen, not a bootloop. I'm terribly sorry for this confusion, my head isn't straight right now.
Still haven't found a solution :/

Cubot x9 not powering on or showing signs of activity!

Hello! So a while ago I bought a Cubot x9 and it was a really good phone. Recently i haven't been able to do anything with it due too I tried to root it and it bugged out so I reinstalled the rom on it and it fixed it for a while but now it won't even show that it's powering on or even charging. I tried connecting it too my pc to see if i could use odin too reset it but it's not displaying on any of the com ports. I'm curious if theres anything i can do for it. I have a newer and better phone now so i dont really need it but it would be nice to try to fix it or(In the case of my tablet) Fully modify it so nothing on it is stock on it.
Cloak2131 said:
Hello! So a while ago I bought a Cubot x9 and it was a really good phone. Recently i haven't been able to do anything with it due too I tried to root it and it bugged out so I reinstalled the rom on it and it fixed it for a while but now it won't even show that it's powering on or even charging. I tried connecting it too my pc to see if i could use odin too reset it but it's not displaying on any of the com ports. I'm curious if theres anything i can do for it. I have a newer and better phone now so i dont really need it but it would be nice to try to fix it or(In the case of my tablet) Fully modify it so nothing on it is stock on it.
Click to expand...
Click to collapse
For your information, odin is for Samsung devices only, hence why it wont recognize you because you are not in download mode. If adb or fastboot recognizes it you can manually flash stock ROM, that is, if you have adb. And also, does your phones display turn on or not?

Categories

Resources