I tried flashing TWRP several times. It seems to have worked out, rebooted into it, but now the touchscreen does not work in TWRP and reboots only in TWRP. ADB stopped seeing the phone on the computer. Is it possible to restore the phone?
Related
Ok this is giving me cancer! I'm flashing TWRP 2.8.1.0 and can enter this recovery immediately after flashing it. But, as soon as I reboot the phone, or boot the OS and then reboot into recovery, the recovery is restored to stock. I've flashed recoveries an unhealthy amount of times on several different devices but I've never seen this behavior before. I'm on stock Android 5.0 LRX21O.
I had this, but i reinstalled, but now it is working just fine, just needed to reinstall it
gefilus said:
I had this, but i reinstalled, but now it is working just fine, just needed to reinstall it
Click to expand...
Click to collapse
Reinstalling the recovery?
Yup, just flashed it again, same image
Look here:
http://forum.xda-developers.com/google-nexus-5/general/warning-lollipop-aosp-roms-broken-t2930512
Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?
so yesterday, I decided to root my tablet. Everything was working nicely after I rooted and downloaded clockwork mod. The whole problem started when I used an app called quick boot, and I booted into recovery mode. As it was rebooting, it asked for permissions(I accepted obviously), and I haven't been able to get past the logo screen ever since. I tried wiping everything, but it still doesn't work. Any solution to this?
Reflash stock firmware with odin should probably work.
I managed to fix it by using the adb sideload thing in twrp.
hey there,
so i had my lgg6 h870 rooted 100% fine, until i yesterday stumbled upon the bug that mobile hotspot turns itself off. so i troubleshooted and i could outsorce that my root is doing that. so i deinstalled magisk and then reset my phone via adb. everything worked perfectly. then i tryed re flashing twrp and it wouldnt at first but then it did after turning on uzb debugging. so then i wanted to boot into twrp, but it only showed me the twrp logo and then booted up into my system as if nothing ever happened. then i deleted EVERYTHING (system, dalvik, cache,.....) and then the fun began, i had no OS on it, so i flashed a lg g6 h870 stock rom onto it and it sayed it worked, so i rebooted to system but i ended up in twrp. so i rebooted again to system and ended up in twrp. so i tryed using adb to get into fastboot, but not even that works. so now im out of ideas what to do, and i hope someone can help me out with this.
thanks
Apologies for being a member of this forum for so long and making this my first post. Regardless of this being my first post, these forums have been a life saver many times, and I would like to thank the very knowledgeable people who frequent these forums for all the time, effort, and patience that the put into new development and answering questions for those like me, who have a lot to learn yet.
Now to my issue...
I have had my OnePlus 7 Pro (Global) for a couple weeks now. It is on Android Pie, and I intend on keeping it on Pie for a while. I rooted it straight out of the box with Magisk 19.3 and TWRP 3.3.1-4 (Guacamole)(Installed by zip to both partitions) and it has been working great. No problems at all.
Two things have changed today, so I'm not sure which is the issue, if either are. One is that I updated to Magisk 20, and the other is that I tried to boot into recovery with and OTG cable attached with a 256g sansdisk flash drive attached to that. This is when it booted into bootloader instead of TWRP.
I disconnected the OTG cable and rebooted into system. I still had root from Magisk, so I attempted to reboot into recovery again, only to find that I booted into the bootloader again. Now I figured that I had lost TWRP, so I hooked my phone up to my windows 10 computer to flash custom recovery once again. I had read that it is possible to install TWRP to the ramdisk now through advanced settings, so I booted into temporary TWRP and selected the TWRP.img file to install to ramdisk. The command line said it was a success, so I backed out of that screen and rebooted into recovery. Once again, I was booted into the bootloader.
I disconnected my phone and booted into system. I still had root and everything was working as usual, so I reconnected my phone again and tried to install TWRP to both partitions as I did originally. The terminal went through the process rather quickly (usually it takes a minute or so to install TWRP), but claimed it was a success and that I lost root, like it should. I backed it up a screen, reboot to recovery.. no dice.
I've tried to take Magisk back to 19.4, but it didn't effect whether TWRP would stick.
I have a TWRP backup that I took of everything a couple days ago. I thought about trying to restore and see if that works, but I wanted to run it by you all to see if maybe somebody else has had this issue.
Could the attempt at rebooting into recovery while connected to OTG have done this?
Thank you all in advance for the assistance. I'm aware that this post is long winded, but I am also aware that you all like as much info as possible.
Thanks.
##############################################
Update
##############################################
My phone is working now, but not before I massacred it. I attempted to restore with that twrp backup I had while temporarily booted into twrp, through the twrp.img, through adb. I had it on the phone, so I figured I could use it.
I don't know if it was a corrupted backup, or if the process wasn't orthodox enough, but the restore crashed in the twrp terminal. I tried to boot into system and found that I had bricked the phone.
I ended up having to use the msm-downloadtool that I found here on xda. It was a lifesaver for sure.
Anyway, I figured that I'd update this thread. My phone is completely reset, bootloader unlocked, rooted, with custom recovery once again. I'm not sure what the cause was for the initial issue. I would still be interested to hear of any theories.