Hello all. First off I have a I337m with baseband NE1. I never see this mentioned anywhere and wanted to know what I can do with this phone.
I've rooted already (with towelroot) and wanted to get a custom bootloader. I've read and read then read somemore but found too many mixed staments regarding this.
Can I install a custom bootloader (say through goo manager) without worries or is there more to it? Does it completely overwrite the stock bootloader?
Do I need to worry about Loki?
Can we use other carrier ROMs?
Is it safe to say that everything in this sub forum works with my device?
Im familiar with flashing and the likes coming from the S2 with CM10.2 but there are too many varients and mixed statments (old to new methods) and I can't for the life of me find direction.
This is what I know about the i337m, mind you I don't have the device:
You can root using chainfires cf-auto root
Use trwp manager to install twrp
You can flash any rom here and you don't need Loki
Sent from my Nexus 5 using XDA Free mobile app
Bluntified said:
Hello all. First off I have a I337m with baseband NE1. I never see this mentioned anywhere and wanted to know what I can do with this phone.
I've rooted already (with towelroot) and wanted to get a custom bootloader. I've read and read then read somemore but found too many mixed staments regarding this.
Can I install a custom bootloader (say through goo manager) without worries or is there more to it? Does it completely overwrite the stock bootloader?
Do I need to worry about Loki?
Can we use other carrier ROMs?
Is it safe to say that everything in this sub forum works with my device?
Im familiar with flashing and the likes coming from the S2 with CM10.2 but there are too many varients and mixed statments (old to new methods) and I can't for the life of me find direction.
Click to expand...
Click to collapse
I have the same phone on Telus... as far as the "custom bootloader" I think you really mean custom recovery, I use TWRP version 2.7. You can also use Philz recovery or CWM but I perfer TWRP as it hasnt given me any issues. If you load TWRP don't go for the latest version as I have seen guys have problems with the latest and greatest.
Once you have twrp on your phone... before you do anything else... make a backup in twrp of your current rooted stock rom so you have a starting point. In twrp, I like to do all backups to the external sd card as there may come a time where you do a factory wipe... and poof its gone...
In the developement thread... there is a rom called Mapleleaf works very well on this phone... I run it myself with the googy-max3 kernel.
If you decide to flash anything else... make sure it will work for i337m, I have seen people get into trouble flashing things meant for the US version (i337). Our bootloader is unlocked so you don't need saftey strap or loki or other things that the i337 users need.
When in doubt... search the forum... if you find nothing... ask before you do anything strange.
As far as the bootloader goes... try to stay on your current one.. mine is still MK6. Once the bootloader is updated there is no going back... period.....
This helped a lot man, I appreciate it.
So just to clarify, can I use goo manager for the recovery or should I use Odin? And is there any version in particular [TWRP] that I should use? What version are you running?
How do I check my bootloader version?
Sent from my SGH-I337M using XDA Free mobile app
Bluntified said:
This helped a lot man, I appreciate it.
So just to clarify, can I use goo manager for the recovery or should I use Odin? And is there any version in particular [TWRP] that I should use? What version are you running?
How do I check my bootloader version?
Sent from my SGH-I337M using XDA Free mobile app
Click to expand...
Click to collapse
You can use goo manager or Odin. Just make sure you have the right version. FYI twrp 2.5.0.2 is the most reliable version that I have used for this device.
Tapatalked from California Custom Chrome M&M I337m
If you want an older version of twrp use odin... goomanager will likely try to load the latest version... as for checking which bootloader version you have, download the app phone info from the play store.... here... https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
my version of twrp is 2.6.3.1 and it works fine... as stated... 2.5 is also recommended by some of the devs....
My bootloader ends in NE1, does that pose a problem - I rarely see it mentioned anywhere? I took the OTA in case anyone is wondering. Basically, can I flash something that's not NE1?
Also, I've been reading that the ROM that's going to be flashed needs to be the same Android Version as the current one on the phone, is this still true?
Bluntified said:
My bootloader ends in NE1, does that pose a problem - I rarely see it mentioned anywhere? I took the OTA in case anyone is wondering. Basically, can I flash something that's not NE1?
Also, I've been reading that the ROM that's going to be flashed needs to be the same Android Version as the current one on the phone, is this still true?
Click to expand...
Click to collapse
This will mean you can flash any rom (for i337m) that is 4.4.2 version of android. You can always go up on android version to bootloader but you can't go down versions unless the bootloader is an earlier version. Since most roms are 4.4.2 or higher, I don't think this should be an issue, not many people are looking to go to an older version of android..... bigger... better and all that...
Gage_Hero said:
This will mean you can flash any rom (for i337m) that is 4.4.2 version of android. You can always go up on android version to bootloader but you can't go down versions unless the bootloader is an earlier version. Since most roms are 4.4.2 or higher, I don't think this should be an issue, not many people are looking to go to an older version of android..... bigger... better and all that...
Click to expand...
Click to collapse
Is this true, bc I have a bell galaxy 4, 4.4.2 i337m NE1 , I want to install a custom recovery,
but I thought my bootloader was locked because its says write protection enabled on the download screen which I thought
meant the bootloader was locked.
strakn said:
Is this true, bc I have a bell galaxy 4, 4.4.2 i337m NE1 , I want to install a custom recovery,
but I thought my bootloader was locked because its says write protection enabled on the download screen which I thought
meant the bootloader was locked.
Click to expand...
Click to collapse
The I337M bootloader is not locked. What you are seeing when you boot after rooting is that you tripped KNOX since new bootloaders are closely tied to KNOX so any violation = tripped KNOX.
I have I337M from Telus with NE1 bootloader (4.4.2) and custom Rom PhoeniX. Everything is great except a newly discovered TD Bank App and inability to link my TD Visa to it...
Related
Hi there guys,
I've been used to flashing android devices in the past (+2 years ago), but I don't have much experience with it nowadays.
first my current situation:
-I'm running MJ7 atm, rooted with kingo
i'm looking fo flash note's 3 4.4.2 kitkat rom, or omega rom, or cm11
If I understood correctly:
1) install a clockwork mod recovery for my 9005
> what "image" do I use for that? clockwork mod recovery doesn't have the note 3 9005 in it's list
2) install another rom through clockwork mod recover?
I've already tried looking for answers on this forum, but either they aren't for my specific device, or it doesn't explain the steps
Any suggestions guys?
The custom recovery is needed because... samsung's recovery is limited or something?
Trying to find answers to these questions!
In case I overlooked some topics, feel free to point me towards them!
Thanks in advance!
Nick
seventje84 said:
Hi there guys,
I've been used to flashing android devices in the past (+2 years ago), but I don't have much experience with it nowadays.
first my current situation:
-I'm running MJ7 atm, rooted with kingo
i'm looking fo flash note's 3 4.4.2 kitkat rom, or omega rom, or cm11
If I understood correctly:
1) install a clockwork mod recovery for my 9005
> what "image" do I use for that? clockwork mod recovery doesn't have the note 3 9005 in it's list
2) install another rom through clockwork mod recover?
I've already tried looking for answers on this forum, but either they aren't for my specific device, or it doesn't explain the steps
Any suggestions guys?
The custom recovery is needed because... samsung's recovery is limited or something?
Trying to find answers to these questions!
In case I overlooked some topics, feel free to point me towards them!
Thanks in advance!
Nick
Click to expand...
Click to collapse
OK, so before you flash you need to know that if you upgrade to 4.4.2 Official your bootloader upgrades and you cannot use CM nor can you go back to 4.3. SO you need to decide which you'd prefer to do.
As for recovery, yes you need a custom recovery to flash a custom mod. -- CWM by Chenglu is the only recovery that currently works on Kitkat 4.4.2.
TWRP/PhilZ/CWM work on 4.3 - so you can flash anything up until MK/ML*
CM11/OMEGA/CRASH/ALLIANCE etc all run on Mj7/MK2-3/ML2 currently so are compatible with your 4.3 build
Since you rooted via Kingo, is your KNOX preserved? because installing a custom recovery will void this.
radicalisto said:
OK, so before you flash you need to know that if you upgrade to 4.4.2 Official your bootloader upgrades and you cannot use CM nor can you go back to 4.3. SO you need to decide which you'd prefer to do.
As for recovery, yes you need a custom recovery to flash a custom mod. -- CWM by Chenglu is the only recovery that currently works on Kitkat 4.4.2.
TWRP/PhilZ/CWM work on 4.3 - so you can flash anything up until MK/ML*
CM11/OMEGA/CRASH/ALLIANCE etc all run on Mj7/MK2-3/ML2 currently so are compatible with your 4.3 build
Since you rooted via Kingo, is your KNOX preserved? because installing a custom recovery will void this.
Click to expand...
Click to collapse
First of all, I want to thank you for the swift response!
So basically:
-once I flash original 4.4.2 I get a new bootloader and I cannot install a different rom except stock one atm?
-If I flash CM11/Omega etc it's no issue.. Any idea why though? CM11 is also 4.4.2 based.. but it doesn't come with new restrictive bootloader I suppose?
-I rooted through kingo, and during boot I don't see any special "text", so I suppose my knox is preserved
-about the "voiding", I found a piece of text in the european law here about rooting and voiding warranty that will help me if I ever needed that warranty
-Question about CMW recovery: If I install it from the play store, what kind of "recovery" do I need to install? is there a Database for that or some sort?
seventje84 said:
First of all, I want to thank you for the swift response!
So basically:
-once I flash original 4.4.2 I get a new bootloader and I cannot install a different rom except stock one atm?
-If I flash CM11/Omega etc it's no issue.. Any idea why though? CM11 is also 4.4.2 based.. but it doesn't come with new restrictive bootloader I suppose?
-I rooted through kingo, and during boot I don't see any special "text", so I suppose my knox is preserved
-about the "voiding", I found a piece of text in the european law here about rooting and voiding warranty that will help me if I ever needed that warranty
-Question about CMW recovery: If I install it from the play store, what kind of "recovery" do I need to install? is there a Database for that or some sort?
Click to expand...
Click to collapse
1- Yup, once you get the new bootloader you can't downgrade, you can however flash ROMS which are created with this new bootloader, so far SweetROM, AndroidNow NG and(soon to be coming) AllianceROM are NA6 compatible.
2-CM was built on the old BL source, it'll probably eventually get updated to NA6 BL at some point, but for now it's based on MJ7 BL.
3/4- Yup if you are EU like myself, then KNOX warranty means nothing to us, I was just confirming you were aware of this
-- CWM has to be installed via ODIN, takes 20seconds to flash via PDA option in ODIN 1.85. CWM will be your main base recovery and you can install/wipe/mount etc as and when you need to.
*Side note, my advice, stick with your current bootloader and avoid the new kitkat bootloader, install CWM and flash in temasek's CM build and custom kernel. It's a fantastic build! just need to install the gAPPS to get Playstore and google apps etc - also Official Nightlies have been announced and are live by CM**
Any other queries just post away :good:
seventje84 said:
First of all, I want to thank you for the swift response!
So basically:
-once I flash original 4.4.2 I get a new bootloader and I cannot install a different rom except stock one atm?
-If I flash CM11/Omega etc it's no issue.. Any idea why though? CM11 is also 4.4.2 based.. but it doesn't come with new restrictive bootloader I suppose?
-I rooted through kingo, and during boot I don't see any special "text", so I suppose my knox is preserved
-about the "voiding", I found a piece of text in the european law here about rooting and voiding warranty that will help me if I ever needed that warranty
-Question about CMW recovery: If I install it from the play store, what kind of "recovery" do I need to install? is there a Database for that or some sort?
Click to expand...
Click to collapse
Where do we find that piece of law? Im just curious since I'm also knox 0x1 Hehe. Currently running Androidnow but after 1 day it seems that I have some forced reboots. Don't know where it comes from. I guess it's because I installed the rom from external sd.
Sent from my SM-N9005 using xda app-developers app
Koumorisword said:
Where do we find that piece of law? Im just curious since I'm also knox 0x1 Hehe. Currently running Androidnow but after 1 day it seems that I have some forced reboots. Don't know where it comes from. I guess it's because I installed the rom from external sd.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Did you dirty flash? - try another ROM, that may be a little buggy... However I suspect you didn't do a full wipe and that's the issue with the FC's
radicalisto said:
Did you dirty flash? - try another ROM, that may be a little buggy... However I suspect you didn't do a full wipe and that's the issue with the FC's
Click to expand...
Click to collapse
I did the Cwm based Phil "prepare for other rom" wipe. Manual wipe would be better you think?
Sent from my SM-N9005 using xda app-developers app
Koumorisword said:
I did the Cwm based Phil "prepare for other rom" wipe. Manual wipe would be better you think?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Nope, that wipe should be enough. Probably a buggy ROM. Try another and see if you have any issues.
Koumorisword said:
Where do we find that piece of law? Im just curious since I'm also knox 0x1 Hehe.
Click to expand...
Click to collapse
You want to look for EU Directive 1999/44/CE
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I've been trying to figure this out for the last day, with no success.
I've got a rooted Note 3 N9005 (MJ7) stock. this is a 4.3 Rom. Knox status is0x0 (didn't trip it when I've rooted it ages ago).
I had enough of sammy rom, and I want to play with some of the new 4.4.4 custom roms.
I'm totally and utterly lost regarding what's tripping knox, and what are the needed steps in order to achieve that.
From what I understand, flashing TWRP (or any other custom recovery) will trip knox. I'm fine with that.
I'm not sure if I'm supposed to first upgrade my 4.3 to an official 4.4.2, and what / if is all the lock/unlock bootloader which seems to differ between versions (4.3 and 4.4). There also seem to be different versions of TWRP depending on if you're on 4.3 or 4.4?
Can I simply flash TWRP on my rooted 4.3, backup, flash new shinny 4.4.4 rom, and be happy ? Will that keep the root ?
Otherwise, do i need to upgrade to official 4.4.2 version first? will that lose root and I'll have to reroot the new version, and then flash TWRP and then flash 4.4.4 roms?
Any kind of help (or point me to an article that discusses it, even though I didn't find any, and i've searched) will be highly appreciated.
Cheers and thanks in advance.
_Noctis_ said:
I've been trying to figure this out for the last day, with no success.
I've got a rooted Note 3 N9005 (MJ7) stock. this is a 4.3 Rom. Knox status is0x0 (didn't trip it when I've rooted it ages ago).
I had enough of sammy rom, and I want to play with some of the new 4.4.4 custom roms.
I'm totally and utterly lost regarding what's tripping knox, and what are the needed steps in order to achieve that.
From what I understand, flashing TWRP (or any other custom recovery) will trip knox. I'm fine with that.
I'm not sure if I'm supposed to first upgrade my 4.3 to an official 4.4.2, and what / if is all the lock/unlock bootloader which seems to differ between versions (4.3 and 4.4). There also seem to be different versions of TWRP depending on if you're on 4.3 or 4.4?
Can I simply flash TWRP on my rooted 4.3, backup, flash new shinny 4.4.4 rom, and be happy ? Will that keep the root ?
Otherwise, do i need to upgrade to official 4.4.2 version first? will that lose root and I'll have to reroot the new version, and then flash TWRP and then flash 4.4.4 roms?
Any kind of help (or point me to an article that discusses it, even though I didn't find any, and i've searched) will be highly appreciated.
Cheers and thanks in advance.
Click to expand...
Click to collapse
If you aren't concerned about KNOX, upgrade to a 4.4 ROM (Official) via ODIN which will upgrade the bootloader, then once that's all done, flash TWRP for 4.4 then download your ROMs and flash via TWRP as normal.
radicalisto said:
If you aren't concerned about KNOX, upgrade to a 4.4 ROM (Official) via ODIN which will upgrade the bootloader, then once that's all done, flash TWRP for 4.4 then download your ROMs and flash via TWRP as normal.
Click to expand...
Click to collapse
Not concerned any more ...
Out of curiosity, what exactly kills the root? flashing a rom doesn't. upgrading via odin ? I'm assuming it has nothing to do with the system/cache, since each flash usually wipes them, so, where does it live?
Cheers
_Noctis_ said:
Not concerned any more ...
Out of curiosity, what exactly kills the root? flashing a rom doesn't. upgrading via odin ? I'm assuming it has nothing to do with the system/cache, since each flash usually wipes them, so, where does it live?
Cheers
Click to expand...
Click to collapse
Reflashing the ROM back to stock is what kills root. It's easy to re-root again once you've tripped KNOX anyways.
But tbh, once you install a custom recovery after you've upgraded your boot loader, you won't need to root. It isn't required for custom recovery
Sent from my Spectrum ZX +2
EDIT: Have you used ODIN to flash stock images before? If not, have a read around, it's pretty straight forward though.
radicalisto said:
Reflashing the ROM back to stock is what kills root. It's easy to re-root again once you've tripped KNOX anyways.
But tbh, once you install a custom recovery after you've upgraded your boot loader, you won't need to root. It isn't required for custom recovery
Sent from my Spectrum ZX +2
EDIT: Have you used ODIN to flash stock images before? If not, have a read around, it's pretty straight forward though.
Click to expand...
Click to collapse
I see ... so -> flash stock (kills root) -> flash TWRP (trips knox) -> flash custom rom without worrying about root ? (wouldn't i need it for titanium backup ,or do custom roms come with SU preinstalled?)
Yep, used odin. file on comp, download mode, couple of ticks, clicky clicky, happiness ensues ...
Yeah you're pretty much spot on. Yeah most ROMs are pre-rooted and if they aren't you can just flash superSU via your recovery. But you should be good to go and know what you're doing by the sounds of it.
Enjoy flashing them ROMs and make an efs backup and store off the device too. There's an adb script for it here (forget where but its here, development thread I think) don't use any apps from the play store as they are notorious for bricking Samsung devices.
Sent from my Spectrum ZX +2
radicalisto said:
Yeah you're pretty much spot on. Yeah most ROMs are pre-rooted and if they aren't you can just flash superSU via your recovery. But you should be good to go and know what you're doing by the sounds of it.
Enjoy flashing them ROMs and make an efs backup and store off the device too. There's an adb script for it here (forget where but its here, development thread I think) don't use any apps from the play store as they are notorious for bricking Samsung devices.
Sent from my Spectrum ZX +2
Click to expand...
Click to collapse
lol ...notorious for bricking samsung devices ... i like it ...
i ran one already (zipped a 6MB and a 14.5MB image and tar into a 300kb zip), and been told you can do that from inside TWRP as well ...
I'll take a deep breath, and start downloading the official image and roms ...
I'll update if i'll get to the other side
out of curiosity ... does it matter which official 4.4.2 image i'm flashing ? (i'm getting the NZ one ...but i assume they should all be similar, and / or that it doesn't matter since i'll be flashing something else on it anyways, right ?
_Noctis_ said:
out of curiosity ... does it matter which official 4.4.2 image i'm flashing ? (i'm getting the NZ one ...but i assume they should all be similar, and / or that it doesn't matter since i'll be flashing something else on it anyways, right ?
Click to expand...
Click to collapse
Yeah try and keep to the country your device is from, otherwise you have to find the right PIT file, and the partitions vary etc
radicalisto said:
Yeah try and keep to the country your device is from, otherwise you have to find the right PIT file, and the partitions vary etc
Click to expand...
Click to collapse
Rubbish. ..I don't recall seeing an australian one... I'll have another look, otherwise ill look into the pit thingy. Thanks.
Been trying to read and figure out as much as I can, but I'm lost. I rooted my phone right when I got it a few months after release. I have the MDL firmware and I'm running stock that I've modified to my liking. I rooted using motochopper, I have TB and SU and I have TWRP installed. I'm ready to take the jump and try to get an updated firmware, but don't know where to look. It seems a lot of the info in now for the newer firmwares.
I would like to run either Google edition or a modified TouchWiz I think. I like keeping things pretty clean and fast. I am currently running Aviate on top of TouchWiz and I like the clean organized feel of it, although a bit laggy.
Please help me XDA, sorry I know this is a newb post. I've been blocking the OTAs for over a year and I'm ready to move on.
First I would suggest NOT to use any STOCK firmware to update to 4.4.2
There are some newer Google Edition Roms I believe in the ATT original ANDROID SECTION. You can use them since you have twrp recovery. Those with newer firmware cannot use the latest google edition Roms unless they are made for safestrap.
Or if you want a modified stock Touchwiz with all the extra benefits you can flash directly to ShoStock-i 8.1 which is 4.4.2 based.
Keeping you MDL bootloader and the Loki bootloader bypass you have now let's you flash ANYTHING you want, including kernels.
If you update firmwares the bootloader becomes MORE LOCKED DOWN and you cannot flash any Roms that need a modified kernel like aosp based Roms, or any kernel other than stock.
Thank you ill check those roms out. I am aware that I DO NOT want to update my firmware, that's part of the reason I asked for advice, to see which roms work well with MDL. Most of what I found was all for newer FW versions.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Would I be better off upgrading to OUDHS Touch CWM-based Recovery 1.0.3.5 instead of TWRP so everything is auto Loki'd?
matchstick13 said:
Would I be better off upgrading to OUDHS Touch CWM-based Recovery 1.0.3.5 instead of TWRP so everything is auto Loki'd?
Click to expand...
Click to collapse
Sorry I haven't tried OUDHS so I cannot comment. But TWRP still works perfectly. For ShoStock you would NOT need to flash Loki-Doki patch or anything. The kernel in ShoStock-i is already Loki patched. If you plan on trying other Roms it is always best to keep the Loki-Doki flashable zip on your sdcard and flash it after flashing a ROM. Just extra insurance that won't hurt anything if the ROM is already lokified.
Ok going to try flashing this
http://forum.xda-developers.com/showthread.php?t=2537495
Followed by Loki Doki
Hope I'm doing this right.
matchstick13 said:
Ok going to try flashing this
http://forum.xda-developers.com/showthread.php?t=2537495
Followed by Loki Doki
Hope I'm doing this right.
Click to expand...
Click to collapse
Should work
Sent from my Nexus 5 using XDA Free mobile app
hi all , sorry but my english is so bad
i just bought a galaxy s4 att secondhand , this had bassband UCUAMDL . and i checked the lastest version of it is 4.2.2
can i upgrade my phone up to 4.4 ?
and i dont know terminology about "MF3 - MK2 ............."
could you tell me ?
thanks so much :victory::victory::victory:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
HORiZUN said:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
Click to expand...
Click to collapse
thanks so much ,
can you get me links :crying:
but MF3 - MK2 ............. what is it ?
when i flash rom , what i have to notice ?
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
i am in 4.2.2
sonluyen94 said:
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
Click to expand...
Click to collapse
I have the same question. hopefully someone will be able to explain it to us.
MF3 would be the last three digits of your system software version
HORiZUN said:
MF3 would be the last three digits of your system software version
Click to expand...
Click to collapse
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
You don't have MF3, and that's a good thing. You can install a custom recovery. You need to root, install a custom recovery, and then you can start flashing roms.
sonluyen94 said:
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
Click to expand...
Click to collapse
nogods said:
I have the same question. hopefully someone will be able to explain it to us.
Click to expand...
Click to collapse
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
npjohnson said:
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
Click to expand...
Click to collapse
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
sonluyen94 said:
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
Click to expand...
Click to collapse
Most if not all. They're all built from either GPE or CM.
All good advice. Plus when you root and get Twrp recovery installed do a backup thru Twrp (Nandroid) and keep on phone and put a copy on pc. That way you have something to restore if you get in trouble. Also, your bootloader is not unlocked. No Att i337s are. Instead devs use an exploit called Loki-Doki to bypass Sammy's security checks to allow custom roms/kernels etc to flash. You can google Loki Doki and read up on it. If the rom or kernel is not loki'd you will have to flash the zip thru recovery to allow the rom or kernel to flash. You will come across this when flashing International roms and kernels. I don't have link any more so maybe someone else can link it. Keep it on SD card. Like noted read OP carefully and last 20 pages of rom thread. Builds newer than MDL are blocked by Att from using Loki and require SafeStrap. Which you don't need to worry about. Although you can read up on it. Good Luck. [emoji1]
Sent from my iPhone 6 Plus using Tapatalk
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
plasticglock said:
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
Click to expand...
Click to collapse
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
plasticglock said:
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
Click to expand...
Click to collapse
ROM manager didn't work. It said it installed cwm recovery but it didn't. I was able to install the latest TWRP with this ROM Installer and it worked like a charm! I then installed my custom TWRP from there, rebooted recovery, and installed Danvh's Google edition. I'm setting it up right now. I'm so happy to get my phone back. I just hope the odin flash fixed my problems.
To the OP try ROM installer to get your custom recovery going. Also if you like simple and fast AOSP check out Danvh's google edition rom, but stick to 4.4.4 for now. 5.0 is out but its buggy. Here's a link to the custom version of twrp that I use. https://www.dropbox.com/l/iDQQqlzNbyiFbQrMF4XcRc It's already loki'd so you can flash it if you have any problems with the latest build.
I've spent hours searching and I know this is an old phone. Is ther anyway to root the Lollipop and download Jelly Bean (custom or stock) to it? I'm not worried about Warranties. I'm not exactly a newb and I don't like Lollipop at all. I don't mind KitKat, but what I hate is the front facing camera can't be flipped. Dumbest thing ever.
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Click to expand...
Click to collapse
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
BikerSk8rKid said:
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
Click to expand...
Click to collapse
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
GDReaper said:
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Click to expand...
Click to collapse
I was half asleep and stressed out when I posted this. It's been a couple weeks or longer since I messed with the phone. Damn forums weren't resetting my password. When I mean I'm not a newb I mean I'm not like brand new to this and I know how to research. I guess you could say I'm not THAT stupid. haha
I'mma have to try this again and figure out what path's I kept trying. I'm so spaced out I can't remember hard any of it. Just that I tried to flash a stock and rooted rom with old odin and new odin. Spent 2 days straight messing with it and trying to get around it. But I kept getting blocked. I didn't come across CF-Autoroot. So I'll try that.
Strephon Alkhalikoi said:
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
Click to expand...
Click to collapse
Of all the researching I've done (I couldn't login) that one never showed up in my searchs. haha I'll have to give that one a try. It's been a couple weeks or longer. SPH-L720. I had a few Tri-Bands, but it seemed those were limited compared to the standard model.
Update: I went the CF-AutoRoot route and then tried to use Odin to flash stock mk2 rom. Now that I remember it kept failing everytime and then it would corrupt the current rom. I also tried using TWRP and couldn't get it to work properly.
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
GDReaper said:
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
Click to expand...
Click to collapse
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
BikerSk8rKid said:
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
Click to expand...
Click to collapse
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
GDReaper said:
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
Click to expand...
Click to collapse
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
BikerSk8rKid said:
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
Click to expand...
Click to collapse
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
GDReaper said:
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
Click to expand...
Click to collapse
I'll look into that and give it a shot. Thank you! I knew it wasn't THAT easy. LOL