Database Info

[Q] How to fix Recovery bootloop on tf101g

Hey,
my tf101g boots only into cwm,
i've tryed to flash a new kenel for ubuntu in ubuntu and it goes wrong.
Ubuntu runs with mountloop from internal sdcard.
now my tf boots only cwm even when i try to "cold boot it".
ive tryed to flash a other recovery, a new android kernel and the original stock firmware form asus.
but nothing worked.
Normaly there is a green bar at the first reboot after flashing something new, but now this not happen.
cwm works completly i have access to all partitions.
Has anyone an idea to solve this bootloop?
Thank you
(i hope my english is understanable)

Caradas said:
Hey,
my tf101g boots only into cwm,
i've tryed to flash a new kenel for ubuntu in ubuntu and it goes wrong.
Ubuntu runs with mountloop from internal sdcard.
now my tf boots only cwm even when i try to "cold boot it".
ive tryed to flash a other recovery, a new android kernel and the original stock firmware form asus.
but nothing worked.
Normaly there is a green bar at the first reboot after flashing something new, but now this not happen.
cwm works completly i have access to all partitions.
Has anyone an idea to solve this bootloop?
Thank you
(i hope my english is understanable)
Click to expand...
Click to collapse
If it boots into CWM Recovery, then.... try the following:
Go to TF101 forum and find/download latest non-touch Clockwork Mod recovery zip.... I heard the touch versions don't work properly yet. Or you can try a different recovery called TWRP 2.3.1.1 http://forum.xda-developers.com/showthread.php?t=1818452
Put .ZIP on external SD card along with the ROM you wish to flash (make sure the ROM is bundled with a kernel.... safest, most stable ROM I would recommend is an ICS one such as Android Revolution HD... just browse or search the TF101 forum for it).
Get the SuperWipe script from Android Revolution HD ROM thread.... put this .ZIP on the external SD card also.
Now, reboot and go into your recovery. First do a Factory Wipe. Then run the SuperWipe .ZIP. Superwipe will format and clean out your data, system and cache.... finally, Wipe the Dalvik cache. On non-touch CWM recovery, this option is found under "Advanced"... also do a Fix Permissions (this is also found under Advanced).... then reboot.
Should be okay after that. No guarantee though.
---------- Post added at 06:16 PM ---------- Previous post was at 06:05 PM ----------
psipunk said:
If it boots into CWM Recovery, then.... try the following:
Go to TF101 forum and find/download latest non-touch Clockwork Mod recovery zip.... I heard the touch versions don't work properly yet. Or you can try a different recovery called TWRP 2.3.1.1 http://forum.xda-developers.com/showthread.php?t=1818452
Put .ZIP on external SD card along with the ROM you wish to flash (make sure the ROM is bundled with a kernel.... safest, most stable ROM I would recommend is an ICS one such as Android Revolution HD... just browse or search the TF101 forum for it).
Get the SuperWipe script from Android Revolution HD ROM thread.... put this .ZIP on the external SD card also.
Now, reboot and go into your recovery. First do a Factory Wipe. Then run the SuperWipe .ZIP. Superwipe will format and clean out your data, system and cache.... finally, Wipe the Dalvik cache. On non-touch CWM recovery, this option is found under "Advanced"... also do a Fix Permissions (this is also found under Advanced).... then reboot.
Should be okay after that. No guarantee though.
Click to expand...
Click to collapse
Oooops, I forgot... flash ROM... reboot... haha
1) Factory wipe
2) Install Superwipe.zip
3) Wipe Dalvik cache
4) Install ROM zip
5) reboot
http://forum.xda-developers.com/showthread.php?t=1245892&highlight=android+revolution
Android Revolution HD thread.
Good luck.

superwhipe erased my internal sdcard.
and i tried to flash the revolution HD rom but it doesn't boot.
is it possible to flash a new bootloader with dd?

Caradas said:
superwhipe erased my internal sdcard.
and i tried to flash the revolution HD rom but it doesn't boot.
is it possible to flash a new bootloader with dd?
Click to expand...
Click to collapse
SuperWipe wipe will erase and format INTERNAL sd system, and cache and data partitions. That is why you should always use an EXTERNAL sd card. Put your ROM zip, recovery zip and superwipe zip on an external SD and always use an external SD. This is how the manufacturer required updating this device also.
In addition, TWRP recovery has issues flashing certain roms because it fails to mount staging partition... I just realized this after testing it. So please flash clockwork mod recovery non-touch HYBRID..... The hybrid version works with flashing from internal and external SD, regardless, I but make sure it is hybrid because there are internal and external only versions. Flashing from internal sd is an OPTION on this device but the best method is always external.
Flashing a bootloader shouldn't be necessary unless you were tinkering with it before. But if you want you can search Tf101 forum for the tool to do that in the Reference sticky post on the Developer forum.
I have never had to mess with bootloader on this device..... But it's not impossible. I had to do bootloader upgrade on other devices when coming from gingerbread to honeycomb. So if you are coming from a 2.xx ROM to a 3.xx ROM then research that.

[Q] Boot loop after installing Gapps

Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.

stanix.de said:
Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.
Click to expand...
Click to collapse
Hi,
Are you s-on/off?
Did you flash the ROM and Gapps at the same time?

malybru said:
Hi,
Are you s-on/off?
Did you flash the ROM and Gapps at the same time?
Click to expand...
Click to collapse
I'm S-OFF. Yes, I flashed at the same time, first the ROM, then the Gapps

stanix.de said:
I'm S-OFF. Yes, I flashed at the same time, first the ROM, then the Gapps
Click to expand...
Click to collapse
Hi,
Then,there is no reason why it should not work.
I would download ROM and Gapps again,place on the sd card,check md5 checksum.
Format all partitions (except sd card),then,install both again.

malybru said:
Hi,
Then,there is no reason why it should not work.
I would download ROM and Gapps again,place on the sd card,check md5 checksum.
Format all partitions (except sd card),then,install both again.
Click to expand...
Click to collapse
Just a question before I start deleting everything - is it possible that this has something to do with the CID number? I have no idea what it is, but I remember that I had to change it once (now it's set to 11111111)

stanix.de said:
Just a question before I start deleting everything - is it possible that this has something to do with the CID number? I have no idea what it is, but I remember that I had to change it once (now it's set to 11111111)
Click to expand...
Click to collapse
no it has not

Problem solved by flashing a new recovery image (CWM Touch 5.8.0.9)
Thanks!

FIX for bootloop after installing GApps
stanix.de said:
Hey,
I'm quite new here, maybe there's an easy solution to that, but I don't know what to do.
I've flashed the CyanogenMod 10 on my HTC Sensation and everything works fine, but as soon as I flash Gapps from the CWM the device enters a boot loop bringing me back to the CWM after rebooting.
J've just tried the newest CM10 (http://forum.xda-developers.com/showthread.php?t=1782009) and the problem is still the same.
Thank you!
Stan.
Click to expand...
Click to collapse
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE

Nadarevicc said:
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE
Click to expand...
Click to collapse
I have done that, and it works, but I think the gapps install somehow corrupted my data, because after my phone didn't boot I backed up data just in case, and doing this it boots, but when I restore data it doesn't. do you have any ideas?

Nadarevicc said:
So, here is a fix, follow my steps:
1. DO NOT USE CWM Recovery OR PhilzTouch Recovery, because you will have bootloop with them OR flashing GApps will fail, so u need to use TWRP
2. Copy CM13 ROM to your sdcard1 (extSDCard) and GApps (nano package from opengapps.com, ARM, 6.0)
3. I think it doesn't matter if you have already CM13 ROM or firmware (correct me if it matters), so just do factory reset, clear cache and dalvik cache
4. After that, flash CM13 and GApps at same time (you have option to choose more ZIPs, 1st ROM, 2nd GApps)
5. After that, you will have button "clear cache", click on it
6. Then Reboot your phone
That's it, I've done this on my i9300, I had already installed CM13 and GApps with CWM Recovery (with bootloop) after that I've done these steps..
Sorry for bad English..
Hope this helps...
PLEASE SHARE THIS IF IT WORKS, I REALLY WANT TO HELP PEOPLE
Click to expand...
Click to collapse
Thank you so much, this worked for me. I was using CWM.

[SOLVED ]"Patching system image unconditionally..." - can't install CM at all.

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

[Help] Flashing 1st Gen Moto G (XT1031) Stock to CM12.1 or CM13, never boots

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

Miui-v10.3.3.0.pdgmixm global stable

New official rom

Hi,
Not sure it's the right place to post, tell me if not.
I received the notification for update yesterday and would like to install it. But I'm bootloader unlocked, rooted and with TWRP installed.
I've tried to install it "the normal way" anyway, but after downloading the update via OTA and rebooting, the phone reboots in TWRP and does not install the update through it...
Is there a way to install the update without loosing TWRP, root and data ?

S377 said:
Hi,
Not sure it's the right place to post, tell me if not.
I received the notification for update yesterday and would like to install it. But I'm bootloader unlocked, rooted and with TWRP installed.
I've tried to install it "the normal way" anyway, but after downloading the update via OTA and rebooting, the phone reboots in TWRP and does not install the update through it...
Is there a way to install the update without loosing TWRP, root and data ?
Click to expand...
Click to collapse
Not update OTA with twrp recovery
You're need:
Download full zip rom
Flash it by twrp recovery without wipe.

heobanhki said:
Not update OTA with twrp recovery
You're need:
Download full zip rom
Flash it by twrp recovery without wipe.
Click to expand...
Click to collapse
Ok, so I could just do the following steps ?
- Download the ROM by the MIUI updater (which stores the full zip in "downloaded_rom" folder")
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Optionally : Flash Magisk to retrieve root
- Reboot
Since my post, I've found this thread for Mi Mix 2 (not 2s) which talk about a LazyFlasher zip...
Isn't it needed ?

subboxcb said:
New official rom
Click to expand...
Click to collapse
Missprint in that update note? My Global 10.3.3.0 PDGMIXM got the security patch from May 1 :S
Update: Nvm, said May patch a line down...
Sent from my MIX 2S using XDA Labs

S377 said:
Ok, so I could just do the following steps ?
- Download the ROM by the MIUI updater (which stores the full zip in "downloaded_rom" folder")
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Optionally : Flash Magisk to retrieve root
- Reboot
Since my post, I've found this thread for Mi Mix 2 (not 2s) which talk about a LazyFlasher zip...
Isn't it needed ?
Click to expand...
Click to collapse
Someone can tell me please ?

S377 said:
Someone can tell me please ?
Click to expand...
Click to collapse
Don't upgrade!! There's no twrp for the new rom
I'll wait some days to see if a working twrp appears else I'm flashing 10.2.2 again (which is a PITA since it needs "flash_all" = reinstall everything)

xumixu said:
Don't upgrade!! There's no twrp for the new rom
I'll wait some days to see if a working twrp appears else I'm flashing 10.2.2 again (which is a PITA since it needs "flash_all" = reinstall everything)
Click to expand...
Click to collapse
Hi !
Please define "no twrp for the new rom"
I'm running V10.3.3.0 with official twrp (3.3.0) and can boot into twrp and install things from there.
(didn't test things like backup/restore though)
kr

flushbeer said:
Hi !
Please define "no twrp for the new rom"
I'm running V10.3.3.0 with official twrp (3.3.0) and can boot into twrp and install things from there.
(didn't test things like backup/restore though)
kr
Click to expand...
Click to collapse
Did you do any workaround for installation? I installed it as usual and it gets deleted at reboot (after flashing from 10.2.2 to 10.3.3).

xumixu said:
Did you do any workaround for installation? I installed it as usual and it gets deleted at reboot (after flashing from 10.2.2 to 10.3.3).
Click to expand...
Click to collapse
copy ROM to any other folder (e.g. from /sdcard/downloaded_rom to /sdcard), then ROM will not get deleted.
(or even better OTG if you have)

flushbeer said:
copy ROM to any other folder (e.g. from /sdcard/downloaded_rom to /sdcard), then ROM will not get deleted.
(or even better OTG if you have)
Click to expand...
Click to collapse
i mean twrp get deleted from the recovery partition on reboot
and i didnt used the "update" zip, but the full rom from miui download site

xumixu said:
i mean twrp get deleted from the recovery partition on reboot
and i didnt used the "update" zip, but the full rom from miui download site
Click to expand...
Click to collapse
oh, I misunderstood.
this behaviour I had with EVERY update. Just installed twrp again and everything working again.

Same here, but in this last update it gets reverted when I reboot, Whether I let it restart right after flashing twrp or if get into it after flashing. Is also noteworthy that it doesn't prompt me the "partition modification" message.
Is there any "settings" or cache for twrp that can be cleaned to have a "fresh" install? It remembers the time zone so I think it should save some things somewhere

Hm. weird. what I did was fastboot into TWRP and from there install as image from internal storage (or OTG).
(Might be, that I tried another version (v14? v15? from this forum) because I tested a few things because of my phone freezing problems. But I guess this should not make any difference.)
So no black magic here.
The only thing i know: I have it running.

Ok, thanks to both of you for your response.
I'll try to install it and will let you know for TWRP !
@xumixu : have you tried to "reboot to recovery" from TWRP once you've installed it and boot to it from adb ?

S377 said:
Ok, thanks to both of you for your response.
I'll try to install it and will let you know for TWRP !
@xumixu : have you tried to "reboot to recovery" from TWRP once you've installed it and boot to it from adb ?
Click to expand...
Click to collapse
No issues reboting into recovery after twrp installation. But once i get into system, recovery partition is factory restored to mi-recovery 3.0

All went good for me !
I've done the following steps :
- Download the full ROM (~1.9 GB) on the official MIUI website
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Wipe Dalvik/ART and Cache
- Flash Magisk to retrieve root
- Wipe Dalvik/ART and Cache
- Reboot TO RECOVERY !
- Reboot to system
I've done this going from MIUI v10.2.2.0 to v10.3.3.0 and using the official TWRP 3.2.3.0

S377 said:
All went good for me !
I've done the following steps :
- Download the full ROM (~1.9 GB) on the official MIUI website
- Reboot to TWRP
- Wipe Dalvik/ART and Cache
- Flash the downloaded zip
- Wipe Dalvik/ART and Cache
- Flash Magisk to retrieve root
- Wipe Dalvik/ART and Cache
- Reboot TO RECOVERY !
- Reboot to system
I've done this going from MIUI v10.2.2.0 to v10.3.3.0 and using the official TWRP 3.2.3.0
Click to expand...
Click to collapse
tried all those steps and I still end up bootlooped (with magisk 19 and 19.3).
ill back up important data, and make a clean 10.3.3 installation. If it doesnt work with 10.3.3, I'll rollback to 10.2.2

Seems that my rom "setup" was the culprit. Made a clean 10.3.3 install (fastboot mode flash_all.bat), reinstalled twrp, magisk and it booted ok (and twrp stayed togheter with encryption support).
No idea what happened in the update from my 10.2.2 to 10.3.3, but twrp works ok on 10.3.3 with a clean installation

Ok, weird... But good to know that all is ok now