Has any found an image with Android 4.2.2 but with the 4.2.1 Baseband?
My connection/service has been horrible since the update. I went back to 4.2.1 just to see, and sure enough connection/service was great.
I would like to update to 4.2.2 but I need the Baseband from 4.2.1 so I won't constantly loose my connection/service.
I'm running stock and with no intentions of rooting, so If root is require to have a different baseband within 4.2.2 then I guess I'll be stuck on 4.2.1 for good.
Thanks for any help given, its much appreciated.
Edit: Nevermind, got it.. I just flashed the radio img through fastboot (required quick unlock, then lock)
UberSlackr said:
Has any found an image with Android 4.2.2 but with the 4.2.1 Baseband?
My connection/service has been horrible since the update. I went back to 4.2.1 just to see, and sure enough connection/service was great.
I would like to update to 4.2.2 but I need the Baseband from 4.2.1 so I won't constantly loose my connection/service.
I'm running stock and with no intentions of rooting, so If root is require to have a different baseband within 4.2.2 then I guess I'll be stuck on 4.2.1 for good.
Thanks for any help given, its much appreciated.
Click to expand...
Click to collapse
There's no stock ROM with the combination you want. Though haven't you tried flashing the .33(4.2.1 baseb) while on 4.2.2?
http://forum.xda-developers.com/showthread.php?t=2087227
Ace42 said:
There's no stock ROM with the combination you want. Though haven't you tried flashing the .33(4.2.1 baseb) while on 4.2.2?
http://forum.xda-developers.com/showthread.php?t=2087227
Click to expand...
Click to collapse
Yeah, I did. Shortly after posting...
when I first tried to do a search for the .33 (4.2.1) Baseband I came up empty handed, but changed a couple search terms and got it right away...
Thank for the info though..
Its ridiculous how much the Baseband (radio) from 4.2.2 messes with service connection.
Im sitting at my office desk, when baseband from 4.2.2 was being used I got maybe 3 bars of service, but mostly just 2 bars (and would drop - grey out - every now and then)
Now when using the Baseband from 4.2.1 (.33) in the 4.2.2 update, I gave full service... drops to 3 for a second, but goes right back to all 4 quickly
Related
I just want to let everyone know that it is possible to go back to ICS after updating to 4.1.2(9.16.6) I was rooted on 4.1.1 today, used ota root keeper to temp unroot and update to 4.1.2 and restore root. I just used Matts RazrHD utility 1.10 and went back to ICS 4.0.4 with no problems what so ever...
Im not sure why its stated that once you update to the newest release that you cannot go back, but its possible. So for everyone that wants to try out 4.1.2 and didnt want to be stuck, you can downgrade.
Hope this helps.
Also for everyone willing to try to downgrade please post results and type of phone you have, also the way you downgraded...
Device: Razr HD XT926 US Verizon non dev ed.
Original firmware 4.0.4(0.6.25)
Used RazrHD Utility 1.10 to downgrade
UPDATE: 3/21
I tried to downgrade again so I can post screen shots for everyone, and it did not work this time!!! Something must have changed/sync'd with my phone since the last time I downgraded that did not sync the first time. This has been a strange experience, but I would not have posted if I really did not have success the first time! It now gives errors, and I have tried everything I could imagine. My phone is not bricked and I am still rooted and have SS.
Preserving the option to downgrade to ICS is certainly important to me. Please, what phone do you have and from what country is your carrier (and thus, presumably, your version of stock ICS)?
lesdense said:
Preserving the option to downgrade to ICS is certainly important to me. Please, what phone do you have and from what country is your carrier (and thus, presumably, your version of stock ICS)?
Click to expand...
Click to collapse
XT926 Verizon US non dev edition, ICS 4.0.4 (0.6.25)
I will add it to the OP
OK ... I've got to know. Why did you leave 9.1.2 immediately after upgrading to it? The knowledge that downgrading back to 4.0.4 from 4.1.2 is certainly valuable, but knowing what prompted you to upgrade and then so quickly downgrade would be valuable to know as well. Did the upgrade go smoothly? Did the upgrade not function as expected?
lesdense said:
OK ... I've got to know. Why did you leave 9.1.2 immediately after upgrading to it? The knowledge that downgrading back to 4.0.4 from 4.1.2 is certainly valuable, but knowing what prompted you to upgrade and then so quickly downgrade would be valuable to know as well. Did the upgrade go smoothly? Did the upgrade not function as expected?
Click to expand...
Click to collapse
No it was fine... I had some weird problems with data switching, from wifi to mobile... Sometimes it wouldn't switch back to mobile after turning off wifi but that was only a couple of times. I really just wanted to see if it was possible to downgrade and was willing to do it even though I could of been stuck without a phone. I also like to start fresh by downgrading and wiping/formatting my sd card every month or so. Im back on 4.1.1 now and will probably go to 4.1.2 soon on my stock slot either way.
What I did was Remote into a DROID RAZR HD owner's computer and flash the ICS boot.img file through fastboot. It failed pre-flash validation so I flashed to new boot.img back on there and considered it a case closed.
If it works to go back by using the Utility, thats great news. However I am not going to remove the warning until I get more than just one confirmation on it.
great news thx
Sent from my DROID RAZR HD using xda app-developers app
I have JB 4.1.2 now and using Matt's tool, I can't seem to get it to downgrade. It will run through the process, then it will just boot up into 4.1.2 again. It gets a couple failed things along the way.
Because I'm still weighing whether to upgrade to 4.1.2 can you tell me -- did you get 4.1.2 OTA or did you flash a file? If you did a "manual" upgrade, how is the experience? Problems? Anything not working, or not working right?
Ota, everything went fine during the upgrade. Just make sure if you are rooted to activate stock slot and wipe all other slots. I also restored a backup of stock jb 4.1.1 I made a week ago with all apps updated and working. Then just booted up and temp unrooted with ota root keeper and accepted the ota. Restored root after it booted. Only thing that was different from other updates is that safe strap did not work afterwards so I had to uninstall and reinstall.
I don't see much improvement, but I just got back to 4.1.2 late last night after downgrading so that's not much time to tell if the improvements are there. I have not tried HDMI out yet,but will later today.
If anyone else tries to downgrade to stock 4.0.4 ICS from this latest update 4.1.2, please post what type of phone you have and if it worked for you. Any problems...???
Sent from my XT926 using Tapatalk 2
an21281 said:
Ota, everything went fine during the upgrade. Just make sure if you are rooted to activate stock slot and wipe all other slots. I also restored a backup of stock jb 4.1.1 I made a week ago with all apps updated and working. Then just booted up and temp unrooted with ota root keeper and accepted the ota. Restored root after it booted. Only thing that was different from other updates is that safe strap did not work afterwards so I had to uninstall and reinstall.
I don't see much improvement, but I just got back to 4.1.2 late last night after downgrading so that's not much time to tell if the improvements are there. I have not tried HDMI out yet,but will later today.
If anyone else tries to downgrade to stock 4.0.4 ICS from this latest update 4.1.2, please post what type of phone you have and if it worked for you. Any problems...???
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
You don't have to wipe your rom slots.just go back to stock slot take the ota and then reinstall safestrap recovery (not the program).your roms will still be there and functional.
Sent from my DROID RAZR HD using Tapatalk 2
Don't know how I've missed all this "stock slot, rom slots" business. I've rooted Android phones and tablets, installed custom ROMs, I've still a noob but learning. Does "slots" refer to all that sdcard0, sdcard1, usbdisk_1.0 business in /storage? I don't think I'd seen that on any of my devices until I got my Maxx HD with 4.1.1. Or are slots part of SafeStrap (I have that too but only because it was on my phone when I bought it on eBay)? Upgrading to 4.1.2 sounds like it goes smoothly if you do it right and is a pain if you don't. Sure would appreciate a little guidance that's specific to this set of tasks.
Well I feel like an idiot. I got the leaked 4.1.2 and now it's literally impossible to downgrade. I hadn't installed any bootloaders/roots/ or anything before doing this, so now that my phone is 4.1.2, it's basically stuck there.
I've tried hours and hours of everything. If anyone has any idea on how to bypass this I'd be grateful.
Mystique5022 said:
Well I feel like an idiot. I got the leaked 4.1.2 and now it's literally impossible to downgrade. I hadn't installed any bootloaders/roots/ or anything before doing this, so now that my phone is 4.1.2, it's basically stuck there.
I've tried hours and hours of everything. If anyone has any idea on how to bypass this I'd be grateful.
Click to expand...
Click to collapse
Not sure why it wont work for you, but Im going to downgrade again and post up screen shots and a vid. also. Just waiting for my phone to charge.
only ocigrarn
an21281 said:
Not sure why it wont work for you, but Im going to downgrade again and post up screen shots and a vid. also. Just waiting for my phone to charge.
Click to expand...
Click to collapse
Did you do this procedure from stock? I tried from 100% stock. No unlocked bootloader, no root, nothing. I'm also using a Verizon Phone.
an21281 said:
I just want to let everyone know that it is possible to go back to ICS after updating to 4.1.2(9.16.6) I was rooted on 4.1.1 today, used ota root keeper to temp unroot and update to 4.1.2 and restore root. I just used Matts RazrHD utility 1.10 and went back to ICS 4.0.4 with no problems what so ever...
Im not sure why its stated that once you update to the newest release that you cannot go back, but its possible. So for everyone that wants to try out 4.1.2 and didnt want to be stuck, you can downgrade.
Hope this helps.
Also for everyone willing to try to downgrade please post results and type of phone you have, also the way you downgraded...
Device: Razr HD XT926 US Verizon non dev ed.
Original firmware 4.0.4(0.6.25)
Used RazrHD Utility 1.10 to downgrade
Click to expand...
Click to collapse
No you cant.
thewahlrus said:
No you cant.
Click to expand...
Click to collapse
I downgraded successfully yesterday, so I reported my experience... I have no reason to lie, otherwise I would not have posted this in the first place!
I had some problems with my comp. and the usb/moto drivers on win7 today so I was trying to fix that before I could try again. I attempted to downgrade/restore to ICS again and this time it did not work! I cant see how it worked for me yesterday and today it wont? I was so happy when it worked, but something must have changed within the last day which is odd. I always upgrade and root the same way, and I have tried everything today to get it to downgrade with no luck. My phone still works so it is not bricked, and I apologize to everyone, like I said it did downgrade yesterday with the RazrHD utility 1.10 and there were no errors what so ever. Now after it asks you to hit any key once the phone comes back on in FB errors come right up. Some things seem to flash though, which is strange and basically it does a factory reset on the 4.1.2 . SS is still installed, its still rooted, and works fine. I can even restore back up of 4.1.1 stock jb(which I made last night after I downgraded to ICS and was upgrading again) on stock slot after wiping data/cache/dalvic and system and boot up to show 4.1.1 and then either try to downgrade, which fails, or take the ota and/or flash 4.1.2 manually but it fails also. Then I just reflash a back up of 4.1.2 and its fine IDK... I also flashed Vit 1.9.3 on stock slot fine, boots etc. but still wont let me downgrade. Then I tried uninstalling all updated apps on 4.1.2 and clearing data on all apps, still nothing.
So for some reason it let me successfully downgrade yesterday, but not anymore. So like many people have said do not try until there's a safe way, unless you are willing to risk bricking.
I am downloading the 4.1.2 fastboot files now.
mattlgroff said:
I am downloading the 4.1.2 fastboot files now.
Click to expand...
Click to collapse
You're amazing.are you a moto insider lol
Sent from my DROID RAZR HD using Tapatalk 2
koftheworld said:
You're amazing.are you a moto insider lol
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
I have friends in the Firmware Team
This is my 1st post ever because every question I've ever needed answered I've been able to find.Unfortunately I cannot find the answer to this problem. Since my Post count is below 10 I cant post the question in Kangabeans thread.
This is the ROM I am using
I rooted and flashed my phone 4 days ago and ever since then my wifi or mobile connection never go above 2 bars. Everything works except data cuts in and out fairly often which never happened before while i was using stock. I can sometimes get LTE but it mostly just says H and is really slow. I live right in the middle of downtown Edmonton and always had an LTE connection before so I'm pretty sure it is an issue with my phone and the ROM. I can also be standing right next to my wireless router and i only have 2 bars showing up for wifi.
I know some people had mentioned similar problems in the Kangabean thread with poor LTE connections but almost all say it is working good which leads me to believe its something I've done. My initial thought to fix the issue was to flash a new modem, specifically this one modem_CWM_I337MVLUAMDJ.zip{4/22/2013}(Canada) from this thread because everyone that was saying their LTE and WIFI were working appeared to be on an MDJ baseband. I tried flashing the modem and nonhlos through Odin but it failed with odin saying: Failed, Receive response from LOKE. I figured my best course of action was to try and reflash the MG1 Baseband but again i recived the Failed, Receive response from LOKE. Thinking i screwed something up i decided to try and boot up my phone and sure enough i was stuck in a bootloop. Luckily all I had to do was load up recover and wipe the cache partion.
Everything is back as it was before i tried flashing the modems, even the poor connection to WIFI and Data.
Does anyone have any idea as to how I can fix this or what I did wrong that caused Odin to fail flashing??
Pretty sure I just found my answer for why I cant flash the modem. Im pretty sure MG1 is newer than MF3 (correct??) and if your on MF3 Odin wont work
I was doing some thinking..... I have mobile odin pro Can I try flashing the MDJ or MF3 Modem and nonhlos files with it or will it too end up failing??
Suyneej said:
I was doing some thinking..... I have mobile odin pro Can I try flashing the MDJ or MF3 Modem and nonhlos files with it or will it too end up failing??
Click to expand...
Click to collapse
Wow hold on! Do you have telus sgh-i337m s4? If so then you don't need anything to do with mf3. Only att and sprint have lockedbootloader. If your baseband is MDB or MDJ then you don't need Loki and mf3 kernel, in fact you'll brick your phone if flash mf3 kernel on any s4 brought in Canada.
You shouldn't be going anywhere near MF3 on your i337m. MG1 or MDJ only for us Canadians
Thanks guys I wasnt sure If I could flash those without any problems so I was waiting for someone to reply to this thread before i tried going that route to fix my connectivity issue again.
Sorry guys,
I am a Canadian with a 1337m MDJ S4 running CM 10.2
I just wanted to double check that I am bound to ROMS made for MDJ. Cannot I not update to MDL?
There are a number of TW Roms that I would like to try to get my camera and multiwindow options back Like :
FoxHound GearEngine 1.3 AROMA OR Eclipse.
Your feedback would be amazing.
Thank you
Thank God im not the only one. Look at my thread http://forum.xda-developers.com/showthread.php?t=2455955
maybe we can find a solution together. Im using CM 10.2 but i live in Mexico son i had to flash my carrier's modem and it seems its coming back to normal but im not totally shure... still testing this modem (all info is on my thread)
Let me know if you find a fix... thanks
Sent from my SGH-I337M using xda app-developers app
After I have upgraded my bootloader and radio to JWR66V using the factory image. Can I still use the 4.2 rom such as cm10?
csunny95 said:
After I have upgraded my bootloader and radio to JWR66V using the factory image. Can I still use the 4.2 rom such as cm10?
Click to expand...
Click to collapse
Yes, you can do so.
OhDae-su said:
Yes, you can do so.
Click to expand...
Click to collapse
But will there any impact or improvement if I use 4.3 bootloader and radio on 4.2 rom?
csunny95 said:
But will there any impact or improvement if I use 4.3 bootloader and radio on 4.2 rom?
Click to expand...
Click to collapse
I upgraded the bootloader and radio, tried all the many variations of 4.3.
Went back to 4.2.2 and have had zero problems.
mrhiab said:
I upgraded the bootloader and radio, tried all the many variations of 4.3.
Went back to 4.2.2 and have had zero problems.
Click to expand...
Click to collapse
So, Do u suggest upgrading to 4.3 bootloader and radio?
csunny95 said:
So, Do u suggest upgrading to 4.3 bootloader and radio?
Click to expand...
Click to collapse
If you have not upgraded to the stock JWR66V ROM, you must upgrade the radio before you can flash a 4.3 custom ROM. If you have upgraded to the stock JWR66V ROM, you can flash back to a 4.2.2 ROM and keep the .84 radio and makoz20i bootloader without encountering problems.
csunny95 said:
So, Do u suggest upgrading to 4.3 bootloader and radio?
Click to expand...
Click to collapse
Eventually you're going to have to upgrade the bootloader. At least that's what molesarecomming said in his thread. Not so much with 4.3 but when KLP comes out you will.
I did mine because I was flashing P.A Ver 3.97 and it's says you have to flash new loader and radio to run the Rom. Or before you go posting that you're having issues at least.
The .84 radio has better performance, reception improved WIFI and battery life.
I average around 4 hours of ST a day with out any problems on it...but there are always factors that can sway battery life other than the radio.
You can always flash the Hybrid .33/.84 and have the best of both worlds...LTE and all the good things .84 brings with it.
mrhiab said:
Eventually you're going to have to upgrade the bootloader. At least that's what molesarecomming said in his thread. Not so much with 4.3 but when KLP comes out you will.
I did mine because I was flashing P.A Ver 3.97 and it's says you have to flash new loader and radio to run the Rom. Or before you go posting that you're having issues at least.
The .84 radio has better performance, reception improved WIFI and battery life.
I average around 4 hours of ST a day with out any problems on it...but there are always factors that can sway battery life other than the radio.
You can always flash the Hybrid .33/.84 and have the best of both worlds...LTE and all the good things .84 brings with it.
Click to expand...
Click to collapse
Do I need to flash the hybrid one in order to get the LTE? stock 4.3 bootloader has already comes with lte?
csunny95 said:
Do I need to flash the hybrid one in order to get the LTE? stock 4.3 bootloader has already comes with lte?
Click to expand...
Click to collapse
only the radios that ends with .27 or .33 are cabable to use LTE. the hybrid ones were designed to provide the best of two worlds as mentioned already above. So, most likely it would be recommended to use one of the hybrid ones for using LTE. try which one gives you the best results when it comes to recepetion, wifi perfomance etc.
the bootloader has nothing to do with all of that. Though use the latest one (bootloader-mako-makoz20i.img) would be the best advice. Regardless if u are using android 4.2.2 or 4.3
csunny95 said:
Do I need to flash the hybrid one in order to get the LTE? stock 4.3 bootloader has already comes with lte?
Click to expand...
Click to collapse
LTE is done through your radio not the bootloader and is disabled on all radios after .33
No you don't have to flash the hybrid to get LTE but you will need a .27/.33 radio then edit your buil.prop file to enable it.
That link earlier was to an AIO the does everything that needs to be done.
Only thing you might have to do is the *#*#4636#*#* then manually tell it LTE everything is in that link.
I've got it to work on every rom I've flashed.
Only thing is at least from my experiences is that if your on LTE it does use a little more battery...but so worth it IMO
I feel like I am either about to really break my phone or fix it with this next flash, some guidance would be amazing!
Started off months ago with Sprint L720 MF9 out of the box and rooted it. Eventually I got around to loading Sacs 4.3 back in January and had no troubles. After getting the OTA update notifications again, I decided it was time to flash a 4.4 ROM and I followed this thread.
Got the NAE modem loaded, flashed philz 6.08.9, and loaded the stock MK2 ROM listed in the instructions. The phone booted and I went through the initial setup without any issues. Baseband and software both say NAE, but then I noticed I have no sound at all. The phone powers off automatically after a while as well. Loading anything from the Play store takes forever, however, the stock web browser runs just fine.
Should I be concerned about no audio or will this be resolved with going to the 4.4 ROM listed in the guide (no data wipe)? I kind of want to flash a rooted stock MF9 ROM and start over...
Any help would be appreciated.
Edit: Flashed to 4.4.2 and SSDD. I finally got sound back though by flashing the MK2 modem, just need wifi working now.
Reckoned said:
I feel like I am either about to really break my phone or fix it with this next flash, some guidance would be amazing!
Started off months ago with Sprint L720 MF9 out of the box and rooted it. Eventually I got around to loading Sacs 4.3 back in January and had no troubles. After getting the OTA update notifications again, I decided it was time to flash a 4.4 ROM and I followed this thread.
Got the NAE modem loaded, flashed philz 6.08.9, and loaded the stock MK2 ROM listed in the instructions. The phone booted and I went through the initial setup without any issues. Baseband and software both say NAE, but then I noticed I have no sound at all. The phone powers off automatically after a while as well. Loading anything from the Play store takes forever, however, the stock web browser runs just fine.
Should I be concerned about no audio or will this be resolved with going to the 4.4 ROM listed in the guide (no data wipe)? I kind of want to flash a rooted stock MF9 ROM and start over...
Any help would be appreciated.
Edit: Flashed to 4.4.2 and SSDD. I finally got sound back though by flashing the MK2 modem, just need wifi working now.
Click to expand...
Click to collapse
Usually your sound issue can be resolved by flashing another ROM.
As far as WiFi goes I just had this problem myself. If your bootloaders NAE and your modem is MK2 , try flashing the NAE modem back. That's what fixed it for me.
I'll not up to speed on all the quirks of the sprint s4 since I'm usually using a Verizon s4 . but it seems to me that if you have a NAE bootloader, it isn't cooperating with downgrading the modem either. Never was a problem for me when my phone was on MK2 build , but with each OTA the security gets upgraded too. Almost doesn't make sense to me though as Sprints bootloaders are unlocked.
Maybe someone else can shed some light on this.
Try NAE modem and see what happens,... bet your WiFi will be back like mine was.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Usually your sound issue can be resolved by flashing another ROM.
As far as WiFi goes I just had this problem myself. If your bootloaders NAE and your modem is MK2 , try flashing the NAE modem back. That's what fixed it for me.
I'll not up to speed on all the quirks of the sprint s4 since I'm usually using a Verizon s4 . but it seems to me that if you have a NAE bootloader, it isn't cooperating with downgrading the modem either. Never was a problem for me when my phone was on MK2 build , but with each OTA the security gets upgraded too. Almost doesn't make sense to me though as Sprints bootloaders are unlocked.
Maybe someone else can shed some light on this.
Try NAE modem and see what happens,... bet your WiFi will be back like mine was.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm actually still on MF9 bootloader. I did end up flashing back NAE modem last night and battery pulled after. All is working now! Thanks.
So I have been running an OLD version of SACS Custom Rom on my Sprint S4 (Think MF9 / MDL time frame).
I was working great for me, so I never updated past this to anything newer.
Fast forward and I just got myself a Note 4. So now I want to return my S4 back to stock and let it update and possibly give it to my daughter.
Anyway, after talking to a few people, it was decided since I never had a newer modem / software on my S4, it would work if I just flashed a Stock MF9 TAR to my phone (via Oden). Once it came back, I could search for new updates / software and let it auto update to the latest software.
I flashed MF9 Stock last night and now my phone is stuck at the Yellow Sprint Screen.
Any ideas how to get this back to stock? What do I need to flash? Like I said, it never went past the old version of SACS, never got Knox, none of that.
Thanks!
AzWizzard said:
So I have been running an OLD version of SACS Custom Rom on my Sprint S4 (Think MF9 / MDL time frame).
I was working great for me, so I never updated past this to anything newer.
Fast forward and I just got myself a Note 4. So now I want to return my S4 back to stock and let it update and possibly give it to my daughter.
Anyway, after talking to a few people, it was decided since I never had a newer modem / software on my S4, it would work if I just flashed a Stock MF9 TAR to my phone (via Oden). Once it came back, I could search for new updates / software and let it auto update to the latest software.
I flashed MF9 Stock last night and now my phone is stuck at the Yellow Sprint Screen.
Any ideas how to get this back to stock? What do I need to flash? Like I said, it never went past the old version of SACS, never got Knox, none of that.
Thanks!
Click to expand...
Click to collapse
Did you try a factory reset from stock recovery after you Odin back mf9?
AzWizzard said:
So I have been running an OLD version of SACS Custom Rom on my Sprint S4 (Think MF9 / MDL time frame).
I was working great for me, so I never updated past this to anything newer.
Fast forward and I just got myself a Note 4. So now I want to return my S4 back to stock and let it update and possibly give it to my daughter.
Anyway, after talking to a few people, it was decided since I never had a newer modem / software on my S4, it would work if I just flashed a Stock MF9 TAR to my phone (via Oden). Once it came back, I could search for new updates / software and let it auto update to the latest software.
I flashed MF9 Stock last night and now my phone is stuck at the Yellow Sprint Screen.
Any ideas how to get this back to stock? What do I need to flash? Like I said, it never went past the old version of SACS, never got Knox, none of that.
Thanks!
Click to expand...
Click to collapse
when i soft-bricked my galaxy s4 (sprint) I just re-rooted the phone using Odin & cf-autoroot...if you wanna update to the latest version for the s4 download the NG5 tar file & flash it through Odin & you should be ok...as far as getting back unrooted factory condition I'm not sure if there's a factory image available yet...not saying there isn't but I haven't seen one
ROMANTiC KiD said:
Did you try a factory reset from stock recovery after you Odin back mf9?
Click to expand...
Click to collapse
Thanks! That worked and got it to boot. It's updating now too!