Related
First off let me say I am a noob I have rooted several phones but just stay stock and do simple mods.... that said....
I got my s4 a week ago, didn't know there was the mf9 update available, so I rooted my phone (on mdl), with CF-Auto Root.
Did the hotspot mod, did a camera tweak, got xposed installer, prl write enable...that's all I've done.
I want to upgrade to MF9 (since I keep getting "message unresponsive" on MDL which it's supposed to fix) ...
I've read the the threads and it seems a lot of people are getting stuck and things occurring when they go from rooted MDL to MF9
so I need help please =DDD
Right now I am
Kernel
Linux version 3.4.0-529760
I tried to be as descriptive as I could since I don't want to run in to any problems..
I want to be able to add all the stuff I currently have on my phone but I don't care if the memory is lost since I can just add it again..
I would REALLY appreciate some help!! since I just got the phone and I don't want to brick it
P.S I got the "system update" notification on my phone telling me to install regarding MF9, would I be able to do it that way and then root (since it would unroot my phone)???
I did that with the s3 and I was unable access root again, it just said I was rooted but I really wasn't....
Or should I unroot, update mf9, then root again?? Is that easier??
helpp!!! Again I read the threads but it dooesn't seem anyone is my situation
Glitterloveglamour said:
First off let me say I am a noob I have rooted several phones but just stay stock and do simple mods.... that said....
I got my s4 a week ago, didn't know there was the mf9 update available, so I rooted my phone (on mdl), with CF-Auto Root.
Did the hotspot mod, did a camera tweak, got xposed installer, prl write enable...that's all I've done.
I want to upgrade to MF9 (since I keep getting "message unresponsive" on MDL which it's supposed to fix) ...
I've read the the threads and it seems a lot of people are getting stuck and things occurring when they go from rooted MDL to MF9
so I need help please =DDD
Right now I am
Kernel
Linux version 3.4.0-529760
I tried to be as descriptive as I could since I don't want to run in to any problems..
I want to be able to add all the stuff I currently have on my phone but I don't care if the memory is lost since I can just add it again..
I would REALLY appreciate some help!! since I just got the phone and I don't want to brick it
P.S I got the "system update" notification on my phone telling me to install regarding MF9, would I be able to do it that way and then root (since it would unroot my phone)???
I did that with the s3 and I was unable access root again, it just said I was rooted but I really wasn't....
Or should I unroot, update mf9, then root again?? Is that easier??
helpp!!! Again I read the threads but it dooesn't seem anyone is my situation
Click to expand...
Click to collapse
Wrong section....please use the "Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshooting" section of the Sprint Galaxy S4 Forums
Oooh you are in big trouble. Lol, I kid, I kid... A Moderator will move this. It is in the wrong section... But while I'm here, use superSU to unroot (there is a setting in it to unroot) reverse any mods, you have got to be 100% stock. Stock kernel, stock recovery, and everything has to match....In download mode if it says you have anything but a zero count, and, or if it says custom, use triangle away to clear the flash count, and if you have custom in about phone.
Once you are unrooted, and everything is stock, do a factory reset, I read you should do it 2 our 3 times. Only when it is like it was when you got it, accept the MF9 update, then root, and you will be all good
Sent from my Nexus 7 using Xparent Skyblue Tapatalk 2
cerj said:
Oooh you are in big trouble. Lol, I kid, I kid... A Moderator will move this. It is in the wrong section... But while I'm here, use superSU to unroot (there is a setting in it to unroot) reverse any mods, you have got to be 100% stock. Stock kernel, stock recovery, and everything has to match....In download mode if it says you have anything but a zero count, and, or if it says custom, use triangle away to clear the flash count, and if you have custom in about phone.
Once you are unrooted, and everything is stock, do a factory reset, I read you should do it 2 our 3 times. Only when it is like it was when you got it, accept the MF9 update, then root, and you will be all good
Sent from my Nexus 7 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
is that one of the easiest ways to just go back to stock then upgrade then root again?
I found the following way to be simple and it worked:
1. Flash your phone with the Samsung MDL tar using Odin. Reboot.
2. Perform a factory reset from Settings. Reboot.
3. Go into stock recovery and flash the official MDL to MF9 zip file from a microSD card. Reboot.
4. To get root back, flash a custom recovery of your choice with Odin.
5. Within custom recovery, flash the latest SuperSU zip. Reboot.
You should now be rooted and you can start modding.
If you are staying stock rooted this is by far the easiest way: http://forum.xda-developers.com/showthread.php?t=2357471
No reason to even mess with flashing the OTA push.
I ended up doing an unroot flash stock, factory reset. Add mf9. Cf root
and now im on mf9 rooted
it seems like the hard method mostly that stock took like 2 hours to download
cerj said:
Oooh you are in big trouble. Lol, I kid, I kid... A Moderator will move this. It is in the wrong section... But while I'm here, use superSU to unroot (there is a setting in it to unroot) reverse any mods, you have got to be 100% stock. Stock kernel, stock recovery, and everything has to match....In download mode if it says you have anything but a zero count, and, or if it says custom, use triangle away to clear the flash count, and if you have custom in about phone.
Once you are unrooted, and everything is stock, do a factory reset, I read you should do it 2 our 3 times. Only when it is like it was when you got it, accept the MF9 update, then root, and you will be all good
Sent from my Nexus 7 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Is this the order these steps should be done in?
My apology if this has been asked as I've scanned through a few with not much luck.
Came across this and i went to sammobile and dl the TELUS 4.4.2 firmware and judging by this article, this is an non-wipe install via Odin3.
I know it is best to wipe and start fresh but hoping someone might be able to point me in the right direction as I would like to upgrade without wiping.
Thanks a bunch!
http://www.howtoroot.mobi/2014/04/install-i337mvlufnc1-442-for-galaxy-s4.html
shuweee said:
My apology if this has been asked as I've scanned through a few with not much luck.
Came across this and i went to sammobile and dl the TELUS 4.4.2 firmware and judging by this article, this is an non-wipe install via Odin3.
I know it is best to wipe and start fresh but hoping someone might be able to point me in the right direction as I would like to upgrade without wiping.
Thanks a bunch!
http://www.howtoroot.mobi/2014/04/install-i337mvlufnc1-442-for-galaxy-s4.html
Click to expand...
Click to collapse
You cant update your phone without whipping your device if using odin unless its an OTA cause if you do you will most like end up in boot llop thus just backup and then flash using odin, what i assume from the article is that it wont wipe your internal sd card but will wipe your data i.e applications and settings etc.
Depends where you are trying to get to..... if you are not rooted on 4.3 and just want to go to 4.4.2, I would just use Kies. If you are rooted and want to go to 4.4.2 then yes this looks like the right method. Things to concider are.... do you want to be able to go back to 4.3 at anytime is so, you really shouldn't use this method as I believe it is going to update your bootloader which means no going back... If you intend on rooting anyway, I would suggest using CF- auto root, added a custom recovery and flashing Mapleleaf rom..... plus the NC1 modem... this is mostly stock, you will have root access and retain the 4.3 bootloader should you want to revert back to 4.3.......this will trip you Knox so if you want to keep warrenty well this isn't a good way to go either... unless of course you have already tripped it...
Ok, so last OTA worked. Here is what i did:
I used triangle away's feature to hide system modified warning
i downloaded the OTA update
I disabled the triangle away fix before installing OTA (like it says to do in triangle away)
Phone rebooted and installed the OTA in CWM
Done.
I tried this today to upgrade from 4.3 to whatever is being pushed by my carrier (kitkat)
this time, when i install the OTA, it reboots to CWM and CWM says "install untrusted zip?" I hit yes, it says install aborted. I hit no, it says same thing.
I have heard others mention this, and were told to restore a stock recovery. I have found instructions to do that here:
http://www.android.gs/how-to-install-stock-recovery-for-the-samsung-galaxy-s4-i9500-i9505/
But i dont have a i9500, i have the canadian model, the i337m
Can i still flash the stock recovery image from an i9500? or will i brick something.
also not understanding why i have to do any of this when it worked last time and nothing has changed....maybe because its jumping from 4.3 to 4.4 ... i dunno..
Any advice appreciated, id love to get this OTA. I just dont want roms anymore, only stock. but i want to stay up to date with my android version, and that is becoming tough for me.
thanks.
luke318is said:
Ok, so last OTA worked. Here is what i did:
I used triangle away's feature to hide system modified warning
i downloaded the OTA update
I disabled the triangle away fix before installing OTA (like it says to do in triangle away)
Phone rebooted and installed the OTA in CWM
Done.
I tried this today to upgrade from 4.3 to whatever is being pushed by my carrier (kitkat)
this time, when i install the OTA, it reboots to CWM and CWM says "install untrusted zip?" I hit yes, it says install aborted. I hit no, it says same thing.
I have heard others mention this, and were told to restore a stock recovery. I have found instructions to do that here:
http://www.android.gs/how-to-install-stock-recovery-for-the-samsung-galaxy-s4-i9500-i9505/
But i dont have a i9500, i have the canadian model, the i337m
Can i still flash the stock recovery image from an i9500? or will i brick something.
also not understanding why i have to do any of this when it worked last time and nothing has changed....maybe because its jumping from 4.3 to 4.4 ... i dunno..
Any advice appreciated, id love to get this OTA. I just dont want roms anymore, only stock. but i want to stay up to date with my android version, and that is becoming tough for me.
thanks.
Click to expand...
Click to collapse
Thats exactly because you're upgrading from 4.3 to kk and yeah bootloaders differ probably that's the reason recovery and roms should be flashed if they are specifically for your model i9300 cabt have a rom which is for i9505 it bricks your phone same with recovery and yeah better make a clean flash via odin!
I guess i want to know what to do now. How do i get the Ota? How do i get stock recovery back
These are basic questions that have been anwsered 1000 times already. There is a search button you know.
First of all this is not the i1337m forum.
Second flashing stuff on your phone that is not for you phone is the dumbest thing to do. You should know that before you start messing with your phone.
Go to your forum and use the search button.
Lennyz1988 said:
These are basic questions that have been anwsered 1000 times already. There is a search button you know.
First of all this is not the i1337m forum.
Second flashing stuff on your phone that is not for you phone is the dumbest thing to do. You should know that before you start messing with your phone.
Go to your forum and use the search button.
Click to expand...
Click to collapse
Ill do just fine without you're attitude, take it elsewhere
I have a Verizon S5 that currently has g900VVRU1B0A8 on it.
Recently the screen has started flashing green and not coming on whrn the power button is pressed.
Im not sure if this is hardware or software so I factory reset it and the issue is still there, maybe not as frequent though.
Do you think it would do any good to upgrade it, can i just odin a new firmware on now, as long as im not going backwards?
If this is a stock factory phone that has never been rooted I would venture a guess that your phone is failing from a hardware standpoint. If it is still under warranty I would replace it before trying any rooting/flashing ... If you want to root it however, DO NOT take the OTA upgrade. That will put you on the latest build but you will not be able to go backwards and root it after taking the update. The version you are currently on can be rooted. And no, you can not just flash a new firmware. If you want to root, you have to follow the steps in the rooting threads and revert back to NCG first to root. Don't flash anything without reading everything thoroughly and understanding what you are doing BEFORE you flash anything.
Oh, its been heavily screwwed with, used to be mine but i gave it to my wife.
Knox is tripped and it says custom on boot.
I took it back to stock when i gave it away....just thinking a updated driver may help.
Been out of the scene for awhile, what are my options?
f4u5t said:
Oh, its been heavily screwwed with, used to be mine but i gave it to my wife.
Knox is tripped and it says custom on boot.
I took it back to stock when i gave it away....just thinking a updated driver may help.
Been out of the scene for awhile, what are my options?
Click to expand...
Click to collapse
Just because it says custom on boot doesn't really mean knox is tripped. All my earlier root versions said that without being tripped. Download the Samsung phone info app from the play store. Run that and if knox says 0x0 it is not tripped. It doesn't really matter though if the phone is out of warranty.
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Oniyuri said:
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Click to expand...
Click to collapse
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Alessandro's said:
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Click to expand...
Click to collapse
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Then you install lollipop stock, make root , flash recovery and then flash cm13
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
GDReaper said:
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
Click to expand...
Click to collapse
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Oniyuri said:
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Click to expand...
Click to collapse
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
GDReaper said:
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
Click to expand...
Click to collapse
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Oniyuri said:
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Click to expand...
Click to collapse
The only concern is about the warranty. Since your phone is some years old, I doubt that is an issue for you anymore.
By losing memory you mean losing data or actually losing storage space?
Either way, I haven't heard of anyone with such a problem around here.
Nor about somebody with a fried motherboard.
There might have been some unfortunate cases, but this is to be expected when you modify your device. There always is a risk of damage, it doesn't matter if it's by rooting or by flashing a ROM.
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Oniyuri said:
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Click to expand...
Click to collapse
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
GDReaper said:
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
Click to expand...
Click to collapse
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Oniyuri said:
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Click to expand...
Click to collapse
1) Is not mandatory, it's just recommended. The only exception is if your device is a Verizon or AT&T phone, then don't - and I repeat - don't update or you risk losing the possibility of any custom ROM flashing or rooting due to the locked bootloaders.
2) and 3) CWM and TWRP backups do not have cross-compatibility. If you backup with CWM you have to restore with CWM.
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
robcore said:
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
Click to expand...
Click to collapse
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Oniyuri said:
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Click to expand...
Click to collapse
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
robcore said:
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
Click to expand...
Click to collapse
Well, so far, the chromecast is only plugged into my tv and basically did the setup by itself only for the google cast app on my phone to not recognize it when it said that it's ready to cast. I've ran out of things to do aside from going to the google forums (which I've already done). I'm starting to wonder if it's my phone that's causing all the issues.