Related
Coming from an Evo 4G that I had rooted right after I got it... ran a ton of different ROMs and that phone seemed like it needed to be rooted to really make it run right... I'm finding that I really don't see any benefit to rooting this phone (other than free tether)...
So, am I missing something? What are these improvements in these custom ROMs that are making it worth it to root... this thing is so freakin awesome already I just can't think of anything else I need...
There are tons of perks in the custom ROMs: themes, TSM-mod, cm7, MIUI, faster lighter ROMs, debloated, Rouge recovery to name a few. If you flashed roms on the EVO im sure its just a matter of time until you dive into the ET4g dev section.
ignore this
phatmanxxl said:
There are tons of perks in the custom ROMs: themes, TSM-mod, cm7, MIUI, faster lighter ROMs, debloated, Rouge recovery to name a few. If you flashed roms on the EVO im sure its just a matter of time until you dive into the ET4g dev section.
Click to expand...
Click to collapse
What's "TSM-mod" and "Rogue recovery".. Or more precisely, what are the advantages of them?
I've looked around at the Dev section but the phone's been out long enough that it's hard to find threads that actually explain what all this is.. it's just assumed that I already know...
I know, I know.. use the search fxn... you dont have to flame me... I'll find out on my own
blakjak220 said:
Yeah, I'm not saying I can deny the "flash bug" for long... but I'm so impressed with the phone as is that I'm content for now I guess...
Click to expand...
Click to collapse
If your impressed now, just wait till you start flashin'.
Sent from my SPH-D710 using XDA Premium App
Reason to flash=MIUI.
Calkulin's rom is great for a boost of performance on a stock rom as well...
Honestly, if you're happy with the phone as is, then maybe you should just leave it as it is until something comes along that makes you change your mind. Having a stock/unrooted phone is not a sin
blakjak220 said:
What's "TSM-mod" and "Rogue recovery".. Or more precisely, what are the advantages of them?
I've looked around at the Dev section but the phone's been out long enough that it's hard to find threads that actually explain what all this is.. it's just assumed that I already know...
I know, I know.. use the search fxn... you dont have to flame me... I'll find out on my own
Click to expand...
Click to collapse
Tsm is like Cyanogen settings from the cm7 roms, but compatible with Samsung ROMs, Rogue recovery is clockwork recovery but redone, the options are grouped better, better theme, a lot less pain in the ass to use.
Oh yea check out qbking77's videos, he does a lot of how to's and reviews of ET4g ROMs, great stuff.
cds0699 said:
Honestly, if you're happy with the phone as is, then maybe you should just leave it as it is until something comes along that makes you change your mind. Having a stock/unrooted phone is not a sin
Click to expand...
Click to collapse
I completely agree. That's what I do with my phones. It also gives you time to get really comfortable with the new device as I know quite a few things change going from an htc phone to a samsung device. I generally will use the phone as is out of the box until I find something I can't bear, don't like or if there is actually a defect of some sort in the software. At which point, I check xda and see if there are fixes for said problems. If there are fixes and you're comfortable, root it and give it a shot. I'd suggest Calkulin's as it kinda seems like the go to rom for just about everyone on here, then maybe venture into the abyss. I'd suggest staying away from modems and other mods until you understand them and are comfortable.
I agree as well, nothing wrong rocking a completely stock phone. There are times I run a stock (debloated) rom just for a change.
I'm running a rooted with no fancy rom phone here. The only reason I haven't flashed a rom yet is because my first phone had GPS problems and this one doesn't. And plus, my evo with 3.0 rom has its own issues too. So I just don't want to jinx it. My wife's phone has the GPS problem. Thinking about bringing it in to the store for a replacement.
Sent from my SPH-D710 using XDA App
Root? Root... ROOT!!!!!!
phatmanxxl said:
Tsm is like Cyanogen settings from the cm7 roms, but compatible with Samsung ROMs, Rogue recovery is clockwork recovery but redone, the options are grouped better, better theme, a lot less pain in the ass to use.
Oh yea check out qbking77's videos, he does a lot of how to's and reviews of ET4g ROMs, great stuff.
Click to expand...
Click to collapse
Thanks man, for the info and the referral. I'm comfortable enough with rooting and tech that it's just a matter of learning the different names for things, as it all goes by something different over here.
And thanks to everyone else for their input... I think I'm just gonna run it stock until I find something I can't live with.. Because right now, I love this thing.
Ok, scratch that.. I rooted yesterday.. just couldn't help myself, I need to be able to tweak the notifications toggles...
Like a drug, its good stuff you probably don't like nascar anyways either or kies or the allinone messenger battery sucker or the.... well ya dig..?
Sent from my SPH-D710 using XDA App
Mynaga said:
Like a drug, its good stuff you probably don't like nascar anyways either or kies or the allinone messenger battery sucker or the.... well ya dig..?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Dig.........
blakjak220 said:
Coming from an Evo 4G that I had rooted right after I got it... ran a ton of different ROMs and that phone seemed like it needed to be rooted to really make it run right... I'm finding that I really don't see any benefit to rooting this phone (other than free tether)...
So, am I missing something? What are these improvements in these custom ROMs that are making it worth it to root... this thing is so freakin awesome already I just can't think of anything else I need...
Click to expand...
Click to collapse
To be perfectly honest with you the way to go is stock rooted. None of the TW roms are really offering anything so much more exciting than stock TW. But definitely root it. On the practical side you can use the Wireless Tether app (if needed) block ads (a big thing for me) and access all files through Root Explorer. IMO those are reasons enough to root. In a nutshell, if you root your stock ROM you aren't really altering it and it is super easy to revert to non-rooted so there really is no downside as far as i can tell.
I debated the same thing... to root or not to root? I rooted and i am glad i did!
I held off for a while too but miui and the xplode roms are awesome. Just something different.
Sent from my SPH-D710 using Tapatalk
Well I rooted and flashed Calk's ROM... within 5 minutes it was having freezes and what not so I said screw it and restored my nandroid of stock... I'll be stayin here for a while.
Edit: not saying anything bad about Calk's work... It prolly would've been resolved with a wipe and clean install and some tweaking but I'm just wanting fast stability right now and stock TW is super fast and my battery life is awesome
Talk about a let down, we were so close to having this thing on our E4GT but it seems to have never been fixed. Now there is TWRP 2.1 and still no dice. I've never been a fan of CWM and I'm getting jealous of all the cool touch recoveries my brother has on his evo 3d. Don't get me started on CWM Touch, lol.
Maybe if we got together and shown that we still want this it could happen? The whole idea of the recovery rewriting itself after every flash was pretty cool.
I had read on one of the developers twitter that twrp had broken up. I also heard they were going to release the code for it for others to use but don't quote me on that.also that developer said he was working on a completely new kind of recovery
Sent from my SPH-D710 using xda premium
Agrabren was the member of Team Win that Rootzwiki gave the E4GT to from our phone winning the poll. Then a month or so later Agrabren and Team Win parted ways, before TWRP was functional on our phone. Since then, Agrabren has been working on his own recovery project called Phoenix. So, who knows if our phone will ever see TWRP support, and who knows what if anything Agrabren ever did with his E4GT.
Links with some details:
http://phx-recovery.blogspot.com/2012/01/twrp-final-chapter.html
http://www.teamw.in/blog/15
Dchibro said:
Agrabren was the member of Team Win that Rootzwiki gave the E4GT to from our phone winning the poll. Then a month or so later Agrabren and Team Win parted ways, before TWRP was functional on our phone. Since then, Agrabren has been working on his own recovery project called Phoenix. So, who knows if our phone will ever see TWRP support, and who knows what if anything Agrabren ever did with his E4GT.
Links with some details:
http://phx-recovery.blogspot.com/2012/01/twrp-final-chapter.html
http://www.teamw.in/blog/15
Click to expand...
Click to collapse
Cool, thanks for the info!
Dchibro said:
Agrabren was the member of Team Win that Rootzwiki gave the E4GT to from our phone winning the poll. Then a month or so later Agrabren and Team Win parted ways, before TWRP was functional on our phone. Since then, Agrabren has been working on his own recovery project called Phoenix. So, who knows if our phone will ever see TWRP support, and who knows what if anything Agrabren ever did with his E4GT.
Links with some details:
http://phx-recovery.blogspot.com/2012/01/twrp-final-chapter.html
http://www.teamw.in/blog/15
Click to expand...
Click to collapse
Thanks for the info. I asked about this in a thread yesterday but nobody answered.
Sent from my Nexus S 4G using XDA
Wish we could just get CWM Touch to work so then Rogue could do his thing with it.
latinmaxima said:
Wish we could just get CWM Touch to work so then Rogue could do his thing with it.
Click to expand...
Click to collapse
I actually put the new TWRP 2.1 on my Nexus and had a problem flashing within the first 24 hours so I went back to the touch recovery which has been flawless on that phone. I would like to see the issues ironed out myself
TWRP 2.0 hard-bricked my original Evo 4G, as it did many other Evos. It will be a cold day in hell if I ever install anything from Team Win on my phones.
However, this whole idea of touch recoveries really baffles me. I am obviously not new to the touch recovery idea, and I agree that it's nicer, but the question is; what is the big deal? If you are a "flashaholic" (I hate that term), you may go into recovery a few times a week, and all you're doing is clearing caches and flashing a new ROM, mod, etc. So does the extra 60 seconds that it takes to fiddle with the volume and power buttons make that big of a difference? I am perfectly happy with a regular recovery that is known to work without problems. So what is this whole deal about "being jealous of all of the cool touch recoveries." I mean honestly, of all of the things to be jealous about, you guys occupy your minds with a touch recovery.
sputnik767 said:
TWRP 2.0 hard-bricked my original Evo 4G, as it did many other Evos. It will be a cold day in hell if I ever install anything from Team Win on my phones.
However, this whole idea of touch recoveries really baffles me. I am obviously not new to the touch recovery idea, and I agree that it's nicer, but the question is; what is the big deal? If you are a "flashaholic" (I hate that term), you may go into recovery a few times a week, and all you're doing is clearing caches and flashing a new ROM, mod, etc. So does the extra 60 seconds that it takes to fiddle with the volume and power buttons make that big of a difference? I am perfectly happy with a regular recovery that is known to work without problems. So what is this whole deal about "being jealous of all of the cool touch recoveries." I mean honestly, of all of the things to be jealous about, you guys occupy your minds with a touch recovery.
Click to expand...
Click to collapse
I only like it to save the wear and tear on my volume rocker but I don't flash ROMs on my Epic Touch near as much as on my Nexus so that really doesn't come into play. I actually went back to good old regular CWM5 when I flashed 4.0.4 on my NS4G and its just as good. When I tried to flash a ROM with TWRP 2.1 this morning it hung at the splash screen. I used Flash Image GUI to put touch recovery on since I had the img and the same ROM zip flashed with no problems
Sent from my Nexus S 4G using XDA
sputnik767 said:
TWRP 2.0 hard-bricked my original Evo 4G, as it did many other Evos. It will be a cold day in hell if I ever install anything from Team Win on my phones.
However, this whole idea of touch recoveries really baffles me. I am obviously not new to the touch recovery idea, and I agree that it's nicer, but the question is; what is the big deal? If you are a "flashaholic" (I hate that term), you may go into recovery a few times a week, and all you're doing is clearing caches and flashing a new ROM, mod, etc. So does the extra 60 seconds that it takes to fiddle with the volume and power buttons make that big of a difference? I am perfectly happy with a regular recovery that is known to work without problems. So what is this whole deal about "being jealous of all of the cool touch recoveries." I mean honestly, of all of the things to be jealous about, you guys occupy your minds with a touch recovery.
Click to expand...
Click to collapse
Im jealous because the geek in me says "wow, thats cool". But really the redeeming quality of TWRP2 to me was that you wouldn't have to worry about bundling the recovery with the kernel anymore. That is an annoyance with this phone that I flat out do not like.
Gordon Ramsay said:
Im jealous because the geek in me says "wow, thats cool". But really the redeeming quality of TWRP2 to me was that you wouldn't have to worry about bundling the recovery with the kernel anymore. That is an annoyance with this phone that I flat out do not like.
Click to expand...
Click to collapse
That's an interesting point, and it was something that I didn't expect when I first came to the E4GT from the Evo. However, if the phone is designed to have the kernel bundled with the recovery, perhaps it's best not to mess with it. I do agree that it's annoying to have to have the bundle, but if it's true what you said about TWRP not being bundled with a kernel, this makes me even more weary of trying it out.
sputnik767 said:
That's an interesting point, and it was something that I didn't expect when I first came to the E4GT from the Evo. However, if the phone is designed to have the kernel bundled with the recovery, perhaps it's best not to mess with it. I do agree that it's annoying to have to have the bundle, but if it's true what you said about TWRP not being bundled with a kernel, this makes me even more weary of trying it out.
Click to expand...
Click to collapse
I am curious about this now too! I know that CWM backups don't show in TWRP. It has its own folder but I don't know if the kernel/recovery being bundled is phone specific or if TWRP is truly separate
Sent from my Nexus S 4G using XDA
JohnCorleone said:
I am curious about this now too! I know that CWM backups don't show in TWRP. It has its own folder but I don't know if the kernel/recovery being bundled is phone specific or if TWRP is truly separate
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
Supposedly the way it worked was no matter what kernel or recovery you flashed, TWRP rewrote itself after every flash, thus giving you TWRP all the time. I think thats how I understood it.
Gordon Ramsay said:
Supposedly the way it worked was no matter what kernel or recovery you flashed, TWRP rewrote itself after every flash, thus giving you TWRP all the time. I think thats how I understood it.
Click to expand...
Click to collapse
Ok, that makes sense. But if that's what happens, then it's really no different than you flashing a new kernel/recovery package after each new ROM flash, it's just that this step is done for you automatically. I've been doing to ODIN leaks for a long time now so I don't remember how typical 3rd party ROMs are packaged, but does each ROM come with it's own kernel/recovery, or is it standalone? I know that with the Evo, you would flash a ROM and the kernel if you wanted to, but the recovery was untouched. Here, I think I typically flashed a ROM, and then kernel/recovery package right after, so the process is really no different from the Evo. I just kept the Rogue package on my SD card. And a second point, let's say that what you are saying is true, that TWRP rewrites itself after every flash, then how do you get rid of it if you want something else? I personally don't really like the idea of turning control of my device to some automated code.
sputnik767 said:
Ok, that makes sense. But if that's what happens, then it's really no different than you flashing a new kernel/recovery package after each new ROM flash, it's just that this step is done for you automatically. I've been doing to ODIN leaks for a long time now so I don't remember how typical 3rd party ROMs are packaged, but does each ROM come with it's own kernel/recovery, or is it standalone? I know that with the Evo, you would flash a ROM and the kernel if you wanted to, but the recovery was untouched. Here, I think I typically flashed a ROM, and then kernel/recovery package right after, so the process is really no different from the Evo. I just kept the Rogue package on my SD card. And a second point, let's say that what you are saying is true, that TWRP rewrites itself after every flash, then how do you get rid of it if you want something else? I personally don't really like the idea of turning control of my device to some automated code.
Click to expand...
Click to collapse
Yea I was wondering that myself, the bit about how to get rid of it. I would assume there would be an option to not rewrite somewhere in the interface. I guess we will never know lol.
I love twrp on my evo 3d its awesome. I would love to see it on this phone or perhaps phoenix
Sent from my BAD A$$ EPIC TOUCH 4G
Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks
When you rooted did you NANDROID backup ? If not go into recovery and clear cache and then go into advanced and wipe delvik cache. reboot
If that fails go back into recovery and do a factory reset and you should be ok.
touchdownadrian said:
Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1727401
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
I disagree as long as you are willing to learn from the mistake all is good. I had a Samsung Exhibit II and deleted touch wiz launched (I was using go launcher) later I would do a factory reset and well... learned that system files do not get restored when you do a factory reset...oops
Sent from my SGH-T999 using xda premium
I agree, we all were NOOBS at some point. That's the one thing I love about XDA is that with patience and the help of the users any noob can learn how to mod their devices. One piece of advice that I can offer is before you do any type of modding is READ and keep on READING. I have bricked the first device I ever rooted because I did not READ the forums as they are meant to be read.
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium
Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium
not fair
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
touchdownadrian said:
Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.
TheSeanTeam said:
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.
Click to expand...
Click to collapse
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.
lordazoroth said:
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.
Click to expand...
Click to collapse
Same here. It took me months of researching on my vibrant before flashing my first rom (bionix 1.6 by teamwhiskey). As I progressed, I did brick left and right but I always managed to bring it back to life with my prior knowledge. Now I'm eagerly waiting for my computer to be done downloading the root files and get started.
Sent from my SGH-T999 using xda app-developers app
Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999
Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
+++++++1 on that.... DAMN talk about headaches....
dmarco said:
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
:good::good:
Yeah one of the only other IMPORTANT thinks i could add would be always do a factory reset before flashing roms.. some people like to flash "dirty" i wouldnt recommend it cause you will ALWAYS have issues maybe not in a hour but guaranteed you will... but knowledge is power dude.. i two read for about 36 hours before rooting my phone.. i rooted my wifes phone days after a rooted mine back in the day it only took like 15 mins.. another thing let phone sit 10 mins before ya play with it... gotta let the cache settle... the ten min wait is well worth it.. ive been doing it that way since the vibrant bro.. happy flashing and welcome..
I read constantly things change hourly like when that new leaked kernels came out for sgs2 and the emmc was trashed never to come back from a brick again. To anyone that cares if you love your phone read more than just the root and flash stuff learn what makes your phone tick from the factory hardware software and added crap from your carrier it all play's a part in the end result. Its as easy as you make it.
Sent from my SGH-T999 using Tapatalk 2
Nabeel10 said:
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999
Click to expand...
Click to collapse
Ive passed down two vibrants (both rooted) to my sons so they can learn to flash roms and everything else that comes from the joys of root.
Sent from my SGH-T999 using xda app-developers app
I found this ROM:
http://www.gearengine.it/?page_id=2
...and would LOVE to run it on my AT&T GSIII but it says they're running it on the international version. I was planning on giving it a shot anyway but, while I'm working on rooting, I'd ask a few questions.
Think it'd work on the AT&T version?
If not, is there an equivalent ROM that will?
I want to keep ALL the stock functionality...camera wise, hardware wise (NFC, Bluetooth, etc) yet still getting the customization that that ROM afforded (I loved the Aroma installer, the inverted apps, etc) while running an overclock/undervolt kernel so I can juice this thing!
What are you guys running?!
One word of advice would be not to flash an international ROM on your AT&T device. I think that would lead to a brick.
Do some reading in the development sections to familiarize yourself with the basics.
Sent from my SGH-I747 using xda app-developers app
CamFlawless said:
One word of advice would be not to flash an international ROM on your AT&T device. I think that would lead to a brick.
Do some reading in the development sections to familiarize yourself with the basics.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have to agree. I actually just commented in a thread before coming across this one: http://forum.xda-developers.com/showthread.php?t=2056655
Foxhound was flashed to their device, and their device was hard bricked. Please do not flash i9300 ROMs to US device variants.
I am currently running cm10.0.0 stable. It runs like a dream, not one issue with it so far. I would not recommend the new cm10.1 nightly builds until the data problem is fixed however.
LOL!!!
Well...this website was down for a few and I though ah hell, why not.
smh
Never actually heard of anyone hard bricking a phone. Awesome. This rounds out my Android experience nicely. Just as dude says, it doesn't do a damn thing. No power, not light, no vibration, nothing.
I can't believe there's no way to fix something like this. I'm all around amazed...I must say.
But yea...so...AT&T I go in the morning to test my acting skills I guess. *shrug*
And the Aroma installer was SO COOL!!!! What a shame...
Had I known the consequences could be so dire...
rmp5s said:
LOL!!!
Well...this website was down for a few and I though ah hell, why not.
smh
Never actually heard of anyone hard bricking a phone. Awesome. This rounds out my Android experience nicely. Just as dude says, it doesn't do a damn thing. No power, not light, no vibration, nothing.
I can't believe there's no way to fix something like this. I'm all around amazed...I must say.
But yea...so...AT&T I go in the morning to test my acting skills I guess. *shrug*
And the Aroma installer was SO COOL!!!! What a shame...
Had I known the consequences could be so dire...
Click to expand...
Click to collapse
Very sorry to hear your luck =( Good luck at AT&T... Don't let this deter you from future ROM flashes, just make sure you are flashing the correct GS3 variant. If you are on AT&T your device is model# i747 and the codename is d2att when flashing ROMs.
I didn't need too many acting skills, I just told them I woke up in the morning and my phone would no longer turn on. They swapped it out pretty quickly =) My hard brick came from a CWM flash when I was inexperienced at flashing. (I came from an iPhone... bleh). I had used a terminal emulator and used some commands to install CWM. Big mistake. I then followed Cyanogenmod's WIKI on installing CWM and it worked like a charm. =)
Of course, in my opinion, nothing beats TWRP recovery installation... Step 1: Download Goo Manager from the PlayStore. Step 2: Click menu and "Install OpenRecovery Script" Step 3: Wait for your phone to reboot into recovery =)
Well now that I'm done with my tangent, I think I'm heading to bed for the night lol. Good luck at the AT&T store tomorrow! ...and have a Happy Holiday! =)
RPelham said:
Very sorry to hear you luck =( Good luck at AT&T... Don't let this deter you from future ROM flashes, just make sure you are flashing the correct GS3 variant. If you are on AT&T your device is model# i747 and the codename is d2att when flashing ROMs.
I didn't need too many acting skills, I just told them I woke up in the morning and my phone would no longer turn on. They swapped it out pretty quickly =)
Again, good luck, and have a Happy Holiday!
Click to expand...
Click to collapse
Hey...it's all good man. I've been in the Android game since the G1 and STILL I'm getting firsts. LOL!!! I will ALWAYS hack, tinker and tweak. That's the fun of it...this included.
I KNEW it was the wrong version. However...what I DIDN'T know was the likely outcome! Had no idea. Only ever heard of hard bricks as a mythical monster-like sorta thing. Through my G1 days, GS days, HTC Doubleshot, HTC One S and AAAAAAAAAAALL the devices I've rooted and ROM'd in between (my tablets and who knows how many friend's devices), I've never seen or had a true hard brick happen. Had a close call sorta with the ex-wife's GS, but I fixed it.
Honestly didn't think this was something that could ACTUALLY happen!!!
We'll see what happens.
Thanks everyone!!
rmp5s said:
Hey...it's all good man. I've been in the Android game since the G1 and STILL I'm getting firsts. LOL!!! I will ALWAYS hack, tinker and tweak. That's the fun of it...this included.
I KNEW it was the wrong version. However...what I DIDN'T know was the likely outcome! Had no idea. Only ever heard of hard bricks as a mythical monster-like sorta thing. Through my G1 days, GS days, HTC Doubleshot, HTC One S and AAAAAAAAAAALL the devices I've rooted and ROM'd in between (my tablets and who knows how many friend's devices), I've never seen or had a true hard brick happen. Had a close call sorta with the ex-wife's GS, but I fixed it.
Honestly didn't think this was something that could ACTUALLY happen!!!
We'll see what happens.
Thanks everyone!!
Click to expand...
Click to collapse
I have been with Android through the GS1, GS2, and now GS3. I totally agree with you. I have done some really stupid stuff, but have always been able to fix the problem, mostly from help from this forum.
It may be just me, but it seems that it is a lot easier to brick the GS3 than its predecessors. Not from personal experience (knock on wood), but from reading through these forums.
Let us know what happens at the AT&T store. As an aside, does anyone ever know what happens in the long run when you turn in a hard brick to AT&T and get it replaced? I would imagine that once they JTAG it they would see that it was flashed. Could they charge you for the device?
cjranucci said:
I have been with Android through the GS1, GS2, and now GS3. I totally agree with you. I have done some really stupid stuff, but have always been able to fix the problem, mostly from help from this forum.
It may be just me, but it seems that it is a lot easier to brick the GS3 than its predecessors. Not from personal experience (knock on wood), but from reading through these forums.
Let us know what happens at the AT&T store. As an aside, does anyone ever know what happens in the long run when you turn in a hard brick to AT&T and get it replaced? I would imagine that once they JTAG it they would see that it was flashed. Could they charge you for the device?
Click to expand...
Click to collapse
That is a fantastic question. I was concerned about that myself the first time it happened. From my experience I was never charged when I went into the store to do the exchange. No bills came later in regards to it either. I think its pretty safe, but I wouldn't make any guarantees.
I also agree with you in that the GS3 seems a lot easier to brick than other phones I've dealt with.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Well...they gave me another one. Couldn't get another red one like I wanted since they didn't have any in stock which kinda sucks so I got the blurple one. Looks cool.
Obviously, I can't agree with the comments on the GSIII's resistance to bricking since I had something happen with this device that I've never seen or even HEARD of anyone doing. lol But it's all good. Time to start tinkering again.
Think I'm going to go the CM10 route since that is apparently a good ROM. However...does everything work with it? NFC and all? And...is there an OC/UV kernel that is compatible with that ROM?
As far as what they do with it after, I don't really know. I had to take it back to Best Buy since that's where I got it and it was so soon after getting it. I only had the thing...for...like...4 hrs when it got killed. lol I would imagine that they have the resources to easily fix a device that has had this happen. If they didn't replace it, I was just going to make a JIG for it (http://www.androidnova.org/unbrick-your-hard-bricked-smartphone/).
Thanks for all the help, guys!!!
Well...I didn't kill it. lol
So...first setup I tried:
ROM - http://forum.xda-developers.com/showthread.php?t=1766684
Kernel - http://forum.xda-developers.com/showthread.php?t=1756776
My ratings, out of 10?
Look and feel: 7...I only give it so low since it's EXACTLY the same as the HTC One S ROM I was running. This is usually a good thing but I was wanting something different.
Functionality: 4...every time I send a text, the damn thing says it didn't send! But it does! Very strange, very annoying, very unusable.
Customizability: 12...it's an AOKP ROM...with the Nova launcher...there are a mind bending number of options. I love it!
Quadrant score: 3...What the hell is an overclocked, current gen phone juiced to over 2.1GHZ doing getting ~3600 pts in quadrant? EXTREMELY disappointing.
Final words: Running Android 4.2...awesome. I love being cutting edge, but there isn't anything really awe-inspiring about it aside from the Jelly Bean 4.2 but the text messaging problem is just insurmountable.
Next is going to be this one:
http://forum.xda-developers.com/showthread.php?t=1949025
Going to keep the kernel and we'll see what happens! I'll let you know!
Glad it worked out. =) Just a heads up 4.2 has a lot of common bugs with it being so new. That texting problem is among many. Bluetooth issues, USB MTP issues, internal/external storage swapped, mobile data and WiFi issues to name a few.. I'd recommend sticking to 4.1 unless you don't mind the above annoyances. =p They will get ironed out soon enough I'm sure. =)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
That ROM flat out didn't work...it booted and everything but the keyboard kept giving me an FC. No bueno.
Back to the other I go!
Can anyone recommend a ROM that is as customizable as the AWESOME AOKP ROMs but still retain a bit of the Samsung-ness? Like...I like having the burst shot in the camera, the cool gesture and motion stuff they have, etc. Is there a middle ground?
rmp5s said:
That ROM flat out didn't work...it booted and everything but the keyboard kept giving me an FC. No bueno.
Back to the other I go!
Can anyone recommend a ROM that is as customizable as the AWESOME AOKP ROMs but still retain a bit of the Samsung-ness? Like...I like having the burst shot in the camera, the cool gesture and motion stuff they have, etc. Is there a middle ground?
Click to expand...
Click to collapse
Checkout NexusMOD in the development forum. Its a touchwiz ROM with AOSP messaging and email. You can still run Nova Launcher if you want, and holo locker if you don't want the TW lock screen.
I'm still tinkering and trying different ROMs. Downloading LiquidSmooth right now, can't find the NexusMOD one mentioned and I just tryed to flash an AOKP ROM and it wouldn't flash.
I SO BADLY want the 4.2 to work. I LOVE it!!! The Camera (wish it had HDR and multi shot modes, though), the stock messenger, LOCK SCREEN WIDGETS...it's just awesome.
I'm with you all the way rmp5s(except the bricking part), I want this ROM sooo bad. It's stockish which I like, yet has a lot of mods, any word yet on it coming to I747?
I just rooted and installed the JellyBomb rom for the GS3 for a friend. They didn't like the rom, so I remembered that there was a GS3 version of Android Revolution HD. I flashed the phone and hit reboot in TWRP and now nothing. I realized just now that the roms are different for the carriers but I possibly installed a rom for a different carrier. Nonetheless, the phone still isn't doing anything. It won't power on. I get no screen. Nothing. Is it completely bricked? How can I at least get back to Download mode for Odin?
MrAutomatic said:
I just rooted and installed the JellyBomb rom for the GS3 for a friend. They didn't like the rom, so I remembered that there was a GS3 version of Android Revolution HD. I flashed the phone and hit reboot in TWRP and now nothing. I realized just now that the roms are different for the carriers but I possibly installed a rom for a different carrier. Nonetheless, the phone still isn't doing anything. It won't power on. I get no screen. Nothing. Is it completely bricked? How can I at least get back to Download mode for Odin?
Click to expand...
Click to collapse
Good friend. You bricked his phone. Way to not read.
The Root said:
Good friend. You bricked his phone. Way to not read.
Click to expand...
Click to collapse
That's all you have to say? Can I unbrick the phone?
MrAutomatic said:
That's all you have to say? Can I unbrick the phone?
Click to expand...
Click to collapse
Nope, probably should have done some more research before breaking someone else's phone for them. Hope you got a good job cuz I'd make you buy a brand new one
I like to break stuff!
-EViL-KoNCEPTz- said:
Nope, probably should have done some more research before breaking someone else's phone for them. Hope you got a good job cuz I'd make you buy a brand new one
I like to break stuff!
Click to expand...
Click to collapse
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
It's bricked if it was an international version Rom. There's usually nothing you can do. Hopefully your friend can take it back to store say it was doing update and it never came back on. I hope he's a good friend. You can't get back into download mode at all because the partitions are different and your download and recovery are no longer in existence.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
It's bricked if it was an international version Rom. There's usually nothing you can do. Hopefully your friend can take it back to store say it was doing update and it never came back on. I hope he's a good friend. You can't get back into download mode at all because the partitions are different and your download and recovery are no longer in existence.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thank you for giving me a real explanation and not just running your mouth. She works for the carrier so she won't have an issue getting the phone replaced. I just hate inconveniencing them. It's just ridiculous that everything went smooth up until that point. What I don't understand is why the phone won't even power back on, at all, but oh well. She says they can have another to her within a day.
MrAutomatic said:
Thank you for giving me a real explanation and not just running your mouth. She works for the carrier so she won't have an issue getting the phone replaced. I just hate inconveniencing them. It's just ridiculous that everything went smooth up until that point. What I don't understand is why the phone won't even power back on, at all, but oh well. She says they can have another to her within a day.
Click to expand...
Click to collapse
here ill explain on the International S3 their Kernel partition is stored where on the US variant our bootloader is stored. So when you flash a international rom it wipes your bootloader because thats where the kernel goes on the international
This same thread will come up in about five hours. I will insult that person too. Learn what you're doing. I'm tired of these threads and they won't ban people who do this. I don't think you should be doing custom stuff to phones if you know this little. Is that more clear?
evo4gnoob said:
here ill explain on the International S3 their Kernel partition is stored where on the US variant our bootloader is stored. So when you flash a international rom it wipes your bootloader because thats where the kernel goes on the international
Click to expand...
Click to collapse
This will prevent it from even powering on or getting into Download mode? Sheesh.
MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
I get that those replies probably werent the most soothing, but all of this could have been avoided and replying like that does not help you resolve you problem.
Now I dont know who you are or how much you looked into it, but next time make sure you stick to the development sections of the phone you're trying to flash
Sent from my PG06100
MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
No problemo! Happy to help
I like to break stuff!
MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
Hey, I'm not trying to be a jackass. Maybe I am, but you have to imagine the frustration of people like myself who read for months before even trying to root a phone. You have to understand what you're doing with your device and especially a friend's. Every phone that goes back and was exchanged because a of a "bad OTA" helped create the excuse for an off-contract $500 Samsung Epic to become a $600-$700 Samasung Galaxy S3. I have never bricked a device. I tested Triangle Away for the first time on this phone for Chainfire and tested countless leaked kernels for Agat on the Epic Touch. My devices are fine because i knew what I was doing. This is why you should read.
MrAutomatic said:
This will prevent it from even powering on or getting into Download mode? Sheesh.
Click to expand...
Click to collapse
Yes since the partitions are different so let's say its supposed to format cache then on the US variant it will format something else. So the System doesn't get installed and the wrong things get formatted. You'd think you could just go back to boot loader but its wiped since the partition was different
Sent from my SPH-L710 using xda app-developers app
evo4gnoob said:
Yes since the partitions are different so let's say its supposed to format cache then on the US variant it will format something else. So the System doesn't get installed and the wrong things get formatted. You'd think you could just go back to boot loader but its wiped since the partition was different
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
For a little comparison, go install linux beside windoze on a separate partition using wubi, then delete the linux install and see if your computer will boot up. Oh no it won't boot because windows can no longer find the MBR (Master Boot Record, which is a PC bootloader) Just like borking the bootloader on a mobile device means that the device no more worky.
I like to break stuff!
-EViL-KoNCEPTz- said:
For a little comparison, go install linux beside windoze on a separate partition using wubi, then delete the linux install and see if your computer will boot up. Oh no it won't boot because windows can no longer find the MBR (Master Boot Record, which is a PC bootloader) Just like borking the bootloader on a mobile device means that the device no more worky.
I like to break stuff!
Click to expand...
Click to collapse
Ah. Hahaha. Good memories
I did this exact thing on my first linux install. Yay for recovery disks lol
Second time around I made sure I chainloaded into windows first and wrote the vista MBR. :good:
Sent from my PG06100
CNexus said:
Ah. Hahaha. Good memories
I did this exact thing on my first linux install. Yay for recovery disks lol
Second time around I made sure I chainloaded into windows first and wrote the vista MBR. :good:
Sent from my PG06100
Click to expand...
Click to collapse
I keep a rescatux disk taped to the bottom of my laptops for just such emergencies. I can't tell you how many times I've decided to upgrade or change my linux distro and hosed the MBR. Even done it a few times when the install was "successful" and linux would boot fine but windoze was MIA :banghead: only problem with a mobile device is once the bootloaders blown there's no rescue disk equivalent for the home user. Sometimes jtag can fix it but not if it doesnt come on at all
I like to break stuff!
Lol..... You did almost the same mistake I managed to do (Was my first time EVER rooting and flashing a rom). Just call sprint an play dumb. You might have to pay a fee but that's all you can really do at this point. After that mistake, I always stay in the Sprint GS3 forum along with researching all my roms, add ons, along with themes that I flash beforehand and reading the reviews on them.
Not to defend anyone but everyone was a newbie at one point but I do agree with if your not sure ask questions and read before flashing
Sent from my SPH-L710 using xda app-developers app
The root is blunt but speaks the truth. If you read. You would have seen that there are threads of people who have bricked their phone. So if you would have searched you would have seen what to do. Sheesh there's even a sticky to remind you not to flash international ROMs on the US variants.
http://forum.xda-developers.com/showthread.php?t=2156714
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png