Hello everybody.
Although I've been following the forum since longtime ago, this is my first post. I hope this is the beginning of a more active and regular participation . Once I've introduced myself, I'll explain my problem:
I've got a Huawei U8110 from Movistar which seems to be in a boot loop as it gets stuck at the Android logo screen. I got it from eBay and it was already in an unusable state. I knew that but I thought it was a good opportunity to make my first steps in this amazing world.
After surfing the Internet for days and reading tons of posts to document myself, I decided re-flash the phone . I tried several stock ROMs (Yoigo, T-Mobile and again Movistar) and I was able to flash them without problems from an SD card. However, I got always the same result with all of them, always stuck at the Android logo. For info, when I bought the phone, it had the original stock ROM from Movistar.
As I've said, I've got no problems to flash the stock ROMs from a SD card. I can also enter into the bootloader mode. Nevertheless, I cannot boot into the recovery mode because after pressing the keys combination "Vol up + Call + Power On", I get into a purple / magenta screen where I can do nothing.
I've tried to root the phone and flash a custom recovery from bootloader mode. Through the rooting process, I can flash the image OK with fastboot tool but at the reboot time, I come again over the boot loop at the Android logo. Same thing for the custom recovery… I get to flash de recovery image but if I try to boot into the recovery mode, I get again de purple / magenta screen.
I'm a bit lost and I don't know what else can I do… Any help would be really appreciated.
Thanks in advance.
Regards.
EDIT:
I've forgotten to comment that if I enter "fastboot getvar all", the result is only "all:" without any variable output... Maybe the bootloader is corrupted?
you can try odin? find the pit and flash a new boot loader.
Related
Hi guys.
I tried to upgrade phone with the latest One Touch Upgrade app. During the upgrade process, app froze and stuck.
After this, it can't boot, stuck in the alcatel boot animation. Tried almost everything: nandroid restore via fastboot (2 or 3 different backups), flashing stock roms posted on forum, nothing worked. Only thing changed is that now it has T-mobile boot animation.
I got clockwork recovery but can't enter it in any way. I managed somehow to enter it once from power off state but accidentally i didn't have any backup image on sd then. I can't manage to enter it again, no matter which buttons i press with power button.
I would be really grateful if someone know any solution for my problem.
same problem here with a alcatel one touch 908f, does anyone knows where i can find the stock firmwares?
like an ftp or something similar
best regards
quimsatanic
hi people ;P
I tried to upgrade phone with the latest One Touch Upgrade app. During the upgrade process, app froze and stuck.
After this, it can't boot, stuck in the alcatel boot animation. Tried almost everything: nandroid restore via fastboot (2 or 3 different backups), flashing stock roms posted on forum, nothing worked. Only thing changed is that now it has T-mobile boot animation.
I got clockwork recovery but can't enter it in any way. I managed somehow to enter it once from power off state but accidentally i didn't have any backup image on sd then. I can't manage to enter it again, no matter which buttons i press with power button.
I would be really grateful if someone know any solution for my problem.
I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
Hi, people. I hope you can help me.
My problem is that my rooted Nexus 7 (2012) with 3G and kitkat Stock Android suddenly turned into so called brick state. Only Google logo was appearing during the boot, and that will last forever. Then, just for interest, I tried to enter into the recovery mode (Clockwork Recovery v6.0.4.3 for tilapia), but the device did not go into it. The logo of CWM appeared in the middle of the screen and then the device reboots automatically showing the Google logo screen for several seconds and then going into recovery mode with the CWM logo appearing on the centre of the screen, and then reboot again. This recovery bootloop lasts forever or till the battery runs out. I tried to use
Code:
adb devices
and
Code:
fastboot devices
on my nexus 4, everythings works fine (meaning drivers are installed correclty). But
Code:
fastboot devices
for the nexus 7 outputs into
Code:
- waiting for device -
I tried to force the battery to run out and then tried to go into fastboot, but that did not help, the recovery bootloop appeared on its own again. Please, help me, I don't know what to do.
EDIT. I tried to pull out the battery for a half day (disconnect battery connectors) in hope that this will somehow reset the boot options, but this did not help.
Any thoughts?
Also, if the thread is not in the appropriate branch of the forum, please, let me know, probably at correct location I will find more help. Thanks.
EDIT2. I solved the problem by trying to enter the bootloader mode via adb. But to enter bootloader required a liitle bit of humoristic approach. I was pressing UP then ENTER to enter fastboot mode via termianl (#adb reboot-bootloader) for 5 to 10 minutes. When I managed to enter the fastboot, I flashed TWRP recovery for tilapia and the latest 5.1 Lopllipop But it seems there is a bug in the stock recovery because it does not work with NEXUS 7, the last two updates of Kitkat and Lollipop required to flash custom recovery, because the stock one did the bootloop on either Google logo or the animation of "beautiful" circles.
Thanks for reading, hope this might help someone.
from danik
Hi,
Glad to hear it solved
Good Luck!
Thread Closed.
Hello guys.
I apologize for making yet another "my phone is soft-bricked" thread, but I have been through at least 20-25 of the other threads, seemingly tried everything, and I can't get past my problem. Also, most of the other threads I saw are pretty old and not really active anymore. A few of the tools there can't even be downloaded anymore because the links are dead.
Anyway, here's my story.
I have a 16 GB US retail XT1032 that I bought mostly to give tech support to my parents, whom I also bought a 8GB each. Theirs, I left untouched. Mine, I unlocked bootloader and rooted right away. All went well for a long time.
My parents kept receiving OTA's and it took them all the way to Lollipop. Me being rooted, I got stuck in KitKat somewhere (I'm not 100% sure whether that was in 4.4.2 or 4.4.4), but since it wasn't my daily driver, I let it lie as stock rooted KitKat. Recently I wanted to go to Lollipop in order to keep seeing "the same things" as my parents, and I installed TWRP in preparation to flash a "stock enhanced" version of Lollipop. TWRP flashed fine but there was something funny all along: I could use ADB or a root app to boot into recovery from the ROM, but I could never manage to get the phone to go into recovery by booting into fastboot (vol down+power) and then choosing recovery. Screen would go black and recovery would never load.
So I copied a "stock" Lollipop image and booted into TWRP from the ROM and wiped everything and tried flashing the Lollipop ROM. It got stuck somewhere part way, and a few hours later there was no more progress.
Ever since then, I am stuck in fastboot. Fastboot seemingly works correctly, recently I was able to flash an OG animation to get rid of the nasty "your bootloader is unlocked" warning. I can flash recoveries (TWRP and/or CWM) without error on the phone or the computer, but when I try to then boot into recovery using the bootloader, I get stuck on the black screen and go nowhere.
As others in the various threads have commented, when I try to boot "normally", I get the boot animation and a vibration and then it gets stuck.
I have tried so many things by reading different threads I couldn't tell you anymore what all of them were. I've gotten errors about downgrading, I've gotten stuck in fastboot reason: "failed flash", I've gotten flashing errors about the size of recovery or boot or gpt. What I've never managed to do again is to boot into anything other than bootloader. No recovery and no ROM.
Could someone with a bit of experience please point me to some working links and/or when you have the time, help me look at a couple of logs or something that can help me figure out where my problem lies and how to get out of it? my daily driver phablet died a gruesome death and I wanted to go back to my trusty moto g, to no avail.
Thank you very much to whomever can help.
Ruben.
Try to reflash full stock firmware for your device according to your bootloader version. Hope it helps....
Try typing in fastboot devices