Related
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!
*****************************************
*******HELP HELP HELP*************
*****************************************
Hi,
I am unable to install CWM or TWRP recovery on my AT&T US - S4 I337. Baseband is NB1.
I have tried almost every option on xda , rom manager , twrp manager , loki method using emulator , 3 way tool , casual etc.
Loki gives loki aboot version error. Earlier phone was on NC1 , got it on NB1 using odin.
I want to get rid of original stock , which is loaded with lot of crap and want to install light weight custom rom.
Any pointers , help is highly appreciated.
Thanks.
rdxdha said:
*****************************************
*******HELP HELP HELP*************
*****************************************
Hi,
I am unable to install CWM or TWRP recovery on my AT&T US - S4 I337. Baseband is NB1.
I have tried almost every option on xda , rom manager , twrp manager , loki method using emulator , 3 way tool , casual etc.
Loki gives loki aboot version error. Earlier phone was on NC1 , got it on NB1 using odin.
I want to get rid of original stock , which is loaded with lot of crap and want to install light weight custom rom.
Any pointers , help is highly appreciated.
Thanks.
Click to expand...
Click to collapse
Download Free version of Rom Manager and after install see if it will not install which ever you want through it CWM or TWRP. Way I do it. You are Rooted???? Here is link https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en After install open and click on "Flash ClockworkMod Recovery" then it gives you choice of CWM or TRWP
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
rdxdha said:
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
Click to expand...
Click to collapse
You can't install custom recoveries. Our bootloader is locked. Your only option is using safestrap
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
U can't install a traditional recover. Since U are on NB1, your baseband is locked and your only option is Safestrap (TWRP). Read the instructions carefully at least once all the way thru and then proceed. Pay close attention because it's not like most phones. It works just fine. U can have a heavily modified Touch Wiz Rom or even now a AOSP based Google Play Edition Rom.
Proceed here:
[INDEX] All things AT&T MK2, NB1, and NC1 (including ROMs
rdxdha said:
I already tried rom manager after rooting the phone, and get the success message as well. But when i restart phone in recovery mode , I am still getting stock recovery options instead of CWM or TRWP.
Click to expand...
Click to collapse
What are you looking for in CWM recovery that is different for Stock recovery????
tailgunner9 said:
What are you looking for in CWM recovery that is different for Stock recovery????
Click to expand...
Click to collapse
I am trying to install custom rom , without safestrap. As bootloader is locked on my phone , I cant use CWM.
Using safestrap , I was able to install [AOSP] Official 4.4.3 - S4 Google Edition. but now I am not able to encrypt my phone.
Any idea on how to encrypt phone now ?
I'd like to test out CM13 on my rooted i337m, currently running CM 12 with bootloader I337MVLUFNE1. Before I start I'd like to get an idea of the steps involved; any help you can offer is appreciated!
My understanding is that to use CM 13 I will need to do the following:
1. Install the UCUAMDB or UCUAMDL bootloader from the i337
2. Flash the version of recovery that corresponds to the cm13 version I wish to use
3. Backup, wipe, flash CM13 ROM and GApps
I have no idea how to do steps 1 and 2. I've never messed with the bootloader and I'm not even sure if it's safe to use the i337 one on i337m. I also can't seem to get twrp manager to flash a .img file.
CM13 thread:
http://forum.xda-developers.com/gal...rom-cyanogenmod13-releases-nightlies-t3459578
Do you have an i337 or i337m? You can confirm the model number in download mode.
If it is the i337m, just flash twrp, cm13, and gaps.
Yes I've got the i337m, running I337MVLUFNE1 bootloader. So you're saying that I don't need to change bootloaders - all I need to do is flash the cm13 recovery that goes with my cm13 rom. That makes things easier!
I already have TWRP 3.0.2-0 installed. I am trying to use TWRP manager to flash the cm13 recovery from the 2016/8/20 snapshot ( cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J3-jflteatt-recovery.img), but it doesn't show up in the directory. I think this might be because it's a .img file instead of a .zip. Should I just zip it up?
If you have twrp installed as a custom recovery, just copy the rom, which should be in a .zip format, to the phone's internal memory or as card, boot into twrp, perform a full wipe, and flash the rom and your choice of gapps if the rom doesn't include google apps.
audit13 said:
If you have twrp installed as a custom recovery, just copy the rom, which should be in a .zip format, to the phone's internal memory or as card, boot into twrp, perform a full wipe, and flash the rom and your choice of gapps if the rom doesn't include google apps.
Click to expand...
Click to collapse
The problem with that is I get "error 7" from TWRP when flashing the rom as described above. The instructions linked in my original post say that the workaround for this is to first flash the specific recovery snapshot that corresponds to the rom snapshot. I put that recovery on my SD card but TWRP manager couldn't see it (its a .img file), so I zipped it and then tried to flash, but this failed.
So it seems the next step for me is to figure out how to flash that recovery snapshot before I go on worrying about the rom.
I appreciate your help and patience!
The status 7 error is usually caused by one of two items: the TWRP version is outdated or the ROM is not for the phone you are trying to flash.
Since you have an i337m, use Odin and flash TWRP for the gt-i9505, then flash CM.
audit13 said:
The status 7 error is usually caused by one of two items: the TWRP version is outdated or the ROM is not for the phone you are trying to flash.
Since you have an i337m, use Odin and flash TWRP for the gt-i9505, then flash CM.
Click to expand...
Click to collapse
Before I try to flash it with Odin, is it okay to instead use TWRP manager to install the latest jflteatt version of TWRP (since it's a jflteatt version of CM I want)? I bricked a device with Odin once so if you think this would work instead that's what I'll do!
Which version of TWRP did you install? Was it for the jfltecan? If it was, it may probably error out when flashing the att version of CM.
Yes I have JFLTECAN TWRP at the moment. On my old phone it was drilled into me to only use stuff for my version of that phone, which I guess isn't the case with the S4. So it's safe to put the jflteatt twrp on my phone?
Did you try to flash the jflteatt version to your phone using the can version of TWRP? If it won't flash, try the 9505 version of TWRP on the i337m.
I understand what you mean about bricking but the recoveries are very similar as are the phones themselves.
I got it to work. There were 2 issues: 1 was that I needed the jfltexx recovery like you suggested, and 2 was that TWRP manager wasn't properly installing new recoveries so I was actually always testing with the jfltecan recovery. Switching to Rashr allowed me to install the jfltexx recovery, which allowed me to get the fltexx cm13.
Thanks again for your help!
To install TWRP, I thought you flashed the tar version of TWRP using Odin 3.07 in the PDA box. That is the simplest way I know to flash it.
Okay, here is the deal. I was trying to install a costum rom on my att galaxy s4. What I did was I rooted it using king root and tried to flash a rom through rom toolbox, but I believe it was just going to take me to my recovery. After that the screen got stuck on the costum screen with the padlock, and only seems to turn on with a charger plugged into it. I am on 5.0.1 lollipop and have managed to flash the original recovery, but any stock rom I try to flash using Odin fails by saying complete thread failed or something like that, and says on my phone binary 1 or something like that. I really need help on where to start.
Thanks
What is the exact Odin error?
AT&T never released a full firmware for flashing via Odin beyond 4.1.2. Look here for a possible solution: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Once the phone is running a 4.3 or higher bootloader, the bootloader is locked and custom ROMs can't be installed unless the custom ROM is based on a stock ROM.
There's an ODIN flashable Android 4.2.2 MDL bootloader tar file out there somewhere too.
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
audit13 said:
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
Click to expand...
Click to collapse
Are there any other options, or should I just give up on it?
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
audit13 said:
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
Click to expand...
Click to collapse
I finally fixed it. I had downloaded that rom before, but it hadn't worked. I decided to try it again and used a different USB port and it worked! Thanks for the help!
Hello everyone,
I was thinking about installing Lineage OS on my Samsung Galaxy S4 GT-I9515 (Value Edition) currently running Stock Android Version 5.0.1 without root.
Is the version of Lineage OS and TWRP I found at https://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-cm14-1-galaxy-s4-jfvelte-gt-i9515-t3534552 appropriate for that purpose?
Now, my confusion arises from the fact that different guides seem to give incomplete or even contradictory instructions on how to approach that. As a first step, I need to install a custom recovery, such as TWRP:
Does this require my device to be rooted?
Some guides apparently require my bootloader to be unlocked; Is this necessary? If so, how do I do that?
Other guides suggest that I use Odin. Is this the correct approach? Does my bootloader need to be unlocked for that method? Is a root required?
Anything else I should pay attention to?
Thank you very much in advance
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Not able to root S4 GT-I9515
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
I tried to flash CF-Auto-Root on my phone after completing the flash till reset on odin phone gets restarted and is showing following messages on top left corner on the samsung s4 logo screen
recovery booting....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
it is not going any further than this please help.
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
the twrp file bricks the phone
raffux3 said:
the twrp file bricks the phone
Click to expand...
Click to collapse
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
TheFixItMan said:
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
Click to expand...
Click to collapse
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
raffux3 said:
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
Click to expand...
Click to collapse
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
TheFixItMan said:
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
Click to expand...
Click to collapse
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
raffux3 said:
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
Click to expand...
Click to collapse
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
TheFixItMan said:
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
Click to expand...
Click to collapse
I have re-installed the usb drivers and odin works fine finally. I will try to root and install twrp again...thank you for support