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.
Related
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.
I have unlocked the boot loader on oneplus one long back. I tried to upgrade my rom to Resurrection Remix 7.1.1
I successfully upgraded the ROM and also flashed SuperSu in it. I wanted to flash the Opengaps Aroma 7.1 and that is where I ran into issue because of my stupidity.
I found from GitHub that there were some issues with twrp versions to run the aroma installer thus I tried multiple TWRP versions via (Google play - official TWRP recovery app) by downloading them and flashing it to recovery.
I have taken the full nandroid backup but unfortunately didn't keep it on external devices. So it was in the phone itself.
Now the issue -
When I tried flashing TWRP 3.0.2.0 from existing 2.8.4.1 I tried to run the Aroma but it didn't work. Then I tried to flash the recovery with TWRP 2.8.6.1 but Aroma failed again.
However, on the GitHub there was a info stating that known working TWRP recovery on Oneplus one is of TWRP 2.8.4.1
I tried to flash that into recovery and flash the Aroma, but it didn't boot into recovery with that image. Later I restarted the phone, and again flashed the latest recovery version 3.0.2.0
From here I ran into issue. When tried again to flash the Aroma, it didn't work. So I booted recovery again and in that I selected the recovery version 2.8.4.0 for both recovery and boot partition.
After that, phone is neither booting the system nor into recovery. I don't want to loose my data (which is in phone backup) and neither want to try Aroma again. (Even if all the 900mb data needs to be deleted.).
Can the XDA members confirm can I reinstall recovery working image (2.8.4.1) once again through the adb flash recovery <image>. And boot into recovery mode so that I can delete the boot partition once again and reinstall the ROM and data ?
I tried doing that once but one of the laptops which I had access didn't recognize the adb devices. May be the driver was not working for Win10 OS. However, on my personal laptop earlier I was able to run adb commands through CMD prompt. Currently, I don't have personal laptop and may get it by next week.
Can anybody please share me the links of working android driver so that I can install them on current laptop and then try adb commands from SDK to connect my phone.
Any suggestion from members would be of great help.
Note: Please don't suggest the methods to factory reset or lock bootloader to factory settings. As I don't want to loose all my contacts and data.
If there is a way to get just recovery working on the phone, it would be of great help. So that I can wipe other partitions and rebuild it again.
Thank You.
Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated
SuperSpasm said:
Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated
Click to expand...
Click to collapse
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.
Mannan Qamar said:
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
removed because I don't have link posting permission
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.
Click to expand...
Click to collapse
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg
SuperSpasm said:
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg
Click to expand...
Click to collapse
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
https://androidhost.ru/
Also instructions are in the zip.
Sparkrite said:
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
Also instructions are in the zip.
Click to expand...
Click to collapse
Tried downloading a rom from androidhost.ru- it had the update folder structure described,
and I put the unzipped dload folder into microSD root like the instructions said.
But pressing vol up+down+power doesn't load any update screen for me.
It just goes to bootloop again.
Is there anything else I can try?
Thanks
I unlocked the bootloader through mi unlock tool. I flashed official twrp from their site, 3.3.1-0-violet.img but when I tried booting it into recovery, it got stuck at twrp logo. Then I learnt that it's necessary to wipe userdata using fastboot first so I did that. Then, when twrp started, it was unable to install/wipe/mount any partition. Tried installing magisk using sideload, did work but then device stopped booting.
Figured out a way on how to fix the mount issue, twrp working fine, but then I accidentally wiped /system. Now my device only opens in fastboot, even though I've tried installing, erasing and reinstalling that twrp recovery as well as a couple of others I found in pixel experience forums for my device.
I've got all the stuff needed to install pixel experience, fcrypto disabler, xiaomi latest firmware and the rom itself. Can anyone guide me on how to install it using fastboot?
Also whenever I try booting the recovery image straight from fastboot, it says that command failed, too many links.
I can't boot into recovery via vol up + power button, fastboot doesn't recognize command fastboot reboot recovery.
you need to install stock rom ,then flash twrp but newer unofficial twrp and orangefox twrp boots into recovery even if system partition is empty.
try installing unofficial twrp or orangefox.
orangefox is recommended .
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.