Ok so I started out on 4.2.2 & never took the 4.3 update in light of all the backtalk about the knox BS... I do my research first lol
But to install a 4.3 ROM I needed to odin the firmware/baseband to mk2... Soft bricked it... Every time I odined that mk2 firmware it would soft brick...
Odined back to 4.2.2 did everything all over again(root & philz touch CWM) & still soft bricked it when I tried to odin the mk2 firmware...
Realized that odin'ing to the mk2 firmware forever ruined any chances of going back to No Knox Stock pre-mk2.
I did however get past the "firmware update FC everything" with a simple factory reset from the devices settings menu!!! Needless to say it wasn't easy between all the FC's lol, but...... Yay no more FC!!!
So, now I'm stuck at stock rooted OTA mk2 with Philz Touch CWM(the only way I could safely get the proper firmware & cant seem to flash a single thing whatsoever...)
I'm a seasoned vet here, ex ACS themer, well over 5000 flashes on my belt & I NEEDS MY FIX!!! Someone please tell me theres a way to flash a ROM after all the BS I've been thru here...
If you were trying to flash the MK2 firmware (modem) by Unknownforce one of the things metioned was
NOTE: With MJA/MK2 Firmware, some people report better success with turning Auto Reboot and F. Reset Time unchecked. Do the same flash, but when you see PASS on Odin, unplug the phone and Hold the Power key for 10 seconds to reboot.
Click to expand...
Click to collapse
Also installing that firmware does NOT put knox bootloader on your system.
Taking the OTA however does!
IF you do have the latest Philz (philz_touch_6.08.9-jfltespr) you should be able to flash most ROMs.
In the last week there have been three or four ROMs that have been updated/released and they all run well. Big thing with flashing is that some builds require different recoveries and/or flashing instructions (as per the dev's OP). Some require rebooting of recovery etc.
leaderbuilder said:
If you were trying to flash the MK2 firmware (modem) by Unknownforce one of the things metioned was
Also installing that firmware does NOT put knox bootloader on your system.
Taking the OTA however does!
IF you do have the latest Philz (philz_touch_6.08.9-jfltespr) you should be able to flash most ROMs.
In the last week there have been three or four ROMs that have been updated/released and they all run well. Big thing with flashing is that some builds require different recoveries and/or flashing instructions (as per the dev's OP). Some require rebooting of recovery etc.
Click to expand...
Click to collapse
Tried this also no luck... although im running Philz v6.0.4.5
& once you install firmware that has knox you cant go back to no-knox versions...
try flashing the latest twrp from Philz, reboot recovery then in TWRP goto advanced and 'fix permissions. Then reboot.
Then back to recovery, flash Philz, reboot recovery and try install from again.
Either way... I still cant get anything to flash lol
I just need to flash something lol
I'm stuck at stock rooted OTA mk2 with Philz Touch CWM
what to do from there?
leaderbuilder said:
try flashing the latest twrp from Philz, reboot recovery then in TWRP goto advanced and 'fix permissions. Then reboot.
Then back to recovery, flash Philz, reboot recovery and try install from again.
Click to expand...
Click to collapse
never tried that lol
i only odined Philz
greenmuggy said:
never tried that lol
i only odined Philz
Click to expand...
Click to collapse
I keep zips of both recoveries on my externalSD card for just that.
leaderbuilder said:
I keep zips of both recoveries on my externalSD card for just that.
Click to expand...
Click to collapse
i didnt bc it didnt work at the time...
greenmuggy said:
i didnt bc it didnt work at the time...
Click to expand...
Click to collapse
leaderbuilder said:
I keep zips of both recoveries on my externalSD card for just that.
Click to expand...
Click to collapse
Both downloaded just gonna back up my backups on my sd & ill give it a try
BRB
7gb... ugh... this might take awhile
Ok as soon as i boot into TWRP & try to flash the newest Philz CWM it wont take...
Yeah... I'm stuck at v6.0.4.6 PhilZ Touch
Is there an odin for this 6.0.8???
I give up for now, its bed time too many beers lol...
Philz PC Odinable .tar
TWRP Odinable .tar
leaderbuilder said:
Philz PC Odinable .tar
TWRP Odinable .tar
Click to expand...
Click to collapse
Thanks, I will try when I get home from work.
Sent from my SPH-L720 using xda app-developers app
leaderbuilder said:
Philz PC Odinable .tar
TWRP Odinable .tar
Click to expand...
Click to collapse
If I can finish my homework 2nite ill give this a try... been busy as hell with my work & 3rd semester college they are kicking my ass this semester lol
leaderbuilder said:
Philz PC Odinable .tar
TWRP Odinable .tar
Click to expand...
Click to collapse
Yeah it still won't flash or odin to the newest Philz... What am i missing i need some major help
If i odin TWRP & then flash the newest Philz, it just goes back to the v6.0.4.6 Philz... Why>>> Ahhh!!!
Try just to PC Odin Philz. Use Odin 3.09 see if that works.
leaderbuilder said:
Try just to PC Odin Philz. Use Odin 3.09 see if that works.
Click to expand...
Click to collapse
Didn't work it wont go away, unless i odin TWRP, but that wont flash any roms either, & from twrp if i odin or flash philz it just goes back to the old version of philz
I think the partition that holds the recovery.img might have gotten corrupted or something that is causing your problems. I would try using odin 3.09 to flash the MK2 full stock tar to bring your phone back to an unaltered state. Then re root using safe root or cf autoroot. Then try to install the recovery you want. Might be less of a headache then fighting this problem you keep having getting a recovery to work.
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!
As the title says, I am currently unable to boot into Philz recovery. I bricked somehow trying to flash sacs 4.3 by stupidly restoring the wrong part of my nandroid backup. Flashed the stock OEM 4.3 MJA and did a factory reset right after. Anyway, when I try to boot into recovery it says "Recovery not seandroid enforcing" and "see warranty bit : recovery" then just reboots into the rom. Can anybody help me out?
Once you flashed stock MJA, you have to re flash Philz and reroot.
Sent from my SPH-L720 using Tapatalk
frostedunit said:
Once you flashed stock MJA, you have to re flash Philz and reroot.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I did both of those. I currently have root access and flashed the recovery twice to make sure I didn't do it wrong the first time. I am beginning to wonder if the bootloader changed from MF9 to MJA when I flashed the OEM, which won't allow Philz to boot properly.
Bump.
Still stuck without a working recovery...
l0udude said:
Bump.
Still stuck without a working recovery...
Click to expand...
Click to collapse
Odin the tar of philz
http://forum.xda-developers.com/showthread.php?t=2201860
Grab the tar and odin
Confused on how you flashed philz 2 times without a working recovery?
ParkerParker said:
Odin the tar of philz
http://forum.xda-developers.com/showthread.php?t=2201860
Grab the tar and odin
Confused on how you flashed philz 2 times without a working recovery?
Click to expand...
Click to collapse
I did use Odin... that's what I meant. I did get it to boot once after disabling the Knox bootloader with SuperSU and installing the binaries for CWM but when I tried to reboot back into recovery it starts booting then reboots normally again. I think I'm just going to have to wait for a MJA compatible custom recovery. Gonna stock it out for now.
l0udude said:
I did use Odin... that's what I meant. I did get it to boot once after disabling the Knox bootloader with SuperSU and installing the binaries for CWM but when I tried to reboot back into recovery it starts booting then reboots normally again. I think I'm just going to have to wait for a MJA compatible custom recovery. Gonna stock it out for now.
Click to expand...
Click to collapse
Im on MJA and using the latest philz with zero problems, also people are having success using twrp 6301, although I would use caution as its not 100% yet, what rom are you on? You can remove Knox with titanium backup, either way philz is rock solid on 4.3, also if making backups on 4.3 you need to go to Nandroid settings and check the selinux 4.3 box before making a backup in order to restore a 4.3 Rom. Also not sure why you are having to install binaries for cwm? Since you are staying stock cool but if you used cf auto root, which you stated you are rooted, you should be able to Odin philz, did you ota? Flash the modem from Unknownforce? @leaderbuilder you have any input man?
Sent from my SPH-L720 using Tapatalk
ParkerParker said:
Im on MJA and using the latest philz with zero problems, also people are having success using twrp 6301, although I would use caution as its not 100% yet, what rom are you on? You can remove Knox with titanium backup, either way philz is rock solid on 4.3, also if making backups on 4.3 you need to go to Nandroid settings and check the selinux 4.3 box before making a backup in order to restore a 4.3 Rom. Also not sure why you are having to install binaries for cwm? Since you are staying stock cool but if you used cf auto root, which you stated you are rooted, you should be able to Odin philz, did you ota? Flash the modem from Unknownforce?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
On the oem 4.3 rom still because I can't flash. Can't flash because custom recovery won't boot. I think it's because of knox. Where do I go in titanium backup to disable knox? Because I can't get supersu to do it again.
l0udude said:
On the oem 4.3 rom still because I can't flash. Can't flash because custom recovery won't boot. I think it's because of knox. Where do I go in titanium backup to disable knox? Because I can't get supersu to do it again.
Click to expand...
Click to collapse
I think you are possibly a little over your head. You must take some time and read through the Stickies, Howtos and original posts. Please.
You can easily root (using cf-autoroot - may have to install Superuser from playstore afterwards) and then put a custom recovery (also easily done by installing GooManager and then selecting install custom recovery CWM or TWRP etc) on stock 4.3 that has knox.
From there you can then change/install whatever recovery you want and whatever 4.3 ROM you choose.
BUT I'd highly suggest you take some time, slow down and read, read a little more then after that read some more before you turn your new phone into a shiny paper weight.
leaderbuilder said:
I think you are possibly a little over your head. You must take some time and read through the Stickies, Howtos and original posts. Please.
You can easily root (using cf-autoroot - may have to install Superuser from playstore afterwards) and then put a custom recovery (also easily done by installing GooManager and then selecting install custom recovery CWM or TWRP etc) on stock 4.3 that has knox.
From there you can then change/install whatever recovery you want and whatever 4.3 ROM you choose.
BUT I'd highly suggest you take some time, slow down and read, read a little more then after that read some more before you turn your new phone into a shiny paper weight.
Click to expand...
Click to collapse
Yeah I'll check around and see if I come up with anything. I'm not particularly new to this if you can't tell. I've rooted and customized 2 different phones, as well as jailbroke, themed, and flashed stuff to my ps3 back when it was possible. I rooted and flashed sacs v4 rom and ktoonsez kernel easily almost immediately after getting the phone a few months ago. I'm currently running a rooted, stable, stock 4.3 MJA everything so I guess I'm gonna wait and see if anything new surfaces. I have a suspicion that something is writing over CWM with the stock recovery when I boot into the rom but I don't know what to do about it. GooManager won't install openrecovery for some reason either, I already tried that. Just stalls at the download page. Thanks for the help anyway guys.
If you can get into download mode there is no reason that a custom recovery shouldn't install via PC Odin.
You can try this.
Grab the recovery .tar Launch Odin (make sure to 'Run As Administrator') place the .tar in the PDA slot and make sure you un-check "Auto Reboot".
Once it installs (Pass) take phone off PC, remove battery.
Put battery back in and then boot straight to recovery - Home button, Volume Up and Power button till you see the very little blue 'entering recovery' at the top left. If you get into recovery just choose the 'restart phone option. Or you might want to step through the Philz menus then back out to the Power Options then Reboot system and then 'fix root' and let it reboot.
Ok so I was running CM 11 while i was on MK2 firmware....i flashed a wrong file now i am stuck, I can get into download mode.
My device is Sprint Galaxy S4 running the MK2 firmware, but i have no idea where to go because it will not boot up anymore and only goes into download mode, any ideas on how to fix?
Thanks
i flashed a wrong file now i am stuck
Click to expand...
Click to collapse
Boy that could be bad...
BUT if you get to Download mode you may be able to grab the full MK2 Odin-able .tar you should be Okay.
Please note that the sph-L720 is NOT the L720T. If you have that version and you flash this .tar you'll be hosed.
leaderbuilder said:
Boy that could be bad...
BUT if you get to Download mode you may be able to grab the full MK2 Odin-able .tar you should be Okay.
Please note that the sph-L720 is NOT the L720T. If you have that version and you flash this .tar you'll be hosed.
Click to expand...
Click to collapse
Ok thanks, i will try this and let you know later after its all downloaded and what happens!
RogSeve said:
Ok thanks, i will try this and let you know later after its all downloaded and what happens!
Click to expand...
Click to collapse
Make sure to Run Odin 'as administrator'.
From the zip just extract the .tar.md5 and place that into the PDA slot. Odin 3.09 seems to be working the best for most on this device.
leaderbuilder said:
Make sure to Run Odin 'as administrator'.
From the zip just extract the .tar.md5 and place that into the PDA slot. Odin 3.09 seems to be working the best for most on this device.
Click to expand...
Click to collapse
Yup just downloaded that odin actually, but i have to wait about an hour for that mk2 file to download. And thanks i know I've actually done this before but on mf9 so it was a little easier. Will this bring me back to stock?
Thanks
RogSeve said:
Yup just downloaded that odin actually, but i have to wait about an hour for that mk2 file to download. And thanks i know I've actually done this before but on mf9 so it was a little easier. Will this bring me back to stock?
Thanks
Click to expand...
Click to collapse
You'll be stock everything - baseband(modem), kernel, recovery and ROM.
You will have the knox bootloader, so when you flash a custom recovery you'll 'trip' that. But not really a big deal. You can remove the 'Knox software(s) if you want - there are some removal scripts here in the forums. Only thing is you can't Odin back before MJA/MK2.
To root you can use CF-Autoroot or Saferoot, then use Goomanager or find a recovery zip here and install custom recovery of your choice.
leaderbuilder said:
You'll be stock everything - baseband(modem), kernel, recovery and ROM.
You will have the knox bootloader, so when you flash a custom recovery you'll 'trip' that. But not really a big deal. You can remove the 'Knox software(s) if you want - there are some removal scripts here in the forums. Only thing is you can't Odin back before MJA/MK2.
To root you can use CF-Autoroot or Saferoot, then use Goomanager or find a recovery zip here and install custom recovery of your choice.
Click to expand...
Click to collapse
Ill try that later if it works, i might just stay on stock mk2 don't wanna mess anything else up....lol
RogSeve said:
Ill try that later if it works, i might just stay on stock mk2 don't wanna mess anything else up....lol
Click to expand...
Click to collapse
Ok so now when i try to open it up in odin it says hash value is invalid....any ideas on what to do for that?
leaderbuilder said:
You'll be stock everything - baseband(modem), kernel, recovery and ROM.
You will have the knox bootloader, so when you flash a custom recovery you'll 'trip' that. But not really a big deal. You can remove the 'Knox software(s) if you want - there are some removal scripts here in the forums. Only thing is you can't Odin back before MJA/MK2.
To root you can use CF-Autoroot or Saferoot, then use Goomanager or find a recovery zip here and install custom recovery of your choice.
Click to expand...
Click to collapse
Ok when i try to open the mk2 file it keeps saying the md5 hash is invalid. Ive tried 3 different odins to open it and i get the same result..
You don't open the .tar.md5 file.
You place this file - L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 in the PDA slot.
RogSeve said:
Ok so I was running CM 11 while i was on MK2 firmware....i flashed a wrong file now i am stuck, I can get into download mode.
My device is Sprint Galaxy S4 running the MK2 firmware, but i have no idea where to go because it will not boot up anymore and only goes into download mode, any ideas on how to fix?
Thanks
Click to expand...
Click to collapse
have you tried heimdall? its unbricked me a few times, and its way easier to use too. i think you can use ob both windows and mac, i used on mac. if you are familiar with how to use a command line tool or terminal, this is the way to go. just my humble opinion.
guys ii really need some help.
i downloaded BTU-N9005XXUENB7-20140310153913 and flashed it via odin while in download mode. the flash was successful but now all im seeing is "recovery booting" on the phone and its just staying there?
ii was on stock rom 4.3 rooted with custom recovery before flashing the 4.4.2 file in odin. have i f****d my phone?
i did the same thing as i did last time iand it worked but im not sure whats going on here?
please can someone help me please:crying::crying::crying::crying:
Same happened to me when i used mobile Odin. The bootloader wasn't updated.
Did you use Odin 1.85? And did you tick the option update new bootloader? If not do that.
If did that then wipe cache and data reset from recovery.
kenny1991 said:
Same happened to me when i used mobile Odin. The bootloader wasn't updated.
Did you use Odin 1.85? And did you tick the option update new bootloader? If not do that.
If did that then wipe cache and data reset from recovery.
Click to expand...
Click to collapse
yeah i used the wrong version of odin. i used 1.85 now its working, but i didnt select update bootloader, how do i know if it updated the bootloader?
You know if the phone is up and running. Kitkat can't boot without new bootloader. So if the phone is working there is no issues.
kenny1991 said:
You know if the phone is up and running. Kitkat can't boot without new bootloader. So if the phone is working there is no issues.
Click to expand...
Click to collapse
last thing. im trying to install TWRP . i have the tar file from their site. i used odin 1.85 and 3 and flashed pda. odin says its done but it wont boot into TWRP it just reboots.
edit: i used mobile odin and its all good thanks for all your help
You welcome
thedan55 said:
last thing. im trying to install TWRP . i have the tar file from their site. i used odin 1.85 and 3 and flashed pda. odin says its done but it wont boot into TWRP it just reboots.
edit: i used mobile odin and its all good thanks for all your help
Click to expand...
Click to collapse
just FYI,
if you want to flash TW custom ROM, the best you use is Chenglu CWM. So far I seldom see user complain got problem during flashing with this CWM.
TWRP, some users got problem, some are not.