So after exhausting all options, I turn to the experts for help. I have a friend in the UK, who wanted to downgrade his Galaxy s5 g900f 5.0 to 4.4. He's familiar enough with basic odin/recovery use, but only vaguely.
He wanred to downgrade, so I had him flash TWRP 2.8.7.0 via Odin. All went well. I then had him make a full back up, boot, system, data etc. He has no sd card, so after the back up I had him move his entire internal storage (except the back up) to his pc. Then we downloaded OmegaDroid v13 (4.4) for the g900f. Flashing went as expected to start, did full wipe, flashed the zip (aroma installer). The two options for kernel choice with this ROM or stock kernel or Omega kernel. Flashing with stock kernel sends the phone into an infinite bootloop, flashing with the omega kernel never boots at all (black screen with blue led on, I had him leave it like this for an hour to make sure). So I told him to restore his back up until we can find another 4.4 to try. Well restore fails every time.
No problem, I thought, we can mount usb or use adb sideload. So I had him download CM 11. Had him boot to recovery and mount usb while connected to pc. The box wont check, just no response. So I got him to download adb and drivers, had him verify his isntall. The problem here is adb devices lists no device. Odin however can communicate with it.
Am I missing something. Is there a way to turn on USB debugging from twrp or the terminal in twrp? Or is there an odin flashable rooted 4.4 rom available for the g900f that anyone is aware of. My google searches have come up with no answers to these. 4.4 roms in general for this device are few and far between. Ive told him he may have no choice but to go and get a sd card, as this would make life much easier, but it still bothers me that adb cant see the device at all, yet odin can.
Thanks for help in advance.
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 wanna go to the RR MM version ROM for Zenfone 5, but fewmsome days before I decide to do it, my microusb got some kind of bug, anyway, it doesn't connect to pc (I tried everything). So, in the tutorial says to flash the new recovery made by them, but i don't have how to connect it on pc to flash the new TWRP recovery, but I have a funcional system working (the stock .87 version from asus) and I want to know if there's a way that I can flash the recovery without using pc (once that my microusb jack is f*kd). I saw in other forum that "recovery.img" is inside the /factory partition, so apps like Flashify cannot read and write on it. Just droidboot can do that. So this is what I want to know, of there's a way to flash the recovery trough the booted Android and if I can make a script to Droidboot run. (Of course, all of them without pc). Or even if I can flash RRMM on my current twrp version (2.8.7.0)
Thanks xda.
Try to flash it via TWRP 2.8.7.0
"Error flashing image, no partition specified".
Twrp actually doesn't show any partitions to install the image.
MarconiGRF said:
"Error flashing image, no partition specified".
Twrp actually doesn't show any partitions to install the image.
Click to expand...
Click to collapse
I provided flashable zip for my RR MM rom. So you shoudl just choose zip archvie with rom to flash it.
It is not a image.
tank0412 said:
I provided flashable zip for my RR MM rom. So you shoudl just choose zip archvie with rom to flash it.
It is not a image.
Click to expand...
Click to collapse
Oh, I read your post again, i'll try to flash with twrp 2.8.7.0
Sucessful installing ROM, really fast and battery management. Thx
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
Hi,
after flashing serveral custom roms (with open bootloader) via twrp (latest version), which btw worked perfectly till now, i suddenly produced a twrp loop. I tried to flash another custom rom, reinstall twrp, but no rom boots. Only twrp appears.
Because of this i can´t also open the port to flash a stock rom via QFIL. Is it possible in my situation to remove twrp and install stock recovery? I can´t find a corresponding img file.
Thanks!