Develop Bugs

Need help, cant get into bootloader in kingsrom

Okay, so im running kingsrom unleashed 4g, and its great i love it. Tired to flash another rom today, elite III. Preformed backup, flashed format_all zip first then was gonna flash elite III next like it states. But now after flashing format_all zip it restarted the phone and now its back to kingrom and its in safe mood. For some odd reason its not letting me load into bootloader so i can flash the next step. And whats really ticking me off is that rommanager is not working. Ive installed and uninstalled countless times and it wont let me open. Does it have to due with being in safe mood. Please help me , need someone to fill me in. Thanks for you time.

I'm confused in regard to your post. Anyway, to get to the bootloader, power off your device. Now simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text will scroll across the screen and then you'll be shown a set of options. Viola, you're at the bootloader screen.
posting & replying via the XDA Premium app.

dougjamal said:
I'm confused in regard to your post. Anyway, to get to the bootloader, power off your device. Now simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text will scroll across the screen and then you'll be shown a set of options. Viola, you're at the bootloader screen.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thats what ive been trying to do for the last hour, i know how to get there. The problem here is that it wont load up, it just starts up once i let go of the power button.

I feel like a broken record: STOP USING ****ING ROM MANAGER!!!!!!!!!!!!!!!!!!!!!!!!!!!
Flash your **** in ****ing RECOVERY like it was designed for.....
10,000 posts about problem flashing ROMS on here, and 9,990 of them were because someone was using ROM manager
Now, I KNOW people are going post that ROM Manager works fine for them, well great! Welcome to the minority.....

HipKat said:
I feel like a broken record: STOP USING ****ING ROM MANAGER!!!!!!!!!!!!!!!!!!!!!!!!!!!
Flash your **** in ****ing RECOVERY like it was designed for.....
10,000 posts about problem flashing ROMS on here, and 9,990 of them were because someone was using ROM manager
Click to expand...
Click to collapse
Take a breather. And I feel like the problem is from him not disabling the function in applications/development that enables the 'fast' reboot.

teh roxxorz said:
Take a breather. And I feel like the problem is from him not disabling the function in applications/development that enables the 'fast' reboot.
Click to expand...
Click to collapse
Possibly.....
Still, I'm gonna start a revolution against ROM Manager and Kernel Manger...
Useless programs for people trying to shortcut a proven system...

HipKat said:
I feel like a broken record: STOP USING ****ING ROM MANAGER!!!!!!!!!!!!!!!!!!!!!!!!!!!
Flash your **** in ****ing RECOVERY like it was designed for.....
10,000 posts about problem flashing ROMS on here, and 9,990 of them were because someone was using ROM manager
Now, I KNOW people are going post that ROM Manager works fine for them, well great! Welcome to the minority.....
Click to expand...
Click to collapse
okay..., looks like i learned the hard way, time to get up and learn from my mistakes. But do you know how i get out of this pickle?

When you do vol-down/power, you don't get to bootloader? What does your phone do?

HipKat said:
When you do vol-down/power, you don't get to bootloader? What does your phone do?
Click to expand...
Click to collapse
Nothing at all. Then after mmm 45 seconds of holding it down i let go, it boots up, quickly too. Im not sure if its because of Kingsrom or what ( on the fast boot that is).

What about fastboot? (Vol up/Power)?
I'm no expert here, but I think you may want to try running the RUU form your PC if that doesn't work, go back to stock and start over. I'm sure someone will come up wit ha better option, but if it was me, that's what I would do.

conman123 said:
Nothing at all. Then after mmm 45 seconds of holding it down i let go, it boots up, quickly too. Im not sure if its because of Kingsrom or what ( on the fast boot that is).
Click to expand...
Click to collapse
You need to go into the settings and disable that 'fast reboot' setting.

teh roxxorz said:
You need to go into the settings and disable that 'fast reboot' setting.
Click to expand...
Click to collapse
Oh yeah, I already forgot about that......

HipKat said:
Oh yeah, I already forgot about that......
Click to expand...
Click to collapse
Its okay to forget things when leading a rebellion.

teh roxxorz said:
You need to go into the settings and disable that 'fast reboot' setting.
Click to expand...
Click to collapse
Thanks so much, it started right up in bootloader.

HipKat said:
Oh yeah, I already forgot about that......
Click to expand...
Click to collapse
Im never using rommanager again i suppose, thanks for the heads up though.

conman123 said:
Thanks so much, it started right up in bootloader.
Click to expand...
Click to collapse
Never a problem. And you can still use rom manager to fix permissions, if you get a whole bunch of force closes on apps for no reason.

teh roxxorz said:
Never a problem. And you can still use rom manager to fix permissions, if you get a whole bunch of force closes on apps for no reason.
Click to expand...
Click to collapse
Okay cool, when i did a google search on safe mode it seemed to me like i was about to have a pretty paper weight.. haha

teh roxxorz said:
Its okay to forget things when leading a rebellion.
Click to expand...
Click to collapse
Lmao.........
Swyped From The Hippest Phone Using XDA Premium

teh roxxorz said:
Never a problem. And you can still use rom manager to fix permissions, if you get a whole bunch of force closes on apps for no reason.
Click to expand...
Click to collapse
Remind me to add that to my Revolt thread that it is awesome for fixing permissions
Swyped From The Hippest Phone Using XDA Premium

conman123 said:
Okay cool, when i did a google search on safe mode it seemed to me like i was about to have a pretty paper weight.. haha
Click to expand...
Click to collapse
Lawlz, no paper weights while I'm around.

Latest T-Mobile Update Slowed Down My Phone

Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?

cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.

reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r

cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.

Thank you.
It's sadly still doing it.

cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.

Factory Reset

Unlocked Bootloader Message

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.

Root

Hello XDA,i tried to root my galaxy S9(Exynos) and i think i f***ed up.
I used a site i fount and seemed ok and now after all i done my phone behaves slow,restarts itself,on short,i dont know exactly what i did wrong,but i know i did wrong,and i want to fix it.
i want a detailed answer,as for dummies,cause i never got into such an complicate root process.
Thanks.
EDIT:Using TWRP i formated data and now the phone looks like its back to normal(stock) if someone can help me root it i will be extremly happy

I never trust anything other than XDA, i'm looking for a way to root too..

Jens956 said:
I never trust anything other than XDA, i'm looking for a way to root too..
Click to expand...
Click to collapse
managed to make root work but a problem appeared:unable to use samsung account,unable to use any other type of lock screen type except swipe,andafter i instaled youtube vanced using magisk repozitory the phone entered again in the lock screen loop.i think its something about the kernel i used(elementalX 2.08) or the no verity version using 1.0.
I will look trough the forum for other versions and i will try to flash them.i will also try to flash a new rom,maybe thats the problem.

DrTrap said:
managed to make root work but a problem appeared:unable to use samsung account,unable to use any other type of lock screen type except swipe,andafter i instaled youtube vanced using magisk repozitory the phone entered again in the lock screen loop.i think its something about the kernel i used(elementalX 2.08) or the no verity version using 1.0.
I will look trough the forum for other versions and i will try to flash them.i will also try to flash a new rom,maybe thats the problem.
Click to expand...
Click to collapse
The ROM is probably the problem for you. Because now knox is tripped for you many samsung and other services dont work anymore for you on pure vanilla stock. If you like oneUI maybe try out a few roms, they are better than stock. There is also a growing AOSP ROM community, there is a group on telegram you should check out.

Haxomen said:
The ROM is probably the problem for you. Because now knox is tripped for you many samsung and other services dont work anymore for you on pure vanilla stock. If you like oneUI maybe try out a few roms, they are better than stock. There is also a growing AOSP ROM community, there is a group on telegram you should check out.
Click to expand...
Click to collapse
Flashing TGP Kernel and magis again worked to get out of the loop,but the services still dont work(samsung,google works just fine).
Can you give me a good and stable up to date ROM for the exynos s9?and some instructions on how to install it?

Every ROM i try to install results in a boot loop, and now my phone FROZE on the boot logo i cant even turn it off! Help!

Jens956 said:
Every ROM i try to install results in a boot loop, and now my phone FROZE on the boot logo i cant even turn it off! Help!
Click to expand...
Click to collapse
WOW!Thats bad.Have you tried the power+power down combo for shutting it down?a thing i can suggest better is to let it drain completly,and try to boot it in twrp,do a wipe and then try again.

DrTrap said:
WOW!Thats bad.Have you tried the power+power down combo for shutting it down?a thing i can suggest better is to let it drain completly,and try to boot it in twrp,do a wipe and then try again.
Click to expand...
Click to collapse
Yeah.. the only thing that worked is by rooting samsungs stock rom with TGPKernel but now the entire phone crashes every 2 days

Jens956 said:
Yeah.. the only thing that worked is by rooting samsungs stock rom with TGPKernel but now the entire phone crashes every 2 days
Click to expand...
Click to collapse
none of the issues detailed in this thread make any sense. If a g965f is bootlooping after an attempt at rooting it, whatever was done in that attempt obviously failed and nothing in this thread really explains why, which mostly seems to be due to the lack of info from the OP and who all has participated thus far. We have no idea what baseband the OP is on, what version of TWRP they used, what version of Odin. We are lucky to know its a 965f so far...
---------- Post added at 08:06 AM ---------- Previous post was at 08:01 AM ----------
Jens956 said:
I never trust anything other than XDA, i'm looking for a way to root too..
Click to expand...
Click to collapse
a great deal of the devs that make the android community great all hang out here and share their contributions first on here, but you will find that certain phones on this site get far more attention than others, and the S9 area is a sad sad shell of what xda used to be. The reason im replying to your post at all is because xda is not the only place one can go to get good info on phones, but it is a reasonable place to put your trust if youre unfamiliar with the myriad of other sites specifically devoted to android and the users that avoid XDA for one reason or another. Try talking about any pay services on here or anything to do with "software of the illegitimate variety"

Question todays Magisk Update corrupted me....

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!