Hi all,
I've had my bootloader unlocked since practically my first day with the phone. The phone has always exhibited this behavior, but I've just now decided to try and fix it if I can. Basically, on the warning screen about the bootloader, it says you can hit the power button to pause boot, and then power again to resume boot. My 6T does not allow for this. If I'm extremely quick about it, I can do it, but after a second or so on that screen, it seems to lock up until it continues booting. No buttons do anything. If this happens after I click the power button the first time, but not the second, it hangs for much longer, since I paused the boot but have no way of resuming it. My OnePlus 5 does not do this. At any point while that screen is showing, I can hit the power button twice on it to continue booting. It is just the 6T that freezes like this. Does anybody else experience this, or does anybody have a fix?
Thanks
PokemonTotalWar said:
Hi all,
I've had my bootloader unlocked since practically my first day with the phone. The phone has always exhibited this behavior, but I've just now decided to try and fix it if I can. Basically, on the warning screen about the bootloader, it says you can hit the power button to pause boot, and then power again to resume boot. My 6T does not allow for this. If I'm extremely quick about it, I can do it, but after a second or so on that screen, it seems to lock up until it continues booting. No buttons do anything. If this happens after I click the power button the first time, but not the second, it hangs for much longer, since I paused the boot but have no way of resuming it. My OnePlus 5 does not do this. At any point while that screen is showing, I can hit the power button twice on it to continue booting. It is just the 6T that freezes like this. Does anybody else experience this, or does anybody have a fix?
Thanks
Click to expand...
Click to collapse
Not sure really, I have never hit the power button on boot or reboot.. what's the point?
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Not sure really, I have never hit the power button on boot or reboot.. what's the point?
Click to expand...
Click to collapse
It speeds up the boot. Regardless, it feels like my 6T takes longer to get past that screen than my 5 did. It seems to be a genuine hang for some reason
I usually let it be, and it will just boot on its own. However, when the Linux kernel does finally load, the whole boot process's usually fast. I wish I could remove or just change the look of the unlocked bootloader warning. I will just pretend it's the OnePlus logo boot splash.
Sent from my OnePlus 6T using Tapatalk
There is nothing you can do to modify the behavior or content of this screen. Nor you can't remove it. It's hardcoded and not accessible from kernel or any software.
Just leave it
As long as i remember, me too unlocked my OP6 from the first day, and i don't remember that pressing one of the buttons really changed anything lol, it never did for me
Related
I have a bell atrix unlocked boot loader, rooted. The problem is when the phone is off, the slightest pressure on the power button turns on the phone. Normally with other phones you have to press and hold the power button for a few seconds before it turns on, this one the slightest push and it boots up! This is very frustrating I was wonder if others have the same issue, if theres a fix?
I have tried over 6 custom roms, and its the same issue. I cant remember if the phone was like this before unlocking the boot loader, as I unlocked it first day.
It's normal for ours phone...
Hey guys, I was wondering if anyone could help me troubleshoot my Galaxy S4 which turns itself off every time I power it on. Basically, I'll hit the power button and the Samsung logo will pop up with the the lock icon showing that the device has been rooted. Then, after a few seconds the screen will go black at which point I am unable to do anything to it other than pull the battery out and repeat the process. If I wait a few minutes though, I am able to push the power button without having to pull the battery out. In addition, if I attempt to pull the recovery menu up, it will begin to load but as before, the phone will turn itself off before I'm able to do anything useful. At one point I was able to somehow get it to load Android though that may have just been pure luck at work.
I don't believe that my root access is at fault here because I've had it for several months with no trouble to note. Immediately before this happened my power button began acting strangely in the OS. I attempted to factory reset in order to fix this and that's when this problem started. The only other which that I can think of that may have caused this is Safestrap which I uninstalled shortly after the power button began acting up.
Does download mode also reboot? Then it's definetely some hardware malfunction.
By the sound of it it's a malfunctioning power button.
Thanks!
Lennyz1988 said:
Does download mode also reboot? Then it's definetely some hardware malfunction.
By the sound of it it's a malfunctioning power button.
Click to expand...
Click to collapse
Thanks for the help Lennyz, I was starting to think the same thing myself. I'll have to take it in for repairs.
Hello
This is my first post here and I'd really appreciate advice in this matter.
I've spent the past couple of hours searching for an answer but nothing works or totally irrelevant results.
I have a problem where I'd rooted my phone with KingRoot, changed it to SuperSU successfully (restarted my phone several times since then and no issues)
I installed TWRP (only the app) from the Google Play store and that's as far as I got before I powered off my phone to cool down before attempting any installation of TWRP. Powered on my phone and I can't get past the Samsung logo.
Recovery won't come up, Download mode works but restarts itself and volume buttons do nothing to let me confirm download mode and so it's sending me in a loop. Samsung logo and restart again and again. I insert my battery and the first thing that happens is my phone goes on a mission, determined to power itself on only to Bootloop.
No, before anyone suggests it be a hardware issue, it's a brand new phone. There's nothing wrong with the buttons.
If anyone is going to point out the obvious in saying that I'm responsible for rooting my device, I'm aware of this. The rooting procedure was a one-click method which was successful and caused no boot issues after restarting the phone countless times.
Basically:
Bootloop
Can't access recovery
Can't get to Download mode without it getting back into the bootloop after 5 seconds or so. Volume buttons do nothing to confirm download mode.
USB debugging wasn't enabled before this Bootloop occurred
Do I have a paperweight or is there a way to salvage something from this?
The phone isn't supposed to power itself on after inserting the battery.
This behavior is only acceptable when the phone is plugged in while inserting the battery. But even so, the phone wouldn't try to boot up, it would just display the charging animation.
i had a similar problem where my phone would boot up to the white samsung logo as soon as i insert my battery. tirned out the power button was stuck. try gently knocking the power button onto the corner of a table or something with the battery pulled out. it might work for you if your problem is what i think it is.
GDReaper said:
The phone isn't supposed to power itself on after inserting the battery.
This behavior is only acceptable when the phone is plugged in while inserting the battery. But even so, the phone wouldn't try to boot up, it would just display the charging animation.
Click to expand...
Click to collapse
Thank you for your response but would you like a video to prove that it is in fact attempting to boot up when inserting the battery?
adrxano said:
i had a similar problem where my phone would boot up to the white samsung logo as soon as i insert my battery. tirned out the power button was stuck. try gently knocking the power button onto the corner of a table or something with the battery pulled out. it might work for you if your problem is what i think it is.
Click to expand...
Click to collapse
Oh my god you are amazing thank you so much! Wow. I really appreciate this you've fixed the problem. Thank you!!!
Thanks to all for the time taken to read this and for the responses
Lol it feels great to be helpful.
Sent from my GT-I9500 using Tapatalk
BackShooter said:
Thank you for your response but would you like a video to prove that it is in fact attempting to boot up when inserting the battery?
Click to expand...
Click to collapse
I tested it on my device (I9505) and it doesn't boot up, it just turns on to display the charging animation. If I want it to boot up I have to hold the power button.
So, in conclusion, it must be your power button.
You can say the phone is new as much as you want, but there is a chance it came with a factory defect.
There might also be a possibility it is refurbished phone, which means it is pseudo-new.
GDReaper said:
I tested it on my device (I9505) and it doesn't boot up, it just turns on to display the charging animation. If I want it to boot up I have to hold the power button.
So, in conclusion, it must be your power button.
You can say the phone is new as much as you want, but there is a chance it came with a factory defect.
There might also be a possibility it is refurbished phone, which means it is pseudo-new.
Click to expand...
Click to collapse
You're correct, thank you again I thoroughly appreciate your time and help with this
Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!
edlovereze said:
Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!
Click to expand...
Click to collapse
Sounds like you may have more than one problem, but many have been able to get a dead phone to start by holding the power button down for a very long time, sometimes 2 minutes or more. If it doesn't start, fully charge it and try the power button again. Assuming you are stock with a locked boot loader.... you didn't mention.
My phone is stock with a locked boot loader. I held the button for over 5 minutes and got nothing. I'm wondering if Google would be willing to help me out. Unless anyone has other ideas
It's hopeless. Don't waste your time trying to revive. Contact Huawei regardless of date of purchase.
If it won't power on it's either not charged, a bad power button, or something with pcm. Which is on Motherboard.
Most common scenario is a bad power button because it's most used breakable part. That won't allow the board to receive power or not enough power if it's shorted.
Dunno if you've poked around the interwebs some more regarding this, but I've been slammed with the N6P bootloop error (which appears might be part of your problem) and I found a stop-gap solution. If you feel like you've got nothing to lose, you can try what I've done: Make sure the phone has a little charge, hold it with a hot mitt from your kitchen, and blast the back of your N6P in the region between the camera lens and the fingerprint sensor with a hairdryer. Doing so will trip the big cluster off, which is the source of the bootloop problem. If you can get it to boot to the Google logo, applying the heat for the right amount of time (maybe not too long.. 2-4 minutes tops) may cause it to make it to the spinning color graphics and beyond.
I've been able to resurrect my phone doing this, but only to back it up and do very simple tasks. The moment I do something processor-intensive (Waze, YouTube, etc) it immediately crashes and bootloops again. The only solution beyond this is to unlock your bootloader, download EX Kernel manager and use it to completely disable the big cluster. Then your phone will likely be reliable, but extremely hobbled.
I bought from Best Buy about 16 months ago, so both Google and Huawei have been utterly useless, which is infuriating. Shenanigans like this are criminal. This is my 3rd Nexus phone and I'm considering abandoning Android altogether after this experience.
My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe
Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.
there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..
Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx
Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs
Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.