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!
Related
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.
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
Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!
So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?
You'll probably have to Odin back to stock and start over...
Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?
Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!
No problem. Glad you got it figured out!
[emoji106]
I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
Update: I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.
I recently picked up my old note 3 and wanted to use it as a gps for my car, but when i tried to start it i noticed it still had some weird rom form a few years back installed. So i went to sammobile to grab the newest official rom and flashed it with odin. That is when the trouble started.
Odin stated that the flashing proces was successful but when it automatically rebooted i was given an unpleasant surprise.
My good old phone kept rebooting to the samsung galaxy note3 logo with the text the top left which stated: "recovery booting....".
My first instinct was that i had to go to the recovery to format cache and data, but the problem was that the recovery wasn't reachable.
So installed twrp 3.1.1.0 which I've used before, but still no luck after doing a factory wipe.
After all of this i've never been able to enter the stock recovery, even after again re-flashing the stock rom.
does anyone have an idea how to fix this.
Search multiple identical posts.
Suggest older 2.8 TWRP.
I inded find some older posts, but none of them discribe this problem. I tried to use twrp 2.8.7 amd that will give me a recovery to work with. But it still won't boot afterwords.
I can flash the older 4.4.3 firmware and it will boot with no problems. But when i try to update it with a newer version, it gets stuck again
Its probably a bootloader problem .
Phone Info from playstore and post bootlader etc.