I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
atlcr said:
I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
Click to expand...
Click to collapse
Nevermind...apparently pressing vol. down when the LED flashes blue gets me to a boot menu. Pheww!
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Please ask all questions in Q&A. Thread moved there.
atlcr said:
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Click to expand...
Click to collapse
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
3ze said:
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
Click to expand...
Click to collapse
I don't think he has to flash the sbf, just flash gapps n wipe data n cache. also try dalvik cache
Sent from my MB526 using xda premium
You could simply install a new .zip from recovery. You could use the same CM10 11/28 or any other rom. This shoud work out for you.
I experienced the same with my Defy today and I installed a new CM 10 09/05 by Epsylon and it worked like a charm.
Thank you for the replies!
I had to flash it a hundred times to get it to work (I kept getting write access errors for cache folder). What ended up working was to wipe everything and install the 9/24 build. From there, I rebooted and installed (without wiping) the latest build along with the correct gapps. It works fantastically now! My phone is soo much more responsive and I'm loving CM10.
3ze had it right. I was using the latest gapps (12/2) instead of the "minimal" version in the quarx dir.
I haven't noticed a battery drain as has been widely reported here. In fact, it seems to be less of a drain now though that is likely due to the fact that I wiped everything and only installed apps I needed this time around. Tons of unnecessary apps could explain why my battery life was less before.
I have noticed a slight difference in reception now though. Places that used to be fine for connecting to the network (Tmobile) have now become less strong and frequently dropping out. I wonder if the signal strength could have been messed with?
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
ChameleonGeek said:
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
Click to expand...
Click to collapse
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
acejavelin said:
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
Click to expand...
Click to collapse
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
ChameleonGeek said:
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
Click to expand...
Click to collapse
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
acejavelin said:
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
Click to expand...
Click to collapse
I wait several times more than 10 minutes. I wipe data/cache after restart the phone. I found the solution in Google Forum: https://productforums.google.com/forum/#!topic/nexus/D2vKK9rLgh8[1-25-false]
You should only have to wipe /cache from recovery to get out of it. I believe wiping /data is unnecessary (so you can avoid losing your data if you are concerned.
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
Planterz said:
The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
Click to expand...
Click to collapse
How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.
Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %
After all , all this hardware mess up can be the consequence of a bad cm flash ?
the whole "optimizing app" thing is the OS rebuilding the cache.
Click to expand...
Click to collapse
I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
By any chance did you have your phone charging while flashing and booting up your ROM?
ChainFires Son said:
By any chance did you have your phone charging while flashing and booting up your ROM?
Click to expand...
Click to collapse
May be? But not the the first time
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Click to expand...
Click to collapse
Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...
Click to expand...
Click to collapse
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
shazR00t said:
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
Click to expand...
Click to collapse
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
I have the same thing for several month now.
Always thought it is the dying battery.
theminikiller said:
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
Click to expand...
Click to collapse
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
shazR00t said:
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Click to expand...
Click to collapse
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
theminikiller said:
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
Click to expand...
Click to collapse
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the image files. If you did that then u don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the images. If you did that then I don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
I m too facing the similar issues. Phone is getting turned off suddenly when not charging, on charging it is working fine. i have done factory reset and also done factory image reset to 5.1.0. i m still facing the same issues. I don't think so it is related to battery. if anyone have the solution then please let me know.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Try the very basic flash technique by double clicking the flash-all.bat. It's not the same as flashing the imgs one by one.
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
gautam.is.sharma said:
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
Click to expand...
Click to collapse
Ok so Battery was the problem!! Got it changed, phone working fine now. Thanx all!
Ok guys i confirm that this is a battery issue. I took it to the service center and the guy temporarily replaced battery to show me issue solved... But... there i saw another issue due to which i did not buy the battery. I saw half the touchscreen not working (including the navigation buttons ). The guy at the center told its a h/w issue and i would have to spend 7K on it so i left my phone dead for now. The Question is ... can this be a s/w issue.. or result of bad flash which can solve on reflashing ??
same problem with my nexus ,but one thing i noticed that the phone does not power off while in recovery...Any idea??
Hey Guys,
Running on marshmallow and the phone got rebooted an hung at optimizing apps says 1 of 1 . Quite some time and doesn't load into the main os. can some on advice ?
norysrinivas said:
Hey Guys,
Running on marshmallow and the phone got rebooted an hung at optimizing apps says 1 of 1 . Quite some time and doesn't load into the main os. can some on advice ?
Click to expand...
Click to collapse
Try wait little more time. I must wait 20 minutes but with another situation and it boot up. Give also information about rom and kernel which you use (build version too of both) will be easy.
Did a wipe cache partition which didn't help, later wiped to factory reset via recovery mode which helped to regain the device access.
How ever the device was running on stock android on android 6. It just rebooted automatically and never came up. Though as said about factory reset helped.
The optimization took me more than 30min. I just left it and did my jogging.
sent from OPO using Tapatalk
Updated!
Having tried many of the Custom roms around for the above phone some of which still had malware installed or were buggy I finally tried Lineage 14.1 based,"Mokee".
https://www.getdroidtips.com/mokee-os-doogee-x5-max-pro/
The flashing it took quite a long time to boot e.g around 15 mins plus but once installed acts as normal.
I can only speak for the 32 bit version as that is what my phone is.
All my fave apps are working.Battery life as normal if not better.No crashes.
Zip was checked with Avast anti-virus before moving to phone and then with Eset and Sophos Anti-virus/Anti-Malware once installed and found clean.
I've also monitored the rom using No-root Firewall over the week and nothing seems to be,"Calling home" that shouldn't.
Unless something changes this is the best clean Rom I've had on the phone.
HTH
Update:1 month on.
Still running fine.This ROM is a keeper for me
Hey, is the rom still running nicely? I got an "x5 pro" and think about flashing mookee but im still afraid:cyclops:
Double post glitch
mia.backkind said:
Hey, is the rom still running nicely? I got an "x5 pro" and think about flashing mookee but im still afraid:cyclops:
Click to expand...
Click to collapse
Yes.Totally rock solid and no problems to date
On the old original Malware infested Stock rom there must have been some kind of hidden timer as it was well behaved for around a year and the just after a year loads of ads started coming up even after Factory restores.
I tried loads of Malware/Anti-virus apps and it was only ESET security that found some hidden Trojans
https://play.google.com/store/apps/details?id=com.eset.ems2.gp&hl=en_GB
See this thread and my tip at the end to get the rom/s to flash,
https://forum.xda-developers.com/doogee-x5/how-to/doogee-x5-max-pro-root-recovery-ota-t3501830/page4
Puts me into a boot loop. Did you follow instructions to the letter? Because instructions include wiping system before flashing mokee (but wiping system removes the chinese recovery (power + volume(-)). After I restored nandroid backup, was still in a boot loop. Had to reflash stock firmware
Had to "cook" my own twrp recovery (none of the ones i found around worked) so maybe I will have to do the same with mokee, like merge it with stock rom to make it work?
I can't remember if I wiped it first
I think I just did a Factory Reset on the rom that was in before flashing with Mokee.
I had no trouble with the files from,
https://www.getdroidtips.com/mokee-os-doogee-x5-max-pro/
When you say Boot Loop do you mean you see the Mokee icon for a long time and it seems like it's doing nothing?
Also mine is the 32 bit version,not the 64 bit.
Also what I had to do at the end of this post,
https://forum.xda-developers.com/doogee-x5/how-to/doogee-x5-max-pro-root-recovery-ota-t3501830/page4
Boot loop like seeing the silver doogee logo. Then shuts down and restarts.
I got mine from the same place. Mine is 32 bit as well
There are 2 factory resets. The advanced reset, that the instructions mention, includes system wipe.
K3rb3r05 said:
Boot loop like seeing the silver doogee logo. Then shuts down and restarts.
I got mine from the same place. Mine is 32 bit as well
There are 2 factory resets. The advanced reset, that the instructions mention, includes system wipe.
Click to expand...
Click to collapse
I'd just try it the other way round from what you have tried.Without being there it's hard to get an idea.As I said it's been a few months now so I can't remember the exact sequence
Also it did take a long long time to first boot.Also try a Factory reset after the rom has flashed..