hello, I made an update from 0.21 to 1.7 /e/os and when the phone has restarted came message ,qualcomm crashdump mode". I then wanted to bring handy in recovery mode, but it came the normal recovery not twrp, then I have fastboot mode on and tried to flash twrp with PC (that did not work). I then changed to slot a (fastboot --set-active=a) and then i started recovery mode and then twrp came. I couldn’t see any data from the phone, not even that system is installed(in wipe there is only: Dalvik/ART Cache, metadata, Data, Internal Storage, Usb Storage and Vendor) and the size is not there either. I then tried to start the system from twrp and waited 2 hours and all the time it loaded (so the E logo with the dot at the bottom). What can I do?
The phone is OnePlus 7 Pro and it was rooted.
See this post. Let me know if it doesn't help.
Related
I used the recovery mode first time - it worked, second time playing with NoBloat - it gets stuck in boot screen.
I can go to the recovery mode menu, both chinese and english, can do a full clear cache, data, format, but phone still won't boot.
I can use ADB shell, but Smart phone flash tool does not recognize phone, MTK droid tool recognizes it, but I can't backup it.
Can someone help me what to do now ?
I can use sideload but installation fails for some reason.
I tried putting stock rom, cwm and modded rom and to no avail.
Hi. I needed to format the data from my old galaxy using twrp 3.2.3 (latest version). I selected "format data", typed "yes" and the process started. Then two or three lines of red text appeared saying "unable to mount \data" or something like that and the phone, which was still connected via usb to my pc, rebooted. The connection to the pc was lost (I imagine no big deal), the phone rebooted in TWRP but I can't do anything, because the format process begins again without giving me the option to cancel it. And then again the phone reboots, and reboots, and reboots, always in TWRP format data loop.
I have a nandroid backup on my pc, but I have no idea how to flash it on the phone, since I can't use the recovery.
I CAN boot into download mode, if it can be useful.
What do I do?
Simple you need to reflash the stock firmware jellybean on sammobile then re root the phone and reflash the latest twrp.tar again using all while using Odin
Gaber92 said:
Hi. I needed to format the data from my old galaxy using twrp 3.2.3 (latest version). I selected "format data", typed "yes" and the process started. Then two or three lines of red text appeared saying "unable to mount \data" or something like that and the phone, which was still connected via usb to my pc, rebooted. The connection to the pc was lost (I imagine no big deal), the phone rebooted in TWRP but I can't do anything, because the format process begins again without giving me the option to cancel it. And then again the phone reboots, and reboots, and reboots, always in TWRP format data loop.
I have a nandroid backup on my pc, but I have no idea how to flash it on the phone, since I can't use the recovery.
I CAN boot into download mode, if it can be useful.
What do I do?
Click to expand...
Click to collapse
my solution, was to change the system from ext2 since I can not format in ext4, it also works in f2fs and but it depends on the kernel with boeffla and LOS14.1 is running well in f2fs
I use gm5 plus mobile phone. And tried to install twrp. Flashed twrp with adb, rebooted but its still stock recovery mode. And booted again, i used "boot twrp.img" command and i get twrp screen. Rebooted again and phone is booting with general mobile screen and closing and opening fastboot mode screen. So pc is dont recognize my phone. i tried wipe data and cache. I dont have sd card
Hello XDA Community,
I just got a Galaxy A40 (SM-A405FN/DS) and flashed TWRP.
Everything was going well, so I decided to try to flash an unofficial LineageOS GSI.
I followed some instructions I found on a website:
- Wipe Vendor, Dalvik/ART cache, Wipe Cache, Data, System, Internal Storage using TWRP Advanced Wipe
- Flash Image to System Partition (Used: lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz)
- Reboot & Pray
I am now stuck in a bootloop, sometimes I am able to start TWRP, but I have tried to flash other images but wasn't successful.
(Loop: Bootscreen -> Warning (Press Power Key) -> Bootscreen -> Blackscreen (Reboot))
I am currently downloading the stock image.
How can I enter recovery mode? Is there anything else I can try?
Got the same goal, installing a Lineage GSI ROM. But... I got stuck in a bootloop just like you after flashing TWRP.
You have any tips getting out of it?
Solution: Okee, I drained my battery first. Then I pressed volume up and down together and connected it to my pc. This way I got it in download mode. (thank god!)
So i managed to get into download mode after being stock in restart loop by holding off button. When screen got black, i plugged my phone into my pc and pressed volume up and down buttons. It worked. I am a genius.
Anyone managed to get a custom ROM to work on that device ?
welpitwentwrong said:
So i managed to get into download mode after being stock in restart loop by holding off button. When screen got black, i plugged my phone into my pc and pressed volume up and down buttons. It worked. I am a genius.
Click to expand...
Click to collapse
YOU ARE AN ABSOLUTE LEGEND THX ALOT
I've installed the Evolution X ROM (A12) on my Redmi Note 5 a while ago. The ROM worked well, it would only start bootlooping when the storage is full, which I always was able to fix by deleting Telegram cache (it grows to 1GB in a single day) and moving my photos to the PC
This morning I've found it bootlooping again, but it was too quick to get to settings to delete cache, so I put it in recovery mode and deleted cache from there, however the phone still only manages to boot to my lock screen and bootloops again after a few seconds. Even does it in safe mode. I've tried to move all my photos again from recovery mode, I freed up 16GB but it still does not boot.
Any non data destructive suggestions would be very welcome
Just tried dirty flashing it, and it still is not working.