I had the Android O Beta version for a week then i downloaded Pre Nexus 7.1.2 from this link
I wiped and flashed it with TWRP
after rebooting
My phone is not turning on
I tried every combination, tried charger
nothing just black screen
Related
I have a asus zenfone 2 (ml550/a008) .The phone worked fine till 2 weeks ago and then suddenly got stuck in safe mode with no access to settings or dialer.
I tried to factory reset and reinstall latest firmware but had the phone start only in safe mode.
I then installed unlocked bootloader, twrp and cyanogenmod latest nightly. The installation went fine and cyanogenmod booted till the first screen to choose language and then the screen completely went black.
I tehn went and reinstalled bliss rom for the same fone . Once again it installed perfectly but then went on to show a black screen when I went into settings or screen. The touch screen gives a haptic feedback suggesting that it is responsive
I am completely at a loss as to how to resolve this.
Please help!!!!!!!
Yesterday night I was trying to restore my phone using TWRP recovery. It was rooted, bootloader unlocked and working on Cyanogenmod 13.0. Meanwhile, it is restoring I fell asleep and today morning I saw that the battery was dead and red light blinked when I press the power button. Then I plugged the phone to the charger for around 15 mins and tried to turn it on. But it didn't boot properly. It does not go beyond the boot logo and occurring a boot loop. So, I tried two factory images both 6.0.1 (MTC20K) and 7.0.0 (NBD90W). Both didn't work. The phone is still occurring a boot loop and I don't have any idea on how to fix it. Please help me...
Sounds like that hardware Boot loop issue
Hello,
I installed LineageOS 14.1 on my S4 Mini about 2 weeks ago and it was working normally, but today when I went turn on it, after it started normal, it caught and shutdown, now when I try turn on again it does not leave the Samsung Logo and if it starts in Recovery Mode it does not leave the TWRP Logo.
neo39 said:
Hello,
I installed LineageOS 14.1 on my S4 Mini about 2 weeks ago and it was working normally, but today when I went turn on it, after it started normal, it caught and shutdown, now when I try turn on again it does not leave the Samsung Logo and if it starts in Recovery Mode it does not leave the TWRP Logo.
Click to expand...
Click to collapse
I have the same problem. While charging over night I realized that somehow my phone turns off. This morning I saw it got stuck at the Samsung Galaxy S4 mini logo. After trying several times to turn it off and on I tried it with the recovery mode. It worked in the beginning. I tried to avoid wiping out the data. It didnt work at all. Even not wiping out somehow. It showed me some error messages.
Now it itsnt even going into recovery mode and it stays in this TWRP logo (version 3.0.2-1).
I also tried to flash different TWRP ROMs with Odin without success. It always showed the same logo again and again.
My LineageOS 14.1 was always stable
Not my first rodeo on this.. running latest beta on my Essential Phone.
I just got a Pixel 2 XL tonight (refurb, was on May 8.1 when I booted it) and I was able to get into Android and toggle OEM unlocked. Did both normal and critical unlocks fine. Flashed latest P beta and after reboot I got a red text screen saying the device was corrupt (not the regular orange text bootloader warning message). Device booted to white Google logo screen with lock (in locked position). It rebooted on its own and same error messages, then got to Google white logo screen with the same lock and sat there for at least 15 minutes before I power cycled it. Same happened again. Went into recovery and factory reset. Same thing, stuck at white screen. Flashed back to 8.1 July update. Same 2 error messages on boot. Did the first short boot to white screen again and reboot again. Stuck at the white logo screen again on 8.1. Started the process over flashing latest P beta again. Same results.\
I should note that my Essential Phone never saw that red message even with leaving the bootloader unlocked, only the orange one. That phone is still working fine on latest beta. That also means I know my USB ports and USB cables are sound.
I'm totally stuck at white screen on boot no matter what I do after flashing. I can't even get 8.1 booting anymore. Flashing all seems to work for both P and 8.1, no errors. Tried a different USB cable and also different USB port. No luck. What's going on? Why can't I get this thing to boot at all past the logo now? Help!
elkay said:
Not my first rodeo on this.. running latest beta on my Essential Phone.
I just got a Pixel 2 XL tonight (refurb, was on May 8.1 when I booted it) and I was able to get into Android and toggle OEM unlocked. Did both normal and critical unlocks fine. Flashed latest P beta and after reboot I got a red text screen saying the device was corrupt (not the regular orange text bootloader warning message). Device booted to white Google logo screen with lock (in locked position). It rebooted on its own and same error messages, then got to Google white logo screen with the same lock and sat there for at least 15 minutes before I power cycled it. Same happened again. Went into recovery and factory reset. Same thing, stuck at white screen. Flashed back to 8.1 July update. Same 2 error messages on boot. Did the first short boot to white screen again and reboot again. Stuck at the white logo screen again on 8.1. Started the process over flashing latest P beta again. Same results.\
I should note that my Essential Phone never saw that red message even with leaving the bootloader unlocked, only the orange one. That phone is still working fine on latest beta. That also means I know my USB ports and USB cables are sound.
I'm totally stuck at white screen on boot no matter what I do after flashing. I can't even get 8.1 booting anymore. Flashing all seems to work for both P and 8.1, no errors. Tried a different USB cable and also different USB port. No luck. What's going on? Why can't I get this thing to boot at all past the logo now? Help!
Click to expand...
Click to collapse
Most likley an issue with the boot.img if your doing flashall.bat make sure you have the newset adb/fastboot files
Does essential have a and b partition?
I know the pixels do and is part of the reason these roms are trickier.
Sent from my Pixel 2 XL using Tapatalk
Fixed it. Caused my own pain (sort of). Path to my platform-tools was changed to an old version (not sure what changed my path grrrrr).
Lucky of 2 things: 1) That I didn't blow out my bootloader and 2) Nothing else caused permanent partition issues.
Anyway, I would recommend anyone else that runs into this issue to be absolutely sure you're running the current version of the platform tools (*all* of them, not just fastboot.exe). Now my device just booted up and with only the usual orange message. Red message is gone.
i was using lineageos oreo but the battery was really bad and i tried to install full clean install to marshmallow.
i successfully installed hboot and then tried to flash firmware and phone stopped before this.
now phone is fully black screen. i tried all button combinations for 10 seconds, 30 seconds, 60 seconds.
i tried charging after 2 days and a low-redlight appeared for second and then everything black again.
what can i do for my phone getting back to life..