I can't seem to get rid of the samsung custom icon on boot. I read another thread that claimed it was caused by an error when rooting and to odin back to stock and try again. I have done this and I still get the custom icon. It's weird because on some roms I get it and on others I don't. Any ideas?
i'm confused...
you are rooted running a custom rom, right?
a.demarco said:
i'm confused...
you are rooted running a custom rom, right?
Click to expand...
Click to collapse
Yes, I had cleanrom and got the normal boot icon, but just flashed hyperdrive and the samsung custom is there.
When your on stock but rooted and unlocked you'll get that. If you install a custom kernel you can remove it.
Sent from my SCH-I545 using xda app-developers app
theycallmerayj said:
Yes, I had cleanrom and got the normal boot icon, but just flashed hyperdrive and the samsung custom is there.
Click to expand...
Click to collapse
ah, ok. you can change that if you want with a custom kernel, but why does it matter? you aren't gonna get rid of your phone in that condition, and if you had to back to vzw or asurion you can just flash back to stock unrooted and download triangle away.
a.demarco said:
ah, ok. you can change that if you want with a custom kernel, but why does it matter? you aren't gonna get rid of your phone in that condition, and if you had to back to vzw or asurion you can just flash back to stock unrooted and download triangle away.
Click to expand...
Click to collapse
.
I know it just annoys me I guess lol. I'll try a custom kernel and see if it goes away.
I had the same problem, I guess the kernel that you flashed caused the "Custom" logo. Well I just flashed stock MDK, then rooted the phone back.
michaely123 said:
I had the same problem, I guess the kernel that you flashed caused the "Custom" logo. Well I just flashed stock MDK, then rooted the phone back.
Click to expand...
Click to collapse
Flashing custom kernels doesn't fix it. I had clean rom and faux kernel and didn't have it and now I have hyperdrive and faux and it's there. I guess ill just deal with it.
theycallmerayj said:
Flashing custom kernels doesn't fix it. I had clean rom and faux kernel and didn't have it and now I have hyperdrive and faux and it's there. I guess ill just deal with it.
Click to expand...
Click to collapse
I haven't tried hyperdrive or faux yet, but you could always try to reroot.
Did anybody find a sure solution to this?
A custom kernel isn't the answer afaik. I used to boot Samsung everytime, even with a custom rom. However, it had since changed to custom for whatever reason the other day and I can't get it back. Used every kernel out, even flashed back to stock/stock with no luck.
Odin mode shows binary as Samsung Official status, and I don't see a flash counter. ...
Proweedsmoker said:
Did anybody find a sure solution to this?
A custom kernel isn't the answer afaik. I used to boot Samsung everytime, even with a custom rom. However, it had since changed to custom for whatever reason the other day and I can't get it back. Used every kernel out, even flashed back to stock/stock with no luck.
Odin mode shows binary as Samsung Official status, and I don't see a flash counter. ...
Click to expand...
Click to collapse
Basically what happens to me. There is no rhyme or reason as to why it comes up custom
I saw somewhere else it is because of using a custom recovery. I was rooted for a day before installing TWRP then noticed the "custom"
Nope. I have a custom recovery TWRP and I don't have the "Custom" screen on boot.
drt054 said:
I saw somewhere else it is because of using a custom recovery. I was rooted for a day before installing TWRP then noticed the "custom"
Click to expand...
Click to collapse
Yeah, the "Samsung custom" didn't hit me til days after flashing a a ROM and kernel. I was trying to boot into recovery from powered off, and accidentally booted into Odin. Then when I rebooted again, it had the Samsung Custom splash screen.... I miss my Galaxy S4 splash screen. Looked so much nicer. But I'm not going to revert all the way back to stock just to get it back.
Sent from my SCH-I545 using Tapatalk 4 Beta
Oh cool. I flashed Hyperdrive 7, and ktoones TW kernel, and gave triangle away another go and it worked.
Sent from my SCH-I545 using Tapatalk 4 Beta
I'm running Darkslide rom with elite kernel and I want to get the custom splash screen gone and back to the samsung s4 splash screen. Triangle away stated not to proceed if I'm not running stock rom or stock recovery or run the risk of soft bricking and bootloops. Has anyone disregarded the warnings and proceeded successfully?
Rooted S4
Yep. It worked. It did not work on AOSP based ROMs though. I don't know why.
Edit: and also the custom unlocked icon will just show up at random. Run triangle away again and it'll be fine. I usually freeze triangle away after running because for some reason every three minutes it'll show up "triangle away has been granted superuser permissions"
Sent from my SCH-I545 using Tapatalk 4
If on mdk. Flash the mdk Odin package and boot into an "official" statused tw ROM like stock or synergy. Then reboot and flash whatever you want.
I hold the stock splash screen on AOSP based roms until through testing I end up flashing a bad kernel. Then I have to reOdin mdk kernel again to get it back.
sent from my Verizon Galaxy sIV
Related
i installed twrp as my custom recovery now when booting phone i get a black screen saying samsung and custom under it is that normal ...
thank you
Very normal.
I think that's just Samsung's way of saying that one of the system partitions has been overwritten regardless of the status of the bootloader. It goes back to normal if you flash a stock recovery or reflash stock via Odin, I presume.
cryogenic666 said:
I think that's just Samsung's way of saying that one of the system partitions has been overwritten regardless of the status of the bootloader. It goes back to normal if you flash a stock recovery or reflash stock via Odin, I presume.
Click to expand...
Click to collapse
You don't have to reflash stock, just remove all superusers and reboot. You still stay rooted, but you won't be able to get root permission you will need to install it again to gain permission for whatever app needs root gain.
Javiggan
Javiggan69 said:
You don't have to reflash stock, just remove all superusers and reboot. You still stay rooted, but you won't be able to get root permission you will need to install it again to gain permission for whatever app needs root gain.
Javiggan
Click to expand...
Click to collapse
Actually, I didn't get the lock icon and "custom" text until after I installed a new recovery and kernel. Rooting doesn't bring that up from what I've seen.
cryogenic666 said:
Actually, I didn't get the lock icon and "custom" text until after I installed a new recovery and kernel. Rooting doesn't bring that up from what I've seen.
Click to expand...
Click to collapse
I have twrp and don't get the custom screen. I am on the stock rooted software tho.
Sent from my SCH-I545 using xda app-developers app
Schoat333 said:
I have twrp and don't get the custom screen. I am on the stock rooted software tho.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Then I guess it's the custom kernel that did it? I'm running Faux's kernel . Earlier I was running that kernel on rooted stock and saw that screen. I've since flashed CleanROM and faux's kernel and I'm getting it still. I didn't get it when I was just rooted running CWM recovery, I don't believe.
cryogenic666 said:
Then I guess it's the custom kernel that did it? I'm running Faux's kernel . Earlier I was running that kernel on rooted stock and saw that screen. I've since flashed CleanROM and faux's kernel and I'm getting it still. I didn't get it when I was just rooted running CWM recovery, I don't believe.
Click to expand...
Click to collapse
Most likely the kernal, ROM or both.
When I rooted using this method, I got the "custom" boot screen while on the MD2 kernel. After restoring the MDK kernel and a couple reboots it went away. Then installed CWM recovery using this method and got the same "custom" boot screen, but it went away after a couple reboots as well.
cryogenic666 said:
Then I guess it's the custom kernel that did it? I'm running Faux's kernel . Earlier I was running that kernel on rooted stock and saw that screen. I've since flashed CleanROM and faux's kernel and I'm getting it still. I didn't get it when I was just rooted running CWM recovery, I don't believe.
Click to expand...
Click to collapse
+1
camaroz28 said:
Most likely the kernal, ROM or both.
When I rooted using this method, I got the "custom" boot screen while on the MD2 kernel. After restoring the MDK kernel and a couple reboots it went away. Then installed CWM recovery using this method and got the same "custom" boot screen, but it went away after a couple reboots as well.
Click to expand...
Click to collapse
I don't recall whether I got the "custom" screen after flashing the pre-release kernel. But I think it's a combination of recovery + boot partition being replaced. That being said, it's not a huge issue because if I ever had to send it in for service, I'd just Odin it anyway.
Its the ROM itself. I'm rooted w/TWRP/fauxU on stock ROM and still boots official.
When I tried a custom ROM, that's when i got custom every boot. Also, using "on boot" settings will trigger the custom logo.
Just from my experience.
Hello,
After installed hyperdrive my galaxy s4 is now stuck with this weird boot screen. It sais samsung on it then shows a unlocked lock and said custom by it. How do i get the stock screen back. i have tried unrooting and flashing a stock MDK image in odin and stilll have that screen. IS there anyway to get the stock screen back?
clapper66 said:
Hello,
After installed hyperdrive my galaxy s4 is now stuck with this weird boot screen. It sais samsung on it then shows a unlocked lock and said custom by it. How do i get the stock screen back. i have tried unrooting and flashing a stock MDK image in odin and stilll have that screen. IS there anyway to get the stock screen back?
Click to expand...
Click to collapse
That's Samsung's way of telling you that they know that you're running non-standard software. Don't worry about it.
You can remove it by installing a stock ROM whenever you like, but you'll lose all of your data in the process.
Well that's the ring l thing I totally wiped and unrooted with a stock mdk image I flashed using odin and is did not go away
Sent from my SCH-I545 using xda app-developers app
clapper66 said:
Well that's the ring l thing I totally wiped and unrooted with a stock mdk image I flashed using odin and is did not go away
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
You need to flash a full-wipe factory restore - signed by the factory. No changes, hacks, or modifications.
Factory reset won't do it.
If you're starting from rooted on MDK, run Triangle Away to clear the flag. Then flash a clean MDK image. You'll lose root but also have no "Custom" flag. If you DO get a custom flag after this, that's because you're not flashing a factory-signed stock image.
I soft bricked my phone. I can get back to TWRP, and any ROM seems to take but none will boot. All stuck on the Samsung Custom (open lock) screen.
I think i formatted too much and now need to go back to MDK.
Any suggestions for the speediest solution?
My thoughts are odin MDK and then root and flash TWRP?
orateam said:
I soft bricked my phone. I can get back to TWRP, and any ROM seems to take but none will boot. All stuck on the Samsung Custom (open lock) screen.
I think i formatted too much and now need to go back to MDK.
Any suggestions for the speediest solution?
My thoughts are odin MDK and then root and flash TWRP?
Click to expand...
Click to collapse
Odin is probably only choice
powered by hashcode safestrap hyperdrive 10.2
decaturbob said:
Odin is probably only choice
powered by hashcode safestrap hyperdrive 10.2
Click to expand...
Click to collapse
I did it. Luckily i was able to odin back to an MDK ROM, re-root and recovery. All is well. I always thought you couldn't go back to MDK, but i guess you could. Does that mean anyone on a ROM today can go back to MDK?
orateam said:
I did it. Luckily i was able to odin back to an MDK ROM, re-root and recovery. All is well. I always thought you couldn't go back to MDK, but i guess you could. Does that mean anyone on a ROM today can go back to MDK?
Click to expand...
Click to collapse
The reason you could go back to MDK, because you were on MDK build. People won't be able to odin back to MDK after they take OTA update.
urcboss07 said:
The reason you could go back to MDK, because you were on MDK build. People won't be able to odin back to MDK after they take OTA update.
Click to expand...
Click to collapse
i wasn't on the MDK build. I had already moved to a custom rom of ME7 and was on hyperdrive 4.3 when i did the ODIN. Is it because i wasn't bootlocked?
orateam said:
i wasn't on the MDK build. I had already moved to a custom rom of ME7 and was on hyperdrive 4.3 when i did the ODIN. Is it because i wasn't bootlocked?
Click to expand...
Click to collapse
Flashing a custom ROM doesn't change your original baseband. If you didn't take any official OTA's then you were still on MDK. Also, there's no such thing as an unlocked bootloader for the S4's.
Sent from my NCC 1701 Using Tapatalk 4
riker147 said:
Flashing a custom ROM doesn't change your original baseband. If you didn't take any official OTA's then you were still on MDK. Also, there's no such thing as an unlocked bootloader for the S4's.
Sent from my NCC 1701 Using Tapatalk 4
Click to expand...
Click to collapse
Your right. I just checked my baseband on my current ROM (recently released hyperdrive r11) and it's MDK.
So does the baseband have any affect on my usage?
ugh i installed this and i cant get past the Samsung logo either... which file should i download to odin??? not what i wanted to deal w/ right before bed.. hopefully the process doesn't take too long.
Powell730 said:
ugh i installed this and i cant get past the Samsung logo either... which file should i download to odin??? not what i wanted to deal w/ right before bed.. hopefully the process doesn't take too long.
Click to expand...
Click to collapse
Boot into the factory recovery and do a wipe/factory restore.
didnt realize this was possible if we're on a custom recovery. i thought factory recovery was erased once you install a custom one?
Powell730 said:
didnt realize this was possible if we're on a custom recovery. i thought factory recovery was erased once you install a custom one?
Click to expand...
Click to collapse
You will wipe the custom recovery when you odin. After that just boot into recovery and select wipe/factory reset.
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
KBizzle said:
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
lacoursiere18 said:
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
Click to expand...
Click to collapse
Thank you. It's been a while.
Sent from my SCH-I605 using Tapatalk
Alright, got one more question. So I thought I had bricked my phone last night. Accidentally flashed an S4 stock rom. I know, dumb. Anyway, after 3 hours of trying to Odin multiple stock roms, I finally got one to take and the phone booted. So I immediately went and used casual to root the device. Everything went fine there. I went ahead and updated TWRP to the latest and proceeded to flash aokp. It locked up at the boot animation. So I then tried to flash a 4.1.2 tw rom. This is where it got weird. It flashed fine but then it never booted. Just a black screen after the Samsung splash screen. I then decided to try and Odin a rooted 4.1.3 rom. Still nothing. So last ditch effort I odin'd the pit file. Back in business on an unrooted tw rom. Now when I try to use casual, it won't download the proper driver to root again. Gives a perpetual error and requests the driver be installed over and over until I pull the USB cable. Is there something I'm missing?
Sent from my SCH-I605 using Tapatalk
Try this. With the phone booted, go into device manager on your computer and uninstall the driver. Then boot the phone into download mode and uninstall the driver for it in device manager. Boot phone back up and try casual again. Also make sure your Antivirus is off before you run casual.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Snake2k said:
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Click to expand...
Click to collapse
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
es0tericcha0s said:
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Click to expand...
Click to collapse
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
ikuni123 said:
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Snake2k said:
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2634408
According to that, only 13 is supported. I dunno if the that thread hasn't been updated or whatever, but something to consider.