Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.
Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Kal5el said:
Hey guys. I've been around since the OG Droid, and I've never posted because I've been able to find the information by searching usually. But now I have a problem that I haven't been able to solve, and I was hoping someone could puzzle it out.
Right now I have a Nexus 5. I got it at launch and it's been perfect, with none of the issues others have had that required RMA. I unlocked the bootloader when I got it and loaded TWRP and rooted, but left it stock beyond that. About a week or so ago, I rebooted into recovery. While I was there, out of habit, I cleared cache and Dalvik. The thing is, it took 5-10 minutes to clear, and during that time I remembered that i had ART enabled. Now, I know others have had trouble with TWRP messing them up on a wipe, but this is where it gets interesting.
I rebooted when TWRP finished wiping. The boot animation spins the balls in once, then on the second time, there is color bleed forming a line across screen on the top and bottom of the boot animation. Again it spins, and it's fine, and then it does it again. Every second spin of the boot animation.
Eventually it booted in and I used the phone. An hour later, I got some force closes, it locked up, and then it rebooted into a bootloop. With the boot animation bleeding every second spin. When I got sick of that, I started trying to fix it by flashing factory images, locking and unlocking bootloader, fastboot erasing cache, userdata and system, fastboot formatting cache, userdata and system, trying TWRP again and wiping, trying CWM and wiping, wiping in stock recovery, anything and everything. I don't know how this is lasting past flashing factory images after an erase or a format, but every time I try to boot my Nexus 5, it either gets caught in a bootloop with varying amounts of boot animation graphics glitches, or it boots into Android and then after I spend a few hours setting up again, it will randomly hit me with graphical glitches in the OS or reboot, and then I'm stuck in the exact same boot loop.
Does anyone have any ideas that I haven't tried? I've done all of these multiple times, checked MD5's and SHA's, used different downloads of factory images, applied or not applied the update to 4.4.1, and nothing seems to work. Sometimes it's right away, sometimes it takes hours or even a day, but eventually I end up with force closes and a boot loop with bleeding graphics.
Thanks in advance for any possible help. I'll sit here quietly and wait for someone to tell me to just flash the factory image.
Click to expand...
Click to collapse
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Reason I say this is because the only three reasons I can think of are 1) app you have installed doesn't play nicely with stock Kitkat 2) something borked your EFS partition 3) your GPU is screwed.
thattypicalnerd said:
What kind of FC's? Random apps you have on your phone or specific apps? Also, do you have any kinds of system mods or complete stock? Do the weird graphical glitches on the bootanimation happen on the boot right after you flash the factory images? Or subsequent boots after the OS graphical glitches start?
As for right now, try running a factory image without installing anything apart from apps that come stock (don't install anything from the Play Store). If you can't live without some apps, try keeping them to the top 100 downloaded apps (ie. ones that have huge userbases and most definitely do not cause system issues).
Click to expand...
Click to collapse
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
"One of the good ones"? You clearly don't have "one of the good ones".
I think this doesn't have anything to do with anything you might have done wrong, I think the phone needs to be RMA...can you relock it?
Kal5el said:
Thanks for the reply.
The force closes are Google Search, or other Google stuff. I had the build.prop edited for 400 LCD density before this all started, but I haven't changed it back on subsequent flashes. So it is completely stock, not even rooted, and sometimes not even a custom recovery. 100% stock. The glitches happen on a clean flash from factory images, immediately on first boot. They get worse on subsequent boots after OS glitches start. In terms of what they look like, they are red or blue or white. Never other colors. On boot, they form dash lines bordering the boot animation. On the OS, they form lines above the default Google folder or vertical or horizontal lines mostly.
I've tried running just factory image with nothing installed except stock. I get the same results. Either I get glitches and force closes followed by a reboot right away, or it starts within a few hours of booting. If it reboots and gets back to OS without boot looping, the glitches in OS will be worse, and it will reboot into boot loops within a few minutes.
I still have my GNex, so I can afford to keep this phone stock until I resolve this. But it is basically unusable, and I don't want to RMA since I seem to have gotten one of the good ones, you know? This has to be a software problem, possibly a partition problem caused by TWRP. I was paying close attention to Metal_Head's thread, but he resolved his problems by wiping in TWRP, and that hasn't worked for me.
Click to expand...
Click to collapse
HIGHLY doubt its a software issue at this point. Considering your phone is completely stock, the crashes are unrelated to the phone app, that takes out app interference/EFS issues. Also, considering it happens on first boot, 99.99% sure it's hardware. Relock and send it back to Google. If you really want to, try CWM and see if that does anything, but I doubt it. In my experience, CWM causes more trouble than TWRP. Computers are complex little devices, it could be a bad CPU that has a small sector of the transistors not working or something like that. Bad RAM even?
So you guys think it's a hardware issue? It's possible, I guess. But it started after TWRP messed up on wiping Dalvik, so I figured it was a partition problem. I can relock it, I'll just have to reset the tamper flag. Was really hoping this was a fixable software problem.
I think you don't have the latest TWRP, which causes some issues on cache partition, and takes ages to wipe
2.6.3.4 is the latest
I'm running 2.6.3.4 TWRP. Thanks for the suggestion though.
Okay, just posting the solution in case this happens to anyone else. Wiping in stock recovery, CWM, or TWRP didn't work. Fastboot erase, fastboot format, and fastboot oem lock/unlock didn't work. Factory images didn't work, with multiple downloads and md5 checking. What ended up somehow fixing it after trying everything I could think of was pretty simple.
In the Android OS, in settings, under backup and reset, I clicked reset. That's it. So far, graphical glitches gone. It's been almost 2 days, far longer than it's gone without a bootloop since it started these shenanigans.
No idea why recovery and fastboot and all that business didn't work. Just posting the solution for those who come after.
Funny thing is the reset in android settings uses recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I know, I can't figure it out. It rebooted into recovery exactly like I had done before, and I watched the robot's polygon spin exactly like I had done 20 times. I can't explain why it worked.
Same thing that happened to me. What I finally got done to resolve it was:
1) Completely wiped the device and I mean all partitions so there is no OS and no internal files
2) Get the refresh zip file from Google to flash the device back to stock 4.4 while in the bootloader
3) Boot up, skip the setup, place CM11 files on the phone, then turn it off, reboot to bootloader
4) Flash CWM with fastboot
5) Boot to recovery
6) Do a factory reset
7) Wipe cache
8) Install CM11 & gapps
9) Wipe cache again
10) Reboot
So far for me no more issues. I did the same steps as you when mine started acting up. Now cache wipes super fast as expected no more reboots.
Sent from my Nexus 5 using xda app-developers app
I was wrong. The reset fixed it for 2 days or so, then it started showing the same problems. Graphical glitches and rebooting. I'm RMAing it. This thread can be ignored from now on. Further discussion of this particular problem can go in ssconceptz's thread linked below.
http://forum.xda-developers.com/showthread.php?t=2547863
That sucks. Mine works great now. I'll remove the first method.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 11:41 PM ---------- Previous post was at 11:41 PM ----------
Maybe you could try the method I show before RMA?
Sent from my Nexus 5 using xda app-developers app