Help with bootloop on EGP010 - Android Q&A, Help & Troubleshooting

Help with bootloop on EGP010 - Android Q&A, Help & Troubleshooting

I'm having trouble with a bootloop issue on an ematic EGP010 (an apparently unpopular device - I am unable to find much detail at all about it
I've posted a video to show what is happening here:
As you can see I get the boot logo, then it appears to attempt to install an update, then it restarts and repeats the process.
I've attempted to get into a system recovery but every key combination I try doesn't work:
-vol up + pwr causes it to shut off as soon as the logo shows up
-vol down + pwr does nothing to the device itself, but will allow a computer to recoginze it via USB
I can get the computer to recognize the device, but because the EGP010 is cheap an unpopuplar, I was not able to find specific drivers for it. I was able to get the generic drivers installed, and its listed as "This device is working properly" however no devices are listed when I run "adb devices"
I'm at a loss for what to try next. Any suggestions for next steps or other things to try?

Related

[Q] Fastbooting and the Kyocera Echo?

I have a Kyocera Echo which has decided to forever loop in the start up instead of doing anything and since I can't hold power and volume down to factory restart I thought it was dusted
but if i read this thread correctly,
HTML:
http://forum.xda-developers.com/showthread.php?t=1129735
I might be able to do a hard rest through fastboot.
I have installed, all the drivers from the Kyocera website, I have the sdk, I know where to go into command prompt, etc. But my phone is not being detected by the fastboot tool. when I type Fastboot devices, I get nothing, not even the ? mark they mentioned and it just hangs on when I do fastboot -w saying it's waiting for the the device.
Even though its looping my computer will detect the phone and when I have placed it in what i think is download mood (power + plus both volume buttons) it has detected the right drivers to install and though it loops will kind of pop up the phone on my computer.
But when I put it it in what I guess is fastboot mode (power + volume up) Window's says it found new hardware, "Android," just plain android. I tried to direct to install the usb drivers from the Android-sdk/extras/ folder, but that doesn't work and Window is not finding anything automatically.
I assume the problem is that I need to find the right driver for the "Android," but I can't seem to figure what driver that is.
Or is it that my phone is not rooted, they didn't mention anything in the thread about needing it, but I'll admit I'm uncertain about that, but I assume I can't root it now anyhow or if that would even help.

Any help please?

Is my Atrix 4G hard bricked?

I tried unlocking the bootloader an atrix that was given to me about a month ago, and it had 3.4.6 (or something like that) and I couldn't find an unlocker for that version so I tried the one for the previous version, which failed at some point in the process and now it just boots to "Failed to boot 1". I've been trying every method I can find to try to fix this, I even bought the little red adapter to change any cable into a dev cable, and i know it works because if I power it on with the volume up key pressed it says "power reason: factory cable".
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
I tried it on several different computers with the same results.
Is this a hard brick? Any advice would be very much appreciated.

Did you install the windows drivers?

Scrub13 said:
Did you install the windows drivers?
Click to expand...
Click to collapse
Yea. I did.

Tekzel said:
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
Click to expand...
Click to collapse
If you power on while pressing volume-up, it should go straight to fastboot since it's the first option available. What happens when you reboot with volume-down?
Also, if the phone says "Starting fastboot protocol support" it's not hard-bricked, even if it's seriously screwed up at the moment. If it says "Entering NVFlash recovery mode," that's the point where it's toast (from the user end anyway).
With your phone in fastboot, does your computer recognize either of the SD cards? Have you re-downloaded the Motorola drivers, just to be sure? If "fastboot devices" comes back blank, then either the phone isn't truly in fastboot mode or the drivers aren't up to date.

Tekzel said:
I tried unlocking the bootloader an atrix that was given to me about a month ago, and it had 3.4.6 (or something like that) and I couldn't find an unlocker for that version so I tried the one for the previous version, which failed at some point in the process and now it just boots to "Failed to boot 1". I've been trying every method I can find to try to fix this, I even bought the little red adapter to change any cable into a dev cable, and i know it works because if I power it on with the volume up key pressed it says "power reason: factory cable".
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
I tried it on several different computers with the same results.
Is this a hard brick? Any advice would be very much appreciated.
Click to expand...
Click to collapse
This isn't a hard brick:good:
when you boot your phone don't hold down the volume button, then hit the volume down button right when the menu comes up. Then just cycle through and hit RSD and that should do it
here is a thread specifically talking about fixing this issue http://forum.xda-developers.com/showthread.php?t=1528729
also, in the future I would recommend using this tool for unlocking and rooting your phone, it's no sweat, and this tool even has an automatic fix for your current problem. if I'm not mistaken..I'm not totally sure
here is the thread where the automatic BL unlocker came from, though the link there is broken http://forum.xda-developers.com/showthread.php?t=1182871

sheeparecurious said:
If you power on while pressing volume-up, it should go straight to fastboot since it's the first option available. What happens when you reboot with volume-down?
Also, if the phone says "Starting fastboot protocol support" it's not hard-bricked, even if it's seriously screwed up at the moment. If it says "Entering NVFlash recovery mode," that's the point where it's toast (from the user end anyway).
With your phone in fastboot, does your computer recognize either of the SD cards? Have you re-downloaded the Motorola drivers, just to be sure? If "fastboot devices" comes back blank, then either the phone isn't truly in fastboot mode or the drivers aren't up to date.
Click to expand...
Click to collapse
Powered on with volume-up it goes to:
Failed to boot 1
PwrReason: FACTORY_CABLE
Starting Fastboot protocol support
With power down (which I didn't know about), I see something flash on the screen really fast and then it goes blank. The computer recognizes it, but it still says "unknown device".
I recently downloaded the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
This machine is Windows 8, but I also tried it on a Windows 7 machine with the same result.
With the phone in fastboot, as above, it the computer doesn't see the internal storage, but it doesn't have an SD card in it, I will put one in it today and see what happens.
I've downloaded the above software fresh on each of the three machines I have tried this on, two Windows 8 machines, and one Windows 7.
Thanks for the suggestions, I really appreciate it.

thewarhawk said:
This isn't a hard brick:good:
when you boot your phone don't hold down the volume button, then hit the volume down button right when the menu comes up. Then just cycle through and hit RSD and that should do it
here is a thread specifically talking about fixing this issue http://forum.xda-developers.com/showthread.php?t=1528729
also, in the future I would recommend using this tool for unlocking and rooting your phone, it's no sweat, and this tool even has an automatic fix for your current problem. if I'm not mistaken..I'm not totally sure
here is the thread where the automatic BL unlocker came from, though the link there is broken http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
Great, I'm glad to know it's not hard bricked!
When I boot the phone with nothing pressed, it goes straight to a single line:
Failed to boot 1
I never get the menu. Also, just tried some presses of the button as it was booting up and found that I don't need to hold either power up or down. If I power it on, and when it stops at failed to boot 1, I can press the power up once and it goes to the fastboot protocol support screen or power down and the screen goes blank.
I'll check out the links you posted, thanks!

Failed to boot 1 should be the same as rsd mode.

Tekzel said:
Great, I'm glad to know it's not hard bricked!
When I boot the phone with nothing pressed, it goes straight to a single line:
Failed to boot 1
I never get the menu. Also, just tried some presses of the button as it was booting up and found that I don't need to hold either power up or down. If I power it on, and when it stops at failed to boot 1, I can press the power up once and it goes to the fastboot protocol support screen or power down and the screen goes blank.
I'll check out the links you posted, thanks!
Click to expand...
Click to collapse
As I understood you wanted to unlock bootloader and failed. So I suggest you to try automatized bootloader unlock tool(@thewarhawk give you link) and then fix the "Failed to boot 1" because if you failed something now you probably hard brick your device I have experience whit one of my atrix. So I in your situation will do that:
1) manually in fastboot (better in win7) fastboot oem unlock (I just doest know command for unique device id in fastboot so it need you to search in xda)
2) then flash fully system partition whit fastboot
3) and then if device doesn't boot correctly try this http://forum.xda-developers.com/showthread.php?t=1528729 as you early said @thewarhawk

Hi, the problem is the windows 8 drivers,First download this. Then you need to boot the phone in fastboot mode, then go in device manager then you will see fastboot with an exclamation mark. Right click on it and select update drivers. Next do search for a driver on my computer, Then you do choose from a drivers list (or something along those lines). Select ADB interface -> Motorola -> Mot composite ADB interface. You will get a warning, say yes anyway then bang... your phone is detected by adb and fastboot.

[Q] Interrupted flashing process

Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.

Zenfone 5 A502CG Unable to enter fastboot/droidboot

Hi all,
I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "A502CG unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
If someone has same problem with me and solve this to recover the firmware to its origin, kindly share. I believe there is someone who are same as my situation here.
Hope for help/guide. Thanks

liey87 said:
Hi all,
I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "A502CG unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
If someone has same problem with me and solve this to recover the firmware to its origin, kindly share. I believe there is someone who are same as my situation here.
Hope for help/guide. Thanks
Click to expand...
Click to collapse
Kindly help

liey87 said:
Kindly help
Click to expand...
Click to collapse
My zenfone 5 lite(A502CG) is hard bricked and
I can't enter into droidboot or sideload it is stuck at the "Intel inside" logo
can anyone please help .
Since I can't find xfstk files for a502cg I am unable to flash it with xfsk & i don't know how to extract the files for xfstk from the firmware.zip for a502cg .
Any help will be thankfull

Possible bricked phone, new to Elephone, familiar with Android rooting and ROMs etc.

Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.

holygoatofsteel said:
Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.
Click to expand...
Click to collapse
Fixed it, but I'll leave this up for anyone thinking they might have the same problem. I fixed this by flashing the stock ROM again, but with one key difference. Ensure you install all appropriate drivers, and then when you hit download, plug the phone in and attempt to put it into recovery mode. This will open the port just long enough for the flash tool to keep it open, and it will flash as usual.

Better Mobile App

welcome