[SOLVED ]"Patching system image unconditionally..." - can't install CM at all.
my device (moto G (falcon) XT1032) is a GPE device.
in the last 2 days i tried to install CM 13 on my device.
i tried 3 different recoveries** - CWM, TWRP and CM recovery - to install cm-13.0-20160206-NIGHTLY-falcon (and yes, i checked before flashing, the SHA1).
in all those tryouts i always get into the sentence in the headline - Patching system image unconditionally... - and it just stays there forever.
one time i waited 40 minutes, and it still stayed on this message, and do nothing.
every time before flashing the rom, i wiped the device (dalvik cache, cache, system, Data).
i also try to flash the latest snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon) because i thought maybe there is a problem with the latest nightly.
i still stuck in the same stage(Patching system image unconditionally...).
i also try to flash stock rom 4.4.4 from motorola (from here: http://goo.gl/xAomMi) which succeeded, and then wipe device(factory reset and wipe dalvik cache, cache, system, Data) and install again cm-13.0-20160206-NIGHTLY-falcon, and it also didn't work.
i'm still get into the same message and stay there forever.
thanks for any help
** EDIT: http://forum.xda-developers.com/showpost.php?p=65237469&postcount=3
papandreoos said:
my device (moto G (falcon) XT1032) is a GPE device.
in the last 2 days i tried to install CM 13 on my device.
i tried 3 different recoveries - CWM, TWRP and CM recovery - to install cm-13.0-20160206-NIGHTLY-falcon (and yes, i checked before flashing, the SHA1).
in all those tryouts i always get into the sentence in the headline - Patching system image unconditionally... - and it just stays there forever.
one time i waited 40 minutes, and it still stayed on this message, and do nothing.
every time before flashing the rom, i wiped the device (dalvik cache, cache, system, Data).
i also try to flash the latest snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon) because i thought maybe there is a problem with the latest nightly.
i still stuck in the same stage(Patching system image unconditionally...).
i also try to flash stock rom 4.4.4 from motorola (from here: http://goo.gl/xAomMi) which succeeded, and then wipe device(factory reset and wipe dalvik cache, cache, system, Data) and install again cm-13.0-20160206-NIGHTLY-falcon, and it also didn't work.
i'm still get into the same message and stay there forever.
thanks for any help
Click to expand...
Click to collapse
Use Philz recovery and make sure you unlocked boot loader cleanly, if this Doesn't help try to flash some other ROM.
Best Of Luck
i also used philz_touch_6.58.7-falcon recovery.
still i got into the same problem i described in my first post.
p.s.
i forgot to mention this recovery in my first post, but after you suggested it, i remembered i used it already.
papandreoos said:
i also used philz_touch_6.58.7-falcon recovery.
still i got into the same problem i described in my first post.
p.s.
i forgot to mention this recovery in my first post, but after you suggested it, i remembered i used it already.
Click to expand...
Click to collapse
Try installing some other ROM.
[email protected] said:
Try installing some other ROM.
Click to expand...
Click to collapse
do you have a suggestion for good ROM (everything works) for moto g (xt1032), which has marshmallow in it?
papandreoos said:
do you have a suggestion for good ROM (everything works) for moto g (xt1032), which has marshmallow in it?
Click to expand...
Click to collapse
May be this helps
http://forum.xda-developers.com/showthread.php?t=3284323
Or
http://forum.xda-developers.com/showthread.php?t=3250449
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
If you can't install this flash stock and check if you can flash any Zip (try SuperSU zip in my word) if this ain't successful try to type unlock boot loader commands again.
Best of luck.
[email protected] said:
May be this helps
http://forum.xda-developers.com/showthread.php?t=3284323
Or
http://forum.xda-developers.com/showthread.php?t=3250449
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
If you can't install this flash stock and check if you can flash any Zip (try SuperSU zip in my word) if this ain't successful try to type unlock boot loader commands again.
Best of luck.
Click to expand...
Click to collapse
i tried now the AOSP rom in one of your links.
i wiped cache, dalvik cache, system and data and then continue to install the rom, but again it stuck in the same line as before and does nothing.
papandreoos said:
i tried now the AOSP rom in one of your links.
i wiped cache, dalvik cache, system and data and then continue to install the rom, but again it stuck in the same line as before and does nothing.
Click to expand...
Click to collapse
Flash back to stock and try to flash supersu zip from here if this doesn't work the problem must be while unlocking bootloader ,anyways was bootloader unlocked normally or you had any problems ?
https://download.chainfire.eu/696/SuperSU/
Flash via fast boot not some other flash able Zip
Best of luck.
[email protected] said:
Flash back to stock and try to flash supersu zip from here if this doesn't work the problem must be while unlocking bootloader ,anyways was bootloader unlocked normally or you had any problems ?
https://download.chainfire.eu/696/SuperSU/
Flash via fast boot not some other flash able Zip
Best of luck.
Click to expand...
Click to collapse
my bootloader is unlocked already.
before i tried to flash CM couple of days ago, i follow steps from CM wiki, and part of them is to unlock the bootloader.
here are the orders i followed(although it's for a different device (moto g 4g)), it worked great:
https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine#Unlocking_the_device
if i get into fastboot mode (volume down + power) it tells me in yellow line: Device is UNLOCKED. Status Code: 3.
i also have root access.
papandreoos said:
my bootloader is unlocked already.
before i tried to flash CM couple of days ago, i follow steps from CM wiki, and part of them is to unlock the bootloader.
here are the orders i followed(although it's for a different device (moto g 4g)), it worked great:
https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine#Unlocking_the_device
if i get into fastboot mode (volume down + power) it tells me in yellow line: Device is UNLOCKED. Status Code: 3.
i also have root access.
Click to expand...
Click to collapse
The metod sound the same...........Have you tried to flash stock ROM via Fast boot again?
[email protected] said:
The metod sound the same...........Have you tried to flash stock ROM via Fast boot again?
Click to expand...
Click to collapse
i forgot to mention that after every failure of flashing, i always get back to lollipop 5.1 GPE version with this helpfull tool:
http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
so everything is OK in my phone.
i'm just frustrated i can't install newer OS.
papandreoos said:
i forgot to mention that after every failure of flashing, i always get back to lollipop 5.1 GPE version with this helpfull tool:
http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
so everything is OK in my phone.
i'm just frustrated i can't install newer OS.
Click to expand...
Click to collapse
Try to flash KitKat for a while then flash CM 11 then any CM 12 then CM 13 I have have an similar error, whenever I try to flash another ROM the data partition doesn't format and then I have to do is to flash KitKat Stock then CM 11 then CM 12 then CM 13 .
Best Of Luck this should work.
---------- Post added at 08:25 AM ---------- Previous post was at 08:16 AM ----------
The tool isn't a good Idea I use to make an bat file and not customized a bit file of firmware if you don't know what it is I will give it to you .
Here , download the untouched version and flash via Fast boot if not completed find KitKat version :-
http://www.gimmickmag.com/restore-moto-g-xt1032-xt1033-xt1034-back-stock-firmware/
If you can't find there wait for FileFactory server to come up again it has all firmwares
[email protected] said:
Here , download the untouched version and flash via Fast boot if not completed find KitKat version :-
http://www.gimmickmag.com/restore-moto-g-xt1032-xt1033-xt1034-back-stock-firmware/
If you can't find there wait for FileFactory server to come up again it has all firmwares
Click to expand...
Click to collapse
i flashed 4.4.4 stock from here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
i used the untouched version:
Retail EU 4.4.4 Stock ROM (Untouched) (457mb)
https://docs.google.com/uc?id=0B6RNTe4ygItBVFlwN2pqWmV1VXc&export=download
so far it's working.
i boot into the stock and it's 4.4.4.
the screen is flickering but it's stock 4.4.4.
now i'm gonna try flash this latest snapshot of CM11:
cm-11-20140504-SNAPSHOT-M6-falcon.zip
from here:
https://download.cyanogenmod.org/?device=falcon
i now into fastboot mode, installing TWRP 3.0.0.0:
fastboot flash recovery twrp-3.0.0.0-falcon.img
success!
get into recovery now.
sha1 verified.
copy CM11 into phone
i'm still on TWRP.
i now wipe data, cache, dalvik cache and system.
done.
now i'll try flash CM11
WOW!!!
after couple of seconds (maybe 30-40) it's done.
i reboot into CM11 without a problem (just the flickering screen again, but never mind. i'm not planing to stay in CM11).
the android version in latest CM11 is 4.4.2
now i'm gonna try to flash CM12
get into recovery again.
sha1 verified.
copy cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon into device.
wiping data, cache, dalvik cache and system again.
flashing!
not working
i again stuck in " "Patching system image unconditionally..." forever.
(going back to GPE 5.1)
Flash via Fast Boot it might be the problem.
[email protected] said:
Flash via Fast Boot it might be the problem.
Click to expand...
Click to collapse
you mean "adb sideload rom.zip"?
if yes, i already did that and it was stopped in 47 percent and sometime in 45 percent.
it stays there forever.
papandreoos said:
you mean "adb sideload rom.zip"?
if yes, i already did that and it was stopped in 47 percent and sometime in 45 percent.
it stays there forever.
Click to expand...
Click to collapse
No Flash Stock KitKat From Firmware via boot loader .
i think i'll pass.
i already flash kitkat and after that CM11 and it didn't help me to get into CM13.
i'm tired of flashing and restoring again and again.
thanks a lot for your help
As you wish...
I followed your steps too and i am exactly facing your problems, i am stuck in "patching system image unconditionally"...
Related
I have a Verizon Motorola Droid Razr HD Maxx (xt926) - I am rooted with unlocked bootloader. I flashed CWM recovery, made a backup, did data wipe/factory reset, then installed cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip followed by gapps-kk-20140606-signed.zip first using push and install method - got stuck in boot loop.
Booted back into CWM, tried wiping dalvik cache, cache, and another data wipe/factory reset - still stuck in boot loop.
Restored my backup, then tried again, this time with just the cm package without gapps. Also, tried sideload method this time - still stuck in boot loop. Again tried wiping dalvik cache, cache, and data, but no luck.
Restored my backup and I'm back to stock KK (183.46.10) - still have root and unlocked bootloader.
Am I using wrong version of cm? Please help.
marcbraze said:
I have a Verizon Motorola Droid Razr HD Maxx (xt926) - I am rooted with unlocked bootloader. I flashed CWM recovery, made a backup, did data wipe/factory reset, then installed cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip followed by gapps-kk-20140606-signed.zip first using push and install method - got stuck in boot loop.
Booted back into CWM, tried wiping dalvik cache, cache, and another data wipe/factory reset - still stuck in boot loop.
Restored my backup, then tried again, this time with just the cm package without gapps. Also, tried sideload method this time - still stuck in boot loop. Again tried wiping dalvik cache, cache, and data, but no luck.
Restored my backup and I'm back to stock KK (183.46.10) - still have root and unlocked bootloader.
Am I using wrong version of cm? Please help.
Click to expand...
Click to collapse
m8 is for jb bootloader you have the kitkat bootlader you need to flash things for that boot loader
billycar11 said:
m8 is for jb bootloader you have the kitkat bootlader you need to flash things for that boot loader
Click to expand...
Click to collapse
Same problem I was having with CWM - how can I tell which bootloader is it for? Can you point me to a proper version for the KK bootloader?
marcbraze said:
Same problem I was having with CWM - how can I tell which bootloader is it for? Can you point me to a proper version for the KK bootloader?
Click to expand...
Click to collapse
if you have stock kit kat you have the new boot loader. here are the recovery's
TWRP http://forum.xda-developers.com/showthread.php?t=2776515 there is a typo in how to flash it take out the "]"
CWM http://forum.xda-developers.com/showthread.php?t=2747535
I have having the same issue as everyone else. When I install the latest build for CM plus the gapps. All my phone does is bootloops the whole time. Can someone help a brother out and them me how you'll installed it? That forum didn't help the issue I am having.
Sent from my SM-N900V using Tapatalk
TheGman125 said:
I have having the same issue as everyone else. When I install the latest build for CM plus the gapps. All my phone does is bootloops the whole time. Can someone help a brother out and them me how you'll installed it? That forum didn't help the issue I am having.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
@billycar11 pointed you to the correct recoveries you need.
All you need to do then is go to the RAZR HD Android Development forum and look in the CM11 thread, which is here -> http://forum.xda-developers.com/showthread.php?t=2518701
That is for the KK bootloaders.
iBolski said:
@billycar11 pointed you to the correct recoveries you need.
All you need to do then is go to the RAZR HD Android Development forum and look in the CM11 thread, which is here -> http://forum.xda-developers.com/showthread.php?t=2518701
That is for the KK bootloaders.
---------- Post added at 12:00 PM ---------- Previous post was at 12:00 PM ----------
@billycar11 pointed you to the correct recoveries you need.
All you need to do then is go to the RAZR HD Android Development forum and look in the CM11 thread, which is here -> http://forum.xda-developers.com/showthread.php?t=2518701
That is for the KK bootloaders.
Click to expand...
Click to collapse
I used the recovery from the forum. Is this the create recovery that everyone is using?
TheGman125 said:
I used the recovery from the forum. Is this the create recovery that everyone is using?
Click to expand...
Click to collapse
I don't understand your question. As I stated, @billycar11 pointed you to the correct custom recoveries you need to install CM11. First, as I asked in another thread, has your phone been upgraded to KK? If so, then using either the CWM or TWRP recovery that @billycar11 linked to is your first step.
Then, go to the link I posted to the CM11 thread to download a CM11 to flash via CWM or TWRP onto your phone.
It doesn't get any easier than that.
Note with CM11, you have to download the CM11 image AND a GAPP image. Without hte GAPP image, you won't have access to google apps (such as the Play Store, etc).
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
I_HAVE_NO_IDEA said:
Hello!
I bought a Moto G falcon 2 mounts ago. Running CM12 everything was good.
I flashed a cm12.1, then my falcon started to crash randomly (mostly because i didn't flash the proper Gapps). So I wanted to revert back to KitKat to make a proper flash since the beginning, wich was ofc a bad idea. So I flashed the 4.4.4 stock ROM and now am in soft brick. I'm stuck at boot logo (The boot loader unlocked one). I tried to flash a stock 5.1 ROM (GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip) without any success.
My bootloader is updated to 4118, I can boot in recovery/bootloader.
Any ideas how to boot again? Thank you!
Click to expand...
Click to collapse
Well if you can boot into the recovery and if its custom (TWRP) wipe all the data on your phone. Second I would try to flash a ROM onto your device such as Resurrection Remix and see if that works. Update on your progress.
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
I_HAVE_NO_IDEA said:
Thank you for your answer.
I tried to wipe data/factory reset, but twrp throws some error messages.
Unable to mount /data, /cache, /system and all derivatives.
I tried to flash a ROM through twrp but I think I can't because of that partition mess. I can't adb push to /sdcard, or sideload (seems to require /data).
I think that my issue is that I flashed the 4.4.4 gpt.bin, and I shouldn't have. If I'm right, is there any way to recover from this?
Click to expand...
Click to collapse
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
vtails said:
I crashed my S3 using camera on old cm12.1 and got into loop with services stopped. Try and D/L the new 4 22 and Slim ggaps 20150422 wipe chache and devik and reinstall cm and ggaps get it working this is what I did but I haven't read any info except to find a file for Odin but don't think you can use Odin. It be nice to have stable way to downgrade. The flash will hopefully get your phone working.
Click to expand...
Click to collapse
Thank you. But I can't flash a cm12.1 atm (see my post below). I can only flash through fastboot. I'm not sure I properly understood you, what do you call 4 22 ?
FYI I managed to boot again. Here's what I did:
Flash a 5.x ROM, try to boot to let the system make partitions and stuff (I think)
Boot in TWRP and saw that system and cache were not mountable, so I wiped them.
Flash a cm12.1 (+ Gapps) and here we go!
Thank you for your help!
I posted this over on the CM forums, but wanted to post here as well for visibility.
I have multiple (read as 30+) 1st Gen Boost Moto Gs (XT1031) and this has been a problem on every.... single.... one...
Stock OS Info
Android Version: 4.4.2
Baseband version: MSM8626BP_1032.355.66.00R
Kernel version: 3.4.0-gc6fc9e1-00001-gf3bf628
System version: 175.44.1.falcon_cdma.Boost.en.US
Build number: KXB20.9-1.10-1.18-1.1
Bootloader: 41.1A
Recovery: twrp-2.8.7.0.-falcon_STOCK_NOTHEME
I've also tested with the Stock 4.4.4 and 5.1 Soak Test OS versions, both have the same results as well.
Additionally, this happens regardless of whether GAPPS is flashed or not.
I've tried the following, and ALWAYS results in an endless boot that just constantly stays on the CM Android head boot animation unless I flash & boot to CM11 first:
(Note: A TWRP Factory Reset is performed before flashing each new ROM)
CM11 - cm-11-20140504-SNAPSHOT-M6-falcon.zip
Stock -> CM11 = Boots and works fine
CM12.1 - cm-12.1-20151115-NIGHTLY-falcon.zip
Stock -> CM12.1 = Endless Boot
Stock -> CM11 (without booting to OS) -> CM12.1 = Endless Boot
Stock -> CM11 (Booted once) -> CM12.1 = Boots and works fine
CM13 (all nightly versions)
Stock -> CM13 = Endless Boot
Stock -> CM11 (without booting to OS) -> CM13 = Endless boot
Stock -> CM11 (Booted once) -> CM13 = Boots and works fine
So...The only way that I can get these to boot, is if I flash CM11 AND boot into it once and THEN flash CM12.1/CM13.
What is it about the first boot of CM11 that makes CM12.1 and CM13 work? any why doesn't direct from Stock -> CM12.1/CM13 work??? Is there a Kernel or something that gets installed when CM11 boots or something?
This is driving me insane. Please help me figure this out so that I can flash directly from Stock -> CM12.1/CM13.
---
Here is an example of exactly how to reproduce this problem. From the Stock ROM, do the following:
{Unlock Bootloader}
{Enable USB Debugging}
adb reboot bootloader
fastboot flash motoboot motoboot_41.1A.img
fastboot flash logo logo.bin
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
fastboot reboot
adb reboot recovery
adb shell twrp wipe factoryreset
adb push cm-12.1-20151115-NIGHTLY-falcon.zip /sdcard/
adb shell twrp install /sdcard/cm-12.1-20151115-NIGHTLY-falcon.zip
adb reboot
Click to expand...
Click to collapse
...Device never boots, and only stays on the CM logo animation.
I've just finished updating from Stock 5.1 (XT1033) to CM 13
Here's what I've done
1. Updated to the latest TWRP recovery
2. Copied the latest CM 13 nightly and Gapps (Pico) to internal storage
3. Reboot to recovery
4. Performed an advanced wipe. Wiping /system, /cache and /dalvik-cache
5. Performed a Factory Reset
6. Flashed both CM 13 and Gapps
7. Reboot
Wait for a few minutes.
mardobloom said:
I've just finished updating from Stock 5.1 (XT1033) to CM 13
Here's what I've done
1. Updated to the latest TWRP recovery
2. Copied the latest CM 13 nightly and Gapps (Pico) to internal storage
3. Reboot to recovery
4. Performed an advanced wipe. Wiping /system, /cache and /dalvik-cache
5. Performed a Factory Reset
6. Flashed both CM 13 and Gapps
7. Reboot
Wait for a few minutes.
Click to expand...
Click to collapse
Exact same steps on my XT1031, waited 6 hours, still didn't boot.
But if I flash CM11, boot to it once, then factory reset and install CM13... it will boot just fine. What magic does CM11 do that CM12.1/CM13 aren't doing?!
As a side note, the TRWP Factory Reset option wipes /system /cache and /dalvik-cache... so step #4 is redundant.... but I did it anyways.
Edit: I guess I skipped step #1 ... didn't realize that TWRP 3.0.2.0 was available for "falcon". I'll try this later tonight and see if it fixes the issue or not.
https://dl.twrp.me/falcon/
twig123 said:
As a side note, the TRWP Factory Reset option wipes /system /cache and /dalvik-cache... so step #4 is redundant.... but I did it anyways.
Click to expand...
Click to collapse
I followed the steps to perform a clean update from the official thread of CM 13 but when I tried to install the zip file it says that the data is incompatible and I needed to perform a factory reset. So that's why I've added that additional step so that there won't be any problems while installing CM 13. :laugh:
twig123 said:
Edit: I guess I skipped step #1 ... didn't realize that TWRP 3.0.2.0 was available for "falcon". I'll try this later tonight and see if it fixes the issue or not.
https://dl.twrp.me/falcon/
Click to expand...
Click to collapse
Okay try first with that one i.e. TWRP 3.02.0. If that doesn't work then maybe you can try this one from here :- http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621 <------- This one worked fine for me i.e twrp-3.0.0.0_2-falcon following the above steps which I've mentioned.
P.S. I'm currently on baseband 1032.3116.98.00R - Retail Asia
mardobloom said:
I followed the steps to perform a clean update from the official thread of CM 13 but when I tried to install the zip file it says that the data is incompatible and I needed to perform a factory reset. So that's why I've added that additional step so that there won't be any problems while installing CM 13. :laugh:
Okay try first with that one i.e. TWRP 3.02.0. If that doesn't work then maybe you can try this one from here :- http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621 <------- This one worked fine for me i.e twrp-3.0.0.0_2-falcon following the above steps which I've mentioned.
P.S. I'm currently on baseband 1032.3116.98.00R - Retail Asia
Click to expand...
Click to collapse
Nope. Flashed back to stock to test, updated to TWRP 3.0.2.0, attempted to flash to the latest CM13 nightly... still endless boot (waited 30min and it just stayed on the boot animation).
I'll try the recovery you mentioned later.... although, I also tried CM's own Nightly recovery... and the same thing happens with that as well.
I tried with the recovery you mentioned, and the same thing happens.
However, the story unfolds...
Recovery log when flashing from Stock-to-CM11:
http://pastebin.com/M0EGdLwu
Recovery log when flashing from Stock-to-CM12.1:
http://pastebin.com/HaderDW2
In the Stock-to-CM12.1 log.... it doesn't appear that anything is copied! if you look at the Stock-to-CM11 log, after the "Installing zip file '/sdcard/cm-11-20140504-SNAPSHOT-M6-falcon.zip'" line, it has a bunch of "minzip: Extracted file" lines. Comparing that to the Stock-to-CM12.1 long, none of those such lines exist in the log! I see the CM12.1 ROM file has a "system.new.dat" file, instead of all of the files extracted in the "system" folder, like the CM11 ROM has... not sure if that is causing the problem or not.
If none of the files are getting copied, that would explain why it never boots.... but this doesn't tell me how to fix it... or why CM11 doesn't have a problem, but CM12.1 and CM13 DO have a problem.
twig123 said:
I tried with the recovery you mentioned, and the same thing happens.
However, the story unfolds...
Recovery log when flashing from Stock-to-CM11:
http://pastebin.com/M0EGdLwu
Recovery log when flashing from Stock-to-CM12.1:
http://pastebin.com/HaderDW2
In the Stock-to-CM12.1 log.... it doesn't appear that anything is copied! if you look at the Stock-to-CM11 log, after the "Installing zip file '/sdcard/cm-11-20140504-SNAPSHOT-M6-falcon.zip'" line, it has a bunch of "minzip: Extracted file" lines. Comparing that to the Stock-to-CM12.1 long, none of those such lines exist in the log! I see the CM12.1 ROM file has a "system.new.dat" file, instead of all of the files extracted in the "system" folder, like the CM11 ROM has... not sure if that is causing the problem or not.
If none of the files are getting copied, that would explain why it never boots.... but this doesn't tell me how to fix it... or why CM11 doesn't have a problem, but CM12.1 and CM13 DO have a problem.
Click to expand...
Click to collapse
Backup first and try to restore your phone to stock firmware using the instructions over here. ----------> http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
And choose the firmware version which is related to your phone. They will be something like this:-
XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip
XT1031_FALCON_REPW_5.1_LPB23.13-51-R.10_cid6_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPB23.13-33.6_cid9_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPBS23.13-33.6-2_cid9_CFC.xml.zip
mardobloom said:
Backup first and try to restore your phone to stock firmware using the instructions over here. ----------> http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
And choose the firmware version which is related to your phone. They will be something like this:-
XT1031_FALCON_BOOST_5.1_LPB23.13-56_cid9_CFC.xml.zip
XT1031_FALCON_REPW_5.1_LPB23.13-51-R.10_cid6_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPB23.13-33.6_cid9_CFC.xml.zip
XT1031_FALCON_USC_5.1_LPBS23.13-33.6-2_cid9_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already flashed to stock (XT1031_FALCON_BOOST_5.1 in this case).
The issue is coming FROM stock to CM12.1 or CM13 that is the problem, but Stock->CM11->CM12.1/CM13 works fine.
I don't want to have to install CM11 every time just to get a bootable rom... :-\
twig123 said:
Thanks for the suggestion, but I've already flashed to stock (XT1031_FALCON_BOOST_5.1 in this case).
The issue is coming FROM stock to CM12.1 or CM13 that is the problem, but Stock->CM11->CM12.1/CM13 works fine.
I don't want to have to install CM11 every time just to get a bootable rom... :-\
Click to expand...
Click to collapse
Save the recovery log while upgrading from CM11 to CM 12.1 to see what's the difference between that one which works and Stock to CM12.1/13
After playing with trying to flash CM13 directly for quite a long time.... I've come to the conclusions that something with the partition wipes don't actually work within the CM13 setup script, nor from Custom Recovery!
However, I found a workaround! Wiping the partitions from the Bootloader, instead of from Custom Recovery, allows a flash of CM13 to boot properly!
(The question still stands as to why CM11 doesn't have this issue, but CM12.1 and CM13 do...... but I have a workaround, so I'm not too worried about it)
I made a Windows Batch script to automate this flashing process, which I posted over on the CM Forum:
https://forum.cyanogenmod.org/topic...-to-cm121-or-cm13-never-boots/#comment-601380
I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......
iHackIt said:
I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......
Click to expand...
Click to collapse
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:
karanksj said:
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:
Click to expand...
Click to collapse
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.
iHackIt said:
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.
Click to expand...
Click to collapse
I quoted 5.0.1 not 5.1 brother It worked for me every time.
karanksj said:
I quoted 5.0.1 not 5.1 brother It worked for me every time.
Click to expand...
Click to collapse
Sorry for misreading...:silly:
I cant flash 5.0.1, 4.4.2,4.4.4
When i try to flash it gives errors and warnings (only 5.1 works )
i will share errors...
works in the sense it was flashed perfectly but it also boots to the recovery everytime like CM13
My bootloader version is 41.1A..
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!
Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241
Thanks a lot, once again
Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode