[Q] Just got this phone and need some general info from - T-Mobile, Samsung Galaxy SIII

So I am a well seasoned samsung vet. I had the vibrant the s2 I curently have the note 2 running the latest cm 10.1 nightliy and now I am the proud owner of a brand new s3 Yay. So I was wondering if this is the same as the note 2 as far as design across carriers and software across carriers. Can we use att roms without port or kernel changes? Are the AOSP roms identical? I havent looked yet but I assume that all I got to do is use odin to install twrp or cwm and then I can install su and root. Also It came with jb 4.1.1 the build number is t999uvdlja. Is that the latest build? every time i check for an update it tells me i have to wait in line. not word for word but that is what it is telling me. I have never seen that. So I am just wondering if I am up to date. I dont know if I will be doing any heavy modifications because it is my girls phone so I might just root it and leave it at that.

You practically up to date. There was a newer base pushed but very minor changes. If anything, you can always flash the new modem that came with it to try it out for better results.
You are right about the root process
You can use att builds... Just may have to edit build.prop to make it say t999 and not t747
Enjoy
Sent from my SGH-T999 using Tapatalk 2

Thanks for the quick answer galaxys3guy I have one question about the root process. On the newer android builds like what came on my note2 there is a built in fail safe that automatically rewrites the stock recovery. So 1. has that been implemented on the latest jb builds on this phone? And if so how do we get around it? When I went to root my note 2 I actually was able to use the exploit that samsung screwed up. If I remember corectly that exploit was originally found on the s3 but I know that samsung recently updated the nate2 so I would assume they updated the s3 to patch the exploit. So the only other way is to A install a custom rom with root via odin or use ADB to disable that function that rewrites recovery. I looked around and didnt see much about rooting for this phone. So what I think I will do is use chainfire's autoroot. Then flash twrp via odin and be done with it. But I was just wondering about the workarounds. As you can probally tell I only half know what I am talking about. I am self taught so sometimes things just dont make sence to me when they should it takes me a while but I usually get it.

Lol I'm glad u know half of what u are talking about cuz I don't
All I did... Was booted into download mode... Put twrp in the PDA section of Odin, and flashed the recovery. (After it was done... If I remember right, I had to unplug and manually reboot because something with Odin was not working... But that was just for me... So if u have that issue where your phone won't boot after it says pass, just unplug and reboot urself). From there I booted into recovery and flashed supersu...
Sent from my SGH-T999 using Tapatalk 2

Hey congrats on New gs3 bro!
I kind of went thru something similar to your rooting proces.
You should check out galaxys3root.com. it is super helpful site. basically when you run Odin to root ( installing custom recovery like cwm or twrp, ) you need to uncheck all tick boxes especially auto-reboot and F.reset time buttons. Otherwise phone will reboot and reinstall stock recovery and in some case stuck on boot.. when you un-check them phone will not reboot after installing. You just pull battery after install and boot into custom recovery by volume+ , home and power together. I'm afraid there no patch that I know of ATM. Good luck..
Sent from my PG41200 using xda premium

Thats what I meant ^^^
Thanks man
Sent from my SGH-T999 using Tapatalk 2

GalaxyS3Guy said:
Thats what I meant ^^^
Thanks man
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I did have a problem with my T-Mobile branded S3 going back to stock recovery and found there are 2 files that need to be renamed using the file explorer of your choice.
install-recovery.sh located in the /system/etc folder
recovery-from-boot.p located in the /system folder
I just add a .bak to the file name. Once this is done install CWM again and it will be OK. Also of note it will trip the counter built into the phone every time CWM is used. Download Triangle Away from the market to reset the counter when needed.

okay Now I see. So One way to fix this is to uncheck everything in odin so that the phone doesnt reboot itself. Then pull the battery and reboot into recovery right away and that will somehow overide the rewrite process.
But GTwalling I have q question. Do you need to be rooted to rename those files? Or does the security leak make that not matter? I know that the leak basically makes one of the partitions read-write when it should be read only. I am almost positive that the last update that you guys got would have patched the exploit because it did with the note2. But in any case basically I would go into /system/ect folder then find the file: install-recovery.sh then rename that file so it should look like this when done install-recovery.sh.bak then do it with the other file as well. Is that right? basically all you are doing is making the file not run without deleting it. Cool. I just learned something. It seems like the peope in this fourm are cool and helpful. Maybe I will learn alot here.
Another thing I noticed that there is a toolkit from mskip I think. I know he does good work from his toolkit for the s2. Maybe there is a way to use his tool kit to disable that rewrite process. The one for the note2 has that feature but it is not made by mskip he actually wanted to make one and posted in the general fourm for ideas and a bunch of the idiots that are in that fourm were like we have one already and we dont need another. I tried to encurage him to make one and not listen to those idiots but It never came to be. But i'm sure if I msg him and tell him he can put that in if it isnt already. I personally dont like to use toolkits because I want to do everything myself but I also think they are a way of the future. Alot of people just want to point and click to do things and dont want to know what the whole thing is.

Related

[ROM][STOCK][FROYO] EC03 Froyo Update

Here is the update that everyone has been waiting for At the moment, I'm only providing the modem, and rooted, stock, deodexed version of the ROM. There will be a cleaned up version to go along with all of this in due time, but we're currently working out some problems with it. I would like to note that despite this being the Froyo update, it is not without its own set of problems, and odds are you may never see another update outside of this from anywhere. However, the benefits of getting Froyo will outweigh the problems with it for most people, so have at it.
You will need a few things to get this, first, the downloads list here will be needed (obviously). You'll also need to have CWM setup and know how to use Odin. Heimdall will also work for those of you not on Windows, but I'm not providing any instructions for flashing using Heimdall. Also note that you will want to wipe data or perform a factory reset before booting into Froyo to avoid any problems. While you may get away with not doing it, you could end up with several problems, so my recommendation is to wipe data. Also, you can flash the ROM first, or flash the modem first, which ever you want to do. There isn't really a required order for it, as long as you do both parts.
[size=+1]Instructions[/size]
Download everything you need.
Odin
Froyo Radio
ROM+Kernel
CWM Kernel
CWM update.zip
Put the ROM zip and CWM update.zip on your SD Card
Flash the Radio via Odin in the PDA box
Enter CWM and flash the ROM+Kernel
Wipe Data in CWM before restarting your phone
Restart and enjoy Froyo
[size=+1]Downloads[/size]
Modem
ROM+Kernel
FAQ
How can I donate to you for this?
You can either click the "Donate to me" button above my avatar, or go through this link. Don't feel obligated to donate though, as Verizon should have given this to you (the users) long ago.
Can I still receive updates after flashing this?
You cannot receive updates after flashing this unless you revert back to DL17, which is the latest official software released by Verizon and Samsung.
If I can receive updates on this, how can I restore back to DL17?
I've been sending this to several people already that have had problems with their phones. If you need to revert back to DL17 for any reason, download this. You will need 7-zip or similar to extract it. Once you have the .tar.md5 file, flash it in Odin via PDA like you did for flashing the modem to get Froyo.
Can I return my phone to Verizon for warranty repair/service with this on my phone?
No. If you need any sort of help with your phone from Verizon, you will need to have the stock DL17 ROM on your phone. Anything else and you have voided your warranty and Verizon and/or Samsung will not have to do anything to help you. See the above question for a package to restore your phone to the latest stock software.
Are there any bugs in this release?
Yes there are, just as there is with any software. I do not know what the bugs are though off hand though as I have not been using this update. I also cannot say whether any of the problems you may have will ever get fixed, seeing as you can't even get a straight answer on why the update has been taking so long.
Is xxx modification/theme compatible with this?
Odds are that it isn't. All of the current themes and modifications for DL17 will not work on this package. They will all need to be updated to be able to work. Given that this is a relatively new release, this could take some time, especially given that it is the summer and people are on vacation (I'm looking at you trailblazer ). We will work though to try and get all of the mods ported from DL17 to EC03 so that you don't have to give up anything to upgrade.
Will you release a "clean ROM" based on this?
Yes, and it is already in progress. I have sent it out to a couple people already to ask for feedback and any issues. Once they say it is ok, I'll create a new thread with the cleaned up version. There is currently no ETA on when it will be released though.
Are there any other kernels I can use with this besides the one that comes with it?
At the moment, there isn't. I'm trying to get a custom kernel to work, but it has some problems. At the very least, we can customize the stock kernel some, but I do not know if a full source built kernel will ever be available.
Can I flash this if I am on the voodoo kernel?
No, if you are running the voodoo lagfix kernel, you will want to disable voodoo prior to doing anything. If you don't, you'll be in for some fun times with Odin getting your phone back in a usable state.
Can I get something included in the FAQ?
Yes you can. Just create a post with the following template, and I'll try to keep the FAQ updated. If I don't see it or add it right away, don't worry, I'll try and update it. If it has been a week or two and I still haven't responded, just send me a message with a link to what you want included. Here is the format to use:
Code:
[PLAIN][b]Question goes here?[/b][/PLAIN]
Answer goes here.
I'm getting ready to download it
When I go to flash the radio, Odin says it's an invalid image type
circa881 said:
When I go to flash the radio, Odin says it's an invalid image type
Click to expand...
Click to collapse
It should work You aren't extracting or renaming it at all are you?
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
circa881 said:
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
Click to expand...
Click to collapse
Your phone is in download mode when you're attempting to flash via Odin?
XD Now I feel like a ruh-tard. I forgot about that part
Wait, it's still saying invalid image type
I'm in shock... I'm on this forum every day and I missed this?! I'm going to install this and mess around with it. Ill post any bugs I find later this evening..
Kudos @imnuts for the effort!
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
jaizero said:
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
Does it really matter?
No... No it doesnt.. Its working perfectly by the way.. But Im sure you already knew that lol..
If jaizero got it to work, why couldn't I?
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
jaizero said:
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
It came from heaven!!!
Sent from my Mind
^ lolololol
Sent from my SCH-I400 using XDA Premium App
FROYO
i think i love you (no homo)
I successfully loaded the ROM.
It hang a bit longer than usual on the verizon logo but after that no issues.
Thanks imnuts and anyone else that worked to make this possible.
Kay, how are people getting this to work when I couldn't get the radio flashed
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
Ok I dl'd both files, I have Odin1.3 both blue n yellow CWM update.zip but what is CWM kernal?
P.S. I totally love you guys and many thanks to nuts for confirming my faith in opensource and saving my phone
Sent from my SCH-I400 using XDA Premium App

Rooting Gnex GSM/HSPDA v4.0.2 Optus Stock

Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
What does stock stand for?
udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.
El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App
Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.
I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.

[Q] why is the stock att rom the only one nobody has?

After being an iphoner right from the get-go, (jailbreaker of course), i finally got bored and moved on. plus, i really wanted a big screen. so i got a gn2 about a month ago, and rooted it on my mac two weeks ago using the CWM/mac/heimdall method. i have been running the stock-but-rooted rom, and not put on a custom rom yet. i have no real good reason for this, but for pure educational purposes and a desire for complete control, and/or warranty reason should they arise, i would like to do a full unroot and restore a stock rom. BUT everywhere I look, I can easily find every possible stock rom from every carrier and every country... except at&t (sgh-i317). i know i can use other that are similar. but my question is, WHY is what is potentially the most common/popular rom of them all, NOT widely available?
second question is: ok, so it's hard to find. but does it exist at all? if so, where? i tried to flash this one, (not allowed to post the link), using the CWM console that got put on the phone when I rooted it, but is fails every time I try saying the file or rom is "bad". is it bad, or do I need to do something else? FWIW, the fail flashings of this rom do no brick my phone. it reboots normally to the stock rooted rom i've been using since I rooted it two weeks.
oops, looks like i can't post links but the sgh-i317 rom i found was at a well-known net repository of stock roms
-peter
I found this over in the dev section in the Reference sticky.
http://www.hotfile.com/dl/181184536/fa1bbef/I317UCALJ2_I317ATTALJ2_ATT.zip.html
I haven't downloaded it, so I couldn't tell you what's in there. It might be a CWM flashable rom-only zip, or it might be odin-flashable files in there. You'll have to download and see.
Edit: Did a little more research.. That's an Odin tar file inside the zip.
pcrussell50 said:
After being an iphoner right from the get-go, (jailbreaker of course), i finally got bored and moved on. plus, i really wanted a big screen. so i got a gn2 about a month ago, and rooted it on my mac two weeks ago using the CWM/mac/heimdall method. i have been running the stock-but-rooted rom, and not put on a custom rom yet. i have no real good reason for this, but for pure educational purposes and a desire for complete control, and/or warranty reason should they arise, i would like to do a full unroot and restore a stock rom. BUT everywhere I look, I can easily find every possible stock rom from every carrier and every country... except at&t (sgh-i317). i know i can use other that are similar. but my question is, WHY is what is potentially the most common/popular rom of them all, NOT widely available?
second question is: ok, so it's hard to find. but does it exist at all? if so, where? i tried to flash this one, (not allowed to post the link), using the CWM console that got put on the phone when I rooted it, but is fails every time I try saying the file or rom is "bad". is it bad, or do I need to do something else? FWIW, the fail flashings of this rom do no brick my phone. it reboots normally to the stock rooted rom i've been using since I rooted it two weeks.
oops, looks like i can't post links but the sgh-i317 rom i found was at a well-known net repository of stock roms
-peter
Click to expand...
Click to collapse
I had to do a double take and make sure I wasnt writing this post. I am in almost the same boat under similar circumstances. I have been waiting for the stock rom for 2 months . I got my AT&T Note 2 in November and went through the root process and had a problem somewhere along the way and had to use a custom rom to get up and running again. Since then I have waited patiently for a stock rom to show up that would get me back to normal . My phone has been working , but my signal strength is bad and I can show 3 bars on my phone , but when I go to make a call , it drops to zero and I cannot make a call . This happens at work all the time and at home most of the times. My incoming calls are not accepted and are routed to my voice mail , which I cant listen to until I get to an area where I get a better signal . I cannot live like this for 2 years , I need this fixed . Just want to get back to stock , with no root , no custom roms , etc . I never had this problem with my iphone ! Love the Note 2 , but come on man!
Buckeyeken said:
I had to do a double take and make sure I wasnt writing this post. I am in almost the same boat under similar circumstances. I have been waiting for the stock rom for 2 months . I got my AT&T Note 2 in November and went through the root process and had a problem somewhere along the way and had to use a custom rom to get up and running again. Since then I have waited patiently for a stock rom to show up that would get me back to normal . My phone has been working , but my signal strength is bad and I can show 3 bars on my phone , but when I go to make a call , it drops to zero and I cannot make a call . This happens at work all the time and at home most of the times. My incoming calls are not accepted and are routed to my voice mail , which I cant listen to until I get to an area where I get a better signal . I cannot live like this for 2 years , I need this fixed . Just want to get back to stock , with no root , no custom roms , etc . I never had this problem with my iphone ! Love the Note 2 , but come on man!
Click to expand...
Click to collapse
Why not flash cleanrom att special edition and the correct modem. I have not had any issues with his rom. Did you do a backup of the stock rom before you flashed a custom rom? If you did go back to your stock backup.
www.stockroms.net
so i see we're all pretty junior here. none of the experienced folks have chimed in here yet.
getting back on topic, you could make a case that the att stock rom could/should be the most widely used rom in the entire gn2 world. yet it does not appear to be widely available, when the most obscure ones are. why is this?
-peter
thank you for posting that link, "member", because i couldn't. that's where i got the one that gives a "bad" or "corrupt" when i try to flash it in the CWM console.
sooo, is it corrupt? or is it user error on my part where i have to do something to the .zip file to make the CWM flash console able to use it? or do i have to flash it with mobile odin, (which i don't know how to use, yet).
-peter
ok member, i just unzipped the sgh-i317 file from stockroms and there is a .tar file in there, but "kies" is in the name of it. does that mean i have to use kies to flash it?
-peter
Hey so the only way to get back stock ATT (well the only way I know) is through ODIN. So follow these steps if you want your old AT&T unroot back, then root it again for a stock root experience.
http://galaxynote2root.com/galaxy-n...ootunbrick-galaxy-note-2-with-stock-firmware/
---------- Post added at 12:13 PM ---------- Previous post was at 12:13 PM ----------
And that .tar file is read only by odin I believe. I do not think you can flash it through CWM or TWRP, but I am fairly new to android (last 2 weeks, and before that 6 years of iOS). So I could be wrong.
UrbanLagoon said:
Hey so the only way to get back stock ATT (well the only way I know) is through ODIN. So follow these steps if you want your old AT&T unroot back, then root it again for a stock root experience.
Click to expand...
Click to collapse
i'm already living the stock root experience. no custom roms, just the stock root from galaxynote2root web site, except i have a mac, so i used the heimdall front end max said to use.
[removed link because it will not let me post any]
UrbanLagoon said:
And that .tar file is read only by odin I believe. I do not think you can flash it through CWM or TWRP, but I am fairly new to android (last 2 weeks, and before that 6 years of iOS). So I could be wrong.
Click to expand...
Click to collapse
you sound almost like me. was with ios from the beginning, (and palm/treos before that), and i just went to android a month ago. been rooted on the stock root rom for last two.
-peter
What are you talking about? http://forum.xda-developers.com/showthread.php?t=2070105
SmiLey497 said:
What are you talking about? http://forum.xda-developers.com/showthread.php?t=2070105
Click to expand...
Click to collapse
He wants completely stock, as shipped. That's how I understand it anyway.
For pcrussell50, you'll use Heimdall to flash that .tar file. I use Windows so I've never used Heimdall, so I definitely cannot help you with it. Good luck!
http://forum.xda-developers.com/showthread.php?t=2020607
success... i think. used mobile odinPRO to flash the rom on stockroms net then rebooted in to download mode and sure enough, there is no longer a binary count, where it used to read "1" and it shows the binaries as stock. a further check under settings>about device>status, all the way at the bottom shows device status: normal. it used to say device status: modified until this flash of the stock rom from stockroms.
now the mystery... am i still rooted? SU, Ti backup, triangle away (which i never used), and mobile odinPRO icons are still on the home screen. i do not know if these things go away automatically after unrooting or if they still hang around. but when i try to boot into the CWM recovery mode, (volume up-center home-power it boots to a similar, but stock looking interface. that makes me think it's unrooted now.
overall pretty satisfied. i'll roll like this for a few days and try to pick up the new ota update and re-root again.
thx, peter
even more success...
i picked up the ota update to 4.1.2 just as if it was totally stock--so i think now i AM totally stock, after waking up this morning rooted, and spending parts of today unrooting back to factory stock. so now i know i can do it. i'll re-root here again when i can get some time. thanks all, and i'll try to help anyone else in my boat as best i can.
-att gn2 sgh-i317, now running 4.1.2
-rooted to stock rom, then unrooted
-using a mac for rooting/syncing
regards,
-peter
pcrussell50 said:
success... i think. used mobile odinPRO to flash the rom on stockroms net then rebooted in to download mode and sure enough, there is no longer a binary count, where it used to read "1" and it shows the binaries as stock. a further check under settings>about device>status, all the way at the bottom shows device status: normal. it used to say device status: modified until this flash of the stock rom from stockroms.
now the mystery... am i still rooted? SU, Ti backup, triangle away (which i never used), and mobile odinPRO icons are still on the home screen. i do not know if these things go away automatically after unrooting or if they still hang around. but when i try to boot into the CWM recovery mode, (volume up-center home-power it boots to a similar, but stock looking interface. that makes me think it's unrooted now.
overall pretty satisfied. i'll roll like this for a few days and try to pick up the new ota update and re-root again.
thx, peter
Click to expand...
Click to collapse
If im reading this correctly u used mobile odin.in that app is a feature called ever root if u had that "ticked" it will retain root...there is a app in playstore u can cheak if u have root
Sent from my SAMSUNG-SGH-I317 using xda premium
twanskys204 said:
If im reading this correctly u used mobile odin.in that app is a feature called ever root if u had that "ticked" it will retain root...there is a app in playstore u can cheak if u have root
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
i must not have had it ticked, because after reading your post above, i went to odin (still on my phone) and tried to open it and it told me i need to have root (super user) to use it. it said no such thing when i was rooted, so at this point i _think_ i'm not rooted. i'll look for the app in the app store for even more confirmation.
normally i'm not such a blabbermouth with posting, but i need to get up to 10 so i can post links. then you might not hear from me as much unless i actually have something of value to contribute.
-peter
Deleted as I was too late to the party.
pcrussell50 said:
i'm already living the stock root experience. no custom roms, just the stock root from galaxynote2root web site, except i have a mac, so i used the heimdall front end max said to use.
[removed link because it will not let me post any]
you sound almost like me. was with ios from the beginning, (and palm/treos before that), and i just went to android a month ago. been rooted on the stock root rom for last two.
-peter
Click to expand...
Click to collapse
So glad I left iOS. Even with a jailbreak it's nothing compared to android. I been rooted since day 1 and now I'm running the type 3 international stock rom by micosa. It's beautiful! Love the inverted apps for battery saving! I also have a swift flow beta keyboard and I lowered the height of the keyboard so there is more screen real estate with the keyboard up. And with s pen board switcher, I can go to handwriting mode as soon as I pull out s pen!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

[Q] to root or not to root, that is the question

So I recently cut ties with my rooted OG evo :'( and have switched to a sprint galaxy s2, aka the epic 4g touch fi27. The first thing I did was head over to these forums because of course my first thought was let's open this bad boy up. But after reading how to, how not to, how to avoid, etc etc it seems that either: a. I am over complicating it, or b. it would be easier, albeit not as much fun, if I just stayed stock due to the overwhelming ways to brick such a (from what I can tell) fragile device. Now I am in no ways new to rooting and all this jazz but it just seems like the risk might overweigh the outcome of rooting and hard bricking my epic 4g touch device?
so this is where I turn to you, the veteran users of the epic 4g touch. What are your thoughts, tips, tricks, advice, or kicks in the right direction?
any help is much appreciated
Just root the phone already
Read the directions and most of a thread before flashing a new rom and you will have very minimal risk.
root it.
I also came from the OG Evo and was hesitant at first, just do a lot of reading and also get to know PC Odin. Also, if you haven't updated to the latest OTA you could just install that root exploit app to obtain root. Probably the easiest way to root unless you took the new OTA update.
Just read as much as you can before you flash anything and always read the instructions in the OP.
evathaevo said:
So I recently cut ties with my rooted OG evo :'( and have switched to a sprint galaxy s2, aka the epic 4g touch fi27. The first thing I did was head over to these forums because of course my first thought was let's open this bad boy up. But after reading how to, how not to, how to avoid, etc etc it seems that either: a. I am over complicating it, or b. it would be easier, albeit not as much fun, if I just stayed stock due to the overwhelming ways to brick such a (from what I can tell) fragile device. Now I am in no ways new to rooting and all this jazz but it just seems like the risk might overweigh the outcome of rooting and hard bricking my epic 4g touch device?
so this is where I turn to you, the veteran users of the epic 4g touch. What are your thoughts, tips, tricks, advice, or kicks in the right direction?
any help is much appreciated
Click to expand...
Click to collapse
You could always just go stock rooted. It's really not that hard to not brick the device, just follow directions and don't skip any steps trying to save time.
I like to break stuff!
Raistlin1 said:
I also came from the OG Evo and was hesitant at first, just do a lot of reading and also get to know PC Odin. Also, if you haven't updated to the latest OTA you could just install that root exploit app to obtain root. Probably the easiest way to root unless you took the new OTA update.
Just read as much as you can before you flash anything and always read the instructions in the OP.
Click to expand...
Click to collapse
From what I understand sprint pushes ota's when you activate a new phone so unfortunately I'm stuck on fi27 even if I didn't want to. does that make a difference?
evathaevo said:
From what I understand sprint pushes ota's when you activate a new phone so unfortunately I'm stuck on fi27 even if I didn't want to. does that make a difference?
Click to expand...
Click to collapse
Actually FI27 is the version right before the new OTA, the newest version is FL24 that has just been released and just being pushed out now. My wife's phone just received that OTA but mine has not yet.
Raistlin1 said:
Actually FI27 is the version right before the new OTA, the newest version is FL24 that has just been released and just being pushed out now. My wife's phone just received that OTA but mine has not yet.
Click to expand...
Click to collapse
so root exploit would be the way to go?
evathaevo said:
so root exploit would be the way to go?
Click to expand...
Click to collapse
You can either oneclick to root or use exynos abuse apk to root on fi27 if you want to stay stock rooted for now I'd just use the exynos abuse method and then if you decide you want to flash something later use mobile odin or mobile odin pro to flash a kernel+recovery without increasing your flash counter
I like to break stuff!
Rooting in and of itself doesn't present a risk as far as the bricking you're referring to goes. It's when you start messing around with unsafe kernels/recoveries that it becomes an issue, but all of the modern kernels/recoveries are safe.
Thanks for all the input guys. I really appreciate it. After much research I've realized that all I'm looking for is jelly bean on my e4gt because that's what i had running on my OG Evo and I've come across a confusing issue. It seems that it is possible to flash jb through Odin without having root. Now coming from my evo this sounds too good to be true but is it?
Sent from my SPH-D710 using xda app-developers app
Yeah, you can definitely flash stock ROM images through Odin without having root. Samsung devices have a download mode for emergency recovery that allows you to do such things in Odin. However, I believe it's limited to the stock images (and the stock images can be pre-rooted), so if you want an AOSP-based ROM instead of TouchWiz, you'll still need to flash it through custom recovery after you're rooted. Also, be aware that flashing ROM images with Odin will completely wipe your device, so back up anything you want to save before you do it.
evathaevo said:
Thanks for all the input guys. I really appreciate it. After much research I've realized that all I'm looking for is jelly bean on my e4gt because that's what i had running on my OG Evo and I've come across a confusing issue. It seems that it is possible to flash jb through Odin without having root. Now coming from my evo this sounds too good to be true but is it?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
if you want cm or aokp you'll need to odin a custom safe recovery then flash those roms.
I know how you feel about all of this. I'm pretty sure I posted something awhile back about this when I first got the phone. It definitely seems like a lot when you don't know how to do much. It's actually quite simple, as as stated above, as long as you follow directions you will be good to go! :good:
Let me see if I can give you some guide on how I learned how to do things to kind of just get in the groove of it.
First things first, you are going to want to check out this page:
http://forum.xda-developers.com/showthread.php?t=1416477
On that page you will be able to download the PC ODIN for stock rooted Gingerbread. You will run that in download mode on your phone (Vol Down + Power.) Make sure you have the Samsung drivers installed on your computer which you can also get from that link. Just follow the instructions to get that installed and you should be good to go. When it is done you can go to Settings > About Phone and make sure that you are running Android 2.3.6 or Gingerbread and you are now rooted at this point (look for the superuser icon.)
After that is done go ahead and check out this page:
http://forum.xda-developers.com/showthread.php?t=1342728
This is the auto root package that will give you the custom recovery that you will want to use for flashing. There is a file in the rar that is called "RUNFIRST" which, obviously, you will run first. It will bring up a Command Prompt for you to type in selections. Since you are running EL26 at this point you will want to hit "C." This next selection page is your recovery selection.
Look down for EL26 and we recommend Chris41g's recovery. The other is Rogue which you can't do too much with. You will want to make sure you go into Settings > Applications and check the box for USB Debugging. Plug the phone back in, and hit "I" <==-- Capital EYE to avoid confusion, and let it do it's work. It will restart the phone, and if all was successful you will now be rooted with a recovery that you can flash from. EL26 recovery is the most recommended recovery to flash from for any ROM. Power down, and use Vol Up + Power to enter your recovery mode.
Using the volume rocker you can hit up + down + up + down to activate the power button selection and from here you can now flash a ROM zip of your choice. If you are looking for a Jelly Bean ROM, might I recommend Sniper's PACman JB ROM that you can find here:
http://forum.xda-developers.com/showthread.php?t=2050948
Good luck!
Be sure to also check out this link:
http://forum.xda-developers.com/showthread.php?t=1525495
That will help you get an idea of things you can do to prevent bricking in the future.
crkdslider said:
I know how you feel about all of this. I'm pretty sure I posted something awhile back about this when I first got the phone. It definitely seems like a lot when you don't know how to do much. It's actually quite simple, as as stated above, as long as you follow directions you will be good to go! :good:
Let me see if I can give you some guide on how I learned how to do things to kind of just get in the groove of it.
First things first, you are going to want to check out this page:
http://forum.xda-developers.com/showthread.php?t=1416477
On that page you will be able to download the PC ODIN for stock rooted Gingerbread. You will run that in download mode on your phone (Vol Down + Power.) Make sure you have the Samsung drivers installed on your computer which you can also get from that link. Just follow the instructions to get that installed and you should be good to go. When it is done you can go to Settings > About Phone and make sure that you are running Android 2.3.6 or Gingerbread and you are now rooted at this point (look for the superuser icon.)
After that is done go ahead and check out this page:
http://forum.xda-developers.com/showthread.php?t=1342728
This is the auto root package that will give you the custom recovery that you will want to use for flashing. There is a file in the rar that is called "RUNFIRST" which, obviously, you will run first. It will bring up a Command Prompt for you to type in selections. Since you are running EL26 at this point you will want to hit "C." This next selection page is your recovery selection.
Look down for EL26 and we recommend Chris41g's recovery. The other is Rogue which you can't do too much with. You will want to make sure you go into Settings > Applications and check the box for USB Debugging. Plug the phone back in, and hit "I" <==-- Capital EYE to avoid confusion, and let it do it's work. It will restart the phone, and if all was successful you will now be rooted with a recovery that you can flash from. EL26 recovery is the most recommended recovery to flash from for any ROM. Power down, and use Vol Up + Power to enter your recovery mode.
Using the volume rocker you can hit up + down + up + down to activate the power button selection and from here you can now flash a ROM zip of your choice. If you are looking for a Jelly Bean ROM, might I recommend Sniper's PACman JB ROM that you can find here:
http://forum.xda-developers.com/showthread.php?t=2050948
Good luck!
Be sure to also check out this link:
http://forum.xda-developers.com/showthread.php?t=1525495
That will help you get an idea of things you can do to prevent bricking in the future.
Click to expand...
Click to collapse
VERY informative and VERY helpful. thank you so much. I wish I could click thanks twice
evathaevo said:
VERY informative and VERY helpful. thank you so much. I wish I could click thanks twice
Click to expand...
Click to collapse
You are welcome!
Sent from my Galaxy SII Epic 4G Touch via Tapatalk.
crkdslider said:
I know how you feel about all of this. I'm pretty sure I posted something awhile back about this when I first got the phone. It definitely seems like a lot when you don't know how to do much. It's actually quite simple, as as stated above, as long as you follow directions you will be good to go! :good:
Let me see if I can give you some guide on how I learned how to do things to kind of just get in the groove of it.
First things first, you are going to want to check out this page:
http://forum.xda-developers.com/showthread.php?t=1416477
On that page you will be able to download the PC ODIN for stock rooted Gingerbread. You will run that in download mode on your phone (Vol Down + Power.) Make sure you have the Samsung drivers installed on your computer which you can also get from that link. Just follow the instructions to get that installed and you should be good to go. When it is done you can go to Settings > About Phone and make sure that you are running Android 2.3.6 or Gingerbread and you are now rooted at this point (look for the superuser icon.)
After that is done go ahead and check out this page:
http://forum.xda-developers.com/showthread.php?t=1342728
This is the auto root package that will give you the custom recovery that you will want to use for flashing. There is a file in the rar that is called "RUNFIRST" which, obviously, you will run first. It will bring up a Command Prompt for you to type in selections. Since you are running EL26 at this point you will want to hit "C." This next selection page is your recovery selection.
Look down for EL26 and we recommend Chris41g's recovery. The other is Rogue which you can't do too much with. You will want to make sure you go into Settings > Applications and check the box for USB Debugging. Plug the phone back in, and hit "I" <==-- Capital EYE to avoid confusion, and let it do it's work. It will restart the phone, and if all was successful you will now be rooted with a recovery that you can flash from. EL26 recovery is the most recommended recovery to flash from for any ROM. Power down, and use Vol Up + Power to enter your recovery mode.
Using the volume rocker you can hit up + down + up + down to activate the power button selection and from here you can now flash a ROM zip of your choice. If you are looking for a Jelly Bean ROM, might I recommend Sniper's PACman JB ROM that you can find here:
http://forum.xda-developers.com/showthread.php?t=2050948
Good luck!
Be sure to also check out this link:
http://forum.xda-developers.com/showthread.php?t=1525495
That will help you get an idea of things you can do to prevent bricking in the future.
Click to expand...
Click to collapse
Thanks for the recommendation. I still think the exynos abuse app would be easier
Turn on outside sources, install the app, root, install mobile odin and the flash kernel apks, flash the el26 cwm tar, flash PACman from recovery
Sent from my SPH-D710 using Tapatalk
LightWeight ? PACman ? PA
I'm on Sniper's PACman rom, and it's good. I much prefer it to stock TouchWiz. If you like the stock TW interface, but want jellybean, have a look at Rwilco's 1-click packages. They make flashing and rooting a snap, and the ones I've used don't trigger the yellow triangle or increase your flash counter (if that matters to you). I stuck with FK23 for quite a while (almost a month), and then did something stupid, so I flashed to FL04 then later to PACman.
I am new to rooting phones and like you a bit overwhelmed at all the information. I finally found this Youtube video that is VERY good and makes rooting easy if you are looking to stock root your phone.
http://www.youtube.com/watch?v=jyEvJ92to64

[Q] VM root/recovery weirdness

I'm no stranger to rooting and flashing ROMs, but this is a new one on me. I've had my Virgin Mobile Siii for several months and am pretty happy with it. However, I want to go to CyanogenMod. I also want to root and put a custom recovery on my phone.
My first problem is that I put TWRP on the phone a month or two ago, but when I try to boot into recovery, all I see is the <e3> recovery. I have a TWRP folder with a copy of a Nandroid backup on it, so it must have been there, right? Anyway, to try to figure this out, I downloaded ROM Manager (free version). It says I have both TWRP and Clockwork recoveries on the phone, and trying to have it set me up to use or update either one goes nowhere. Superuser says I'm not rooted.
What I'd prefer to do is get a working root and TWRP recovery on the phone -- I've used it with both an EVO 4G and HTC One V I had in the past and I'm comfortable with it, though if I have to use CWM I can. Then I'd like to use the new CyanogenMod installer if I can be sure it's compatible with the phone. My baseband/build version numbers end with MG2, so I know the phone might be slightly different than a Sprint SIII, but from my exploring the forums here and on other sites it seems to be pretty compatible.
This uncertainty of whether or not I have a custom recovery on the phone makes me very leery of trying to flash a new one without a second opinion. Can anyone help or give me guidance on this?
EelResuah said:
Can anyone help or give me guidance on this?
Click to expand...
Click to collapse
Have you went here and used this method? I would first flash all that way back to stock unrooted on pc Odin to get rid of all the clutter. And if it were me, I wouldn't use ROM manager either. It says Sprint in the link, but everything is the same.
http://forum.xda-developers.com/showthread.php?p=34579827
Sent from my SPH-L710 using XDA Premium 4 mobile app
Gracias
jdsingle76 said:
Have you went here and used this method? I would first flash all that way back to stock unrooted on pc Odin to get rid of all the clutter. And if it were me, I wouldn't use ROM manager either. It says Sprint in the link, but everything is the same.
http://forum.xda-developers.com/showthread.php?p=34579827
Thanks, I will check this one out. The problem I often have is finding my way through a dozen or so threads that almost give me what I need, but this one looks pretty straightforward. I probably won't try it until the weekend, but in the meantime, thanks for the tip!
Click to expand...
Click to collapse

Categories

Resources