Related
I truly need the community's help on this one. Trying to fix a rom that I was using, I decided to wipe everything to reflash it. However, some how I read the thread wrong. Using TWRP, I formatted the "internal storage" thinking that was going to fix my Rom problems.
Now, I can't boot into the Rom or any rom, unless I wipe everything and restore one of my back ups. I restored a back up and it booted, but my data is jacked and phone service is not operable. I thought maybe a reboot will fix it, and now my phone is stuck at "Samsung Galaxy S 4". It doesn't move from there.
What should I do? How do I get it it continue the boot into the rom after a regular reboot? How do I get my radio back?
It's funny to me because I usually never get this careless with my phone. So I can laugh about it but damn I have to figure this one out!
Please help!!!!!!!!!!!!!!!!!
I am by know means an expert but I think you may have to start here with the firmware files then try and flash your backup http://forum.xda-developers.com/showthread.php?t=2338919
Sent from my SPH-L720 using Tapatalk 4
Thanks Chief, let me try that!
Thanks Chief. Unfortunately, that didn't work. I used Odin to flash the Firmware files and let it reboot. I'm still stuck at the Samsung Gal...boot screen. Let me try manually going into recovery and restoring.
Any other ideas? Anyone?
Kenjari said:
Thanks Chief. Unfortunately, that didn't work. I used Odin to flash the Firmware files and let it reboot. I'm still stuck at the Samsung Gal...boot screen. Let me try manually going into recovery and restoring.
Any other ideas? Anyone?
Click to expand...
Click to collapse
Have you tried flashing the complete odin ROM? You can find the all in one somewhere on the dev thread, it has rom, kernel, firmware and the rom all in one as it came from samsung. That should take care of your problem. It will wipe everything, or I think there was also a thread somewhere with odin flashables that didn't wipe data or internal sd but I can't seem to find it right now.
ifly4vamerica said:
Have you tried flashing the complete odin ROM? You can find the all in one somewhere on the dev thread, it has rom, kernel, firmware and the rom all in one as it came from samsung. That should take care of your problem. It will wipe everything, or I think there was also a thread somewhere with odin flashables that didn't wipe data or internal sd but I can't seem to find it right now.
Click to expand...
Click to collapse
Exactly. I'm on the target. I'm currently waiting for this tar that will unroot the phone. It is MDL but I will update and reroot. I hope this does the ticket. I'm going to use Odin to flash it or unroot.
Well strike two. That didn't work either. I downloaded a unrooted MDL tar and connected to Odin. When through the entire process and it rebooted. It still is stuck at "Samsung Galaxy S4".
I read on the Nexus 7 that I might have to reflash a system.img and boot.img? Someone else had a similar experience on the N7 and had to download it via flashdrive and then install via recovery. I'm not saying that's the case but I wonder if I need to reflash a boot.img or something.
Please help. Not sure where to go at this point. Unrooting didn't help.
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Progress made.
leaderbuilder said:
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Click to expand...
Click to collapse
leader, chief, ifly4,...I'm making progress.
leader, actually I flashed a previous version, the MDL via Odin. At first it didn't boot as stated in my previous post. I decided to wipe and factory reset. """"Bingo"""" it booted. Now I'm on MDL and unrooted. However, I transferred my phone over to a previous device so I can't update profile and prl. I'm going to activate the phone and see if it works. For some reason I can't can't seem to get a radio signal on it. It shows the be O with the slash in the middle. This is what it looked like before I deactivated it and lost everything before.
I post back with results. Not quite solved yet.
Thanks leader and everyone else.
Sound like your on the wrong firmware/baseband. what does your modem/baseband say?
Yeeessssss
leaderbuilder said:
Sound like your on the wrong firmware/baseband. what does your modem/baseband say?
Click to expand...
Click to collapse
It says L720VPUAMDL. I actually got it going. I had to change it from WCDMA to CDMA and reset. Now I'm unrooted. and going. However, leader, is there away to update the modem/baseband before I root? Or should I root then flash the MF9 Modem?
if you got MDL to activate you can jst take the OTA update to MF9. It will update it all.
Then use CF-Autoroot to gain root. After that same - install goomanager from Playstore and use it to install TWRP.
leaderbuilder said:
if you got MDL to activate you can jst take the OTA update to MF9. It will update it all.
Then use CF-Autoroot to gain root. After that same - install goomanager from Playstore and use it to install TWRP.
Click to expand...
Click to collapse
Awesome. Hey thanks again leader for helping me out. I'm usually never careless with these things. I use SACS rom but decided to try Miui. From some reason every time I flash Miui, I get the "Roaming Indicator Off" thing along with two signals. Reading the thread it suggest to format the internal. Why oh Why did I try that step. The rest is history....
Thanks again. Learned a lot with this process.
Glad you got it working.
There is a 'thanks' button too.
leaderbuilder said:
Glad you got it working.
There is a 'thanks' button too.
Click to expand...
Click to collapse
No doubt. I got to remember that!
Sent from my SPH-L720 using Tapatalk 4
Glad to hear you got it going.
Sent from my SPH-L720 using Tapatalk 4
leaderbuilder said:
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Click to expand...
Click to collapse
Thank you!
I installed the KOT49H GE ROM on my AT&T SGH-I337 and it runs great. I then decided to see if there was an update to TWRP and I found an updated one and flashed it via goo.im. I later read that this is not the way to do it. Anyway, when I boot into recovery a big yella triangle appears and at&t scolds me for running in authorized firmware. I can boot into download, cancel it and the ROM boots and runs fine.
Under the "about device" page on settings it says the baseband is MK2 (because I flashed that modem). If I look at the boot loader version via android terminal emulator it shows I'm still on MDL.
Any ideas how to get recovery working again?
I am trying to understand the reason why you flashed a recovery.
From your post, it looks like you are using safestrap and deadly venom tool to run GE.
You can flash the MLD files from the tool to get the recovery back.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
insaneretard said:
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
Click to expand...
Click to collapse
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
jmjoyas said:
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
Click to expand...
Click to collapse
Thanks for helping me out. I tried this yesterday and today with the link you provided. When I try to flash it via odin, it comes up as failed. On my phone, it says "SECURE CHECK FAIL: recovery" in red letters on the download page. Any other ideas?
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Do i need root to do this? I don't think I even have root any more. I'm running a custom ROM without root access. I tried to use CASUAL to root and install the recovery but it couldn't root it.
You will only need to root again if you go all the way back to stock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
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!
I know I am stupid, but I am trying to just get this phone to work. I did try and search for something that would come close to what I am encountering, but so far I can't find anything that would suggest a possible workaround. So, I hope this is in line with the rules, if not, please let me know and I will remove this myself pronto.
I was on 4.3 (MK2), rooted with TWRP and installed Xposed, all was fine and well, until AT&T decided to attack my phone to "remind" me to update to a newer version. After a few weeks I finally gave in, and knowing that I have somewhat heavily modified this phone, I went ahead and disable and uninstall Xposed, then head on to try and flash NC1 onto this phone via TWRP 3.72.
I was following this post, using post#3, and all was well, expect when I tried to flash AP using Odin, it was late and I failed to catch the fact Odin didn't connect my phone, so I guess the kernel didn't update. Then I went ahead and try booting it up. It got to the AT&T globe logo, only it has orange strips instead of blue. I waited maybe 15 mins for it to boot, and upon thinking it is not working, I pulled the battery and went into recovery and found I had a very early version backup, which I then restored that. It did boot! But the wifi wouldn't turn on, so I went and checked, the baseband was on NC1, but everything else is at MK2 (4.3). At that point, I give up and went to bed.
This morning, after giving it some good thoughts and research, I tried to Odin again, and this time I succeed, Odin recognizes my phone, and it flash the AP as it should. But when I try boot it up, it would only get to "safestrap disabled" and then black screen. After that, I can only get into the custom recovery, but no matter what I try, full/advance wipe, install, it would show something like "E: cannot mount system" so no matter what ROM I downloaded, it would not install, and when I try and re-boot, it would warn me that there is " No System"
So my question now is: since I can still see and access recovery, not all hope is lost, but since this is a work phone, I do need it back up and running, and I need it fast. How should I proceed from here? I tried straight flash a GPE ROM from here, but it would still run into the error of "E: cannot mount system" and trying to wipe/advance wipe would not work either.
If anyone has any idea what kind of problems I am running into, I am all ears to hear and try my best to get my work phone back up and running. Thank you all for taking you time to read, think and maybe help.
iantung329 said:
I know I am stupid, but I am trying to just get this phone to work. I did try and search for something that would come close to what I am encountering, but so far I can't find anything that would suggest a possible workaround. So, I hope this is in line with the rules, if not, please let me know and I will remove this myself pronto.
I was on 4.3 (MK2), rooted with TWRP and installed Xposed, all was fine and well, until AT&T decided to attack my phone to "remind" me to update to a newer version. After a few weeks I finally gave in, and knowing that I have somewhat heavily modified this phone, I went ahead and disable and uninstall Xposed, then head on to try and flash NC1 onto this phone via TWRP 3.72.
I was following this post, using post#3, and all was well, expect when I tried to flash AP using Odin, it was late and I failed to catch the fact Odin didn't connect my phone, so I guess the kernel didn't update. Then I went ahead and try booting it up. It got to the AT&T globe logo, only it has orange strips instead of blue. I waited maybe 15 mins for it to boot, and upon thinking it is not working, I pulled the battery and went into recovery and found I had a very early version backup, which I then restored that. It did boot! But the wifi wouldn't turn on, so I went and checked, the baseband was on NC1, but everything else is at MK2 (4.3). At that point, I give up and went to bed.
This morning, after giving it some good thoughts and research, I tried to Odin again, and this time I succeed, Odin recognizes my phone, and it flash the AP as it should. But when I try boot it up, it would only get to "safestrap disabled" and then black screen. After that, I can only get into the custom recovery, but no matter what I try, full/advance wipe, install, it would show something like "E: cannot mount system" so no matter what ROM I downloaded, it would not install, and when I try and re-boot, it would warn me that there is " No System"
So my question now is: since I can still see and access recovery, not all hope is lost, but since this is a work phone, I do need it back up and running, and I need it fast. How should I proceed from here? I tried straight flash a GPE ROM from here, but it would still run into the error of "E: cannot mount system" and trying to wipe/advance wipe would not work either.
If anyone has any idea what kind of problems I am running into, I am all ears to hear and try my best to get my work phone back up and running. Thank you all for taking you time to read, think and maybe help.
Click to expand...
Click to collapse
Are you sure you have Safestrap 3.72? It should be working if you do. Either way, try flashing the MK2 AP file/kernel from the downgrade thread or the KitKat Toolkit. That should guarantee it mounts and then you can try again. If that doesn't work, you might just have to ODIN NB1 and start from the downgrade.
DeadlySin9 said:
Are you sure you have Safestrap 3.72? It should be working if you do. Either way, try flashing the MK2 AP file/kernel from the downgrade thread or the KitKat Toolkit. That should guarantee it mounts and then you can try again. If that doesn't work, you might just have to ODIN NB1 and start from the downgrade.
Click to expand...
Click to collapse
I am now just trying to boot up the phone to check, and right now it is stuck at the Samsung Custom lock (white). So I guess either Odin NB1 or MK2 and start from there?
The only thing I think its odd is, it keeps telling me that it can't mount the system, and I can't for the live of me figure why that would even happen....
iantung329 said:
I am now just trying to boot up the phone to check, and right now it is stuck at the Samsung Custom lock (white). So I guess either Odin NB1 or MK2 and start from there?
The only thing I think its odd is, it keeps telling me that it can't mount the system, and I can't for the live of me figure why that would even happen....
Click to expand...
Click to collapse
If you had not taken the OTA from AT&T your phone bootloader is still on MK2.
Did you flash NC1 before or after you received OTA from AT&T.
sway8966 said:
If you had not taken the OTA from AT&T your phone bootloader is still on MK2.
Did you flash NC1 before or after you received OTA from AT&T.
Click to expand...
Click to collapse
I was not able to take the OTA from AT&T, due to that it was rooted and Xposed, so somehow the system check would backfire. When I got the phone, it was on MK2, and I only rooted it and installed custom recovery, for I only need to be able to delete some stuff at will, thus, the root access.
Actually, since I can't boot pass the Samsung custom lock, is it still possible to use Odin? I would have thought Odin would not recognize the phone since it is not on.....
iantung329 said:
I was not able to take the OTA from AT&T, due to that it was rooted and Xposed, so somehow the system check would backfire. When I got the phone, it was on MK2, and I only rooted it and installed custom recovery, for I only need to be able to delete some stuff at will, thus, the root access.
Actually, since I can't boot pass the Samsung custom lock, is it still possible to use Odin? I would have thought Odin would not recognize the phone since it is not on.....
Click to expand...
Click to collapse
It will still work, ODIN requires you to hold one of the volume buttons while powering on to go into download mode on the phone which doesn't require booting to system.
DeadlySin9 said:
It will still work, ODIN requires you to hold one of the volume buttons while powering on to go into download mode on the phone which doesn't require booting to system.
Click to expand...
Click to collapse
OK, so just tried Odin it using the files from Deadly Venom Kitkat Magic Tool. Odin caught the phone alright, but after the files are lined up (the mk2 ones), it give me the following:
Get PIT for mapping..
There is no PIT partition
All threads completed. (succeed 0/ failed 1)
And of course, the top also showed FAIL!
Any suggestions? Try going directly to NB1 and downgrade from there?
iantung329 said:
OK, so just tried Odin it using the files from Deadly Venom Kitkat Magic Tool. Odin caught the phone alright, but after the files are lined up (the mk2 ones), it give me the following:
Get PIT for mapping..
There is no PIT partition
All threads completed. (succeed 0/ failed 1)
And of course, the top also showed FAIL!
Any suggestions? Try going directly to NB1 and downgrade from there?
Click to expand...
Click to collapse
So after an all-night, I finally got it back up and running. Here is what I did, in case someone runs into the same problem.
I grabbed the MK2 file here, un-zip it, Odin it to its respective slots, and then flash it. It took over 10 mins, but it did finish the flash, and Odin showed "PASS!"
So, now I have another question, I booted it up like when it first came in the box, so went through and did all the setup. I went into setting, and I see the following:
Android version: 4.3
Baseband: I337-MK2
Kernel: signed Sat Nov 16 14:33:13 KST 2013
Build #: JSS-MK2
So if I want to do this upgrade to 4.4.2/4.4.3 again, would I consider my phone as stock MK2 that has not been tried to upgrade to 4.4.2/4.4.3? I did try and confirmed that I don't have root (obviously), so I guess I have to treat this phone as if it never took any updates/modifications? Then I would ask which route to follow to ensure the best and most confirm result of upgrading to either 4.4.2/4.4.3.
Thanks all for your thoughts on how to de-bug this. :laugh:
iantung329 said:
So after an all-night, I finally got it back up and running. Here is what I did, in case someone runs into the same problem.
I grabbed the MK2 file here, un-zip it, Odin it to its respective slots, and then flash it. It took over 10 mins, but it did finish the flash, and Odin showed "PASS!"
So, now I have another question, I booted it up like when it first came in the box, so went through and did all the setup. I went into setting, and I see the following:
Android version: 4.3
Baseband: I337-MK2
Kernel: signed Sat Nov 16 14:33:13 KST 2013
Build #: JSS-MK2
So if I want to do this upgrade to 4.4.2/4.4.3 again, would I consider my phone as stock MK2 that has not been tried to upgrade to 4.4.2/4.4.3? I did try and confirmed that I don't have root (obviously), so I guess I have to treat this phone as if it never took any updates/modifications? Then I would ask which route to follow to ensure the best and most confirm result of upgrading to either 4.4.2/4.4.3.
Thanks all for your thoughts on how to de-bug this. :laugh:
Click to expand...
Click to collapse
Yes your phone is stock MK2.
I do not know about 4.4.3 but you can find many 4.4.2 custom rom in the developer section.
First you need to root the phone. You can get the required files and instruction from here.
Second, you need to install the custom recovery. Since you are on MK2 you need to use Safestrap version 3.71. You can get the file and instructions here.
Once you have rooted and finish installing the SS (safestrap) you can find the custom rom in the developer section. Find the roms with SS option.
sway8966 said:
Yes your phone is stock MK2.
I do not know about 4.4.3 but you can find many 4.4.2 custom rom in the developer section.
First you need to root the phone. You can get the required files and instruction from here.
Second, you need to install the custom recovery. Since you are on MK2 you need to use Safestrap version 3.71. You can get the file and instructions here.
Once you have rooted and finish installing the SS (safestrap) you can find the custom rom in the developer section. Find the roms with SS option.
Click to expand...
Click to collapse
Sway8966, thank you for saving my behind more than once.
I will be following your instruction as to rooting the phone and also install custom recovery. However, if you see my first post, it seems I need to first install SS 3.71 to root, then SS 3.72 to upgrade to NB1/NC1? I will take a safe bet that I can't just use SS 3.72 to avoid brick. Also, that GPE version ROM, I had trouble finding the kernel, would there be a place to find it? Or is it in the package? I un-zipped it, but can't find the file that looks like the kernel in it.
Thanks again. :laugh:
iantung329 said:
Sway8966, thank you for saving my behind more than once.
I will be following your instruction as to rooting the phone and also install custom recovery. However, if you see my first post, it seems I need to first install SS 3.71 to root, then SS 3.72 to upgrade to NB1/NC1? I will take a safe bet that I can't just use SS 3.72 to avoid brick. Also, that GPE version ROM, I had trouble finding the kernel, would there be a place to find it? Or is it in the package? I un-zipped it, but can't find the file that looks like the kernel in it.
Thanks again. :laugh:
Click to expand...
Click to collapse
iantung329 I am glad to help you out.
You do not need to install SS recovery first to root the phone. Rooting is done by using the adb command to push the super user in the system area.
Since you are in a MK2 firmware/bootloader Safestrap 3.71 is the only one you can use.
Also your bootloader is MK2 so I would not go to install the NB1/NC1 system file on your phone. SS 3.72 is for the NB1/NC1.
To upgrade your phone to 4.4.2 OS you can find the custom rom packages (including the kernel) in here.
Bootloader MK2 and above can not use the custom kernel since there is no exploit for the kernel out so far. So you need to choose the TOUCHWIZ rom with SS version, not AOSP (Android open-source project) rom.
We are not supposed to tell you which rom to choose because people might not have similar taste or expectation in the choice of rom. Read around and choose the rom that you want.
If you'd asked me, I use Golden Eye rom. I am on NC1. You can see that in my signature section.
I will tell you how I installed the Golden eye rom as an example.
I download the package (zip file), my NC1 stock kernel file and superSU file.
Using the safestrap I installed the package zip file. After the installation finished I installed the NC1 kernel file and SuperSU file. Then I reboot my phone. That is. Other roms might have different instructions.
iantung329 said:
Sway8966, thank you for saving my behind more than once.
I will be following your instruction as to rooting the phone and also install custom recovery. However, if you see my first post, it seems I need to first install SS 3.71 to root, then SS 3.72 to upgrade to NB1/NC1? I will take a safe bet that I can't just use SS 3.72 to avoid brick. Also, that GPE version ROM, I had trouble finding the kernel, would there be a place to find it? Or is it in the package? I un-zipped it, but can't find the file that looks like the kernel in it.
Thanks again. :laugh:
Click to expand...
Click to collapse
sway8966 said:
iantung329 I am glad to help you out.
You do not need to install SS recovery first to root the phone. Rooting is done by using the adb command to push the super user in the system area.
Since you are in a MK2 firmware/bootloader Safestrap 3.71 is the only one you can use.
Also your bootloader is MK2 so I would not go to install the NB1/NC1 system file on your phone. SS 3.72 is for the NB1/NC1.
To upgrade your phone to 4.4.2 OS you can find the custom rom packages (including the kernel) in here.
Bootloader MK2 and above can not use the custom kernel since there is no exploit for the kernel out so far. So you need to choose the TOUCHWIZ rom with SS version, not AOSP (Android open-source project) rom.
We are not supposed to tell you which rom to choose because people might not have similar taste or expectation in the choice of rom. Read around and choose the rom that you want.
If you'd asked me, I use Golden Eye rom. I am on NC1. You can see that in my signature section.
I will tell you how I installed the Golden eye rom as an example.
I download the package (zip file), my NC1 stock kernel file and superSU file.
Using the safestrap I installed the package zip file. After the installation finished I installed the NC1 kernel file and SuperSU file. Then I reboot my phone. That is. Other roms might have different instructions.
Click to expand...
Click to collapse
As sway said, you do not need Safestrap to root, you just use Saferoot and you have root. However, you can actually use SS 3.72 and it would be better to use it since you can then mount /system even while on a 4.4.2 kernel. You can also use the single GPE located in the general section. Sway's ROM flashing instructions are correct, but also remember to flash the kernel module zip in Safestrap, and you would be using the MLD set since you have the MK2 bootloader. The kernels and everything you need are included in the KitKat Magic Toolkit.
DeadlySin9 said:
As sway said, you do not need Safestrap to root, you just use Saferoot and you have root. However, you can actually use SS 3.72 and it would be better to use it since you can then mount /system even while on a 4.4.2 kernel. You can also use the single GPE located in the general section. Sway's ROM flashing instructions are correct, but also remember to flash the kernel module zip in Safestrap, and you would be using the MLD set since you have the MK2 bootloader. The kernels and everything you need are included in the KitKat Magic Toolkit.
Click to expand...
Click to collapse
:crying::crying::crying:
Sigh, I will admit, I have done it again, so I am back to flashing the MK2 file from a few post ago.
I think I will either go with stock rooted ROM or the GPE version, I think the only thing I am missing is the kernel, which I found in one of the post I have to Loki it since I am on AT&T, but I can't find the Loki software, or would that be using Odin as well?
The only reason I am looking to root this phone is so that I can tether. Traveling roughly 2-3 weeks a month ain't fun, but not all hotels have free wifi, so having my phone rooted and able to tether is like a life line. Also, after I tried GB, its wonderful! Apart from I can't find a good quiet time option, everything is awesome being able to use GB and AdBlock. Does either Sway or DeadlySin9 have a good recommendation for quiet time app/mod?
As soon as I get the phone back on stock MK2, I will be looking into either stock root ROM or GPE version. Thanks all! :fingers-crossed:
iantung329 said:
:crying::crying::crying:
Sigh, I will admit, I have done it again, so I am back to flashing the MK2 file from a few post ago.
I think I will either go with stock rooted ROM or the GPE version, I think the only thing I am missing is the kernel, which I found in one of the post I have to Loki it since I am on AT&T, but I can't find the Loki software, or would that be using Odin as well?
The only reason I am looking to root this phone is so that I can tether. Traveling roughly 2-3 weeks a month ain't fun, but not all hotels have free wifi, so having my phone rooted and able to tether is like a life line. Also, after I tried GB, its wonderful! Apart from I can't find a good quiet time option, everything is awesome being able to use GB and AdBlock. Does either Sway or DeadlySin9 have a good recommendation for quiet time app/mod?
As soon as I get the phone back on stock MK2, I will be looking into either stock root ROM or GPE version. Thanks all! :fingers-crossed:
Click to expand...
Click to collapse
OK. @DeadlySin9, got the final question (hopefully :fingers-crossed
I am going to flash GPE version (here) and I will be following the direction on that, wipe, flash, kernel then reboot. You mentioned that I should use the MLD kernels, but which one is that in the Kitkat magic tool? AP_MLD, BL_MLD? And now I have SS 3.71 on the phone, would you recommend uninstalling that and install SS 3.72 instead, since I will be flashing GPE version anyway?
Also, what of this ROM (here)? I guess I can't flash this one?
iantung329 said:
OK. @DeadlySin9, got the final question (hopefully :fingers-crossed
I am going to flash GPE version (here) and I will be following the direction on that, wipe, flash, kernel then reboot. You mentioned that I should use the MLD kernels, but which one is that in the Kitkat magic tool? AP_MLD, BL_MLD? And now I have SS 3.71 on the phone, would you recommend uninstalling that and install SS 3.72 instead, since I will be flashing GPE version anyway?
Also, what of this ROM (here)? I guess I can't flash this one?
Click to expand...
Click to collapse
Actually, neither of those work. There's one in the General section, with Safestrap in the thread title. That's the one you need. I do recommend going to 3.72 on Safestrap, and you need to use both the AP and BL files in ODIN.
Sent from my SGH-I337 running GPE
DeadlySin9 said:
Actually, neither of those work. There's one in the General section, with Safestrap in the thread title. That's the one you need. I do recommend going to 3.72 on Safestrap, and you need to use both the AP and BL files in ODIN.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
This is the only one I can find (here)
Also, by the look of it, paid apps wouldn't work in this ROM, that might be a problem.
Here is another one that I was considering from the start (here), but I am not sure if I should follow the first post or second?
iantung329 said:
This is the only one I can find (here)
Also, by the look of it, paid apps wouldn't work in this ROM, that might be a problem.
Here is another one that I was considering from the start (here), but I am not sure if I should follow the first post or second?
Click to expand...
Click to collapse
If you're still on MK2 then you can use the second one. And yeah, you can't download paid apps from the Play Store for some reason.
DeadlySin9 said:
If you're still on MK2 then you can use the second one. And yeah, you can't download paid apps from the Play Store for some reason.
Click to expand...
Click to collapse
@DeadlySin9, thanks for pointing out the correct one to use, and yes, I am still stock on MK2, rooted and have not installed SS, pending the version discussion. I will go ahead and install SS 3.72 and the ROM from the first post and :fingers-crossed: that it will work wonders.
The reason that I am choosing this over the GPE, don't get me wrong, GPE I think is better, but no download paid apps is not going to work for me, some apps like, root explorer and a few others are a must on the phone. So that's a bummer. I wish it works, then I can just flash and be in peace.
Thank you @sway8966 also for helping out on this. I just freaked out when I found out the work phone was dead.....
Ive been going so crazy trying for about 15 hours total now trying to root and get a custom recovery on my phone, for some reason, nothing will work. I do have alot of experience with rooting and ive done just about everything, attempting to get this phone to flash a custom recovery.
ATT SGH i337
4.4.4
KTU84P.I337UCUFNJ4
I am currently rooted, but i cannot get a custom recovery. I have just tried this method,
http://forum.xda-developers.com/showthread.php?t=2297033
with that tool, however after running it, it successfully flashes the recovery, then boots me into the Odin Mode Download screen with the picture of an android. Same thing with trying any other method of flashing a recovery. Can someone please tell me how to get past this, im so exhausted trying to fix this. I tried factory reseting my phone from the phones settings and even that brought me back to the download screen with a picture of an android. I cant get into any recovery at all! Stock or custom it sends me back to that screen.
How can i flash a custom recovery and get this working? Thank you guys in advance
You're on nj4. Safestrap is the only recovery you're going to be able to use. Read the stickies in the general forum
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're on nj4. Safestrap is the only recovery you're going to be able to use. Read the stickies in the general forum
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
i installed the proper NJ4 safestrap apk and pressed install recovery, however it still says it is not installed "reboot to recovery" is greyed out. Upon booting into recovery, i am still stuck in Odin mode. Anyway for me to stop odin mode from continuing to come up instead of recovery?.
I would guess the system is looking for stock recovery, and it isn't there any more due to your flashing the CWM OUDHS recovery and/or TWRP. You probably need to put the stock recovery back.
I know and I've been trying to find out a way to do that. Could you help me if that's what I need to do? Once I reinstall stock recovery will safestrap work?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I would suggest that you flash nb1 then nb4, root and install safestrap. At this point, a clean install is your best bet. Refer to this thread in the general forum.
U can get stock recovery back by either flashing the whole stock firmware via odin or extracting the recovery image from the firmware and flashing it by its self via odin I don't know anything about safestrap as I'm on Canadian version some one else can hopfully help u out with tht
I read what you posted and I don't entirely understand. Could you point to me to a download a maybe dumb it down a bit?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
How would I do that..
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
xstokerx said:
U can get stock recovery back by either flashing the whole stock firmware via odin or extracting the recovery image from the firmware and flashing it by its self via odin I don't know anything about safestrap as I'm on Canadian version some one else can hopfully help u out with tht
Click to expand...
Click to collapse
Exxoriscism said:
I read what you posted and I don't entirely understand. Could you point to me to a download a maybe dumb it down a bit?
Click to expand...
Click to collapse
Exxoriscism said:
How would I do that..
Click to expand...
Click to collapse
You are on NJ4 (I337UCUFNJ4). There is no flashable "whole stock firmware" for that version. There is a flashable whole stock firmware for the NJ1 version (I337UCUFNB1). Also, there is no easy way to "extract the recovery image out of the firmware and flash it by its self via odin." The reason for this is that you need a .tar archive to flash in odin, so if you extract just the recovery, you then need a Linux box, or a Linux virtual machine running on your windows pc to make the tar file from it.
This is why I suggested that you flash the NB1 full stock firmware, and then flash the upgrade to NJ4 from stock recovery, as outlined in the guide I linked.
As you asked for a little more detailed help, I'll try to walk you through following the Odin to Stock, Updating, Rooting, and Safestrap Guide.
First, read through post #1 and the FAQ in post #3. Next, you need to decide what version you want to end up with. Let's assume that you want to end with NJ4 -- KitKat 4.4.4. (If you want to end with OC3 -- Lollipop 5.0.1, then the instructions are a little different.)
In post #2, under the section titled NJ4 -- KitKat 4.4.4 expand Step 1 - Odin to stock. The files you need to download are at the top of this section. Follow the steps; they are pretty self explanatory. Part 1 installs full stock NB1, and Part 2 installs the upgrade to NJ4.
You are now on fully stock NJ4. If you want to root and install Safestrap, expand Step 2 -- Root and Install Safestrap. The files you need to download are at the top of this section. Again, the steps are pretty self explanatory.
That's it. If you want to now install custom firmware, you are ready, or you can just stay on stock if you prefer.
creepyncrawly said:
You are on NJ4 (I337UCUFNJ4). There is no flashable "whole stock firmware" for that version. There is a flashable whole stock firmware for the NJ1 version (I337UCUFNB1). Also, there is no easy way to "extract the recovery image out of the firmware and flash it by its self via odin." The reason for this is that you need a .tar archive to flash in odin, so if you extract just the recovery, you then need a Linux box, or a Linux virtual machine running on your windows pc to make the tar file from it.
This is why I suggested that you flash the NB1 full stock firmware, and then flash the upgrade to NJ4 from stock recovery, as outlined in the guide I linked.
As you asked for a little more detailed help, I'll try to walk you through following the Odin to Stock, Updating, Rooting, and Safestrap Guide.
First, read through post #1 and the FAQ in post #3. Next, you need to decide what version you want to end up with. Let's assume that you want to end with NJ4 -- KitKat 4.4.4. (If you want to end with OC3 -- Lollipop 5.0.1, then the instructions are a little different.)
In post #2, under the section titled NJ4 -- KitKat 4.4.4 expand Step 1 - Odin to stock. The files you need to download are at the top of this section. Follow the steps; they are pretty self explanatory. Part 1 installs full stock NB1, and Part 2 installs the upgrade to NJ4.
You are now on fully stock NJ4. If you want to root and install Safestrap, expand Step 2 -- Root and Install Safestrap. The files you need to download are at the top of this section. Again, the steps are pretty self explanatory.
That's it. If you want to now install custom firmware, you are ready, or you can just stay on stock if you prefer.
Click to expand...
Click to collapse
Yes and i did everything under the NJ4 Kitkat 4.4.4 section. I am rooted and everything worked except for safestrap. I open it and press install recovery and everytime it finishes it says "state:Not Installed". And reboot to recovery is greyed out. Upon manually rebooting into recovery mode, i am in normal stock recovery.
I cant use the selinux mode changer it says. To root i didnt use towelroot because installing the NC1 kernel disables my wifi connection, and since the phone has no service, i had to use KingO Root. I have confirmed root access using root checker. But Safestrap wont work.
What do i do? Is safestrap not working because i didnt root with towelroot? I assumed it didnt quite matter how i rooted. If it is because of towelroot, then how do i get towel root to work while on the NC1 kernel with no wifi and no cell service?
Update: I found a selinux Mode changer apk on xda and installed it. I tried it and safestrap still would not work and said "not installed". I also reflashed the NC1 Kernel and the same thing happened. I booted into recovery for confirmation.
I guess its maybe because i didnt root with towelroot? But it is impossible without phone service because flashing NC1 disables the wifi. Please reply as soon as you can
I can't help with your current issue with safestrap because I don't own this phone. I have worked on my son's S4, and a couple of others that have come through my hands. I have performed the exact process you just used with no issues.
I would suggest you post your issues in the guide thread where someone who has more experience with safestrap can help.
creepyncrawly said:
I can't help with your current issue with safestrap because I don't own this phone. I have worked on my son's S4, and a couple of others that have come through my hands. I have performed the exact process you just used with no issues.
I would suggest you post your issues in the guide thread where someone who has more experience with safestrap can help.
Click to expand...
Click to collapse
Can i move this thread?
Exxoriscism said:
Can i move this thread?
Click to expand...
Click to collapse
You can't move this thread into that one. But you can state your issue in that thread and then provide a link to this one for more info.
Sent from my Nexus 9 using XDA Free mobile app