Was testing kn0x0ut on our device when I ended up flashing an empty system image. I was on MK2 and attempted to use the MJ6-MJ9 method of flashing just enough files to pass the OTA checks. They didn't flash, and now it says my PIT is broken. I have recovery, and the data partition is in place as on a normal boot it loads to black screen with a blue LED. I can use adb, but there is no root so I can't restore my system. Any suggestions? I'm busy today so I won't be able to reply much, but I can gladly give more information.
EDIT: The system apparently isn't empty. The partition got flashed at some point and appears to have MF3 files.
However, there is still no root and it boots up to nothing but a black screen with blue LED still. I can't get the small update from cache that the MJ6-MJ9 thread mentions. Also, attempting a recovery boot results in the Secure Fail: Kernel screen. Recovery is fixed with the MJ6 recovery file.
FIXED: I was able to get it working following the instructions again. Not sure what the exact issue was with the first time i tried, but flashing the MJ6 recovery makes recovery boot again. I had to flash the two emergency tars, flash the recovery tar again, and then boot into recovery. It then applied the update from cache and on next reboot i went back in and used the sideload.
Have you tried ADB sideloading the update through the recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Supreme Dynamite said:
Have you tried ADB sideloading the update through the recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It doesn't go through since it fails the file check.
Possible help
Hey there, I Gorked my i337 at&t version on Thanksgiving day! I was able to go to this thread and just used Odin to flash the two .tar files and then was able to sideload the mk2 update. Boom phone was back to 4.3
http://forum.xda-developers.com/showthread.php?t=2526964&page=19
joshzdad2013 said:
Hey there, I Gorked my i337 at&t version on Thanksgiving day! I was able to go to this thread and just used Odin to flash the two .tar files and then was able to sideload the mk2 update. Boom phone was back to 4.3
http://forum.xda-developers.com/showthread.php?t=2526964&page=19
Click to expand...
Click to collapse
That's what i've been trying to no avail. The first small update from cache never happened and now it's broken even more.
EDIT: Recovery is booting after flashing the MJ6 recovery, surprisingly. Will attempt instructions one more time and report back.
I beleive i just said screw it since I knew I was boned! I then just flashed recovery-mj6.tar.md5 not even sure if it worked. Then flashed the mf3-emergency-part-1.tar.md5 then the mf3-emergency-part-2.tar.md5 and finally I beleive I tried the side load of my mk2 full update file and it worked.
joshzdad2013 said:
I beleive i just said screw it since I knew I was boned! I then just flashed recovery-mj6.tar.md5 not even sure if it worked. Then flashed the mf3-emergency-part-1.tar.md5 then the mf3-emergency-part-2.tar.md5 and finally I beleive I tried the side load of my mk2 full update file and it worked.
Click to expand...
Click to collapse
Good job man you had me on the seat of my pants reading this.
ROOTED ATT MK2 using Tapatalk
Related
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Did you try and reflash recovery ? Does the phone boot up once you restore via Odin ?
Have you tried flashing twrp via Odin?
I have not tried flashing TWRP with Odin... is there a Odin version of TWRP?
It did not boot after flashing stock. I'd like to Odin TWRP if it's available.
I found an Odin TWRP.tar for SGS3, but nothing for S4, yet. Need a little more help.
Did you try rooting and flashing twrp via goomanager? I had something similar happen to me on my skyrocket and that's how I fixed it.
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
TheAxman said:
Aroma does not work on the GS4 yet. At least that is what I have been reading.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This version of CWM claims to work with Aroma on the S4...
http://forum.xda-developers.com/showthread.php?t=2322682
scott14719 said:
This version of CWM claims to work with Aroma on the S4...
well lets take a look see...shall we. thanks
Click to expand...
Click to collapse
came across this thread: http://forum.xda-developers.com/showthread.php?t=2281287
it converts an img to an odin-flashable tar.
i went ahead and converted the latest twrp img for the at&t S4 and have attached it. i have not tested it as i am not near my device at the moment. if you decide to try it, unzip the tar.md5 and flash at your own risk as i have not tested this method by @cabloomi.
False aroma works fine with twrp on a gs4.
Sent from my SGH-I337 using Tapatalk 4 Beta
This happened to me. Use odin to put TWRP back on. You'll be fine.
Sent from my SGH-I337 using Tapatalk 2
Yeah I had this a couple different times trying to get rid of the custom/lock icon boot up. Flash fresh stock rom, root it and install recovery with "Root and Recovery for ATT-TMO GS4-CASUAL-R527b" --> http://forum.xda-developers.com/showthread.php?t=2297900 then flash the recovery you want etc, and restore Nandroid of backed up rom. Worked for me!
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
JJ5150 said:
I bricked it. I had TWRP installed, and running a debloated Odexed version of Stock. I attempted to flash Slim Bean 6.5 Weekly with Aroma addons. The Aroma ended up borking my recovery. It bootloops pre-recovery mode. I can get into Download mode and Odin'd back to Stock, but it's still won't go into recovery and vibrate loops with a black screen.
Anyone know how to fix this? Damn locked bootloader!!!
Click to expand...
Click to collapse
I had a similar issue. When you hold the key combination to boot into recovery, do it for more than one cycle. Sometime for some reason it doesn't take the first time so keep holding the buttons. After getting into android recovery, clear cache and reset the phone.
JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing. I have yet to find a Odin version of TWRP that's loki'd for the S4. If you have done this, and it worked, please supply a link to the correct file. In this case an Odin version of TWRP. Thank you
Click to expand...
Click to collapse
When I had the problem is sounds like your having I Odined the Stock image back to the phone and then cleared the dalvik and cache with the stock recovery menu, then I was able to boot, I then rooted and used the debloater program found here on the forums and then just downloaded goomanager and installed TWRP, the one it pushes is LOKIed for you.
This is also the only .img file I can find for the our version of TWRP. IIRC you can use Odin to flash it
EDIT: Like trublu said, you may have to do it several times (clearing the caches in the stock recovery after ODIN)
JJ5150 said:
Everyone keeps saying to Odin TWRP like it's a common thing.
Click to expand...
Click to collapse
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
JJ5150 said:
I have yet to find a Odin version of TWRP that's loki'd for the S4.
Click to expand...
Click to collapse
i believe that all s4 recoveries are "loki'd", if you will.
xBeerdroiDx said:
you are correct in that twrp has not posted tars on their website yet for download. they have, however, posted imgs. find a way or find someone to convert that img to an odin-flashable tar and you'll be all set.
i believe that all s4 recoveries are "loki'd", if you will.
Click to expand...
Click to collapse
The Tmo and Sprint variants do not require Loki'd recoveries, as their bootloaders are not locked.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
They do great work..used them 2 years ago. With a mytouch..ouch..
Sent from my SAMSUNG-SGH-I337 using xda premium
JJ5150 said:
After trying many options available to me such as, Flashing Stock with Odin and trying to access recovery via the three finger method, and trying to convert a TWRP.img file to a .tar file... which I managed to successfully flash, but to no avail. I'm stuck at the vibrating boot loop dead screen, soft brick scenario.
I found these guys in a similar thread http://mobiletechvideos.com/
I called them and they were really nice and professional. I shipped out my phone for Brick Repair today. I believe I'll be happy with the results from these guys from they way they conduct themselves in their videos.
I'll report back when I have my fixed, unbricked S4 back in my hands
Click to expand...
Click to collapse
It's called Jtag repair. And the guys you mentioned have saved many a ass with it. I've seen several good results. Unless something else is found, it is the only way I know of to fix a truly bricked phone. Some people (those who flash a lot and Dev a lot) have their own Jtag boxes.
BTW, which tool / method did you use to convert the .img to a TAR? I've seen a couple of methods and a tool or two but I was wondering if you used something I don't know about? TIA.
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!
RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.
So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?
Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Good deal
Sent from my GT-I9505 using xda premium
Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:
Let me preface this by saying I have searched here and other websites and have tried the methods I have found and cannot get the issue fixed. ANY help is greatly appreciated.
I have a sprint s4 l720. I rooted it and installed a custom rom and twrp a few months ago. I recently saw that 4.4 came out and wanted to try a new rom. I first booted into recovery and tried to restore my system back to the original stock rom that I had backed up when I first installed the new one. I was able to restart it and it loaded fine but if I pull the battery or do a restart it gets stuck at the samsung splash screen. I have tried advanced wipe, format data, wipe dalvik and cache and even installing other roms and it still gives me the same behavior. I have tried other methods to re-install the stock rom and I keep encountering issues. I downloaded the most recent ODIN and the samsung USB drivers and "jflterspr16gb.pit" and sprints .tar.md5 file. It loads into odin fine and shows the added on the dialogue box and I load the respective files into odin and it keeps failing. I am at a lost.
All I want is to be able to add either the stock rom or preferably the custom 4.4 rom and work as it used to. Restart when needed and not get stuck at the boot screen. ANY help is much appreciated. any ideas on what I am doing wrong? Thanks guys!
Anything 4.4 at this point is custom. Just boot into recovery, wipe and flash the 4.4 ROM.
Sent from my SPH-L720 using Tapatalk
if your at ota MJA then trying to odin md5 will not work. Did you take the MJA update?
frostedunit said:
Anything 4.4 at this point is custom. Just boot into recovery, wipe and flash the 4.4 ROM.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I have tried that. I boot into twrp and have tried formatting all data and just wipe data and then I restart and load gummy 4.4 and the gapps for it and then wipe the dalvik and cache. It will boot into the gummy rom fine and give me no issues, but it is if I try to restart it or power it down and power it back on is where it gets stuck at the samsung splash screen.
rheller219 said:
if your at ota MJA then trying to odin md5 will not work. Did you take the MJA update?
Click to expand...
Click to collapse
I am not for sure what the MJA is. Could you pleaes elaborate to me? Thanks.
pgrim85 said:
I have tried that. I boot into twrp and have tried formatting all data and just wipe data and then I restart and load gummy 4.4 and the gapps for it and then wipe the dalvik and cache. It will boot into the gummy rom fine and give me no issues, but it is if I try to restart it or power it down and power it back on is where it gets stuck at the samsung splash screen.
I am not for sure what the MJA is. Could you pleaes elaborate to me? Thanks.
Click to expand...
Click to collapse
Where does it stop on the odin error? And dont use the pit file. Try again without the pit file.
Sent from my SPH-L720 using xda app-developers app
You should always be on a stock ROM of the latest version prior to flashing an unofficial, newer Android ROM.
For example:
If you're trying to flash 4.4, you should be on stock 4.3 such as this: http://forum.xda-developers.com/showthread.php?t=2505025
MJA is the latest official 4.3 build for the Sprint S4.
If you're on 4.2, you should update to 4.3 stock, then flash 4.4. This generally prevents any unexpected results.
Furthermore, always ensure you are flashing from a trusted recovery such as TWRP and CWM.
Occasionally, one recovery will not run the install script properly.
If you are certain you are doing the install right, you can try from another recovery.
Additionally: If you are having trouble with Odin on Windows 8, ensure your computer does not report a driver malfunction when you plug your device in after entering download mode.
This can possibly be fixed by running Odin as administrator. Or, you can attempt to manually install the USB drivers by downloading them, disconnecting from the Internet, uninstalling previous drivers, then manually installing the USB package you downloaded.
Sent from my SPH-L720 using xda app-developers app
R0CKSTAR3N3RGY said:
You should always be on a stock ROM of the latest version prior to flashing an unofficial, newer Android ROM.
For example:
If you're trying to flash 4.4, you should be on stock 4.3 such as this: http://forum.xda-developers.com/showthread.php?t=2505025
MJA is the latest official 4.3 build for the Sprint S4.
If you're on 4.2, you should update to 4.3 stock, then flash 4.4. This generally prevents any unexpected results.
Furthermore, always ensure you are flashing from a trusted recovery such as TWRP and CWM.
Occasionally, one recovery will not run the install script properly.
If you are certain you are doing the install right, you can try from another recovery.
Additionally: If you are having trouble with Odin on Windows 8, ensure your computer does not report a driver malfunction when you plug your device in after entering download mode.
This can possibly be fixed by running Odin as administrator. Or, you can attempt to manually install the USB drivers by downloading them, disconnecting from the Internet, uninstalling previous drivers, then manually installing the USB package you downloaded.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Is there a way I can fresh restart my phone? I do not have any recovery files since I wiped my phone in its entirety and I had no backed it up on the SD card, rookie mistake, I know. I don't necessarily need 4.4, but what I do need is my phone to boot up properly whenever I choose and not have to boot into recovery, wipe the phone and then when I turn it on have to go through the setup process.
ROMANTiC KiD said:
Where does it stop on the odin error? And dont use the pit file. Try again without the pit file.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I will have to look where it stops again tonight. but it does connect by showing the "pass" on the odin box on the left. could it be that I have the wrong odin? I noticed the top of odin it shows epic 4g when I have a galaxy s4, is this ok or is there a way I can change that? I dl the odin from a forum that was specifically a tutorial on how to flash the galaxy s4, sprint specifically, so I figured it would be the correct one. Also, I did try again without the pit file and it still failed.
Thanks for the help so far guys
Some of the Odin packages have multiple versions thrown together. Make sure to use the highest version number (3.07?) And that you are putting the .tar in the PDA slot. If all else fails, try deleting the .md5 off the end of the file before you load it in Odin. Used to work on OG Epic sometimes.
Sent from my SPH-L720 using Tapatalk
Hello. I recently ran through QBKing's unroot guide. The process seemed to go fine, but now I get stuck at the yellow Sprint screen. I have tried several things to remedy this. I've ran the unroot Odin file multiple times. I have tried to install a stock rooted MF9 tar with odin, I have tried to re-root and install TWRP recovery.
Nothing seems to work. What can I do now?
Thanks!
Edit: I just checked, and my Unroot/Unbrick tar didn't pass MD5...Re downloading again, see you in 2 hours lol.
When you are some try going into recovery and doing a factory reset.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Alright, so after a fresh download where the MD5 matched, I'm still stuck on the yellow Sprint boot screen. Any thoughts? What can I try? Where can I find a valid custom recovery TAR to push out with odin?
Wiskid15 said:
Alright, so after a fresh download where the MD5 matched, I'm still stuck on the yellow Sprint boot screen. Any thoughts? What can I try? Where can I find a valid custom recovery TAR to push out with odin?
Click to expand...
Click to collapse
First off, the mf9 tar file is 4 versions old now so are you using the correct tar file. Second, you will need to do a factory reset if it is hanging on the yellow Sprint screen. What exactly are you trying to do. If you want to unroot to upgrade to Kit Kat, then just flash the new NAE full tar file that is available in the development section from Random45. That will upgrade you to Kit Kat in one easy step.