I had flashed my Motorola XT5 (Z71 variant) to CM 7.0.3 and installed CWM Recovery 2.5.1.3. Everything was going smoothly since 17-Oct-11. I used update-CM-7.0.3-Z71-signed.zip to updated using ROM Manager 4.5.0.1
I installed a few apps from the Market yesterday & they were working fine. Total apps installed = 128. I switched off the phone yesterday night.
This morning, when I switched it on, the Motorola Logo appeared followed by the CM7 Splash Screen (for a little while only). Then the screen went blank (slight glow in the background) and remained like that for several minutes. No buttons working incl. Power. Had to reset the phone by removing the battery.
Tried to boot into recovery by holding 'Camera+Vol Up+Power' buttons. Motorola Logo appears with "Enter recovery" written across on top. remains in this screen for several minutes. Had to again reset by removing battery.
Please Help! I can't seem to figure out what to do. I have a fairly good tech skills. Will follow steps if you're kind enough to guide me. Please.
Enter fastboot
Use it to install the custom recovery.
What is the key sequence to get into Fastboot on Motorola Xt502?
What should I do once I get into Fastboot?
Please guide!
TIA
It's
endcall vol down power
But you need some tools to install recovery.
Other solutions use [SUT] to refresh the firmware '*. nbo'
Hi, i just flashed this rom onto my phone, and it seemed like it worked. as it booted up, it showed the iho logo, and when to an android boot logo, in which it stopped in the middle of and has been stuck since. every few seconds it goes back to the iho screen, comes back to the splash and stays there. i have tried booting into recovery with no luck. PLEASE HELP!
try flashing a new recovery through your pc and revert to your previous rom
mellowdev.net
Hey, I know this is late reply but this is for anyone else who may run into this problem with any phone actually. Check out my site mellowdev.net and download Orange Tools, this allows adb commands etc in a very nice UI. You can then reboot into recovery in your situation. PM for more info. Thanks
EDIT: this is now called Mango Tools
I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english
Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.
Good evening, I have a LG P720h, it is rooted and has Thundersnap ROM. I had installed CWM 5.0, went into ROM Manager tries to update the CWM to install CyanogenMod 10.1, which was trying and gave error. Selected by ROM Manager to update CWM, only the version that is in Rom Manager is for the previous version of the Optimus 3D Max, Optimus 3D. I selected it "thinking" it would work. It did not work, installed CWM and rebooted to install the ROM. And after I rebooted it never left the screen with the LG logo, I can not enter the Recovery for a reset, and could enter once in download mode, but the LG Update gave the following message "The phone does not support software update. "I rebooted and it does not enter in more or download. Any idea what it might be?
I thank you.
Details: If I take the battery and put it initiates alone. If I stand holding the power button it turns off, and if I push the button once to turn on again (without being depressing) it binds.
I was able to successfully root this LG G3 D-852 device (after downgrading the stock android) and install TWRP and LineageOS. It was quite an effort to get there, but I was very happy to finally have it working. It worked for a few weeks, then I installed a new nightly build and the phone no longer will boot LineageOS (Note: I dont know that it is directly related to the update).
The phone will show the LG splash screen, then go dark, and then show it again. I can get to TWRP by holding volume down and power, letting go of power when the log shows, and then pressing it again. I tried to go in there and wipe and reinstall, but it still doesn't boot LineageOS anymore.
What am I missing? How can I debug what is happening?