Hi,
i wanted stock android on my s4 and downloaded cm11 and installed using the easy installer thing. Cm11 was not as great as i thought and was looking at the GPE rom.
I have the zip file downloaded for the GPE , just wondering to complete
do i need odin and if so what v?
do i need root?
Do i need CWM?
Im new to downloading and installing roms but i am a quick learner
Thanks
Every time you want to flash a custom rom you will require root and a custom recover (Like CWM, TWRP or PhilZ).
There are a few cases where you need Odin to flash the rom. But for the GPE rom you will need just a custom recovery and root.
Considering you have already installed a custom rom (although with the cyanogenmod installer) you should be rooted and maybe have a custom recovery.
Here is a root guide just in case.
But if you have an app like SuperSU, then you're rooted.
Then you still need a recovery. I don't know if the CM installer flashes one.
I myself use TWRP recovery. Because CWM just didn't work.
Used Nandroid manager (from google play) to flash TWRP because everything else failed.
If you don't have a custom recovery, then you can flash TWRP. I haven't tested the other recoveries on this device.
Go here and download the latest .img file.
Then you will use Nandroid manager to flash that img file. Then select "reboot into recovery".
Now you should have TWRP flashed. In case Nandroid says that you need to download busybox from google play, do that and install it. But CM should have busybox installed already.
Now put the rom zip on the external or internal storage. Boot into recovery, go to the Wipe tab and do a factory reset.
Then go to Install and select the zips you want to flash. This is how you basically flash a rom.
Some roms may require you to do some other stuff. So make sure you check the rom flash instructions.
nandroid is saying ,the file .... can not be flashed by this app , i checked if i was rooted by downloading a root checker and it said yes... what am i doing wrong?
nevermind, i used CWM instead and worked perfectly, couldnt have done it without you!!! Thanks
CWM didn't work for me.
But if it works for you, I guess it's alright
Just tried to flash Xposed on here using the Samsung-based one from Arter. Now that phone doesn't allow me to boot past the flashing android logo. Should I flash the uninstaller via recovery ("update via SD card"), or completely wipe the ROM, go back to NCG(I think), and then reflash it? I'm kinda at a lost at home I should handle this. I've heard that I shouldn't flash anything via the stock recovery on FlashFire-based roms.
You can't flash anything via the stock recovery. I recommend using Safestrap--read about it.
To make sure everything works completely on any firmware, I recommend doing the following:
Flash this with odin, boot the phone and go through the setup wizard:
https://www.androidfilehost.com/?fid=24052804347794178
Then, reboot to download mode again and flash this:
https://www.androidfilehost.com/?fid=24052804347776876
After it boots, root it with towelroot, install busybox, then install safestrap. There are directions posted already for this.
Look for jrkruse's "rooting tools for sdcard" zip and install it after you reboot into safestrap. Then you can wipe and install your rom and the firmware and never have to use odin again. You reinstall that zip after installing the ROM to get the apps for using safestrap without odin, also.
I have a SGH-I337M S4 via Koodo in Canada. I've spent 15 hours on this so far and am now really confused.
History: I installed Cyanogenmod a couple years ago. Recently wanted to change from that so I decided to install stock first via SamMobile for SGH-I337M Koodo. I downloaded 5.0.1 from here sammobile
I had it installed fine and then went to root, so I used Odin, enabled USB debugging - and installed CF Auto Root. That worked.
Then I went to install Clockwork Recovery mod and it errored out and I don't recall exactly what happened but now I'm stuck with the yellow exclamation point saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
In the TOP LEFT of screen is says:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL: LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled
1) I tried to do emergency recovery through KIES but my phone isn't being recognized in Kies.
2) I uninstalled Samsung USB drivers and tried just KIES alone
3) I tried just USB drivers with flashing stock firmware via Odin in download mode - it errors out and says no partition found or says FAIL in red.
I've read a lot but i'm not that technical when it comes to this.. not sure what to do at this point. I can get into download mode but I can't get anything to work.
Is the phone ruined??
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
audit13 said:
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
Click to expand...
Click to collapse
Hi Audit,
Thank you for the reply. I was able to try the original USB cable now and loaded the stock Koodo firmware through Odin and it worked flawlessly. Once loaded and rebooted, it went right to the homescreen and skipped past all the normal setup stages, so I assume something on the phone was there already but just corrupted on a bad upgrade.
Never again using an older USB cable.
Whew, that was a learning lesson. Now I'd like to:
1) re-root again
2) Install custom recovery (clockwork?)
3) Install the marshmallow OS via Broken I believe.
I will keep the thread posted for others who need help and for my own reference.
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
audit13 said:
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
Click to expand...
Click to collapse
I did not know that. I thought I required root first and then had to install a custom ROM. Interesting.
Ok, so the plan then is to find twrp for my phone model and install that first... I'll search and try to do that now.
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
audit13 said:
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
Click to expand...
Click to collapse
Done. I used the latest one for the tar and I have v2.8.4.0 right now. I held volume up and power and it went to Teamwin with a bunch of options. Install/wipe/backup/restore/mount/settings/advacned/reboot
On the TWRP website it says: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
1) I'm not sure what it means by typing that. I'd like to keep TWRP as I install my custom rom. I have the custom rom on an external SD card along with GApps. Should I insert the sd card and then boot to recovery, wipe all data and install from zip on sd card? Is that correct?
2) How do I keep TWRP from not getting overwritten?
Thanks so much for the help. Really appreciate it after a weekend of terror.
I backed up the EFS portion and it wrote it to the internal storage of the phone I believe... data/TWRP something. I did not have my external card in when I did that. Is that the correct way and how would I access that backup if I needed to?
Sorry for the questions. Trying to learn without running in circles.
After I backed up the EFS it also asked me to install SuperSU and I did that - then it rebooted automatically.
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
audit13 said:
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
Click to expand...
Click to collapse
I'm not sure if I can post links due to the new account, but the latest files for me are found on dl.twrp.me/jfltecan/ and the only tar image is twrp-2.8.4.0-jfltecan.tar
I will have to go over your other comments on my own to see the functionality. As of now, this is what I have:
1) Stock firmware
2) TWRP installed
3) TWRP asked if I wanted to root (I said yes, figuring that's what you meant)
4) TWRP installed SuperSu and rebooted
5) I downloaded Root Checker and it verified root.
I did just test it by powering off phone and then booting into recovery. Teamwin came up - so I assume that it's all working correctly and the stock ROM did not overwrite anything?
Questions:
1) Now I can boot into recovery mode and install the custom ROM via a zip file on sdcard?
2) Do I install GApps via recovery mode after I install a custom ROM?
3) Should I wipe/format before installing and if so, which one - "Advanced" or "Format" buttons?
I did a factory reset via TWRP then installed the custom ROM. Seems to be working quite well. Maybe I will try it a couple times in order to get the hang of it.
In order to determine that TWRP is the default recovery - it should load when I go into recovery mode correct?
If the phone boots to twrp once, it should not revert to stock recovery in the future.
Is there a stable ROM for a S4 i337m that is newer? I'm having some trouble finding a solid list that is known to work. I don't want to install a wrong version and mess up. I did try the "broken" ROM but 50% of time when someone phones me, they can't hear me speaking so I'm going to have to go back to stock firmware for now.
You could try ROMs made for the 9505 and i337.
I have searched and can not seem to find a solution
Here is where I am at:
Odin back to stock 4.4.2
Root with Towel Root
Install SuperSU, Update, and Disable KNOX
Install busy box
Install SafeStrap
Install Recovery
Boot into SafeStrap Recovery
Create Backup, Create a Partition and active Rom Slot 1
Wipe System, Cache, Data
Install Zip via External Card
Install goes perfect every time
Reboot
Phone gets stuck on the "Samsung Galaxy S5" screen
I can get into the stock recovery (not safestrap) and Download Mode
I then Odin back to stock and try again
I have tried 4 times and 4 different Roms. Has to be something I am missing
would using Flashfire possibly fix this?
EDIT:
Current set up
Android 4.4.2
Kernal 3.4.0
Build KOT49H.G900VRU1ANCG
update: Same problem with flashfire....
update 2: Could have been bad/wrong kernel. Going to odin to 5.0 and see what happens
67speeda said:
I have searched and can not seem to find a solution
Here is where I am at:
Odin back to stock 4.4.2
Root with Towel Root
Install SuperSU, Update, and Disable KNOX
Install busy box
Install SafeStrap
Install Recovery
Boot into SafeStrap Recovery
Create Backup, Create a Partition and active Rom Slot 1
Wipe System, Cache, Data
Install Zip via External Card
Install goes perfect every time
Reboot
Phone gets stuck on the "Samsung Galaxy S5" screen
I can get into the stock recovery (not safestrap) and Download Mode
I then Odin back to stock and try again
I have tried 4 times and 4 different Roms. Has to be something I am missing
would using Flashfire possibly fix this?
EDIT:
Current set up
Android 4.4.2
Kernal 3.4.0
Build KOT49H.G900VRU1ANCG
Click to expand...
Click to collapse
I think the problem may be you are trying to use the ROM slot. I thought I read that you are supposed to flash ROMs in the stock slot with safestrap.
Thank you for the help
I fixed it but not really sure how.
I THINK it was messed up because I had the wrong Kernel
Here is what I did:
Flashed latest Lollipop with Odin (on parrells on a Mac, worked really well)
Followed the KingRoot Guide to root phone
After a few attempts got root back
Installed the Rom suggested in the the Kingroot Thread
Found some script on XDA to debloat
I really wanted to try the toxic rom but going to play it safe for now...
ROM slot 1 is your problem, as it isn't supported on our devices.
Flash to stock slot only. Ignore the ROM slots.
If you did indeed have the wrong kernel flashed, you would never successfully boot.
Sometimes you also have to wipe cache and dalvik cache again after installing a ROM.
Hi there,
I'm trying to flash Resurrection Remix 6.0.1 to my Note 3. I've rooted with Kingo, flashed cwmod through ROM manager and done a backup. The ROM file and GApps are ready to go on my SD card. But whenever I try to get into recovery, I end up in the stock recovery instead? Any ideas how I can get around this? From reading around it seems Samsung phones can force stock recovery if they detect anything else. I've read that Philz Recovery can get around this but I don't have a Windows PC (rather than a Mac) to use Odin.
Use this to flash twrp and then reboot to recovery. Twrp will get around the stock recovery flash. https://play.google.com/store/apps/details?id=com.cgollner.flashify
Sent from my SM-N900P using Tapatalk