Hello there.. I normally don't have a problem figuring out what to do but I'm totally stuck here. I have a Sprint Galaxy S4 SPHL720T. I was rooted and running a custom ROM. I was having issues with the wifi so I decided to flash back to GPE 5.0.1 here from the xda forums. I am running twrp v2.8.4.0. I made a backup and wiped system/data/cache and dalvik. I went to install JFLTE-GPE-20150303 (LRX22C) from ultimarom.com via here at XDA. It said zip is corrupt. So i redownloaded on my PC and transferred it to my sd card. Still said corrupt. So I downloaded a different ROM on my PC and moved to SD. Still said corrupt. I tried to flash a GAPPS package and it worked but no ROMS I tried would. I tried to install my latest backup through recovery. It said MD5 doesn't match. If I hit reboot in twrp it prompts to install superuser because the phone doesn't appear to be rooted. If I hit that it runs the script for about 2 seconds then reboots. It won't boot into the OS as there is no OS and if I reboot into recovery it still gives me the "install su" prompt at the reboot screen. So then I hooked up into ODIN and download mode and flashed "CF-Auto-Root-jflterefreshspr-jflterefreshspr-sphl720t.tar.md5" and "openrecovery-twrp-2.8.4.0-jfltespr.tar". Still having the same issues. I have no idea what to do at this point. Any help would be GREATLY appreciated as I need my phone for work and play .
Thanks,
Aaron
OK I am running a 5.0.1 ROM, I have tried a few but all have some bug or other that eventually becomes annoying. The 5.0.1 stock is rubbish hence why I stuck a ROM on, I want to go back to stock but not 5.0.1, 4.4.2 for me worked fined, when I used kies to try and downgrade I got an AUTH Error, I presume because KNOX is tripped. Is there any way around this?
1. Make a backup of your internal data.
2. Flash android 4.4.2 firmware using ODIN but unticking "Auto-reboot" option.
3. Take the battery out when ODIN tell you PASS in green.
4. Put the battery in again and boot Recovery Mode -> Wipe data/factory reset + wipe cache partition.
5. Select first option: Reboot system now.
6. It should boot normally and you will have android Kit Kat again working perfectly.
Sadly it doesn't even go as far as flashing before giving auth error.
READ THIS BEFORE DOWNGRADING!!!!
Today i downgraded my friend's s4 i9500, downgrade was successful but the PHONE IS NOT DETECTING ANY SIM CARD.
moreover i lost my IMEI no. and when i checked in 'about' screen i saw BASEBAND is UNKNOWN . Read some instructions for backing up ur EFS data before downgrading this device.
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.
Good day guys,
I am from Singapore and I want to flash custom rom for my Note 3 LTC SM-N9005. I am not new to custom flash as I have done it successfully last time using Cwm.
However I been facing problem flashing custom on this note 3.
I have downloaded AryaMod ROM, rooted my stock firmware with chain fire auto root(flash using ODIN), installed twrp 2.8.7.0 using flashify.
I copied the rom to my SD card, power off phone, enter recovery mode (volume up, power and home) with Twrp interface . Wipe up the necessary delvik cache etc, then I install the ROM.
However I get to the screen where it says
Installing external_sd/ROM.zip
Checking md5 file.
Skipping md5 check. No md5 file found
.
.
.
Flashing file 1 of 1
External_sd/rom.zip
It run for about 2 mins. Then it auto goes back to twrp page. I reboot the phone into system mode but the firmware is not being flashed.
External_sd/rom.zip
What zip file is it ??
Edit: Didn't realize that AryaMod uses Aroma so latest version of TWRP is a no go.
If its an Aroma install then newer TWRP may/will not work .
See Rom faqs .
Fossildj said:
Good day guys,
I am from Singapore and I want to flash custom rom for my Note 3 LTC SM-N9005. I am not new to custom flash as I have done it successfully last time using Cwm.
However I been facing problem flashing custom on this note 3.
I have downloaded AryaMod ROM, rooted my stock firmware with chain fire auto root(flash using ODIN), installed twrp 2.8.7.0 using flashify.
I copied the rom to my SD card, power off phone, enter recovery mode (volume up, power and home) with Twrp interface . Wipe up the necessary delvik cache etc, then I install the ROM.
However I get to the screen where it says
Installing external_sd/ROM.zip
Checking md5 file.
Skipping md5 check. No md5 file found
.
.
.
Flashing file 1 of 1
External_sd/rom.zip
It run for about 2 mins. Then it auto goes back to twrp page. I reboot the phone into system mode but the firmware is not being flashed.
Click to expand...
Click to collapse
Download this one and flash it in your current twrp https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.zip.html
After that reboot again to your twrp and start flashing your rom.
You probably have flashed the one for 4.3 bootloader, a wrong one...
I guys I have the same problem when I'm trying to flash any Rom my phone its a 9005. I thinks its not TWRP 2.8.7.0 4.4 hlte etc... because I have it and did not work. tried by 2 ways: by updating bootloader/modem and without them and the result are the same. Im running stock lollipop, now without root neigther. So Im kind a stuck here in this obsulete 5.0 lol
any ideias, thanks in advance
See your multiple identical posts .
Start at stage one boot to download mode and see what model you have .
As posted .
https://forum.xda-developers.com/showpost.php?p=71296606&postcount=13244
JJEgan said:
External_sd/rom.zip
What zip file is it ??
Click to expand...
Click to collapse
Hi it's aryamod rom
Factory reset .
Flash stock rom through ODin .
Put Araymod zip on ext sd card .
Flash TWRP file through Odin .
Boot to recovery and flash zip .
FOLLOW ROM INSTRUCTIONS .
Installation Steps
Root permission and Custom recovery (PhilZ Touch 6.48.4 or twrp-2.8.7.0) is required for flashing any custom rom so make sure you are done this part.
Make sure your phone is fully charged to 100%.
Now follow as below:
Download the ROM zip and make sure md5sum is matched then transfer to your phone
Flash odin latest modem and bootloader from here
Boot the phone into Recovery Mode
Do a FULL wipe: Dalvik Cache, Cache, Data, System even if coming from a port rom
Flash rom
The first boot may take 15-20 min
After booting up in setting wizard make sure to uncheck diagnostic data
Notes
Please read and search before asking any question that hasn't been asked before
i recently just installed the floyd oneui rom onto my samsung note 5. after reboot it froze on phone is activating . can someone please tell me what i may have done wrong or if my phone is bricked ?
i unlocked the bootloader and flashed the twrp recovery onto the device using the lastest version of odin. i had the floyd file saved on the phone , did a wipe with twrp and installed the floyd file and after selecting only
items i was going to use went to reboot and now it's froze on phone is activating screen . i can still go back and do a full wipe with twrp recovery but is there anything else i can do or is the phone bricked
Are you using the latest version of twrp if not install it and try again after a full wipe. Also before anything backup your efs