Database Users

Stuck on Samsung Custom Screen w/ Custom ROM

Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!

I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta

Flash a different kernel.
Period
your welcome

TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz

And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.

KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.

what procedures are you using for all of this? is there a specific guide you are following?

xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.

There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1

TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.

i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.

xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!

I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.

I am 1000000% sure of this.
are you really sure?
j/k, perfect.

TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.

jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.

Only one rom is able to reboot on my phone.

Hello, I have 10.1.3 CM on my phone right now. If I flash any other Roms like 10.2 CM, AT&T stock MF3, etc I'm having reboot problems. The initial first boot into the phone desktop is fine. However, I can never get into again. It always gets stuck on the Samsung boot screen. It's the image with Samsung and a unlocked lock. When I go into recovery, I have to wait a long time too. Sometimes I get the enter a password screen in TWRP. Once I get in, I have to format data and I can get to phone desktop again. However, when I reboot again, I get stuck and the cycle continues. The only thing that reboots for me with no issues is 10.1.3 CM.

Are you wiping data, system,dalvik, and cache before you flash?

mately tingbad
jd1639 said:
Are you wiping data, system,dalvik, and cache before you flash?
Click to expand...
Click to collapse
Yes. But as long as I go back to CM 10.1.3, it always works fine and no issues at all. It's only when I try any other rom I get stuck on the Samsung boot logo screen after a reboot.

genxseven said:
Yes. But as long as go back to CM 10.1.3, it always works fine and no issues at all. It's only when I try any other rom I get stuck on the Samsung boot logo screen after a reboot.
Click to expand...
Click to collapse
What recovery are you using? Is it the latest version?

jd1639 said:
What recovery are you using? Is it the latest version?
Click to expand...
Click to collapse
No, I'm using 2.6.0.0 twrp. Should I upgrade to the latest version? I think the latest is 2.6.3.1?

genxseven said:
No, I'm using 2.6.0.0 twrp. Should I upgrade to the latest version? I think the latest is 2.6.3.1?
Click to expand...
Click to collapse
Yes, that's the problem

jd1639 said:
Yes, that's the problem
Click to expand...
Click to collapse
Ok I will try that. Thank you for your fast responses.

Trying to Manually Downgrade from Android N Beta 3 to Marshmallow

I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!

asadabbas95 said:
I have been trying to go back to Marshmallow from the N beta 3 preview for a few days now, but it doesn't seem to be working any way I try. I originally tried to use the OTA method by unenrolling my device because that is the way I got the preview to begin with. Every time I tried that, though, it would end in an error after trying to install the update. So i tried flashing the Marshmallow images manually using fastboot. I flashed everything, including the bootloader, radio, recovery, boot, system, vendor, cache, and userdata, but when I tried rebooting, it would be stuck on the Google logo. Can someone please tell me if I am doing something wrong or can maybe help somehow? Thanks in advanced!
Click to expand...
Click to collapse
Not trying to say you're lying but are you sure you flashed everything? Are you using the flash all script or are you doing each image manually?
Mainly you need to flash boot, system, vendor, and userdata. Userdata just wipes that partition.
The N bootloader and radio should be compatible with the latest marshmallow release.
My best guess is if you used the flash all it didn't work, because it never works.
If not that then maybe you got a corrupted file? Try redownloading it and try again.
Sent from my Nexus 6P using Tapatalk

Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong

I am having the SAME EXACT issue. Found this on a search. Any solutions?

asadabbas95 said:
Nah I don't use the flash all script. I flashed everything manually and I didn't forget anything. I actually tried this twice and used a new file the second time so it's really weird. I have no idea what's wrong
Click to expand...
Click to collapse
Try this command first: "fastboot format userdata" - then flash all images, exept "userdata.img".

ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip

I'm.at work or else I would try that method can anyone try it and see what happens . I'm trying to go back to mm also
Sent from my Nexus 6P using Tapatalk

ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Sent from my Nexus 6P using Tapatalk

Okay so I'm not the only one who's having this problem. Did the sideloading method format the sd card?

havy15 said:
So you wiped everything and used that ? Can we just flash that or does it have to be side loaded I'm.on N it works but I don't wanna go back to MM cuz it's causing issues to others from what I heard I can keep the bootloader and radio but everything else you gotta flash would you lose root or have to re unlock the bootloader?
Click to expand...
Click to collapse
Download the file and rename it whatever you want. I changed it to update.zip.
Go to stock recovery and then select update from adb.
Then type ---> adb sideload "name of zip".
You will then be downgraded to stock MM with everything working.
Well at least that's what worked for me. Because I was on Android N Preview 3. It was too buggy so I tried to manually flash 6.0.1. but kept getting stuck on the white Google logo. The above method worked for me.

Are you rooted still? Someone told me if I'm going to pure rom all I need to do is wipe like normal like when you u flash a ROM and with gaps and I'll be fine with the vender image . Or do I have to do it your way . Did you go back to stock mm or a rom ?
Sent from my Nexus 6P using Tapatalk

ClassickWORLD said:
ADB Sidleoading this file worked for me https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
This didn't work for me either. I tried sideloading and it was sending the file, but it stopped at .02% and it gave me an error 7 and the download failed...This is really starting to annoy me because so many apps are really buggy for me on N

Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! ?? Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk

havy15 said:
Yeah Snapchat is super buggy and my phone stays crashing when it warms up lol . But I'm rooted unlocked bootloader Android N I'm trying to stay rooted unlocked bootloader and go back to MM how can I do that ?!?!?! Like I'm legit frustrated lol
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out

​
asadabbas95 said:
Lol trust me i know. I've been trying for so long and it's so frustrating that I can't do anything except wait for the official release to come out
Click to expand...
Click to collapse
are you trying to back to stock or another mm rom

havy15 said:
​
are you trying to back to stock or another mm rom
Click to expand...
Click to collapse
I tried both..neither worked

asadabbas95 said:
I tried both..neither worked
Click to expand...
Click to collapse
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid

havy15 said:
well i just read to go back to a mm rom you just have to wipe like when you flash a rom in general then go and flash rom gapps and vender and it should be solid
Click to expand...
Click to collapse
nah i tried that and was stuck on the google logo

asadabbas95 said:
nah i tried that and was stuck on the google logo
Click to expand...
Click to collapse
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?

havy15 said:
really thats what people are telling me to do and they say its working. you sure you are flashing the correct vender for that rom?
Click to expand...
Click to collapse
yup flashed everything correctly. Try flashing and tell me if it works for you

PLZ HELP!! Nexus 6p keeps booting into TWRP menu

Today and after deciding to simply restart my Nexus 6P, it booted into TWRP menu, I tried to reboot again, but no luck. can someone please help?
is there a way to get off the TWRP menu and boot my phone normally?
Note: The root used to simply work fine for about a month now.

Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.

Gytole said:
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Click to expand...
Click to collapse
Rooted my phone, and it was working fine for about a month, I done nothing unusual, All i did is restart my phone and it went to the TWRP menu, thats all. Im stuck there now.
I don't recall doing an update or whatever. Im using "BETA-SuperSU-v2.67-20160121175247.zip"

Any Idea how to get off the TWRP menu and boot my phone normally? Please help

MahmoudEMH said:
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
Click to expand...
Click to collapse
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?

Heisenberg said:
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Click to expand...
Click to collapse
Yes to each one of those questions.

MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
I will have to call you out here buddy. If you have indeed tried to flash all factory images, you won't even have TWRP in the first place.
Go to this wonderful guide by the wonderful @Heisenberg, and scroll down to "10. How To Flash The Factory Images (And Return To Stock)". You will find very clear instruction on how to return your phone to its factory stock state. This will most likely get rid of the problems you're facing.

MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
If you had flashed the full factory images I don't see how it's possible at all to be in your current situation. Explain how you flashed them, and exactly what you flashed please.

A20 (SM-A205F) Stuck in bootloop after flashing in twrp

Hi! am first time here
So I try to root my stock rom phone but I have a problem after I flash a Magisk.
Flashing file is complete but after I reboot it, It is stuck in boot animation for a long time, and then it reboot itself again.
Does anyone know how to fix it?

ah man , This is a sensitive situation, please note that you data is at risk , maybe the phone didn't recognize the custom recovery mode try re-installing TWRP again.

Soufy01 said:
ah man , This is a sensitive situation, please note that you data is at risk , maybe the phone didn't recognize the custom recovery mode try re-installing TWRP again.
Click to expand...
Click to collapse
I already know what caused it. It was caused the dual speaker mod.

merc547 said:
I already know what caused it. It was caused the dual speaker mod.
Click to expand...
Click to collapse
so how to fix it?

I had a similar issue, I fix it by reinstalling the stock ROM, with Odin.