Related
Hey everyone, I'm trying to upgrade from Myn's Warm Eclair [BETA 1] (I know, I know, lol I should check here more often...) to Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] [7/8/10] (the download link that says "DOWNLOAD RLS10" in large orange font underneath the "What Doesn't Work" secton on his 1st post.
I'm doing what I usually do to install android, which is:
download the .nbh (which is voguimg-240x320-froyo-08-07-10.nbh)
rename it to RUU_signed.nbh
place it in the ROMUpdateUtility
add the ANDBOOT folder to the root of my SD card
placing the androidinstall.tar file inside
holding the power and camera buttons to boot into the RGB 'usb' screen
then running the ROMUpdateUtility to install it and boot up the linux
in linux I hold down the center button to get the the install menu
then install both system and data to the NAND (since I don't have partitions on my 8 gig SD
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
this happens to me all the time. the question you need to ask is "is the device getting to the desktop?" and "is the operating system fully loading to a usable state?"
in my experience answering either of these questions 'yes' puts you in a good position. there have been reports of boot sequence taking up to 20 mins. personally, i can make it to desktop in about 10 mins every time.
hope it helps.
sometimes you just need to format the sd card to fat32 again then try reinstalling after putting the files back on the card of course. if the sdcard is formatted wrong then it wont be able to read the directory and will give you that error
Darkstarrdp said:
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
It's not a problem - this is the permission setting - ignore the messages
Just let it get back to the install screen, and then hit Quit or soft-reset device.
Then wait about 10-15 minutes for first boot and go through startup setup
Reboots are quicker, maybe anywhere from 2-4 minutes.
I overclocked my vogue to 496mhz with no issues & I guess some people hit 510mhz safely.
Just to add, Ive been running at 520 for a month now without noticing any major adverse effects...Sorry to chime in
I second wisconsinated's note -- I had this problem last night. I reformatted the card as FAT32 and things went as expected after. Not sure why they tanked in the first place, but I suppose that's not important, right?
ill third that. a reformat of my microsd did the trick.
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
ericbond said:
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
Click to expand...
Click to collapse
oddly enough, with an experimental operating system, one needs to exercise extreme patience at times.
glad its all in order for you now
Thanks guys, I got it to finally install after the third try, I guess it was just having hiccups trying to install. Everything's good now.... OS installation side at least.
Now I have a different problem... my touch sensitivity is kinda out of whack.
it's like touch screen is dead half the time, on my stock sprint ROM it will work perfectly, but, on the newer builds of android (2.1's) the touch screen won't react most of the time. Like, I'll have to hit the screen over and over a few time's before it'll finally pick it up. I've used the calibration tool to get it all lined up, but when I go to test the calibration I notice that it will only recognize my touch between the .50's and .60's range, it's like it's locked into that area and won't pick up anything else. I also drew a circle around my screen about 10 times once I got it to recognize my pressure and out of the 10 circles 4 or 5 drew a line directly to the bottom right corner of the screen then it would bounce back to where I was actually pressing. It makes it really hard to get anything done on a touch phone if the screen doesn't want to pick up lol.
Like I say, when I move back to my original sprint rom everything is fine and dandy using WinMo 6.1 but who wants to use 6.1 now adays
So, is there any way to fix my touch sensitivity? or is my screen just crapping out on me?
Digitizer going bad
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Darkstarrdp said:
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Click to expand...
Click to collapse
I am not sure this can help, are you familiar with terminal?
open terminal or adb and type
Code:
cat /sys/module/tsc2003/parameters/sensitivity
to see current setting, it usually is 8192
write it down and change the param to lower value like 3072
Code:
echo "3072" > /sys/module/tsc2003/parameters/sensitivity
check the result
Code:
cat /sys/module/tsc2003/parameters/sensitivity
it should now display 3072
HTH
Can someone please tell me with Cognition running - what files I need to replace/edit to change the boot-up sound/image sequence as well as the same for shutdown.
Thanks!
EDIT: Please be very specific with your instructions as I have some Linux experience but not much - enough to get myself into trouble ;-p
Q - In need of an A
Bump
- I was able to change the power on sound. I was also able to change the 2nd set of boot images but not that damned At&t screen.
-Can anyone tell me how to do that & can anyone tell me how to get my power on sound to play for as long as the sound file is?
jhsperc said:
Bump
- I was able to change the power on sound. I was also able to change the 2nd set of boot images but not that damned At&t screen.
-Can anyone tell me how to do that & can anyone tell me how to get my power on sound to play for as long as the sound file is?
Click to expand...
Click to collapse
AT&T World Phone screen can't be changed, it's not part of the system area of the phone, it's actually ingrained MUCH deeper into the device- no one has found a method for removing it, and I know the brave souls on the I9000 boards have had some real legitimate bricks in the process of trying to figure it out.
As for the PowerOn.wav, I'd imagine it will only play for as long as it takes the phone to boot and no longer.
Thanks for the info.
On the Power On sound it plays like 6 seconds, then boot takes another 5-6 seconds but it cuts the sound off, which I have not been able to find a settings file for.
jhsperc said:
Thanks for the info.
On the Power On sound it plays like 6 seconds, then boot takes another 5-6 seconds but it cuts the sound off, which I have not been able to find a settings file for.
Click to expand...
Click to collapse
Hmm I haven't really played with it... there might just be a hard limit as to how long sound is available during boot- heck the system might wait x amount of seconds before proceeding. A lot of different things are initializing when the phone starts up, stands to reason that perhaps it reinitializes audio at a certain point before the OS starts
check here
http://forum.xda-developers.com/showthread.php?t=736412
First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)
Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.
To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.
I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.
Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state
I can't believe I'm the only one with this problem
lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?
I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.
unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.
Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.
Well, strange that only two or three of us noticed this strange problem.
Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...
I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.
Very screwy behavior on my Captivate. Hoping someone out there can help me diagnose this..
Captivate is running stock KK4; rooted via kernel swap method; some AT&T bloatware frozen in TiBu - no other image changes
The Captivate is struck on the swipe to unlock screen. I sync this phone to my company's Exchange server and have a PIN-lock policy enforced. I believe that it goes to the PIN at 15 minutes. The clock and swipe screen are showing a time less than 15 minutes after the last time I had used the phone; the screen was dark until I pressed power once, but now I can not make the screen go back to sleep. Plugging the phone into the computer does show the phone connected, and the Live Wallpaper is still running (i.e., it is not frozen in place, which I also see some times).
EDIT: After rebooting (vol-up and power does respond); it looks like something may have been up the same time as I was frozen with my phone signal - yellow instead of green; don't know if that was a coincidence or not
Any one have any ideas as to what may be going on here, and how I would remedy this?
Probably asking the obvious, but can you get into recovery or D/L mode to possibly reflash the rom?
jeeper11 said:
Probably asking the obvious, but can you get into recovery or D/L mode to possibly reflash the rom?
Click to expand...
Click to collapse
I can, and I can reboot, and have the phone work again for the next 24-36 hours before it freezes again.
I am hoping that someone has an idea of the root cause of this issue, bad flash or otherwise, to try to solve this once and for all. To be honest, I have had horrible experiences with GB on the Captivate, but since this is my work phone, paid for, and technically owned by my employer, I have been hesitant to stray too far from stock (heck, if AT&T's tethering manager could figure out that a corporate phone plan with tethering should be allowed to tether, I would have stayed fully stock).
I'm betting that it's bad behaved software, rather than a bad flash due to the unpredictable nature of this problem, but I am not sure of a way to capture logs in a consistent basis that would allow me to trap what actually goes wrong to solve this. GB seems to get progressively less stable the more apps are installed, but I don't know if that is the root cause, or just the increasing likelihood of installing something with an insidious bug. But short of stripping everything off and losing the advantage of having a phone with apps, I don't know how to solve this and the soft reboot issue that also came with the first GB leaks and never went away.
Sigh.
There could be just one rogue app causing it
After unlocking the bootloader on each boot a message shows up with the message, that the device ist unlocked and cant' be trusted anymore. ist there any way to make this message disappear? (relocking the bootloader is no way! )
Same question exists in the OnePlus 3 section (with no solution)
Link to OnePlus 3 thread --> http://forum.xda-developers.com/oneplus-3/help/request-remove-bootloader-unlocked-t3405485
As far as I know there is no way to change it
It has been happening from OnePlus 3 and there is no way to remove it
but how can this be fixed on other devices? I've reat about some moto devices, where this message was "fixed".
Yes maybe someone will be able to do in near future
rUmtifUsel said:
but how can this be fixed on other devices? I've reat about some moto devices, where this message was "fixed".
Click to expand...
Click to collapse
I've already put up pretty much the similar post for the 3t not only here but also in the oneplus forums (3t), where I was actually contacted by a oneplus person asking for some details. I've fixed this on pretty much every single android phones I've ever had until now but this is clearly a new quirkier way of doing the logo that doesn't follow any tradition.
I'm guessing that it's been looked at by non-Oneplus people (here, other places) about a million times without finding where that partition, file, ramdisk, lives, and will stay that way until someone has incredible luck or intuition about it, or .. a oneplus engineer decides to reply to me (or you) and tell us the answer. They obviously know since they stuck it there to begin with. I've kind of hit the point where I just ignore it , push the on button (speeds by the screen) and go about my business. The only positive thing I've noted is that over on the oneplus forums, once someone at oneplus notices your post, you often get results, or at least, that's your best shot.
Cheers.
Hi there,
well, my guess that this is part of the IPL (Initial program loader; not boot.img) since the message appears pretty early in the boot-chain. It would make sence since it also checks the LOCK-status and decides if it allows booting unsigned boot.img images (which include kernel and ramdisk). The logic might look something like
if (bootloader.isUnlocked()) {
showMessage();
bootUnsignedImage();
} else {
bootSignedImage();
}
rUmtifUsel said:
but how can this be fixed on other devices? I've reat about some moto devices, where this message was "fixed".
Click to expand...
Click to collapse
This is a standard on Nexus devices and isn't "fixed" on them. Doubt it's going to be different on this.
http://www.droidforums.net/threads/bootloader-unlocked-warning-cant-be-removed-on-nexus-6p.286627/
Pretty sure it's a standard in all new Android phones, and really doubt it will ever be removed.
gladiac said:
Hi there,
well, my guess that this is part of the IPL (Initial program loader; not boot.img) since the message appears pretty early in the boot-chain. It would make sence since it also checks the LOCK-status and decides if it allows booting unsigned boot.img images (which include kernel and ramdisk). The logic might look something like
if (bootloader.isUnlocked()) {
showMessage();
bootUnsignedImage();
} else {
bootSignedImage();
}
Click to expand...
Click to collapse
I think that's somewhere near the truth. I've got build-able source for the 3t (3.5.3) and just finished getting the prebuilts from the phone as well, so here goes a most-likely fruitless search for something resembling a clause that I can figure out where the actual screen is coming from. If I can string together a well enough constructed $find | $grep -i {whatever} | {as many other cmds as needed}, then when I get back from work today, I can find out (well, probably) nothing at all , but it's worth a shot since I don't have to watch it and wait.. ;
gladiac said:
Hi there,
well, my guess that this is part of the IPL (Initial program loader; not boot.img) since the message appears pretty early in the boot-chain. It would make sence since it also checks the LOCK-status and decides if it allows booting unsigned boot.img images (which include kernel and ramdisk). The logic might look something like
if (bootloader.isUnlocked()) {
showMessage();
bootUnsignedImage();
} else {
bootSignedImage();
}
Click to expand...
Click to collapse
I found this code in the file listed after the code:
Code:
#if FBCON_DISPLAY_MSG
display_bootverify_menu_thread(DISPLAY_MENU_ORANGE);
wait_for_users_action();
#else
dprintf(CRITICAL,
"Your device has been unlocked and can't be trusted.\nWait for 5 seconds before proceeding\n");
mdelay(5000);
#endif
}
#endif
Filename in build tree: ~/sandbox/oneplus3t/bootable/bootloader/lk/app/aboot/aboot.c
------------------
So:: There's quite a bit more text for that screen in that file, and it's not as simple as just replacing the entire file with a single line that (e.g.) sets a = 0;
The thing is that the file does a lot of checks and I suspect the boot process won't even get it's feet wet if the file is actually damaged, but ::
The code above could pretty easily just be slightly modified not to print a message or to print a nice message, or a pretty little graphic, and the delay has no reason to exist. As soon as I can get 3.5.3 to built without errors (I just downloaded it again since my first try was from a 3rd party git repo), I'll see if it can be tampered with. The real problem is "Is this worth screwing around with?" . How many people (and I'm not even one of them) would want to blow away their setups just to install a new OS that has this crazy change in it.
Anyway, now that I've found it, I'll see if I can find some better way to handle it, but many have fallen on this sword so I probably will follow in their footsteps.
edit: As I was staring at the filename, it dawned on me that it's where all the stock & custom recoveries are made and is the next tree over called bootloader. That "might" (really doubt it) make this more doable. If we only had to change one partition to get rid of this thing, it'd be more like flashing a logo partition to get rid of it. My guess is that they're way to smart to allow someone to slap a different bootloader in there without there being a price to pay. (like no longer booting because of dm-v*). We'll see.
If it ain't broke
don't fix it
obamadictator said:
If it ain't broke
don't fix it
Click to expand...
Click to collapse
What're you? An insurgent? lol. This is XDA, the home of breaking things that ain't broke. ;
OK, the way I see it is that this problem is pretty much the same everywhere. What differ is the type of message it convey. To me and maybe the initial poster as well is not that it have some sort of language saying it's unlock, but it also has 5-sec delay which is annoying. In my opinion, say a Nexus device which only show a picture of a padlock "unlocked" is a much nicer way to me. That said, that little padlock may not enough to tell a normal person looking at a phone and for them to know it's boot-loader unlocked and it could have "extra stuff" hiding in the system. Originally Nexus and OP device serve different market. OP were aim at the mass, the normal people, while Nexus served the dev. So if we start with that point, then it make more sense that the OP device bootloader unlocked message need to be more clear. Even though it's annoying, but it's a phone to me and I intend to have a stable ROMs on it and I don't have a need for it to reboot every day or many time a day on the normal usage. So, if I'm not going to see that majority of the time, I'm ok with that. If it need to be fixed, I think at least the language on the message could be better, and maybe tell us what is going to load after the 5-sec delay, eg: system or recovery.
To clear things up:
The security warning is displayed by what lives in the aboot partition. It is a part of the boot chain and the piece that loads the kernel. Each part of the boot chain verifies the next one using RSA certs and signatures, starting at the bootrom, which is read-only. Aboot is also responsible for fastboot, the splash screen, and everything else you see on your device which is not recovery or OS (except hsusb 9008 mode, which kicks in in case the cert chain described above fails). Whilst some part of it source code may be included in the OOS device tree all magic is left out. The partition itself contains an somewhat corrupted elf file you could analyze. (If you do, remove the two "NULL" and the "EDIDX" program header). Maybe some qfuse or toggled bit somewhere can remove the warning. If you are good at reverse-engineering low-level arm and know some quallcomm internal stuff, go ahead. Otherwise, please stop confusing things and repeating things that are wrong or irritating.
justibasa said:
This is a standard on Nexus devices and isn't "fixed" on them. Doubt it's going to be different on this.
http://www.droidforums.net/threads/bootloader-unlocked-warning-cant-be-removed-on-nexus-6p.286627/
Pretty sure it's a standard in all new Android phones, and really doubt it will ever be removed.
Click to expand...
Click to collapse
it's fixed on nexus 5x
https://forum.xda-developers.com/showthread.php?p=70567187
What's the variable "FBCON_DISPLAY_MSG" set to?
If the code is written in c (which from the looks of it; it is)
Couldn't you just set a global variable = to whatever the default value is? Or for example if something is changing that value when you unlock the bootloader, just set it back to default after that.
If it's in the aboot.c file, then it must be part of the boot.img right?
Also the boot.img file isn't the whole OS. As long as you don't tamper with the actual calling functions for the system it should be fine "theoretically". My OP3T should be coming in tomorrow, so maybe I can take a look at this as well when I have some time.
EDIT: I just read Jo_Jo_2000's response after what I wrote. That actually makes sense, and that's probably what makes this more difficult to do because you have to re-sign the files using valid certs, otherwise if it fails who knows what could happen since you're modifying the boot partition
any update on this issue?
As I understand the problem there really isn't a way to "fix" it that doesn't involve disabling more security. the dm-verity feature is built in and verifies that the boot process hasn't been tampered with. Once you unlock the bootloader, that isn't the case and dm-verity will always alert. Until you reflash a completely stock "factory" setup and re-lock it in that state. There could be some minor differences necessary to make this happen, but the gist of it should be correct.
I'm hoping against all odds that this isn't the case and that someone will eventually figure out how to re-enable dm-verity for a specific build... such as OOS_Beta + Magisk. But I'm pretty sure that's a futile hope. Google's been waging war on root for a while now and they're winning. Since they ultimately control the platform, it's my prediction that they're going to win.
This wouldn't bother me so much if I thought the ad networks were malware-free. I shouldn't have to expose my personal data or security for advertising. I don't care how passionately you argue on behalf of the content creators.
You really can't without someone customizing their own boot.img with that out. Even then you will see a black screen for a second before it advances to actually boot. Once the bootloader has been modified in any way, this trips and tells you basically you cannot use safetynet stuff. Its not a big deal, OnePlus 3t allows you to skip it pretty quick. Unlike my last phone i had to look at that screen for the entire 5 seconds it asked me too even if i asked it to boot immediately. Its just a warranty and security thing its not a big deal. Can be ignored just like the dm verity warning. Trust me, you dont have it as bad. I get both the bootloader and dm verity warning in the same boot. I do actually enjoy them though because they let you use the volume up and down option to go to fastboot or bootloader or recovery or just turn the thing off without needing to do the stupid button presses which i never remember which one does what. Theyre a nice blessing on this phone i must say. a few vol down clicks and im in twrp. Its nice.
In the oneplus 5 has been done!
https://forum.xda-developers.com/oneplus-5/themes/mod-bootloader-changer-t3800862