Related
Not sure what these numbers and letters mean....
Mine sais EL29, so i only flashed the ROM (Blazer ROM 4.0) that had all the same information as my phone displayed under "About Phone"....
This page http://forum.xda-developers.com/forumdisplay.php?f=716 has a list of ROMs, a few of which i would like to use. Specifically the new ICS leaks (Hurry up SPRINT, release the ICS ALREADY!!)...
My question is... is the "EL29" "EH17" "SRF12" and all those others the firmware versions? Modem Versions? What are these? If a ROM specifies this information anywhere, will i have to upgrade or downgrade to the appropriate files (Or firmware) before flashing the ROM? I have no idea what these are or what they mean.
From what i've read and picked up, i know that some of these things will have to be done through ODIN and I think I read that some other things can be done through CWM, like flashing the ROM itself.
I just need a little more information on how flash ROMs properly concerning what needs to be done BEFORE I flash a new one... No one wants a Samsung PaperWeight.
Things I already know:
1.) Must install a ROM compatible with your phone (DUH)
2.) Sometimes you gotta use ODIN (Is this only for root? Or do you use this to upgrade/downgrade modem firmware or something, too ?)
Also, what other file exensions should I be familiar with and what do they do? I just want to be able to modify my phone with no problems and a collection of links and bookmarks for me to pull it off. I'm not trying to be a programmer (yet =)
Any links specific to my questions would be greatly appreciated!
Thanks in advance.
Most of this could be answered with a little reading, frankly. Many of the stickies explain most of this.
I would start by watching some of QBKING77s YouTube videos, they will explain Everything.
There should be a link in my sig to get yourself started with an easy one click root, but read, read, and then read some more before doing anything.
A link to a post I answered similarly previous :
http://forum.xda-developers.com/showthread.php?p=23413749
Sent from my calculator watch.
Date the firmware was built that simple. EL29 was the most recent gingerbread build. FC13 build which btw was todayish is the latest ics leak.
In simplest terms:
EL29
E is the year. E was 2011, F is 2012, etc.
L is the month. A=Jan, B=Feb, C=Mar, ... L = Dec
29 Well, given the rest of the pattern, is the compile date. In this example, 29 is the 29th day of December, 2011.
And as the other poster says, this info is out there if you spent a bit of time searching for it.
I want to see a custom ROM based on the SRF12 leak.
Compusmurf said:
In simplest terms:
EL29
E is the year. E was 2011, F is 2012, etc.
L is the month. A=Jan, B=Feb, C=Mar, ... L = Dec
29 Well, given the rest of the pattern, is the compile date. In this example, 29 is the 29th day of December, 2011.
And as the other poster says, this info is out there if you spent a bit of time searching for it.
Click to expand...
Click to collapse
Thanks. Thats what i was looking for. Never would had guessed what the E's and L's stood for.
I have read on this, trust me. Including the links that kingdazy provided. Although i will watch that youtube video to see what i can learn from it.
As i've said i've already root my Samsung E4G Touch flawlessly and i'm loving it, i was just wanting clarification on things.
My main question is.... If it has a different build, for instance mine is EL29, i would have to somehow get FC13 firmware on to my Samsung E4GT to flash any ICS ROM on to it, right? Either that, or whatever other firmware version the ROM instructions specify, i'm guessing.
I think the firmware is done using ODIN, right? I know i just used ODIN to flash an already rooted EL29 image..
But is CWM only used to install files from zips such as ROMs or stuff like Gapps?
Or does it depend entirely on the developers instructions? I know some dev leave out some instructions such as "use ODIN" or "use CWM" so when they do, i'm assuming i can use either or?
I DO see that they tend to tell you what NOT to use.. Like this one for CM9
"Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED"
Needed clarification as to whether or not i've been understanding what i've been reading. Overall, i'm just wanting to know if i'm on the right track. If you guys got any pointers or advice. I would greatly appreciate it.
And just FYI.... I do my research. I know how to read. I'm just not as familiar with these forums like you guys are and have problems finding things. You got to admit, sometimes performing searches require a little finesse and know how....
Anyway, Thanks a lot.
Sorry I'm at work, can't link or go into detail, but in general ".zip"s are for cwm, ".tar"s are for odin.
If a dev insists on one or the other, they will say.
Sent from my calculator watch.
exitprogram said:
Thanks. Thats what i was looking for. Never would had guessed what the E's and L's stood for.
I have read on this, trust me. Including the links that kingdazy provided. Although i will watch that youtube video to see what i can learn from it.
As i've said i've already root my Samsung E4G Touch flawlessly and i'm loving it, i was just wanting clarification on things.
My main question is.... If it has a different build, for instance mine is EL29, i would have to somehow get FC13 firmware on to my Samsung E4GT to flash any ICS ROM on to it, right? Either that, or whatever other firmware version the ROM instructions specify, i'm guessing.
I think the firmware is done using ODIN, right? I know i just used ODIN to flash an already rooted EL29 image..
But is CWM only used to install files from zips such as ROMs or stuff like Gapps?
Or does it depend entirely on the developers instructions? I know some dev leave out some instructions such as "use ODIN" or "use CWM" so when they do, i'm assuming i can use either or?
I DO see that they tend to tell you what NOT to use.. Like this one for CM9
"Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED"
Needed clarification as to whether or not i've been understanding what i've been reading. Overall, i'm just wanting to know if i'm on the right track. If you guys got any pointers or advice. I would greatly appreciate it.
And just FYI.... I do my research. I know how to read. I'm just not as familiar with these forums like you guys are and have problems finding things. You got to admit, sometimes performing searches require a little finesse and know how....
Anyway, Thanks a lot.
Click to expand...
Click to collapse
To answer your first question (flash firmware first, and then the ROM) there isn't an easy answer as a lot of ROMs are complete systems which include the firmware. Some though are not and do require the correct firmware to work or install properly. From what I'm seeing, the ICS ROMs appear to all be full system ROM's meaning you wipe your phone and install and you're good. Some require additional files such as modems or whatever. But you could easily go from Gingerbread to the current stock version of ICS (which is what I'm using) with one simple flash.
The method you use to flash isn't specific to what you're flashing rather what the software was designed to be flashed with. Many developers prefer to use a recovery install (zips) while others use ODIN (tar). As I was coming from a stock software pack (and stock recovery) my only real option was an ODIN flash. Most of the time you cannot flash using the stock recovery. The software has to be signed by sprint in order for the stock recovery to flash a zip.
The most important things to be aware of in terms of those bricking their phones is be CERTAIN you are using software for YOUR phone. Not the Samsung Galaxy S2 but the specific one you use (in my case Epic 4G Touch which is Sprint). International files seem to do major damage. DO NOT stop the flash process mid-way through. I bricked a Samsung Moment that way and you have to go with your tail between your legs to the store. Avoid some of the ROM switchers and MobileODIN. They are great resources for an advanced phoner, death of a newb.
I would start with a basic stock flash through ODIN to ICS there are videos that make it pretty darn simple. Use it for a few days, figure out what you like and what frustrates you and then evaluate the ROMs to see if any might be better.
The Stock ICS I am using IS rooted but it's so stock that I will still receive the OTA (over-the-air) update from Sprint. So I have some bugs.
EDIT: OH LOL I just realized I'm in the Epic 4G Touch forum, I could've been more specific regarding the ROMs and what not I thought I was in a general forum.
exitprogram said:
Thanks. Thats what i was looking for. Never would had guessed what the E's and L's stood for.
I have read on this, trust me. Including the links that kingdazy provided. Although i will watch that youtube video to see what i can learn from it.
As i've said i've already root my Samsung E4G Touch flawlessly and i'm loving it, i was just wanting clarification on things.
My main question is.... If it has a different build, for instance mine is EL29, i would have to somehow get FC13 firmware on to my Samsung E4GT to flash any ICS ROM on to it, right? Either that, or whatever other firmware version the ROM instructions specify, i'm guessing.
I think the firmware is done using ODIN, right? I know i just used ODIN to flash an already rooted EL29 image..
But is CWM only used to install files from zips such as ROMs or stuff like Gapps?
Or does it depend entirely on the developers instructions? I know some dev leave out some instructions such as "use ODIN" or "use CWM" so when they do, i'm assuming i can use either or?
I DO see that they tend to tell you what NOT to use.. Like this one for CM9
"Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED"
Needed clarification as to whether or not i've been understanding what i've been reading. Overall, i'm just wanting to know if i'm on the right track. If you guys got any pointers or advice. I would greatly appreciate it.
And just FYI.... I do my research. I know how to read. I'm just not as familiar with these forums like you guys are and have problems finding things. You got to admit, sometimes performing searches require a little finesse and know how....
Anyway, Thanks a lot.
Click to expand...
Click to collapse
I was wondering the same so don't feel stupid exitprogram. I too have read a lot, and the more I do the more confused I get. Frankly, I have no idea how to move forward.
I'm pretty noob with this phone, but have rooted my HTC Hero and flashed a few ROMS on it, rooted my et4g and installed starburst, even rooted and cm7ed my nook, but I'm very confused about the firmware version compatibility with ROMS for the ET4G. I've been waiting to see how the ICS ROMS are before doing anything further to my phone.
I'm sure you guys who replied must get tired with noobs asking the same old questions, but saying go read the internets ("Read Everything before flashing Anything.") isn't very helpful. I appreciate you taking the time to help, I really do, but it's frustrating.
You say to watch QBKing77 videos, and all will be revealed. Here is an example of what is confusing for me, one of QBKing77 videos
In the vid it says it's a FC06 ICS ROM. Then leads you through the format all and zip install. I have no problem doing that, but I have EG30, and I have no idea if following the above install procedure will update me to FC06 or will leave me with a brick and/or headache.
ok general rule for samsung at least, only use GB firmware (kernel) with GB roms (system), ICS with ICS... For the QBKing example, i didnt watch the vid, but usually he says where hes coming from. Odds are its EL29, the official stock, if you wanted to do what he did, get to the starting point he was on then go from there. Honestly I think a lot of this has been made really complicated with the ET4G, mainly because of all the leaks, all fifteen personalized recoveries, people demaning preference on CWM or Odin... on the OG Epic there werent THIS many leaks, and there was time to catch up the new people, now its insane. I think the CWM variants really only serve to complicate, example the Rom Manager works good for CM9 I guess, but not really at all for everything else, and Rogue doesnt work for CM9, but great for the regular stuff... too much redundancy. And honestly it isnt just Rogue and ACS, they just try to simplify Koush's CWM, but then Koush has Rom Manager and it says it supports our phone, but the temp recovery is iffy and dont even mess with the Touch Recovery.
Anyways, just follow OP instructions, give the search a shot so you can tell the trolls you did so (it usually yields nothing, google works better) and sift through the chit chat in the dev threads for the info. If its not there in 20 pages, and not in the OP, just ask... if someone figures something out after the thread is created, someone should let the OP know to update their thread. Some devs are in a hurry and forget to clarify things... it happens.
in general, .zips are flashed thru CWM, look/ask which one to use if not specified, .tar, .md5, .bin... all use Odin... look for which to use (the one-clicks are actually cool... make Odin easier till people get familiar with what goes where). I think once we get ICS official and the first onslaught of ROMs come out, things will settle down a lot.
Does anyone else notice those are bothe of epic and epic touch radios? Op be very careful not to make the mistake of flashing wrong ones
Sent from my BAD A$$ EPIC TOUCH 4G
ungovernable1977 said:
ok general rule for samsung at least, only use GB firmware (kernel) with GB roms (system), ICS with ICS... For the QBKing example, i didnt watch the vid, but usually he says where hes coming from. Odds are its EL29, the official stock, if you wanted to do what he did, get to the starting point he was on then go from there. Honestly I think a lot of this has been made really complicated with the ET4G, mainly because of all the leaks, all fifteen personalized recoveries, people demaning preference on CWM or Odin... on the OG Epic there werent THIS many leaks, and there was time to catch up the new people, now its insane. I think the CWM variants really only serve to complicate, example the Rom Manager works good for CM9 I guess, but not really at all for everything else, and Rogue doesnt work for CM9, but great for the regular stuff... too much redundancy. And honestly it isnt just Rogue and ACS, they just try to simplify Koush's CWM, but then Koush has Rom Manager and it says it supports our phone, but the temp recovery is iffy and dont even mess with the Touch Recovery.
Anyways, just follow OP instructions, give the search a shot so you can tell the trolls you did so (it usually yields nothing, google works better) and sift through the chit chat in the dev threads for the info. If its not there in 20 pages, and not in the OP, just ask... if someone figures something out after the thread is created, someone should let the OP know to update their thread. Some devs are in a hurry and forget to clarify things... it happens.
in general, .zips are flashed thru CWM, look/ask which one to use if not specified, .tar, .md5, .bin... all use Odin... look for which to use (the one-clicks are actually cool... make Odin easier till people get familiar with what goes where). I think once we get ICS official and the first onslaught of ROMs come out, things will settle down a lot.
Click to expand...
Click to collapse
First of all. All of you suck and none of this information was helpful WHATSOEVER.
JK!
It's good to have received that the clarification as to what ODIN uses and what CWM uses. I was pretty much correct as far as that point goes, because no where inside of CWM does it have options for .tar files, etc...
Now, these modem firmwares, and all these other EL29, FC this and FU that (lol) can be a get confusing and i just want to be sure i do everything EXACTLY as they say it needs to be done, which of course means, don't ASSUME anything and always do your research and get clarification. Otherwise, you might end up with a $600 paperweight that reminds you of your stupidity on a daily basis when you look at it.
I appreciate all of your guys's input and i consider this is a great community.
Androidforums.com + XDA-Developers.com = Excellent resources and tools.
I'll admit i was in a bad mood and cussed out a MOD on androidforums one day, but its all good. People have bad days.... Hopefully that guy didn't take offense to the comments i made about his homosexuality lol. Won't happen again. I'll just beat up a co-worker instead haha.
Thanks again! NERD POWER!
Fyi we tell newbs to go read because that is how you learn....if you don't want to put the time into reading and learning you probably want a different phone..we all learned how to do things on this phone by reading and galaxy s3 will be similar so it's something most should do is read read read
Sent from my SPH-D710 using xda premium
E is the year. E was 2011, F is 2012, etc.
L is the month. A=Jan, B=Feb, C=Mar, ... L = Dec
29 is the day so in EL29 would be dec 29th 2011
ungovernable1977 said:
ok general rule for samsung at least, only use GB firmware (kernel) with GB roms (system), ICS with ICS... For the QBKing example, i didnt watch the vid, but usually he says where hes coming from. Odds are its EL29, the official stock, if you wanted to do what he did, get to the starting point he was on then go from there. ...
I think once we get ICS official and the first onslaught of ROMs come out, things will settle down a lot.
Click to expand...
Click to collapse
Thanks for the clarification. I'll take my phone back to stock and start again at some point. Think I'll still wait for the more finished ICS ROMs to play it safe. Some kind soul will no doubt write a howto for those less able among us.
Edit: decided to go back to stock and update to EL29 following the vid tut linked above. For anyone googling through, I was a little confused at one point but worked it out. Currently the EL29 file is a zip, inside is a .tar.md5 file which is what you select in Odin for the PDA box. Nice to know it's that easy... when you know how
SRF1.2 was a custom rom for old Epic based on froyo by MysteryEmotionz. It was based on the original work done by k0nane when CIQ was originally removed.
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
Click to expand...
Click to collapse
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
As I understand it, you should just be able to re-apply a stock GSM ROM to your Galaxy Nexus to get back to the original state of things. That's the whole point of a Nexus - it's stock with no customisations etc. It sounds like you'll have start from the very beginning and reinstall apps etc. but I guess you've already bitten that bullet, and presumably you're happy with your current ROM configuration?
It's not clear what recovery you have installed at the moment. You've made mention of CWM ... Clockwork Mod recovery possibly installed in that case? Again, as I understand it, Clockwork Mod recovery means you can't <s>receive</s> apply OTA updates. If you're on a stock ROM you should still receive notification about them though? If you are truly on stock, but have the Clockwork Mod recovery installed you can reinstall the stock boot recovery image. You should be able to find the stock images via a google search easily enough.
Once you've determined which recovery you currently have installed you'll have a better idea of how to get back to stock everything.
Above all, don't panic
PS I could add that busybox doesn't screw stuff up ... it just allows you to screw things up
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
real_becksaufex said:
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
Click to expand...
Click to collapse
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Syn3rgi3 said:
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Click to expand...
Click to collapse
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
I executed that successfully however CWM still exists =/
Syn3rgi3 said:
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Click to expand...
Click to collapse
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
Disable bootloader?
Pressed from my Maguro
efrant said:
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Syn3rgi3 said:
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Click to expand...
Click to collapse
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
LOL, Telstra
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
DO NOT GET YAKJUDV!!! Try and just get Yakju, Then you will get your updates from Google NOT Telstra. You don't need the Telstra stock rom, you can use Google's Yakju. I have a Telstra one and I get updates from google because I put Yakju. You will need to flash the ROM though your pc. I have been through what you have with the exact phone (Telstra one), If you need any help you can PM me
I agree with the post from Atifsh.
The guide offered by Efrant gives you, step by step, everything you need to reach your goal.
Contrary to your case I did not need to change the factory ROM but I applied the rest of the guide (for instance post 855 in Efrant thread shows what I did).
Since I want to learn I refuse, so far, to rely on a toolkit.
I deeply share Efrant philosophy of learning. And I agree on the purpose of the XDA forum. It is not a walking clinic, it is a hospital implementing new medecines:laugh:.
Finally, taking into account my age I am closer to the hospital than to the clinic.
Thanks to Efrant and few others I am doing "stuff" I did not know I could do.
And, yes I am over the time I used to want and get everything at once.
efrant said:
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
Click to expand...
Click to collapse
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
As you say, the problem is you need the stock recovery for the build that you are on. What build is the backup you restored? If it is ITL41F, then you are in luck. Go to this thread and download any one of the two yakjudv updates to /sdcard. Use CWM to flash it, and you will be all set -- it will wipe CWM and replace it with the correct stock recovery for that build.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And please change the title of this thread to "Return to stock yakjudv" as it is very confusing. Most people refer to stock as yakju or takju for GSM devices.
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
---------- Post added at 07:36 PM ---------- Previous post was at 07:31 PM ----------
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
picton said:
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
Click to expand...
Click to collapse
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
efrant said:
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
Click to expand...
Click to collapse
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
picton said:
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
Click to expand...
Click to collapse
Ok, are you flashing it in CWM? The "red triangle with a robot" IS the stock recovery, it is not an error. What is the exact procedure you are using to flash it?
Ok so here goes a long but detailed read. I am writing this in hopes other fido users searching may find this thread and avoid future questions. Phone came with the TW 4.1.1 from fido and is fully stock.
Brand new S3 Galaxy from Fido (same as rogers) i747M Phone is great but the rooting bug has caught me.
1. I plan to root the device fairly shortly and install a non touchwiz variant. I will be following "High on Android's" Technique. detailed in this youtube video.
Is that method correct for my phone?
or should I be following something different? I just noticed Mr. Robinson posted the Fido TAR with root injected already on it. Does this make any difference? Links to TAR file are here
2. Now assuming I get everything up and running. What is the deal with "Triangleaway" and flash counters? From my understanding, Samsung has a counter installed that ensures they keep an eye on voided warranties due to flashing. Sure thats fine but lets talk about what we can do.
From what I gather, Triangle away will sort me out and get rid of the counters and put them back to zero in case I need to send my phone in for warranty. Is this correct?
Most of the triangle away info I read is for pre 4.1.1 confirmations hence why I ask.
3. Now lets assume I have flashed thephone and I am running CM 10 beautiful. Oh no power button breaks. What will be the required steps to get my phone back to 'stock" to send to Samsung. Will this even be possible to send it in without a worry? I cant seem to find steps online for this.
4. A lot of guides talk about the importance of backing up. Sure sounds great but they dont seem to give detailed instructions. What are the most important things I should backup before, during and after rooting my phone in case I brick it or anything goes wrong? Again any link or detailed explanations would be great.
Sorry for being so exhaustive in my questions. I like to learn it all so I can help other afterwards but also structured the thread so its easy to search for future users.
Happy new year everyone!
sspikey said:
1. I plan to root the device fairly shortly and install a non touchwiz variant. I will be following "High on Android's" Technique. detailed in this youtube video.
Is that method correct for my phone?
or should I be following something different? I just noticed Mr. Robinson posted the Fido TAR with root injected already on it. Does this make any difference? Links to TAR file are here
2. Now assuming I get everything up and running. What is the deal with "Triangleaway" and flash counters? From my understanding, Samsung has a counter installed that ensures they keep an eye on voided warranties due to flashing. Sure thats fine but lets talk about what we can do.
From what I gather, Triangle away will sort me out and get rid of the counters and put them back to zero in case I need to send my phone in for warranty. Is this correct?
Most of the triangle away info I read is for pre 4.1.1 confirmations hence why I ask.
Click to expand...
Click to collapse
I'm going to answer these two questions together, because they're interrelated.
There's no one single root method that's more "correct" than any of the others. The key difference between the end result of most of the methods is whether the flash counter has been tripped, which occurs (under circumstances where you're coming from ICS) if you use Odin to flash something other than a stock image (untouched or rooted as in Mr_Robinson's case). You can also trip the flash counter if you have the Jelly Bean boot loader and boot into a non-stock recovery image.
Thus, if you want to avoid tripping the counter for as long as possible, you want to use a method for rooting that doesn't trip the counter, such as the Mr_Robinson method.
If you're going to flash a custom recovery after working from stock JB, you'll probably end up tripping the flash counter the moment you boot into it, in which case (assuming your phone is still rooted) you could use Triangle Away to reset said flash counter.
sspikey said:
3. Now lets assume I have flashed thephone and I am running CM 10 beautiful. Oh no power button breaks. What will be the required steps to get my phone back to 'stock" to send to Samsung. Will this even be possible to send it in without a worry? I cant seem to find steps online for this.
Click to expand...
Click to collapse
I'd do the following:
Triangle Away, if the flash counter isn't 0;
Boot into download mode;
Flash a normal stock image from here; [*]Boot into stock recovery and wipe data/cache; [*]Boot phone as normal.
sspikey said:
4. A lot of guides talk about the importance of backing up. Sure sounds great but they dont seem to give detailed instructions. What are the most important things I should backup before, during and after rooting my phone in case I brick it or anything goes wrong? Again any link or detailed explanations would be great.
Click to expand...
Click to collapse
There are two major approaches you can take here, and using both of them responsibly is probably a good idea.
Titanium Backup, usable if your device is rooted, can back up all of your application data and some system settings; it's great for transferring data between ROMs and/or between devices altogether (I've done both). Most people I know of only use it for the former, as trying to restore system data with TiBu usually causes bizarre and unpredictable effects (with a few exceptions, such as text message data).
With a custom recovery, you can make what's called a "nandroid" backup, which is a complete image of your current ROM and userland data; it's most useful when you want to make a restore point of sorts for if you're, say, flashing experimental ROM images or other things you don't expect to work very well.
Hope this is of help.
smelenchuk said:
I'm going to answer these two questions together, because they're interrelated.
There's no one single root method that's more "correct" than any of the others. The key difference between the end result of most of the methods is whether the flash counter has been tripped, which occurs (under circumstances where you're coming from ICS) if you use Odin to flash something other than a stock image (untouched or rooted as in Mr_Robinson's case). You can also trip the flash counter if you have the Jelly Bean boot loader and boot into a non-stock recovery image.
Thus, if you want to avoid tripping the counter for as long as possible, you want to use a method for rooting that doesn't trip the counter, such as the Mr_Robinson method.
If you're going to flash a custom recovery after working from stock JB, you'll probably end up tripping the flash counter the moment you boot into it, in which case (assuming your phone is still rooted) you could use Triangle Away to reset said flash counter.
Click to expand...
Click to collapse
It seems the flash counter is a lot less worrysome to me now that you indicated I can always go back to a stock rom and return it for warranty regardless if it has a counter or not. Now I wonder why people even worry about tripping it.
I'd do the following:
Triangle Away, if the flash counter isn't 0;
Boot into download mode;
Flash a normal stock image from here; [*]Boot into stock recovery and wipe data/cache; [*]Boot phone as normal.
Click to expand...
Click to collapse
So Sounds to me like I should not worry about flashing and warranty correct? There will always be a method to go back to my phone in order to deal with warranty if something physical goes wrong? Any guide you could point me towards for this? I found this http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-canadian-galaxy-s3-sgh-i747m-stock-roms/
but it doesnt mention any fido files (understandable since its new)
There are two major approaches you can take here, and using both of them responsibly is probably a good idea.
Titanium Backup, usable if your device is rooted, can back up all of your application data and some system settings; it's great for transferring data between ROMs and/or between devices altogether (I've done both). Most people I know of only use it for the former, as trying to restore system data with TiBu usually causes bizarre and unpredictable effects (with a few exceptions, such as text message data).
With a custom recovery, you can make what's called a "nandroid" backup, which is a complete image of your current ROM and userland data; it's most useful when you want to make a restore point of sorts for if you're, say, flashing experimental ROM images or other things you don't expect to work very well.
Hope this is of help.
Click to expand...
Click to collapse
These two forms of backup I am use to and have used extensively on my nexus S. What I am worried about is more deep "system" type backups people do. is there any for this phone I should do through odin or Kies?
Edit: almost forgot to say thank you!
How come the root66_FMC_I747MVLDLK4.7z download link keep saying searching for mirror, please wait? Waited for 1 hr, no links. Refresh, no links.
thats odd I tried it yesterday and it worked
send a PM to the thread starter he will put up a new mirror I guess
Hey guys, I am new to this forum here but before anyone flames me, I did read the faqs and tried to uninstall from there but it did not work out. Apparently I dont think you can get rid of CM11 since you cant install any stock firmware older than it? Before I installed CM11, I was on jellybean. I had tried to find the latest kitkat update for the s3 (att) and there is no file of it found online (tried sammobile). When I tried flashing an older firmware with ODIN, it just fails at "NAND!". Any help would be appreciated. I am COMPELETELY new at this so specific directions would be appreciated!
I really do love cyanogenmod but there are simply too many glitches and not enough guidance on how to fix em. I am, however, currently using it on my HP touchpad, if anyone remembers what it is . Maybe ill go back to using it in the future.
thanks!
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
DocHoliday77 said:
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
Click to expand...
Click to collapse
..
I am on "I747UCUEMJB"
and i am not sure what build i am on but according to my "build number"this is what it says: "cm_d2att-userbug 4.4.2 KOT49H"
The main issue is, I cannot find 4.3 update anywhere on the internet
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
DocHoliday77 said:
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
Click to expand...
Click to collapse
i have no idea what MJB means (i google'd it) and i just found out what my bootloader version is via download mode (its at the very bottom) and i have version 2.0?
ok downloading the giant file now. will report details. just follow instructions in the first link?
[sorry, like i said, im a noob so i really apologize for the lack of terms here]
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
DocHoliday77 said:
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
Click to expand...
Click to collapse
Cool! Got it. I think that was my main problem. I could only find 4.0 (or 4.1) and have been trying to use that on ODIN. Perhaps that was the main issue....
Oh already ran it and got "I747UCUEMJB", sorry if didnt say it properly.
Really appreciate the help! Ive at this for days and no solutions. Sometimes the hacking/custom firmware isnt for everybody
Ill update what happens. Download is taking forever.
EDIT: BTW, for the first link, which poster am I gonna have to follow? im assuming "garbage guy"?
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
DocHoliday77 said:
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
Click to expand...
Click to collapse
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
david12795 said:
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
Click to expand...
Click to collapse
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
DocHoliday77 said:
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
Click to expand...
Click to collapse
TIL that OTA arent as fast. Ill download KIES and give it a try.
Just installed KIES and it said my phone has the latest firmware?
david12795 said:
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
TIL that OTA arent as fast. Ill download KIES and give it a try.
Click to expand...
Click to collapse
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
david12795 said:
Just installed KIES and it said my phone has the latest firmware?
Click to expand...
Click to collapse
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
DocHoliday77 said:
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
Click to expand...
Click to collapse
No no! Its fine, I wasnt planning using it or anything, I just wanted to get rid of it since I have no use for it, no need to apologize. , I was fully aware that I would lose all files, other than SD ext drive. I just wanted to make sure that all files are in the right place and none of the unnecessary files are taking up space (e.g. files from cyanogenmod)
As for the update, I talked to a samsung representative and they said one can go to Best Buy and get it updated there through a technician, so Ill try that later since I am close to it ATM. If it back fires, Ill try your suggestions.
I really do appreciate for the help , I have been completely lost for days but it turns out I was just using the wrong firmware. Thanks for pointing it out. Good karma is coming your way . Hopefully one day, I will be here again and trying out a new custom firmware.
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
DocHoliday77 said:
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
Click to expand...
Click to collapse
Ill hope for the best and prepare for the worst.
Of course, if the worst happens, I can just use one of your links you mentioned. :good::good:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!
General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.
Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.