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.
Related
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
This is embarrassing but I think I might have just bricked my phone. I'm hoping that there is a work around. Please let me know if you need more info to possibly help me.
I was running:
1. SIM Unlocked/Rooted T-Mobile Amaze 4G with 1.43.531.3 Radio
2. BulletProof 2.41 Rom
3. Faux123 Kernal v.0.0.8 [Jan 22]
4. Have Clockwork Recovery Installed
I've been dealing with constant reboots since I bought the phone new. I saw that someone posted in the Energy Rom thread that when they installed his Rom that the reboots went away. So I decided to try his.
I then:
1. Grabbed the Stock Kernal Flasher and tried to flash back to the stock kernal using Xboarders Easy Flasher. Everything seemed to go fine.
2. Phone rebooted and Its just stuck at the HTC Logo.
Any options for me? I did try to restore from my last ROM backup using CWM (which I figured was futile) but that didn't change anything.
Thanks for your help on this. I love this phone but I just couldn't keep dealing with the constant reboots. Now I'm really hosed
Reflash the kernel again...maybe it didn't write everything.
Sent by accident from my Amaze using Tapatalk
Double0EK said:
Reflash the kernel again...maybe it didn't write everything.
Sent by accident from my Amaze using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply,
I used Windows to flash the phone's kernal. It won't recognize the device since its stuck at the logo.
If there is a way to flash the kernal in Recovery (I'm still S-On with unlocked bootloader) please let me know and I'll try it that way..
Stephen
dnslammers said:
Thanks for the reply,
I used Windows to flash the phone's kernal. It won't recognize the device since its stuck at the logo.
If there is a way to flash the kernal in Recovery (I'm still S-On with unlocked bootloader) please let me know and I'll try it that way..
Stephen
Click to expand...
Click to collapse
i think the problem is using the stock kernel.
take out the battery, use the vol down+power buttons to boot into hboot, then boot into fastboot, flash the kernel appropriate to the rom your using, dont just use stock, and then reflash your rom. always remember to do a full wipe
alx294 said:
i think the problem is using the stock kernel.
take out the battery, use the vol down+power buttons to boot into hboot, then boot into fastboot, flash the kernel appropriate to the rom your using, dont just use stock, and then reflash your rom. always remember to do a full wipe
Click to expand...
Click to collapse
Thanks for your suggestion. Before I saw your reply, I decided to flash the Energy Rom since it had the Stock kernal built into it. I fortunately already had the rom on my SD card so I went into Recovery and flash that rom.
FORTUNATELY, the phone rebooted successfully after rom flash to the new rom. My phone is still using Faux123's kernal so the Energy rom didn't flash the stock kernal after all. But my phone is working again!!!
Thanks for everyone's help. I guess I'll just leave the Faux123 kernal on it and be satisfied with that with the Energy rom. Hopefully the constant reboots will go away.
Stephen
dnslammers said:
My phone is still using Faux123's kernal so the Energy rom didn't flash the stock kernal after all.
Click to expand...
Click to collapse
Thanks to S-ON the kernel will not flash when you flash a rom. You have to flash the kernel separately using the kernel flash utility.
I'm running the Energy rom using the stock kernel from his thread and am loving it. Battery life is great. I've heard that battery life is not so good with faux.
No worries needed... glad you figured it out. The good news though about having S=on is that it's virtually impossible to brick. I'm pretty sure I've read posts from members saying good luck trying to brick it.
I'm sure if you edit the right code in the build.prop, you might be able to brick it, but even then you should still be able to boot into recovery.
Sent from my HTC_Amaze_4G using xda premium
tried installing latest version of cyanogen using clock work recovery, froze at white htc menu. now rebooting using my recovery i backed up and its still loading files after 1 hour. if i ever get my phone working again what rom or method on installing rom should i use, i always used clockwork on my other phones with no prob.
Alpinestars96 said:
tried installing latest version of cyanogen using clock work recovery, froze at white htc menu. now rebooting using my recovery i backed up and its still loading files after 1 hour. if i ever get my phone working again what rom or method on installing rom should i use, i always used clockwork on my other phones with no prob.
Click to expand...
Click to collapse
Are you S-Off or S-On?
Ps. I'm not a fan of CWM. I've used TWRP mostly, and I love it, although a lot of people still swear by Amon Ra
do yourself a HUGE favor and just flash Amon RA 3.15....TWRP has come a long long way but by far the most reliable recovery is amon, hopefully that solves your issues
How do I flash using aromna? Also where do I get it?
Alpinestars96 said:
How do I flash using aromna? Also where do I get it?
Click to expand...
Click to collapse
check the link:▼▼▼
http://www.droidforums.net/forum/ht...05839-guide-unlocking-rooting-roming-faq.html
also the latest version of Amon Ra can be found here: ▼▼▼ remember to unzip the file before flashing
http://forum.xda-developers.com/showpost.php?p=23890117&postcount=523
Curious:
What ROM are you trying to flash. Some ROMs have custom kernels, and if you are S-on they will not be able to flash from recovery. You will need to flash them from fastboot/hboot. That would cause the ROM not to boot properly if you did not have the right kernel.
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
So I wasn't thinking when I first got my s4 and figured the update was just something small but now that I look on here it looks like that update was definitely something big... What does this mean for me? Can I not run custom roms or kernels now?
That is correct. Currently you can root but you cannot install a custom recovery. Without a custom recovery you cannot install different roms or kernels. You cannot odin back to MDK. Hashcode is fine tuning a workaround using Safestrap, but it is not available yet. You can follow his progress here
http://forum.xda-developers.com/showthread.php?p=45185924
jaxon01 said:
That is correct. Currently you can root but you cannot install a custom recovery. Without a custom recovery you cannot install different roms or kernels. You cannot odin back to MDK. Hashcode is fine tuning a workaround using Safestrap, but it is not available yet. You can follow his progress here
http://forum.xda-developers.com/showthread.php?p=45185924
Click to expand...
Click to collapse
Okay thanks for the info. I used safestrap and it seemed to work well on my droid razr do you know the difference between using safestrap and using normal recovery, I'm just curious.
fatmando2 said:
Okay thanks for the info. I used safestrap and it seemed to work well on my droid razr do you know the difference between using safestrap and using normal recovery, I'm just curious.
Click to expand...
Click to collapse
custom recovery replaces your normal recovery, allowing you to overwrite the whole system when flashing a rom
safestrap keeps the stock software, and boots a recovery on top of it, keeping the stock software while kind-of dual booting your own ROM.
Or at least i think this is how it works in a layman's term.
JaeKay said:
custom recovery replaces your normal recovery, allowing you to overwrite the whole system when flashing a rom
safestrap keeps the stock software, and boots a recovery on top of it, keeping the stock software while kind-of dual booting your own ROM.
Or at least i think this is how it works in a layman's term.
Click to expand...
Click to collapse
Ok, are there reasons why one is better then the other or are they just different methods of doing the same type of thing?
fatmando2 said:
Ok, are there reasons why one is better then the other or are they just different methods of doing the same type of thing?
Click to expand...
Click to collapse
safestrap wont ever really brick your phone, but you got double the storage for system files