[HELP] CM13+TWRP - Installation error, bootloop, PC doesn't recognize phone via USB

aendroit

Member
Jul 4, 2016
5
0
0
Moto G XT1032

Hello,
I hope that you understand my English. I am kind of a layman concerning Android, but still wanted to install Cyanogenmod 13. I followed these instructions (can't post them apparently since I am new). Official instructions on the CM website. (Bootloader was already unlocked because I already installed Cyanogenmod 12, went back to Stock ROM and now tried to install CM13). Like alwas there were some minor errors during the first steps, but I handled them alright, I think.
The real problem started when I tried to install the zip-file of CM13 ("Installing CyanogenMod from recovery", step 8). I followed the instructions (wipe etc.), but the installation stopped at "Patching system image unconditionally" and it said something like "missing md5-file" although the file I downloaded on the TWRP website was right next to the recovery .img.
After trying and trying I started to go through the options in TWRP recovery (which was a fault, I know) and wiped some things that probably should not have been wiped. Next error message was: "unable to mount /system". New problem.

Then I thought, I might try the recovery that was right next to the downloadlink of the CM13 firmware. Installed it succesfully and tried again some things, now I have a bootloop and can't shut off the phone. When I shut it off, 1 second later the Google-screen with the open lock appears again". The only help was to manually shut it off with recovery.
I can't even start Android anymore, which means I can't activate USB-debugging, the installation files of CM13 are missing and the main problem: my PC only recognizes the phone in fast boot mode - I can't move files to the phone, it just says in the task bar: "Fastboot falcon S".
As soon as I enter recovery mode, the USB-sign on Windows vanishes.
Tried to move the files to the devices by "adb push cm-13.0-20160703-NIGHTLY-falcon.zip /scard", but it says "* daemon not running. starting it now on port 5037 *
* daemon startet successfully *
adb: error: connect failed: no devices/emulators found"

The device is not recognized by "fastboot devices" in cmd.

I hope that you understood everything. Already tried to get help in German forums, but nobody answered there.
And yeah, I definitely stopped trying to solve it by myself because I might just destroy it more.

Thanks for your help!
 
Last edited:

desvadeos

Member
Sep 26, 2015
9
0
0
seems like we are on the same trolley.
I wanted to have a 100% clean system so I wiped everything.
I reinstall SDK, google drivers, motorola drivers, but no success. In fastboot mode it's written: USB connected, on the computer eject "Fastboot falcon S". I create file adb_usb.ini with id in it, restarted system, killed adb and so on. Tried different USB port, different cables.
Aendroit, if you find a way share.
I'm on W10 if that matters.

Ok. So I managed to go through the problem.
First, I was able to reinstall TWRP with fastboot (fastboot root twrp.....), so fastboot worked for me. Then it seems that on the main screen, where you choose options with volume buttons, fastboot works, but not adb.
I went into recovery and "adb shell" worked, so did "adb devices".
I used push command and so on.
 
Last edited:

aendroit

Member
Jul 4, 2016
5
0
0
I'm glad you got the solution now. Unfortunately I can't follow the instructions. Could you please take me through it step by step ("fastboot root twrp", I never used a command like this before). Thanks!
Because when I go in recovery and type in "adb shell" or "adb shell" on my computer, it says "no devices/emulators found".

Update: Got it. I can enter TWRP now, but in the installation log it said "Mismatched partition size (recovery)" at the end. If someone knows what that means ...
 
Last edited:

desvadeos

Member
Sep 26, 2015
9
0
0
I meant: fastboot flash recovery twrp-3.0.0.0_2-falcon.img

Mismatched size is just an information, nothing to worry about. Now, when you are in TWRP try to check the device "adb devices", should work.
 

aendroit

Member
Jul 4, 2016
5
0
0
Thank you, my computer recognizes the device again! I was able to copy the files to my phone. Unfortunately I still can't install a custom rom. I tried Mokee instead of CM13 now and i always get the same messages:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 146758281
Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and so on.

I don't know what that is supposed to mean ...
 

desvadeos

Member
Sep 26, 2015
9
0
0
Well, I'm not very good oriented in all this stuff, so I don't know why you got those problems, far from being a dev.
I copied ressurection ROM + open gapps nano (thou I always used banks, but this time wanted to save more free space) and installed it via TWRP without any issues.
 

aendroit

Member
Jul 4, 2016
5
0
0
Thank you for the answer. Mokee works now! I'm not happy that I can't use CM13, but I got Mokee working after a while and I'm glad about it. :)