So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
I had an AOKP rom on my sph-l720 and was working properly. Then I tried to install this stock rom - http://forum.xda-developers.com/showthread.php?t=2486134
Somewhere around the time i was flashing the rom from within mobile odin, my phone stopped booting.
Now on boot i see the Samsung s4 logo screen then phone turns off. If I try to boot into recovery, i see the blue writing "Recovery Booting..." but then phone turns off again.
Can someone help me atleast get back to recovery so I can try flashing another rom and get my phone running properly again.
I can get into download mode and have tried flashing TWRP a few times with odin which says it PASSED then phone restarts and turns off again.
Anyone have any advice for me?
Thanks!
Personally, I think I would go into download mode and odin back to stock. Then if you want you can reroot and flash another recovery. Here is a link to really good post that probably has everything you need. http://forum.xda-developers.com/showthread.php?t=2303917
I had an MK2 ATT Galaxy S4, which I believe has a locked bootloader?, that I rooted a long time ago. Keep in mind I don't know much at all about phones and only managed to do it by following a guide here. So I just switched to T-mobile and gave the phone to a guy in a store to allow it to work on T-mobile, which it does now. I noticed that the version is now 4.4.2 sgh-l337UCUFNB1. So I wanted to root it again. I finally rooted it using the towelroot.apk, after initially trying to root it with the Casual jar file and motochopper, which both didn't work for some reason.
After towelroot installed, I installed SuperSu and titanium backup. I then downloaded safestrap 3.75 and busy box and then installed a recovery. When I rebooted to recovery the phone didn't take me to safestrap custom rom slots, but instead just restarts the phone as normal, but with "Recovery Booting..." showing up in the left hand corner at the first splash screen in small blue text. I couldn't figure out why it wasn't working, so I repeatedly uninstalled recovery and tried the older versions/revisions of safestrap from 3.72 and up, but either the reboot from recovery option was grayed out or rebooting from recovery just restarted the phone like previously.
Now I just noticed that when the phone is off and plugged in with a USB cable, the phone doesn't light up and show a charging icon. Instead, it vibrates every two seconds while it's plugged in. Holding the power button does nothing until I unplug the cable, which will finally allow it to turn on.
I don't know what I've done that could have caused this. Is there any way to restore it? I would do a factory reset, but would it undo the T-mobile network transfer on the phone? I'm not exactly sure how it works when the person at the store switched it from AT&T to t-mobile. Is there any other solution for the vibrating? I'm scared that if I run out of battery, I won't be able to charge the phone again and will be left with a brick.
Thanks in advance. Help is very appreciated! :crying:
Hey guys,
I have a rooted Note 3 from verizon on the hyperdrive rom. today I got a message from SUbinary (something like that) that there was an update and that I need to reboot to update. So I just clicked okay and my phone restarted. However since then I'm stuck in a boot loop with the blue message in the upper left corner saying "recovery loading.." with the note 3 white logo appearing. Then the phone vibrates twice and comes back to the same screen. I don't see the custom/lock picture like I used too. I've tried multiple times to take the battery out but no luck. I can't seem to actually enter the recovery panel at all. I've tried holding the home/power/volume up but it just starts the boot loops again. Not sure what to do. I just want to the phone to work but it seems like a hard brick?
secants said:
Hey guys,
I have a rooted Note 3 from verizon on the hyperdrive rom. today I got a message from SUbinary (something like that) that there was an update and that I need to reboot to update. So I just clicked okay and my phone restarted. However since then I'm stuck in a boot loop with the blue message in the upper left corner saying "recovery loading.." with the note 3 white logo appearing. Then the phone vibrates twice and comes back to the same screen. I don't see the custom/lock picture like I used too. I've tried multiple times to take the battery out but no luck. I can't seem to actually enter the recovery panel at all. I've tried holding the home/power/volume up but it just starts the boot loops again. Not sure what to do. I just want to the phone to work but it seems like a hard brick?
Click to expand...
Click to collapse
If you soft brick then u can only access download mode and if you hard brick then you need an expert. The problem is that verizon and at&t have locked bootloaders. Safestrap recovery is usually used there.
Can you reflash safestrap recovery via Odin ?
This link might be helpful cause im not so used to safestrap only know the basics.
Galaxy-note-3.wonderhowto.com/how-to/install-custom-recovery-your-bootloader-locked-galaxy-note-3-at-t-verizon-0156667/
If you cant access the recovery and only download mode then you have soft brick and need to reflash stock firmware.
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!