So my mom and I have the same phone, a Huawei P Smart 2019 pot-lx1.
The problem
The phone started doing a boot loop anytime you try to turn it on.
It vibrates and shows the Huawei logo like normal, but after the logo the screen turns dark (not off, just dark, the backlight seems to still be on).
Sometimes after this black screen, a 'recharging' icon is visible in red for a brief moment. It's a red circle with a red lightning symbol in the middle.
It does this regardless of whether it's plugged in or not.
I have no idea what this means because as far as I'm aware, the device can function fine without power (see further down below).
After this black screen or flashing the red recharging icon, it just reboots and does the same.
What I tried
The phone refuses to open Erecovery mode (hold volume up and plug in the device). I have confirmed that this method -should- work since I tried it on my own phone of the same model. In the case of my mom's phone it just shows a black screen like normal.
I can get the phone into fastboot, which is great. It tells you to open HiSuite on your computer, which I do, only for HiSuite to tell me "Your device is not supported for system recovery". Furthermore, any commands that could help me return 'Command not allowed', this is returned from the bootloader of the phone and is NOT an OS permissions issue. I've tried stuff like booting into TWRP or wiping userdata this way but it's simply not allowed.
Regarding the battery, I've tried unplugging the phone while it's in fastboot mode. It just stays on like expected and doesn't turn off, so I don't think the battery has no charge.
From what I gather online, the phone has an FRP lock which prevents you from doing anything that could result in the phone getting a reset. FRP can supposedly be disabled, I've tried dc-unlocker but it simply didn't work, presumably the phone is 'too new' because it wasn't in the model list. (I used detection & then the blue nuke option that said Temp FRP unlock or something like that). There are sites that offer FRP unlock passwords which can be used with 'fastboot oem frp-unlock XXX' but I REALLY don't trust these sites and the prices are expensive.
USB debugging is not enabled and I cannot possibly enable it because the phone will never boot, hence I cannot hop into adb and disable FRP that way or do anything else that adb could. I'm essentially stuck.
I also tried some random things like holding volume up + volume down + power during boot. I have also tried countless times to get into erecovery but it simply will never get to that point.
I also tried downloading the phone's firmware and putting all the files where the UPDATE.app is also located in the 'dload' folder on an SD. I also tried putting an 'update.zip' in the root, but this didn't do anything and I think it's pointless unless you can boot into erecovery.
My mom and dad suspect they damaged something related to charging the phone, either the pins or something inside the device by inserting the charger agressively, is that possible at all? It could explain the red charging icon regardless of battery status, but I'm really not sure.
Same problem!
Hi I have the exact same problem with my huawei. Could you able to solve your problem? If so, could you tell me how?
Thank you in advance.
Related
Hi, I got Motorola Moto G, original system, no root. I just encrypted my phone, process most probably finished without problems - I stopped watching the phone on around 90%. Then it restarted, boot animation, "enter your password to decrypt the phone", I type it in, green robo shows for 1 second and then black screen (backlighted) :/ After couple hours nothing changes.
If I type wrong password, phone ofc doesn't acccept it. Computer sees device, but I can't access it. When I turn off the phone by pressing POWER for long time, it just resets and goes back to asking for passwod again.
Please help me recover my data...
EDIT
before entering password PC says phone is off, after typing it, PC says it doesn't have drivers (it worked normally before encryption).
EDIT 2
I can enter fast boot, but IDK what next. Recovery mode just ends with "NO COMMAND"
I see that probably all users who got this problem have Motorola Moto G too. Mostly people who use CM and tried to encrypt phone.
I downloaded Android SDK, fastboot.exe tool sees my phone in this state. Not sure if it can be used to do something useful....
adb.exe doesn't see device
Cyanogenmod is very buggy and in perpetual development state, not recommended.
Try this
http://forum.xda-developers.com/showthread.php?t=2542219
scandiun said:
Cyanogenmod is very buggy and in perpetual development state, not recommended.
Try this
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks, but I got stock Android and I don't want to loose my warranty :/
bump
So, I left the phone in black screen step over night. Battery ran out. I tried turning it on/off, entering fast boot mode, but nothing happened, then connected to USB. LED turned on for a while, screen too, showing battery with 0%. But now nothing again. Just black or off, not sure. Can't do literally anything, I tried pressing different keys for minutes and changing USB slot.
EDIT
nevermind, fixed battery problem, Moto G with no power needs normal charger or much longer time on USB
From what I've read, encrypted data on phone is protected by password and some kind of encryption key/file. Reflhasing firmware would cause permanent lose of that key and thus whole encrypted data.
The only solution I guess is copying that key on PC. Copying encrypted data if possible, and decrypting on PC using some tool, as Android is open source, so it shouldn't be a problem to extract it's decryption mechanism and run it on PC.
OR copying key to PC, reflashing phone, copying back key and praying this time system will start.
I am trying to get a Huawei Y6 2015 (I believe the model is SCL-L04) to work again. When it was given to me, the phone would power on, display the Huawei logo for a few seconds, then the screen would shut off and the notification LED would turn solid blue. Nothing else would happen. I just flashed a new stock ROM onto it via SD, and now it is simply boot looping - it comes on, shows the Huawei logo for a few seconds, but instead of the blue LED, it simply repeats the cycle over and over again. The phone died randomly while in use for no apparent reason - it just shut off, then the LED went blue, and that's the last that was heard of it. It is able to enter fast boot mode, and recovery mode. I have tried factory resetting it, as well as clearing the cache partition, but neither of those worked. HiSuite does not detect the phone when it is in fast boot mode, but my computer does detect it as removable media and allow me to view its files.
Any suggestions? At this point, I'm beginning to suspect hardware failure. Thanks!
Hi, got a samsung J6 phone with android 8.0, non-rooted and no custom recovery, usb debug is enabled
It just froze when starting an app that always worked before, now there is a blackscreen, buttons doesn't do anything; power included, but the phone seem still on, and as a proof, he's detected by my PC, which won't happen when it's off, on my side at least, i tried to reboot it into recovery via adb, this error popped:
C:\android\platform-tools>adb reboot recovery
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
then i tried to kill the server, and it just hand there doing nothing too now.
C:\android\platform-tools>adb kill-server
_
i can't remove the battery nor i can open the phone without breaking it seem, so what should i do?
@Gess1t
The catch is that you must have root access on your device if you want to perform adb reboot recovery cmd
So basically, my phone is just unusable now? tried to call it with another phone, instantly not available, so well, guess i'll have to wait for the end of the quarantine to send it for repair, still have the warranty i believe . hope they just don't remove my internal data for no reason, cause if they do that my google auth i had there is gone forever.
but wouldn't the phone still work if it was just the screen?
After all the battery still receive power apparently and the phone seem to do be detected by my PC, so it seem it still on? or maybe it's still in that crashing state.
So i was right, it was in a certain freeze mod, after couple day, the battery seem to have emptied, as i knew it would happen, i then plugged it in one of my external fast-charge battery, screen showing battery, i can turn it on, and it seem to run normally, playing high graphic game seem to be just as fine as before. still weird tho, what happened?
Hi. I have a problem with a bricked Samsung Galaxy S7, SM-G930F (the Exynos one). A bought it a few years ago and let someone root it to play around with it. I got it back recently and it didn't turn on. I had the battery replaced which allowed me to turn it on, to a "no command" message. I got it into recovery mode. I chose "factory reset" to try to bring it back to a working state. That didn't help, so I booted into download mode and was able to flash the latest firmware; I made sure it was the correct one for this model. It would reboot to a screen with the Android logo and a message of "erasing" with rotating arrows on the Android that stopped after a few seconds. If I left it plugged in, it would stay like that indefinitely. If I unplugged it it would turn off within a few seconds. For a while I could still get it to come up in download mode, but now it does nothing no matter which buttons I press. No lights come on when I plug it into a USB charger, although a wireless charger seems to detect it as the charger's red LED comes on. Following advice on this forum for a bricked S8, I left it not charging for 24 hours to see if it would drain the battery completely, letting me try again. That didn't work; no matter how long I charge it or what buttons I press, nor whether it's plugged into the charger or computer or not, nothing happens. There's no way to tell if it is charging. I have evidence that it works since I was able to flash the firmware and that process went smoothly, but I can't get it back to that mode. Any ideas? Thanks.
Re-flash Stock ROM.
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Thanks for your reply. I flashed the stock firmware before the phone became unresponsive. Now I can't flash anything since none of the buttons have any effect. and the phone is not recognized by my PC.
@Doctor_Perceptron
If you can't access phone by means of Odin then with 99.9% certainty phone's boot-loader is broken. Put phone into e-waste.
If it was a Qualcomm device I'd be able to help you through EDL flashing. Since it's not I do believe your not able to flash it at this point as already said by the user above my reply
My V30 worked perfectly for years, Android 9 running, had it rooted using the sticky guide, and Magisk installed. I had just boarded a plane on Monday, sat down, and noticed the LG screen with the bootlaoder unlocked message warning you always see when rebooting. Then it just reboots again, I see the LG logo, the bootloader warning message, reboots again after about a minute.
I also could not turn it off because it would just turn itself right back on, and go back into the loop. Eventually the battery drained and it died. When I got home, I held the power button and the volume down then plugged in to go into I think it's recovery mode, which worked, but my only options were to flash or reboot (I think, my memory is fuzzy). Then I ran LGUP and it detected my phone, but said it can't load the model from C:\Program Files\LG Electronics\LGUP\model\com.
Next I tried running adb commands against it which is working, however I"m getting back LGUS9983322eaa5 unauthorized which I don't understand because I clearly had debugging turned on (which I think is what causes that message?)
Any ideas on what to try next, or what could have happened? I had not installed anything new. This data recovery company called Drivesavers quoted me 900 to get my files off, but I have backups, and there's nothing on the internal memory I can't live without.
Thanks for your help!