hi guys,
i flashed recovery using the manual method from this thread http://forum.xda-developers.com/showthread.php?t=2468858.
I wasn't able to use the last command
Code:
rm /sdcard/g2_security
I thought it didn't work , i also updated the my phone software.
When my phone restarted it went to cwm and now its stuck there.
Now when I try to boot I can either get in CWM or some Korean Recovery Menu with three option (i tried all nothing happend) or just stuck in boot loop!
I can't get in download mode by pressing vol up and plugging usb cable (tried all possible methods)
I will be glad if someone can help me out.
Thanks in advance
That's an unexpected situation to say the least.
So in short: installation of recovery worked, but you lost access to your ROM.
Correct?
Now, if you had a flashable ROM on your sd card you would be sorted, no?
I would say, get any compatible ROM, put them on a micro sd card and plug them into your phone. Flash through cwm...
Am I misunderstanding?
Otherwise there is always the fully back to stock option:
http://forum.xda-developers.com/showthread.php?t=2475045
Zentac said:
That's an unexpected situation to say the least.
So in short: installation of recovery worked, but you lost access to your ROM.
Correct?
Now, if you had a flashable ROM on your sd card you would be sorted, no?
I would say, get any compatible ROM, put them on a micro sd card and plug them into your phone. Flash through cwm...
Am I misunderstanding?
Otherwise there is always the fully back to stock option:
http://forum.xda-developers.com/showthread.php?t=2475045
Click to expand...
Click to collapse
I was able to fix my phone using this thread. I was able to get in recovery but not in download mode. After executing these commands I flashed stock firmware through LG flashing tools.
aatish said:
hi guys,
i flashed recovery using the manual method from this thread http://forum.xda-developers.com/showthread.php?t=2468858.
I wasn't able to use the last command
Code:
rm /sdcard/g2_security
I thought it didn't work , i also updated the my phone software.
When my phone restarted it went to cwm and now its stuck there.
Now when I try to boot I can either get in CWM or some Korean Recovery Menu with three option (i tried all nothing happend) or just stuck in boot loop!
I can't get in download mode by pressing vol up and plugging usb cable (tried all possible methods)
I will be glad if someone can help me out.
Thanks in advance
Click to expand...
Click to collapse
The same exact thing happed to me. did u fix it, if yes can you please tell me how??
I have the same issue. Nothing mentioned in other threads is useful just because I CAN'T ENTER DOWNLOAD MODE. Totally stuck Help! Devs! Anyone!
Try installing some custom rom from recovery...after installing custom rom you can enter into download mode and do whatever u want...return to stock using kdz files or anything else..
Hi all,
I am not sure whether this the right forum to post my query. It's been a year a since I bought my S4 (i9500) so O thought of rooting and installing recovery on my phone. I was on stock 4.4.2 and I was able to root my phone using the CF-AUTOROOT, but after that when i am trying to flash a custom recovery using Odin it ends up in the download mode. I have disabled knox after rooting the phone and my phone status is now custom and so I cannot get any official update.Is there anything I did wrong which is forcing the download mode to overwrite the custom recovery I am tryjng to install???? Any help is highly appreciated.
Thank you,
Bobby Thomas.
Just boot into download mode. Uncheck auto-reboot in Odin and flash the recovery. That's it.
Thanks Lenny for your prompt reply, actually I did try that but after the manual boot it again goes back to the download mode instead of recovery mode....I even tried to install it through ADB shell but with no luck...I just goes to the download mode whatever I tried to do...
I was having a problem with the system trying to enforce the stock recovery every time I flashed TWRP through Odin. Turns out I got it by simply removing the battery as soon as Odin finished the job and restarted my phone. Waited for a few seconds, put battery back on and voila.
It worked for me. Do it at your own risk.
I also had the same trouble and had to untick auto-reboot, take out battery reboot back into download mode flash again. The first time I tried that it didnt work and the only way I got it to work was you Cyanogens windows installer, then went into recovery and flash the rom of choice.
What happens when you boot your phone, download terminal emulator from the market (or use adb) and type the following:
su
reboot recovery
I wanted to completely reformat my phone as my phone was buggy with Cyanogen Mod 12, so I formated everything.
The problem is that my PC was not detecting the drivers when in recovery mode, so I couldn't side-load with ADB, and I have no way of getting a .zip on to it.
I tried re-installing the clockwork mod using ODIN but it would just crash the application. I then tried heimdall and that said it installed it (I was hoping that it would fix adb)
Now I can't boot in to the clockwork mode recovery as it just instantly turns the phone off, however I can just boot normally in to the Galaxy S4 logo screen.
When I'm in the logo screen I do have access to ADB, however my phone is unathorised and I have no way to authorise it.
How can I A) fix clockwork recovery so it works again and B) put a zip on the phone or fix ADB detecting my device in recovery?
If you can get into download mode, flash a full stock ROM via Odin and start again
DSA said:
If you can get into download mode, flash a full stock ROM via Odin and start again
Click to expand...
Click to collapse
That worked great, thanks.
no probs, i find it to be a pretty good fall back in case of issues (just annoying reinstalling games etc..)
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
Today i tried to flash a rom. I flash twrp recovery through odin (latest). Went to twrp, flashed lineage os but forgot to factory reset the device. I end up with encryption unsuccessful with a option to reset phone (which i dont why i cant click it). Tried to go in download mode. Got into download mode but canoot use the volume up key. I have tried to get access with tge adb tge device doesnt show up in the listed devices. So please if anyone can help me.
Daydrea said:
Today i tried to flash a rom. I flash twrp recovery through odin (latest). Went to twrp, flashed lineage os but forgot to factory reset the device. I end up with encryption unsuccessful with a option to reset phone (which i dont why i cant click it). Tried to go in download mode. Got into download mode but canoot use the volume up key. I have tried to get access with tge adb tge device doesnt show up in the listed devices. So please if anyone can help me.
Click to expand...
Click to collapse
Go to twrp again,do a full wipe and reflash lineageos.