I recently rooted my phone.
All went fine, I got into CWM and did a factory reset. Rebooted just fine. Tried to back into recovery to flash SU. When I try to go back into recovery I get the Android with the red examination mark on the belly. Tried re-flashing CWM, did not fix it. Tried rebooting into bootloader mode, got the red LED a couple times, but the phone did boot back into regular mode.
Tried erasing cache through fastboot and reflash CWM, now the phone won't boot, it'll boot into bootloader mode when I try to enter recovery, it just show me a black screen. No led.
Any help would be greatly appreciated.
Thank you.
UPDATE: Flashed a newer version of CWM, seems to be working fine now. Should I be worries about the red LED?
iTeeXDA said:
I recently rooted my phone.
All went fine, I got into CWM and did a factory reset. Rebooted just fine. Tried to back into recovery to flash SU. When I try to go back into recovery I get the Android with the red examination mark on the belly. Tried re-flashing CWM, did not fix it. Tried rebooting into bootloader mode, got the red LED a couple times, but the phone did boot back into regular mode.
Tried erasing cache through fastboot and reflash CWM, now the phone won't boot, it'll boot into bootloader mode when I try to enter recovery, it just show me a black screen. No led.
Any help would be greatly appreciated.
Thank you.
UPDATE: Flashed a newer version of CWM, seems to be working fine now. Should I be worries about the red LED?
Click to expand...
Click to collapse
Red LED in itself shouldn't mean too much unless you are having other problems as the LED is configurable. I would be worried if this issue continued to pop up.
Hi all,
I have a UK N910F 32GB Snapdragon Note 4, with a custom Lollipop rom that I've been using with no problems for a few months (http://forum.xda-developers.com/note-4/snapdragon-dev/rom-bob4-devbase-multi-csc-safe-bloat-t3033881). Yesterday the weirdness began - my Note 4 froze randomly in normal use and rebooted. It was then fine for around 5 hours, then froze again, and when it restarted it would continue to freeze on start-up. At that stage I could still boot into recovery (Clockwork Manager custom recovery), so I tried clearing cache and dalvik, which changed nothing. But now I am unable to do even that - it just gets stuck in bootloop and won't even go into recovery.
When I turn it on, it will stay on the Samsung splashscreen for 10 seconds, then reboot and vibrate twice, then go back onto splashscreen, reboots, etc. I need to remove the battery to stop this. The only thing I am able to do is boot into download mode, where the phone works with Odin fine, and I am able to flash successfully with Odin.
So far I have tried reflashing a stock UK 5.0.1 ROM - it initially gave me the ext4 error but I then got the N910F pit file and repartitioned - Odin flashing completed fine, then still got stuck on splashscreen with "Recovery booting...."). I have also tried to flash CWM and TWRP, which both flash fine, but then the phone still won't boot into recovery - I get:
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
and doesn't boot into recovery. I'm pretty sure I'm using the correct TWRP and CWM versions.
I've spent all day trawling XDA and the wider web with no luck. Does anyone have any ideas on how to fix this? I'm hoping it is a softbrick but cannot work out how to get it back. I don't care about losing any data at this stage, just keen to bring my Note 4 back to life!
TL;DR: phone will stay on bootloop when powered on - not caused by failed software install, just started happening randomly. Cannot boot into recovery. Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.
Markachy said:
Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.
Click to expand...
Click to collapse
.
Have you tried flashing your variants cf-root file with auto reboot unchecked, let it Pass, remove USB abd battery, wait 30 seconds and reboot? Sounds weird.. i know, but for a while that put many users on 5.0.1 softbricks back to their previous working ROM.
I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.
Markachy said:
I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.
Click to expand...
Click to collapse
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.
phongpan355 said:
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.
Click to expand...
Click to collapse
Just tried that, same issue. When it boots after installation, it says "Recovery booting..." in top left corner, then goes into bootloop. Thanks for the tip though.
Any other ideas out on the grapevine? Or is it time for a return?
I'm having the same issue. Tried stock ANK4, BOB4 and BOC3. Only bootloops and can't reach recovery mode.
Than I tried TWRP 2.8.7.0 and "philz_touch_6.59.0-trlte" but they don't work either.
Don't know what to do now. Never had this issue before on any Samsung device
EDIT: Tried Samsung Smart Switch and it dowloaded PDA: OC3 / CSC: OB6 / PHONE: OC3 (DTM). But my Note bootloops furthermore
Saw 2 other guys with the same Problem and no solution here.
And I found this. This could be the same issue we are facing:
http://forum.xda-developers.com/showthread.php?t=1840030
Hope there is a dev that can make this for our 910F
Hi all
This is now also happening to me...
Have Odind back to stock and it works for about 4 hours,
Then issue starts...
Reboots randomly
Then reboots to blank screen... No recovery
Again uk note 4. 910f
Hello
I have a rooted G900H on the stock ROM with the stock recovery installed.
I was going to patch the core.jar using Lucky Patcher so I figured I should make a nandroid backup first, so I booted to recovery only to find out it was the stock recovery. I figured I would go back to normal and then figure it out from there.
I chose the 'reboot to system' option and the phone got stuck at the Samsung logo.
I tried removing the battery and when I booted it up it got stuck again.
I have tried choosing the 'power down' option then turning it on, booting it without the microSD card, rebooting using power and volume down, and removing the battery and replacing the battery with a spare I have but everything leads back to the same - stuck at the Samsung Logo.
I have also tried rebooting to bootloader which also leads to getting stuck at the Samsung Logo.
When I go into the recovery it comes up with the Android Bot with it's body open and "no command" very quickly, before getting to the system recovery.
The last thing I tried was clearing the cache partition then choosing the 'reboot' option. Again, stuck at the Samsung Logo.
On the system recovery it has "Android System Recovery <3e> LRX21T.G900HXXU1BOAD" in red at the top.
If possible, I would really like to avoid having to factory reset or flashing a ROM again.
Thanks
Boot to recovery and clear the caches, see if that gets you back in, if not, flash the same stock ROM over the top of that one, you'll only lose root
Thanks for the reply.
I have tried clearing the caches from the recovery and rebooting but it did not help.
How would I go about reflashing the stock rom without a custom recovery? And where would I get the file?
Thanks
sammobile . com & ODIN
All links and instructions are under the download on sammobiles firmware section of their site, just enter your S5 Model into the firmware section (Free account needed to download)
Or samsung-updates . com
Hey. Sorry, I forgot to reply. Your suggestion worked out. Thanks for the help.
I was able to go back then get a custom recovery. Thanks again./
Nice one
Hi, Im new to the forum.
My Galaxy S5 LTE-A (G906S) has been stuck in a boot loop. I successfully restored it through Kies a month ago but now its doing the same thing.
I've now tried flashing with both, Kies and Odin, but it still appears to be in a boot loop but now with a prompt at the top "recovery booting" in blue.
Also I can only access the download mode and cant seem to enter recovery. If i try to charge it while off it enters bootloop. Hope it isnt a hardware problem... Can anyone please shed some light on the issue.
Thanks
PS. The device isnt/wasnt rooted.
slsamg said:
Hi, Im new to the forum.
My Galaxy S5 LTE-A (G906S) has been stuck in a boot loop. I successfully restored it through Kies a month ago but now its doing the same thing.
I've now tried flashing with both, Kies and Odin, but it still appears to be in a boot loop but now with a prompt at the top "recovery booting" in blue.
Also I can only access the download mode and cant seem to enter recovery. If i try to charge it while off it enters bootloop. Hope it isnt a hardware problem... Can anyone please shed some light on the issue.
Thanks
PS. The device isnt/wasnt rooted.
Click to expand...
Click to collapse
hi bro....first flash kitkat rom version with bootloader and modem ...after your phone coming up but give error and force close in app start...you should tern off phone and flash lollipop rom and bootloader and modem(loliipop version) again...after flash your phone bootloop and not came up.tern off and go to recovery and wipe data and partitions...and restart phone...enjoy
miladhiper said:
hi bro....first flash kitkat rom version with bootloader and modem ...after your phone coming up but give error and force close in app start...you should tern off phone and flash lollipop rom and bootloader and modem(loliipop version) again...after flash your phone bootloop and not came up.tern off and go to recovery and wipe data and partitions...and restart phone...enjoy
Click to expand...
Click to collapse
Can you suggest which one on here would do the job
http://www.sammobile.com/firmwares/database/SM-G906S/
Ive tried the 3 on the top, to no avail
Hello,
I have got tough nut to crack - T561 so nonQualcom one I bought on ebay.
Generally it is stuck on boot logo. I can get into Download Mode but not into Recovery mode (i know the combo - it simply doesn't work).
It is recocgnized by ODIN so I have tried flashing stock rom - it passes but even stock ROM is stuck on boot logo and doesn't go into Recovery.
I have tried flashing TWRP via ODIN - flashing passes but still cannot get into recovery - what's more there is red exclamation mark in upper left corner of the screen.
After TWRP i can still flash stock ROM and exclamation mark disappears - so it is just a marker of non stock component.
I have simply ran out of ideas. One interesting comment I have found on different device :
Factory resetting and wiping cache removes the conflicting data and allows the device to boot. Flashing via Odin does not wipe the data from the device during the flashing process unless the firmware being flashed has an upgraded/downgraded bootloader.
Click to expand...
Click to collapse
Is there an option to upgrade bootloader in my case so the caches are wiped ?
Or maybe someone has any other idea ?