Database Info

CM 13 on XT1031 -- boot loop

I'm trying to install Cyanogenmod 13 on a Moto G -- according to the person who sold me the device, it was a XT1031, but I haven't actually verified this is the correct model. (Edit: I took off the rear case and verified that it was the XT1031 model.)
I'm using these instructions: https://wiki.cyanogenmod.org/w/Install_CM_for_falcon
I have adb and fastboot installed and working properly on OS X.
I used the Motorola Bootloader Unlock process to unlock the bootloader.
I installed the TWRP recovery image and am able to enter that recovery app. Specifically, twrp-3.0.2-0-falcon.img
The first time I tried to install Cyanogenmod from TWRP, I got error code 7 saying that my bootloader version, 4113, was not correct.
script aborted: This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
This package supports bootloader(s): 0x4118, 0x4119, 0x411A; this device has bootloader 0x4113.
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/cm-13.0-20161006-NIGHTLY-falcon.zip'
Click to expand...
Click to collapse
Subsequently, I downloaded (https://www.mediafire.com/folder/nd7xvjndir52j/motoboot#tf9bzbdkxwkn3) and installed motoboot_4118.zip successfully, allowing the CM13 installation to complete.
However, when I reboot normally, the device is permanently stuck at the animated Cyanogenmod logo screen. (I left the device in that state overnight with no changes, so it's not just being slow.) This is consistent for the latest nightly build of CM13 and the latest stable build.
This comment (http://forum.xda-developers.com/showpost.php?p=65319505&postcount=7) suggested going into Recovery and wiping some stuff before installing CM, so I tried this by going into TWRP, choosing Advanced Wipe, and selecting the System, Data, and Cache checkboxes, and wiping, and then re-installing CM. However, this did not resolve my boot loop problem.

urjhnbnreaf said:
I'm trying to install Cyanogenmod 13 on a Moto G -- according to the person who sold me the device, it was a XT1031, but I haven't actually verified this is the correct model. (Edit: I took off the rear case and verified that it was the XT1031 model.)
I'm using these instructions: https://wiki.cyanogenmod.org/w/Install_CM_for_falcon
I have adb and fastboot installed and working properly on OS X.
I used the Motorola Bootloader Unlock process to unlock the bootloader.
I installed the TWRP recovery image and am able to enter that recovery app. Specifically, twrp-3.0.2-0-falcon.img
The first time I tried to install Cyanogenmod from TWRP, I got error code 7 saying that my bootloader version, 4113, was not correct.
Subsequently, I downloaded (https://www.mediafire.com/folder/nd7xvjndir52j/motoboot#tf9bzbdkxwkn3) and installed motoboot_4118.zip successfully, allowing the CM13 installation to complete.
However, when I reboot normally, the device is permanently stuck at the animated Cyanogenmod logo screen. (I left the device in that state overnight with no changes, so it's not just being slow.) This is consistent for the latest nightly build of CM13 and the latest stable build.
This comment (http://forum.xda-developers.com/showpost.php?p=65319505&postcount=7) suggested going into Recovery and wiping some stuff before installing CM, so I tried this by going into TWRP, choosing Advanced Wipe, and selecting the System, Data, and Cache checkboxes, and wiping, and then re-installing CM. However, this did not resolve my boot loop problem.
Click to expand...
Click to collapse
I have the exact same problem on the same phone (XT1031) and have gone through the same steps except I'm still at the 41.1A boot loader.
The other thing worth mentioning is now the phone shows up with "fastboot devices" but adb can not find it so I had to load different firmware using USB OTG flash drive.
===
I got it booting. I think the issue was I had to install the CyanogenMod Recovery from https://download.cyanogenmod.org/?device=falcon. Once I installed CyanogenMod Recovery ( cm-13.0-20161008-NIGHTLY-falcon-recovery.img) in place of TWRP and then installed cm-13.0-20161008-NIGHTLY-falcon.zip via USB OTG it booted up.

nooky1 said:
I have the exact same problem on the same phone (XT1031) and have gone through the same steps except I'm still at the 41.1A boot loader.
The other thing worth mentioning is now the phone shows up with "fastboot devices" but adb can not find it so I had to load different firmware using USB OTG flash drive.
===
I got it booting. I think the issue was I had to install the CyanogenMod Recovery from (snip). Once I installed CyanogenMod Recovery ( cm-13.0-20161008-NIGHTLY-falcon-recovery.img) in place of TWRP and then installed cm-13.0-20161008-NIGHTLY-falcon.zip via USB OTG it booted up.
Click to expand...
Click to collapse
Can you explain how you installed CM from CM Recovery? I can't seem to find an appropriate option. When I select Apply Update => Apply from ADB, it won't let me select the "ADB Sideload" option, and adb says that my device is offline.
Note: Whenever I flash the "recovery" partition with the nightly or stable build of CM13 Recovery while in Fastboot Flash Mode, I get a "Mismatched partition size (recovery) message" in the console window.

I was able to get CM13 installed and started finally.
One change I made was to install CM13 Recovery, do a factory reset from there. Stuff broke, including the ability to use adb, so I went back to twrp-3.0.2-0-falcon.img. There I tried installing CM13 one more time, and it worked this time.
Unfortunately, I can't say exactly what made it work this time around, but I'd speculate that it was the "factory reset" operation that did it.

Can't install lineage-15.1-20180918 on a Google Pixel (sailfish) - bootloop

Hello,
I'm trying to install lineage-15.1-20180918 on my new (second hand) Google Pixel (sailfish). It came with Android 7.1.0 (NDE63H, Oct 2016) pre-installed.
No mater what I try to do, after installing Lineage zip file, I always get a warning saying that there is no OS. When I try to reboot to System, I am stuck in a boot loop between a screen saying that I should lock the bootloader and another one displaying the Google logo.
General information about device and softwares used
I run Debian on the PC that is used for the install, adb (v 1:7.0.0+r33-1) and fastboot (v 1:7.0.0+r33-1) are installed.
I got the Lineage zip from there (the shasum is good).
I got the TWRP image from there (v 3.2.3-1).
What I did
I followed the official howto there.
I have unlocked the bootloader, can boot into the TWRP recovery.
TWRP is launched via
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
I did "Format Data", then "Advanced Wipe" (selected everything and wiped).
Then
Code:
adb push lineage-15.1-20180918-nightly-sailfish-signed.zip /sdcard/
(Note that I first tried to sideload both this zip and the suaddon one, given that it didn't seem to work, I wiped everything out again and went with the adb push method)
And, finally, went back to the "Install" menu, selected the zip and launched the install process (without checking the "Verify signature checkbox").
I managed to restore the initial backup created with TWRP, the system booted normally. I then tried a LOS install again and got stuck into a boot loop again.
Problem
At the end of this process, when offered with a swipe gesture to reboot, there is a warning saying that no OS is installed. Swiping to reboot leads to the reboot loop described above.
Any idea on what I can do to fix this issue?
Huge thank you in advance!

Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.

post-mortem said:
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
Click to expand...
Click to collapse
I did not. But there were other issues as well (I used outdated version of adb and fastboot), I followed the instructions there (due to the stupid rule for new users, I can't post a direct link to it) old.reddit.com/r/LineageOS/comments/9h0aqy/cant_install_lineage15120180918_on_a_google_pixel/e6nbqg6/ and it worked

My OP 7 PRO(GM21AA) is being completely stuck at Fastboot.

Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.

Maybe THIS can help you?

Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.

Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone

lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes

Stuck in CrashDump Mode

I just purchased a new OnePlus 7 Pro yesterday and immediately set about rooting it. This is the process I followed:
fastboot oem unlock
fastboot flash boot twrp-3.3.1-4-guacamole.img
TWRP: Install > Select Storage > Internal Storage > Magisk-v20.3.zip
TWRP: Wipe > Format Data
I rebooted and was confused when I wasn't rooted. It seemed the last step had undone my root, so I went back into TWRP and installed Magisk again this time without formatting data. When I rebooted I had root and all was well.
However, there was an OEM update available that warned me it would remove root if I installed it. I found this guide to install an OEM update without losing root, which basically says to download the update via Oxygen Updater and then install it from TWRP. On step 6 is says to select the "Inject TWRP after install" option, but this didn't exist in my TWRP. I went ahead without it, thinking maybe it was enabled by default in my newer version of TWRP. The installation seemed to go without a hitch, but when I rebooted after I was stuck in fastboot. I couldn't boot my phone, nor could I get back into TWRP or regular recovery, only fastboot.
I tried flashing TWRP again using fastboot, but to no avail. I also tried running fastboot -w, but was still stuck in fastboot. I did some more research and found this comment which made it seem like all I had to do was download 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT from here and then run flash-all.bat. Once I did so I ended up stuck on the following screen:
Code:
QUALCOMM CrashDump Mode
--------------------------
dm-verify device corrupted Force Dump
kernel_restart
I can't seem to do anything at all with my device; not even turn it off. I tried holding the power button down for nearly a minute and no response from the phone. Is there any hope at all for my phone or have I properly destroyed it?

https://forum.xda-developers.com/oneplus-7-pro/help/mistake-kernel-error-t4029743
Same thing happened to me and I searched around a bit and found resolution. You can try what I did or try msm tool but search first as crashdump error is becoming common issue it seems
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed

Thank you so much! I thought I'd corrupted fastboot and permanently bricked the phone.
Once I was in fastboot I used tool all in one to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip onto my phone by picking Flash Factory Images, and now it's back up and running.
jasons1004 said:
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed
Click to expand...
Click to collapse
This was the magic trick I needed to know. Holding both volume buttons didn't quite work for me. I held them both down for over a minute and nothing happened. Then I tried holding down the power button and that seemed to work after several seconds. I didn't hold down volume down quickly enough the first time, so I had to do it again. I held both volume buttons and the power button for over a minute, but again, nothing. I tried a couple more times and got it to work. Haven't been able to figure out exactly what causes it to exit the CrashDump mode, but the volume buttons together seems to be the important part.

This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?

altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
Just use tool to flash 9 then after first boot fasboot flash whatever 10 build you can find. Then after first boot of 10 try boot twrp and install twrp.
Honestly I just used the tool to root and flash recovery. There is a button for that and just pick your files. Good luck

altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.

redpoint73 said:
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Click to expand...
Click to collapse
Ah, I was using the Official TWRP App to get the images so I was under the impression that twrp-3.3.1-4-guacamole.img was the latest. I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
redpoint73 said:
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.
Click to expand...
Click to collapse
This is good to know. Thanks.

Just to follow up, I applied the available OTAs through the phone settings (up to bulid 10.3.0.GM21AA) and then followed the More articulated but fully functional instructions to install TWRP 3.3.1-74 Unified Unofficial Q. Everything went well and I'm now up to date and rooted. Thanks again to both of you!

altayh said:
I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
Click to expand...
Click to collapse
That is the correct TWRP to use ("Unofficial" version -74), as it appears you have already determined.
I don't know why the "official" versions have fallen so far behind. It's been months stuck on version -4, so it seems that they have stopped going "official" for some reason. No matter, the unofficial versions are working fine (and in fact required for Android 10 as you now know), so the "official" tag seems like a technicality.

On these OnePlus phones I don't know why they love Qualcomm Crashdump mode. I fixed it sort of like you, but this worked 100%. You hold all 3 buttons (power, vol up, vol down) and you bypass the crashdump (takes several seconds 5 maybe 10), just quickly let go so you'll be in fastboot mode and can work your magic to fix the damn thing....
I even contacted OnePlus on an 8 they had no idea what to do...

Fastboot flash boot recovery.img <-- bad idea
Fastboot boot recovery.img <-- provit

Android Recovery: Issues flashing via ADB or external SD card

Hey,
following happend: I dirty flashed LOS 17.1 february update over december version following the instructions ivan gave. After flashing gapps and magisk I flashed the newest TWRP image.
Everything went well (at least it seamt so) I booted to LOS and set up new fingerprints (had to deleate them before flashing), started first app (spotify) and screen went black and phone restarted. Than I got the the FRP Lock message and wasn't able to boot agian neither to LOS nor to TWRP.
Everything followed is here. Tldr: I wasn't able to reflash Stock Rom with Odin no matter what I tried and got lost bettween download mode and nothing.
However I somehow got Android Recovery working!! This is what I can and cannot do:
chrisrevoltes said:
Now I'm able to boot to download mode and original recovery but not to system.
This is what Recovery shows:
View attachment 5218201
I can wipe data and cache partition, but not system partition.
I can view the logs, but I'm not sure what they are telling me....
I can view my external SD card, but trying to install ether TWRP, LOS or the stock image aborted with an error Update from external storage is disabled following a reboot to recovery. Any idea how to enable that?
ADB seams to be working. It can find the phone, although there is an message Stopping adbd... on the phone.
View attachment 5218209
adb devices -l shows:
XXXXXXXcf0cd263704 sideload product:heroltexx model:SM_G930F device:herolte transport_id:8
Sideloading the stock image or TWRP results in: Total xfer: 0.00x in console and adb status 1 on phonescreen with phone reboot to recovery.
Any other adb command (except those three getter) has ether no effect or results in an error.
Any further attempt to flash again with Odin results in the same errors like described in my last post.
Any ideas? ADB or external storage seams like a good way. But system partition worries me.
Click to expand...
Click to collapse
Can anyone help me?

Some time ago I had a Samsung S6 Edge G925I with which I had the same problems and errors as you. After an intense week flashing systems and without getting it to work, I took it to a colleague who has box and other tools to unbrick, unfortunately he discovered that the problem was hardware, more specifically emmc memory problem, I had to resort to changing the plate and problem solved. I would advise you to try all the firmwares that you can from your binary and with old versions of Odin, without opening as administrator, I hope you are lucky; I'll keep thinking if I can think of another solution, regards.

Thanks! I have finally made it. It took my the third day (thanks to covid home office) but I'm now up again with new LOS (but old TWRP).
For the record: My last try was using an older and modified version of Odin (3.13 here) and flashing the newest stock image with extracted PIT file. After 3 minutest it finally booted.
Im not sure if it was the older Odin version (some recommending using v3.14 for devices newer 2018) or the modified Odin version.