Database Users

Cannot enter recovery

My phone originally was using omega rom and philz recovery. I accidentally pressed the "remove recovery flash" while in philz recovery when I was trying to reboot the phone. My phone couldn't boot to os nor recovery, but download mode still works. So I tried to flash custom recovery again but it does not work. Tried flashing stock rom and kernel but recovery does not work. However, the phone is now able to boot to os but the screen color gone wrong. The whole screen is purple-ish when in os.
How can I get back recovery and also solve the purple problem?

Maybe try using a different recovery, at least to get back to stable? I've used TWRP and OUDHS via Odin, and both work well.

jejb said:
Maybe try using a different recovery, at least to get back to stable? I've used TWRP and OUDHS via Odin, and both work well.
Click to expand...
Click to collapse
Thanks alot! Finally able to enter recovery. Spent quite a long time trying to flash different roms etc.
Now trying to solve the purple problem....
Edit: Everything working fine now.

[Troubleshoot] Unable to into Recovery

Hey Guys,
I just rooted my i9505 via CF-Auto-Root and it worked like a charm. The next thing I did was to flash Philz Recovery, at first it auto reboot and it never went into recovery, so I followed the steps to re-flash it without the auto reboot and force it into recover. It loaded into Philz Recovery perfectly fine, now when I reboot, it gave me the option to disable auto flash recovery, so I selected yes.
After that I was never able to get into Recovery Mode ever again. All it does is says Recovery Booting in the top left corner and then restarts and loads into the OS. I followed the steps again to re-flash Philz with auto reboot unchecked and it still failed to get into recover. I then tried CWM and TWRP (via Odin), but all of these gave me the same problem and failed to get into recover.
I then tried SGS4 Flasher but still the same question.
Anyone here who has this problem before and know the fix or is able to recommend another method?

Was able to fix it. Had to flash the original stock Recovery back on and then re-flash a custom recovery. Not sure what happen but was able to install TWRP on without an issue, maybe something in Philz Recovery that stuffed it up.

OK! Looks like it is not working correctly. For me to get access to a custom recovery, I have to flash the stock recovery via Odin and then flash a custom recovery to get it working EVERYTIME. It will boot into Philz, CWM and TWRP only once, then you need to flash stock recovery and do the process all over again.
So it looks like the recovery gets over written each time even if you select "yes - disable flash recovery" in Philz Recovery. Anyone know of another way to disable flash recovery?

Z-Blade said:
OK! Looks like it is not working correctly. For me to get access to a custom recovery, I have to flash the stock recovery via Odin and then flash a custom recovery to get it working EVERYTIME. It will boot into Philz, CWM and TWRP only once, then you need to flash stock recovery and do the process all over again.
So it looks like the recovery gets over written each time even if you select "yes - disable flash recovery" in Philz Recovery. Anyone know of another way to disable flash recovery?
Click to expand...
Click to collapse
with a root explorer, go to system/recovery-from-boot.p and rename it to recovery-from-boot.p.bak

samersh72 said:
with a root explorer, go to system/recovery-from-boot.p and rename it to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Thanks for responding samersh. To lessen the pain of constantly flashing the recovery via Odin on my PC, I bought Mobile Odin Pro. However, it looks like when I flashed using Mobile Odin Pro, it fixed my issue.
I checked \System\ and there was no recovery-from-boot.p there. So it is confirmation that this has been fixed. Thanks again for responding.

I've got a soft brick going on

OK, I've had my S4 a couple months. It's already been rooted, with TWRP installed and also MDOB custom ROM. But tonight I decided to replace TWRP recovery with CWM then I was going to flash CM 10.2. after flashing CWM I now have the yellow triangle and a message saying "system software not authorized by AT&T has been found on your phone" and the phone won't boot nor recovery is working. With no recovery I can't reflash the current ROM i had installed, I have the MDOB file on my memory card ready to reflash, but the phone won't do nothing. What to do now?

Can you get into download mode by pressing home, power, and volume down at the same time while booting up? If so, you could use this guide I've had success with. http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

I had a similar issue were I flashed philz recovery and it wasn't the loki'd zip.I to had the triangle of death with unauthorized ATT msg, I tried three times to boot into recovery and the last time I tried it went to (pic posted)and from there I pushed down for restart phone.it booted up like a regular reboot and was OK.
Also after it booted I lost custom recovery, so like I did the first time I achieved recovery I flashed with ROM manager clicking the T-Mobile S4 when prompted. Note : only use ROM manager to flash recovery.now use recovery to flash a auto Loki recovery. Hit thanks if I helped
Sent from my GT-I9505 using xda premium

[Q] Root Problems

I'm having a strange time with my phone, I rooted the phone, by the guides on xda, everything went well, superSu was installed,
then I tried to flash a new recovery and a new kernel, but nothing worked, after some searching I found this AutoRec tool, it worked
the recovery changed to TWRP, so I tried to flash dorimanx again, and again nothing changed, the flashing was done, but after reboot still
no change with the kernel.
So I checked if the device is rooted, I did this on the begining of the process and it was, now, it showed that the device isn;t rooted.
Now I have a TWRP recovery, without root, and when I try to root, I have to press "apply update from adb..." but I dont have thing option anymore,
Thanks a lot for your help!

maxwellz said:
I'm having a strange time with my phone, I rooted the phone, by the guides on xda, everything went well, superSu was installed,
then I tried to flash a new recovery and a new kernel, but nothing worked, after some searching I found this AutoRec tool, it worked
the recovery changed to TWRP, so I tried to flash dorimanx again, and again nothing changed, the flashing was done, but after reboot still
no change with the kernel.
So I checked if the device is rooted, I did this on the begining of the process and it was, now, it showed that the device isn;t rooted.
Now I have a TWRP recovery, without root, and when I try to root, I have to press "apply update from adb..." but I dont have thing option anymore,
Thanks a lot for your help!
Click to expand...
Click to collapse
You can still root with custom recovery the difference is you need to go to advanced and sideload to be able to apply the root.zip, you can also look for the flashable supersu.zip and flash it from recovery and that will root your device
Sent from my LG-D800 using XDA Premium 4 mobile app

Thanks for your reply, I gained back the root.
Downloaded from PlayStore some app called Rebooted - went to recovery [TWRP if it has any influence] and flashed Dorimanx kernel,
the flashing is over, but nothing new... it just doesnt install nothing... so strange..

Anyone please?

maxwellz said:
Anyone please?
Click to expand...
Click to collapse
I suggest you start over. Not sure if you performed wipes(wipe all except internal).
But
1. flash kdz
2. root
3. autorec
4. wipe wipe wipe(except internal)
5. install
6. profit

From CynogenMod to WanamLite - Help me get there!

Hi,
I'm currently running CyanogenMod KitKat version with ClockWorkMod. Since the rom has several bugs and for the past few months they haven't published any updates to my Galaxy s4 I9505, I've decided to switch to WanamLite.
There I found out I need TWRP recovery so I went ahead and downloaded GooManager which installed an outdated version, as I've found out.
I tried wiping my internal storage as recommended but the recovery couldn't mount any of my partitions.
So now CyanogenMod won't boot. I know this issue is fixed in the updated version of TWRP but I'm not sure how to update it without the phone booting (Odin perhaps? It doesn't recognize it currently... Should I move to download mode for it to be detected?)
Anyways, I'm kind of stuck as of now. Any help would be very much appreciated!
Btw I have a question, what's the difference between using Odin 1.85 and 3.09? Why do people still use the old version?
Thanks in advance!!
Neta
Edit:
Alright, now I can't get into recovery either. When I try, I can see the Samsung logo and there's "recovery" written in the top left but then it just restarts again into the same logo without "recovery". I'm starting to lose my cool now. Anyone have any ideas?

Try flashing latest stock through download mode and see if it boots.
Sent from my GT-I9506 using Tapatalk

Flash this recovery through odin. It's TWRP 2.6.3.1. Worked alwys for me.:fingers-crossed:
https://db.tt/SwLvOrZl

Uncheck auto-reboot in Odin.

Thank guys
I got freaked out and just did everything I could to make the phone working again.
I found a thread on XDA explaining how to return your phone to stock version, so I followed it, rooted with auto root, (btw Odin didn't recognize my phone because I used the front usb... how annoying!), then flashed the latest TWRP (2.7.0.1, not 2.6.x.x as GooManager downloaded for me), then booted to recovery and flashed WanamLite.
Everything is working now!
Except one thing - I'm still not able to access recovery mode through physical buttons, only using boot apps. Is this a kernel issue?
Could be some incompatibility since CyanogenMod uses it's own kernel and CWM recovery.
The recovery itself is working fine, but when I try to access it using buttons it shows the Samsung logo with the recovery on the top left, and then reboots again to normal boot.
What do you think?
Thanks!