Related
So i rooted my Samsung Galaxy s4 today, and i was told by my friend to use clockworkmods recovery before i start using custom roms. Since there was no option for a gt-i905 on there, i went to the internet and i found a .tar file that had gt-i905 compatibility. SO, through the amazing power of odin, i went into download mode and "installed" clockworkmods. According to odin, it was successful. According to my phone it was not. IT couldnt boot in to recovery and it always went back into download mode saying that it could not boot properly and that it was in odin mode. So pulled the battery out and went back in to download mode and instead of volume up, i pressed volume down to restart the phone. The turned back on normally.BUT, everytime i attempt to go back into recovery, it shoves me back into download mode. I have no idea what i did and i would like to know if there was anyway of fixing such problem?
Thanks
LVURFR3NZ said:
So i rooted my Samsung Galaxy s4 today, and i was told by my friend to use clockworkmods recovery before i start using custom roms. Since there was no option for a gt-i905 on there, i went to the internet and i found a .tar file that had a way to restore the nand and flash? compatibility. SO, through the amazing power of odin, i went into download mode and "installed" clockworkmods. According to odin, it was successful. According to my phone it was not. IT couldnt boot in to recovery and it always went back into download mode saying that it could not boot properly and that it was in odin mode. So pulled the battery out and went back in to download mode and instead of volume up, i pressed volume down to restart the phone. The turned back on normally.BUT, everytime i attempt to go back into recovery, it shoves me back into download mode. I have no idea what i did and i would like to know if there was anyway of fixing such problem?
Thanks
Click to expand...
Click to collapse
Hi mate ,
I guess is a mistype( gt-i905) what model do you have?
Try flashing Philz touch recovery or TWRP
LVURFR3NZ said:
So i rooted my Samsung Galaxy s4 today, and i was told by my friend to use clockworkmods recovery before i start using custom roms. Since there was no option for a gt-i905 on there, i went to the internet and i found a .tar file that had gt-i905 compatibility. SO, through the amazing power of odin, i went into download mode and "installed" clockworkmods. According to odin, it was successful. According to my phone it was not. IT couldnt boot in to recovery and it always went back into download mode saying that it could not boot properly and that it was in odin mode. So pulled the battery out and went back in to download mode and instead of volume up, i pressed volume down to restart the phone. The turned back on normally.BUT, everytime i attempt to go back into recovery, it shoves me back into download mode. I have no idea what i did and i would like to know if there was anyway of fixing such problem?
Thanks
Click to expand...
Click to collapse
Very easy to Fix it...
If you are rooted install Mobile odin, search on XDA not on Google in S4 I9505 section For a Recovery...
Download it (Make sure it is the right file)
Put it in Odin and just press flash...
Enjoy...
If there is a Problem check your device and flash the stock firmware from Samsung and then Flash again the recovery....
Hit thanks if i helped...
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
Model: SM-G900P
I've tried every kind of rom flashing here, re-partitioning, recovery images, etc.
I really just want to get to the stock recovery mode with out the auto boot loop.
Please help.
What else do you need to know?
Try flashing TWRP 2.8.7.0 with ODIN, and boot into TWRP recovery
If you can get into TWRP, you have a very powerful recovery with a lot more options than stock, to try and get things working again before going back to 100% stock - if that's what you're aiming for
*Detection* said:
Try flashing TWRP 2.8.7.0 with ODIN, and boot into TWRP recovery
If you can get into TWRP, you have a very powerful recovery with a lot more options than stock, to try and get things working again before going back to 100% stock - if that's what you're aiming for
Click to expand...
Click to collapse
The flash seem to work via ODIN. See image below.
But it is still stuck in a boot loop for normal booting or for recovery mode.
Am I using Odin incorrectly??
url to screenshot: pasteboard.co/1jlllhvK.png
xojgiiox said:
The flash seem to work via ODIN. See image below.
But it is still stuck in a boot loop for normal booting or for recovery mode.
Am I using Odin incorrectly??
url to screenshot: pasteboard.co/1jlllhvK.png
Click to expand...
Click to collapse
A lot of newer S5s do the same thing (Except they usually boot back into stock recovery, but as yours isn't working, same thing)
Follow this guide (Using the correct version TWRP for your model S5)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
You can ignore steps that are not relevant to flashing TWRP, or follow them all for a rooted phone (Apart from reactivation lock as you can't boot yet)
*Detection* said:
A lot of newer S5s do the same thing (Except they usually boot back into stock recovery, but as yours isn't working, same thing)
Follow this guide (Using the correct version TWRP for your model S5)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
You can ignore steps that are not relevant to flashing TWRP, or follow them all for a rooted phone (Apart from reactivation lock as you can't boot yet)
Click to expand...
Click to collapse
I followed these steps:
"3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)"
Although, they were not very specific....
To flash with odin, I used the AP button and did not let it auto reboot. Removed battery immediately. tried to reboot in recovery and saw the same issue.
I think I need all files.
BL
AP
CP
CSC
and possibly to re-partition with a PIT file
You say in the first post you have already repartitioned?
PIT file is for repartitioning
http://forum.xda-developers.com/attachment.php?attachmentid=2799613&d=1402839135
Extract to .pit, add to PIT section in ODIN, add ROM to AP section, flash both together
You can try older versions of ODIN for TWRP to, some people have success with version starting 3.07 > 3.10.7
I was able to do the PIT and the TWRP at the same time.
Although, my phone said "SECURE CHECK FAIL : pit" on the screen, it seemed to do everything.
But upon reboot to try to get to Recovery (power, home, Vol+), it no longer waits and reboots/recycles. It fails with a message that says "Could not do normal boot." and send me to Download mode.....
If I try to boot normally, I still get the boot loop....
I just used the PIT file I used last time and it's back to where I was when I started this post.
Endless reboot cycle...
Maybe the bootloader needs to be flashed?
Ok. My issue with the failing pit (and any other failures from Odin) was a combination of using a bad version of Odin or a bad version of the tar or pit files.
I am able to flash the latest stock rom g900p OK4 just fine.
I can flash twrp just fine as well.
But the boot loop cycle still remains.
I believe I know exactly what I need here and it's the stock OK4 boot loader.
Here's an Odin flashable OK4 bootloader for the G900P. https://mega.nz/#!9ItUDZ7C
InsanePostman said:
Here's an Odin flashable OK4 bootloader for the G900P. https://mega.nz/#!9ItUDZ7C
Click to expand...
Click to collapse
This link needs a decryption key
xojgiiox said:
This link needs a decryption key
Click to expand...
Click to collapse
**** okay. I'll relink with key once i get to my computer
Here you go. https://mega.nz/#!9ItUDZ7C!MxiO87vn7KBiy4ZLtDFx-AoahYPftyf3985nOXenPig
Bootloader file was exactly what I was asking for. Thanks.
However, it did not solve the problem.
Boot loop cycle going on still after stock BL, Ap, PIT all flashed....
Any other suggestions ???? Please. From anyone?
I'm sorry to write in this old topic, but I want to know if you solved your problem, as I'm having the same trouble. Everytime I turn on the phone it stucks on bootloop, and after 5 to 10 cycles it starts. When trying to enter to Recovery it stucks on bootloop and never enters. I've tried with TWRP or Philz CWM but it just doesn't enter to recovery :'(
So, i tried to flash twrp on my galaxy a40 through odin, i did it step by step as it should be done, odin said pass, but it didnt. I rebooted, and it immediately booted into download mode, again and again, whenever i tried to reboot. I tried everything i know i could try, but nothing works. Is there any way to get the twrp on it? Thanks.
Have you enabled USB debugging and OEM unlocked the phone (in the settings)?
What phone do you have? You need to flash original rom via odin. I think that your phone is bricked.
it often happens quiet it can be solved very simply by installing the patched Vendor if you want I can send you the vendor that you will have to flash it with odin and then restart the phone and return to download mode and flash TWRP from the official website
Alexmalek836316 said:
So, i tried to flash twrp on my galaxy a40 through odin, i did it step by step as it should be done, odin said pass, but it didnt. I rebooted, and it immediately booted into download mode, again and again, whenever i tried to reboot. I tried everything i know i could try, but nothing works. Is there any way to get the twrp on it? Thanks.
Click to expand...
Click to collapse
have you installed vbmeta?
the phone behaves similarly without vbmeta installed.
.
Hi there. I know this question has been posted but none of the solutions is working for me.
I flashed official ROM using Odin on my S8 950FD. The process was smooth, the phone rebooted, installed update (blue screen), erased, rebooted again and then stuck on logo. I waited for a long time, then pressed Power + Vol down buttons. As soon as it turned off, I pressed Power + Bixby + Vol up. I was in stock recovery. Wiped cache and data, rebooted again, same result.
I went to download mode again, my KG state was showing Prenormal. I tried flashing TWRP, OFRP recoveries but of course got Official Binaries blah blah error. I tried flashing stock firmware again and again but no luck. All I can see on my phone is either Samsung Galaxy S8 or I can go to recovery or download mode. The phone will never boot.
I tried Miracle Box 2.82 cracked version as well, but still no luck, it shows PACKET SIZE TOO BIG or something like that.
Any chance I can get my phone working and alive again??
shoaibahmad121 said:
Hi there. I know this question has been posted but none of the solutions is working for me.
I flashed official ROM using Odin on my S8 950FD. The process was smooth, the phone rebooted, installed update (blue screen), erased, rebooted again and then stuck on logo. I waited for a long time, then pressed Power + Vol down buttons. As soon as it turned off, I pressed Power + Bixby + Vol up. I was in stock recovery. Wiped cache and data, rebooted again, same result.
I went to download mode again, my KG state was showing Prenormal. I tried flashing TWRP, OFRP recoveries but of course got Official Binaries blah blah error. I tried flashing stock firmware again and again but no luck. All I can see on my phone is either Samsung Galaxy S8 or I can go to recovery or download mode. The phone will never boot.
I tried Miracle Box 2.82 cracked version as well, but still no luck, it shows PACKET SIZE TOO BIG or something like that.
Any chance I can get my phone working and alive again??
Click to expand...
Click to collapse
What you want to do is flash full latest stock firmware for G950F (yes even tho you have fd, they are same exact device and share fw) with CSC and not HOME_CSC together with AP, BL and CP files, you can find latest firmware on samfw.com they dont have download speed limit or you can use tools that can be found here on xda for downloading samsungs latest fw.
using CSC will format device and return it to factory state
I have already done that, grabbed firmwarre from SamFW G950FXXUCDVG4 as this was what written in my Settings, VG4. I flashed AP, CP, BL and CSC using Odin in my windows and when it didn't work, did it from JOdin3 from my Mac. Nothing changed after several tries.
Any help? Did I trip the knox? The last time it happened to me, I flashed TWRP recovery and wiped/repaired file system and it worked. This time, I am unable to install unofficial binaries.
Update: I downloaded combination fw and flashed it but no luck. One thing I observed in stock recovery that it says DM-VERITY VERIFICATION FAILED. Could this be the issue? How to resolve this?