Bootlop error after root failure. - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello,
I decided to try and root my phone yesterday in order to use flux and the AdAway for my Samsung Galaxy Note 3 SM-N9007. However when i used Odin instead of saying "Pass" it was saying "Reset". As it was my first time doing anything like this, I unplugged my phone which seemed to have been the wrong move. My phone would vibrate once or twice and then reboot to show me the Samsung logo and the words "Recovery is not Seandroid forcing". It would show that screen for approximately 2 seconds where it turns off and repeats the process. Whilst off for that period of time I cannot enter recovery mode. However I can enter the download mode (vol. down + power). I have researched a bit on what to do however I am still a bit unsure.
*It seems the main problem is I can not enter recovery mode at all. As the logo shows it just turns off instantly and then turns back on getting stuck in a loop.
What I gathered online.
- Download the stock firmware for it. (The file I'm downloading is roughly 1.3 gb)
- Load the file the same way I tried to root the phone.
Is this correct? Could I get some assistance please?
Thank you

I have managed to resolve the error by loading in the stock firmware with Odin.

Heize_July said:
I have managed to resolve the error by loading in the stock firmware with Odin.
Click to expand...
Click to collapse
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted

ShaDisNX255 said:
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted
Click to expand...
Click to collapse
Yea I made the mistake of choosing the wrong CFRoot file. The one I installed was for Android version 4.3 whereas my device was 5.0. After retrying I manged to get the root to work. Thanks anyways!

Related

[Q] Boot loop after rooting my Galaxy note 4 N910F

Hello everyone,
I tried rooting my Note 4 using Chainfire's [SM-N910*] CF-Auto-Root :
http://forum.xda-developers.com/not...-auto-root-t2897428/post55865442#post55865442
However after Odin finishes and shows "pass", the phone does not reboot in recovery mode nor shows the red android, it loops on the samsung logo and written in the top left corner of the screen 3 lines reading :
Recovery booting ...
Recovery is not seandroid enforcing
Set warranty bit : recovery
I used the correct file for my phone, and now i cannot enter recovery mode, only download mode is accessible.
Any advice is greatly appreciated.
Flash stock firmware with odin and try again
The message is normal it comes up when you root your phone. Do you have a custom recovery installed?
sawdoctor said:
The message is normal it comes up when you root your phone. Do you have a custom recovery installed?F
Click to expand...
Click to collapse
I didnt have custom recovery and it happened, i fixed my boot loop and i still want to root it but each time i try it goes back to the boot loop. My note 4 is SM-N910F
Alex_popa said:
I didnt have custom recovery and it happened, i fixed my boot loop and i still want to root it but each time i try it goes back to the boot loop. My note 4 is SM-N910F
Click to expand...
Click to collapse
indentical same problem
SM-910F
4.4.4
N910FXXU1ANKA
help please
Probably should have mentioned my build number and what not too...
healthyboy said:
Hello everyone,
I tried rooting my Note 4 using Chainfire's [SM-N910*] CF-Auto-Root :
http://forum.xda-developers.com/not...-auto-root-t2897428/post55865442#post55865442
However after Odin finishes and shows "pass", the phone does not reboot in recovery mode nor shows the red android, it loops on the samsung logo and written in the top left corner of the screen 3 lines reading :
Recovery booting ...
Recovery is not seandroid enforcing
Set warranty bit : recovery
I used the correct file for my phone, and now i cannot enter recovery mode, only download mode is accessible.
Any advice is greatly appreciated.
Click to expand...
Click to collapse
nikboss77 said:
indentical same problem
SM-910F
4.4.4
N910FXXU1ANKA
help please
Click to expand...
Click to collapse
I had a same problem but I found easy solution. If you have a bootloop install latest CWM recovery, open ODIN (I used newest version) and uncheck Auto Reboot, select CWM in AP and flash it, after that phone will stay still in Download mode. Then unplug usb from PC and remove battery for 5-7sec, give it back and turn phone on - your phone will boot into CWM recovery for sure ...then I flashed latest TWRP
bondro said:
I had a same problem but I found easy solution. If you have a bootloop install latest CWM recovery, open ODIN (I used newest version) and uncheck Auto Reboot, select CWM in AP and flash it, after that phone will stay still in Download mode. Then unplug usb from PC and remove battery for 5-7sec, give it back and turn phone on - your phone will boot into CWM recovery for sure ...then I flashed latest TWRP
Click to expand...
Click to collapse
Thanks I wanted to ask you once I am in recovery with cwm as I install TWRP? Also from odin?
And how to proceed with CF-Auto-Root?
Sorry for my ignorance....
nikboss77 said:
Thanks I wanted to ask you once I am in recovery with cwm as I install TWRP? Also from odin?
And how to proceed with CF-Auto-Root?
Sorry for my ignorance....
Click to expand...
Click to collapse
Download corespond file from cf auto root page , put your phone into download mode ( VOL - home button and lock screen button ) then select in odin AP file : CF-Auto-Root-trlte-trltexx-smn910f.tar.md5 , start , and wait a few seconds to boot ! Cheers
ManDone.vRs said:
Download corespond file from cf auto root page , put your phone into download mode ( VOL - home button and lock screen button ) then select in odin AP file : CF-Auto-Root-trlte-trltexx-smn910f.tar.md5 , start , and wait a few seconds to boot ! Cheers
Click to expand...
Click to collapse
I know what to do, I have been doing this all along but it goes into a mad boot loop. The Red Android doesn't pop up on screen either. I thought for a second I bricked my phone when it happened but luckily I was able to restore it. Any other suggestions??
Alex_popa said:
I know what to do, I have been doing this all along but it goes into a mad boot loop. The Red Android doesn't pop up on screen either. I thought for a second I bricked my phone when it happened but luckily I was able to restore it. Any other suggestions??
Click to expand...
Click to collapse
It is in fact ... I did the root samsung in many of my friends ... always the same procedure with odin. But this does not load Note4 just the red robot and immediately goes into loop.I do not understand where it can be the error or incompatibility
Plz Help
Sorry for posting on this forum but i cant find any help on the N910H forum. Hi am having the exact same problem phone cant boot to download mode and not recovery. i tried to odin back to stock same problem, i tried twrp, philz and cwm recovery. it says pass in Odin but the phone wont reboot past the android logo and cant boot to recovery.Model number is SM-N910H
Had the same issue, fixed it however flashing CF auto root always results in a boot loop.
Is there any other way of rooting the note 4 without Odin?
At this point I realized that more than anyone has this problem of our loop in doing root on your Notes 4, now in addition to figure out if there is a solution to this problem, I would like to know if this problem is present on the Notes 4 with the same model, firmware updates etc. etc .... or this Note 4 that we are "bad"?
I successfully rooted my note 4 SM-N910F using this method.
Search zedomax note 4 root. It should be the first result.
Sorry I wasn't able to link the video I was not allowed to submit an external link until I have 10 posts.
My phone did this weird thing where it erased twrp so straight after passing in odin I took out the battery and entered twrp. From there it was easy. Hope this helps anyone else with this problem
Alex_popa said:
Is there any other way of rooting the note 4 without Odin?
Click to expand...
Click to collapse
You can flash a flashable SuperSU from chainfire's website using CWM or TWRP recovery.
But if you are on stock TW 5.1.1, you can't root it just yet, it will cause bootloop.
Flash stock 5.1.1 again to fix bootloop
i flashed again to the stock 5.1.1 and i still get stuck on Samsung Galaxy Logo i tried every thing wipe data and wipe cache and i remove battery for million time and i even rooted the phone and start but still freezing on galaxy logo and then Re download the latest Official Rom From sammobile and still Stuck on Galaxy logo the problem came to me when i install Twrp on my rooted note 4 and it's stucked on twrp so i downloaded the latest Rom and still get freeze on Galaxy Logo please help me :/
Same problem here. Flashed SM-N910F (International, Qualcomm): CF-Auto-Root-trlte-trltexx-smn910f.zip but stuck in bootloop, all i get is the threeuk logo and the music. Tried with auto reboot on and off but with no luck.
breeg said:
Same problem here. Flashed SM-N910F (International, Qualcomm): CF-Auto-Root-trlte-trltexx-smn910f.zip but stuck in bootloop, all i get is the threeuk logo and the music. Tried with auto reboot on and off but with no luck.
Click to expand...
Click to collapse
If you're on 5.1.1 then you need a root capable kernel to be flashed too...

[FIX?] Stuck on bootloop

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

Samsung Galaxy S5 SM-G900F No Recovery Mode always restart Brick

Hello,
I´ve got a problem with my Samsung Galaxy S5
The History:
I bought a Samsung Galaxy S5 SM-G900f from Ebay with a Software Problem. The seller said, he try to flash a Custom Room like Cyanogenmod, he don´t know which)
The flash failed (i don´t know why). Now the S5 have a brick.
I tried so much, but i can´t repair it, pls help me.
The Problem is:
I can not start the Recovery Menü to flash a new Custom room. Always i tried to start the Menü, there is just a text "recovery Booting", then the phone restarts after round about 10 sec.
So even if i tried to start the S5 normally without recovery Menü, it´s just the Samsung Galaxy S5 Logo power by Android, then the phone restarts all the time.
The only thing i can do is start the download mode.
Things i tried:
- Firmware installation about Kies (pass, but still the Same Problem)
-Firmware Installation about Odin (pass, but still the same Problem)
- CF-Autoroot flashing (pass) then i tried to flash a recovery like PhilZ but then when i tried to open the recovery it`s "Recovery is not seandroid enforcing" Set Warranty bit
I tried so many firmwares but still the same Problem. Now it is installed Lollipop 5.0 G900FXXU1BOI3_G900FDBT1BOI1_G900FXXU1BOI3_HOME
There is no chance to repair it over ADB oder Fastboot, cause USB-debugging is disabled
Maybe you can help me and help me to stop spend all my time for this phone, cause im interested to know how i can repair it.
flash twrp from odin
then sideload a rom
install the rom
tell me if it works
.
I tried to install twrp 2.7.0.0-klte with odin. It´s pass, but when i tried to boot into Recovery he said "recovery is not seandroid enforce" Set Warranty bit: recovery
Pls help me i´ve got no idea more
Try this hold on (power volume up and home) then do not release until recovery mode boot
sh4dow6oy said:
flash twrp from odin
then sideload a rom
install the rom
tell me if it works
Click to expand...
Click to collapse
I tried to install twrp 2.7.0.0-klte with odin. It´s pass, but when i tried to boot into Recovery he said "recovery is not seandroid enforce" Set Warranty bit: recovery
Pls help me i´ve got no idea more
With some of the newer LP based firmwares, twrp 2.8.7.0 klte is the only version that works.....
Other than that, you might find it necessary to odin back to KitKat (flashing a pit file too) and try 'towelrooting' your device.......
BE WARNED.......If you *do* flash a pit file, make sure it's the CORRECT pit for your device.....In some cases, flashing the wrong pit will permanently kill a device.
http://i.imgur.com/rVnFwJM.jpg
So i had try it.
1.)hold on ( volume up and home) then do not release until recovery mode boot
--> The phone always restart no recovery is possible
2.) I try to install on LP the TWRP 2.8.7.0 Still the Same error "recovery is not seandroid enforce" Set Warranty bit: recovery
Before i root the device with CF-Autoroot and it´s pass
3.) I downgrade to 4.4.2 with a full package of Firmware with CSC,BL,AP,CP and a pit file.
The downgrade pass, when the phone starts it says recovery booting in blue script, then the phone restarts. I can´t intstall towelroot, cause the system is not booting, so i´d tried to install CF-Autoroot (pass) and then also the TWRP 2.7.0.0 pass but not booting and then 2.8.0.0.
But still the same "recovery is not seandroid enforce" Set Warranty bit: recovery
If you got a pass on your KK flash, you have a stock recovery......
Have you tried booting into that recovery and wiping cache and factory resetting? It is necessary to do this when downgrading......
http://i.imgur.com/rVnFwJM.jpg
Yes it was a KK stock recovery.
I tried to boot in this recovery, but when the phone starts it says recovery booting in blue script, then the phone restarts after a few seconds.
It´s not possible to wipe cache or make a factory reset, cause the recovery is not booting. That´s my problem. Also when i have flash the stock firmware i tried to go into the recovery but when the phone starts it says recovery booting in blue script, then the phone restarts after a few seconds. ( 4.4.2 and 5.0)
I´can´t flash a custom rom cause the recovery is not booting. I´ve no idea
Are you attempting the 3 button combination from powered off to get into recovery?........
@'detection' does the OP's situation sound familiar?.....
http://i.imgur.com/rVnFwJM.jpg
Very familiar -
https://dl.twrp.me/klte/
Flash TWRP 2.8.7.0 .TAR (Do not unzip) with ODIN 3.10.7 - in Download mode (Volume Down & Home & Power)
It will say "recovery is not seandroid enforce" Set Warranty bit" at the top when you boot into recovery, give it a few seconds and you should see the TWRP blue splash screen, and then recovery should load up
Then flash a custom ROM from TWRP
--
If that all still fails, try flashing the PIT file for the G900F along with a Stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract this one so it is .PIT, and add it to ODINs PIT section
If that still fails, try flashing just the PIT file with ODIN, and then the TWRP 2.8.7.0 with ODIN and see if you can get in that way
Or PIT and TWRP together
Try a combination until you get back in
Also try different versions of TWRP from 3.07 up to 3.10.7
keithross39 said:
Are you attempting the 3 button combination from powered off to get into recovery?........
@'detection' does the OP's situation sound familiar?.....
Yes i did, than the it happen what i wrote upside
What do you mean with "@'detection' does the OP's situation sound familiar?....."
Click to expand...
Click to collapse
It sounds familiar because it's happened to many other people recently too, although TWRP usually fixes it
Follow my instructions above
No chance guys,
i´d tried to install all TWRP which i found once in 5.0 and also i tried to install on 4.4.2. But always the same mistake. (recovery is not se.....)
Now i´ve tried to install CWM-Recovery and now there is no mistake like upside. Now in blue "recovery booting" and in yellow set warranty bit: recovery
But the recovery is not booting, the phone always make a restart. I´d also tried to install the recovery without auto-reboot in odin. But no help.
I don´t understand, cause when i flash a Stock Firmware, the recovery menu ,in my opinion, it have to start, but it doesn´t. Maybe i have anexpensive paper weight now
I search the internet to install a Custom room over Odin, but i don´t find any results, so i think it is not possible.
Do you have more ideas? Pls help. Thanks
I have the exact same problem, some are calling it the Black Screen of Death (with the blue led flicker). This is what happened to me:
0) had TWRP + latest 12.1 Cyanogenmod
1) installed the alpha 13 Cyanogenmod, which worked, more-or-less...
2) lost access to TWRP recovery, did not lose access to download
3) tried every single type of black magic from XDA (Kies, pit files, bootloader files, etc)
4) now it turns on, the LED turns blue and slowly, slowly flickers, but the screen is blank. At some point it plays the Samsung boot sound
Any help will be enormously appreciated.
check PM
bowzee said:
I have the exact same problem, some are calling it the Black Screen of Death (with the blue led flicker). This is what happened to me:
0) had TWRP + latest 12.1 Cyanogenmod
1) installed the alpha 13 Cyanogenmod, which worked, more-or-less...
2) lost access to TWRP recovery, did not lose access to download
3) tried every single type of black magic from XDA (Kies, pit files, bootloader files, etc)
4) now it turns on, the LED turns blue and slowly, slowly flickers, but the screen is blank. At some point it plays the Samsung boot sound
Any help will be enormously appreciated.
Click to expand...
Click to collapse
Another idea?
Joda899 said:
Another idea?
Click to expand...
Click to collapse
Ithink you should try re instal original firmware using odin and get ur warranty back then fix it on samsung
I found a trick that seems to help slightly, until an actual solution is published. During a misbehave episode, assuming that something shows up (which is not always the case):
1) press <power + home + vol-down> until the download thing shows up
2) press <up-arrow> so that it actually gets into download mode
3) press <power> until the screen turns off and immediately release (otherwise it will try to reboot); this makes it stay off
4) let it "rest" for a certain period of time (could be 5 minutes or more)
5) back to normal
Did u root your device vai CF auto root? Did it work?

Samsung Galaxy S5 SM-G900F 5.0 stuck during root

This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar
*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...
i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance
seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch
manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.
GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)
So I'm guessing no one knows the answer to my problem considering almost a moth has passed...
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too

i need emergency help to my constant recovery boot loop without any recovery mode.

hello, i think i just bricked my note 3. i accidentally boot the phone into the recovery mode on my sm-n9005 singapore lte version.
i downloaded this application called Quick Boot (Reboot) by GHCV on google play store. upon opening up the application and selecting the "Recovery" mode, it rebooted my phone into the recovery mode but there is a problem. it keep on saying: "Recovery is not SEandroid enforcing set warranty bit: recovery" and it constantly stuck in the recovery boot loop ever since then till now. my note 3 sm-9005 5.0 version is rooted by kingo root. i tried to install TWRP into my note 3 but failed, on the odin 10.7 it showed that it is successful but on my phone it doesn't even go into TWRP recovery mode. i tried these steps but all failed: pull out battery then press volume down, power button and home button for awhile then put in battery; boot it into download mode then press volume down to restart but still it brings me to recovery boot loop. i cannot even go and hardware reset my phone anymore. please help me i need my this phone urgently as this is my every day phone. i didnt flash CWM too as i ran out of time. please reply me as soon as possible to my email [email protected] thanks. urgently needed help.
mastermind_tan said:
hello, i think i just bricked my note 3. i accidentally boot the phone into the recovery mode on my sm-n9005 singapore lte version.
i downloaded this application called Quick Boot (Reboot) by GHCV on google play store. upon opening up the application and selecting the "Recovery" mode, it rebooted my phone into the recovery mode but there is a problem. it keep on saying: "Recovery is not SEandroid enforcing set warranty bit: recovery" and it constantly stuck in the recovery boot loop ever since then till now. my note 3 sm-9005 5.0 version is rooted by kingo root. i tried to install TWRP into my note 3 but failed, on the odin 10.7 it showed that it is successful but on my phone it doesn't even go into TWRP recovery mode. i tried these steps but all failed: pull out battery then press volume down, power button and home button for awhile then put in battery; boot it into download mode then press volume down to restart but still it brings me to recovery boot loop. i cannot even go and hardware reset my phone anymore. please help me i need my this phone urgently as this is my every day phone. i didnt flash CWM too as i ran out of time. please reply me as soon as possible to my email [email protected] thanks. urgently needed help.
Click to expand...
Click to collapse
Home-Volume Down-Power = Download Mode
Home-Volume Up - Power = Recovery Mode
You'll need to flash the Bootloader and Recovery. It may start up at this point. If not, then flash the Singapore ROM. You can extract the bootloader and recovery and then make them a .tar .md5 file for Odin. Read about it HERE. I've used it to recover my Canadian SM-N900W8 Note 3. All it would do was vibrate and boot loop. Now I'm 100% back up and running in Lollipop. Only use files for your version of the Note 3.
http://www.sammobile.com/firmwares/database/SM-N9005/
Singapore has 4 cell providers to choose from.
Or
you can try using Samsung Kies . Tools > Emergency Firmware Recovery. You'll need the serial # under your battery.
Or you just flash this one https://idlekernel.com/twrp/3.0.0-0/twrp-3.0.0-0-hlte.tar.md5 by Odin on the AP slot. If you really have a SM-N9005 like me (No other strange SM-N900* one!) this will work and fix your loop by updating the bricked recovery to the most recent TWRP one. Here is more information I'd recommend to at least read a bit of to at least understand a bit what you are installing by that: http://forum.xda-developers.com/showthread.php?t=2467001
ODIN 3.09 for ya: http://androidhost.org/PVAIv (using old crap 1.85 is NOT NEEDED)

Categories

Resources