Related
Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69
Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !
I also don´t like the screen... the opportunity to hide would be great.
here's the same, maybe someone can make a xposed module?
kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
any luck on the nag screen yet? maybe gone in the july update? =D lol
I get this message Everytime, any ideas? Help would be great
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.
How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it
..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."
I am posting hoping some progress may or may not have been made on this. Its atrocious.
So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
TheKnux said:
So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
Click to expand...
Click to collapse
I tried it, but it just hangs while trying to load resources. I think I'm just unlucky lol
I installed it but got a boot loop. I could only start the phone by flashing latest oos without magisk but even after uninstalling live boot, magisk still kept the liveboot00001 file or whatever so I had to remove it manually in twrp in /data/adb/magisk/ (somewhere around there.. ) Just in case someone else has this problem..
No problem here, using it since 4 weeks, several OOS updates never had an issue
TheKnux said:
Looks amazing on the OP6T.
Click to expand...
Click to collapse
It sure does! Thanks for the share. Works great on beta 2, even though I have the McLaren Magisk mod running (which replaces boot animation with McLaren's).
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Ironic said:
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Click to expand...
Click to collapse
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
TheKnux said:
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
Click to expand...
Click to collapse
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
tech_head said:
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
Click to expand...
Click to collapse
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
TheKnux said:
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
Click to expand...
Click to collapse
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
tech_head said:
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
Click to expand...
Click to collapse
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
TheKnux said:
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
Click to expand...
Click to collapse
I didn't change it. No real incentive right now.
This app was my old favorite and I miss it, I hope it still works as I havnt tried... Just wanted you all to know this is the best app ever and the scrolling text (if your developing) is actually SUPER helpful... I remember I would use the filter to find specific debug lines only and it was so usefull... I only installed it because Im a huge nerd so it was an extra awesomeness to have it be super usefull!
2023 BEST APP EVER!#[email protected]#
Anyone knows when is beta 5 is coming out. I tried beta 4 but had too much problems with it
Rumor has it that today it will launch since its usually the first Wednesday of the month but last Wed was right before the 4th. If not today, Perhaps August?
Gotta be soon with all the online chatter already about what it contains.
Sent from my Pixel 2 XL using XDA Labs
Just can't wait some good stuff coming along with it
According to the Android program overview, the releases of Beta 5 & 6 are scheduled in July! so it's inevitable that b 5 will be released this week...
Beta 5 is out
https://developer.android.com/preview/download
https://www.xda-developers.com/android-q-beta-5-rolling-out/
Downloading currently!
Yeah, I just got it and my phone is now quite screwed. Boot loops for a while, then drops me into recovery with "Cannot load Android system. Your data may be corrupt." I get the option to try again (which eventually just dumps me back into recovery) or "Factory data reset". Ugh.
Edit: and the factory reset does appear to "work" though of course now I have a load of work to do to get things back the way they were. Oddly, the phone now thinks it has a different phone number. This is going to be fun. Also get fun things like "Settings keeps stopping". Yeah, this isn't going to be a good day.
epithumia said:
Yeah, I just got it and my phone is now quite screwed. Boot loops for a while, then drops me into recovery with "Cannot load Android system. Your data may be corrupt." I get the option to try again (which eventually just dumps me back into recovery) or "Factory data reset". Ugh.
Edit: and the factory reset does appear to "work" though of course now I have a load of work to do to get things back the way they were. Oddly, the phone now thinks it has a different phone number. This is going to be fun. Also get fun things like "Settings keeps stopping". Yeah, this isn't going to be a good day.
Click to expand...
Click to collapse
Ugh, had this issue with QB4. Might wait a little bit. Thanks for letting us know!
Okay i have updated it but what the hell is new ?
Pixel 2 XL on Beta Q 5. Gmail & Docs will not go dark even with override force dark on. Anyone else have the same issue?
And...the OTA was pulled:
https://www.androidpolice.com/2019/07/10/get-your-pixels-ready-android-q-beta-5-is-landing-today/
"According to Google's official reddit account,*Q Beta 5 has been pulled*for all devices. No specific reason has been given aside from being "related to installing updates," and there's no ETA for its return either. We will keep you posted when we get more information."
Sent from my Pixel 2 XL using Tapatalk
Taking the update right now, I guess it is back?
I'm updating now. So I guess the update is back on.
Titanium backup doesn't open at all on Android q is this just me??
prot- said:
Titanium backup doesn't open at all on Android q is this just me??
Click to expand...
Click to collapse
Reboot.
Droid_Nut said:
Reboot.
Click to expand...
Click to collapse
I have many times
prot- said:
I have many times
Click to expand...
Click to collapse
Fixed by enabling untrusted sources with magisk
prot- said:
Fixed by enabling untrusted sources with magisk
Click to expand...
Click to collapse
How is that done?
Droid_Nut said:
How is that done?
Click to expand...
Click to collapse
Sorry "install unknown apps" in Android settings. And tick magisk in that list
Anyone get Viper4Android to work on rooted QB5? Mine keeps asking for driver.
ask in the thread, i am sure its not supported yet,
and probably waiting twrp and other stuff to be worked out on final release
Daisymae said:
Anyone get Viper4Android to work on rooted QB5? Mine keeps asking for driver.
Click to expand...
Click to collapse
It is. Not the module though, 2.7.1 works. It'll ask for a driver then reboot, but you'll have to do this a few times before it takes. I cancelled after my second time, went to settings and changed to compatibility mode, then it worked for me. Not sure if that had anything to do with it or I just hit the magic reboot number. You might try that first.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
gettinwicked said:
It is. Not the module though, 2.7.1 works. It'll ask for a driver then reboot, but you'll have to do this a few times before it takes. I cancelled after my second time, went to settings and changed to compatibility mode, then it worked for me. Not sure if that had anything to do with it or I just hit the magic reboot number. You might try that first.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Click to expand...
Click to collapse
Thanks! Just had to do it a few times then it finally worked!
Sent from my [device_name] using XDA-Developers Legacy app
Can u give me a rooted boor img?
i peached by magisk(19307)...but failed every time after flash boot...
If you have the magisk peached boot.img for pixel3 xl
Send a link to me plzzzzzzz
Thank you soooooo much
Opened Magisk, said there was an update....upon reboot I am Corrupted and froze basically.....now to try and figure out recovery
On A12, Kiriaskura kernal, very few magisk modules...
cmh714 said:
Opened Magisk, said there was an update....upon reboot I am Corrupted and froze basically.....now to try and figure out recovery
On A12, Kiriaskura kernal, very few magisk modules...
Click to expand...
Click to collapse
Magisk support thread
No issue on my Pixel 5, stock kernel, only SafetyNet/systemless host modules.
atm I am struggling to get the device into Recovery mode...wont power down...
cmh714 said:
atm I am struggling to get the device into Recovery mode...wont power down...
Click to expand...
Click to collapse
Hold the power and volume up buttons together for over 30 seconds, maybe longer, and it should force it to power down.
Then if you haven't already, Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Good luck, let us know how you did. I had no trouble updating although at the moment I happen to be on the stock kernel - I don't plan on remaining stock and have previously updated at least one custom kernel.
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
cmh714 said:
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
Click to expand...
Click to collapse
CleanSlate worked well for me when I've been using a custom kernel. I know Kiriaskura is based on CleanSlate, but there are differences.
Glad you got it fixed.
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
roirraW edor ehT said:
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
Click to expand...
Click to collapse
But that's no fun
But seriously, that is probably wise. I've stayed on Canary to make it easier if Google decides to play with us again like they did in December with their load fstab shenanigans and of course earlier with their vbmeta shenanigans. Those were fixed quickly in Canary but took a while to make it to Stable. But with that comes the cons, of course, as evidence by today. But Stable is good advice.
On a side note, I never received the corrupted message like others did when updating Magisk while on Kirisakura today. However, I still have verity and verification disabled. Hmmm.... makes you wonder
"Mama always told me not to look into the eyes of the sun, but mama
That's where the fun is"
Lughnasadh said:
On a side note, I never received the corrupted message like others did when updating Magisk while on Kirisakura today. However, I still have verity and verification disabled. Hmmm.... makes you wonder
Click to expand...
Click to collapse
Sounds likely for what kept you safe to me.
Lughnasadh said:
"Mama always told me not to look into the eyes of the sun, but mama
That's where the fun is"
Click to expand...
Click to collapse
Mama, life had just begun
But now I've gone and thrown it all away
Oh sorry, mine's the wrong mama.
roirraW edor ehT said:
@cmh714 I was looking at the Kiriaskura thread's last page of posts and someone mentioned Magisk Canary. Is that what you were on? For what it's worth, maybe you have some specific reason to still be on Canary, but once the Android 12-compatible Stable release came out, I switched over to Stable too, and I recommend doing the same. Just a suggestion, though.
Click to expand...
Click to collapse
I might give that a try later, already wasted too much energy on fixing myself but yes, still on Canary
roirraW edor ehT said:
Sounds likely for what kept you safe to me.
Mama, life had just begun
But now I've gone and thrown it all away
Oh sorry, mine's the wrong mama.
Click to expand...
Click to collapse
Mama Queen meets Mama Manfred Mann's Earth Band... I love it!
cmh714 said:
Thnks Man, already fixed.....Kiriaskura is the problem....gonna leave the kernel alone for now
Click to expand...
Click to collapse
Same happened to me, but can't get rid of corrupt system at boot...
I'm in the same boat, tomorrow I'm going to fully wipe and see if it go's away. That's the only thing I've seen that gets rid of that warning.
GIKE said:
Same happened to me, but can't get rid of corrupt system at boot...
Click to expand...
Click to collapse
Same here atm....will see if this months update (once it arrives) fixes things.....dont want to wipe but boy the message is a PITA!
I have the weird problem of no longer being able to modify the services.jar since the Magisk update.... I remove the navbar by modifying it. I can't change the size either. Weird that a Magisk update would hinder that.
GIKE said:
Same happened to me, but can't get rid of corrupt system at boot...
Click to expand...
Click to collapse
Blade22222 said:
I'm in the same boat, tomorrow I'm going to fully wipe and see if it go's away. That's the only thing I've seen that gets rid of that warning.
Click to expand...
Click to collapse
cmh714 said:
Same here atm....will see if this months update (once it arrives) fixes things.....dont want to wipe but boy the message is a PITA!
Click to expand...
Click to collapse
Flash an old (I did Feb .003 one.) boot.img, boot, then reboot and flash the current patched boot.img. Should get rid of it.
(don't forget direct install in magisk manager afterwards)
I tried with the newest boot.img, but it didnt work.
Sek0n said:
Flash an old (I did Feb .003 one.) boot.img, boot, then reboot and flash the current patched boot.img. Should get rid of it.
(don't forget direct install in magisk manager afterwards)
I tried with the newest boot.img, but it didnt work.
Click to expand...
Click to collapse
that worked for me, thanks!
Tulsadiver said:
I have the weird problem of no longer being able to modify the services.jar since the Magisk update.... I remove the navbar by modifying it. I can't change the size either. Weird that a Magisk update would hinder that.
Click to expand...
Click to collapse
sounds like something might be wonky with that new canary.
Freak07 said:
sounds like something might be wonky with that new canary.
Click to expand...
Click to collapse
Even more weird, I tried going back to an earlier version and the problem persisted. Bootloop. It doesn't bootloop until I unlock my phone though.
Tried to Fastboot flash boot boot.img with the mid-Feb release. I am still getting "Your device is corrupt". Going to "flash-nowipe"
Edit: While running flash-nowipe, got the same "device is corrupt" message. Thankfully when I hit resume the device went into fastbootd and is getting the image. Still getting device corrupt, but device booted and apps are still intack.
Rolled back Magisk to 24.3.10 with Kiris kernel 1.8.4. Everything is working fine, but still get the corrupt device message. Requires an extra "resume" when rebooting.
Hopefully tomorrow we will get the March release and an updated Magisk which make the problem go away. Hoping!