Related
While i am a noob for Android/Smartphones, I am kinda a geek for pc's... With that in mind, I ask: Why doesn't someone create a program that can be downloaded and placed on a SD card that will run during a smartphones boot up that will start the phone in a "Safe mode" and allow users to fix them.
I currently have a Samsung that keeps freezing when the logo appears. I have attempted to perform a "Soft reset" but it still freezes. I don't know were to turn, so here I am....
I apologize if I have posted this in the wrong forum... Any help with were i should go from here will be greatly appreciated.
try charging it and turning it on....or try to repeatedly take out the battery and then turning it back on.....it happens sometimes one mine
You also could run a logcat to see where the phone is hanging.
Are you running stock?
newboyx said:
You also could run a logcat to see where the phone is hanging.
Are you running stock?
Click to expand...
Click to collapse
will the phone go to download-mode? hold the volume-/camera/power for about 10secs it should get to a download screen so it can be reflashed, otherwise... well you know...
Sometimes this startup hanging happens for me & it will only boot w/o the SD card. Give that a shot.
This happens to me several times a month. The only solution that works consistently for me is:
1. Remove the battery
2. Wait for several minutes (Seems that some component needs to cool down, or capacitors need to drain, or something)
3. Then plug the battery back in
4. Reboot
i have found that when you hold down the Phone button for about a minute or so after you remove the battery , the phone will vibrate , do not remove your finger until the phone vibrates ...and it should boot from there.
Solution
I was talking to a tech rep at Virgin Mobile one day, and asked him if this was a common problem (knowing already that it was). Sparing you the details, what he told me is that when the intercept boots up, something gets jammed up with the 3G. And then the phone locks in the flashing logo phase. Now, EVERY single time I shut my phone down, I put it in airplane mode. It then reboots in airplane mode, and I almost never have a problem (meaning two or three times in the last 6 months). When is does happen, I reboot it again, and it boots right up. I presume that if need be, take it into a place with no signal and reboot it then.
Hello all, I'm curious to hear your thoughts and advice.
My nook is completely unresponsive. It is not stuck at rooted forever.
In fact this has nothing with a root attempt/reset/restore/power on.
I had done a a fresh reset/root with touchnooter about four months ago and was happily and smoothly reading for about two months. I then got busy and put the nook down, did not touch or use for about another two months. I tried to use it about a week ago but found that it had run out of battery in sleep after the two months of disuse (not surprising). I put it on charge overnight and everything booted right and functioned well once it turned on, except that the battery indicator in the statusbar showed a "?" and the battery info in system info showed 100% "unknown". After alot of fruitless research I put it down with the intention of reset/restore/root when I had the time.
I just picked it up this morning and was faced with the expected "Press then button below to wake up your NOOK" screen. But when I pressed the "n" button nothing happened. Obviously holding the "n" did nothing as well.
I tried to power it off and on- nothing
holding power for 20- nothing
power for 30- nothing
8 failed boots- nothing
left right- nothing
left right power-nothing
random pushing and holding of power- nothing
all these with mem card in and out- nothing
all these plugged usb- nothing
all these pugged ac- nothing
I let it charge some more- nothing
None of the buttons do anything, the screen stays inevitably at the " press the n button to wake" screen. no activity whatsoever except that when It is plugged in, the green light shows. NO ORANGE LIGHT... it is fully charged by both usb and ac.
It is not detected at all by windows anywhere.
In Linux- lsusb, bklid, and df -h yield nothing. My nook might as well be the invisible stupid ereader.
I did not drop it, sumbmerge it, perform magic around it... It has been sitting on a shelf doing nothing.
To repeat, the only thing my nook does is light up green when plugged.
It is unchangeably stuck on poe's face...
If this isn't true brick, I don't know what is.
I'm exhausted. Any ideas? I appreciate the help.
Best,
Thomas
i don't know. i just know my dog ate mine and i'm now in the market for a new screen, so if you don't get it working sell me the unit and get some money for yourself to purchase a new one =D
or you could google the disassembly instructions and try unplugging the battery, not very hard to do. could be of .. some help perhaps?
I would definitely take you up on your offer, but i'm still under warranty.
However, I would still like to have my original, and figure out what is going on and why it happened.
Ideas?
Thank you.
similar problem were solved
Hi! I might have read about similar problem solved on USB host mode here http://forum.xda-developers.com/showpost.php?p=23475998&postcount=131
That's it, thanks so much.
if it help
if it helps let them know in the tread that you had same problem. they are wondering whether it is due to host mode
[N2E]: After automatic update to 1.1, Nook Touch Screen absolutely DEAD--Nothing Work
THIS WAS A POST FROM ANOTHER SITE AS TO MY PROBLEM:
I was reading on my N2E last night. I put it down for about 30 minutes and when I came back it was displaying the default "Authors" screensaver (I had switched to the Nature photos) and asking to slide to unlock. I thought, "Oh, the new software update must have downloaded and installed. I'll check it out." To my shock, the touch screen was completely unresponsive--no amount of swiping would unlock from the screen saver. I let it set for a while longer thinking perhaps the softare update was not yet finished. No such luck.
As a result of the new update, my NOOK is now completly DEAD! I tried powering off, but couldn't do that because you are asked to confirm power off on the touchscreen, which no longer works. So, I looked online and tried the soft reset/reboot by holding down the "Home" or "n" button and then pressing the power button for several seconds. Great--it started rebooting...and came right back to the "authors" screen saver and asking to swipe to unlock. I tried this rebooting process several times, always with the same result: back to screeensaver mode with completely unresponsive touchscreen.
So, looked at the online technical troubleshooting discussion and helps and decided to try a downloaded manual install of the software update. Plugged my NOOK into my computer and it recognized it. So, I downloaded the manualo software update and dragged and dropped it onto the NOOK as directed and sure enough, it started to reboot itself. I thought, "whew, maybe this will fix it". NOPE--came right back to the locked screensaver, with no mention of attempting to update software, and the touchscreen is still dead. (By the way, all of this was done initially with the NOOK showing about 94% charged, so it was not a battery issue.)
Reconnected the NOOK to my computer and the software update file was gone from its home directory, which implies it did something with it. So, I tried repeatedly to install the software update manually, always with the same result: NOOK comes back to locked default "authors" screensaver wtih a dead touchscreen.
Looked online for B&N technical support again saw that others had this problem (though only found a couple references). Found the instructions to do a factory reset and reluctantly tried that, desparate to make my NOOK work again, but frustrated that if it did I would have to rebuild everyting on it and download my 400+ B&N book library all over again. But, guess what, factory reset just comes up to the "Welcome to your all-new NOOK" screen (sounds like progress), BUT the touchscreen is STILL dead, so I can't hit the "Next" button onscreen to proceed with setting up my factory-reset NOOK. Tried rebooting again (as this seems to be the only solution offered in the online tech support) and now it just keeps coming back to the "Welcome to your all-new NOOK" screen with a dead touchscreen keeping me from doing anything.
So, now I am taking it back to my local B&N store in hopes they will exchange it for a new NOOK.
I really want to see a feature to disable automatic updates in the future. I specifically didn't download and manually install when the update came out, figuring I'd wait for the automatic download to give time to B&N to work out the bugs and perhaps issue a patch (as they have done in the past for the N1E). Instead I get no warning about the automatic download (happens while I am reading and set the NOOK aside for 30 minutes), and then the update KILLS my NOOK.
I am not a satisfied NOOK customer at this point.
MY POST: (from the that site)
Not Sure how to do this post or whatever, but I was happy until the update and everything that happened to you is the same with me. This is the first post that describes what happened to me. I'm out of warranty and refuse (and can't) to buy another one of these. If their updates can do this, I'm not sure I want to sink another $100 into the shareholders pockets. I'd really like to know if anyone knows what may be wrong with it.
In addition to what was already mentioned, I took the battery out several times(which seems intimidating but very easy but voids the warranty) and took it completely apart cleaning the screen very well with water and another time a glass cleaner. I tried rooting also. Not sure of what to do now. It seems software related due to working fine until the update. Still at the "Welcome to your all-new NOOK" screen with unresponsive screen. I wasn't sure if the last sentence from B&N was a personal message to me welcoming me to the "new" state of the my nook.
Thanks for any help from anyone.
Thanks.
Identical problem.... and no fix..
It is a shame you got no solution for this. and the worst, you are not the only one... it happened exactly the same with my Nook ST....
Hopeless...
Machiavelli_The_Man said:
THIS WAS A POST FROM ANOTHER SITE AS TO MY PROBLEM:
I was reading on my N2E last night. I put it down for about 30 minutes and when I came back it was displaying the default "Authors" screensaver (I had switched to the Nature photos) and asking to slide to unlock. I thought, "Oh, the new software update must have downloaded and installed. I'll check it out." To my shock, the touch screen was completely unresponsive--no amount of swiping would unlock from the screen saver. I let it set for a while longer thinking perhaps the softare update was not yet finished. No such luck.
As a result of the new update, my NOOK is now completly DEAD! I tried powering off, but couldn't do that because you are asked to confirm power off on the touchscreen, which no longer works. So, I looked online and tried the soft reset/reboot by holding down the "Home" or "n" button and then pressing the power button for several seconds. Great--it started rebooting...and came right back to the "authors" screen saver and asking to swipe to unlock. I tried this rebooting process several times, always with the same result: back to screeensaver mode with completely unresponsive touchscreen.
So, looked at the online technical troubleshooting discussion and helps and decided to try a downloaded manual install of the software update. Plugged my NOOK into my computer and it recognized it. So, I downloaded the manualo software update and dragged and dropped it onto the NOOK as directed and sure enough, it started to reboot itself. I thought, "whew, maybe this will fix it". NOPE--came right back to the locked screensaver, with no mention of attempting to update software, and the touchscreen is still dead. (By the way, all of this was done initially with the NOOK showing about 94% charged, so it was not a battery issue.)
Reconnected the NOOK to my computer and the software update file was gone from its home directory, which implies it did something with it. So, I tried repeatedly to install the software update manually, always with the same result: NOOK comes back to locked default "authors" screensaver wtih a dead touchscreen.
Looked online for B&N technical support again saw that others had this problem (though only found a couple references). Found the instructions to do a factory reset and reluctantly tried that, desparate to make my NOOK work again, but frustrated that if it did I would have to rebuild everyting on it and download my 400+ B&N book library all over again. But, guess what, factory reset just comes up to the "Welcome to your all-new NOOK" screen (sounds like progress), BUT the touchscreen is STILL dead, so I can't hit the "Next" button onscreen to proceed with setting up my factory-reset NOOK. Tried rebooting again (as this seems to be the only solution offered in the online tech support) and now it just keeps coming back to the "Welcome to your all-new NOOK" screen with a dead touchscreen keeping me from doing anything.
So, now I am taking it back to my local B&N store in hopes they will exchange it for a new NOOK.
I really want to see a feature to disable automatic updates in the future. I specifically didn't download and manually install when the update came out, figuring I'd wait for the automatic download to give time to B&N to work out the bugs and perhaps issue a patch (as they have done in the past for the N1E). Instead I get no warning about the automatic download (happens while I am reading and set the NOOK aside for 30 minutes), and then the update KILLS my NOOK.
I am not a satisfied NOOK customer at this point.
MY POST: (from the that site)
Not Sure how to do this post or whatever, but I was happy until the update and everything that happened to you is the same with me. This is the first post that describes what happened to me. I'm out of warranty and refuse (and can't) to buy another one of these. If their updates can do this, I'm not sure I want to sink another $100 into the shareholders pockets. I'd really like to know if anyone knows what may be wrong with it.
In addition to what was already mentioned, I took the battery out several times(which seems intimidating but very easy but voids the warranty) and took it completely apart cleaning the screen very well with water and another time a glass cleaner. I tried rooting also. Not sure of what to do now. It seems software related due to working fine until the update. Still at the "Welcome to your all-new NOOK" screen with unresponsive screen. I wasn't sure if the last sentence from B&N was a personal message to me welcoming me to the "new" state of the my nook.
Thanks for any help from anyone.
Thanks.
Click to expand...
Click to collapse
The factory restore does not actually fix every possible problem with your Nook.
If your Nook responds at all, try to boot it up on an SD card like ClockworkMod or noogie.
At least that way you can see what is happening.
The partitioning might have become corrupted which the "factory restore" does not touch.
If no response with anything, try disconnecting the battery.
You might also try booting over USB using the techniques in rooting the new white glow.
Hello I was wondering if I'm just screwed I bought 2 nook simple touch, one for me and one for a present to my mother for her birthday on march 16. I bought them at best buy for $40 a piece on January 30. I used mine and was perfect but when I tried to set up my mom it wouldn't load the license agreement, always got stuck or reboot or something, so I loaded cwm on an sd card just to play around, tested on my nook and was fine, then put it on my moms nook booted once then I didn't press anything and turn it off then I load the image but when I tried to boot again it got stuck on the load screen and wont do anything, no reset sequence will work with the sd card on or off the other nook boots with this sd card. at the end I exchanged with my mom she is happy with her nook an I have a useless unit do you think they will exchange it I didn't rooted it or did anything to it but has the n cwm splash on screen forever. I'm in Costa Rica right now and wont return home until May do you think I'll might be able to exchange it or should I just try to repair it.
I'm glad that your mother got the working one!
You say that that one will boot on your CWM SD card, but yours won't?
It may be hard to get your unit exchanged with a conspicuous screen on it, even if it's not your fault.
When you plug it into your desktop is there any indication of a new USB device found?
If it's charged and no amount of the power button gets a reaction, I'd open it up.
any news???
Hi endor43, same problem here, have been able to find any solution?
endor43 said:
Hello all, I'm curious to hear your thoughts and advice.
My nook is completely unresponsive. It is not stuck at rooted forever.
In fact this has nothing with a root attempt/reset/restore/power on.
I had done a a fresh reset/root with touchnooter about four months ago and was happily and smoothly reading for about two months. I then got busy and put the nook down, did not touch or use for about another two months. I tried to use it about a week ago but found that it had run out of battery in sleep after the two months of disuse (not surprising). I put it on charge overnight and everything booted right and functioned well once it turned on, except that the battery indicator in the statusbar showed a "?" and the battery info in system info showed 100% "unknown". After alot of fruitless research I put it down with the intention of reset/restore/root when I had the time.
I just picked it up this morning and was faced with the expected "Press then button below to wake up your NOOK" screen. But when I pressed the "n" button nothing happened. Obviously holding the "n" did nothing as well.
I tried to power it off and on- nothing
holding power for 20- nothing
power for 30- nothing
8 failed boots- nothing
left right- nothing
left right power-nothing
random pushing and holding of power- nothing
all these with mem card in and out- nothing
all these plugged usb- nothing
all these pugged ac- nothing
I let it charge some more- nothing
None of the buttons do anything, the screen stays inevitably at the " press the n button to wake" screen. no activity whatsoever except that when It is plugged in, the green light shows. NO ORANGE LIGHT... it is fully charged by both usb and ac.
It is not detected at all by windows anywhere.
In Linux- lsusb, bklid, and df -h yield nothing. My nook might as well be the invisible stupid ereader.
I did not drop it, sumbmerge it, perform magic around it... It has been sitting on a shelf doing nothing.
To repeat, the only thing my nook does is light up green when plugged.
It is unchangeably stuck on poe's face...
If this isn't true brick, I don't know what is.
I'm exhausted. Any ideas? I appreciate the help.
Best,
Thomas
Click to expand...
Click to collapse
There are times when a Nook gets in a mode where it won't accept a charge.
Opening it up and disconnecting the battery for a minute might fix this.
endor43 said:
That's it, thanks so much.
Click to expand...
Click to collapse
When this worked for you did the light turn orange right when you plugged the battery back in? I just took the battery out, plugged the nook into a charger, and with it plugged in plugged the battery back in and the light stays green the whole time yet I'm not able to use the nook at all.
My nook second generation is not responding to my touch I tried everything to get it to work and I eventually got it to completely power of what if it does not work when I turn it on what should I do
It could be power/battery problems.
Check to see if it makes itself known when the USB is plugged in.
If it reacts at all, that's an indication of life.
Hi,
I have a Galaxy S4 i9505 LTE which is is rebooting every 10 minutes and sometimes even every minute.
I have also flashed the phone using odin to I9505XXUENAA 4.3 and wiped both userdata and cache partitions, to ensure all data has been lost. However the phone still does the reboots. The reboots only happen if the phone happens to be in sleep and running on battery, if the phone is either connected with the USB or with the screen on, it simply won't restart however if a certain time passes and goes to sleep then after 10 seconds it triggers the reboot.
Maybe this can even add some more info I noticed that exactly at the time before a restart is about to happen (the phone is currently in sleep state) if you press either the home or power button to wake it up, it simply does not show the screen and after few seconds you can hear a short vibrate then another short vibrate and the Samsung Logo appear.
I have also tried to monitor the logcat through ADB, and I tried to study the log for the E/ logs. Basically every minute or so the following line is printed on the logs:
Code:
E/watchdog (xxx) [email protected] Y
(where Y is a incremental number starting from 0 from the time booting)
Attached here is also a copy of the logcat textfile generated. (Sorry I had to archive it as it is too large to attach)
Do you think this is a software or hardware issue, it seems that an android watchdog timer is not happy with some sort of thing, can anybody help me?
AnArChYm said:
Hi,
I have a Galaxy S4 i9505 LTE which is is rebooting every 10 minutes and sometimes even every minute.
I have also flashed the phone using odin to I9505XXUENAA 4.3 and wiped both userdata and cache partitions, to ensure all data has been lost. However the phone still does the reboots. The reboots only happen if the phone happens to be in sleep and running on battery, if the phone is either connected with the USB or with the screen on, it simply won't restart however if a certain time passes and goes to sleep then after 10 seconds it triggers the reboot.
Maybe this can even add some more info I noticed that exactly at the time before a restart is about to happen (the phone is currently in sleep state) if you press either the home or power button to wake it up, it simply does not show the screen and after few seconds you can hear a short vibrate then another short vibrate and the Samsung Logo appear.
I have also tried to monitor the logcat through ADB, and I tried to study the log for the E/ logs. Basically every minute or so the following line is printed on the logs:
Code:
E/watchdog (xxx) [email protected] Y
(where Y is a incremental number starting from 0 from the time booting)
Attached here is also a copy of the logcat textfile generated. (Sorry I had to archive it as it is too large to attach)
Do you think this is a software or hardware issue, it seems that an android watchdog timer is not happy with some sort of thing, can anybody help me?
Click to expand...
Click to collapse
My mate has a i9500 and it was rebooting at random. He took it to the Samsung Repair Centre here and they replaced his battery on the spot. Since then he hasn't had any random reboots. Apparantly there was a faulty batch of batteries with serial numbers starting with BD
It could be that you have a similar case. Might be worth the check.
Thanks Gboss01 for your reply, I quickly checked the serial number basically phone's serial starts RF and battery serial starts with LC.
I have already tried changing the battery as the current battery was exposed to high water damage, the other battery I tried with is a shop battery which we use for just testing to check whether or not a samsung s4 powers on. However tonight I will try to install a new battery and see how it goes.
Basically my S4 was bought in pieces, and all parts were subjected to the water damage, however the board was offered from a friend (from a complete different handset) who decided to scrap his phone after he has smashed the screen, so the board is clean (even checked it under a microscope), that is why I'm ruling out hardware problem at the moment.
AnArChYm said:
Thanks Gboss01 for your reply, I quickly checked the serial number basically phone's serial starts RF and battery serial starts with LC.
I have already tried changing the battery as the current battery was exposed to high water damage, the other battery I tried with is a shop battery which we use for just testing to check whether or not a samsung s4 powers on. However tonight I will try to install a new battery and see how it goes.
Basically my S4 was bought in pieces, and all parts were subjected to the water damage, however the board was offered from a friend (from a complete different handset) who decided to scrap his phone after he has smashed the screen, so the board is clean (even checked it under a microscope), that is why I'm ruling out hardware problem at the moment.
Click to expand...
Click to collapse
No prob, I hope you get to the bottom of your random reboots.
Gboss01 said:
No prob, I hope you get to the bottom of your random reboots.
Click to expand...
Click to collapse
Hey,
After numerous attempts via software, battery replacements and even trying to rewrite the bootloader of the phone via riffbox, I concluded it was coming from the board, basically after a bit more testing found out that during standby the phone heats up, enough to trip the main power management chip which then reboots the phone to not let the phone from overheating. Basically I replaced this chip and everything is working fine I think the phone was smashed pretty bad when my friend "dropped" it as I could notice some contacts from under the chip which were not making proper contact with the board.
Hey friends of the beloved Note 4, I was deeply gutted by the malfunctioning of my phone. I have been using an N9100 for the past 6 months. The phone was new out of the box (manufactured in July 2016), with stock marshmallow installed. I rooted it by flashing cf-auto-root through odin. Everything was fine and dandy until 2 weeks ago, when reading comics (presumably not a particularly taxing job for the hardware) its screen suddenly started to glitch then the phone completely died. I found one useable recovery firmfare from trial and error to revive the phone (Kitkat 4.4.4). But the symptoms persists, which sounds eerily familiar to but somehow different from the infamous emmc failure:
1. A grey bar appears at the bottom left of the screen for 1-2 seconds when booting up;
2. Reboot or bootloop occurs when waking up the phone after display timed out or pressing the power button;
3. Screen glitches and phone randomly reboots from time to time;
4. Recovery mode cannot be accessed most of the times, even after freezing the phone in the refrigerator;
5. The tried and true wakelock revamp app is unable to stop the phone from going to sleep and rebooting.
It seems the phone itself is seriously compromised. What maybe the root cause of this nuisance? And more importantly, is there any solution to it other from switching the motherboard, that is logistically and economically sound?
Alas, roses are red and Samsung phones are high maintenance...
Switching motherboard will create a lot more issues.
It looks like the EMMC is dying. Search about it. Also someone found a solution to insert a heat artic pad underneath the eMMC and apparently it worked. Also search about this.
Hi, i have a bit of a problem with my own Huawei G7: it wants to stay dead.
Just to give a quick "backstory" of the device in question:
I've been owning it since 2015, so far so good, but after 3-4 ish years of usage it started to get issues without doing any particular stuff (ex. rooting, unlocking bootloader, etc.). I've used to update the phone whenever updates came out, and i was exactly on the latest M release.
Since i've got that update and, to add, a newer phone in late 2018, the phone decided to kill off itself.
Each time i've booted up the thing, it was making more and more struggle to boot up into android- even to a point of getting into a bootloop, or straight out softlocking after the bootup animation or EMUI trying to fix itself.
Latest times i've got it to boot the device up correctly, it worked fine, honestly-
no apps crashed, no strange behaviors from the os, but the only bad part were pics from my gallery got corrupt (not all, but a good chunk of it).
After next bootups i've tried, it decided to show no life except the notification LED.
The screen was dead, no vibrations started when booting up, but only the LED displayed a certain order of colors (blue, green, red, orange- then the pattern repeated).
After a long while, i've recently took it back to give it a fix.
At first i tried following typical solutions given on the internet, like:
button combos to boot the device into different modes, load an sdcard with an update.app package on the dload folder, even making it charge for an extended while (around 1-2hs) and see if it worked- but the phone was still dead, still shown the LED pattern.
Moving on, i decided to move to the manual work:
Disassembling, reassembling, plug off different modules (+ battery) and attach them back, also attempting to charge while i had detached the battery's pins with my nails. Still no signs of life happening. I've tried everything except one very thing: short the pins and boot it up to EDL mode (since it has QCom chip).
So, as a last resort, i've tried to search far and wide on the internet about a QCom FW for this specific device.
None to be found, except few useful sites:
The device's page over PostmarketOS' wiki (that's how i've found out about the points to short on the board);
Huaweistockrom's page on the device (i refuse to hyperlink it because their .xml file inside the .zip made QDL puke out errors about it having no correct syntax on the code. Didn't bother myself to fix it alone- also has 'wares inside, so i won't break a rule);
An obscure thread found over gsmturkey.net (the only one offering a perfectly functioning FW. If it doesn't load for you, here's an archive.org snapshot) + a functioning DL link;
Without further ado, i've went trial & error flashing the FW dump from gsmturkey's site over my phone's board via triggering EDL with pin shortage (with my rooted phone on the terminal to flash it).
Didn't felt like it took much, but i saw the terminal was reporting the partitions being written successfully, then QDL disconnected and printed somewhere in the text (possibly flagging it has flashed the FW successfully):
Code:
"partition 0 is now bootable."
By now, the phone should have shown signs of life- like the screen turning on or anything (like i previously did with another QCom phone).
Phone was still dead, but on the bright side: no more colored LED pattern!
I tried booting it up manually, even doing key combos, disassembling it and do other shenanigans to make it work:
the phone still was dead, but the only functioning thing was the red LED showing any signs of the battery charging- but at some point it turns off, no signs of the green LED nor the screen printing any cool battery level animation (like it should normally do on any phone when the OS isn't on).
Moving on, i gave a good ol surf around the web and found out something: this issue isn't uncommon at all, it exists even on older Huawei models.
For example, i saw across XDA itself and other android-centric blogs the specific issue of "LED turning on when charging, but phone doesn't turn on" kind of deal.
If i were to link up several for proof:
A P10 Plus facing a similar issue, over Huawei's consumer help page;
A very exact problem of what i've used to have too, over HTCMania (spanish page);
Same page, this time is about a G610;
Several users having the same malfunction, over the Ascend G6's XDA page;
A Huawei Mate 20 Pro, shared over r/Huawei's sub;
Another person- but this time's about the colored led thing, over Android Central;
Aside the list, i wonder if either the colored LED thing is a code for the motherboard or EMMC dying (even though convinced more of the mobo, if the EMMC wasn't alive: then none of the flashing could have took place) or a planned obsolescence made by Huawei for their own devices.
Whatever that is, i'll await for answers if my issue would be resolvable- or atleast bypass this red LED and black screen issue without putting extra expenses to buy new components (i was very affectionate of this device and would like to revive it in order to extend it's lifespan).