A couple years ago I managed to install LineageOS, currently on 15.1. I want to update, but I have not been able to fix or get into recovery since I installed LineageOS.
When I reboot into recovery, I am greeted with a black screen and the light next to the front facing camera goes solid white, can't do anything.
I have tried installing various dumpling (5T) recoveries including LineageOS and twrp (both through the app and through adb). All the installations show successful, no error or anything. But I always get the unresponsive black screen when booting into recovery.
Any thoughts would be appreciated. Thank you.
Related
Hello guys,
Thank you for reading, any help is appreciated.
My device was running the latest release of CM13 (cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NK-serrano3gxx) and TWRP v3.0.2-1
So yesterday afternoon my phone randomly shutdown and I was unable to get it turned back on until this morning.
However though when i did manage to get it powered on after hours of failed tries it was stuck on the Samsung boot screen.
I've since tried to access the TWRP Recovery (Pwr + Vol Up + Home) but it sticks on the TWRP slash screen and then attempts to reboot normally (which as i said stick on the Samsung boot screen).
I also tried re-installing TWRP via Odin and it appears to be installing properly and successfully but when i attempt to access TWRP it again sticks on the splash screen,
I've also tried installing CWM Record via odin and that also appears to be installing properly and successfully but when I attempt to access the recovery I am yet again greeted with the TWRP Slash Screen which has lead me to believe something is going wrong.
Any ideas or suggestions as to what may be going on here ?
Thanks in advance, any help is appreciated.
Hey again guys,
I have tried installing stock rom via Odin, It says Pass but nothing at all seems to be changing.
I'm beginning to think Odin may really not be working at all or something is wrong with the phone
Update: I tried flashing TWRP recovery via Heimdall and it appears to have completed successfully saying "RECOVERY upload successful" but when i reboot immediately after into Recovery mode it still sticks at the TWRP 3.0.0-0 Splash Screen then attempts to reboot normally which as mentioned earlier also sticks on samsung slash screen
I was an idiot and did a factory reset (not while in recovery mode) and when everything restarted I ended up with my tablet stuck trying to load TWRP - I am/was running the lastest CM nightly from the end of May, I don't know what version of TWRP is currently on there. I just get the blue teamwin screen that stays there for about 5 seconds, flashes black, then back to the teamwin screen again. I got it into download mode one time, but as I was not in a situation where I could take advantage, and have since forgotten what I did to get it into download mode. (I think) I've tried all the button combinations with the tablet in the bootloop, and with it off (dead battery) to no avail. I've checked the forums and the few that I've found with the same situation as me, there is either no solution offered, or the solution was never posted, just that the situation was resolved - the thread most resembling my situation is this one http://forum.xda-developers.com/galaxy-tab-s/help/galaxy-tab-s-sm-800-stuck-flashing-twrp-t3219865.
Any help would be greatly appreciated. If you need more information, let me know. Thanks!
Hello,
I am quite new to the community, did some flashing some time earlier on Xperia SP successfully but now I am struggling with Xperia Z1c (Amami) with new Pie releases.
I have been trying to flash my Z1C to Android 9, and all I can see is as those roms are working fine, but whatever I do, I end up with unusable phone.
When I tried clean flash (wipe Cache/Dalvik/System/data) and flash even the rom only (no gapps or any other module) I end up with a black screen after the splash screen is gone. When I flash also Gapps, I get the screen where I can pick the language and afterwards it says I shoudl wait a few moments and it literary goes forever, with 1 change that after 1-2 mins screen goes dark and from time to time it lights up with lockscreen or the screen to unlock SIM, but the touchscreen does not respond and also HW buttons are not working, shutting it down via vol up plus power.
I also tried to go dirty and use older oreo builds (Recovery Remix and AICP Roms) to go to Pie successors, but then I end up in a similar loop, where it says Android system is starting (this is when the touchscreen works) and then the screen goes dark and once it lights up, the touchscreen is not responding like in case of clean flash.
I am using TWRP 3.2.3 recovery plus AICP and RR roms. in both cases 8.1 roms work like a charm, but I am missing the security patches.
Is there anybody who could suggest if I am doing anything wrong, or just its my phone?
EDIT: happens the same on Lineage OS as well... quite desperate as I am not able to gather any info what could be going wrong
Thank you in advance.
https://forum.xda-developers.com/so...om-lineage-os-16-0-xperia-z1-compact-t3886233
I recently decided to to root my SM-t110 so that I could upgrade to LineageOS, but after I had gotten TWRP working it offered to install SuperSu so that it could be rooted, so I rebooted SuperSu was installed and then I had to reboot and now I'm completely stuck in TWRP. I can't even boot into safe mode, download mode, or anything except TWRP.
I had also had backed up everything and then tried to restore from that, but even that didn't work. Any help would be very much appreciated!
I Have fixed the problem, I'll come back and post how I fixed it in a couple of days.
Never mind, it appears I'm stuck in a bootloop again, except this time it's far worse because it's stuck on the launch screen of TWRP 2.7.0.1 and then artifacts into a back bar at the top half and then two purplized TWRP boot images next to each other on the bottom half.
Also, last time I fixed it by flashing TWRP again, except through TWRP itself instead of Odin (I put the TWRP file on the sd card).
Any help with the new issue would be helpful and appreciated though.
Hi everyone,
When trying to update from LOS 18.1 for microG to 19.1 for microG today, something went terribly wrong.
The recovery flashing for LOS 19.1 went ok, but when i tried start the bootloader i got an ugly "Waiting for flashing full ramdump" message. I managed to reboot pressing the three physical buttons, and i even managed to start the 18.1 recovery mode. Assuming the recovery didn't get properly flashed, i flashed it again and the operation seemed successful.
But when i tried to boot the device again, i realised i was stuck in the fastboot mode, whatever key combination i would press. If connected to the computer or the power, the device wouldn't even turn off, it would boot into fastboot again.
Before flashing the device i spent a lot of time trying to properly install the ADB USB drivers, but it would always return me a "Code 10" error message. I tried it on 4 different computers. But when booting in fastboot, the drivers seemed to be properly installed (no "!" in the device manager).
When i first installed LOS, i first installed LOS 18.1 and then decided to switch the LOS 18.1 for microG, but i did not flash the LOS 18.1 for microG recovery. Could it be part of the problem ?
I don't mind formatting everything, as i wanted make a new clean install.
Your help would be really appreciated as i am totally lost as a real noob. I'm afraid that i bricked my phone.
Thanks.
Problem solved.
I used the script mentioned here.