It started a few days ago. My phone would suddenly reboot and such and wouldn't be able to get past the Samsung screen until I went into TWRP and rebooted through there. Now my phone won't even do anything. It just keeps rebooting immedialty. Should I install the Stock firmware again and then go back to Cyanogenmod 10.2?
bvm1228 said:
It started a few days ago. My phone would suddenly reboot and such and wouldn't be able to get past the Samsung screen until I went into TWRP and rebooted through there. Now my phone won't even do anything. It just keeps rebooting immediately. Should I install the Stock firmware again and then go back to Cyanogenmod 10.2?
Click to expand...
Click to collapse
First, can you give us some information...
What model of the S4 is it?
What baseband are you on?
Etc, etc...
bvm1228 said:
It started a few days ago. My phone would suddenly reboot and such and wouldn't be able to get past the Samsung screen until I went into TWRP and rebooted through there. Now my phone won't even do anything. It just keeps rebooting immedialty. Should I install the Stock firmware again and then go back to Cyanogenmod 10.2?
Click to expand...
Click to collapse
Since you have twrp, I assume you have an i337 and you're on mdl firmware. If so, I'd flash the stock mdl firmware and see if you still have the problem. If you do then it's most likely a hardware problem and you should look into warranty.
Related
EDIT: okay I found the stock rom, but my problem persists, so I'll just state the issue im having and hopefully someone who knows what theyre doing can tell me where I screwed up lol.
So, I had my Sprint S4 on MDC, was rooted with CF auto root, and had TWRP recovery.. I let my little brother play with my new phone, and he saw the lil update notification in the tray, so he updated to MF9 for me... That didnt go as planned.
After the update, my phone rebooted, and went all the way to the sprint logo, and stuck there. for about an hour. My device got reeaaallly hot so i popped the battery out, since power buttons werent responding. Put the battery back in, and same problem. SO, I got the stock rom, and booted it with Odin. It booted to recovery, then rebooted and stuck on the Samsung Galaxy S4 splash screen. I did the stock rom again, did the same thing. Now im stuck on the samsung splash screen and I have no idea what to do
dannyblunts said:
EDIT: okay I found the stock rom, but my problem persists, so I'll just state the issue im having and hopefully someone who knows what theyre doing can tell me where I screwed up lol.
So, I had my Sprint S4 on MDC, was rooted with CF auto root, and had TWRP recovery.. I let my little brother play with my new phone, and he saw the lil update notification in the tray, so he updated to MF9 for me... That didnt go as planned.
After the update, my phone rebooted, and went all the way to the sprint logo, and stuck there. for about an hour. My device got reeaaallly hot so i popped the battery out, since power buttons werent responding. Put the battery back in, and same problem. SO, I got the stock rom, and booted it with Odin. It booted to recovery, then rebooted and stuck on the Samsung Galaxy S4 splash screen. I did the stock rom again, did the same thing. Now im stuck on the samsung splash screen and I have no idea what to do
Click to expand...
Click to collapse
Go to recovery, do a factory reset, reboot.
Bt I doubt he was able to update you to MF9 since you were in MDC I believe he updated you to MDL.
Edit: here a stock tar of MF9 if you need it. http://forum.xda-developers.com/showthread.php?t=2375523
Sent from my SPH-L720 using xda app-developers app
I'm not sure that will work but it's worth a try. You might have to just use PC Odin and do a full flash then reroot it and get it to where you want it.
It's been awhile since I changed anything on this phone, I've been running CM11 with no issues. The wife was playing with my phone which is on cm12 and wanted me to upgrade it. Great, I hate having to touch her phone but ok.
1. Did a straight upgrade to CM12 nightly (couple nights ago build) with gapps from CM site. After the install everything crashes on the initial load, it's like the baseband is jacked and doesn't know how to handle the new google play services because everything crashes.
2. Went back and wiped internal everything this time, re installed nightly and gapps. No change.
3. Tried step 2 a couple more times and different gapps from PA and other random sites (micro, light, stock versions) and then TWRP just died on me. It's asking for a password when I first go in so now I'm stuck there. Tried to use ODIN to install the latest TWRP after converting it with another script found here (i'll find the link).
so, I'm probably going to have to use ODIN to restore some stock version of S4 ATT but I really don't know which one is stock that would work with CM12. I don't want to get caught in the safestrap crap of dual boot and whatever else. Any help is greatly appreciated.
You'll need to Odin the mdl firmware in Odin. Be careful as it will want to update itself after you flash it. See sammobile.com for the firmware.
Sent from my Nexus 9 using XDA Free mobile app
Awesome, thanks!
Flashed the stock, towelroot, twrp from google play and cm12 nightly. Perfect and back where I left off. Thanks!!
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
kronikwisdom said:
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
Ok, factory reset worked on the second try. Sent it in to a boot loop on the first go around, odd. Thanks!
Hi,
I have a rooted nexus 6p, all was well until it decided to reboot and boot-loop when I opened my music app. I get as far as the white Google logo then the phone restarts and I'm back to the normal warning then Google logo then reboot.
I have managed to get into the recovery screen (with the android laying down) but when i choose recovery mode the phone just starts boot-looping again.
I am wondering if I have somehow managed to hard brick it?
I have tried to flash the latest OS onto my phone but it said no signature.
I did managed to wipe the device also.
Thanks for any help.
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
istperson said:
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
Click to expand...
Click to collapse
When my phone started playing up I was still on MM 6.0.1, I tried to flash N after the boot-looping started.
Thanks
i have been trying to install a good rom on my s5. i know that since i have an 11' toshiba chip, i cant do any major custom roms only stock touchwiz roms. i have 3 or 4 that i have found that actually work on my phone and when i tried a new rom today, it didn't work. so i flashed 4.4.2 again to start from scratch and i went back to my usual stock deodexed rom that is always a for sure rom that works. today when i flashed it, twrp (safestrap) prompts me to either boot normally or to continue. i have had this problem in the past, and whenever it shows that screen, it will never boot up, after the prompt it will just have a black screen for about 5 min. before booting stock recovery. if i boot it up again, safestrap will still prompt me if i want to boot recovery or continue and keep repeating this cycle. last time, it had resolved itself and didnt show up after wiping and reflashing my rom. this time it wont go away and my phone wont boot anything. thanks in advance
as.hs said:
i have been trying to install a good rom on my s5. i know that since i have an 11' toshiba chip, i cant do any major custom roms only stock touchwiz roms. i have 3 or 4 that i have found that actually work on my phone and when i tried a new rom today, it didn't work. so i flashed 4.4.2 again to start from scratch and i went back to my usual stock deodexed rom that is always a for sure rom that works. today when i flashed it, twrp (safestrap) prompts me to either boot normally or to continue. i have had this problem in the past, and whenever it shows that screen, it will never boot up, after the prompt it will just have a black screen for about 5 min. before booting stock recovery. if i boot it up again, safestrap will still prompt me if i want to boot recovery or continue and keep repeating this cycle. last time, it had resolved itself and didnt show up after wiping and reflashing my rom. this time it wont go away and my phone wont boot anything. thanks in advance
Click to expand...
Click to collapse
Find youre phones firmware and put phone into download mode and flash firmware!
[My phone is already repaired by Samsung under warranty, my internal storage was broken so they replaced the motherboard. There is no need to reply to this thread anymore. Thanks anyway]
Hello everyone, I need help!!!!
Today my Samsung GS6 Edge+ died. (At least, that's what I think)
I own my G928F for 1,5 years now. I rooted it two weeks after that. Several weeks ago I flashed a new ROM called N-Lite Nougat v4.1 which has worked smoothly and without any problems since I've flashed it.
However, today, the 26th of June, my phone turned off all of a sudden while scrolling through Facebook. I haven't flashed, installed nor done, anything that would affect my phone in such a way that it would crash this way. I tried force rebooting with the 3 buttons pressed (Home, Vol+, On/Off) several times. My phone just boots into the ROM and then freezes instantly. Again tried force rebooting for like 5 times, NO luck. Then I tried booting into recovery mode (TWRP 3.1.0.0), cleared Dalvik and cache, factory reset, rebooted, still no luck. Tried several other custom ROM's, still NO luck. Also tried flashing stock Samsung Firmware using ODIN, no luck whatsoever.
I couldn't find any similar problems in the ROM thread, nor anywhere else on the internet. Besides that, I'm starting to think this problem is a defect to the hardware, not the software.
Does anyone know what would be the best thing to do in my situation? Or perhaps anyone who might know what the problem might be and have a possible solution?
Thanks in Advance.
Recovery mode (TWRP 3.1.0.0) is accessible though, but that's all. While trying to install another ROM it just reboots randomly, during flashing progress.
When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?
kdogguk said:
When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?
Click to expand...
Click to collapse
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success
Larss97 said:
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success
Click to expand...
Click to collapse
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?
kdogguk said:
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?
Click to expand...
Click to collapse
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.
Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
Try to do a factory reset in the stock recovery. It might help.
vishnu8058 said:
Try to do a factory reset in the stock recovery. It might help.
Click to expand...
Click to collapse
Done that, no success
kdogguk said:
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.
Click to expand...
Click to collapse
Yeah i got the right rom for my phone. I've already sent it to a certified Samsung repair centre, it's still under warranty. Thanks for the help anyway