Related
can someone with a stock vibrant tell me if you were able to apply the update smoothly. either ota or odin.
and no rooting required please, there are lots of ways there but I can't see anyone posting for a stock phone and not rooted.
Yes, I was able to right now. (10:17pm PDT)
Stock, no root, no titanium backup, no roms. Worked perfect. From reading some of the threads reporting problems, 90% sounds like a specific combination of the above 3 things is what is causing issues.
Charged the battery to 100% before i did it.
OTA (was connected to home wifi when i clicked on the updated notification). Don't know if it used the wifi connection or switched over to 3g to download the update ...
Clicked on update. It said it was going to reboot phone, and rebooted.
Then it started download/install. Took about 5 minutes to download and install. It sat at 50% for a little bit longer than the other %'s. Also sat at 85% for a minute or so. Then it booted up. "Vibrant" screen displayed for about a minute. Then the GalaxyS screen displayed for about a minute or 2, then phone booted like normal.
Everything seems okay.
Stock vibrant (non rooted) should be fine. Its what the update was made for.
anthonys2r said:
Stock vibrant (non rooted) should be fine. Its what the update was made for.
Click to expand...
Click to collapse
I read in the t-mobile forums that most of them are running stock phones, but they weren't able to update their phones.
what do you mean by 'weren't able'? a majority of the people still have not received the t-mobile notification (me included). is that what you meant?
no. sorry i guess i didn't put much details to what i have said. some of them already received the notification from t-mobile. but they weren't successful with the processing of the updates on their phone. and i read that they are running stock vibrants.
i tried to update via odin, but i can't go to download mode. seems that i just have to use a stock vibrant.
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
I wasn't so luckly. I undid my lag fix and un rooted and still soft bricked mine and had to use odin to get it back
how long
HumanTarget said:
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
Click to expand...
Click to collapse
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
jblade1000 said:
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
Click to expand...
Click to collapse
took about 3-6 minutes for me.
I got very worried... but was patient.
Stock ROM
Rooted
All bloatware removed.
wasted mine with no lag fix rooted on stock kernel, stock build..had to odin back and update via odin...****ty
well damn, im kinda at a loss then about whether to go through with this. I want the update but I dont have the time to be messing with flashing and odin right now...
Weirdddddddd
I to bricked my phone with the ota. I was rooted, stock rom, lagfix with clockwork. I undid the lagfix but still bricked. My boy's running the same without clockwork (never had time to put it on). Unrooted, delaged and removed the update.zip that was on the phone from root and cleared the cache. Ota worked without a problem. Some believe it is the result of an update.zip left on the sd which causes the problem.
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
http://forum.xda-developers.com/showthread.php?t=771590
Well you didn't actually brick it if the sprint and galaxy s things came on. Could've used odin to reset it to factory.
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
black screen of death. reflash stock .tar with odin. happened less than an hour after i bought mine.
LucJoe said:
http://forum.xda-developers.com/showthread.php?t=771590
Click to expand...
Click to collapse
Wow, that was helpful. Thanks.
If the vbulleting search feature didn't blow donkey balls so hard, then maybe I could find an answer. Instead all I find are generic results that happen to have the word root or brick in them, none of which applied to my scenario.
If this belongs in General, then my apologies. In the hero forum we didn't discuss rooting, or ROMs in General section. It was all in Development.
So should I just try again, or is there something I'm doing wrong? I mean how hard is it to screw up a one click root???
I'd actually be more comfortable doing it through ADB...
Try again. Make sure you use a good usb cable and you connect through the back of your computer. Restart phone and computer to be safe.
If you "brick" it again just use Odin to flash the stock tar.. you were never truly bricked!
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
Lol. Agree. I screamed and yelled at htc ppcs cuz they lack 3d gpu power.and cripple features on their hsndsets. Now im a samsung costumer for life. Even faster than iphone 4. Love it!
Sent from my SPH-D700 using Tapatalk
Try the drockstar all in one root v2.01, worked like a charm for me rerooting the other day. Had some issues with the one click the first time awhile ago.
You didn't really brick your phone. Hold 1 when you power up to enter download mode. Make sure you firewall and antivirus are disabled, odin wouldn't work with my Norton AV. Then you can always flash the stock D18 through Odin.
You should root asap. Like they said you can allways flash to stock if something happens instead of returning the phone. I remember I used to use my phone all day connected to a power supply. Now I don't have to do it with the syndicate rom and my phone is even faster.
Sent from my SPH-D700 using XDA App
You didnt brick your phone. I have had that screen hang for 6-7 minutes many of times after rooting or flashing. Because that is when your kernel and files get rebuilt at that splash screen so it is really slow and feels like forever but it will boot. If not battery pull and try to boot again or use odin.
poor_red_neck said:
Let me preface by saying I'm not a newb, just a newb to the Galaxy S line.
I've rooted other Samsung android phones, no problem.
The day after buying my Epic, I tried to root to use wifi tether and remove bloatware. Not interested in modding right now, as well.... this thing is blazing fast as is. Only complaint so far is of course battery life.
So, following this thread, It bricked my phone.
It successfully rooted, and I even had ADB access to SU, and my android terminal program could get SU.
I then restarted the phone after the "one click" root, and it hangs after the splash screen.
I could still get to the Recovery that was flashed, and tried a wipe of all data/cache etc. No go. The bottom 4 lights stay on, as well as the red LED. Nothing happens. I couldn't get ADB to connect. I never even had the chance to do a Nand backup. The FIRST reboot after booting, "bricked" it. The sprint 4G logo came on, then the Galaxy S splash screen, then hangs.
Took it back to BestBuy (purchased the black tie warranty as well) and the first question he asked is "Did you try and root it." I've bought 3 phones from this guy, and a crap ton of accessories for friends and family, so I was honest and said yeah, I tried. He said no worries, and gave me a new one, but I wasn't the only one to bring in a bricked phone like mine after trying to root.
SO what gives?
After purchasing the phone, there was 2 system updates. The first one downloaded and installed, and about an hour or two after that another one. Is this a patch?
The z4 root option from the market still works (the temporary option, not permanent) and with temp root I can still get WiFi tether to work, so it's not that big of a deal.
However I'm noticing some quirky things that I think a custom ROM may fix.
One: the GPS will randomly activate with no active programs on, not get a fix because I'm inside, and DRAIN the battery. I went from 80% to 17% in about an hour.
Two: The battery percentage/capacity/stats seem to be VERY unstable. I've had the phone at 60%, rebooted, then it shows like 15%. Reboot again and its back up to 50%. Very odd.
Other than that, MY GOD THIS PHONE REALLY IS EPIC. I mean, un freakin' believable. Everything I've EVER wanted from a phone.
Click to expand...
Click to collapse
Well 1st things 1st. Your phone WAS NOT BRICKED!!! All you had to do was use Odin to flash your phone back to stock! If you would have done your homework, you woulda known that! But you didnt! Cuz your too freakin LAZY to READ!!!! A EPIC CONNOT BE BRICKED UNLESS YOUR A IDIOT!!!!
@OP
Hey man, did you try this procedure?
http://forum.xda-developers.com/showthread.php?t=773032&highlight=revert+stock
Good luck and don't give up on it!
It is fully possible to Brick an Epic... a fair amount of idiocy is involved though.
Epic Experience 1.2.0.9/Phoenix 1.49s/Elegant Steel .21
Damn, I always rush into these topics thinking someone bricked their phone, but turns out most of the time it's just someone else misusing that word
sniperkill said:
Well 1st things 1st. Your phone WAS NOT BRICKED!!! All you had to do was use Odin to flash your phone back to stock! If you would have done your homework, you woulda known that! But you didnt! Cuz your too freakin LAZY to READ!!!! A EPIC CONNOT BE BRICKED UNLESS YOUR A IDIOT!!!!
Click to expand...
Click to collapse
Should I release the angry grand wizard kkk silverback gorilla on him? Lol.
Sent from my SPH-D700 using Tapatalk
Tomorrow is my 46th birthday, and I have tried to stay on top of technological advancements as best possible given my busy schedule. What I have noticed is that my ability to digest the latest techno trends and techniques does have a limit, especially when it interferes with the approaching martini hour at afternoon's end!
I don't know if this is a question or a mid-life existential moment. I bought the Samsung Epic 4G last fall because it was supposed to be cutting edge in terms of hardware for Android, and I as many of you have expressed, I made the decision to buy the Epic because of the promised firmware update that was imminent.
Fast forward half a year, and I now have the 2.2.1 EB13 firmware, which is rooted. I received the SMS yesterday (Wednesday) afternoon from Sprint about Sprint ID coming, but no update. Since I am rooted on EB13 I have no idea whether or not I will ever get the OTA and the last time I tried ODIN I had to take a tranquilizer, so I have no desire to go back to 2.1 to get the OTA.
Will the EC05 OTA be appearing given rooting on EB13? EB13 is giving me problems. I loved moving many (most) apps over to SD (I have a 32 gig card). But WiFi is not good, and I lose the ability to play movies, audio files, visual voicemail, or even hear my phone ringer (all seem connected in terms of the error -- I get an "unable to play message" or "unable to open file" error). I have to turn the phone off completely, then back on, wait for the media scan, etc. for it to go back to normal, then the errors will come back. I was hoping that EC05 would fix this. Maybe not. In perusing and searching I see nobody else has reported these problems which did not exist on DI18 (although I do see reports of WiFi connectivity problems that appear similar).
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
UPDATE: Life is grand at 46 (almost!). I posted later the following URL:
hxxp://forum.androidcentral.com/epic-4g-rooting-roms-hacks/71389-odin-ec05-froyo-ec05-prerooted-cwm-v2-5-1-0-rfs-odexed.html#post761525
When I got home I did as instructed using ODIN, and now I have EC05, with root, no data erasure, all is well! I still see so much consternation going on in the other threads. If you go to this URL and follow the directions, it works without any issues. I noticed immediately my WiFi issues are issues of the past. You can either wait for Sprint/Google to OTA you, under certain limited conditions, or do this, and be whole. Your choice. JJP
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Thank you, what a nice response. Hopefully an update.zip will appear for EB13. Stranger things have happened.
drplaud said:
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
Click to expand...
Click to collapse
Unfortunately, all the AMPS and Digital TDMA networks have long since been shut down, so it would do you no good
But I do have a bag phone haha
Sent from my SPH-D700 using XDA Premium App
I wish I was 18 again, but for other reasons.
Yeah it is hard to keep up with tech these days,it changes by the hour now. And Ill have to say that Android is fragmented,this makes it harder; Look at what 2 updates to 2.2.1 and a 2.2.1 leak has done to this Epic forum,it has become a mess,I just hope now that we have CM7 and probably the last update for atleast 6 months,we should start to see some serious progress.
Sent from my SPH-D700 using XDA Premium App
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
I do not think I will receive the OTA as I used one click to root after installing EB13. Perhaps this is the time to go Bonsai as I understand it now has EC 05 built in. I apologize, but is there a primer on how specifically to go to Bonsai? I have never flashed before (as I thought I might be arrested). Thanks.
Sent from my Samsung Epic™ 4G
You mentioned you're rooted. Do you know if you have CWM3 installed?
Its all a little trial and error but once everything is properly installed flashing roms is a cinch. I'm a big fan of the ACS roms. Bonsai worked well on my phone but there were a handful of idiosyncracies present that I could not put up with. Of course YMMV but don't hesitate to try different roms until you find one that your phone works well with.
stir fry a lot said:
You mentioned you're rooted. Do you know if you have CWM3 installed?
Click to expand...
Click to collapse
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
drplaud said:
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
Click to expand...
Click to collapse
Cool. If you want to give EC05 a shot, go to this thread and download the modem.
http://forum.xda-developers.com/show....php?t=1003447
Insert the modem into the Phone section of odin and hit start
Put aside some time before proceeding. If you have the correct CWM installed it won't take more than ten minutes but play it safe.
Download a rom of your choice, plug your phone into your computer and place it in the root of your SD card. You can download multiple roms if you want to see which works best for you. You will lose all your data the first time installing any new rom as it is not really recommended that you transfer settings of apps between different roms. Once you find a rom your're happy with you can simply update it it with the newest version without having to wipe your data however. Its really not as bad as it sounds and the ACS rom comes with an excellent app recovery program called MyBackup Pro Root that you can backup your apps and data with. You can use it to transfer apps between different roms and even some data but data from different roms can sometimes give you problems and is not really recommended. I have transferred data with some apps without any problems however. Its really just data that is tied to the system itself that will probably give you problems.
Unplug your phone from your computer and long press the Power Button, select Reboot, and then quickly hold down the Power, Volume Down and Camera Buttons.
Now press and hold down the Power, Camera, and volume down buttons. It should boot to the samsung logo and then to a black screen with orange text on it.
Use the volume keys to navigate and the power button to make selections. Choose Wipe Data/Factory Reset and wipe it 3x, then do the same for the Cache Partition and Dalvik Cache which can be found in the advanced options.
Select Go Back and navigate to Install Zip from SD card. Choose the rom you downloaded to it and you're good to go.
If after you do the three finger boot and you're not brought to a black screen with orange text you will need to install the correct CWM. If its black with green you have an old version and if you get a different screen than that this means that you do not have CWM at all. If this is so, just navigate to reboot and press the Home key to select it.
Something to think about
Thank you for the very helpful responses. I will ponder what the best option is, but it may indeed be time to explore custom ROMS, and your responses have given me the courage to do so. Many thanks! Joe
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
I would Odin to EC05 first and see if it fixes anything for you. If not, reboot your phone into CWM and if you have the correct (orange and black) version, just reboot load the ACS rom onto to your phone and give it a try. If you're not happy with it or even if you are make a backup with Mybackup Root and explore other roms until you find one that works for you.
If you make a backup I would advise making separate backups of your apks, data for your apks, and photos as it makes it much faster to get back to where you were originally. Another tip for my backup is after making one go to View and double check that it actually made one as sometimes it will not.
I would have thrown this phone away by now if it weren't for the ACS rom btw. Its much smoother, has better battery life, doesn't skip keys even without the patch that they will be implementing soon and doesn't have all the god awful bloatware.
musclehead84 said:
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
Click to expand...
Click to collapse
Where do I obtain one click root with cwm3? Thanks.
musclehead84 said:
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Click to expand...
Click to collapse
stir fry a lot said:
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
Click to expand...
Click to collapse
I agree with all of these except that odin never gave me trouble even the first time i used it..
Odin is cake just read the simple directions and everything should be fine, people dont use there heads when they get that android dude and the computer on there epic, the most ive been through is acore of force closes but its so easy to fix,
people just dont read the instructions all the way through,
Yesterday i was scared to update the prl manually but i read step by step instructions had to play around and find what i needed to do which wasnt on the instructions, and it was cake, almost just as easy as clicking the system updates/update prl button in the settings
but 98% of the time the instructions are flawless and work as long as you read carefully and do step by step.
drplaud said:
Where do I obtain one click root with cwm3? Thanks.
Click to expand...
Click to collapse
Development section stickied
Called One Click Clockwork 3.0.0.6
Oh yes happy birthday as well, have a great one!!
IMO, if you are on EB13, and want to update to EC05, the EASIEST way to do it, if you can wait a bit, is to use the stock SWUpdate for EB13, which will convert your phone back to a clean fresh stock install of EB13, then once/when it is released, install the EB13 to EC05 update via the over the air process, then reroot and move forward.
that all depends on samsung/sprint releasing a EB13 to EC05 OTA update, and your ability to wait for it though
I'm getting to pilot having a Galaxy S5 for work since they're finally going to allow a choice of iphone or android instead of just bes5 blackberry devices.
Now I love me some rooted droid, like my Nexus7 and old classic galaxy s 4g.
What exactly is Knox? I read a little that its a bit that you can flag.
Also anyone familiar with Airwatch? When I used to test it i had my rooted devices as compromised.
I may be getting elevated rights to even white list myself but in the meantime since its a company phone, I need to keep it someone stock, so I was hoping for a simpler debloated stock with maybe a toggleable root if no work around for Airwatch is available.
Thelgow said:
I'm getting to pilot having a Galaxy S5 for work since they're finally going to allow a choice of iphone or android instead of just bes5 blackberry devices.
Now I love me some rooted droid, like my Nexus7 and old classic galaxy s 4g.
What exactly is Knox? I read a little that its a bit that you can flag.
Also anyone familiar with Airwatch? When I used to test it i had my rooted devices as compromised.
I may be getting elevated rights to even white list myself but in the meantime since its a company phone, I need to keep it someone stock, so I was hoping for a simpler debloated stock with maybe a toggleable root if no work around for Airwatch is available.
Click to expand...
Click to collapse
Knox is a flag system for Warranty void to my understanding.
Don't know about Airwatch, sorry.
Towelroot will root you in about 5 seconds SO LONG AS YOUR KERNEL DATE IS PRE-June 3rd. SuperSU can Un-root you too if needed. But you can also root, uninstall Towelroot.apk, and debloat the phone with the lists in other threads.
Good luckl
kprice8 said:
Knox is a flag system for Warranty void to my understanding.
Don't know about Airwatch, sorry.
Towelroot will root you in about 5 seconds SO LONG AS YOUR KERNEL DATE IS PRE-June 3rd. SuperSU can Un-root you too if needed. But you can also root, uninstall Towelroot.apk, and debloat the phone with the lists in other threads.
Good luckl
Click to expand...
Click to collapse
No problem. VZ phone should be brand new, delivered today. But then again, when I bought my wife and my Galaxy S 4g's, side by side from the stash, we had totally different setups. one had froyo, other eclair if I recall. even packaging was different. The sticker on my screen had no text, so I left it on. Hers had crap all over.
So hopefully it's got older kernel.
If it is newer, is it that I cannot root at all, or a more complicated method?
For reference air watch is an MDM solution so people can enroll with their personal device, so they can get the corporate email. Also adds an option to remotely wipe the corporate email accounts. Once it detects root it used to kill the email app and stop the emails.
Normally I love to play around with stuff but I don't want to be in limbo without email in between.
I think i should be able to hold off on activating the cell number and just play with it in Wifi mode for the time being, and rock the bold 9930 a few more days.
Thelgow said:
No problem. VZ phone should be brand new, delivered today. But then again, when I bought my wife and my Galaxy S 4g's, side by side from the stash, we had totally different setups. one had froyo, other eclair if I recall. even packaging was different. The sticker on my screen had no text, so I left it on. Hers had crap all over.
So hopefully it's got older kernel.
If it is newer, is it that I cannot root at all, or a more complicated method?
For reference air watch is an MDM solution so people can enroll with their personal device, so they can get the corporate email. Also adds an option to remotely wipe the corporate email accounts. Once it detects root it used to kill the email app and stop the emails.
Normally I love to play around with stuff but I don't want to be in limbo without email in between.
I think i should be able to hold off on activating the cell number and just play with it in Wifi mode for the time being, and rock the bold 9930 a few more days.
Click to expand...
Click to collapse
If it has the newer kernel, you may be able to flash back to NCG root, then modify what is needed, then update to NE9 again, and re-root after.
Nice, the box has SW Ver ending NCG, confirmed Kernel was on May xx.
I had it up but Airwatch kept failing.
I tried Rootcloak. Then saw that needed Cydia substrate.. then saw that needed SELinux changer... Then that needed Knox disabled...
That needs SuperSU.
Air watch still failed.
Removed all of that and installed fine. So I'll play with this some more later.
I guess I can just root up, kill bloatware, and then unroot again.
Well I went to reroot to play with it more, unrooted and still detected as Compromised.
It seems if it sees I have towelroot installed, not even if rooted, its compromised.
At least I narrowed that down. Ill retry rootcloak later and ensure I have towelroot uninstalled.