Related
Hi, I flashed this monday the leak of Lollipop for Samsung Galaxy S4 (9500) and after I followed all the steps one by one I'm the only one in earth that isn't able to start the phone in the recovery mode. For this reason I can't flash gapps. I am not able to downgrade even because for the KNOX.
Someone has the same problem? Can anyone figured out how to enter in recovery mode?
P.D: I have attempted to do it with the buttons (vol down + pow + home) and with adb and the usb connected to the phone. Anyone was the solution.
masicen said:
Hi, I flashed this monday the leak of Lollipop for Samsung Galaxy S4 (9500) and after I followed all the steps one by one I'm the only one in earth that isn't able to start the phone in the recovery mode. For this reason I can't flash gapps. I am not able to downgrade even because for the KNOX.
Someone has the same problem? Can anyone figured out how to enter in recovery mode?
P.D: I have attempted to do it with the buttons (vol down + pow + home) and with adb and the usb connected to the phone. Anyone was the solution.
Click to expand...
Click to collapse
after flashing Rom with Odin you have to flash openrecovery-twrp-2.8.4.0-klte.tar
Installing Recovery and rooting steps :
1- download twrp from here
2- go to flash mode
3- run Odin load file as AP then click start
4- go to recovery by powering off your device and hold volume up + home + power button
5- when you want to reboot to system Twrp will ask you to install SuperSU (rooting your device)
6- swipe to confirm
More info here
haririan said:
after flashing Rom with Odin you have to flash openrecovery-twrp-2.8.4.0-klte.tar
Installing Recovery and rooting steps :
1- download twrp from here
2- go to flash mode
3- run Odin load file as AP then click start
4- go to recovery by powering off your device and hold volume up + home + power button
5- when you want to reboot to system Twrp will ask you to install SuperSU (rooting your device)
6- swipe to confirm
More info here
Click to expand...
Click to collapse
I did all of this, still can't to initiate in recovery mode.
i had the same problem, try downloading philz (philz_touch_6.48.4-i9500) or twrp recovery (openrecovery-twrp-2.8.4.0-i9500) and install via odin (AP box)
I didn't try the above i just installed the rom again, doing this:
- only the AP file
- uncheck "auto reboot"
- After the process finishes dont reboot the phone to tw, just go to the recovery mode and the wipe cache/data
- Install philz or twrp via odin
dnnz said:
i had the same problem, try downloading philz (philz_touch_6.48.4-i9500) or twrp recovery (openrecovery-twrp-2.8.4.0-i9500) and install via odin (AP box)
I didn't try the above i just installed the rom again, doing this:
- only the AP file
- uncheck "auto reboot"
- After the process finishes dont reboot the phone to tw, just go to the recovery mode and the wipe cache/data
- Install philz or twrp via odin
Click to expand...
Click to collapse
So, flash the ROM again with nothing more than the AP box fullfiled and then, when it finishes hold (vol up + power + home). Wipe cache, restart and flash custom recovery.
Am I right?
masicen said:
.........................P.D: I have attempted to do it with the buttons (vol down + pow + home) and with adb and the usb connected to the phone. Anyone was the solution.
Click to expand...
Click to collapse
masicen said:
So, flash the ROM again with nothing more than the AP box fullfiled and then, when it finishes hold (vol up + power + home). Wipe cache, restart and flash custom recovery.
Am I right?
Click to expand...
Click to collapse
It can not, because in the first flash has deleted the modem, bootloader, csc and others, so if flashing only AP will not operate the phone, only the PDA.
And masicen these questions have to do in the same thread firmware also behold the solution.
Flashes the firmware again, to start turn it off and go into Recovery by: Volume Up + Home + Power in this order and holding down until you see the Samsung logo there S4 loose and enter the stock recovery, do wipes and restart it, then download Philz Touch in its latest version and flash it with Odin and restart turn it off and try to enter the recovery now.-
lobomarino said:
It can not, because in the first flash has deleted the modem, bootloader, csc and others, so if flashing only AP will not operate the phone, only the PDA.
And masicen these questions have to do in the same thread firmware also behold the solution.
Flashes the firmware again, to start turn it off and go into Recovery by: Volume Up + Home + Power in this order and holding down until you see the Samsung logo there S4 loose and enter the stock recovery, do wipes and restart it, then download Philz Touch in its latest version and flash it with Odin and restart turn it off and try to enter the recovery now.-
Click to expand...
Click to collapse
Hi, I wasn't able to test it before but now I had my computer and I did all that you suggested and could iniciate in the recovery mode but when I tried to flash gapps an error appeared (status 6) and now I can't manage to flash it :'(
Any solution to that??
p.d: thanks for your help.
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 have a Samsung Galaxy A8 (SM-A800I) but I tried to root by a kernel which is SM-A800F cause I didn't know , exactly I tried this kernel "SpaceX Kernel-0.1Auto Root A800F" . Now I stuck in boot loop, please help.
roni.bd said:
I have a Samsung Galaxy A8 (SM-A800I) but I tried to root by a kernel which is SM-A800F cause I didn't know , exactly I tried this kernel "SpaceX Kernel-0.1Auto Root A800F" . Now I stuck in boot loop, please help.
Click to expand...
Click to collapse
Flash Stock Firmware Image through Odin
http://www.sammobile.com/firmwares/database/SM-A800I/
Restart some 4 to 5 time it may come
---------- Post added at 03:56 PM ---------- Previous post was at 03:49 PM ----------
Because I have problem with spacex kernel on a800f
shubham540 said:
Flash Stock Firmware Image through Odin
http://www.sammobile.com/firmwares/database/SM-A800I/
Click to expand...
Click to collapse
if stock firmware flash failed (like what happened with me):
download and flash this stock boot.img and your device will be fine
https://www.dropbox.com/s/hyoaolar7lilpj2/boot.img?dl=0
Is xposed mod working on a00f???
Cwm 6.0.5.1. For a800f its working for me
http://forum.xda-developers.com/showthread.php?t=3282316
So I finally managed to root A800F 6.0.1 thanks to @rs1981
Link for TWRP: http://www.4shared.com/get/oUigxM-6ba/TWRP_302-0.html
Downloaded supersu from:
Http://viid.me/qqB1fh
1. Make sure usb debugging is on and oem unlock is on
2. copy supersu file into phone
3. Turn off phone and go into download mode (vol down+home+power)
4. Connect to pc and flash TWRP file via odine (make sure you untick autoreboot)
5. When flash passes unplug phone and hold (vol down+home+power) immediately once the screen turns black switch to (vol up+home+power) even if you see the red error keep holding and TWRP will open
6. Flash the Supersu file that you copied from TWRP and wipe delvik cache then reboot to system
Supersu should be installed and you should have root.
Thanks again @rs1981
Been trying to root A8 all day with no luck... It took me 10 mins using this way
guys please help me i dono what with my phone hanged on logo nd i even tired safe mode but its not working out
I also have the same problem mine is completely in boot loop and whatever combination keys i do all ending up in recovery mode no download mode. The problem started when i tried to remove the mdm samsung knox .Right now the only mode the phone can go is recovery mode, i can not access download mode.Any help please?
Hi Guys
please anyone help me. i think i have lost my phone.
after i had installed custom kernel i wanted to flash the stock boot. img file what extracted from ap.tar.md5
Now i have a phone what doesnt boot into recovery or system, only or in download mode.
When i want to flash the stock ap&bl&cp&csc file i have a message from odin: "fail" and it says deviceInfo.
Please help me if anyone can
thank you very much
Are you sure that you have the good stock files ?
And you have to flash your old kernel
NeoVander said:
Are you sure that you have the good stock files ?
And you have to flash your old kernel
Click to expand...
Click to collapse
Thanks.
But how to flash my ol kernel?
i can boot only on download mod.
odin always say: FAIL(DEVICEinfo)
Does odin fail when you start the process or after flashing ?
Try to find your stock kernel on internet
NeoVander said:
Does odin fail when you start the process or after flashing ?
Try to find your stock kernel on internet
Click to expand...
Click to collapse
It always fails before flashing process.
It seems to start the flashing method but after 4-5 second it says fail.
i didnt find any stock kernel to my nougat galaxy s7 edge.
i hope that i didnt destroy my phone totally.
You can't boot to twrp right ?
Because your kernel is on the "boot.img", you have to flash it.
---------- Post added at 10:10 AM ---------- Previous post was at 10:00 AM ----------
Maybe you can try this :
http://www.spflashtooldownload.com/2016/01/flash-stock-boot-MTK-android-sp-tool.html?m=1
NeoVander said:
You can't boot to twrp right ?
Because your kernel is on the "boot.img", you have to flash it.
---------- Post added at 10:10 AM ---------- Previous post was at 10:00 AM ----------
Maybe you can try this :
http://www.spflashtooldownload.com/2016/01/flash-stock-boot-MTK-android-sp-tool.html?m=1
Click to expand...
Click to collapse
I had the exact same problem and was having the same error even trying to flash stock form Odin.
Solution:
Restart Odin
Boot into TWRP
Boot back to Download mode but from TWRP not from the button combo
Flash stock ROM (available from Sammobile) through Odin
That worked and I didn't lose anything but of course it will overwrite TWRP.
DenisEhm said:
I had the exact same problem and was having the same error even trying to flash stock form Odin.
Solution:
Restart Odin
Boot into TWRP
Boot back to Download mode but from TWRP not from the button combo
Flash stock ROM (available from Sammobile) through Odin
That worked and I didn't lose anything but of course it will overwrite TWRP.
Click to expand...
Click to collapse
He cannot boot into TWRP
NeoVander said:
He cannot boot into TWRP
Click to expand...
Click to collapse
Ah yes ok I misread. I want to say it would work even if you went directly to download mode, but if it doesn't, I would try flashing TWRP again after killing all involved processes.
Solution here
https://www.sammobile.com/forum/showthread.php?t=38591
Code:
2) Boot into download mode by pressing ( power + volume down + Bixby button) and stop at the screen of continue and reboot.
Press volume down to restart phone
Quickly boot back into download mode by pressing (power + volume down + Bixby button)
Press continue
Congratulations fully working now
3) Install firmware with Odin
4) Wait for the firmware to be installed
5)Ready)))
Anyone with idea to restore imei. I have unknown imei error.
Hi everyone,
I am trying to root my device but I have had no luck!
I flash the TWRP with Odin and get a pass, but when I boot my phone into recovery mode to install SuperSu I am faced with the normal Android recovery mode.
I am running 5.1.1 Lollipop and have made no changes to the device.
Can anyone help?
Bump
Do not restart on the rom after the flash but on the recovery.
barjos12 said:
Hi everyone,
I am trying to root my device but I have had no luck!
I flash the TWRP with Odin and get a pass, but when I boot my phone into recovery mode to install SuperSu I am faced with the normal Android recovery mode.
I am running 5.1.1 Lollipop and have made no changes to the device.
Can anyone help?
Click to expand...
Click to collapse
djeman said:
Do not restart on the rom after the flash but on the recovery.
Click to expand...
Click to collapse
Hi there,
Sorry im quite new to all of this.
Do you mean untick auto-reboot on odin?
At reboot, after the recovery flash, you need to press "volume up+home+power" to reboot on the recovery.
If you uncheck auto-reboot you can reboot with "volume down+home+power" and when the screen goes off press "volume up+home+power".
So for my problem the solution is not to tick auto-reboot on odin right? I am highly confused
Disable auto reboot or you need to be faster to press buttons when the screen goes off ^^
If the stock rom boots it'll replace the recovery by the original, you need to accept a popup in the twrp recovery to lock this function.
I forgot to say, supersu is not the best software at the moment magisk is maybe a little better :
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
barjos12 said:
Hi everyone,
I am trying to root my device but I have had no luck!
I flash the TWRP with Odin and get a pass, but when I boot my phone into recovery mode to install SuperSu I am faced with the normal Android recovery mode.
I am running 5.1.1 Lollipop and have made no changes to the device.
Can anyone help?
Click to expand...
Click to collapse
Untick auto reboot, after flashing twrp pass then remove your battery from phone.
Plug in your battery and press power+volume up+home together to go to twrp and flash supersu or magisk