I've received a Redmi Note 8 Pro from a relative which does not boot. Turning it on, it stays at the "Redmi" logo, and restarts after some time. The charging LED does light up and turn off again, and also the "low battery" symbol shows up, however offline charging results in the same loop at the logo. Fastboot does work, however the bootloader is (and always was) locked; recovery or boot menu does not work (also gets stuck at logo). I've also tried reflashing different firmwares (versions and regions) using the auth bypass method (https://telegra.ph/UNBRICK-BEGONIA-NO-AUTH-01-23), with and without formatting, with no luck. However, the logo at which it gets stuck changes with older firmwares, so flashing seems to work correctly. I'm not sure whether it's a hardware or a software problem, as flashing seems to work. Is there anything else left to try?
Related
When i boot up my gnex, it shows the google logo for a short moment and the screen goes black. It boots up but there is nothing on the screen. While charging ( after turning off by battery pull and connecting to charger) I can see the charging icon. Anyway to fix? I just flashed stock image but it dosent seem to be working.
help please..
try flashing a different kernel just to see if it is a voltage issue. Can you get into recovery?
The phone is a Samsung Galaxy S4 mini (GT-I9195). I believe it was originally on the EE network, but then used on the Three network. I'm not sure if it needed to be unlocked for this to happen, or if it was purchased unlocked.
Starting with the phone switched off in each scenario below:
If I switch the phone on, it vibrates once and the Samsung logo appears. It then goes into an indefinite loop of vibrating twice, and the Samsung logo appearing, vibrating twice, etc.
If I plug the phone in, the battery appears with the grey circle inside. Without me doing anything, it goes straight to the Samsung logo, and then to the aforementioned indefinite loop.
If I switch the phone on, holding the home button and volume up to enter recovery mode, it goes to a sick robot with 'No Command' underneath and some text that reads 'Manual mode, appling [SIC?] Multi-CSC..,. Applied the CSC-code: BTU, Successfully applied multi-CSC'
I'm not sure what the 'correct' firmware to flash is for the phone or how to find out. I have flashed some 'BTU' 'stock' firmware a couple of times using ODIN; the result is 'PASS' but the boot loop continues. I have also flashed TWRP recovery using ODIN; the result is also 'PASS', but the boot loop persists as before after launching recovery mode.
Similar posts have been raised before, but I've never seen it answered.
Why is this happening, and how do I fix the problem?
Thanks.
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.
So, the phone works, but when it turns on, nothing displays at first, no logo or loading animation. but, once its fully tuned on, everything shows again. now, the real issue... I cant get into recovery mode, or anything to try and get it factory rest or flash new firmware on it to fix the issue, because the screen displays nothing when I'm trying to access recover menus. it just stays black until i disconnect the batter and let it turn back on normally all the way.... tried some research and did the usual black out issues... but nothing.
any help would be great thnx!
Hi, I'm having a problem with my phone (C21Y RMX-3263) being stuck in bootlop after accidentally updating magisk via direct install option (has been rooted once already with patched boot img and spd tools). I figured I should just flash the old firmware but neither SPD research and upgrade tools work properly, for about 10-30 seconds all is going well, but then it just gets stuck on downloading, on different parts like super, or boot randomly alternating between attempts. I've left it on for about 4 hours and tried multiple times with no progress at all. There is nothing visible on the screen but holding the vol down button and plugging the cable in seems to initiate fastboot. I've tried using different versions of the tools and different firmwares for my model but nothing seems to work. The bootloop itself is very weird - the phone buzzes and the splash logo appears, afterwards starting to glitch out extremely eerily, the colors start to become weird, white lines dance on the display and after that it turns blank and flashes gray for a few seconds before turning off, looping and doing it all again. Pretty sure this isn't a hardware issue as the phone was working fine before. Assistance would be much appreciated
its dead
loardsudo said:
its dead
Click to expand...
Click to collapse
Thank you for your incredibly detailed and elaborately constructive reply