Database Users

OP2 soft bricked, can't access recovery, not recognized by laptop

Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.

If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac

CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.

AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.

justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.

Can't access Recovery, only fastboot and the universal bootloader, please help!

So after stupidly trying to update twrp through twrp instead of fastboot, I can only access fastboot and the universal bootloader installed on the phone. If I don't do anything, the phone simply goes through universal bootloader and I see a small penguin before the screen goes back and I need to restart the phone again. However, in the bootloader I can select to go to fastboot which does work. I've tried flashing TWRP through fastboot (fastboot flash recovery twrp...) and it said success however after clicking 'reboot to recovery', the phone once again just boots to the bootloader and I'm back at square one.
Thank you so much if anyone can help!

FYI, you can update TWRP using TWRP. Nothing wrong with that, I do it all the time. It's faster and easier to do so.
You might have an incompatibility between bootstack and TWRP.
So, please provide us more info.
ROM:
Bootstack used:
TWRP version:
What were you trying to do besides updating TWRP?:

Funny thing... I'm having the exact same problem.
I instaled TWRP (3.1.1-0-9c3b7e99) using the AxonToolkit 1.2.1.
Everything went smooth with the toolkit. I could get into TWRP and did some back-ups (as recommended), then wipe Dalvik/ART Cache, System, data, cache, and finally, try to install LineageOS 15.1.
I used the files:
- ZTE_A7LOSv1_UniversalBootStack.zip
- A2017U_OreoModem.zip
- lineage-15.1-20180810-UNOFFICIAL-axon7.zip
UniversalBoot and Modem were installed correctly, but I got an error when trying to install Lineage. I can't remeber the error number but it said something like: "this ROM is for device ailsa_ii_axon7 but this device is ."
Since then... my phone is in eternal loop and can only get into Fastboot. Can't access TWRP.
Thanks in advance to anyone willing to help me.

Don't mind... I have it back.
After many reboots, It only seems that this is working different with the Universal O bootloader. On the main screen, I tap the volumen button, choose "Recovery", reboot, press the power button on the main screen, press it again, the Linux Pinguin appears, press power button again, and then TWRP is back.
After that, I got to wipe and do the normal ROM installation process.

Samsung J7 Pro Soft Brick after Oreo 8.1 update (no root)

Hi everyone...
Two days ago, and a few hours after installing the 8.1 update, my mom's J7 touchscreen was unresponsive, including the power button. It ran out of battery, and after I restarted it this morning, it goes to recovery mode after it tries installing system update and the No command screen is displayed.
I've searched on the web for hours and hours for solutions but none of them have worked, most probably because it requires the phone to be connected to the PC, and my PC (Windows 10) isn't even seeing the phone via USB (can't use ODIN nor ADB). BTW, the debug option most probably wasn't turned on prior to soft brick.
Phone Info:
SM-J730G J730GDXS5BRK1
No root
Error on recovery screen (the SD card has been taken out):
======================================
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
=======================================
Additional info: As I've mentioned, the power button isn't responsive, so I press the volume down button to choose the recovery options. I've tried all recovery options except for:
Wipe data / factory reset, as the phone data isn't backed up (mom doesn't want to lose the personal data as much as possible)
Apply update from ADB
Apply update from SD card
All other options are looping back to the recovery screen after installing system update screen.
Lastly, in recovery, there's an option at the bottom that states "Lacking storage booting". I'm sure that would mean something to someone reading this that would help solve the issue.
An OS downgrade or same 8.1 fix is preferred, as long as the phone data is intact. Any and all help would be much appreciated.

Try "Emergency Software Recovery" feature in Samsung Smart Switch for PC.
It could be a hardware issue as well. Clean your USB charging port with a brush and a drop of alcohol. Then dry with a hair drier.

Good evening, have you tried installing the latest version of the firmware by odin?
If not, try this.
probably its touch stopped working after the update because it was not original (already it has been changed) or it can be other cases ..
if you still can not install the newest firmware downloaded from the sammobile site you can do the second procedure.
Such you will find in this same forum.
In it you use the pc miracle box application and downgrade to 7.1.
this is the title of the post.
follow all procedures.
and it will be all right.
Fix Touch does not work on Samsung J7 Pro (J730G, J730GM) when updating Android 8.1
https://forum.xda-developers.com/ga...ix-touch-samsung-j7-pro-j730g-j730gm-t3850177
PS: Putting it into download mode: Turn the device on by holding the volume down buttons + Home + Power

Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.

Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.

Cloud1245 said:
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Click to expand...
Click to collapse
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.

Marius.Banderas said:
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Click to expand...
Click to collapse
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------
Cloud1245 said:
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
Click to expand...
Click to collapse
https://youtu.be/UOACi_sUDQY
do only steps 1, 4, 5, 6, 7, and 8 of the video description.
Will be all right!

Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Before trying to flash TWRP, first flash a full stock firmware and make sure your can at least boot all the way up to the main screen.
Once that works, only then try to flash any custom recovery or custom rom.

Same prob
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!

uz91 said:
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
Click to expand...
Click to collapse
that is a drk error
you can modification the stock firmware with 7z program
1. open your stock firmware go to AP file
2. click rename than erase the (.md5)
3. extarct the file
4. find (system) file
5. make a (.tar) file with (7z) program with the that system file
6. flash
7. done

JiaYu S3 TWRP loop

Hello,
I am into a TWRP boot loop.
- I can boot into TWRP
- I can update ROMs
- I can update TWRP
- I can connect to the computer and send files using mtp://[usb:001,003]/
- I can Wipe ...
But when I reboot into the system, regardless of the ROM that I use, I get again into recovery
I have read in some posts that from the TWRP command one could try to clear the first sectors of the misc partition
For instance for a Lenovo ZUK Z2 (Plus) in https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14 it is said that this could help
"dd if=/dev/zero of=/dev/block/platform/soc/7464900.sdhci/by-name/misc"
but ... I cannot find the misc partition in /dev from the TWRP shell ("find /dev -name misc") !
Could someone help me with this one ? I would appreciate it a lot !
Regards

Same problem on MadOS 8.1 (MT6752)!
TWRP loop

Just flash old stock 5.1 Android ROM through Flash Tool. Its pretty easy. Then turn it, turn it off and wipe data. restart TWRP, upgrade TWRP and install new Android 8.1 and gapps. Turn the phone on and its finished. You can do recovery now for the next instalation if you want. I am doing this often because I have same problem for several months. Fortunetaly google backup works pretty fine so its not problem with installing apps again. The command you wrote above doesnt work for me.

I'm having the same problem. I was using my phone today, when it started to show wifi problems (couldn't connect); so, I rebooted it and its screen started to blink; when I rebooted it again, it automatically entered into recovery mode (TWRP). After this, the phone didn't boot normally (MadOS Android 8.1) anymore - only TWRP. Even when I try to charge it, it boots into TWRP mode instead of showing the battery animation.
In my attempts to solve the problem, I firstly reinstalled the MadOS 8.1 ROM but it kept booting into TWRP mode. So I flashed an old Android 5.1 ROM I got (connected and uploaded the device successfully with SP Flash Tools) but it also kept booting into TWRP (now an older version from the 5.1 ROM). Then I uptadated the TWRP and the OS again to MadOS 8.1 but the result was the same.
With any other alternative, I came accross this topic and tried the steps described above (practically identical to what I just did), but again I hadn't any positive results.
What else could I do?

Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.

imascara said:
Hello,
I have finally resolved my issue !!!
a) Using "SP_Flash_Tool_v5.1824_Win" and the "RC5_S3_16GB.zip" stock rom I flashed it using ---->>>>> "firmware upgrade" mode <<<<-------.
The option you can find it in Smart Phone Flash Tool, between the "Authentication File" and the table with the partitions.
b) Once done with the flasshing, boot the telephone into the Stock fimware
c) Boot into recovery (power + volume up) and flash the latest TWRP
d) Flash you new ROM
Do not hesitate to ask me if you have questions.
Click to expand...
Click to collapse
Thanks! With this method, I solved the problem, identical to yours !!

[Help] Bootloop after updating, usb debugging not enabled.

Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.

Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.

Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com