Hello
Newbie here
So I've been wondering, what's actually happening on the "ur device can't be trusted screen" on unlocked bootloader device. Is it just a message with delay period? Does it do essential boot up on the back ground? Can I perhaps turn it off and speed up booting process?
Been very curious since it says " your device will start after 5 seconds". I mean, how could they know it took 5 seconds? What if it could be changed to 0s?
It's a delay counter. It replaces the default initial (non-animated) boot screen, so it might also be longer than 5 seconds.
It is just a delayed message. Trust me, the linux kernel can boot up insanely fast on g5s plus's hardware.
Custom ROMs cannot change this delay because it is coded into bootloader, which is very difficult to modify.
Related
My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
tdrussell said:
My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
Click to expand...
Click to collapse
ask franco if fsync is enabled default and if is barrier=0 in the kernel
Try holding in the power button for 45-60 seconds. If that doesn't work then Plug in the unit, and let it try to charge for an hour or two. Then try holding in the power button for 45-60 seconds again.
There seems to be a glitch where the unit will die when the battery is low. Some people have report something similar when the unit was ~23% battery life.
Apologies if this is the wrong area for this or if up to date information is available, but I can't find any solutions anywhere.
My daughter has a pre-paid Virgin HTC Desire 510 that she has had for some time, but just started acting up today. Starting from off, it boots up and goes to the home screen fine. Then 35 seconds later (I've timed it several times) it shuts down. No matter what you are doing it goes black, just as if you pulled the battery. Then it boots up again automatically and continues the same cycle indefinitely until the battery is pulled.
I've been searching for the last 3 hours and have tried every remedy I've read, from checking the battery connections, wedging a small piece of paper there to force a better connection, and trying a new battery, to booting it without the sim card, without the sd card, and without both. Makes no difference, the phone is usable for 35 seconds, then power cycles. One interesting note on this though, if I try to manually shut down the phone, as soon as I press "shut down" or even "restart phone", it instantly shuts off the same as at the 35 second mark. Instant black screen with no proper shutdown sequence.
I (and she as well) have conceded to just wiping the phone entirely to attempt to fix the problem. Only that doesn't work either. I found that in order to do a factory reset, the "fast boot" option must be turned off in the power settings. Her's is not. In the 35 seconds I have to go into the menu, I can deactivate the setting, but it always hits that 35 second mark and turns off just after I do. After rebooting (either by letting the cycle occur, or pulling the battery and booting fresh) the "fast boot" section is still valid. In fact, I even went so far as to try to move icons around, change other settings, etc. to see if anything sticks after the boot cycle and nothing does. It seems the improper shut down that occurs prevents any previous changes from being saved. In turn, this prevents the phone from doing a factory reset.
Now, I've tried the factory reset several times and it always reboots with the same normal home screen, 35 second function, then power cycle. I've also tried recovery mode as well but it just stays on a black screen with a red triangle and "!" inside until battery pull.
This is about all the information I can dig up or provide without any further insight. I will say that I'm not that comfortable with my skill at attempting anything that requires downloading and transferring any kinds of files to the phone and installing them manually, as I'm not THAT savvy when it come to things like rooting phones, etc.. So if there are ANY solutions short of "rooting", "unlocking", "bootloader", etc that I just don't know much about, please let me know.
Thanks for any and all help, I will attempt any possible solutions I am able!
Hmmm....this sounds strange. The things you described could be from a bad kernel. But you haven't tried to root it yet so that rules out the bad kernel. I think that you should reinstall the whole system using an RUU. That is your best shot at this moment. If that also doesn't resolve your issue, your only option will be to root your phone and install a custom ROM. If you have any questions, don't hesitate to ask
psycho76384 said:
Apologies if this is the wrong area for this or if up to date information is available, but I can't find any solutions anywhere.
My daughter has a pre-paid Virgin HTC Desire 510 that she has had for some time, but just started acting up today. Starting from off, it boots up and goes to the home screen fine. Then 35 seconds later (I've timed it several times) it shuts down. No matter what you are doing it goes black, just as if you pulled the battery. Then it boots up again automatically and continues the same cycle indefinitely until the battery is pulled.
I've been searching for the last 3 hours and have tried every remedy I've read, from checking the battery connections, wedging a small piece of paper there to force a better connection, and trying a new battery, to booting it without the sim card, without the sd card, and without both. Makes no difference, the phone is usable for 35 seconds, then power cycles. One interesting note on this though, if I try to manually shut down the phone, as soon as I press "shut down" or even "restart phone", it instantly shuts off the same as at the 35 second mark. Instant black screen with no proper shutdown sequence.
I (and she as well) have conceded to just wiping the phone entirely to attempt to fix the problem. Only that doesn't work either. I found that in order to do a factory reset, the "fast boot" option must be turned off in the power settings. Her's is not. In the 35 seconds I have to go into the menu, I can deactivate the setting, but it always hits that 35 second mark and turns off just after I do. After rebooting (either by letting the cycle occur, or pulling the battery and booting fresh) the "fast boot" section is still valid. In fact, I even went so far as to try to move icons around, change other settings, etc. to see if anything sticks after the boot cycle and nothing does. It seems the improper shut down that occurs prevents any previous changes from being saved. In turn, this prevents the phone from doing a factory reset.
Now, I've tried the factory reset several times and it always reboots with the same normal home screen, 35 second function, then power cycle. I've also tried recovery mode as well but it just stays on a black screen with a red triangle and "!" inside until battery pull.
This is about all the information I can dig up or provide without any further insight. I will say that I'm not that comfortable with my skill at attempting anything that requires downloading and transferring any kinds of files to the phone and installing them manually, as I'm not THAT savvy when it come to things like rooting phones, etc.. So if there are ANY solutions short of "rooting", "unlocking", "bootloader", etc that I just don't know much about, please let me know.
Thanks for any and all help, I will attempt any possible solutions I am able!
Click to expand...
Click to collapse
Has she done anything to the phones files? (deleting stuff you shouldn't?).. RUU for Virgin Mobile - Run from a Windows computer. http://dl3.htc.com/application/RUU_A11_CHL_K44_DESIRE_SENSE60_Sprint_WWE_VM_1.49.652.3_Radio_1.47.40.0224_NV_SPCS_1.08_003_release_448617_signed_2.exe
Thanks for the responses. It seems like fixing this phone would be more trouble than it's worth for me, as it wasn't an expensive phone and I have no experience rooting phones, lol! I think she has money saved up and wants a new one anyways. Thanks for taking the time help out!
I've got a strange bootup problem that I can't find any help on. My S20 FE 5G fails to boot properly on every other bootup. On the failed bootups, it spends 3-5 minutes on the initial Samsung S20 FE 5G splash screen (the one with the android logo). When it eventually gets past that screen, it boots up to the lock screen and prompts me to swipe, but all touch input is ignored. My only option is to hold power and volume down to force a power down. Powering back up, it will boot normally, spending only a few seconds on the splash screen before booting up and functioning as expected. It's been doing this for a long time, and today I finally got annoyed enough to try a factory reset, which hasn't solved the problem. I also lined up a safe mode boot with a failed boot, and the touch screen still didn't work in safe mode. Anyone know enough about how these phones boot up to explain why this alternating pattern of failures might occur? Is it alternating between two images of the OS and one of them is possibly corrupted? Is there any debugging method I can use to try and figure out what's going on?
I'm new here, so if there's a better place to ask this question, please let me know. Thanks!
I'd try flashing a stock rom to the phone, see that fixes it. if it doesn't you should get Samsung to look at it.
Hello dear community,
Something really strange happened with my device about 1.5 years ago, but since I still keep it in my house, I can't help but wonder what happened and is it fixable.
So, the story: In some sunny day in July/August of 2020 I was browsing through my device, then I locked the screen and few seconds later I remember that I want to check something, so I pull the phone out of my pocket, use my fingerprint or face to unlock it, then just during the screen unlock animation (that takes ~1 second to "expand"), the device froze halfway through and would become unresponsive. By that I mean that the touch did not work, nor the Power/Vol/Bixby buttons. The phone heated up so much that in the span of a few seconds, the metal frame got so hot that it burned the skin of my hard, then a few more seconds after, the screen went black. This was the last time the device had worked in any way.
What have I tried to do to ressurect it:
Turn it on via the power button
Plug it in a PC with Odin - Odin did not pick-up the device
Let it charge overnight
Any possible button combination to get to various screens (fastboot, etc)
What I believe happened: Since I was running a custom ROM I believe that when I unlocked the device, something went wrong in the code and it caused the device to freeze and the heat was produced by frying the SoC or something else. Taking the back glass did not show any visible (and smellable) damage.
What do you think ? Is there something that you can suggest me to try to bring the device back to life ?
Thanks in advance!
If you can't get into fastboot, download mode, recovery mode, etc. Then your phone is probably - in my experience - subject to a physical repair.
Hello. For a while now, I haven't been able to see anything when I boot my device into recovery mode. The screen remains blank unless I press the power button, which makes my device reboot. I can boot ok into bootloader but even when I try booting into recovery from bootloader, I still don't see anything on the screen.
Also, whenever I boot up my device, after the "Galaxy s20 fe 5g | Powered by Android" pops up, instead of showing the Samsung logo, my screen goes blank, and it stays like that until the boot is done. The only way I know my device is booted up is by a vibration.
I feel like the two problems are related. Is there something that can be done?
flash your firmware, if that doesn't fix it go see a Samsung service engineer.
But is it possible to also root my phone? I'm using the S20 FE 5G US version (G781U). I heard the bootloader in itself isn't unlockable.
no not possible unless you've not bothered to update for nearly a year.
Hi.
Please my brightness doesn't increase past the 50% level. Increasing it above that won't change the brightness. The brightness remains the same from 50% through to 100%. Is this a bug or something?
I don't have adaptive brightness on by the way so I know it isn't the problem. I've heard stores that people who backup settings from other phones and restore into new phones usually get this problem. What can I do?
[email protected] said:
Hi.
Please my brightness doesn't increase past the 50% level. Increasing it above that won't change the brightness. The brightness remains the same from 50% through to 100%. Is this a bug or something?
I don't have adaptive brightness on by the way so I know it isn't the problem. I've heard stores that people who backup settings from other phones and restore into new phones usually get this problem. What can I do?
Click to expand...
Click to collapse
you could try finding your settings apps and wiping their data. you'll have to bring up your system apps to do that... remember all device settings will go doing that.