Related
Due to many lags and problems with last stock rom from samfirmware I finally choose to mount a custom rom, as I have always done with all my devices in have taken a lot of informations before proceding so I have some questions to do:
what is the best rom for my tablet? ( I am an advanced user)
how can I bypass my bootloader block?
How can I install without bricking?
I have tried to install overcome kernel following standard procedure but my table was blocking in a new download mode image, and it didn't start. I solved flashing new stock rom, very indecent and lagging
thank for responses to everybody
with overcome you can follow the guide i think you might be making the mistake i made
read the guides well
before starting
1 root your device
http://forum.xda-developers.com/showthread.php?t=812367
2 how to unlock there is a sticky post here dont flash but if you do there is an apk file you have to run first on the stock rom to unlock (need step 1 to execute this)
http://forum.xda-developers.com/showthread.php?t=888071
read this guide and the steps below first before proceding
http://forum.xda-developers.com/showthread.php?p=11713685
3 copy the zip rom file to your internal SD not external
4 when you flash the kernel it boots into samsung screen wait it sais converting
then it estimates miutes then it finishes (i followd the guide and thought it was stuck on that screen before it was done converting to the new format
http://forum.xda-developers.com/showthread.php?t=932082
now proceed with the setps from but keep step 3 and 4 in mind
http://forum.xda-developers.com/showthread.php?p=11713685
GL!
I got my Galaxy Tab about a week ago and flashed Overcome right after. Highly recommended!
Follow the first post.
As far as recommending a Rom/Kernel. The Overcome Kernel and Rom are being developed and updated almost weekly. It's very stable and quite powerful.
I have done nr. 1st and 2nd steps and I'm going to make a 3rd. Step but I have another question in link you have posted there are old overcome kernel and rom, which I must download? The procedure is the same?
procedure is the same simply flash/install latest version.
How about if I want to use SMS after flashing? It's working on stock rom right now, do I need to do anything special when flashing Overcome?
i have done all steps, now i'll try this kernel and rom....thanks a lot to everybody!!
ravness said:
How about if I want to use SMS after flashing? It's working on stock rom right now, do I need to do anything special when flashing Overcome?
Click to expand...
Click to collapse
on euro tab all functionality works,
wifi
3g
gps
call
sms
accelerometer
light sensor
did not try using video call / mms
dose not work for me
vpn with tun.ko vpnc
what you sometimes need to do after flashing is to set up the acces points for some things like 3g connection you can usualy go to your providers homepage and have them send an sms to you with correct settings or fill in manualy
So no need to flash a modem or something, right? Thanks
Second that! I just installed Overcome 1.4.2 (replaces both the kernel and ROM) and everything is working dandy. Waiting to test it under day-to-day usage on weekdays next week, but for now it's been pretty stable and lag-free.
Did hit a road block while flashing yesterday (hit the same 'stuck at Samsung screen' issue others have faced), but there main ROM thread and another that it pointed to had step by step guides to everything. From flashing the kernel to troubleshooting problems. I just got into Android last month and this is my first flash.
Did find that the battery temperature on Overcome seems to be higher on average than when I had stock Euro... Am not overclocking though. Will continue to monitor this one.
no the modem dose not get replaced
you can chouse to go for a newer modem if you wish
Hi guys.
I want to get into rom flashing, but to be honest I find it rather confusing to say the least.
It would appear that ROM manager seems to be the easiest way to flash my phone correct?
Am I right in saying that all I need to do is download whichever rom I wish to install, rename it to "install .zip", put this file on the internal SD (not quite sure where exactly), then use ROM manager to flash, then it's done?
Is this the safest way of doing a flash?
Sorry for the noob questions.
You shud read your previous post dude
Sent from my GT-I9000 using XDA
Omarjivraj said:
You shud read your previous post dude
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
Thanks mate. I did, but I'm interested in trying other roms other than 2.3.6.
Darren K said:
Hi guys.
I want to get into rom flashing, but to be honest I find it rather confusing to say the least.
It would appear that ROM manager seems to be the easiest way to flash my phone correct?
Am I right in saying that all I need to do is download whichever rom I wish to install, rename it to "install .zip", put this file on the internal SD (not quite sure where exactly), then use ROM manager to flash, then it's done?
Is this the safest way of doing a flash?
Sorry for the noob questions.
Click to expand...
Click to collapse
I thought ROM manager took all that out of it. All you need to do is make sure your on latest CWM (which is does for you before you can download, i believe) and then you pick your download. Once it finishes it asks you whether you want to install and it does it all for you...
There is no "safe" way to flash. Something can always go wrong. I advise you follow the directions on the threads of your chosen rom. That way you can learn of the current bugs, the best way to flash based on your current situation (GB, Stock, another ICS etc) and what you may need to do before hand e.g. wipe/factory reset
If you have any questions on a particular installation method search the forum and the thread. If you cant find it then ask within the thread of your chosen rom.
Usually if its another rom i believe the best thing to do is wipe/factory reset from recovery menu and then choose zip from sd card. (But you still shoud read the first 2 pages and last 3 pages of the thread)
Talon26 said:
I thought ROM manager took all that out of it. All you need to do is make sure your on latest CWM (which is does for you before you can download, i believe) and then you pick your download. Once it finishes it asks you whether you want to install and it does it all for you...
There is no "safe" way to flash. Something can always go wrong. I advise you follow the directions on the threads of your chosen rom. That way you can learn of the current bugs, the best way to flash based on your current situation (GB, Stock, another ICS etc) and what you may need to do before hand e.g. wipe/factory reset
If you have any questions on a particular installation method search the forum and the thread. If you cant find it then ask within the thread of your chosen rom.
Usually if its another rom i believe the best thing to do is wipe/factory reset from recovery menu and then choose zip from sd card. (But you still shoud read the first 2 pages and last 3 pages of the thread)
Click to expand...
Click to collapse
What is the CWM, and why do I need that?
CWM = colockworkmod. Its basically the a new recovery menu that gives you more freedom to what you can do whilst in the menu. You have it on non-rooted devices (stock firmware/samsung firmware) but as i said it provides more freedom. I believe almost every rom uses a version of it, either adapted or not.
Im not sure you will be able to use ROM manager on a device that is not yet rooted (rooted means you have administrative privileges like in windows). You will need root access as you will be changing the system files which if done incorrectly will cause something to go wrong. Which is why you wish to use ROM manager. TBH is very hard to do something wrong with the SGS and not be able to come back from it to have a fully capable phone again.
Don't rush into anything though. Don't root or flash anything without knowing the risks and what could happen, and in-turn what needs to be done to correct it. If you know this then usually you will understand what went wrong and how to fix it.
Sorry for leaving all these long messages, just trying to be clear
Hello guys, it's me (nay, not Mario :laugh again. Another question.
Got a new battery which seems to hold charge well so I thought I might flash something in the likes of CM9 or CM10(.1).
I'm starting this thread because I would like to be totally sure what should I do (although I know I will never be 100% sure I'm doing it right). The reason I'm starting this thread is fear from bricking my phone (now troll me).
A little background (might be TLTR so freely skip it):
A year or so ago, I had a LG GT540 in my possession. Spoiled by the painlessness (is this a word?) of flashing Huaweis I fearlessly dared to flash fastboot on it in order to flash custom ROMs and stuff. The installation instructions seemed dead simple. Battery was full. Followed the procedure from letter to letter. Despite the fact that I followed the whole tutorial, in the end I got a hard brick. One hour later I thought it ought to be either finished or terminated due to an error of some kind. But no. It just stuck. Unplugged it and tried to turn it on. Fail, bootloop. Tried to reflash it, in all the modes I knew of. There were two or so modes: emergency and some über-emergency mode thingy. Fail. Then I tried with the official LG update tool. Final fail. That was the worst idea one could ever get, it got hard bricked, with no signs of life at all. RIP.
Back to the question.
As a proof that I used that damned search feature (at least tried to) here goes the procedure as I've understood it (while searching):
do a Nandroid and TB backup (optional, but you might really regret it if you don't do so)
back up your EFS folder
wipe data/factory reset
flash the ROM thru recovery
reboot
if it bootloops, reboot to recovery manually
flash the ROM again to finalize the procedure
eventually flash GApps
So,
did I leave out something?
what's the most reliable procedure/app to backup EFS?
is there a way to verify if EFS is properly backed up?
what's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
Semaphore's recovery tends to blink when browsing through using the capacitive menu button instead of volume buttons, is that a problem?
is Semaphore's recovery itself, regardless of the before mentioned issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
will I survive on XDA with that much questions at once?
It's SIM unlocked (don't know how, second hand phone, most likely with Helroz's unlock application), other details are in the signature.
Thanks in advance!
EDIT: See last post (#7 if the discussion goes on) for more details and answers to my questions.
http://www.youtube.com/watch?v=2DLySUtI8vo
http://www.youtube.com/watch?v=iRnH13sRAIc
http://www.youtube.com/watch?v=1RoZU5ZPMS4
http://www.youtube.com/watch?v=PwHVm90HO1w
check out these and you wont brick your phone happy flashing
I have already flashed a rooted kernel with CWM (CF-Root and later Semaphore).
Please, I know my English ain't perfect, but try to skim through my post. At least the second half of it.
your english is fine i read your post all of it i was just giving you a bit of direction incase you soft bricked your sgs,and as for what the best rom is they are all good roms the devs spend alot of time developing them its just a matter of what set up you like so try them all till you find one you like darkyrom v11 ,is pretty smooth its ics and stable cm 9 is good also ,remics jb 4.2.2 is good also .sgs i9000 is almost impossible to brick just read or watch the info two or three times just to be sure goodluck
TIGER 123 said:
your english is fine
Click to expand...
Click to collapse
Aw, thank you! Sorry for me being kinda needlessly rude.
TIGER 123 said:
and as for what the best rom is they are all good roms the devs spend alot of time developing them its just a matter of what set up you like so try them all till you find one you like darkyrom v11 ,is pretty smooth its ics and stable cm 9 is good also ,remics jb 4.2.2 is good also .
Click to expand...
Click to collapse
You meant this?
moorkai said:
what's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
Click to expand...
Click to collapse
In fact I wanted to know (along with the doubts from post #1) what do I need to flash prior to playing with ICS and/or JB because I thought that there are some ROMs (e.g. CM9) that do the necessary repartition process(es) as there are some partition layout differences between stock Gingerbread and the newer ICS and JB ROMs... and that failing to do so might lead to soft/hard bricks.
I know that asking questions like "What's the best ROM for my phone?" might lead to subjective and conflicting answers as some prefer lightweightness over functionality and vice versa, thus I don't prefer to do so, neither I did so in my first post. Sorry if you understood me otherwise.
Hope that I made some things more understandable now.
Okay, solved this doubt:
moorkai said:
what's the most reliable procedure/app to backup EFS? Tar zcvf contents of the /efs folder in terminal.
Click to expand...
Click to collapse
However, in one of the videos you posted here CWM 2.5.1.2 was used and thus it additionally stresses the following question:
moorkai said:
is Semaphore's recovery itself, regardless of the before mentioned issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
Click to expand...
Click to collapse
Help me!
I finally dared to flash CM10.1! Everything went silky smooth. Here are my conclusions for further reference (maybe someone can find them useful). These might be inaccurate, but I didn't brick my phone. After all, don't hesitate to correct me if I'm wrong.
How I flashed CM10.1:
do a Nandroid and TB backup (optional, but you might really regret it if you don't do so)
back up your EFS folder
wipe data/factory reset, wipe cache partition, advanced > wipe dalvik cache
flash the ROM through recovery (install zip from sdcard > choose zip from sdcard)
now it will reboot and finalize the flashing if everything is OK
eventually flash GApps
Questions from the first post and ...answers:
Q: Did I leave out something?
A: Most likely, not.
Q: What's the most reliable procedure/app to backup EFS?
A: Type the following stuff in Terminal Emulator or adb shell (root privileges necessary):
Code:
su
tar zcvf /sdcard/efs-backup.tar.gz /efs
# some users suggest that backing this up can also help if IMEI goes belly up
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
Q: Is there a way to verify if EFS is properly backed up?
A: Dual File Manager is quite useful for testing archive integrity.
Q: What's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
A: CM10.1, I guess.
Q: Semaphore's recovery tends to blink when browsing through using the capacitive menu button instead of volume buttons, does that mean it will cause ROM installation to fail?
A: I don't know, maybe, so flash CM10.1 with CF-Root kernel installed instead.
Q: Is Semaphore's recovery itself, regardless of the before mentioned
issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
A: See previous answer.
Bought a second hand Note. It's rooted as CWM on it. It won't update OTA (no updates showing at all for the past couple of days), and it's on 2.3.6.
Can I manually install an update via Odin? If so which one?
Direct links would help, I'm a bit of a noob
U.K Note btw
JccageX2 said:
Bought a second hand Note. It's rooted as CWM on it. It won't update OTA (no updates showing at all for the past couple of days), and it's on 2.3.6.
Can I manually install an update via Odin? If so which one?
Direct links would help, I'm a bit of a noob
U.K Note btw
Click to expand...
Click to collapse
Being a 'noob' isn't an excuse for not looking. Go to the stock ROM sticky thread and try actually looking next time.
It's always so much harder when you have to try (David Gray).
JccageX2 said:
Bought a second hand Note. It's rooted as CWM on it. It won't update OTA (no updates showing at all for the past couple of days), and it's on 2.3.6.
Can I manually install an update via Odin? If so which one?
Direct links would help, I'm a bit of a noob
U.K Note btw
Click to expand...
Click to collapse
instruction sent
check your PM
AndroidSlave said:
Being a 'noob' isn't an excuse for not looking. Go to the stock ROM sticky thread and try actually looking next time.
It's always so much harder when you have to try (David Gray).
Click to expand...
Click to collapse
Typical "Omfg do it yourself guy". Here's an idea, stop being such an ass, I evidently looked as I know what Odin is, I wanted to be sure from a member who knows what he's doing just in case I did something wrong. Imbecile.
Thank you Comscier, downloading all the stuff now
JccageX2 said:
Typical "Omfg do it yourself guy". Here's an idea, stop being such an ass, I evidently looked as I know what Odin is, I wanted to be sure from a member who knows what he's doing just in case I did something wrong. Imbecile.
Thank you Comscier, downloading all the stuff now
Click to expand...
Click to collapse
No here's a better idea - stop being a lazy
If you want someone to do it all for you, there are websites you can pay to root your phone. XDA is NOT that place.
There are threads already for this but you are just to lazy to lift two fingers to look
So you call me an ass? Okay buddy I'm an ass because your too lazy to read the guide that someone spent hours making that is at the very top of the forum as a sticky note in capital letters.
And yet with 152 posts you still refuse to just look at the guides that are step by step instructions because you expect to be spoon fed
Let's look at your other threads "which rom is best" "how to root my desire" and so on
Its not like you even try to look. You just over and over break xda policy and are lazy. Get with the picture and follow the rules
No reason to call me an ass, I am actually a very useful and helpful person to many people on this website. But everyone is expected to at least TRY to look before posting, which you consistently refuse to do (as your previous threads for other devices proves)
AndroidSlave said:
No here's a better idea - stop being a lazy
If you want someone to do it all for you, there are websites you can pay to root your phone. XDA is NOT that place.
There are threads already for this but you are just to lazy to lift two fingers to look
So you call me an ass? Okay buddy I'm an ass because your too lazy to read the guide that someone spent hours making that is at the very top of the forum as a sticky note in capital letters.
And yet with 152 posts you still refuse to just look at the guides that are step by step instructions because you expect to be spoon fed
Let's look at your other threads "which rom is best" "how to root my desire" and so on
Its not like you even try to look. You just over and over break xda policy and are lazy. Get with the picture and follow the rules
No reason to call me an ass, I am actually a very useful and helpful person to many people on this website. But everyone is expected to at least TRY to look before posting, which you consistently refuse to do (as your previous threads for other devices proves)
Click to expand...
Click to collapse
Never said you weren't a useful guy. However you for some reason insist I didn;t look beforehand. I made a thread to make sure I didn't mess up my phone, I didn't know if I could flash stock firmware over a root + recovery or not.
So before you attack members in their first post with a new phone, I'd suggest you'd think twice.
I appreciate your work. Bye.
JccageX2 said:
Never said you weren't a useful guy. However you for some reason insist I didn;t look beforehand. I made a thread to make sure I didn't mess up my phone, I didn't know if I could flash stock firmware over a root + recovery or not.
So before you attack members in their first post with a new phone, I'd suggest you'd think twice.
I appreciate your work. Bye.
Click to expand...
Click to collapse
My only thing I want to say is next time say what you read. Otherwise it looks like you have done nothing and are just posting out of laziness. There was no way I could have known you did any due diligence with your post aside from a mention of Odin.
I am going to link you to a very detailed post I wrote about upgrading from gingerbread. This post I wrote will guide you.
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
---------- Post added at 11:10 PM ---------- Previous post was at 11:06 PM ----------
Here is my post from the philz thread. Let Mr know if u have questions. Please also be SURE to read the brickbug sticky thread
TO ANYONE READING THIS POST - NOTE THAT THIS IS ALL SPECIFIC TO UOGRADING FROM GINGERBREAD ONLY
@onetonnoodle Honestly, if you like the features of Sweet Rom, it is an Amazing rom (maybe the best?), but I personally (when I use touchwizz interface) prefer a stock interface, which is why I like @ThaiDai's stock-deodexed LT9. If you were thinking of sweet rom, just go with it. It really is spectacular and constantly updated. Just be aware you may issue a couple bugs here and there because it is in constant development, but they always get fixed right away.
Regarding hardbricking, as long as your only doing wipes while PhilZ kernel is installed, you are safe. Remember anytime a new rom is flashed it overwrites the kernel with whatever is packaged with that rom. Also any gingerbread kernel philz or not are safe. Be very careful if on an ICS ROM though.
There are 3 ways that I would do it. Obviously, there are about 100 ways to do this. These are the methods I may use
IF ITS GINGERBREAD COMPATIBLE (I dont remember), the Mobile Odin Pro method is by far the easiest way
Here is one Method (easier, but only if u have pc odin setup):
1. Flash Sweetrom via PC odin
2. it wont boot because of all your old gingerbread data. After turning it on, immediately boot to recovery. Do a factory reset, or if you want a completely clean install do a full wipe and then reflash sweetrom again via recovery.
3. reboot to system
4. YOU WILL HAVE A YELLOW TRIANGLE. Use Triangle Away from XDA (its free) to remove that, but this does have a risk.
Mobile Odin Method this would be my first choice so long as your GB rom is rooted
I think mobile odin is compatible with gingerbread. You will have to download sweet rom to your phone.
If it is, you can use mobile odin to flash the sweetrom zip, you are already on gingerbread so you are brickbug safe...
If mobile odin is gingerbread compatible, which i believe it is, this is really a simple method.
Obviously your gingerbread ROM has to be rooted if you want to do this.
NOTE: you will get issues because mobile odin doesnt really do a full wipe. if hte issues do arise you can reboot to recovery included with sweet rom and just do a factory reset and you will be fine.
Here is yet another method to update:
1. Open the browser ON YOUR PHONE. *(a) Download SweetRom to the sdcard (internal or external); (b) Download the newest LT9 Philz kernel to your sdcard also.
* **Note: if you have issues getting the download to complete, try opera mini browser because it supports resume downloads.
2. [OPTIONAL STEP, not required] Flash Abyss 4.2 kernel, and do a full nandroid backup in recovery... * I personally would skip this step. *I dont even know if you could find abyss anymore, but I am making an option for you to get a nandroid backup of your gingerbread rom that will boot... *really though, dont waste your time on this unless you want to assure you have a full backup of gingerbread with a gingerbread kernel
3. *Unfortunately, you can't flash philz directly from your 3e recovery (because you are on gingerbread)... it will give a signature verification error. *so you can either flash it via PC odin, or do an OTA upgrade and then flash it (be careful, once you do this you are not brickbug safe).
4. Flash PhilZ LT9 Kernel from either Abyss if you did step 2 (optional), from your stock android recovery if you can put it on your external sd card *only if you did an OTA update , or via PC Odin if you dont have an external SD Card. *Be sure to follow the philz flashing instructions step by step.
5. NOW YOUR PHONE WILL NOT BOOT. dont be alarmed, you only want to go to recovery. *You will have no issue getting into recovery as long as philz flashed properly. *Your phone now has a JB kernel with a GB system, this is why it won't boot.
6. boot recovery (power - volume up - home held until you get to philz touch interface)
7. Go to factory reset, and choose the wipe all option (this wipes /system /data /cache /preload and .android_secure). *Your phone now has no system, but will retain the philz kernel and touch recovery.
8. no need to reboot recovery. *Just go to flash the Sweet ROM Zip. *let it run.*
9. reboot to system
10. Done. *it will already include the kernel.
If you are confused about any step, dont even start the process. ask first.
And be aware, there is always a risk doing this. It won't brick your phone, but you may softbrick it and lose recovery if something goes wrong. The solution for this is to use PC Odin and flash a ROM via PC Odin.
Thanks.
Introduction:
The search function, both on XDA and Google, can only take you so far. Getting my new (Dec 2013) Sprint Samsung Galaxy S4 successfully rooted, modified, ROM-ified and tricked out was an absolute nightmare because it came pre-installed with the MK2 firmware. While there are resources everywhere on XDA for every thing you could possibly think of, it took three weeks of cross-referencing dozens (hundreds?) of links, posts, snippets of information across the net and a lot of trial and error to get up and running. A lot of the material I came across was either outdated or irrelevant due to the original release of the phone in 2012 and the new MJA/MK2/NAE (reverse-compatible) firmwares released later in 2013/early 2014 and constant, daily development here on XDA.
I would like to clarify "Super Safe" does NOT mean you don't risk bricking your phone and you will most certainly void your warranty with Samsung (see post #2). It means I have included every possible step to avoid problems, incompatibilities and common errors. As with everything else on XDA related to modifying your phone, you are solely responsible for any damage done to your device.
Who This is For:
As an end-user, having this guide handy when I first arrived on XDA with my new S4 would have made my painfully long 3-week process cut down to about 4-6 hours (including download times). It is written so anyone can understand (I hope) without having to do much external research.
As a developer, pointing people to this thread will save you a lot of headaches and constantly repeating yourself with common questions and keeping your OP clean and tidy.
What It Covers:
The guide is long because it is detailed, comprehensive and takes you through all steps to having a backup of your stock data followed by (re)rooting, flashing a custom recovery, installing your custom ROM of choice and having a backup of it. I decided to go the "manual, old school" route because sometimes the latest tools and methods created conflict with other information available. That isn't to say new utilities and methods are bunk or won't make your life easier, but this is the dumbed-down, nitty-gritty guide when all else fails or you just want to avoid problems right from the start. The rest is all customization and entirely up to the user and I leave that ball in the court of other, more proficient and knowledgeable users in their appropriate threads.
What It Does Not Cover:
I do not go into detail about KNOX, AROMA, odex/deodex, choosing what ROM is right for you, optimization, better battery life, 3rd party applications (aside from three that are backup-related) and other, more detailed information. It is a straight, to the point, "This is how you get results, step-by-step." If you want to know about these features (and annoyances), there are plenty of resources available here to fill your mind.
This all-in-one guide is meant for everyone and to be shared by anyone who finds it helpful as a way to troubleshoot your device or totally start from scratch and avoid a lot of VERY common errors and misconceptions.It focuses on having a fresh backup of the stock 4.3 ROM (pre-rooted and deodexed) in case you ever need to return your phone, @Unknownforce's TriForce ROM and @Phil3759's Philz Touch Recovery, but can be adapted and applied to nearly any other ROM that isn't dependent on TWRP (which, in most cases, comes down to personal preference). Edit 2/7: It seems many new KitKat releases require TWRP, so be sure to read the directions for the ROM you choose carefully regarding which recovery to use!
The guide is presented as a .docx (Microsoft Word) file which can also be downloaded and/or printed. Links won't be preserved if you print it out, so be sure to download what you need before you walk away from the computer!
So, without further adieu, I would like to present:
Spiricore's Super Safe Root-To-ROM Guide v1.5
for Sprint's Samsung Galaxy S4 (SPH-L720/jfltespr)
READ. IT. ALL.
About Me:
I am not new to XDA (mostly a lurker until very recently), but I am very new to Android 4.x as my last phone was an EVO Shift 4G running 2.3.5 for the better part of two years. Before that I was on a flip phone. I am no expert - I wouldn't even call myself an approaching-advanced user - but the information I have compiled has already helped numerous users of all skill levels in all sorts of situations in the few hours I've had it publicly available. I will do my best to answer any questions asked, but the vast majority of what I know is already contained within the guide. I can expand upon what I do cover, but be forewarned that answering very specific, user-to-user questions may be beyond the scope of my knowledge. The most I can offer in that case is to point you in a direction that can better serve you. If I don't respond to you it's because your question has already been answered in my guide or in my first few posts. Read more gooder! :silly:
I did my best to credit all original authors and posts I gathered this information from. I am not here to step on anyone's toes, nor to make enemies! Any feedback, corrections, missing information, thanks and so on would be greatly appreciated!
Special Thanks:
A personal "thank you!" goes out to all original authors and developers, @Unknownforce, @sac23, @rawintellect, and @inlineboy for their contributions, help, advice and - in @inlineboy's case - compiling information together for the rest of us so we aren't banging our heads against the wall trying to find the exact information we're seeking.
Changelog:
1.5 - Updated some links; added TWRP link; fixed derp with Philz link; added note to second post on this thread regarding Philz versions.
1.4 - Fixed booting process procedure (thanks @cruise350); updated note 2; added note 5; removed app versions unless specific ones are necessary; various formatting fixes; tried to make things a little less ROM-specific.
1.3 - Fixed UF's stock firmware link for Odin; added link for flashable version from recovery (thanks @evilbeef54)
1.2 - Updated to reflect new release of SuperSu and some formatting tweaks
1.1 - Massive formatting update for public consumption
1.0 - Initial release (originally copied from a mountain of text in some PMs I sent to help @Caffeinatrix out)
Additional Notes:
KNOX and OTA Updates:
Flashing custom recoveries will trip KNOX. This includes custom ROMs and anything that modifies system files because you need a custom recovery to do so. (thanks @cruise350)
Your KNOX counter being tripped to 0x1 only means you cannot get support directly from Samsung. Your service provider will still help, but once KNOX has been tripped you've effectively terminated your warranty with Samsung (say, for example, if you needed to send it back for repair or replacement). Many stores will still provide help/repairs/replacements regardless of your KNOX flag and there never really has been any definitive "Do it!" or "Don't do it!" documentation I could ever find. If you have rage or toilet-dropping issues it may be wise to hold off. Otherwise, take the jump!
That said, if you have rooted your phone and are running at custom ROM, NEVER, ever, EVER under ANY circumstance accept an OTA (Over The Air - aka from your carrier) update!!! Your best bet is to use an application like Titanium Backup or ROM Toolbox to freeze any update apps (I used this thread as a resource; just be sure to double-check .apk names as it is a little out of date). Stick with the leaked stock ROMs releases found here on XDA if you wish to update but still be running things normally but with a few tweaks here and there.
ODIN Flashable vs. Recovery Flashable:
If a file ends in .tar, .md5 or .tar.md5 you can flash it in Odin on PC or MobileOdin (not covered). If it's .zip, open it up and see if there's a .tar or .md5 or .tar.md5 file. If there is, extract it with a tool like 7-Zip or WinRAR and you're good to flash from Odin. If not and you see other files and folders, copy the .zip to your phone's internal or external sdcard and flash it from Philz Recovery or TWRP. If you're not sure, ask!
Philz Recovery versions:
Philz Recovery v6.08.9 is recommended in this guide due to some changes made to later versions which can cause the flashing process to abort due to a permissions error. This has since been fixed in Philz using an option found within its settings in versions >6.13.1, but installer scripts not updated to these newer standards will kick you out with the error if you're not aware of the change and option. Once more releases/ROMs/tweaks have updated their installer scripts - or there starts being a problem using the older version - I will edit the guide to reflect using the latest version.
Also reserved
I've had my new s4 on mk2 for about 2 weeks and was wanting to root but with all the Knox crap have been waiting for a good guide. I will be trying this out this weekend. Thanks
Sent from my SPH-L720 using Tapatalk
This resource is awesome, thanks! I have been reading for a few days now trying to find something like this. This info is on various threads but it is scattered about like you said.
It also figures that I just flashed/rooted the phone last night before I saw this, I was going to wait one more day to do some more reading but decided to do it last ngiht. I stayed on the MF9 bootloader and loaded up Philz, MK2 modem and a stock MK2 rom with Knob removed.
First off, the S4 has never required you to hold the "Home" button while booting into recovery or download mode so remove that from your guide as it is an unnecessary requirement. Also, not to rain on your parade, but this is about the most backwards way to root your device that I have ever seen. All you need to do is download cf-autoroot, install it with odin, if SuperSu didn't take, download it from the Play store, install and update binaries. Install goomanager from play store, let it install twrp, or odin phillz, back up and install your favorite rom or mod.
cruise350 said:
First off, the S4 has never required you to hold the "Home" button while booting into recovery or download mode so remove that from your guide as it is an unnecessary requirement. Also, not to rain on your parade, but this is about the most backwards way to root your device that I have ever seen. All you need to do is download cf-autoroot, install it with odin, if SuperSu didn't take, download it from the Play store, install and update binaries. Install goomanager from play store, let it install twrp, or odin phillz, back up and install your favorite rom or mod.
Click to expand...
Click to collapse
This fix got my phone working again after having messed with it using cf auto root and all that crap. It's long but it's the reason my phone is actually working again.
cruise350 said:
First off, the S4 has never required you to hold the "Home" button while booting into recovery or download mode so remove that from your guide as it is an unnecessary requirement. Also, not to rain on your parade, but this is about the most backwards way to root your device that I have ever seen. All you need to do is download cf-autoroot, install it with odin, if SuperSu didn't take, download it from the Play store, install and update binaries. Install goomanager from play store, let it install twrp, or odin phillz, back up and install your favorite rom or mod.
Click to expand...
Click to collapse
Thank you for your feedback. I will check in to the home button part - I always assumed it was necessary because I never saw the home button not being necessary mentioned anywhere else. Appreciate the tip!
As per CF-Auto-Root, it's how I originally rooted my phone but, as I state in the OP, this is to avoid using tools such as that because I had trouble with it very similar to @Caffeinatrix below. There's too many "if's" and troubleshooting within the method itself it you're green behind the ears. Knowing the base workings of the entire process allows you to troubleshoot it at a core level so that if a tool doesn't work the way it's intended (be it the tool not working or the user not using it right), there is always this fall-back.
Caffeinatrix said:
This fix got my phone working again after having messed with it using cf auto root and all that crap. It's long but it's the reason my phone is actually working again.
Click to expand...
Click to collapse
I'm glad it worked buddy! It has served me well after all the flashes and wipes I've done getting the exact, fool-proof method figured out. :victory:
Dude, thanks. I won't have time to check this out till the weekend.
I get the need for this with all the bad experiences reported in many, many threads.
I'll report back when I check your method out
Sent from my SPH-L720 using Tapatalk
Your method works and easy to read, nice!
definately think the guide is a good thing
i want to know what happens if we try and flash an offiical stock knox enabled firmware with odin pc when the phone is setup per your guide
KNOX = 0x1 (per your guide right?)
SuperSU1.86.zip = rooted (when ran from the phone in apps drawer do you tell it to disable all knox stuff)?
phlz recovery (arent you supposed to tell it to fix root/permissions) the first time you tell it "system reboot now"?
ok with that setup if you go grab an official MK2 complete tar.md5 (that has not been touched) no root, no recovery....100% STOCK<<<
you open odin 3.07 and pick that tar.md5 file and tell it to flash the phone while in download mode.
WHAT HAPPENS???
this is what we all want to know
does phone FAIL to Flash?
does it Brick?
does it flash just fine and then if it does an OTA then it will brick?
what happens....
en11gma said:
definately think the guide is a good thing
i want to know what happens if we try and flash an offiical stock knox enabled firmware with odin pc when the phone is setup per your guide
KNOX = 0x1 (per your guide right?)
SuperSU1.86.zip = rooted (when ran from the phone in apps drawer do you tell it to disable all knox stuff)?
phlz recovery (arent you supposed to tell it to fix root/permissions) the first time you tell it "system reboot now"?
ok with that setup if you go grab an official MK2 complete tar.md5 (that has not been touched) no root, no recovery....100% STOCK<<<
you open odin 3.07 and pick that tar.md5 file and tell it to flash the phone while in download mode.
WHAT HAPPENS???
this is what we all want to know
does phone FAIL to Flash?
does it Brick?
does it flash just fine and then if it does an OTA then it will brick?
what happens....
Click to expand...
Click to collapse
If you install the full mk2 tar file then you will end up with a stock unrooted phone. That is what a full tar does. So yes, you can take an OTA. If you are rooted though, OTAs on the other hand are upgrade files and abort whenever they encounter a changed system file or anything else that has been modded in system or recovery.
You will still have the Knox warranty flag tripped since there currently is no way to reset that.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
If you install the full mk2 tar file then you will end up with a stock unrooted phone. That is what a full tar does. So yes, you can take an OTA. If you are rooted though, OTAs on the other hand are upgrade files and abort whenever they encounter a changed system file or anything else that has been modded in system or recovery.
You will still have the Knox warranty flag tripped since there currently is no way to reset that.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
the two files that i have seen that are avail for android 4.3 users are MJA and MK2
i put phone in odin mode and flash that mk2 and it does NOT erase my mdc modem
so either something is wrong with that MK2 full stock file or........
anyhow if i do a ##72786# and then reboot it puts me on MK2 baseband
not sure if its the reboot doing it or if its the ##72786# but since im there i also do the ##786# just to make sure
i am seeing some things in *#9090# not changing during this process
##3424# resets
*#0011# resets (meaning i can not get into the menu but values in networking are diff so i believe that area gets reset)
*#9090# does not reset
whats going on? is it the actual firmware not erasing what it should, the way we are flashing it or something we did before when we ran the unlock.exe and downgraded the modem too.
the odin mk2 full stock should erase everything on phone and flash....something not right in denmark
im gonna root right now per your guide mostly
Sezmar said:
Your method works and easy to read, nice!
Click to expand...
Click to collapse
Agreed..^^^
Sent from my SPH-L720 using XDA Premium 4 mobile app
ok so a bit of a hang up here... i flashed Triforce 5.2 over stock rooted mja, you directed me here to your write up saying that i needed to flash firmware before flashing the rom, in your write up you say to flash the firmware through odin using the mk2 modem only .tar, but the link you gave above for firmware does not go to the tar, it goes to a zip of a modded stock kernal... which i thought was included in the rom since it asks weather you want to flash the modded stock kernal or ktunz, so do i need to flash this zip, or did this get flashed when flashing the rom, or should the link have taken me to the file listed in step 4.
EDIT
i found UF's thread with the tar so i odin'd that.... still says MJA
edit #2
I odin'd it again and now it shows MK2, no idea why the first one didnt take.... but still step 4 should either say to use the kernal .zip if that works, or you need to fix the download link for firmware to direct to the .tar
thanks
This is a really useful thread, especially for people new to rooting and flashing roms
evilbeef54 said:
ok so a bit of a hang up here... i flashed Triforce 5.2 over stock rooted mja, you directed me here to your write up saying that i needed to flash firmware before flashing the rom, in your write up you say to flash the firmware through odin using the mk2 modem only .tar, but the link you gave above for firmware does not go to the tar, it goes to a zip of a modded stock kernal... which i thought was included in the rom since it asks weather you want to flash the modded stock kernal or ktunz, so do i need to flash this zip, or did this get flashed when flashing the rom, or should the link have taken me to the file listed in step 4.
EDIT
i found UF's thread with the tar so i odin'd that.... still says MJA
edit #2
I odin'd it again and now it shows MK2, no idea why the first one didnt take.... but still step 4 should either say to use the kernal .zip if that works, or you need to fix the download link for firmware to direct to the .tar
thanks
Click to expand...
Click to collapse
Whoops, that's what I get for putting this together in the wee hours of the morning. Fixed - thanks for pointing it out!
Updated to v1.3:
1.3 - Fixed UF's stock firmware link for Odin; added link for flashable version from recovery (thanks @evilbeef54)
The. Man.
Thanks, man. I have unsuccessfully tried to root on a Mac 3 times with no luck. I kept giving up after hour 2 of cross-referencing all the different info out there. You have proactively paid your debt to society, Sir.
Knox flag
Will this method trip the knox flag. Thank You for all the hard work.