Database Info

[Q] Can't get into recovery, can't flash new recovery

Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE (updated with latest omni versions as they became available).
Everything been working fine until two days ago, when Xoom froze. It had happened before a couple of times and a reboot had solved the problem. Did that, and this time it got stuck in a bootloop, only getting as far as the Omni splash screen before rebooting. Few reboots later, nothing improving, and then it didn’t get past the Motorola M splash screen.
Tried booting into recovery, frozen at teamwin splashscreen. Nothing was working. Rebooted few time, same thing. Connected to power, charged til green, left for extra 30 minutes, tried again, same problem. Switched off. Came back to it today and....
All of the following done via Fastboot:
Tried flashing non bigpart TWRP (R.A.H._TWRPv2.6.3), still stuck at teamwin splash screen. Flashed Clockwork recovery, booted into recovery fine, but couldn’t see memory card. Flashed Clockwork recovery touch version, same problem. Flashed back to TWRP non bigpart, and it booted into recovery fine, sdcard mounted fine, seeing all files. Excellent. Decided to reflash bigpart version, used reboot option in TWRP, it tells me there is NO OS INSTALLED.
Ok, that’s a bit odd. Must be corrupted or something, but might explain the original freeze and bootloop and then not even getting to Omni splash screen. Swiped to reboot. Flashed bigpart version of TWRP. Rebooted into recovery. Back to original problem, stuck at teamwin splash screen. Left it for 10 minutes just to be sure. No joy.
Tried retracing steps, flashing Clockwork recovery. Reboot. Teamwin splash screen. WTF? Try flashing Rogue recovery. Reboot. Teamwin splash screen.
Kinda confused. It’s like it’s telling me it’s successfully flashed but it hasn’t actually done anything. Power everything down, disconnect everything. Start again. Flash Clockwork recovery, reboot, displays teamwin splash screen, sticks. Flash TWRP, non bigpart, displays teamwin splash screen, sticks. Reboot. Flash TWRP bigpart. Reboot, displays teamwin splash screen, sticks.
Walk away in disgust so as not to throw something at Xoom.
Ok, TL-DR recap.
Worked fine for months
Two days ago, froze on Omnirom logo, got stuck in bootloop
After few reboots didn’t even make it to Omnirom logo, stuck on M screen
Flashed TWRP recovery, non bigpart, stuck at teamwin splash screen
Flashed Clockwork recovery, got into recovery, no SDcard
Flashed Clockwork recovery, touch version, same problem
Flashed TWRP non bigpart, got into recovery, could see SDcard and files, rebooted from within recovery to flash bigpart version, tells me NO OS installed
Reboot
Now, regardless of which recovery I flash it goes straight to teamwin splash screen and stays there.
Help

Bump
Come on guys, 100 plus views and no replies? Surely somebody has an idea?

At the bottom of your tldr
Flashed twrp.. booted into recovery flashed bigpart twrp then says no OS.
It will say no OS cause bigpart would have wiped everything to resize the partition.
I've updated my TWRP to support bigpart and a few other things. Grab it from the pined thread by myself flash it and wipe everything but sdcard.
THen from the terminal in twrp type
df
Ensure the system is around a gig if so then you have repartitioned your /system
Then flash your bigpart Rom and gapps should be good to go from there
sent from::§::

Cheers for the reply, but I'd already had it flashed and running fine for about three months, as I said in my first line:
Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE
Actually, reading that back, it may not have been clear enough that I meant I'd been running it that way for a while.
Oh, also in the TLR, I meant I rebooted so that I could flash TWRP bigpart from ADB/FASTBOOT, not that I flashed it from within TWRP (which is what I should have done since it turned out to be the one and only time I managed to get past the splash screen). It told me there was no OS installed after I flashed the non bigpart version of TWRP and before I rebooted from within the recovery.
My point is I can't get past the splashscreen, no matter what I do, so I can't use any of the recovery / flash options in TWRP. I also can't flash any other recoveries using ADB or FASTBOOT because no matter what I flash it still stays stuck on the TWRP splashscreen when I reboot into recovery, whether I use FASTBOOT REBOOT or reboot using the volume rocker.
runandhide05 said:
At the bottom of your tldr
Flashed twrp.. booted into recovery flashed bigpart twrp then says no OS.
It will say no OS cause bigpart would have wiped everything to resize the partition.
I've updated my TWRP to support bigpart and a few other things. Grab it from the pined thread by myself flash it and wipe everything but sdcard.
THen from the terminal in twrp type
df
Ensure the system is around a gig if so then you have repartitioned your /system
Then flash your bigpart Rom and gapps should be good to go from there
sent from::§::
Click to expand...
Click to collapse

codliness1 said:
Cheers for the reply, but I'd already had it flashed and running fine for about three months, as I said in my first line:
Ok, so I have an MZ601. Flashed with R.A.H._TWRPv2.6.3_BigPart_selinux and omni-4.4.2-20140321-1754+0100-everest-HOMEMADE
Actually, reading that back, it may not have been clear enough that I meant I'd been running it that way for a while.
Oh, also in the TLR, I meant I rebooted so that I could flash TWRP bigpart from ADB/FASTBOOT, not that I flashed it from within TWRP (which is what I should have done since it turned out to be the one and only time I managed to get past the splash screen). It told me there was no OS installed after I flashed the non bigpart version of TWRP and before I rebooted from within the recovery.
My point is I can't get past the splashscreen, no matter what I do, so I can't use any of the recovery / flash options in TWRP. I also can't flash any other recoveries using ADB or FASTBOOT because no matter what I flash it still stays stuck on the TWRP splashscreen when I reboot into recovery, whether I use FASTBOOT REBOOT or reboot using the volume rocker.
Click to expand...
Click to collapse
I'm stuck in TWRP v2.6.3.0(RunAndHide05 Edition) cant mount system, wipe any data tried or install any rom. Tried flashing different recovery via fast boot but stays the same
*No Os installed error

@crazylegs90 did you figure this out man? Im stuck at twrp start screen..

[R7SF] Stuck in TWRP Recovery mode only, flashed rom but unable to boot into it.

After flashing TWRP and being successful, i installed LineageOS 14.1 and gapps as you have guided on your posts, i saw that there were some old folders that were left over from the many apps my wife have installed previously, so i decided to do a factory reset. After pressing factory reset, the phone restarted and booted into TWRP recovery, which then i clicked on "Format Data" from the wipe tab.
Things went really south from here on, i am unable to boot into anything i have flashed (i tried flashing LineageOS 14.1 and gapps). Once the rom and gapps are installed, the phone reboots back into TWRP again. it seems like the internal storage of the phone is still empty except with the 2 zip files i've put in. I am able to access TWRP Recovery and detect it as a R7S on my computer, but i cannot boot into anything else, its been stuck like that booting ONLY into TWRP ever since i've pressed "Format Data" which in this case is my mistake and i apologize, is there any solutions to unbrick the phone? Could anyone please help me? I would be very very thankful.
Edit: I have flashed a newer TWRP via TWRP itself under Install > install image. previously running on 3.0.2-2-r7sf-final.img but i tried downloading from TWRP website twrp-3.1.0-0-r7sf.img and flashed it vi TWRP since i cannot get into fastboot. phone booted up after wards into OS and made backups and kept it somewhere safe. was reading and panicking around the web for a good 10 hours

Twrp opening screen shown then device goes into bootloop.

I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro

[email protected] said:
I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro
Click to expand...
Click to collapse
Try reinstalling the stock ROM, it'll delete any modification brought to the device...

OOS11 Broke TWRP and bricked my devices

My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.

Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com

humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.

Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?

Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards

Lenovo Tab 4 10 plus 30 second boot loop

How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?

I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.

pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/