Database Info

[Q] Stuck in recovery some time after flashing cwm

Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...

If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).

Sideload worked perfectly! Thank you so much!

cm11 working only TWRP here , with cwm appears same error

mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse

Help please Bug Moto g XT1033

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

Oneplus one(bacon) boot and recovery partition crashed. Can fastboot. phone brick

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.

[TWRP][BRICK] Motorola Moto G LTE 2013 Peregrine - Fail entering Recovery Mode

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.

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