My GS4 ATT keeps getting stuck on the Samsung Custom screen after rebooting my rom.
The initial reboot after doing a clean install works fine, but after restarting, it gets stuck.
I have tried 3 different roms so far and all have the same problem, any suggestions?
other information:
model#: sgh-1337
version 4.3
baseband:1337UCUAMDL
kernal:3.4.0-g4fe9989-dirty
what recovery
what roms did you try
by clean, i assume you wiped system also
i don't pay attn to kernel names. is that part of the rom you last flashed or did you get it elsewhere and if so exactly how did you flash it
rugmankc said:
what recovery
what roms did you try
by clean, i assume you wiped system also
i don't pay attn to kernel names. is that part of the rom you last flashed or did you get it elsewhere and if so exactly how did you flash it
Click to expand...
Click to collapse
I tried hyperdrive rls14 3 times and lquidsmooth, shostock, all have the same problem.
I flashed it through TWRP like normal, wipe, install, wipe chache ...
i might have to go back to stock via odin, but im currently running a mac.
is that kernel stock for one of the roms, if not flash rom with it's stock kernel
which twrp, 2.5.0.2 is best
rugmankc said:
is that kernel stock for one of the roms, if not flash rom with it's stock kernel
which twrp, 2.5.0.2 is best
Click to expand...
Click to collapse
its the stock kernals with the roms, im not sure which version of twrp I have because then I wont be able to boot into into rom.
ok, so you can't boot into recovery?
have you ever flashed and ran a rom successfully, which one?
if so, what has changed if anything to be a possible cause
rugmankc said:
ok, so you can't boot into recovery?
have you ever flashed and ran a rom successfully, which one?
if so, what has changed if anything to be a possible cause
Click to expand...
Click to collapse
No i can boot into recover, i cant boot into the rom after restarting (after installing the rom it will boot, but after restarting it gets stuck on boot)
I have ran many roms in the past, i flashed over stock root. I am not sure what to, and dont want to restore it completely unless its a must.
baseband is your radio, what's your Build number, if you know
i think on a mac you will need to use heimdal, this guy Ashton may be able to help if you go that route
http://forum.xda-developers.com/showthread.php?t=1917237
i just was confused. if you can't get to recovery, how did you flash 3 roms and have same issue?
rugmankc said:
baseband is your radio, what's your Build number, if you know
i think on a mac you will need to use heimdal, this guy Ashton may be able to help if you go that route
http://forum.xda-developers.com/showthread.php?t=1917237
i just was confused. if you can't get to recovery, how did you flash 3 roms and have same issue?
Click to expand...
Click to collapse
I dont think you completely understand my situation. So everything works fine, except when I restart my phone after flashing a new rom, it will get stuck on the samsung boot logo. this happens to every rom I have tried.
Bump.
gsr101 said:
Bump.
Click to expand...
Click to collapse
You do know that the first boot after flashing a rom is going to take longer than normal. I think that's what you're experiencing
jd1639 said:
You do know that the first boot after flashing a rom is going to take longer than normal. I think that's what you're experiencing
Click to expand...
Click to collapse
it boots perfectly after flashing the rom, but after i get into the rom and install stuff and then I reboot causes the phone to get stuck on the logo.
I noticed that there is something wrong with the root permissions.
gsr101 said:
it boots perfectly after flashing the rom, but after i get into the rom and install stuff and then I reboot causes the phone to get stuck on the logo.
I noticed that there is something wrong with the root permissions.
Click to expand...
Click to collapse
Try flashing super su in recovery again
jd1639 said:
Try flashing super su in recovery again
Click to expand...
Click to collapse
I have, it works but wont boot into the os unless i wipe and install the rom again
gsr101 said:
I have, it works but wont boot into the os unless i wipe and install the rom again
Click to expand...
Click to collapse
What recovery are you using?
also, i don't remember you saying what your build is, just the baseband.
these things uaually happen if you are flashing a rom not meant for your phone or an incompatible kernel
rugmankc said:
also, i don't remember you saying what your build is, just the baseband.
these things uaually happen if you are flashing a rom not meant for your phone or an incompatible kernel
Click to expand...
Click to collapse
oh, thanks for the help. I really want to run Hyperdrive RLS14 on it, so should I goto stock then update and root?
well, would like to know your build not baseband
ie, mdl, mf3, mk2
otherwise back to stock thru heimdall, since you are on mac, may be path, never used it but there is info on it thru google searches
also, if possible backing up important info on internal card and reformatting may be another option
rugmankc said:
well, would like to know your build not baseband
ie, mdl, mf3, mk2
otherwise back to stock thru heimdall, since you are on mac, may be path, never used it but there is info on it thru google searches
also, if possible backing up important info on internal card and reformatting may be another option
Click to expand...
Click to collapse
My BASEBAND says MDL, My BUILD says RLS13.
gsr101 said:
My BASEBAND says MDL, My BUILD says RLS13.
Click to expand...
Click to collapse
Still think it's an issue with your recovery. Google twrp 2.5.0.2 zip xda and flash that in your current recovery. Then flash your rom and see if you still have the problem
Related
I am in need of some help.
I recently installed a 4.3 rom Kangabean and the install went fine. However on first reboot, I got a yellow triangle warning me that the software was not authorized by att has been found on your phone.
Holding down power and volume down then get me the custom icon
So I am able to boot back the phone but cannot get into recovery.
The phone is MDL and the rom is supposed to be loki'd
How do I get rid of this crap and be able to reboot into recovery.
I'd Odin back to stock and start over.
yeah i think thats what I am going to do
man this is so weird.
Returned to stock. Rooted then went to install twrp. At reboot, bam custom icon. I cannot get into twrp at all
what the heck am I doing wrong?????
Suzook1 said:
man this is so weird.
Returned to stock. Rooted then went to install twrp. At reboot, bam custom icon. I cannot get into twrp at all
what the heck am I doing wrong?????
Click to expand...
Click to collapse
I was going to say this earlier, flash the correct kernel, you are flashing the wrong one...
Thanks you
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is the one I am flashing. How is that wrong?????
Suzook1 said:
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is the one I am flashing. How is that wrong?????
Click to expand...
Click to collapse
that is NOT a kernel, you must use a loki kernel...
TheAxman said:
that is NOT a kernel, you must use a loki kernel...
Click to expand...
Click to collapse
He can't get into recovery. The tar looks correct for Odin.
yes correct I cannot get into recovery. I flashed back to stock. Rooted then did goo manager and as soon as I rebooted into recovery I got the custom icon and it loads stock recovery..... WERIDNESS
ok update. After installing recovery like 5 times through goo it FINALLY boots to twrp
my question is this though, why after just reinstalling the stock firmware, rooting and then installing twrp is is showing a custom rom icon at start up????
Suzook1 said:
ok update. After installing recovery like 5 times through goo it FINALLY boots to twrp
my question is this though, why after just reinstalling the stock firmware, rooting and then installing twrp is is showing a custom rom icon at start up????
Click to expand...
Click to collapse
Post #2 should help getting rid of the custom icon. http://forum.xda-developers.com/showthread.php?p=42320414
thank you for the link. I will chalk that one up as mystery !!!!
I have an ATT i337 S4 (mdl baseband) running on T-mobile. Current setup was wicked 7.0 ROM with ATT kernel.
I was trying to change to cyanogenmod ROM and tried using my TWRP 2.5.0.2 to load the rom but it would flash it and gave me an md5 error. Supposedly this is a known issue with TWRP so most people recommend using clockworkmod recovery and I tried to load that using recovery tools. Recovery tools couldn't find the CWM image file but did find the 2.6.3.0 updated TWRP image file so I tried to update TWRP and when I did, I can't boot to recovery anymore and instead get the yellow triangle saying unauthorized software.
At the same time (ugh) I flashed wicked 8 ROM update and think I loki'd it (I am running wicked 8.0 now) but I forgot to run the att kernel afterward. The current kernel is 3.4.5 ... dirty ptmr3 ... N5110 #1. I think this is the standard t-mobile kernel which will obviously not work on my ATT phone.
The problem is, now I can't reboot into recovery mode. When I try, I get the yellow triangle "system software not authorized by ATT...". I don't know if the problem is with the bad kernel or with the updated 2.6.3 TWRP. The only way I can get around the bootloader problem is the hold down the down vol and home button, then the power button and that gets me into a "Warning a custom OS can cause critical problems ..." page. From there if I continue, I get the yellow triangle. If I hit the volume down button to cancel, it boots normally but not into the bootloader and I have partial functionality of my phone.
Where do I go from here? Odin to stock? Replace the bootloader somehow? Anything else?
I did do a nandroid of my system before all of this but for some reason I can't access my SD card. I can hit mount but nothing shows up on file manager. Will that backup replace the bootloader with the known good one? I could copy the backup to the phone memory and do it from there using titanium backup I think.
Thanks,
odin back to stock and then wipe/clear then retry should fix this problem
lilg754367 said:
odin back to stock and then wipe/clear then retry should fix this problem
Click to expand...
Click to collapse
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
colorchange said:
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
Click to expand...
Click to collapse
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
colorchange said:
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
Click to expand...
Click to collapse
I'm guessing I might be able to modify the open boot script and change to the old version but I don't know how to do this.
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
lilg754367 said:
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
Click to expand...
Click to collapse
Thanks lil, i know the kernel I want and have it downloaded. Right now I am downloading the tar file to get me back to stock. I was hoping to do something easier but crud...
yea no problem just hit the thanks button for me good luck
I can't get Odin to talk to my device. When it is not in download mode, Odin sees it but hangs and can't communicate. When I connect it in debug mode (very hard to get into download mode), Odin can't see it.
Help!
Tried to install CWM from rom manager 6.0.4.6 but i had 6.0.4.7.
This cus i have problem installing CM updates directly by pressing restart and install.
Efter this i was in a boot loop an could not access CWM only the DL mode. So i installed CWM from the original source i did the first time and then the boot was ok all the way but then tried PWR VOL+ HOME but then i gut in to the boot loop again untli i reinstalled the CWM tried once more but same result.
So now i have CWM installed and i can boot up but i cant access CWM to make backup or restore the previus one.
Any ideas of what could be wrong?
Wrong section
Sent from my SM-N900T using Tapatalk
6.0.4.7 is for KK bootloader. If you haven't that's why
go back to 4.6
I have kitkat cm11
maybe thats why it does not work now?
With one should i have? Link to dl pls.
Sorry if posting wrong could someone move it please?
spyvingen said:
I have kitkat cm11
maybe thats why it does not work now?
With one should i have? Link to dl pls.
Sorry if posting wrong could someone move it please?
Click to expand...
Click to collapse
its your bootloader thats still 4.3, cm kitkat works on the old bootloader .... just go and download a older version of cwm
ratcom said:
its your bootloader thats still 4.3, cm kitkat works on the old bootloader .... just go and download a older version of cwm
Click to expand...
Click to collapse
I upgraded to samsung stock kikat before and its non reversible as i got it does that matter?
to be frank, I never try to flash anything from ROM manager.
This tools I've left it very very long time ago.
Have you tried to reflash the KK stock firmware, since you said you are on KK already (to get your stock recovery first), make sure everything is ok. Then reflash the CWM through ODIN. Don't use ROM manager.
antique_sonic said:
to be frank, I never try to flash anything from ROM manager.
This tools I've left it very very long time ago.
Have you tried to reflash the KK stock firmware, since you said you are on KK already (to get your stock recovery first), make sure everything is ok. Then reflash the CWM through ODIN. Don't use ROM manager.
Click to expand...
Click to collapse
Could try that. The problem is i cant make a backup now when i dont have access to CWM
But if it is the only way sure i will try it.
I'm going to flash the new ROM over my 4.4.2 S4 LTE. After flashing this new ROM, what are the necessary steps I should do to get my phone rooted?
Which are the compatible flashing/rooting programs to use for this new ROM?
greeny2010 said:
I'm going to flash the new ROM over my 4.4.2 S4 LTE. After flashing this new ROM, what are the necessary steps I should do to get my phone rooted?
Which are the compatible flashing/rooting programs to use for this new ROM?
Click to expand...
Click to collapse
You're talking about official 5.0.1?
GDReaper said:
You're talking about official 5.0.1?
Click to expand...
Click to collapse
Yes. That's the ROM I'm talking about. I've just flashed Philipz recovery using Odin and everything looking fine. However, I still get the default recovery and not the PhilipZ version.
Is the 5.0.1 not ready for the present recover like Chainfire or Philipz?
greeny2010 said:
Yes. That's the ROM I'm talking about. I've just flashed Philipz recovery using Odin and everything looking fine. However, I still get the default recovery and not the PhilipZ version.
Is the 5.0.1 not ready for the present recover like Chainfire or Philipz?
Click to expand...
Click to collapse
I had problems flashing recovery on stock kitkat. Used a workaround with Nandroid manager from play. But you need root for that..
Maybe try a different recovery. I don't see why PhilZ would be the only one to work with the 5.0 rooting method presented somewhere around the forum.
A recovery has nothing to do with the version of the rom you have flashed.
Uncheck auto-reboot before flashing the rom with Odin.
Lennyz1988 said:
A recovery has nothing to do with the version of the rom you have flashed.
Uncheck auto-reboot before flashing the rom with Odin.
Click to expand...
Click to collapse
Will give this a try.
Update - No go with what you have described. Stuck at the end of Odin flashing. Have to pull out the battery. Luckily, phone still can boot but with the default recovery.
I have a verizon s5 type kltevzw kernal 3.4.0-4782027 boot loader g900vvru1b0c4 andriod 5.0 build # g900vvru2b0g5
i am rooted and installed busy box and safestrap 3.75 .
everything installed just fine . when i reboot the phone it never goes into safe strap..
has anyone else come across this?
how can i fix it?
thanks in advance
mark
jtskir222 said:
I have a verizon s5 type kltevzw kernal 3.4.0-4782027 boot loader g900vvru1b0c4 andriod 5.0 build # g900vvru2b0g5
i am rooted and installed busy box and safestrap 3.75 .
everything installed just fine . when i reboot the phone it never goes into safe strap..
has anyone else come across this?
how can i fix it?
thanks in advance
mark
Click to expand...
Click to collapse
you have to flash an ni2 kernel first i suggest just downloading the application for it just search ni2 kernel flasher apk
That's all I have to do?
I don't have to flash stock kernel before I get out if safe strap?
splash screen
Veid71 said:
you have to flash an ni2 kernel first i suggest just downloading the application for it just search ni2 kernel flasher apk
Click to expand...
Click to collapse
I appreciate the help. I just want to make sure i do it correct the first time.
I had someone tell me " You need to flash the NI2 kernel first, then reboot. This should get you into SS. Look for NI2flasher.apk
You will also need to flash your build kernel (OG5) BEFORE you exit SS."
Is this the correct way or just flash like you said ..?
thanks again
jtskir222 said:
I appreciate the help. I just want to make sure i do it correct the first time.
I had someone tell me " You need to flash the NI2 kernel first, then reboot. This should get you into SS. Look for NI2flasher.apk
You will also need to flash your build kernel (OG5) BEFORE you exit SS."
Is this the correct way or just flash like you said ..?
thanks again
Click to expand...
Click to collapse
Yup
Veid71 said:
Yup
Click to expand...
Click to collapse
yup your way ? or the way with the stock kernel ?
thanks
jtskir222 said:
yup your way ? or the way with the stock kernel ?
thanks
Click to expand...
Click to collapse
I mean they're the same way mine is just the first part but the stock kernel one
Here's what you do flash the NI2 kernel either by the app or in download mode with Odin or using flashfire then it should restart and you click the recovery button and it goes into safestrap then you flash what you want And flash the og5 kernel and restart
Veid71 said:
I mean they're the same way mine is just the first part but the stock kernel one
Here's what you do flash the NI2 kernel either by the app or in download mode with Odin or using flashfire then it should restart and you click the recovery button and it goes into safestrap then you flash what you want And flash the og5 kernel and restart
Click to expand...
Click to collapse
thanks for the reply
you bring up one more question
1 flash ni2
2 you say flash what i want? will i lose the stock rom?
3 flash the og5 kernel
sorry for being a PIA.
mark
jtskir222 said:
thanks for the reply
you bring up one more question
1 flash ni2
2 you say flash what i want? will i lose the stock rom?
3 flash the og5 kernel
sorry for being a PIA.
mark
Click to expand...
Click to collapse
Yes you flash NI2 then you do whatever you wanted to do in safestrap usually I flash Roms and stuff that's why I said that but you don't have to then when you're done you flash the OG5 kernel to be able to use the phone again and yeah if you flash a different ROM you'll lose the stock ROM but you can always just flash it back if you don't like that ROM or you can keep it if you like it its all up to you and may you're fine
Veid71 said:
Yes you flash NI2 then you do whatever you wanted to do in safestrap usually I flash Roms and stuff that's why I said that but you don't have to then when you're done you flash the OG5 kernel to be able to use the phone again and yeah if you flash a different ROM you'll lose the stock ROM but you can always just flash it back if you don't like that ROM or you can keep it if you like it its all up to you and may you're fine
Click to expand...
Click to collapse
your the best thanks
Veid71 said:
Yes you flash NI2 then you do whatever you wanted to do in safestrap usually I flash Roms and stuff that's why I said that but you don't have to then when you're done you flash the OG5 kernel to be able to use the phone again and yeah if you flash a different ROM you'll lose the stock ROM but you can always just flash it back if you don't like that ROM or you can keep it if you like it its all up to you and may you're fine
Click to expand...
Click to collapse
ok so i did everything.
but when i reboot it still does not go into safestrap..
it did go into it when i flashed the first one. then the og5 file. rebooted a few times still no safestrap splash screen.
what im i doing wrong?
jtskir222 said:
ok so i did everything.
but when i reboot it still does not go into safestrap..
it did go into it when i flashed the first one. then the og5 file. rebooted a few times still no safestrap splash screen.
what im i doing wrong?
Click to expand...
Click to collapse
you havent done anything wrong the only time the safestrap screen comes up is when you flash that NI2 kernal safestrap doesnt work on any of the lollipop kernels :/
Veid71 said:
you havent done anything wrong the only time the safestrap screen comes up is when you flash that NI2 kernal safestrap doesnt work on any of the lollipop kernels :/
Click to expand...
Click to collapse
so whats the purpose of saafestrap?
I have to flash ni2 to get to it? i do that everytime i want to get into it? can i still make a backup in it? can i use a back up i made from it if i cant flash the ni2 to get the splash screen to come up?
I'm i able to install custom rom ?
I'm use to my s4 and safe strap coming up every reboot ..
i dont understand what the point is if i cant use SS
thanks
jtskir222 said:
so whats the purpose of saafestrap?
I have to flash ni2 to get to it? i do that everytime i want to get into it? can i still make a backup in it? can i use a back up i made from it if i cant flash the ni2 to get the splash screen to come up?
I'm i able to install custom rom ?
I'm use to my s4 and safe strap coming up every reboot ..
i dont understand what the point is if i cant use SS
thanks
Click to expand...
Click to collapse
yes you can make a backup in it and yes you have to flash the ni2 to get to the ss and yes you can use a backup you made from it i believe ive never used the backup function and you should always be able to get the splash screen to come up if you wind up hardbricking your phone some how all you should have to do is flash the boot.img and that should fix it then flash the ni2 kernel and go into it but ive never hardbricked it and yes you are able to install a custom rom using SS all you have to do is go to the install tab in it and install whatever you wanna install and and flash the regular kernel and youre good to go
Veid71 said:
yes you can make a backup in it and yes you have to flash the ni2 to get to the ss and yes you can use a backup you made from it i believe ive never used the backup function and you should always be able to get the splash screen to come up if you wind up hardbricking your phone some how all you should have to do is flash the boot.img and that should fix it then flash the ni2 kernel and go into it but ive never hardbricked it and yes you are able to install a custom rom using SS all you have to do is go to the install tab in it and install whatever you wanna install and and flash the regular kernel and youre good to go
Click to expand...
Click to collapse
Hey so my question is I can get into safe strap via app on my rom but in the tutorials, I see people being able to do it via splash, why does my splash screen not show up like the rest? My specs are the same as him except I am using ss 5.01
---------- Post added at 09:06 AM ---------- Previous post was at 09:03 AM ----------
I want to be able to instantly boot into it when my rom is corrupt from improper flashing so I can easily restore and try again properly
Alixbot said:
Hey so my question is I can get into safe strap via app on my rom but in the tutorials, I see people being able to do it via splash, why does my splash screen not show up like the rest? My specs are the same as him except I am using ss 5.01
---------- Post added at 09:06 AM ---------- Previous post was at 09:03 AM ----------
I want to be able to instantly boot into it when my rom is corrupt from improper flashing so I can easily restore and try again properly
Click to expand...
Click to collapse
As far as I know you can't do that but if your rom or something is messed up all you have to do is boot into download mode and flash an ni2 kernel and it'll pop up