Hi all
I have a really weird problem with an S5 SM-G900F. I am trying to install to it via Odin a recovery and also root the phone.
I have used various versions of Odin.
The issue is that Odin works fine - we get the phone detected, we install the image, the green status appears and the phone reboots.
When the phone reboots, it doesn't do any installing - it just reboots back into the old rom.
I've Googled for ages and can't find out what the reason is for this problem.
Basically, Odin seems to work, but it's as if the image isn't booted, or written to the phone.
Not sure what else to do. I have tried running the same TWRP and root install to another S5 with no problems. Can someone help?
thanks in advance
scatat said:
Hi all
I have a really weird problem with an S5 SM-G900F. I am trying to install to it via Odin a recovery and also root the phone.
Click to expand...
Click to collapse
When we install a custom recovery, and when we root a phone the ROM doesn't change.
I've found a post at last which helped the issue. It is ongoing as whenever I boot the phone normally, my custom recovery is overwritten.
http://forums.androidcentral.com/sa...s/523843-odin-says-pass-but-doesn-t-work.html
Related
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?
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:
So I have a galaxys s5 g900f which i cleared it from a rom i used before and got it back to the original form of it. Got the .tar.md5 file of the official galaxy software from sammobile and installed it with odin. After that I wanted to root my phone again and stick with the official software. I tried to do that by the way I always used to with CF-Auto-Root using Odin once more and after downloading the file my phone was normally rebooting to recovery but it actually got stuck there without doing anything. Tried to flash twrp too but still nothing. The only thing i can flash at the time is the official software. Anyone had this issue before and can help? Thanks in advance
Flash the stock ROM again and get your phone back up and working properly
Then use this guide to root / twrp
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Hi Guys,
I have a weird problem with my S4 I9505 running Lollipop. WiFi works fine with my home network but when i am connecting to the Cisco AP at the office, i face very frequent disconnection and most of the times it doesn't get connected.I tried solution with lots of forums and finally decided to Root and Install Cynogenmod. After i installed the CWD Recovery with the Odin which said pass all the time..The device doesn't go into the CWD when restarted and only goes to stock Samsung Downloading Mode.So i am not able to install the Custom Rom's.
Can any of you guys help me out with this. Solution to any of these two issue will be very much grateful for me.
Thanks a ton in advance.
Well, firstly: CWM is outdated. So I suggest you TWRP recovery.
Secondly, after flashing the custom recovery you have to boot manually into it. Auto-rebooting causes the stock recovery to overwrite the custom one.
In other words, untick the auto reboot option in Odin. Actually, untick everything except F. Reset time.
HI, I have tried to root my S5 900I but failed badly, have done other phones in the past but somehow stuffed this.
The phone is stuck on downloading screen and cannot do normal boot.
I Started with flashing "recovery.tar.md5" 1st which passed in Odin but phone stuck on downloading screen, then I went into recovery and tried reset and flash CF Auto Root but still not working.
Then flashed twrp.kit.tar and still no normal boot but I can get into recovery Team Win, have tried numerous wipes and installing more CF Auto Root's and also tried flashing Miui Rom.
I believe I have screwed up the stock rom and don't know what to do next.
appreciate any help
brendy79 said:
HI, I have tried to root my S5 900I but failed badly, have done other phones in the past but somehow stuffed this.
The phone is stuck on downloading screen and cannot do normal boot.
I Started with flashing "recovery.tar.md5" 1st which passed in Odin but phone stuck on downloading screen, then I went into recovery and tried reset and flash CF Auto Root but still not working.
Then flashed twrp.kit.tar and still no normal boot but I can get into recovery Team Win, have tried numerous wipes and installing more CF Auto Root's and also tried flashing Miui Rom.
I believe I have screwed up the stock rom and don't know what to do next.
appreciate any help
Click to expand...
Click to collapse
Same happened to my wife's Galaxy Grand Prime months ago; stuck at downloading mode after rooting and installing TWRP recovery. The problem was with the version of TWRP recovery I was installing. Looks like I was installing the wrong one (although the website I downloaded it from states that it's the correct one for the device model). I tried different versions from different websites and was about to wipe everything and flash the stock rom but finally I got the correct one and that fixed the problem. Hope that helps.
iSergiwa said:
Same happened to my wife's Galaxy Grand Prime months ago; stuck at downloading mode after rooting and installing TWRP recovery. The problem was with the version of TWRP recovery I was installing. Looks like I was installing the wrong one (although the website I downloaded it from states that it's the correct one for the device model). I tried different versions from different websites and was about to wipe everything and flash the stock rom but finally I got the correct one and that fixed the problem. Hope that helps.
Click to expand...
Click to collapse
Thanks, I'll keep trying different TWRP, have tries so many but have changed the outcome yet