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

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

Related

wiped everything, no OS installed, TWRP restarts on flashing.

Long story short I was running latest nightly of cm13, I decided to flash to cm14 to try nougat. I had backups, during the process I pulled an idiot and wiped everything dalvik, system,data,internal storage,cache . So now I have no backups, I can still get into TWRP and attempt to flash Roms but I've tried countless ones and same outcome, TWRP just restarts half a second after it tries to flash, I've even tried the stock rom with no luck.it starts and gets to MTP enabled installing "name of rom" and then reboots . I've been using a tablet to install the Roms onto an sdcard and then using the sdcard to flash, I'm hoping it's an sdcard issue and I'm waiting to get the laptop to try and put the Roms on internal phone storage and try. I'm hoping I won't have to go back to unroofed stock using kdz tot. If anyone knows what's wrong please help.
Well I tried flashing to stock and can't get into download mode, computer won't recognize phone. So I decided to try updating Twrp flashed the image, rebooted and now I'm stuck on [11050] fast boot mode started. Nothing gets me out of that.

Issues with installing CarbonROM on the K1 -> Bootloop

Hello guys.
Last time I rooted and installed a Custom ROM was like 7-8 years ago with CM5 or so. So I'm not really up to date.
On my K1 tablet, I wanted to install the CarbonROM. Tablet runs Nougat.
The Root was successful, used fastboot for TWRP recovery. (Version 3.1.1 and 3.0.2, tried both). As in many tutorials described I wiped data/cache before installing. Installed CarbonROM (latest version) + gapps micro for 7.1 then wiped cache/dalvik and rebooted.
System then was stuck in bootloop forever, waited about 20mins but nothing happend.
Managed to backup by hard-reboot into recovery/adb and flash twrp again. Tried this time with twrp version 3.0.2, same issue.
I know about the presence of "blob", whatever it is. But since a few guides use it, and few dont, I tried with once with it but managed to land in bootloop again.
Tried with CWM but it didnt even recognize my SD card, or confused the internal storage as sd card. Moved the CarbonROM to the internal storage then and tried to install it. After boot image there was an android with a red "!" and "no command". Vol up + pwr -> recovery. rebooted. Still had the firmware from before, nothing happend at all.
I don't know anymore what to do to get CarbonROM installed and actually started.
Anybody got ideas or a actually a solution?
Greetings
Try a different ROM, or try another gapps (I've often had to mess with different gapps on AOSP ROMs on previous devices).
As for just getting the phone working again, you should have made a TWRP backup before trying to flash a custom ROM. Then you could have just restored the backup.

Please help! My phone doesn't want to boot into the system.

After I unlocked my bootloader of my Xiaomi Mi A1, I wanted to boot into TWRP by using this command: fastboot boot twrp.img but it wouldn't do anything so then I typed 'fastboot reboot' and it started to reboot and went onto the screen with the MI logo but then the screen went blank, the phone vibrated and it started rebooting again. I left it for a while and when I returned, it was still rebooting constantly. I do not know what is happening but I tried to lock the bootloader and then boot into recovery but that didn't work. I managed to somehow get into TWRP (not knowing how) twice and the first time I just rebooted and the second time, I factory reset my device. From that point onwards I couldn't get into TWRP because I was trying to flash Ressurection Remix rom if I could get into the recovery. My phone is not yet rooted.
Good/Bad news
I installed a different version of TWRP and was able to boot to TWRP successfully so I installed Lineage OS 15.1 and it said that it can't mount '/system' or '/storage' as it doesn't exist after that, I booted and it went into some kind of Lineage OS recovery and I
didn't know what to do with it as applying an update from SD card didn't work so then I installed the pixel experience ROM which also put me into a recovery and the apply update from SD card didn't work as it says 'couldn't mount /sdcard Installation aborted.
Instaling an update from ADB doesn't work either as it tells me to sideload the zip file which I did and nothing happened. Whenever I choose reboot system now, it just reboots back to the recovery.
My phone is not yet rooted but if that would help in any way, I could root in TWRP.
Please help, I don't know what to do.

[Q] SM-G928F / zenlte logo bootloop after twrp flash

I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.

TWRP doesnt show anything in install

hey guys im kinda new to this stuff
i think there is accidentally wiped out awaken os i installed
so here is what i did
i installed twrp
installed magisk
booted to Oxygen os and set up magisk
went back to twrp and flashed awaken os but forgot to flash finalize zip, the device restarted
now i thought it was necessary so i went back to recovery even though awaken was working fine
thats where things went downhill
the recovery was from awaken os
i used adb to boot using twrp.img from my pc
i dont remember what i did exactly after that as i was in panic mode (sorry)
somewhere in between there was the "random names in install folder" error coming up a couple of times
i tried wiping internal storage but it didnt work
basically
when i boot to system it goes back to twrp
i went to install awaken os again i cant access the internal storage through my computer
and twrp doesnt show anything in sdcard
there is also no mount storage button in mount option of twrp
have tried lots of different methods from the internet
tried wiping some things
tried pushing the file from pc as suggested by some article, cmd got stuck and didnt push it completely (or maybe i wasnt patient enough)
what do i do now
ask me for any info u want from my side

Categories

Resources