I stupidly chose "fix permissions" on my 5.0 ROM and now my phone is stuck in a bootloop. To make matters worse, I can't sideload anything with TWRP because when I do "adb devices", the device status shows up as "device", not "recovery". And when I go to sideload, the status is still "device" and not "sideload". Is there anything I can do? I don't have any ROMs on my phone anymore so my only option is to sideload/push through TWRP.
Edit: So I realized that when in TWRP, the phone was in the USB MTP mode. I managed to copy my ROM to the phone. I did a system, cache, and Dalvik wipe, and installed the ROM. However, it still doesn't boot. I end up at the DemiGod Crash Handler every time I boot it.
Edit 2: Wiping everything and flashing again fixed the phone!
Related
Specifics first -
Device: VS980 (VZW LG G2)
Recovery: TWRP 2.6.3.2
ROM: CM 10.2 12/6 Nightly
I had a random reboot while trying to answer a phone call today. Its happened before. So I figured I would reflash the nightly to see if it would correct itself. I entered recovery from the power button menu. I tried to flash the nightly from the CyanDelta folder (tinkering around earlier, downloaded it, detected rom, and deleted from cmupdater file). For some reason I decided to wipe cache and dalvik after installing. The phone never rebooted after that. I proceeded to try and power up only to be faced with a constant CM boot screen (I knew something was wrong when I notice how long it took to get to the CM screen). I was able to get back into recovery to try and flash the 11/30 nightly, which I hadn't touched. After flashing, I noticed the "Unable to mount /cache". So instead of trying to fight with my phone to get back into recovery, I flashed a backup. It also displayed the "Unable to mount /cache". My phone was in recovery where I performed a factory reset. ADB was recognizing it and receiving commands. I unplugged it to see if I could get into download mode. Now I cant get it back into recovery. When I do "adb devices" it shows up as "unauthorized". Where do I go from here? I have very limited adb experience.
I have a d802 . I had cloudy1.3 and twrp 2.7 installed with autorec. I tried to update it using
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
(from twrp page, with the latest img file).
But I coudn't access recovery, some error about security. Then I shutdown my phone and then it booted fine into system. I retried to access recovery but nothing.
So I decided to return to autorec, I installed it, I clicked "Flash Recovery" and now my phone doesn't boot in any way.
It show "lg security error" and then shutdown.
I can access download mode. Is there a way to fix my phone without deleting everything?
I'm sure the problem is the recovery, I was messing with it, can I bring my phone back and don't delete my configuration, photos, apps?
Thanks
I'm so happy!
I did it!!!
I managed to boot into recovery with the usual combination of keys (with the method that ask you if you want to format, but then you press power and it boot into recovery).
From there I saved everything using adb pull (Just in case). Then I dirty flashed Cloudy 1.3 and my phone is back !
I hope my experience can help someone
Heeelp
I tried to install Cataclysm ROM, and then it went into some sort of installer, after that I tried to reboot, but TWRP said it didn't have any OS?? So i tried to boot it up anyway? but nothing, just stucked on Google Logo. After that I tried to boot into TRWP agian. But then TWRP says "Mount Decrypt Data" and then i have to enter a password?? but i removed my pattern lock before flashing. Because i made a Nandroid and i read i had to remove the password before making a backup. But then i just press cancel. Then it says " Unmodified System Partition" "Swipe to Allow Modifications" and i do that. Now i have nothing on my SD card?? Then i thought i could flash stock through Fastboot/ADB, but now it won't see my device in ADB? I have updated my drivers, both by Google and Intel (Read they helped someone else) But nothing? so i cant retutn to stock and can't boot up.
Please help, highly appreciated
Some how i got i to reboot by an ADB command and then i could flash factory imgs and return to stock.
That very same thing happened to me the 1st time I tried to install Cataclysm. Somehow my SD card got wiped.
I had to start from scratch with the factory image.
I don't know what happened but I have since successfully installed Cataclysm.
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.
steps i did:
installed twrp twrp-3.4.0-1-markw
flashed lineage-17.1-20200920-UNOFFICIAL-markw by shiabzzz
wiped data and cache, excluding internal storage
tried to flash gaps but failed due to error 20
flashed magisk
reboot.
now im stuck on bootloop. i know i should have deleted data before flashing the rom, not afterwards. when i press power+up it's not going to recovery.
how can i fix it?
are gaps mandatory for it to boot?
will my phone turn off when it runs out of battery, will i be able to go to recovery then?
update: i can access fastboot mode, but when connecting to pc and trying to boot to recovery it says "waiting for device".