I have flashed CM 11.0 M7 on phone #1. It worked for a few days (except clock which always got the "sorry clock has crashed" popup) then I suspect it discharged and now it's a brick. If I put it on the charger then the Motorola dual core screen comes up, if i press vol dn + power, it goes black for a few seconds then this logo comes back. I can't find another interaction which does anything at all.
Good think I have a spare Droid 4.
Phone #2 I tried to flash with Slim, Paranoid, CM -- all of them got stuck in a bootloader loop. All. I did a factory reset, wiped caches, wiped /system everything between them, of course. CM 10.2 stable is working without a hitch. Previously this phone had Eclipse on it, I think JB 4.1 based.
safestrap version?
verifying md5 check sum for rom and gapps?
using kitkat gapps?
rom slot 1, 2, or stock?
Sent from my DROIDX using Tapatalk
Related
I tried using miui android 2.3.3 - it worked.
The only other rom that works is the AOKP milestone 5.
So far:
BCM doesn't get past the X on boot.
Runny rom does get past the X but gets stuck at boot animation.
MIUI 4.0 goes into bootloop.
CM 7.1 does boot, but also has it's problems: when the screen turns off, if i try to wake the nexus using either the power button or the trackball wake, it remains black.
*** I'm using blackrose and always partition the hboot correctly for the specific rom.
I tried to format sd card, clear data, clear ext partition, clear cache, clear dalvik cache, always do a clean install, but everytime, theses roms fail me.
Now, I'm mostly curious about the booting issues. What could I do to fix them?
I've flashed CM 9.1 rom 2 weeks ago. Everything was perfect (well, ok camera app was a bit laggy). I installed it through CWM, like wiki says.
2 days ago, I was using phone as Navigation, and battery depleted to 0 (phone switched off). When I plugged it into a charger, battery charging animation was displayed, then phone switched off and so on (loop). Same situation is when I power on. CM logo endless loop.
Recovery doesn't start, download mode is working tho.
I checked different battery, same thing.
Is it software related problem ? Should I just flash phone again via ODIN or Heimdall?
I had something similar like this a few months ago because my nephew was pressing random buttons. I did indeed just reflash the phone again. Lucky for me I had a backup of my data so that fixed most of my problems.
Hope you figure it out,
Currently, I've flashed hardcore Kernel (CM wiki page) to flash CM9.1 rom.... it gives me Status 7 error (get.prop("ro.product.device")). Same with CM 10 Nightly.
Flashing Slim ICS gives me Status 0 error.
What should I do?
Hey just flash stock GB firmware via Odin then u r good to go...
Do post results
If my post helped, don't mind hitting THANKS
Yes it helped. Thanks.
Strange tho, stock 2.3.6 feels faster than CM9.1
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
vite0150 said:
Hi, in the past couple of days I have tried two 4.4.2 roms (cm 11 and ose)...
On both roms I get the black screen of dead when I woke up in the morning... (when this happens i have to press the volume down and power button to restart the phone)
Is this a common thing on 4.4 or this happens on all the custom roms? (I'm asking because on the rom thread this wasn't listed on the bugs)
Click to expand...
Click to collapse
This is not common at least not for CM11.
I've been running CM11 nightlies since they started to roll out, currently running 20/12 without issues.
I would recommend going to recovery, back up, and erase system, data, cache and dalvik, then flashing CM11 nightly to start clean.
I've been running CM11 and Validus13 ROMs since they became available and never had this issue.
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
I don't recall wiping Cache, Dalvik, or Data after installing 4.4 ROMs.
vite0150 said:
I used the cm11 12\26 (latest i think).. And did a full wipe (even the internal sd got wiped)...
Something i didn't do was wipe cache and dalvik after flashing the rom, does it is required
Click to expand...
Click to collapse
You should totally clean cache and dalvik when flashing new roms (CM usually does this by itself anyways). Make sure you're cleaning these, won't hurt at all anyways.
Ok, make a factory reset after flashing... Also i see in some roms that i gotta mount system and other things, i never did that (i didn't saw that in the instructions of the two roms that I've tried...)
Also I used for this couple of days the stock rom just to check that it wasn't a hardware problem... worked flawless...
Right now i'll try valadus... I'll let you know how it goes
Update: valadus gave me a lot of errors... Something like it couldn't write on storage/cwm... And when it was aborted it says that cache can't be mounted... So i ended up installing cm11 (the same that i flashed before)
You're running the latest CWM or Philz recovery?
Philz
It's strange because I'm running the latest CWM and I can install the latest Validus13, Cyanfox, CM11, and Probam without a problem.
Flashed probam last night, and it survived the night! Only thing I changed from before was wiping again after flashing...
Thanks for ur help
Update:
In the morning i connected the phone to the charger, and now i went to see if it was fully charged and surprise!!! It happened again!
Maybe is the charger cause I'm using a generic, but why it doesn't happen on stock rom?
At this moment i will just leave it stock and put it for sale, don't want to keep dealing with this...
Hi guys,
A couple days ago i noticed that on stock (att) rom i wasn't getting bsod but i do was getting reboots when charging the phone (i don't know how i didn't noticed it before)...
So maybe someone can tell what are the specs of the original power brick (amps, input, output) to find a similar one and see if that can solve the problem
Edit:
Nvm i found a samsung charger... Now everything is working flawless on OSE rom
Lost the keyboard lights on my droid 4 running ics 4.1.2 so I decided to upgrade to kitkat, which should have and did fix the problem. Upgraded to liquidsmooth 3.1 and the 4.4.4 gapps. Got most everything vital configured but noticed the unit started having frequent lockups after the first day. 3 days later the screen is unresponsive most of the time. Rebooting boots up to safestrap, but screen is still unresponsive to get into recovery mode so it continues on and boots up the liquidsmooth rom 4.4.4. Rom slot 0 is stock and liquidsmooth is in rom slot 1. So decided to factory reset using power and vol up/vol down keys and I can get into the firmware menu but selecting recovery results in a toes up droid, then a reboot into 4.4.4. Is there any other way to do a factory reset other than within the OS, which I can't seem to get into? Is it possible to adb into the device w/o usb debugging enabled or to do a reset remotely? Thanks in advance for any help offered.
manfone said:
Lost the keyboard lights on my droid 4 running ics 4.1.2 so I decided to upgrade to kitkat, which should have and did fix the problem. Upgraded to liquidsmooth 3.1 and the 4.4.4 gapps. Got most everything vital configured but noticed the unit started having frequent lockups after the first day. 3 days later the screen is unresponsive most of the time. Rebooting boots up to safestrap, but screen is still unresponsive to get into recovery mode so it continues on and boots up the liquidsmooth rom 4.4.4. Rom slot 0 is stock and liquidsmooth is in rom slot 1. So decided to factory reset using power and vol up/vol down keys and I can get into the firmware menu but selecting recovery results in a toes up droid, then a reboot into 4.4.4. Is there any other way to do a factory reset other than within the OS, which I can't seem to get into? Is it possible to adb into the device w/o usb debugging enabled or to do a reset remotely? Thanks in advance for any help offered.
Click to expand...
Click to collapse
All factory reset does in stock recovery, is wipe user data, and reset defaults.
It will not restore changes made with root, nor will it reset rom slots other than stock.
Use factory reset options in safestrap or
If you want to restore factory setting, flash firmware/xml with rsd lite.
Sent from my XT862 using Tapatalk
I recently rooted my droid turbo 32gb using sunshine root and kingroot. I successfully flashed Resurrection Remix Lollipop 5.1.1_r26.
However sometimes when the phone is idle in my pocket for awhile and i go to pull it out it is off. Also, it takes about a minute or so of pressing the power button to turn on. I also cleared the cache after flashing and reset everything. When i cleared the cache it seemed to work over night but turned off automatically during the day with more than sufficient battery life left. If anyone has any possible fixes, i would greatly appreciate it. Thanks in advance.
kernel problem
guccimcilroy said:
I recently rooted my droid turbo 32gb using sunshine root and kingroot. I successfully flashed Resurrection Remix Lollipop 5.1.1_r26.
However sometimes when the phone is idle in my pocket for awhile and i go to pull it out it is off. Also, it takes about a minute or so of pressing the power button to turn on. I also cleared the cache after flashing and reset everything. When i cleared the cache it seemed to work over night but turned off automatically during the day with more than sufficient battery life left. If anyone has any possible fixes, i would greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
I am not sure 100% but it may be kernel problem as support for xt1254 from stock kernel is added 3 days back in cm12.1 and RR is based of cm12.1
possible solution
1) try clean flash RR
2) if first does not solve flash CM12.1 (running very smooth without any bugs) until RR team update their ROM
It's probably RR rom. I had an issue with my Droid Ultra on dirty unicorns. Went back to cm 12 and it worked fine.
Sent from my XT1254 using Tapatalk
I am running resurrection remix fine on my droid turbo. For two days now I have had no issues. What I did is, in twrp, I did a factory reset, wiped dalvik and then cache. Then I flashed the ROM and then gapps. No more wipes. I booted it up from there and I've been stable ever since.
Thanks all. Went to cm 12. Now the GPS is the problem. Any fixes?
guccimcilroy said:
Thanks all. Went to cm 12. Now the GPS is the problem. Any fixes?
Click to expand...
Click to collapse
Yeah, freeze motogeofences in Titanium Backup and install TopNTP.
See this post:
http://forum.xda-developers.com/showpost.php?p=64109692&postcount=306
I was able to freeze georef then I installed TopNTP. however when it rebooted nothing changed. The GPS still didnt work. Do I have to flash again? Sorry I'm a noob
guccimcilroy said:
I was able to freeze georef then I installed TopNTP. however when it rebooted nothing changed. The GPS still didnt work. Do I have to flash again? Sorry I'm a noob
Click to expand...
Click to collapse
do you have "high accuracy" turned on?
Yeah. I turned it off when I froze it though
All you have to do is freeze georef then download TopNTP then reboot? Or am I missing a step
Do I have to go into stock to download topntp for it to work then flash cm 12.1 again?