I upgraded to Nightly 20160107 today through a notification on my S4. After the upgrade, I noticed that the phone was not working right. A number of apps were missing and the camera was not responding, etc. I quickly went to Recovery and chose Restore. But I did not wipe before I pressed on the Restore Button. The process hung and did not advance after 10 MB of 5600 MB. After a fairly longtime, I removed the battery and after I reinserted, the phone hung on the boot screen showing SAMSUNG GALAXY S4. I have tried removing and reinserting the battery several times but got the same result.
Can somebody help me please?
Try to flash stock rom with odin http://www.sammobile.com/
Try a full wipe before restoring.
Normally, when you restore something, it automatically wipes.
But yeah, since the restore didn't complete you messed up the OS. In other words there is no OS to boot in. So I'd suggest flashing a rom. Any rom should do.
Related
Okay I've never read such a weird explanation on any thread in this forum.
Btw, I recently flashed InDroid 4.3. Less than a week ago.
My phone was running perfectly, but my google account linked with my phone was not what I wanted it to be. So I added another account and my phone said that to delete my previous account I had to do a factory reset.
So I deleted my older backup that I had created using Titanium Backup (when I was using stock ROM) and I created a new backup.
So I held down the power button and tried to get into recovery. But my phone just got stuck at the "samsung i5801" screen. I let it be for 10-15 minutes but it won't go beyond that. So I re-inserted the battery, and tried to get into recovery again. Didn't work.
Then I tried to just start my phone in normal mode, but still it just got stuck at the i5801 screen. I removed the sim card, SD card and tried, still stuck at the same screen.
Then I tried to get into downloading mode, which (thank god) worked.
Now I know the logical thing to do is just to flash a new ROM but my questions are :
a- WTF happened?!??!?!?!
b- since I can't get into recovery or normal mode, how do I reset factory settings / clear cache? And if I don't do all that, will flashing be successful? and safe?
btw, I'd like to continue with InDroid until Kyrillos 6.0 is perfectly stable.
-That happens frequently with indroid.. main cause could be the filesystems..
-flash kyrillos v6 its pretty much stable..
-Once you flash a new rom you'll be able to boot into recovery..
-Remove sdcard while flashing once done insert sdcard and wipe data n cache from recovery..
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Which ROMs are you installing? On I337M your best bet is T-Mobile ROMs and Kernels. I have Bell I337M and have no issues.
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
kiru said:
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
Click to expand...
Click to collapse
i just went through this all last night what a pita , problem is twrp , if you do a full wipe when you type the word yes , you can only bootup 1 time then it gets stuck next time you boot , theres no way to fix it , even going back to old version of twrp wont do it , you have to compleatlly remove root and return to stock , re root and install twrp again , then if your luck your nandropid backup will work , it took me 5 hrs to fuger this all out , stupid twrp drove me nuts .,...
in short , return to stock and reroot , then never do a full wipe where you have to type yes
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
i had the same problem, im with rogers so i downloaded the rogers rom 4.2 and i cant make any phone calls or listen to music or watch videos. my phone came with 4.3 does anyone have any ideas to help me?
I've spent close to most a work day now searching for an answer but am stumped.
I'm on MDL.
Downloade and flashed latest version of Goldeneye. Works great. After a bit, went to reboot phone.
Phone stuck @ boot screen ("Samsung" w/ unlocked lock below).
pull battery, same screen.
Wipe/reflash - all is well. Then re-boot, and stuck at same screen.
I have tried restoring multiple Nandroids and loaded 2 differnet roms. All with same result.
Also tried wiping data and restoring ESF backup and restoring my first rooted stock backup.
Same issue. works great till I reboot. Obviously somehting isn't sticking.
Any ideas? I hope I gave enough info
what recovery are you using?
The last few days I had an experience that I want to share. Maybe it helps somebody else.
Last week I upgraded my Defy from Quarx's CM10.2 to CM11 version 20140724.
It ran for about two days. It was stable and the performance looked better than before.
Then, when I was outside, my battery was empty. I always have another battery with me, so I exchanged the battery.
Then, two seconds after I inserted the battery, a black screen with the following white text appeared spontaneously, without pressing a button:
Bootloader
09.10
Code Corrupt
Ready to Program
connect USB
I could not enter recovery, or anything else.
So, I decided to go back and flash the original Motorola Android 2.2 version.
On earlier occasions this worked perfectly when I bricked my phone, but this time, after flashing the SBF with RSDlite, the phone hang while booting with the android logo on the screen. Only after a few hours of trying different SBF systems, the idea popped up, that the problem was not in the SBF, but in the combination of the old Motorola system and the new CM11 data partition. So, I entered recovery and wiped the data partition.
Then the system booted normally and I could proceed with rooting the system, installing custom recovery and restoring the backup.
Everything is back to normal again.
Now, I wonder what could have caused this problem.
I am a bit suspicious about the backup method I used. I create backups with the online nandroid app. The CM11 system installed the TWRP 2.7 recovery. The first time I tried to restore a backup, I noticed that the TWRP recovery had a problem with the old (CM10) and the new (CM11) backups, because they contained files for partitions and-sec and recovery, that it could not handle. In later attempts to restore the backup I unticked these partitions and the restore seemed to work well. I rebooted it several times. Could it be that these attempts damaged the system in such a way, that only when inserting a battery, the corruption was detected?
Or should I assume that there was a hardware glitch when the battery was replaced?
F.Zwarts said:
.
Then, when I was outside, my battery was empty.
Click to expand...
Click to collapse
iirc this was one of the bugs of cm11. if you let the battery runs completely down, it may not boot again. not sure if this has been fixed with the latest cm11.
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.