Currently having an issue with my Droid R2D2 (rooted), I was installing a new battery mod for my phone, restarted the status bar and all worked out fine. I went to do a reboot to make sure it all worked out and BOOM, phone became stuck at Moto Logo for the past 20 mins when I tried to restart it.
I can't seem to get Bootloader to load up even with the phone plugged into the computer itself, but it will go into recovery mode after holding the X button on keyboard, but search key wont bring up any luck either.
I can't seem to find my back-ups either before I installed the battery logo, ROM Manager would back-up my stock R2D2 ROM but it wouldn't appear on the list of possible recoveries before the phone went into deep sleep.
Only thing that I've found to fix this is to just SBF_Flash back to stock and start over.
Related
Hi, first time modding and I've come up with a problem.
Baisically what's wrong now:
Phone is stuck at large green android logo when I turn on the phone.
Can't boot into Cyanogen
Can't get Clockworkmod to open
Phone only turns off with a battery pull
How I got the phone to this point:
Followed the instructions at wiki.cyanogen
(Backed up with titanium backup pro)
The first time I installed the mod I got stuck in a boot loop. But I fixed this by deleting data and cache in Clockworkmod and going through the steps again.
The phone and it's new mod seemed to work. I installed the google apps.zip, via CLockwork, still fine.
Then I tried to reinstall apps from Titainium Backup.
Some of these went well, but I started to get 'com.google.process.gapps' stopped working force close notifications.
I rebooted to see if that would make them stop.
But I got stuck in a boot loop of the Cyanogen animated logo, where it would boot, show me the unlock screen, I would unlock it, get another 'com.google.process.gapps' message and the phone would then freeze and reboot. The sequence then continued.
I tried battery pulling and tried to boot into Clockwork by holding down Menu Up and Power. But not after a while it just shows the green android logo. HELP.
I didn't read all!
So...
this problem is easy fix!
I spent 3 Hours with my blade to get my Blade II to work!
you have same problem which some other has posted somewhere here...
search on google or on Modaco: ZTE Blade TPT GEN1 or GEN2...
follow instructions!
now Blade II needs to work!
http://android.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/
After a year of playing with Galaxy S3 I got bored with constant flashing and well, I never got used to onscreen keyboard.
I wanted a phone that will just work and decided to go for a Droid Pro+. Device was form Germany as there is no official distribution in Poland. It worked like a charm for two weeks till just now.
While playing with it (changing ringtones and stuff) I got several messages about services failing - com.service.usb, com.service.google, etc.) As it happened before (but only com.service.usb) I restarted it - in a normal way - power button and then Reboot. It rebooted and after that got stuck on M logo.
The firmware was as stock as it could be. No modifications were made. What's strange, the device can't be hard resetted. I can hold the power button for several minutes and it won't turn off.
Recovery mode works, but wiping does not help. Fastboot also works, but RSD Lite shows N/A in every column of Device info. I flashed GB 2.3.6 (5.5.1Q-110_ELW-TA-36-65-release-keys-signed.Retail-en-GB.tar) found on XDA. The rom itself should be OK, as no functionality was lost (recovery and fastboot), but the device still hangs on the boot logo. Device info is still N/A.
Could it be a hardware malfunction or is there something else I could try? Warranty is probably not an option since as i mentioned there is no official distribution in Poland. Any help would be appreciated since I'm out of ideas by now... Also, does anyone know if the battery is charged when in Recovery or fastboot mode? Connecting to a charger ends up on the M logo. And because very few people in Poland have Moto devices I have no other way to recharge the battery.
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
My wife killed her phone. She had romboons 30 installed with dorimanx 4.2 kernel and blastagators twrp 2.8.7.1
She then started installing other roms and now the phone is stuck at lg logo bootloop. I tried every button combination to get into recovery but notting
Tried download mode but it says rooted and freezes.
I am running linux lite 2.4 and am not that experienced at it.
My wife knows that its her own fault that the phone doesnt work anymore but is there a way to get it back to life again?
Thanks a lot for your help
Edit: Been trying to get into recovery mode for the past 3 hours. tried all combinations but notting. I only am able to get into a screen for hardware buttons. Download mode doesnt work either. phone is detected by linux when i hook it up.
I think the wife finally completely killed the poor phone It does not want to go into recovery
Well will mean that i will have to learn how to live without a phone cause she already took mine as replacement.
I have been able to get into recovery after several hours and installed new rom. So this can be closed and if you want even be deleted
Hi, I replaced the battery in my Moto X Pure edition and when I tried to power it on it just kept restarting. The phone would not power on before the battery was replaced and was basically bricked. Anyway, I can't get it to boot into recovery mode or show the exclamation point. I can open the bootloader but it seems to just ignore it and after I exit it nothing changes. I don't know what to do. If any of you know please help!
P.S. I never reflashed the ROM or anything everything is stock.
Similar issue
I am unable to get TWRP to load on my phone, I woke up two days ago and had seemingly powered off overnight despite it being on a charger and the notification light was still on (I'm using lineageOS 14.1 so the light under speaker grill is functional) after powering the phone on I started getting Google play services stopped working messages. Trying to fix it I cleared the cache for the app and rebooted, the issue persisted so I decided to load a back up through TWRP but it will not load for me. It just loops the loading screen for TWRP. Any useful ideas or insights would be greatly appreciated.