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.
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 got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
lackyking said:
I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
Click to expand...
Click to collapse
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
simms22 said:
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
Click to expand...
Click to collapse
I tried, but also stopped on the first screen of manufacture logo.
lackyking said:
I tried, but also stopped on the first screen of manufacture logo.
Click to expand...
Click to collapse
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
simms22 said:
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
Click to expand...
Click to collapse
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
lackyking said:
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
Click to expand...
Click to collapse
youre not the only one that the latest cm code isnt booting up on.. http://forum.xda-developers.com/showthread.php?t=2435980
I recently installed the Dec.20.14 build of Kitkat 4.4. However, when my Defy booted up, from the start, the Wi-Fi said it was "turning on," and stayed like that for a couple of hours, and wouldn't turn on. Does anyone know the cause, or how to fix this issue?
Thanks in advance.
ricanrocks said:
I recently installed the Dec.20.14 build of Kitkat 4.4. However, when my Defy booted up, from the start, the Wi-Fi said it was "turning on," and stayed like that for a couple of hours, and wouldn't turn on. Does anyone know the cause, or how to fix this issue?
Thanks in advance.
Click to expand...
Click to collapse
Reboot.
hotdog125 said:
Reboot.
Click to expand...
Click to collapse
Didn't help...
ROM only first
Try flashing ROM only and reboot.
If Wi-Fi works then reboot to recovery and flash gapps and other zips if needed. :good:
Absroid said:
Try flashing ROM only and reboot.
If Wi-Fi works then reboot to recovery and flash gapps and other zips if needed. :good:
Click to expand...
Click to collapse
Thanks for the advice. Without gapps, 4.4 has wifi. However, now, i cannot flash gapps, as it says "Insufficient storage in the system partition" or something like that.
core gapps
ricanrocks said:
Thanks for the advice. Without gapps, 4.4 has wifi. However, now, i cannot flash gapps, as it says "Insufficient storage in the system partition" or something like that.
Click to expand...
Click to collapse
I think you used GApps Standard (~70MB), try using GApps Core (~16MB).
BaNkS GApps 4.4.2
Absroid said:
I think you used GApps Standard (~70MB), try using GApps Core (~16MB).
BaNkS GApps 4.4.2
Click to expand...
Click to collapse
Thanks everything works great now
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.
Well I have no problem flashing stock rom back, but everytime I flash TWRP it seems to just want to go in a bootloop. I have G928R4 USC on 7.0, every time I restart the phone it just bootloops. I can access TWRP but when I reboot it pulls that crap -_- Please help. Thank you
Tokumei no said:
Well I have no problem flashing stock rom back, but everytime I flash TWRP it seems to just want to go in a bootloop. I have G928R4 USC on 7.0, every time I restart the phone it just bootloops. I can access TWRP but when I reboot it pulls that crap -_- Please help. Thank you
Click to expand...
Click to collapse
You use the latest twrp??
dizio said:
You use the latest twrp??
Click to expand...
Click to collapse
Yes on the latest twrp. Idk what the issue is.
Would it be because I'm on 7.0? Idk if that's a thing but I would assume it wouldn't be the case.
https://twrp.me/devices/samsunggalaxys6edgeplus.html
Are you using the one for your device from here?
There are 2 variants of the SM-G928R4
kdogguk said:
https://twrp.me/devices/samsunggalaxys6edgeplus.html
Are you using the one for your device from here?
There are 2 variants of the SM-G928R4
Click to expand...
Click to collapse
Yes I'm sure I'm using the right one for my device. I have never had this issue before.
Went back to twrp 3.0.2.0 and it's fine, I guess it was just the latest release that was the issue.
Wu
Root
Tokumei no said:
Well I have no problem flashing stock rom back, but everytime I flash TWRP it seems to just want to go in a bootloop. I have G928R4 USC on 7.0, every time I restart the phone it just bootloops. I can access TWRP but when I reboot it pulls that crap -_- Please help. Thank you
Click to expand...
Click to collapse
Root it first
unbelievable i did a hard reset , then clear cache , before was random reboot , now it became worse and constant boot loop ,does replugging the battery solve this issue ?