Hey guys, just got a NOS One Vision to install LineageOS but when I try to fastboot flash recovery "LineageOS zip"
I always get an error because the recovery partition does not seem to exist.
Then I tried TWRP on external storage. TWRP can boot then install itself: boot recovery from volume down boot up,
but then TWRP always gives an error 255 on flashing lineageOS that way.
Please help!
Just so you know, the phone came with android 9. After my tries, I factory recovered it and it is now at 11
but I did nothing since.
Any ideas?
Update: After letting the Motorola recovery tool upgrade the phone to 11, installing LineageOS went as per instructions
MasterGoa said:
Update: After letting the Motorola recovery tool upgrade the phone to 11, installing LineageOS went as per instructions
Click to expand...
Click to collapse
Where is the instructions plz tell me
Related
I own a moto g xt 1033 and installed cyaonogem mod 13, I used to recovery twrp,but he did not quit the cyaonogemmod robot image, then restarted and tried to reinstall the android back , but when the device will start it appears the image of the unlocked bootloader and restarts and it becomes infinite.
when I try to clear system cache, the TWRP error , it seems the TWRP is corrupted , what can be ?
If anyone can help me I can post a video on youtube showing defects
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Professor Gibbins said:
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Click to expand...
Click to collapse
Sorry for the delay....i using twrp 2.8.5.0, I stored in the internal storage to cyanogemcm12, It was executed wipes, install cyanogemmod, but got stuck in logo cyanogem,
I returned the recovery was made and wipes again, and install Rom XT1033 Android 4.4.4 KitKat Dual Chip, unfortunately now he does not leave the image "boot loader" unlocked).
*I have access to fastboot via adb!
*I have access to recovery!
*however after all these errors, the TWRP does not allow Wipes, and also appears error installing rom.
*When I install a rom stock fastboot , this does not seem a mistake, but goes into bootloader and is restarting without stopping
help you if I put a video on youtube?
I will record a video and share tomorrow.
Thanks
Sorry my english
Professor Gibbins said:
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Click to expand...
Click to collapse
i using twrp 2.8.5.0, I stored in the internal storage to cyanogemcm12, It was executed wipes, install cyanogemmod, but got stuck in logo cyanogem,
I returned the recovery was made and wipes again, and install Rom XT1033 Android 4.4.4 KitKat Dual Chip, unfortunately now he does not leave the image "boot loader" unlocked).
*I have access to fastboot via adb!
*I have access to recovery!
*however after all these errors, the TWRP does not allow Wipes, and also appears error installing rom.
*When I install a rom stock fastboot , this does not seem a mistake, but goes into bootloader and is restarting without stopping
i have link youtube
Thanks
Sorry my english
To get the phone working again, I would suggest flashing latest 5.1 version of these factory firmware images (for your exact device model) through fastboot.
To flash CM13, try using TWRP 3.0.2-0, and the latest CM13 snapshot. Note that the first boot of Cyanogenmod can take a long time (20+ minutes).
Professor Gibbins said:
To get the phone working again, I would suggest flashing latest 5.1 version of these factory firmware images (for your exact device model) through fastboot.
To flash CM13, try using TWRP 3.0.2-0, and the latest CM13 snapshot. Note that the first boot of Cyanogenmod can take a long time (20+ minutes).
Click to expand...
Click to collapse
I tried all these Step
I think TWRP is corrupt, or the fast i dont know , it installs the features, but not fixed
link my video youtube.com/watch?v=ZGgpL_JCQSY
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.
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
Please, help me, is it a hardware problem that can't be fixed or does it have solution?
Flash stock lollipop 5.1 ROM
later flash latest twrp recovery image file.
Later download latest lineageos from official website and nougat opengapps from official website
This should solve your problem
If you still face problem visit lineage wiki page about falcon for detailed guide to install lineage ROM
SunilSuni said:
Flash stock lollipop 5.1 ROM
later flash latest twrp recovery image file.
Later download latest lineageos from official website and nougat opengapps from official website
This should solve your problem
If you still face problem visit lineage wiki page about falcon for detailed guide to install lineage ROM
Click to expand...
Click to collapse
Hey, I tried to flash stock lollipop ROM in fastboot mode many times but it doesn't boot into the system, when it finishes I try to boot the phone but it boots me into fastboot mode again, it just can boot into fastboot, ¿what can I do?
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
silencefalls said:
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
Click to expand...
Click to collapse
Try these steps in order, stopping if a particular works.
- Ensure you installed the correct TWRP image for Peregrine, not for Falcon.
- Try entering fastboot mode manually, if you didn't already try to: Turn off the cell phone, then press and hold the Volume Down button for couple of seconds and while still holding Volume Down button press the Power button for a little bit and then release both buttons at the same time.
- If you updated TWRP with the Official TWRP app, try flashing it manually in fastboot mode: fastboot flash recovery TWRP image name, copied exactly. If you did flash it manually, try installing via the Official app.
- Make sure your downloads for both the Rom and TWRP image are not corrupted - re-download with md5 sum checks and re-flash with verification.
- Backup all your data (including on SD Card) and clean flash TWRP & the rom again (i.e., wipe System, cache, Dalvik cache and format/wipe Data - important).
- If issue persists, re-flash the previous version of the TWRP or rom, depending on which one is the culprit, and report to developer.
silencefalls said:
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
Click to expand...
Click to collapse
This thread is quite old (around 2 years old). But nevertheless, I am sharing my experience so that it may help someone facing similar problem. I have a Moto G 1st Gen Falcon which was running Lineage OS 14.1 based on Android 7.1.2. I was planning to update it to Android 10 based Unofficial Lineage OS. I downloaded latest TWRP zip to update existing TWRP. I rebooted into TWRP and flashed the zip. It installed perfectly. Then to check it attempted to reboot into recovery. But it instead went to fastboot mode with the error "Invalid boot image size! failed to validate recovery image Boot failed". I tried botting into recovery but was not working. I tried flashing through adb a different file but it was not working. Then what worked was booting into recovery using the command Fastboot boot recovery recovery.img. After that I was able to flash Android 10 and now everything is working perfectly.
Need some help, I keep getting a infinite boot animation. I tried to install LineageOS (thread) on my G920F three times and let them all boot for about an hour without success.
This is the order of how I flashed it:
1. Wipe Davik, System, Data and Cache
2. Flash the LineageOS zip
3. Flash the Zerofltexx kernel img
4. First try flashed OpenGAPPS, second try flashed MindTheGAPPS and third try didn't flash GAPPS at all
5. Reboot and wait, after an hour still booting
Any idea's of what I'm doing wrong?
Fixed my issue!
Hi!
I had the same issue as you, followed the guides and installed TWRP through ODIN and flashed the OS through TWRP to boot it.
When I booted the device it just got stuck indefinitely on the loading animation (the Lineageos loading logo in my case).
Since you and some others had the same issue as me I assumed it was something to do with a new version of some software.
I resolved the issue by installing an older version of TWRP through ODIN,
I installed the TWRP version 3.2.3.
And then I flashed the same ROM with the GAPPS again.
After the ROM and GAPPS I also flashed MAGISK aswell from the magiskmanager website.
Download the MAGISK Zip.
After I flashed the ROM, GAPPS and MAGISK through the TWRP 3.2.3 it booted as intended.
Hope this works for you aswell!
how long did it take to boot
First Boot needs longer...up to 15 minutes is possible.
solonf
speedson
i have same probleme wtih my samsungs6 g920f i wiil try it ...hope it work ....
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
If you can give us exactly the steps you follow
Lineageos 17 boot animation stuck
krimnian said:
If you can give us exactly the steps you follow
Click to expand...
Click to collapse
Steps (I have followed the instructions to the letter)
Wiped all partitions (advanced wipe)
formatted DATA partition
rebooted back into recovery
installed Lineage 17 and Gapps
Rebooted to system and left it all day, still stuck on boot animation
Tried again without gapps same results
Tried other roms they work, AOSP showing no encryption which works fine
What am I doing wrong? Do I have to flash different kernel? TWRP 3.3.1 installed.
Im using G920L it booting to long then just go to twrp anyhelp?
Helpful
crmcc said:
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
Click to expand...
Click to collapse
this was extremely helpful as soon as i unchecked installing with twrp it worked immediately.
crmcc said:
Remove the TWRP from the phone via the advance key in TWRP. I had tried several ROMs and Gapps only to get stuck on the boot screen then back to the TWRP screen. Removing the app made my new rom boot in less than 10 seconds.
Click to expand...
Click to collapse
Can you explain the process a little?I have flashed lineage os 18.1 in moto g5 plus , but it's stuck on lineage booting animation.
rog__ said:
Can you explain the process a little?I have flashed lineage os 18.1 in moto g5 plus , but it's stuck on lineage booting animation.
Click to expand...
Click to collapse
For reference, formatting data after install seems to often be the solution when flashing a new OS to a Moto G5 Plus.
gamemaster2030 said:
Need some help, I keep getting a infinite boot animation. I tried to install LineageOS (thread) on my G920F three times and let them all boot for about an hour without success.
This is the order of how I flashed it:
1. Wipe Davik, System, Data and Cache
2. Flash the LineageOS zip
3. Flash the Zerofltexx kernel img
4. First try flashed OpenGAPPS, second try flashed MindTheGAPPS and third try didn't flash GAPPS at all
5. Reboot and wait, after an hour still booting
Any idea's of what I'm doing wrong?
Click to expand...
Click to collapse
These steps solved my issue. thanks