Hello everyone
I just got a I9505, and I'm coming from the first Note. Before I had rooted my Note only once, I dont remember how I got Custom Recovery (CWM) into the phone, but I used it for every rom flash, I have never used Odin before.
So far What I have seen here is that the guide for flashing appears to not include Custom Recovery (CWM I guess, there appears to be one other variation now), but in every ROM thread all I see are download links to flash with odin, looks like nobody is using CWM to flash roms anymore.
The main advantage of CWM is that for me it appeared to be safer (My friend who likes to use Odin he has difficulties flashing most of the time), and it does not increase the counter.
Also, I'm not sure if to obtain ROOT I can just flash a pre-rooted rom from Odin while not being rooted. Does it work?
Thanks in advance
sniperbr0 said:
Hello everyone
I just got a I9505, and I'm coming from the first Note. Before I had rooted my Note only once, I dont remember how I got Custom Recovery (CWM) into the phone, but I used it for every rom flash, I have never used Odin before.
So far What I have seen here is that the guide for flashing appears to not include Custom Recovery (CWM I guess, there appears to be one other variation now), but in every ROM thread all I see are download links to flash with odin, looks like nobody is using CWM to flash roms anymore.
The main advantage of CWM is that for me it appeared to be safer (My friend who likes to use Odin he has difficulties flashing most of the time), and it does not increase the counter.
Also, I'm not sure if to obtain ROOT I can just flash a pre-rooted rom from Odin while not being rooted. Does it work?
Thanks in advance
Click to expand...
Click to collapse
We use CWM to Flash only Custom ROMs/Kernels.
We use ODIN to flash Stock ROMs/Kernels.
The easiest way to have Root and CWM is HERE
Or you can Flash a Pre-rooted Stock ROM
Good luck
Related
Hi there,
I'm a newbie to android. Just got my i9000 (international version of Galaxy S) for two weeks which I like it very much and flashed it to the official Froyo 2.2 (Build ZSJPD, which to my understanding is based on the European JPO) straight away. But only recently that I find out that it can neither boot into the recovery nor the download mode via the 3 button method, which makes flashing via the Odin impossible for me. I tried to download the Rom Manager to install the Clockwork Recovery Mod but I faced the same problem as the top message of this thread, i.e. it cannot get into the unsigned CWM recovery as it is running the stock 3e recovery.
Nonetheless, thanks to the "Quick Boot App", I was able to go into the stock recovery mode by clicking the dedicated button. So my question is:
Is there any way I could flash the stock kernel back to 2e recovery, given the above condition, so that I could run the CWM recovery?
Is there any apps, which would actual install a different kernel so that I could bypass the stock kernel?
Hope big guys out there could give me some hint and show me the way! Otherwise, I would miss a lot fun and can't even apply the Universal lagfix.
Alex
I am curious too. I am running ZSJPE (Asian Build) but it doesn't seem to have 2e recovery as I am unable to boot into CWM, even with ROM Manager installed.
Any help would be greatly appreciated.
aywchiu said:
Hi there,
I'm a newbie to android. Just got my i9000 (international version of Galaxy S) for two weeks which I like it very much and flashed it to the official Froyo 2.2 (Build ZSJPD, which to my understanding is based on the European JPO) straight away. But only recently that I find out that it can neither boot into the recovery nor the download mode via the 3 button method, which makes flashing via the Odin impossible for me. I tried to download the Rom Manager to install the Clockwork Recovery Mod but I faced the same problem as the top message of this thread, i.e. it cannot get into the unsigned CWM recovery as it is running the stock 3e recovery.
Nonetheless, thanks to the "Quick Boot App", I was able to go into the stock recovery mode by clicking the dedicated button. So my question is:
Is there any way I could flash the stock kernel back to 2e recovery, given the above condition, so that I could run the CWM recovery?
Is there any apps, which would actual install a different kernel so that I could bypass the stock kernel?
Hope big guys out there could give me some hint and show me the way! Otherwise, I would miss a lot fun and can't even apply the Universal lagfix.
Alex
Click to expand...
Click to collapse
It amazes me the amount of people flashing roms without 3br. Why dont you install the 3br fix? then you can do whatever you like to your phone
http://forum.xda-developers.com/showthread.php?t=785201 odin
http://forum.xda-developers.com/showthread.php?t=821698 update.zip
Try either of these before you brick your phone! it doesnt matter how carefully you follow instructions it takes just one bad flash and your history...
tragusman said:
It amazes me the amount of people flashing roms without 3br. Why dont you install the 3br fix? then you can do whatever you like to your phone
http://forum.xda-developers.com/showthread.php?t=785201 odin
http://forum.xda-developers.com/showthread.php?t=821698 update.zip
Try either of these before you brick your phone! it doesnt matter how carefully you follow instructions it takes just one bad flash and your history...
Click to expand...
Click to collapse
I've been directed to one of these links to fix the 3BR bug on my I9000, but after reading some replies I'm a little hesitant as several people have reported their phone being bricked thanks to it...
If by any chance my phone does get bricked because of this, is there any other way to re-flash or something of the sort?
EDIT: Sorry to bump an old post...
i installed safestrap and tried updating to oudhs recovery through recovery.
it says it installs but when i reboot its still safestrap.
also tried installing twrp thorugh android emulator still have safestrap.
any suggestions?
You can't flash a recovery. You're going to have to return to stock
Edit how can someone with so many posts know so little about their device. If you're on ss you have to use the recovery that comes with it. Read the stickies
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
bstylz911 said:
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
Click to expand...
Click to collapse
So if you are on MDB or MDL (You must have been if you have the AT&T S4 and custom recovery) just Odin back to stock firmware and re-install whichever custom recovery you want (as long as it is for this phone and LOKId). Make sure you get the custom recovery on the phone before it tries to update to a firmware that you can't do anything (other then Safestrap) with. Search and read to find the information you need if you don't understand what I am telling you. And don't do anything to your phone until you do. Good luck.
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!
Hi there, I rooted this phone a while back and for some reason decided to also load a custom recovery (Pretty sure it's TWRP) even though I was using stock firmware and just wanted root. Now the phone's trying to do an OTA and it won't work of course because of my custom recovery. I was wondering if someone had a link to a stock recovery I could flash via ODIN/Heimdall? Thanks!
P.S. If you could include a step-by-step on what I need to do, that'd be nice. As far as I remember it's just putting the phone in Download Mode and flashing the .tar file via ODIN.
Hello to all ..
is there any chance to root my S4 with the i9505XXUPPI1 version installed on it Or is there any other Way to Downgrade it to an earlier version and root it thereafter?
greetingz from Germany
HouseMeischda
You could try cfautoroot or flash TWRP and then flash supersu from TWRP.
CF-Auto-Root is your best option.
Thanks for your help.
For all i9505 Users with the same Problem ..
First i've flashed the original I9505XXUHOJ2 Firmware who listed on chainfire's Page, to be on the safe way =). Then i've flashed the cf-root Kernel from Chainfire. After that i installed the newest TWRP recovery and then the Resurrection Remix Rom 5.5.9.
Now i will test everything but seems to be nice till this moment =)
Thread can be closed .. Thanx
BTW, rooting is not required to install TWRP with Odin.
audit13 said:
BTW, rooting is not required to install TWRP with Odin.
Click to expand...
Click to collapse
True. But some people (including me) have had problems getting TWRP to stick with the Odin install.
I had to use an app to flash it when I took to the custom software world.
A user had the same problem few days ago. Also solved it with the app method.
I've never had a problem with getting TWRP or CWM to stick on the s2, s3, s4, note 1, note 2, or note 3 by unchecking auto reboot in Odin before flashing recovery. Once recovery has been flashed, I remove the battery and immediately boot into recovery. I found that not booting into recovery right after flashing will cause the stock recovery to overwrite the custom recovery when the phone boots normally.
Thats right. But in my case and first of all i wanted to test the stock rom with only root Access. But then i decided to install a custom one very quickly =)
After all i installed latest twrp via twrp-app, backed up everything, perform a full wipe and flashed ResurrectionRemix 5.5.9. Now i went to dirty unicorn rom on Android 6.0 base. Very nice performance, very clear Design and absolutely stable.
One more word to overriding the Recovery. In many other Posts, this Problem seems to be normal, if the S4 was already updatet to an official lollipop rom(with the new knox Bootloader, that verifies signatures of recovery and kernel) in the past. I think this issue was not present with kitkat and oder versions.
But with my little detour, i also was not effected from that override
Hope this can help others with similiar reservations who i had before. Not the fear of loosing warranty(because phone is anyway too old) but fear of tripping the bad eFuse and thus hardbricking the phone. BUT WELL DONE !!!
Many thanks for the support .. And greetingz to all =)
There is no eFuse that will hard-brick the S4.
It only has an eFuse for Knox, which simply prevents you from resetting the Knox counter back to 0x0, but it won't hard-brick anything.