I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)
bounddyy said:
I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)
Click to expand...
Click to collapse
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5
leaderbuilder said:
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5
Click to expand...
Click to collapse
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?
bounddyy said:
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?
Click to expand...
Click to collapse
If you can get into recovery now (philz). You can certainly flash Sac's 4.3. If you want the mf9 modem that is in the dev section too. Check out Unknownforce's post
But I suspect you've taken the mja "firmware" and tripped that Knox counter, and if that's the case I dint believe you can Odin back to mf9.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app
bounddyy said:
Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
well that didn't workout so i figured out that i shouldnt let my phone reboot after flashing Philz recovery and instead directly force into recovery and it worked but now i need to just flash it thourgh there lol
Related
I just got a replacement Galaxy S4 today. I didn't even bother to check what ROM it was on because I didn't think to pay attention. I flashed CWM with a tool (http://forum.xda-developers.com/showthread.php?t=2297033) and CWM booted fine. I went to install the Paranoid Android 4.3 beta, and all went as planned. I rebooted, and it just hung on the Paranoid Android boot screen. If I then turn the phone off and reboot, it get stuck on the Samsung locked screen. I'm praying I didn't brick this thing for good, but reading about the MF3 headaches, I'm not so sure. Can anyone offer some insight? I can't access USB in CWM either.
Edit: The box says SW-VER: 1337UCUAMDL; does that mean I'll be able to odin to stock?
geokhentix said:
I just got a replacement Galaxy S4 today. I didn't even bother to check what ROM it was on because I didn't think to pay attention. I flashed CWM with a tool (http://forum.xda-developers.com/showthread.php?t=2297033) and CWM booted fine. I went to install the Paranoid Android 4.3 beta, and all went as planned. I rebooted, and it just hung on the Paranoid Android boot screen. If I then turn the phone off and reboot, it get stuck on the Samsung locked screen. I'm praying I didn't brick this thing for good, but reading about the MF3 headaches, I'm not so sure. Can anyone offer some insight? I can't access USB in CWM either.
Edit: The box says SW-VER: 1337UCUAMDL; does that mean I'll be able to odin to stock?
Click to expand...
Click to collapse
If you are on AT&T MDL firmware you should be able to ODIN to stock, do a factory reset and take it from there. I suggest you do a lot more reading before you touch anything else. You can start by reading the "pinned" threads in the General section. Everything you need you will find there. Good luck
You need to flash Loki doki after each custom ROM if you're in CWM or any non auto loki'd recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
djpharoah said:
You need to flash Loki doki after each custom ROM if you're in CWM or any non auto loki'd recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
What he said...you are not on mf3 dont worry about that...if you were on mf3 you wouldny have been able to even get a recoveryjust odin to stock and start over...either find and use the "loki doki" zip (google can find it) and flash it after every rom flash or use the auto loki recovery which pretty much runs the loki doki script every rom rom flash for you right before it reboots
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
What he said...you are not on mf3 dont worry about that...if you were on mf3 you wouldny have been able to even get a recoveryjust odin to stock and start over...either find and use the "loki doki" zip (google can find it) and flash it after every rom flash or use the auto loki recovery which pretty much runs the loki doki script every rom rom flash for you right before it reboots
Click to expand...
Click to collapse
The tool he linked contains auto-loki CWM so I'm not sure that's his problem.
Definitely ODIN back to stock with this procedure:
http://forum.xda-developers.com/showthread.php?t=2261573
Using the MDL download you can find here:
http://forum.xda-developers.com/showthread.php?t=2263533
And try again! Make sure you read the stickies in the general forum too.
Can someone please help me get out of this soft brick because I am really stuck. Currently I am getting the error message that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." but I have done that and it has failed on both mac and windows 7. I have also tried flashing stock build UCUAMDL 4.2.2 firmware via odin 1.7, 1.85 and 3.07 and I have also used the PIT files along with re-partitioning and F. Reset Time. Every single time in odin it has gotten to system.img.ext4 and then failed immediately following. A couple of times I have been able to get into stock recovery mode and it stated an error that the /system partition could not be accessed and I wiped cache/system/data and then tried rebooting and it stayed in the big white galaxy s4 letters and didn't even go to the boot logo. Based on this can anyone help me please???? If there's an existing thread can you please let me know? Thanks!
Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
sounds like you wiped your phone when you wiped system/data, why did you do that
you have nothing to boot
kies don't work with iMac
yeah give all the phone info you have, model, build, etc. build may be on your box
i think you can now only flash stock firmware thru Odin to recover, but if you were mf3, you may need to go to bestbuy and see samsung reps to flash phone. don't have any experience at that or using odin
stay on windows pc to do this
may be tomorrow till you get some help from others
good luck
RAID Xero said:
Which model do you have? What firmware are you on?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sorry I forgot to mention that it's a SGH-I337 as well and I was running the jamal 4.3 AOSP ROM
well then you are with what custom recovery?
and you are not mf3
sounds like the mf3 update was trying to flash. did you not delete the update files with Titanium so the Update would not run
can you boot into recovery and restore a nandroid
---------- Post added 2nd October 2013 at 12:00 AM ---------- Previous post was 1st October 2013 at 11:54 PM ----------
i gotta call it a nite. maybe some west coasters can help since they are 3 hours behind us
but, please don't say you don't have a nandroid--
i think this is fixable--:good:
restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app
Kelevra_96 said:
restoring a nandroid backup could solve your problem, did you try flashing with fastboot instead? When you installed AOSP ROM were you using a toolkit? If so did you flash a temp recovery?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you have an i337. We don't have fastboot. Our bootloader is locked.
Sent From My SGH-I337 Using Tapatalk 4
What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app
Br4nd3n said:
What custom recovery are you using?
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?
adambombz said:
I don't have one, although do you think that I can flash a custom recovery with a PIT file because that seems to be the only thing that works. Also I do not have a nandroid backup. Is there somewhere that I can download someone's already made?
Click to expand...
Click to collapse
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.
jd1639 said:
It's been asked a couple of times, but do you know what firmware your phone was on? It's important to know to be able to help you.
Click to expand...
Click to collapse
I was running a custom ROM AOSP 4.3 that's all I know sorry
adambombz said:
I was running a custom ROM AOSP 4.3 that's all I know sorry
Click to expand...
Click to collapse
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.
also, if you are running a custom rom you have a custom recovery
cwm or twrp?
jd1639 said:
That's close enough. That means you aren't on mf3.
Edit, have you tried to odin the stock firmware? Never mind I see you have
I would download the stock firmware from sammobile.com and try Odin again on a pc. Either version of odin is ok, 1.85 or 3.07.
When you use Odin only have auto-reboot checked, Don't check re-partition.
Click to expand...
Click to collapse
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.
rugmankc said:
also, if you are running a custom rom you have a custom recovery
cwm or twrp?
Click to expand...
Click to collapse
They key word here is that I WAS running a custom recovery when all of this started. It was actually the recovery that started all of this. What happened specifically was I tried to update TWRP via goo manager and whenever I tried to go into recovery it gave me the error that at&t has detected unauthorized software on my phone which I thought was weird because I believe that goo manager auto-lokis. Anyway I tried using other apps to add a custom recovery like ROM manager by clockworkmodz and nothing worked. I then tried to flash TWRP 2.6.3.0 via odin and that's what sent my phone into the state that it's in now. Something that confuses me even more is is that whenever I plug in my phone a battery logo comes up that I don't recognize and then freezes.
adambombz said:
I have tried doing this many, many times and each time it gets to the system.img.ext14 and then fails.
Click to expand...
Click to collapse
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file
When you get it sorted use twrp 2.5.0.2. I think I posted a zip for you.
jd1639 said:
Have you re-downloaded the firmware? It could be a bad download. Are you using the .tar.md5 file
Click to expand...
Click to collapse
Yes I have tried multiple files and builds and I am using .tar.md5
adambombz said:
Yes I have tried multiple files and builds and I am using .tar.md5
Click to expand...
Click to collapse
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.
jd1639 said:
When you flashed twrp with odin are you sure it was for your device? I think you might have borked your partitions.
Click to expand...
Click to collapse
That is possible, I know what is causing this has something to do with the partitions being messed up since I can't access /system in the stock recovery mode
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.
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
its been my experience with philz recovery once you factory reset you have to go into power menu and reboot into recovery again and then flash rom
loumoli said:
its been my experience with philz recovery once you factory reset you have to go into power menu and reboot into recovery again and then flash rom
Click to expand...
Click to collapse
So you are saying that Once I flash the Rom
1. Go back to Recovery and Do a factory Reset
2. Re-Flash the Desired Rom.
I tried this too.
Its not just Philz Recovery. I user CWM Recovery as well and having similar issues.
[email protected] said:
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
Click to expand...
Click to collapse
Use PC Odin to flash Philz latest recovery.
But in Odin don't check the "Auto Reboot". When Odin is finished unplug the phone and hard power it off or batter pull.
Edited for clarity - Meant AutoReboot
leaderbuilder said:
Use PC Odin to flash Philz latest recovery.
But in Odin don't check the f.reset. When Odin is finished unplug the phone and hard power it off or batter pull.
Click to expand...
Click to collapse
i will give this a try today after work.
Will let you know
[email protected] said:
i will give this a try today after work.
Will let you know
Click to expand...
Click to collapse
Meant - "Auto Reboot". Didn't have enough coffee yet.
leaderbuilder said:
Meant - "Auto Reboot". Didn't have enough coffee yet.
Click to expand...
Click to collapse
So when i did install custom Rom I am stuck on Samsung Galaxy s4 Screen
With Error
KERNeL IS NOT SEANDROID ENFORCING ( RED color)
Set Warranty Bit : Kernel (Yellow Color)
Its about 10 Minutes now and I will leave it that way for 1 more hour.
Update: its been 30 mins and am still stuck in that screen.
I'm curious as to what ends up happening with this. I was reading how to flash a custom rom, by using Clockworkmod Recovery.
It looks like the CWM is flashed in via ODIN after the root as a .tar.md5, then you factory reset/wipe data, then wipe cache, then wipe davilk cache, then install from .zip extSDcard. It seemed simple enough, and I have the same model as you, but it appears there are hang ups that you are having which I'll wait until I try it.
I also have stock ROM and MK2 GS4 with Sprint.
[email protected] said:
So when i did install custom Rom I am stuck on Samsung Galaxy s4 Screen
With Error
KERNeL IS NOT SEANDROID ENFORCING ( RED color)
Set Warranty Bit : Kernel (Yellow Color)
Its about 10 Minutes now and I will leave it that way for 1 more hour.
Update: its been 30 mins and am still stuck in that screen.
Click to expand...
Click to collapse
Reflash a ROM
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Reflash a ROM
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Did So. And no changes.
Stuck in The same screen.
[email protected] said:
Did So. And no changes.
Stuck in The same screen.
Click to expand...
Click to collapse
Forgot you have to wipe data. And fdont flash any kernel or anything like that.
Sent from my SPH-L720 using Tapatalk
[email protected] said:
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
Click to expand...
Click to collapse
make sure to wipe delvic and cache and what is the error, it sounds like a bad download possibly
deneid310 said:
make sure to wipe delvic and cache and what is the error, it sounds like a bad download possibly
Click to expand...
Click to collapse
No you get that error when you trip Knox. Well at least it did for me.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
No you get that error when you trip Knox. Well at least it did for me.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
How did you Pass that?
[email protected] said:
How did you Pass that?
Click to expand...
Click to collapse
By rooting with saferoot in Verizon forum or kingo app
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
By rooting with saferoot in Verizon forum or kingo app
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
If you root with safe root you are correct, you won't trip the knox warranty flag. But you can't install a custom rom without flashing a custom recovery which is what actually trips the knox flag not root. So safe root is only good if you are going to run stock rooted and not install a custom rom.
[email protected] said:
How did you Pass that?
Click to expand...
Click to collapse
My sprint s4 with Philz does the same exact thing, gets stuck at the same screen. Sometimes it takes a few then boots up , other times I have to manually reboot it.
I've tried many things myself and still this problem confines.
I've asked in other threads about this but no one had an idea of way.
The phone was on MK2, rooted with CF Auto, and has latest Philz.
I'll be checking in here to see if we can fix this... If it's even fixable. I think it has to do with Knox /new security.. But I'm no programmer so maybe a pro can chime in.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hoping for some experts to help us.. May be a video on how to root of MK2 version And flash custom Rom will help us..
Sent from Sprint GS4
Hello.First post here.
I currently have been using CM11 for a few months now but miss some features on stock. (multiwindow, air view) so I installed Sacs ROM.
Everything was working great today except a known problem is wifi will not work due to radio opbstructions (i believe). So i attempted to change the baseband to MF9.
At first, Odin started then immidately it failed. The error read 'Fused 4 Binary 1'
So i assumed it was a connection error. I loaded back into download mode and tried again. Failed.
At this point i thought screw it, and took the battery out. tried to reboot and stuck at the soft brick "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I installed Kies. Plugged in my phone. Drivers installed but Kies will not connect. Try to do 'Firmware Upgrade and Initialization'
However Kies will NOT accpet my S/N number. i tried everything. writing it all out or with a space every 3 numbers or with 'DEC' at the front. nothing worked.
I even called sprint to double check S/N (ESN/DEC)
so basically I'm soft bricked and Kies is screwing me over. Any ideas?
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
ROMANTiC KiD said:
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
whatthe_fuzz said:
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
Click to expand...
Click to collapse
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
whatthe_fuzz said:
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
Click to expand...
Click to collapse
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i searched around and eventually found a working .md5 file. its apparently is stock. got my phone to start booting but it got stuck at the yellow sprint screen. im going to try to boot into safe mode. any ideas how to access my recovery file? i have one form CWM and one from Ti Backup
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
leaderbuilder said:
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
Click to expand...
Click to collapse
I think i fixed it.
Problems resolved.
The issue was i had Sacs v4 which didnt support wifi and i read that it needed MF9 firmware.
i had a lapse in judgement and without thinking tried to go back from MJA. didnt catch it until now.
I eventually found the correct stock file. eventually got into the phone. rerooted and in the process of install the proper sacs ROM (v5.6)
this was a simple error that i shouldve caught thanks guys!
hopefully this ROM will work with wifi...
BTW, all my backups were wiped
Your backups weren't on your external sd? Ooo, that sucks. Glad you got it.
Sent from my SPH-L720 using XDA Premium 4 mobile app