Database Info

Another Bootloop Thread

com.google.gapps kept crashing so I decided to flash rayman's CM10 v6 rom over b5. Now I'm stuck on the CM10 logo. Cold boot doesn't work, Apx to cold boot doesn't work, and I can get back to recovery but flashing the rom again and/or wiping cache, wiping davlik and factory reset still didn't work.
EasyRecovery appeared to work at first but then at the stage where my device is supposed to reboot it started throwing me a 'device not found' error and it of course continued to be stuck in the bootloop.
What should I do?
EDlT:Easyflasher worked, but I lost all my data

Apparently the same issue
Well, apparently I'm having the same problem as Devour, I have the Team Rogue Recovery installed into my device and tried to install many different OS but always results into being stuck in the OS boot. I also wiped everything, cold boot but always end up with the OS boot stucked.
Does anyone can help?

Stuck in hard bootloop

Hi there,
I was running CM 12.1 very smooth on my XT897 4G with f2f filesystem on cache about half a year. After rebooting I was stuck in a bootloop. The phone freezes during bootlogo and reboots again. Wiping Dalvik and reflashed CM 12.1 leads to no success. So I successfully flashed
asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml
Via RSD 6.1.6. But the same error appears, the only difference is the bootlogo.
TWRP can't mount the partitions I tried every possible version of it. I'm able to flash fastboot and enter recovery.
Is there anything I can do to get my loved modded phone back? :crying:

I have the same issue what did you do to resolve it?

if iam right u need a backup zip and load it via the recovery.
if u not have your own try this: http://forum.xda-developers.com/showthread.php?t=2532620
did you try to reflash a cm rom?

Hard-bricked my moto G - need help.

Hello fellas,
I had few problems with my Moto G. I was on official Moto lolipop.
I've unlocked bootloader, flashed TWRP, flashed SlimRom from dev thread, but it was hard to boot (bootlooping after phone restart, I was forced to turn down, and then turn on the phone, and sometimes it was booting) and I wanted to flash other rom, without ,,hard boot" problem.
And there is how I bricked my phone.
When I tried to wipe data in TWRP (factory/cache wipe) my phone reboots suddenly. It didn't wipe anything. It just reboot my system. I tried many times - always ending with reboot.
So, I tried to flash AICP rom without wiping anything. I installed it, and I had ,,android.acore has stopped working" error. Phone was rebooting often.
I tried to wipe my data again, without succeed. It was rebooting, and I've seen all my apps I had installed before.
I though it was TWRP fault, so I flashed CM recovery. Same thing occured. Next, I flashed CWM recovery. Same situation (reboot after choosing wipe).
So, I deleted my userdata and cache from fastboot, and tried this to solve my problems :
http://forum.xda-developers.com/moto-g/general/how-to-to-stock-5-0-2-motorola-lollipop-t3077806
Unfortunetly, it didn't helped me. Now I have one big bootloop.
What to do? Help me, please.
Thank you for your time!
////EDIT
I think I know whats happening. I have deleted my partition accidentally... I have Internal storage 0MB free, and mount errors... Is there a way to fix that, or I am screwed?

radogost said:
Hello fellas,
I had few problems with my Moto G. I was on official Moto lolipop.
I've unlocked bootloader, flashed TWRP, flashed SlimRom from dev thread, but it was hard to boot (bootlooping after phone restart, I was forced to turn down, and then turn on the phone, and sometimes it was booting) and I wanted to flash other rom, without ,,hard boot" problem.
And there is how I bricked my phone.
When I tried to wipe data in TWRP (factory/cache wipe) my phone reboots suddenly. It didn't wipe anything. It just reboot my system. I tried many times - always ending with reboot.
So, I tried to flash AICP rom without wiping anything. I installed it, and I had ,,android.acore has stopped working" error. Phone was rebooting often.
I tried to wipe my data again, without succeed. It was rebooting, and I've seen all my apps I had installed before.
I though it was TWRP fault, so I flashed CM recovery. Same thing occured. Next, I flashed CWM recovery. Same situation (reboot after choosing wipe).
So, I deleted my userdata and cache from fastboot, and tried this to solve my problems :
http://forum.xda-developers.com/moto-g/general/how-to-to-stock-5-0-2-motorola-lollipop-t3077806
Unfortunetly, it didn't helped me. Now I have one big bootloop.
What to do? Help me, please.
Thank you for your time!
Click to expand...
Click to collapse
Easiest thing to do . Reflash stock via fastboot

I tried, my friend. Bootloop. Always bootloop.

I think I have deleted my partition accidentally... I have Internal storage 0MB free, and mount errors...

Thread closed per OPs request.
Regards,
XDA-Staff

Recovery Loop...please help

I flashed the RR 7.1.1 rom on my Phone. The phone started well and after setting up everything I did the factory reset. After that the phone restarted into recovery. Now its stuck at recovery. Everytime I restart the phone to system it restarts into recovery only. I tried flashing again but no result. What shall I do???

Explain the steps you followed which will give idea for others to help you. Have you tried wiping system and flashing the ROM.

[Help] Flashed Franco Kernel over CM13 Stock and ended in bootloop

Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please

First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?

leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.

Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.