Stuck in hard bootloop - Motorola Photon Q 4G LTE

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?

Related

[Q] no boot or recovery img

i tried flashing a kernel on my phone using recovery, after i tried to reboot it my phone kept going back to fastboot saying "no boot or recovery img"
i wiped cache partition and tried to factory reset it but i keep getting the same thing. PLS HELP
nexus s
nvmd, just find a clockwork mod recovery i used 3.0.2.4 and use any rom i used cyanogen 7

[Q] Recovery bugged and bootloop

I tried Reflashing a viper one s rom (dirty flash) aroma got stuck at 90% trying to "restore stock sense camera". So i did an adb reboot. After that My recovery got bugged. I would go into a bootloop if I tried an adb reboot into recovery, stuck at the htc developer only warning screen.
If i try to manually go into recovery through the bootloader. It starts up but I can't flash anything. If i try flashing/fixing permissions/clearing cache, recovery just reboots itself or crashes and again goes into the bootloop. I tried reflashing twrp/stock recovery/cwm through fastboot. all of them have the same issue.
I'm now trying to use the Soft Brick fix, but after pressing clear storage I'm in stock recovery and the progress bar doesn't move. Please Help me someone

[Q] Moto G Stuck in CM12 Boot Loop

My Moto G, model XT1032 is stuck in a CM12 bootloop. I can boot into fastboot mode and ClockWorkMod Recovery.
So far I have tried re-flashing the CM12 ROM with no success, I have downloaded the original firmware and tried to flash that but I get a "Preflash Validation Failed" error, my phone won't show up on RSD, and I have tried wiping the phone to it's factory setting.
None of these worked and I am out of ideas. Are there any other options to try?
Thanks.
Did you ever have the GPE ROM on your phone? Does your data partition uses f2fs?
If you are getting the validation error when flashing motoboot.img, that is because your current bootloader is newer than the bootloader you are trying to flash.
Hi, I'm fairly certain I had the GPE ROM on it. It was what it came shipped with, that is all I know. As for the data partition I am unsure of the format of it, how would I go about finding this information?
Thanks.
If it has the GPE ROM, it would not use f2fs for data. Do you have twrp on it? If you do, boot into twrp, advanced wipe, and check partition info.
I do not have twrp, I have ClockWorkMod. How do I check the partition on this?
In CWM, go to wipe & format options, custom format options, toggle f2fs<->ext4 migration. Then wipe data, cache, Dalvik, and reboot.
I don't have those options on my CWM, All I have is Reboot, Install Zip, Wipe Data/Factory Reset, Wipe Cache Partition, Backup and Restore, Mounts and storage and advanced. I am using version 6.0.4.6 of CWM.
Install the latest version of Philz Touch for your phone.
Okay, I did that and now my device hangs at the Motorola Bootloader Unlocked Warning screen. Should I flash a new ROM such as CM or try again with the motoboot?
I would do a full wipe and re-install to see what happens.
It's just gone back into the CM boot loop where it hangs at the pulsing CM logo. Should I try a different version of CM that is more stable?
RyanVadera said:
It's just gone back into the CM boot loop where it hangs at the pulsing CM logo. Should I try a different version of CM that is more stable?
Click to expand...
Click to collapse
I'm running the latest CM12 on my xt1032 with no problem.
You may need to flash back to stock 4.4.4, re-install Philz, and them CM12.
The partition layout on the GPE ROM is different than the partition layout on the stock.
Do you know where I can find the stock 4.4.4 file? I can't seem to locate one?
Try here: http://motofirmware.center/files/category/26-falcon/
Thanks, I got 4.4.2 running fine. Any advice on how to avoid getting stuck in another bootloop when I try to re-flash CM12?
Install the latest Philz, create a backup, then flash a ROM of your choice. To be safe, do a full wipe, including system, but not internal storage, before and after the ROM was been flashed.
Okay, Thanks for all your help.
So it all worked? I hope it did.
I'm afraid to say it did not work, It just went back into the boot loop.
How about flashing stock 4.4.4 or ota to the latest stock before flashing cm.
Are you flashing the cm for your phone?

Stuck in Bootloop

Hi,
I tried flashing my second ROM in my moto G. While clearing cache/data, my phone restarted automatically after the wipe.
Then I flashed the ROM but it seems to be stuck in loop for more tham 15 min.
Any suggestions or help.
And I cant get to recovery. As soon as I enter into recovery and twerp wallpaper shows up the phone reboots again.
prthmshetty said:
Hi,
I tried flashing my second ROM in my moto G. While clearing cache/data, my phone restarted automatically after the wipe.
Then I flashed the ROM but it seems to be stuck in loop for more tham 15 min.
Any suggestions or help.
And I cant get to recovery. As soon as I enter into recovery and twerp wallpaper shows up the phone reboots again.
Click to expand...
Click to collapse
I tried to reflash the recovery TWERP and installed cyanogen, first rom again because the same problem persisted when I tried to install another rom.
BTW while flashing recovery i got an error stating that the partitions are mismatched.

[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.

Categories

Resources