Related
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?
I can't install custom ROMs on p3113
Steps Taken
Starting with stock firmware/recovery
using chainfire autoroot
reboot
use root checker to confirm root
Use Odin to flash a custom recovery. (I tried Andi's CWM, TWRP, and also Philz touch 6.40)
Custom recovery flashes no issues and I can boot into custom recovery
I do factory wipe, then also dalvik, and cache again for good measure
Go to install a custom ROM via recovery
Go to reboot and the recovery prompts me that I need root and to asks gives me an option to install su
When I do that and reboot it bootloops.
I've tried 3 different recoveries. The ROMs I've attempted to flash are Dhollmen 4..4.4, and Andi's Omnirom 4.4..4.
It appears I can install 5.x ROMs without issue.
Any idea what I can do to fix this problem?
edit: in the process of trying twrp 2.8.0.5
edit2: no luck with 2..8.0.5 which I found on Dhollmen's thread. Going go browse through the forum looking for older recoveries.
Have you tried clearing /system
Yes
Try updating your SU binary before the flash, also try plain jane CWM, Andis CWM acts weird sometimes.
If SU binary won't update delete and install a different one, then update.
Pp.
Wipe cache
Wipe dalvic
Format /data
Format /system
Reboot recovery once
Flash rom.zip (don't flash anything else!)
Reboot into system, don't use "fix root"!
If it boots (Lollipop takes some time) your are good to go to flash gapps etc.
Send from OnePlus One using Tapatalk
Android-Andi said:
Wipe cache
Wipe dalvic
Format /data
Format /system
Reboot recovery once
Flash rom.zip (don't flash anything else!)
Reboot into system, don't use "fix root"!
If it boots (Lollipop takes some time) your are good to go to flash gapps etc.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
The only thing I wasn't doing was rebooting after wiping. Wiping then rebooting let me install the 4.4.4 ROMs no problem. I never would have figured this out thanks a lot. What causes the need to reboot after wiping?
@HappyRoot good to hear.
Seems like one of the partition wasn't unmount by the updater-script or recovery after wipe and caused that issue.
Send from OnePlus One using Tapatalk
Android-Andi said:
@HappyRoot good to hear.
Seems like one of the partition wasn't unmount by the updater-script or recovery after wipe and caused that issue.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
It only worked with installing SlimKat/Dhollmen I'm still unable to install Omni 4.4.4. I've done a complete wipe Odin'd twrp 2.8.4.1 and flash the zip via adb sideload. I keep getting an updater binary error.
update: twrp would crash at 37% and give me a binary error. when i odin'd updated cwm from you android file list i was able to get to 100% but then i would get a status 6 error.
Then you are doing something wrong...
Recovery log?
Send from OnePlus One using Tapatalk
So I tried flashing CM 12.1 on my Moto G (2013) and it had an error on flashing:
Code:
Detected filesystem ext4 for /dev/block/platform/msm/sdcc.1/by-name/system
Patching system image unconditionally...
blkdiscard failed: Invalid argument
E:Error executing updater binary in zip '/sdcard/cm-12.1-20150429-NIGHTLY-falcon.zip'
It shouldn't do that, I'm not sure why it didn't work. I wiped the system, cache, and data partitions beforehand.
I'm on a Telus XT1032 that I have converted to GPE.
I tried downloading an older nightly, verifying the md5sum, and trying that, same error. I read that for GPE you need to convert the data partition to F2FS from ext4, so I did that. I actually tried a number of different fielsystems for data, system, and cache. Nothing worked.
I flashed a gpt.bin partition table file from XDA that was supposed to fix things, and then the "unmountable" problems started happening. At first data wasn't mounting, but the others were.
Now I've got system as ext4 and cache+data as f2fs. I tried this, which resulted in the data partition being unmountable by TWRP. So I decided to just try to get my stock ROM running again, (Telus 5.02 ROM), using the instructions based on an XDA thread which I can't link since I just made an account (fastboot flash boot.img, system.img_spacechunk.0, etc) and it's stuck at the boot logo screen, and TWRP says the cache and system partitions could not be mounted.
I've made a reddit thread on /r/motog which I also can't link. I thought I'd mention it in case it had any more information that could help, though I've tried to put it all into this post.
If I try to turn it off, it just turns on again and gets stuck on the boot logo, but I can access fastboot and TWRP. I just want something to boot on it.
Can someone help me completely re-image my phone to fix any partition table stuff and format the partitions as the right filesystem and get it to boot?
I tried flashing the latest CM 12.1 nightly zip again, it said the cache wasn't mounting and failed. I reformatted cache as ext4 and retried it again, and it seemed to work.
It works now, though I'm not 100% sure what I did. How do I close this topic?
theRealPadster said:
I tried flashing the latest CM 12.1 nightly zip again, it said the cache wasn't mounting and failed. I reformatted cache as ext4 and retried it again, and it seemed to work.
It works now, though I'm not 100% sure what I did. How do I close this topic?
Click to expand...
Click to collapse
the same problem as yours.I feel so confusing..
I've read this issue with other devices, however. i've not found a solution for this yet
I'm new to this forums, let me know if i don't do something right.
I've been using Alberto97's AOSP Lollipop 5.1.1, it's my first custom rom install, i got it on
the first try, TWRP 2.8.6.0 running with no problems.. flashed other stuff like moto camera, marshmallow bootanim, and that's all
Last week i've tried to update to the CAF latest version of his build, however, TWRP
reboots when i try to wipe the /data partition, in the custom TRWP 2.8.7.0 thread found
i might need to repair the partition, i tried it with no success, repaired /cache with no problem, but when i try to fsck /data on TWRP it gaves me an error, haven't tried /system yet.
tried using CWM and it got stuck at wiping /data for like an hour (endless loop), i rebooted, the data was wiped, but i couldn't flash the ROM image, rebooted to clean system with no problems, it wipes cache and dalvik with no issues.
What's causing this? i have not faced apps FC or anything, just the TWRP random crashes at wiping, i'm using a Moto G XT1032 16GB TWRP 2.8.6.0 No custom kernel or non official recovery.
justpaste.it/wipedar
Leaving recovery.log on external page for reference.
hope you can help, thanks in advance.
Same problem here
You can use CWM by PhilZ for fixing what I think is a broken symlink to the emulated internal storage card.
I am using philz-6.58.7-falcon that you can find and download here: http://forum.xda-developers.com/showthread.php?t=2639583
Once you have flashed the new recovery you can go to "Advance menu", then to "change sdcard target" and define it to /data/media (you just have to tap on the option to set it).
Go back, select "Wipe option", then "Wipe User media" and the process should be successful.
If you reinstall TWRP and wipe "/data" now the rebooting problem should be gone and everything back to normal.
Hope this helps for you.
By the way this is my very first post here. So I hope I am doing this right.
Greetings.
Thank you for the help, i fixed it by repairing the userdata partition with the latest TWRP
I had to flash the stock firmware while I was on back to note rom, since my phone got stuck during a bootloader upgrade.
My galaxy s6 doesn't boot anymore, it's stuck during boot saying that memory is corrupted, it says that I need to do a factory reset (Data partition was f2fs before odin flash).
If I choose to do the factory reset it reboots and if I'm on arter's recovery it wipes data and cache but nothing happens (I think it doesn't format it to ext4), if i'm on stock recovery or twrp doesn't work.
I can't enter recovery except for the data reset procedure.
I can enter in download mode, flashing stock firmware doesn't solve the issue (there isn't data.img in it so data partition doesn't get wiped).
Is it possible to flash arter kernel from odin? Or do you have any other ideas?
Thanks in advance.
Regards.
Edit: smart switch and kies don't work as well
Hello,
After a memory corruption, flash the stock firmware via Odin and let boot up the phone.
At the first boot, it will say that the memory was corrupted and need to format it.
Let it do the format and then it will boot.
-JFK- said:
Hello,
After a memory corruption, flash the stock firmware via Odin and let boot up the phone.
At the first boot, it will say that the memory was corrupted and need to format it.
Let it do the format and then it will boot.
Click to expand...
Click to collapse
Memory is not corrupted, data partition is in f2fs file system so stock firmware can't handle it. After the first boot if I choose to format the device, the stock recovery is unable to format it as well for the same reason.
I had similar problem ! I have formatted all my partitions in f2fs with arter's recovery install back to note and arter kernel but I can't format back to ext4 with arter's recovery! Arter's recovery is faulty ! I flash back twrp and reformat all with ext4 and all is fine now! I think twrp is the solution for you! If arter kernel work you can flash back to note and arter kernel and see if it boot
wil123 said:
I had similar problem ! I have formatted all my partitions in f2fs with arter's recovery install back to note and arter kernel but I can't format back to ext4 with arter's recovery! Arter's recovery is faulty ! I flash back twrp and reformat all with ext4 and all is fine now! I think twrp is the solution for you! If arter kernel work you can flash back to note and arter kernel and see if it boot
Click to expand...
Click to collapse
The problem is that if I flash twrp or philz recovery trough odin, I can't access recovery
Edit: Rooted the phone with odin, flashed twrp, and now I can access to recovery.
Wiped everything in ext4 and now the phone works.
Cool! Arter's work is good but I leave f2fs and arter's recovery for now!