Database Develop

CM13(20151128) Broken recovery, Won't flash.

I use TWRP 2.8.7.1(which was flashed to the phone) and now after flashing this nightly version, the recovery gets stuck on the TWRP screen and flashes every 60 seconds, but never lets me use it.
I've searched through all the forums, but can't find anyone else with this problem. I just want to flash CM12.1 Snapshot, but I can't without the recovery working.
Everytime I flash the same recovery(TWRP2.8.7.1), the bootloader gives me the error "Mismatched partition size". I've tried "Fastboot boot TWRP2.8.7.1.img, but it sits stuck on the loading TWRP screen. I've cleared the cache, but still nothing.
The only recovery that I can get to work is CWM by booting the .img from the bootloader, but that still does nothing because none of the directories will mount, so I cant flash from the recovery.
I'm waiting on motorola to send me the stock files and just reflash stock and start from scratch, but I really want to save my data.
Does anybody have any clue as to what I'm doing wrong before I reset to stock?

Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom

uluf said:
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
Click to expand...
Click to collapse
Nope.. didn't work. I had the 5.0 files from motorola that I flashed, and I'll update from there.
I really wish motorola would leave those files open to download instead of having to wait... sucks not having a phone, but I survived.

i have the same issue, any idea how to fix it ?

Serious help needed; completely broken 3T

UPDATE: I was able to install stock recovery through BOOTLOADER (it started working again) and I tried sideload 4.1.7.zip that way. It seemed to work for a while, but unfortunately, sideloading crashed. Same for 4.1.6, update fails around 45%. Phone says INSTALLATION FAILED. Any thoughts?!
Hi guys,
I'm a longtime flasher of phones, but my wife today jacked up her 3T beyond the point that I know what to do. In short:
Her phone was rooted, had an unlocked bootloader and TWRP installed. She updated (despite my endless begging never to do that) the OTA, which crashed her phone. Duh. Not smart. The problem: the phone would not restart the OS anymore. Upon restarting, the phone immediately jumped to TWRP and hung at the splash screen (which takes a while to load, but she doesn't know that). She panicked, rebooted the phone a bunch of times before giving it to me.
I was able to get into TWRP eventually, and figured I'd manually install the newest 3T firmware. This is what I did:
First, I updated TWRP through TWRP, to the most recent version. This was successful. Then, this happened:
Downloaded 4.1.7 from the OnePlus website
Placed it on the phone's internal storage
Went into TWRP, wiped Dalvik, Cache, System etc. (leaving Internal Storage in tact)
Flashed the firmware
I've done this thousands of times, never fails. Except now.
After flashing (which was supposedly successful, as I did not receive error messages), I hit 'reboot' and TWRP told me 'NO OS INSTALLED - WANT TO REBOOT ANYWAY?'
That is bad, right? So, I did not reboot, stayed in TWRP and ended up trying to wipe internal storage, thinking I could then add the .zip with the firmware again later and try flashing again. Just a clean phone, you know? I was wrong. I cannot copy anything to the phone right now, so I can't flash anything (because I can't put anything on the phone).
I'm trying to sideload things now through TWRP (adb sideload) and regular fastboot (either the firmware 4.1.7 or 4.1.6 - I've even tried flashing the stock recovery through fastboot to try and get the stock back, so I can sideload the firmware through there), but nothing works.
If anyone knows what to do, or can give me an outline on what to try, I'd be very helpful. The situation right now:
3T, without OS or ANYTHING on the phone
With functioning TWRP
Only recognized in the command prompt when in TWRP, not when in BOOTLOADER
Phone does not allow things to be copied to the phone via my laptop.
On behalf of my extremely upset wife, I thank you!

@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.

Siddk007 said:
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.

Donaghy said:
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Click to expand...
Click to collapse
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Sent from my OnePlus3T using XDA Labs

Siddk007 said:
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Click to expand...
Click to collapse
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.

Donaghy said:
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Click to expand...
Click to collapse
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Sent from my OnePlus3T using XDA Labs

Siddk007 said:
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Click to expand...
Click to collapse
I don't own an OTG cable. The only USB option there is, is within the ADB menu in the recovery.
EDIT: locking the bootloader seemed to have made things worse, as I now cannot get the .zip files with the firmware on it to be accepted by ADB/the phone... God, this is a gigantic mess..

I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.

C3C076 said:
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
Click to expand...
Click to collapse
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.

Donaghy said:
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Click to expand...
Click to collapse
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs

Siddk007 said:
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Whichever is the most recent one that is on the OnePlus website. I downloaded the .img off of their website.

I've had a similar issue, and I tried a billion times on trying to reflash Stock OOS 4.1.0, and sadly nothing happened. I then tried LineageOS by SultanXDA, nada.
So then, I said "Scr*w my data, I'm going to start anew", and I tried the Unbrick Tool, and Voila, new phone with OOS 3.5.X. Not the latest, but it's working.
I suggest you try that mate, you can find it over here.
Cheers!
P.S. - Love your profile pic.

If you sucessfully flashed 4.1.7 then I'd just reboot into system. TWRP sometimes says "No OS installed" if /system was wiped prior to flashing.
Regardless, I recommend you do these things now (if you havent already) and report back:
-Unlock bootloader (fastboot oem unlock)
-Flash TWRP* recovery, not stock. (fastboot flash recovery twrp.img)
-Boot recovery (fastboot boot twrp.img)
-Wipe data + system + cache + dalvik from TWRP
-ADB sideload in advanced section of TWRP
-from your PC: "adb sideload oos417.zip"
-from TWRP: reboot into system (ignore "No OS installed")
If you follow this and its succesful, everything will be fixed
* flash the twrp by xda member eng.stk, not the official one: the only place I can find his TWRP is in the 3/3t toolkit zip. So extract the v5 zip and use the "TWRP_recovery.img": https://drive.google.com/drive/u/0/folders/0B1cephDrsyt_ZzJ1cXpUUlVhSzg
Edit: Instead of doing all this manually, you may want to use the toolkit. See if your device is recognised

Thanks for the help, everybody!
I used the unbrick tool, which worked! I got the phone 'alive' again.
New problem: Right after successfully booting the phone again, I set up the phone (so: clean install, no root, stock recovery, straight out of the box, you know what I mean) and then proceeded to download the OTA that OnePlus pushed to the phone (4.1.7). It downloaded quickly, but the installation has been stuck for almost an hour.
The phone says 'Updating, please wait - do not turn off your phone', and the blue bar is filling. Well, not filling, as it has been stuck at about 10% for an hour.
Is this normal? If not, what can I do? Thanks again!

I turned the phone off and was able to successfully sideload 4.1.7 via ADB. Upon updating, the phone gave me a notification (blue and white letters) that the "DECRYPTION IS UNSUCCESSFUL. The password you entered is correct, but you have to perform a factory reset to use your phone".
So I did another factory reset in recovery, rebooted, and it's up and running, with 4.1.7 on it! I can't believe we got it back from the dead. Thanks everyone, for your help! Really appreciate it!

Can't wipe data, can't install stock recovery, phone stuck in boot animation

Hello, I've been trying to bring back to life this old XT1068.
In the past years, I had installed several ROMs until one day the phone stopped working (probably I made some mistakes like flashing something not supposed to be flashed on this device, probably) and since that moment if I turn it on it remains stuck on the boot animation (the coloured google dots moving...).
I tried everything. I have TWRP 3.1 installed, I tried to wipe everything, I tried factory reset, I tried to erase the internal storage, I tried to install new ROM, including a stock ROM and the stock recovery. The result is always the same: no errors at all in TWRP, but it's like nothing changes. It does not boot and if I go to TWRP I can still see files that I put in the phone years ago, after I tried every possible wipe. Imagine that I still see the WhatsApp folder of years ago.
As I already mentioned, I also tried to flash a stock recovery: the process finishes without errors but if I reboot to recovery, I always end up in TWRP.
The only thing I can do is to reboot into recovery or fastboot.
The phone is recognized by the computer ("adb devices" / "fastboot devices").
Does anyone of you guys ever experienced something like this?
Thanks in advance.

I have exactly the same issue. Did you find a solution?

I never got that problem, is pretty strange, i think some zip you flashed before is still installed automatically, for example, there is some option on supersu called survival mode, if you enabled that, i think an supersu uninstaller zip could work, also you can try to install any rom, install supersu and check on supersu settings
---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------
Also probably some partition got damaged or anything, i recommend to flash an stock rom that flashes many things except for nvdata and nvram partitions because it could make you can't get signal if those partitions are from another zone

Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please

eagledipesh said:
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
Click to expand...
Click to collapse
Hello!
I`ve done the process to install via mfastboot the stock IMG, no errors at all. When the phone reboots it goes into the previous installed rom boot animation and stays there at bootloop.
I even tryed to install an updated TWRP recovery (3.4) via fastboot. Is shows "OK" but when it loads it is still the previous version.
It looks like the phone is "write pretected".
Any further suggestion?
Thanks in advance.
Allisson

Same problem here. I can accces the fastboot menu via "VOLUME DOWN + POWER" but whatever I try, the red error message comes up. I can boot into twrp via USB/PC but i cannot install it. I cannot factory reset.
when I reboot from TWRP I come to lineageOS boot loop.
ANY IDEAS?

Moto G7+ Flashing Lineage fails -> Touch doesn't work anymore - Brick?

Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.

probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.

Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.

joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.

digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.

Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.

Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!

I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.

I got stuck in a 'recovery bootloop' and I'm desperately trying to rescue my data

Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!

Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.

V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.