12.2 Boots to black screen. Can force boot to TWRP, but not Android - Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble

SM-T900 Pro 12.2 boots only to a backlit black screen. If I attempt to boot to recovery (vol down + home + power), I can boot to TWRP, but not to an OS.
This device had been rooted before. I was trying to install LineageOS 14.1. In my mind, I followed these instructions perfectly.
https://forum.xda-developers.com/ga...-7-1-xsm-t900-unofficial-cyanogenmod-t3524853
I've rooted and installed quite a few ROMs on quite a few devices, but I'm stumped.
Works:
Can boot to download (and can use Odin (v.3.10)
Can boot into TWRP recovery
Can always reboot with vol down + home + power
Doesn't work:
Can't boot normally - a reboot takes me to a backlit black screen.
Can't boot to the OS (not from recovery either)

How strange, mine has just started doing the same thing, I thought I needed a new battery but no.
I have a SMT-520
Like you I can boot into TWRP and the android recovery mode but that's it when I try to boot to android it just sits on a black screen nothing more,
I can connect with Odin, I've tried re-flashing new rom and the original rom back on to the device but still not working please any info will be great
thanks
wolf

Mine did the same thing but I left it on the black screen and after a couple minutes it rebooted and went black for a while and then finally booted into 14.1 rom

Related

[Q] Note 2 LTE bootloader bootloop?

I have a problem, I was on AICP 6.0 (stock AICP Kernel) and had TWRP recovery [t0lte - Note 2 lte]. This morning, my phone randomly shutdown with full battery, and went into bootloop. Its the kind of boot loop where when I try to access my recovery (Vol. up + home + power) The phone restarts before it even gets to the recovery. Same with the Download mode, It restarts before I press up to confirm that I really do want to go in download. Now, I'm stuck here unable to do anything. Any Ideas?
I got it to somehow boot into recovery. It is solved now

Phone shuts off and wont turn back on

I've had a CM11 Official Nightly installed on my phone for a couple weeks, and just today my phone started turning off, and when I try to turn it back on it just shows the Samsung logo for a few seconds, then flashes the CM11 logo, then the screen goes black. It does fully boot up when I pull the battery for a few minutes then turn it on again, but it only lasts for a couple minutes before shutting off again. It does the same thing when I try to boot into recovery (TWRP), it shows the Samsung logo with the boot recovery text, then shows the TWRP screen for a second, then shuts off again. Rarely it will boot into recovery. Any idea what the problem is or how to fix it?
I would try installing the latest version of Philz Touch for the d2lte to see if you can get into recovery and stay in recovery. I used to have twrp on my phone but it gave me problems when flashing ROMs.
Thanks, installed Philz Touch recovery via Odin, and got it to boot into recovery and installed CM11 and it seems to be working so far.
Good news. For future reference, I would load the Samsung Phone Info app from the playstore to confirm the bootloader and modem on your phone as some ROMs may require the latest bootloader and modem to function properly.

GT-I9190 stuck on TWRP Slash Screen and Unable to re-install

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

Stuck in the boot animation logo - can I recover?

--- I am stuck in the boot animation logo screen with both Lineage OS 8 and the stock Samsung ROM ---
I have a Samsung Galaxy Tab S (SM-T800). I've installed TWRP and Lineage OS 7.1.2 on it a while ago. However, I was never able to boot into TWRP after that - pressing the Power key, the Volume up key and the Home key always got me to the "Downloading..." screen instead.
Recently, my Lineage OS ROM kept resetting unexpectedly, so:
- I did a factory reset, trying to solve the problem. It didn't, but I noticed that on first reboot after the factory reset, I got to the TWRP Recovery screen.
- I decided to install a new custom ROM. I downloaded Lineage OS 8 and did another factory reset from my existing Lineage OS 7.1.2.
- When I got to the TWRP Recovery screen, I chose "Install" this time and installed Lineage OS 8 (without doing a clean first...)
- On first boot after install, it got stuck into the Lineage OS boot animation logo.
- I had to reset it using the Power key, the Volume up key and the Home key - this got me into the "Downloading..." screen
- I used Odin to flash the stock SM-T800 ROM I got from sammobile.com (T800XXU1CRJ1_T800OXX1CRJ1_ROM.zip)
- ROM was successfully flashed, but it got stuck again - this time in the stock ROM boot animation logo on first reboot.
So now:
- I am stuck in boot animation logo with both Lineage OS 8 and the stock Samsung ROM
- My tablet is visible in Odin (so I could maybe flash smth else?)
- I can only reboot in Download Mode
- I have adb and fastboot on my PC, but I don't know how to make my tablet visible to these tools in the current situation
Is there any way I can recover from this?
Did you end up finding a solution? I am having a similar issue with my T700. Trying the stock rom now
Yes, managed to boot into recovery mode (Home + Volume Up + Power button). From there, I went through format partition and reset dalvik, then reset - the tablet finally booted after that.

Need Help. Phone stuck on black screen on boot

I flashed nusantara project 2.6(android 11) on my redmi note 5 pro along with nikgapps. Everything was working fine on booting but I didn't like the launcher. I saw that nikgapps had an addon package for pixel launcher and thought i'll install that. So i booted into my recovery and flashed that and rebooted into my system. On booting, I get the boot animation which gets completed and the phone boots but instead of the lockscreen, i only see a black screen. On holding the power button I see three options: power off, reboot and emergency call.
So i thought maybe the launcher was not compatible and that reflashing the rom would fix it. But I'm not able to boot into my recovery with any key combo. I'm also not able to boot into fastboot either. So I can't even use the miflash tool to flash a fastboot miui rom.
When booted into the black screen, miflash does detect my device when i connect it but when i flash a fastboot rom, nothing happens. It says flashing for an extremely long time and my phone is still in the black screen itself
Let me know if you have any ideas which i can try to fix this
Fixed it by going into edl mode and using miflash tool

Categories

Resources