I9505 rooted but cant install custom recovery - Galaxy S 4 Q&A, Help & Troubleshooting

EDIT: Sorted it, flashed TWRP in odin and it worked this time.
I have rooted my i9505 (5.0.1 stock Baseband i9505XXUHOD5) using CF-auto and Odin but I cant install a custom recovery. When I try in odin it says pass but then gets stuck in a loop at reboot. When i go to recovery its still stock and the only way out of the loop is to factory reset abd then try again. It looks like a Vodaphone Germany rom thats been unlocked installed. Any ideas please? I want a custom rom to get rid of the Samsung crap in the background.

Thread can be closed
As you have solved it,like this you open this thread for nothing
And also, CWM and Philz are outdated and out of support(only for this device), always use TWRP[emoji6]
Sent from my GT-I9505 using Tapatalk

Related

Recovery Issues At&t S4

Alright I have searched all day and can not seem to find a resolution to my problem. It is my fault I shouldn't fix something that isn't broke but it has resulted in issues and I would appreciate it if someone could help me.
I had twrp 2.5.0.2 installed running GE 4.2.2 ROM with MF3 radios installed and GE kernel v11. I saw twrp had a update to 2.6.0.0 and I decided to install it via goo manager it booted up in recovery with the "the software is unauthorized by att" screen and I can do volume down + power after that to reboot phone and not have issues as far as getting my phone booted and working on all the above. But the problem I am having now I have lost custom recovery. I have tried goo manger again as well as some on click root/recovery methods from these forums and all result in the same back to the unauthorized screen mentioned above its like it won't boot into a custom recovery. Any advice is greatly appreciated.
Sent from my Nexus 7 using xda app-developers app
Maybe try ROM manager and install cwm .it will pop up in ROM manager as the T-Mobile s4 but that's what I used to install the first recovery image,then I used that recovery to flash the auto Loki recovery.I have used the same plain auto Loki recovery since then.
Sent from my SAMSUNG-SGH-I337 using xda premium
Just tried that as well. Still not working. When I takes me to that unauthorized page top left it says "secure fail: kernel". But when I reboot the phone normal it comes up just fine....so that tells me its getting past with Loki to boot up my ROM and kernel but for some reason it will not take a custom recovery anymore when I have had one installed previously.
Sent from my SGH-I337 using xda app-developers app
If memory serves me right the Google Edition ROM will make TWRP / GooMananger think you have a 9505(G) and thus it will install that version. So you installed a non-loki'd recovery.
Use Odin, go back to AMDL firmware. (Take SIM out before doing so so it wont download the AMF3 update). Redo Root + Recovery. BEFORE you flash another rom, install GooManager and then update from there. You will be running stock firmware so it will identify the model correctly. Then flash your custom ROM.
Forgive me for being noob when it comes to Odin. But does this OTA the software or will I need to get Odin on my desktop?
Sent from my SGH-I337 using xda app-developers app

[Q] unable to install Gapps after installing latest 4.4.2 firmware

Hi there,
Long time lurker on the forums here, and have been browsing around the whole day to find a solution to my problems without luck .
Yeasterday I received my Galaxy Note 3 (N900T), but I had very poor reception, I thought this was because the N900T was appearantly a US model which I wasn't aware of, but since hardware was the same I decided a custom rom might fix things up.
I installed the latest CM 11 nightly and appropriate google apps but without any luck (reception still bad)
Then I decided to install the origional 4.4.2 firmware for T-mobile N900T, now the reception and everything works just fine, but I get a bunch of errors that google app x (youtube, playstore etc) have stopped working, so I get alot of these pop-ups and can't use the playstore.
I thought: Ok I just need to install the latest Gapps for the 4.4.2 version, there's where the problem comes in. When I booted into recovery it would boot into the standard android recovery and not CWM recovery. I couldn't do anything in the normal recovery mode to install gapps. So I managed to download the rom manager through my browser and just installed that without the playstore, after this i installed the recovery, found out my root was undone after the patch.
I then downloaded the chainfire thingy and flashed it with odin, which all worked fine and I managed to root my phone again. When opening SuperSU it says there was some 'KNOX thingies remaining which I said ok take away. After this I installed the CWM recovery, and said: Launch ClockworkMod recovery so I could install the new version of Gapps there. However: This is where it gets stuck in a loop trying to launch the bootloader, and I was unable to get into the bootloader. The only way to stop the bootloader loop was to take out the battery, boot into download mode and cancel the download mode after which my phone would continue to boot normally.
After this I tried to flash the 4.3 version of android with odin, and even reflashing the current 4.4.2 version, but I can't flash any roms with odin anymore as it gives me the Fail! Auth. error everytime in odin.
If anybody could help me that would be greatly appreciated!
Just to clarify:
I am still working on this, I downloaded Goomanager and installed TWRP recovery, but no luck, my phone will simply get stuck in a loop when i try to boot it into recovery. I can still startup my phone normally, but it's quite useless without gapps.
Thanks in advance for any assistance, I really feel lost on this one :/
Maybe its too late but I wonder if it would have helped if you install another kernel when you had CM11. Maybe that would have had solve the problems with the reception? I'm a total noob at this, so I don't know, its just something that I thought of.
grafgever said:
Just to clarify:
I am still working on this, I downloaded Goomanager and installed TWRP recovery, but no luck, my phone will simply get stuck in a loop when i try to boot it into recovery. I can still startup my phone normally, but it's quite useless without gapps.
Thanks in advance for any assistance, I really feel lost on this one :/
Click to expand...
Click to collapse
Not sure but when i upgraded my N9006 to KitKat and tried to root it using cf-auto-root for my phone it went into a boot loop. I ended up using the one designed for N9005 as it specifically stated it was made for the 4.4 boot loader. I'm guessing the other ones are for 4.3?
locn said:
Not sure but when i upgraded my N9006 to KitKat and tried to root it using cf-auto-root for my phone it went into a boot loop. I ended up using the one designed for N9005 as it specifically stated it was made for the 4.4 boot loader. I'm guessing the other ones are for 4.3?
Click to expand...
Click to collapse
I managed to flash the philz recovery with odin, I got the phone working now, except when I make a call I'll loose all mobile network signal afterwards. Unsure how to solve this. Could I flash a European stock firmware to my n900t?

Galaxy S4 bricked?

Hey guys,
I got jamals google edition installed on my S4 and when I forgot to charge it and I started the device I got a bootloop. I dont know why, but I also couldĀ“t get into the recovery mode, so I flashed an originial Samsung firmwar via Odin on my S4 (4.4.2)
After that, it restarted but I got a "android.process.acore has stopped" message and I couldn't use the S4 because the message kept popping up and the S4 automatically restarted and when it restarted the message appeared again, so i had a very strange loop i couldnt interrupt. So i flashed another 4.4.2 firmware and also again the same firmware, but nothing helped, I still got the message and the S4 kept restarting.
So I flashed the Omega Pre-rooted 4.4.2 firmware via odin (and the exact same thing happened). But whats strange is, that before it started it said "updating 1 of 172 apps) so that must mean, that even though I flashed 3 firmwares via Odin, my apps somehow stayed on the S4? And also the wallpaper was the same wallpaper I had before, what was very strange.
Then I installed Philz CWM Recovery because I waned to perform a factory reset. But after I installed it and tried to get into recovery mode, I couldn't and only this was displayed :
Recovery Booting...
Recovery is not Seandroid Enforcing
Set Warranty Bit: recovery
So it seems like nothing works and I'm getting really desperate, does anyone of you has an idea how to fix this? Otherwise I guess my S4 is bricked
Regards and thanks for your help
Flash latest firmware via odin with auto reboot option unchecked and before u boot into os simply open stock recovery and perform a factory reset.. hope it will help u..
Sent from my GT-I9500
coolkoushik07 said:
Flash latest firmware via odin with auto reboot option unchecked and before u boot into os simply open stock recovery and perform a factory reset.. hope it will help u..
Sent from my GT-I9500
Click to expand...
Click to collapse
Thx, I'll give it a try! Could you maybe tell me, where I get the latest firmware?
coolkoushik07 said:
Flash latest firmware via odin with auto reboot option unchecked and before u boot into os simply open stock recovery and perform a factory reset.. hope it will help u..
Sent from my GT-I9500
Click to expand...
Click to collapse
Thx man it worked :good:
thomas333 said:
Thx man it worked :good:
Click to expand...
Click to collapse
Glad to know that it worked...
Sent from my GT-I9500
I'm assuming you know about KNOX now that you've flashed an official firmware you will have KNOX and you've already tripped KNOX by installing recovery but you won't be able to use a lower version firmware just bare that in mind when flashing official stock again.
Sent from my GT-I9505G using Tapatalk

[Q] Unable to install Custom Recovery

Hello,
I am facing weird problem, I am not able to install custom recovery, I have tried almost everything.. nothing helped.
I am still getting stock recovery..I have tried to flash it via Odin, via some apps, unfortunatelly nothing worked.
My Samsung Galaxy S4 i9505 is running KK 4.4.2.
Any idea?
Thank you.
I had this problem too. keep flashing cwm recovery through the app (needs root I think). and reboot into recovery, once you get cwm you can flash a custom rom or another recovery like twpr or philz.
s4 i9505 stock KK
I have that problem too. I have stock KK 4.4.2 XXUGNG8 updatet ota. When i try to flash flashable zip file cwm of philz or twpr i get some error like:
E:footer bad
Mds check
Something like that and cant flash it. I tryed with odin but no luck. Does anyone have same problem?
I had this problem to
I fixed it by checking te root options.
If u use a root app, make sure it gives always root acces.
After this, install a custom recovery rom
After that you'll have no problem installing a custom ROM
Good luck.
Xehk said:
I had this problem to
I fixed it by checking te root options.
If u use a root app, make sure it gives always root acces.
After this, install a custom recovery rom
After that you'll have no problem installing a custom ROM
Good luck.
Click to expand...
Click to collapse
But my phone is not rooted, its new, with stock recovery, knox 0x0 still....
Have any idea?
Ok, but what if my phone is not rooted, how am I supposed to root it? When I tried CF-Auto-Root my phone started to reboot randomly during the phone call.
I have found one solution, but I am not sure if it works, it says that if you are flashing custom recovery via odin, you have to take out the battery after the flash is done so you won't allow your phone to restart and rewrite the recovery back to stock. Have anyone heard about it?
No, no idea.
Thats crappy.
Only know how I fixed it
icefun said:
I have found one solution, but I am not sure if it works, it says that if you are flashing custom recovery via odin, you have to take out the battery after the flash is done so you won't allow your phone to restart and rewrite the recovery back to stock. Have anyone heard about it?
Click to expand...
Click to collapse
Just uncheck auto-reboot before you flash the recovery. That will fix your problem.
I have tried it, but it didn't help still looking for solution, is there any way how to RENAME RECOVERY RESTORE FILES so I can finally flash custom recovery? (non-rooted phone)
OK, so the solution that worked was simple and I have already mentioned it, you have to take out you battery on samsung galaxy s4 logo, before it reboots.
My solution
Hi I had the same problem too,
I solved it this way: (My phone was rooted)
Download the .zip file from the recovery you want (I used CWM 6.0.4.7)
Next download 'SGS4 flasher' from the playstore.
SGS4 flasher needs root (I think) andyou can flash your recovery through that app.
Next boot into the recovery and you should probably end up in your custom revovery every time now.
If you don't end up in your custom recovery, download ROM manager and then choose the option boot into recovery.
This worked for me at least :laugh:

SM-G900S bootloop after trying to root

Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet

Categories

Resources