Hey,
i've buyed a used Milestone for christmas, and it was modded with cyanogenmod, but i was kinda laggy. So i decided to wipe and clear it as described here. But now, my milestone won't boot anymore, it's booting as normal, but at the screen where it show's "android", it is booting, the screen turns black and starts again at the "android" screen. Can someone help me fix this problem?
Sure you do "3 wipes" after flashing? boot to recovery and wipe data/factory reset if you didn't. If you did... Try another rom or flash the rom again.
I got a Milestone that is stuck at the Bootloader 30.04 screen with Err:A5,70,70,00,1F
Mem_Map Blank
Service Req'd
Now I am a TRUE NOOB yes
but I have RSD Lite and the phone connects it even install/flashes the VRZ_MB810_2.3.34_1FF_01.sbf and says it will restart but restarts right back to the bootloader,
I have tried reading on other threads and forums, but nothing ever answers my question,,,,what am I missing? is it bricked?
NightDragon666 said:
Hey,
i've buyed a used Milestone for christmas, and it was modded with cyanogenmod, but i was kinda laggy. So i decided to wipe and clear it as described here. But now, my milestone won't boot anymore, it's booting as normal, but at the screen where it show's "android", it is booting, the screen turns black and starts again at the "android" screen. Can someone help me fix this problem?
Click to expand...
Click to collapse
I had the absolutely same issue. What I did is simply flashed the sbf again then wipe and it works now!
Hi, I have a Moto X with 4.4.4 original rom (eu.fr) on ART, today I was updating Monument Valley when the phone turned off and got stuck on "M logo" boot screen.
I tried to wipe the cache partition through recovery but it got stuck there too.
Any other way, before trying factory reset?
...Nope, had to hard reset... Luckily it worked, at least for now. Hope not to see the same error on further reboots.
Kind advice: do not install Momument Valley under ART.
my moto g2 xt1068 running on stock android L 5.02, suddenly got stuck in a boot loop and was unable to boot. I tried all the recovery options including a factory reset, but in vain. Finally i downgraded to stock kitkat 4.4.4 after unlocking the bootloader. Now it starts up and runs fine until i try and log into my google account or install a few apps, in which case it goes into boot loop again ..... i am suspecting a few bad blocks in the internal memory....can anybody please help me???
Moto G XT1068 is not booting
After rooting i tried for CM14 ROM with Nought , after wiping system, data , cache when i tried for CM14 it got failed then i restore back up and then when i try to boot it stuck @ bootloader unlock warning and not booting as well as not shutting down.
Please anyone can help.
sorry if there is any thread for this already present.
MaxD
So i've got this old XT1064 that i ended up passing down to my brother, but he managed to brick it a while ago. A few days back my friend's phone got stolen, so i decided to try and fix this old brick that was sitting in my shelf. Its the Canadian version XT1064. It used to have a custom rom when it got bricked (no clue wich one, long ago.)
Anyways, the problem is; Its constantly in the booting animation. Its not rebooting over and over as it usually happens in a bootloop. The animation just never ends. It doesn't restart, doesn't start into system etc. The only way to get out of the booting animation or powering it off is by hard rebooting it (holding power for 10 secs.)
I've tried a number of stock roms of different versions for the XT1064 and absolutely nothing seems to fix it.. When i try flashing a rom with fastboot, everything shows up as "OKAY [ #.###s]", yet when i reboot it gets to the same animation as before..
Here's a youtube video of the booting animation: /watch?v=HoSds0LULH4
My friend has no money to buy a new phone for a few months and i really want to help her out.
Thanks in advance!
I presume you cleared all the caches and user data and tried again.
Just installing ROM's won't clear caches, you need to use the mfastboot erase command to clear them.
I my case, I had a bootloop, which was not fixed by just flashing a stock ROM.
I had to erase all the caches etc as well