Related
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.
I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!
Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.
I don't have a nandroid I have a twrp backup
Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.
Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!
jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.
Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM
Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...
Anyone know if I can just use the Rogers ROM its pretty much the same company
Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs
Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had
This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.
Hi guys,
This is my issue: I rooted my S4 with CF-Root with Odin, installed PhilZ Touch 5 recovery, installed and installed Janjan's 4.4 http://forum.xda-developers.com/member.php?u=490110. So far so good, everything worked. Then I made a mistake and enabled encryption. Phone still worked but after some modifications I wanted to rewipe and reload the OS image and this is where everything broke.
It seems I can wipe all partitions (no errormessages) but after loading the zip from the external SD card (no error messages) it still seems to have encryption enabled. The phone boots and asks for entering the PIN after a while like its still encrypted. Then after a while it reboots.
Any suggestions?
Thanks
Had the same prob a few months back, check my post on this:
I believe using encryption on cyanogenmod is a bad idea, better to just have it removed for i9505 I think.
http://forum.xda-developers.com/showthread.php?t=2451822
I assume you haven't installed samsung 4.3? Have never tested this out on that version. Can't be much worse than a phone that wont boot. Good luck,
ephraim87 said:
Had the same prob a few months back, check my post on this:
I believe using encryption on cyanogenmod is a bad idea, better to just have it removed for i9505 I think.
http://forum.xda-developers.com/showthread.php?t=2451822
I assume you haven't installed samsung 4.3? Have never tested this out on that version. Can't be much worse than a phone that wont boot. Good luck,
Click to expand...
Click to collapse
You saved my bacon. Did the factory restore with the PID as described here
http://forum.xda-developers.com/showthread.php?t=2265477
bambam4171 said:
You saved my bacon. Did the factory restore with the PID as described here
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
Your welcome, just remember if all else fails, flash back to stock, :good:
I have a rooted Galaxy Note 3 (Verizon). I'm running Safestrap and made a backup of the stock ROM about two weeks ago.
...I had not tried any other ROMs, now I wish I had. Something went wrong with my stock ROM, long story short - it's just not workin' right and I want to restore it from the backup I've made.
I want to restore it to the stock ROM slot (not a new ROM slot).
The backup is on a Micro SD card, Safestrap sees the backup file. The 'Restore' button is not red (while I've got the stock ROM activated).
I haven't done anything yet. I'm hoping I can just hit restore and it'll restore the stock ROM slot to the backup I made a couple weeks ago.
...is it that simple? Is there anything I should or should not do?
Twisked said:
I have a rooted Galaxy Note 3 (Verizon). I'm running Safestrap and made a backup of the stock ROM about two weeks ago.
...I had not tried any other ROMs, now I wish I had. Something went wrong with my stock ROM, long story short - it's just not workin' right and I want to restore it from the backup I've made.
I want to restore it to the stock ROM slot (not a new ROM slot).
The backup is on a Micro SD card, Safestrap sees the backup file. The 'Restore' button is not red (while I've got the stock ROM activated).
I haven't done anything yet. I'm hoping I can just hit restore and it'll restore the stock ROM slot to the backup I made a couple weeks ago.
...is it that simple? Is there anything I should or should not do?
Click to expand...
Click to collapse
It is that simple, just hit restore, select the file, then swipe the restore button.
airmaxx23 said:
It is that simple, just hit restore, select the file, then swipe the restore button.
Click to expand...
Click to collapse
Just one more question, if for any reason the restore fails... will Safestrap be unaffected?
What I mean by that is, I have another ROM (Hyperdrive) up and running that I can choose with Safestrap. If for some reason the restoration of the Stock ROM (in the stock ROM slot) fails, Safestrap will keep on working and I can choose Hyperdrive.
...and then if I reboot, I can still choose to boot up into Recovery mode with Safestrap. Is that correct?
Twisked said:
Just one more question, if for any reason the restore fails... will Safestrap be unaffected?
What I mean by that is, I have another ROM (Hyperdrive) up and running that I can choose with Safestrap. If for some reason the restoration of the Stock ROM (in the stock ROM slot) fails, Safestrap will keep on working and I can choose Hyperdrive.
...and then if I reboot, I can still choose to boot up into Recovery mode with Safestrap. Is that correct?
Click to expand...
Click to collapse
If the restore fails you'll get a message saying that it failed, you can then just restore a different backup.
airmaxx23 said:
If the restore fails you'll get a message saying that it failed, you can then just restore a different backup.
Click to expand...
Click to collapse
I've only got the one backup file that I'd made.
If it does fail, could I download a stock ROM from somewhere to put into the Stock ROM slot?
I'm not sure how Safestrap works, in my thinking if I screw up (wipe out) the Stock ROM slot then I've deleted Safestrap too. I think that's where my biggest worries are coming into play here. I'm hoping my understand of that is wrong.
...thanks by the way for your replies :good:
EDIT: I found a site that has a rooted stock ROM for the Verizon Galaxy Note 3. Downloading it now to be safe.
Twisked said:
I've only got the one backup file that I'd made.
If it does fail, could I download a stock ROM from somewhere to put into the Stock ROM slot?
I'm not sure how Safestrap works, in my thinking if I screw up (wipe out) the Stock ROM slot then I've deleted Safestrap too. I think that's where my biggest worries are coming into play here. I'm hoping my understand of that is wrong.
...thanks by the way for your replies :good:
Click to expand...
Click to collapse
If for some odd reason your backup fails you could place one of the available ROMs on your sdcard and install it from there. In a worst case scenario you always have Odin and the .tar files to restore your phone.
airmaxx23 said:
If for some odd reason your backup fails you could place one of the available ROMs on your sdcard and install it from there. In a worst case scenario you always have Odin and the .tar files to restore your phone.
Click to expand...
Click to collapse
Hopefully last question (sorry, want to make sure I have my head wrapped around this)
You said if the restore fails I'll simply get a failed message. ...if that happens, could I choose to boot with the Hyperdrive ROM and restart the phone with no problems?
I guess what I'm trying to ask is, isn't Safestrap running from that Stock ROM slot? Or does it run independently of whatever ROMs are in the slots.
Twisked said:
Hopefully last question (sorry, want to make sure I have my head wrapped around this)
You said if the restore fails I'll simply get a failed message. ...if that happens, could I choose to boot with the Hyperdrive ROM and restart the phone with no problems?
I guess what I'm trying to ask is, isn't Safestrap running from that Stock ROM slot? Or does it run independently of whatever ROMs are in the slots.
Click to expand...
Click to collapse
If the restore fails it will not effect SafeStrap, you will just be able to boot up HyperDrive afterwards. The chances of it failing are extremely slim.
airmaxx23 said:
If the restore fails it will not effect SafeStrap, you will just be able to boot up HyperDrive afterwards. The chances of it failing are extremely slim.
Click to expand...
Click to collapse
Thank you so much for all your help! I'm probably going to wait 'til tomorrow evening to do this (need my phone runnin' smoothly from now 'til then for work).
...not sure which reply of yours to click 'THANKS' on. I guess the first one, but they were all helpful. :good:
Twisked said:
Thank you so much for all your help! I'm probably going to wait 'til tomorrow evening to do this (need my phone runnin' smoothly from now 'til then for work).
...not sure which reply of yours to click 'THANKS' on. I guess the first one, but they were all helpful. :good:
Click to expand...
Click to collapse
One more thing, more of a "heads up". During the restore if your screen turns off and pressing Power or Home doesn't turn it on just leave it and when the restore is done it will turn on or just reboot on it's own. Restores can take 5 minutes or more depending on how big of a backup file you have.
airmaxx23 said:
One more thing, more of a "heads up". During the restore if your screen turns off and pressing Power or Home doesn't turn it on just leave it and when the restore is done it will turn on or just reboot on it's own. Restores can take 5 minutes or more depending on how big of a backup file you have.
Click to expand...
Click to collapse
Thought you might like to know, my meeting for tomorrow was cancelled so I went ahead and tried the restoration. ...worked FLAWLESSLY!! Whew!! :laugh:
So my phone is back, everything is running PERFECTLY.
Which brings me to a new question (hopefully you might know). I'm on 4.3 and do not want to get the OTA update for 4.4 from Verizon. It will download automatically (640 MBs or so), and a notification will appear that can't be swiped away.
Is there something in Titanium Backup that I can freeze to prevent the OTA update? To stop that non-swipable notification from appearing?
Twisked said:
Thought you might like to know, my meeting for tomorrow was cancelled so I went ahead and tried the restoration. ...worked FLAWLESSLY!! Whew!! :laugh:
So my phone is back, everything is running PERFECTLY.
Which brings me to a new question (hopefully you might know). I'm on 4.3 and do not want to get the OTA update for 4.4 from Verizon. It will download automatically (640 MBs or so), and a notification will appear that can't be swiped away.
Is there something in Titanium Backup that I can freeze to prevent the OTA update? To stop that non-swipable notification from appearing?
Click to expand...
Click to collapse
Yes, you can follow THIS guide to remove the notification and prevent further OTA updates from showing up.
I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Haloman800 said:
I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Click to expand...
Click to collapse
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Misterxtc said:
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Click to expand...
Click to collapse
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
edit: p.s. nice avatar
Haloman800 said:
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
Click to expand...
Click to collapse
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Edit: Thanks on the avatar, quite a few people like it. Hopefully it helps someone out.
Misterxtc said:
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Click to expand...
Click to collapse
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Haloman800 said:
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Click to expand...
Click to collapse
Yup, run towelroot and update SU from SS.
Worked perfectly. Thanks!!
Haloman800 said:
Worked perfectly. Thanks!!
Click to expand...
Click to collapse
Cool, I'm glad it worked for you.