Related
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4
Hello, My desperation level is at it's climax.
I got my hands on "Galaxy S4 Black Edition GT-I9050" I wanted to install kitkat firmware, i did everything as usual, i deleted the system folder on my S4, When i wanted to install the ROM, I found out that my phone was not reading the SD Card on Recovery Mode... Clockwork recovery mode. I formatted my SD Card in all formats, FAT,Etc. Still no hope, Than i wanted to restore to the original firmware by flashing the phone with odin, because my phone wont boot, it's stuck at the boot screen.
I downloaded countless firmwares, some of them Fail at MDM, and other fail right of the bat
Things that i have done:
Installed Samsung Drivers, uninstalled them.
Tried Different USB Hubs, Cables.
Tried many versions of Odin.
Nothing works.. I am really sad.
My Device: Galaxy S4 Black Edition
Model: GT-I9505
Problem, Unable to Flash Back/Phone stuck at boot screen
PS: I did research on how to restore stock firmware, etc, But nothing helps.
I really need your help! Cheers
I believe, and don't quote me on it, but that the black edition version of the s4 have slightly different firmware. Have you looked on sammobile for firmware specified for the black edition?
Sent from my GT-I9505 using XDA Free mobile app
What happens when you try to flash with a different recovery? Try Philz or TWRP.
But the Black Editions model number is i9506, no?
Lennyz1988 said:
What happens when you try to flash with a different recovery? Try Philz or TWRP.
Click to expand...
Click to collapse
Thanks for replying, I Downloaded both, Only philz is working fine, however I still don't see my external SD Card, Only internal one is there..
I found black edition firmwares, but as i am downloading one by one, nothing worked so far.
The firmware is located here : androidromupdate.com/2014/02/06/i9505xxuena4-4-3-firmware-samsung-galaxy-s4-gt-i9505-black-edition
Edit: I found specific Black edition firmware on sammobile, once i try them, i will post back here,
I tired flashing again but still no hope. What i am doing wrong? is it the firmwares? please help.
mangomhf said:
I tired flashing again but still no hope. What i am doing wrong? is it the firmwares? please help.
Click to expand...
Click to collapse
Did you try wiping data for the bootloop issue? :/
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
DeepankarS said:
Did you try wiping data for the bootloop issue? :/
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
Click to expand...
Click to collapse
Things that i did:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
When i turn on my phone, i see the boot and on the top left corner i see a msg which says;
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
Quick update, I finally managed to install Android 4.4 KITKAT Via SideLoad, It loaded fine, but now im facing another problem which is the Touch Screen is not working at all in the welcome menu. What could be the issue?
mangomhf said:
Quick update, I finally managed to install Android 4.4 KITKAT Via SideLoad, It loaded fine, but now im facing another problem which is the Touch Screen is not working at all in the welcome menu. What could be the issue?
Click to expand...
Click to collapse
Just do a factory reset in the recovery, but don't install the rom again.
mangomhf said:
Quick update, I finally managed to install Android 4.4 KITKAT Via SideLoad, It loaded fine, but now im facing another problem which is the Touch Screen is not working at all in the welcome menu. What could be the issue?
Click to expand...
Click to collapse
Told you. Data wipe!!!
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
having problems flashing a lollipop ROM. Ive never had any problems like these in the past, all other upgrades have gone smoothly
I am running into two problems. Either I will get stuck staring at a boot animation which never goes away, or I actually get through and all Google services go crazy and force close, with the google first time setup repeatedly trying to start and force closing itself so it is impossible to do anything on the phone.
The best I have done so far is flash a ROM without Gapps, but then for some reason I was not able to download any apks so there was no way to get the Play store on the phone.
If anyone could help me I'd appreciate it
brettzz said:
having problems flashing a lollipop ROM. Ive never had any problems like these in the past, all other upgrades have gone smoothly
I am running into two problems. Either I will get stuck staring at a boot animation which never goes away, or I actually get through and all Google services go crazy and force close, with the google first time setup repeatedly trying to start and force closing itself so it is impossible to do anything on the phone.
The best I have done so far is flash a ROM without Gapps, but then for some reason I was not able to download any apks so there was no way to get the Play store on the phone.
If anyone could help me I'd appreciate it
Click to expand...
Click to collapse
I was under exact same position. downloaded 2-3 lollipop rom, different size of gapps from diff sites same place.
solution is to flash factory image and everything works. now I am waiting for 5.1 OTA update and later try again few roms.
So best flash factory image as of now.
just as an update I tried a different kitkat rom and it went smoothly
not sure why lollipop is not working, one difference is when I reboot from recovery after flashing lollipop it tells me root may have been lost, and I get an option for 'yes, fix root' and it reboots.. when flashing kitkat didnt see that message it just rebooted
brettzz said:
just as an update I tried a different kitkat rom and it went smoothly
not sure why lollipop is not working, one difference is when I reboot from recovery after flashing lollipop it tells me root may have been lost, and I get an option for 'yes, fix root' and it reboots.. when flashing kitkat didnt see that message it just rebooted
Click to expand...
Click to collapse
What recovery and version are you using. You may have to update your recovery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What recovery and version are you using. You may have to update your recovery.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
hm looks like I was on a slightly outdated one I have updated and will see if this works now
brettzz said:
hm looks like I was on a slightly outdated one I have updated and will see if this works now
Click to expand...
Click to collapse
aha that did it
thank you very much!
Hi everyone,
Yesterday I flashed CF auto root to my Samsung S4 i9505 and it worked just fine. Then I tried to give root permissions to a launcher I like to use and the phone just rebooted and it's now stuck on the samsung animated logo. The led light is blue but it's not blinking or anything.
I've tried taking the battery off then going into recovery and wiping both data and cache, but I'm still stuck.. I'm using the stock 5.0.1 lollipop and I had never messed with the phone using Odin before. I only flashed CF auto root.
I'm thinking I should maybe flash a stock rom or something, but I just wanted to check if anyone knows what to do before I break it even more.
Any help is appreciated!
Flashing a stock ROM is not a bad idea. It will restore your phone to working condition, and then you can flash CF-Autoroot again. Potentially silly question here, but why did you need to give root permissions to a launcher?
Strephon Alkhalikoi said:
Flashing a stock ROM is not a bad idea. It will restore your phone to working condition, and then you can flash CF-Autoroot again. Potentially silly question here, but why did you need to give root permissions to a launcher?
Click to expand...
Click to collapse
It has some extra features only available with root. This is the launcher https://play.google.com/store/apps/details?id=com.amigo.navi&hl=en
I decided to try alternative roms and now I have MIUI7 5.10.16 installed, which I love, but the gapps are broken and so far I haven't found a workaround for it..
Anyway, thanks for the help! If I got MIUI7 to boot I'm pretty sure I could have flashed a stock ROM to get rid of that problem too.
I would be a little bit leery. Based on my experience, a launcher shouldn't need root access to do its job. Right now I'm running Nova on my S4 and it has never needed root to do anything.
Install a GApps package from OpenGApps and see if that helps resolve your Google apps problems.
Strephon Alkhalikoi said:
I would be a little bit leery. Based on my experience, a launcher shouldn't need root access to do its job. Right now I'm running Nova on my S4 and it has never needed root to do anything.
Install a GApps package from OpenGApps and see if that helps resolve your Google apps problems.
Click to expand...
Click to collapse
Funny you should mention OpenGApps, I'm actually trying that right now haha. Thanks again.
I installed the twrp app on my rooted samsung s7 edge, it downloaded and installed the image, now when rebooting all i have is a red screen? someone please help
thanks
nevermind all sorted now phew
stephenuk said:
nevermind all sorted now phew
Click to expand...
Click to collapse
How did you sort it out?
Flame_Beard said:
How did you sort it out?
Click to expand...
Click to collapse
Reinstall twtp agaim that worked for me
Sent from my SM-G935F using XDA-Developers mobile app
Flame_Beard said:
How did you sort it out?
Click to expand...
Click to collapse
Used an older version through odin
This ended up being sorted for me, as it just booted after about a half hour. But how, if you hit this red screen can you reflash? You aren't getting to dowload mode or recovery with that perma-red screen
lol, I spoke too soon again, was reflashing twrp after going back to a stock rom, this happened again for me only its not budging from red screen now. I can't get into download mode as I mentioned above too
hey guys I have the same
the phone dont even switch off
how did you fix it?
edit SOLUTION : I managed to reboot the phone with adb
add reboot
then I flashed the version 3.0.0.0 of TWRP and it worked !
Help!
stephenuk said:
I installed the twrp app on my rooted samsung s7 edge, it downloaded and installed the image, now when rebooting all i have is a red screen? someone please help
thanks
Click to expand...
Click to collapse
I rooted my phone, had twrp recovery successfully. then i tried to install xposed and it was probably the wrong version. tried to use odin to get the stock rom, but the screen is only red, and i can hear the volume sounds... any help?
sammobile.com/firmwares/database/SM-G935F/TEN/ i used the newest version
adrianbjorvatn said:
I rooted my phone, had twrp recovery successfully. then i tried to install xposed and it was probably the wrong version. tried to use odin to get the stock rom, but the screen is only red, and i can hear the volume sounds... any help?
sammobile.com/firmwares/database/SM-G935F/TEN/ i used the newest version
Click to expand...
Click to collapse
I am having the same problem. Odin is stuck in "Setup Connection"
Do you have any ideas?
Thanks
You have probably flashed a wrong kernel.
The solution is to flash the right kernel for your device.
I was flashing S7 root on S7Edge
Flame_Beard said:
How did you sort it out?
Click to expand...
Click to collapse
i just used an earlier version
julien32 said:
how did you fix it?
edit SOLUTION : I managed to reboot the phone with adb
add reboot
then I flashed the version 3.0.0.0 of TWRP and it worked !
Click to expand...
Click to collapse
Thank you very much, worked for me!:good:
i tryed the posted solutions, but won´t work for me.
I found a another version an flash it, so that the red sceen is gone, but this was the wrong version.. so i tried to flash the right twrp image, but odin freezes everytime...
what can i try?
Hi Guys,
I flashed everything stock after having some issues with encrypton and a custom ROM.
After flashing twrp-3.1.1-0-herolte.img with Odin 3.17 I only get a red screen when booting into recovery and the phone won't even boot the OS.
Any idea how to get TWRP working so I can get back to a custom ROM?
Thanks,
Nicolas
Edit: Hero2lte worked
flashed ****ty rom /** THE GALAXY PROJECT **/ with twrp + themes and hard bricked my phone
my usb doesnt work, just for charging, i was told something gone on my mobo of s7 edge.
i can boot into download mode but nothing to do without pc...
Nikouy said:
Hi Guys,
I flashed everything stock after having some issues with encrypton and a custom ROM.
After flashing twrp-3.1.1-0-herolte.img with Odin 3.17 I only get a red screen when booting into recovery and the phone won't even boot the OS.
Any idea how to get TWRP working so I can get back to a custom ROM?
Thanks,
Nicolas
Edit: Hero2lte worked
Click to expand...
Click to collapse
you are a live saver!!i love you!!!
juda iskariotsky said:
flashed ****ty rom /** THE GALAXY PROJECT **/ with twrp + themes and hard bricked my phone
my usb doesnt work, just for charging, i was told something gone on my mobo of s7 edge.
i can boot into download mode but nothing to do without pc...
Click to expand...
Click to collapse
Lol. I have the very same problem: Flashed The Galaxy Project ROM and hit "update bootloader etc...." and now all I have is this red screen..... - Though the ROM worked for a couple of hours, but when I tried to enter the recovery I stock with this red screen. Cant even go into download mode...
Any help? How did you solved this issue?
I didn't, ****ty Rom just bricked it.
Just reflash the recovery or flash stock. I can't, my pc doesn't recognize my s7 anymore.
He doesn't even bother to mention that bug...
NandorHUN said:
Lol. I have the very same problem: Flashed The Galaxy Project ROM and hit "update bootloader etc...." and now all I have is this red screen..... - Though the ROM worked for a couple of hours, but when I tried to enter the recovery I stock with this red screen. Cant even go into download mode...
Any help? How did you solved this issue?
Click to expand...
Click to collapse
Same here. Only in my case I use this ROOM for weeks