Fluxi kernel and brickbug questions? - AT&T Samsung Galaxy S II Skyrocket SGH-I727

So I just stumbled upon the whole EMMC brickbug issue, and realized my insert indefinite period of time dependent on Samsung here is ruined. Ruined is a harsh word. Let's use "dampened." I ran the Got Brickbug app and apparently mine is known to have issues. Read an extensive thread where some devs were talking to Sammy representatives about it but my knowledge on that.niche of tech is pretty much nonexistent I was all set to flash task650s AOKP JB rom with the latest Fluxi kernel, and after some searching I couldn't really find a list of kernels that were safe (had emmc cap_erase disabled) but the search on my phone also turns up no results far often than I'd think possible..I did find one post bit it was outdated a couple months. And I read all cm kernels were safe but I really don't wanna run cm. And task650s ROM is packaged with the Fluxi kernel.so..does anyone know if.its safe? Like does it have the aforementioned cap disabled? And where would I check so as to.be informed when Samsung fixes this issue? Hell I'm glad I found it when I did or o might've bricked already. I also read that its not even a problem with sr, according to chainfire its mainly notes being affected. But still, I'm not gonna be able to get a new phone for awhile so I wanna play on the safer side for a couple more months at least. Also I recently flashed sky ics and cymbaline kernel and I was fine, but again idk if I just got lucky because I also read the bug doesn't follow a fixed pattern, like you could wipe/flash with no problems multiple times and then BAM random brick. Sorry of this is obviously listed somewhere.. the search on xda when accessed through my phone is really weird. And I don't have access to a computer at all. I did search the fluxi kernel OP but it didn't say anything about the cap being disabled. Heck I don't even know if it was the right version I was looking at. Help would be much appreciated, if it means staying on sky and keeping my phone functional then I can wait lol. Just wanted to see if I'm holding back for nothing or not, my inner desire to flashflashflash newnewnew changechangechange is left sad and neglected now.

ryancnap said:
So I just stumbled upon the whole EMMC brickbug issue, and realized my insert indefinite period of time dependent on Samsung here is ruined. Ruined is a harsh word. Let's use "dampened." I ran the Got Brickbug app and apparently mine is known to have issues. Read an extensive thread where some devs were talking to Sammy representatives about it but my knowledge on that.niche of tech is pretty much nonexistent I was all set to flash task650s AOKP JB rom with the latest Fluxi kernel, and after some searching I couldn't really find a list of kernels that were safe (had emmc cap_erase disabled) but the search on my phone also turns up no results far often than I'd think possible..I did find one post bit it was outdated a couple months. And I read all cm kernels were safe but I really don't wanna run cm. And task650s ROM is packaged with the Fluxi kernel.so..does anyone know if.its safe? Like does it have the aforementioned cap disabled? And where would I check so as to.be informed when Samsung fixes this issue? Hell I'm glad I found it when I did or o might've bricked already. I also read that its not even a problem with sr, according to chainfire its mainly notes being affected. But still, I'm not gonna be able to get a new phone for awhile so I wanna play on the safer side for a couple more months at least. Also I recently flashed sky ics and cymbaline kernel and I was fine, but again idk if I just got lucky because I also read the bug doesn't follow a fixed pattern, like you could wipe/flash with no problems multiple times and then BAM random brick. Sorry of this is obviously listed somewhere.. the search on xda when accessed through my phone is really weird. And I don't have access to a computer at all. I did search the fluxi kernel OP but it didn't say anything about the cap being disabled. Heck I don't even know if it was the right version I was looking at. Help would be much appreciated, if it means staying on sky and keeping my phone functional then I can wait lol. Just wanted to see if I'm holding back for nothing or not, my inner desire to flashflashflash newnewnew changechangechange is left sad and neglected now.
Click to expand...
Click to collapse
First off is this the aokp jb rom you were referring to??? http://forum.xda-developers.com/showthread.php?t=1766684. If so be happy that you got scared about a brickbug that is only possibly a issue on leaks where a factory reset was done within ics. Many cwm's are gb based and thus unaffected and those using ics kernels were made from source with MMC_CAP_ERASE removed. Back to the rom....IT IS FOR THE GALAXY S3!!! NOT THE SKYROCKET!! It seems you don't need to worry about brick bug but more on your own due diligence when it comes to flashing.
A) You certainly didn't search
B) Do you really think all these people in the skyrocket community would be lining up to flash their phones if bricks were almost imminent and in a way a jtag couldn't even restore.
C) Always make sure you are only flashing roms and kernels made for your phone.
I'm not trying to come off as a jerk and if I am then I apologize, but for someone so worried about their device they were about to flash a gs3 rom. We see enough people with bricked phones around here due to user error and we don't need anyone else added to the bunch.
Nice book btw. I made a sequel.
--------------------------------------------
Sent from my Skyrocket i727 running CM9
For a one stop shop 2 of Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398

Mike on XDA said:
First off is this the aokp jb rom you were referring to??? http://forum.xda-developers.com/showthread.php?t=1766684. If so be happy that you got scared about a brickbug that is only possibly a issue on leaks where a factory reset was done within ics. Many cwm's are gb based and thus unaffected and those using ics kernels were made from source with MMC_CAP_ERASE removed. Back to the rom....IT IS FOR THE GALAXY S3!!! NOT THE SKYROCKET!! It seems you don't need to worry about brick bug but more on your own due diligence when it comes to flashing.
A) You certainly didn't search
B) Do you really think all these people in the skyrocket community would be lining up to flash their phones if bricks were almost imminent and in a way a jtag couldn't even restore.
C) Always make sure you are only flashing roms made for your phone.
Nice book btw. I made a sequal.
--------------------------------------------
Sent from my Skyrocket i727 running CM9
For a one stop shop 2 of Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Click to expand...
Click to collapse
Awww man...how did I miss that?! I was wondering why it wasn't alpha or beta or anything! Lol whew REALLY good thing I found the brickbug huh, otherwise I would've never made this.post and. I would've never gotten help from someone that specializes in saying DUH! lol oh boy I feel really stupid. Okay, but seriously thank you for one pointing that out and two, easing my concerns. A, I really did search, not to argue or anything but I just wanted to make that clear so I don't seem like.one of those people.. I don't know, every time I search something it says no results found, something to that effect. B, yep that's what I was thinking but it seemed like a pretty dumb assumption to make on my part considering my non-replaceable-atm-phone situation. C, heh I'm gonna hit your thanks button for this one cause I'm pretty sure that's the best advice you can give to anyone xD
Alright, I'm gonna go hide in embarrassment while I try to find a new rom. This ones gonna be for MY phone though, neat concept right?
And yep unfortunately haven't even read it yet, that comes after Sam's teach yourself android apps. Nowhere near that point yet but I thought it looked good just for a better generalized understanding of Android and reviews said it was good for a better understanding of the lifecycle of an app. So to confirm. I dont need to worry about the brickbug at all, I can just flash any ol' kernel I want?

ryancnap said:
Awww man...how did I miss that?! I was wondering why it wasn't alpha or beta or anything! Lol whew REALLY good thing I found the brickbug huh, otherwise I would've never made this.post and. I would've never gotten help from someone that specializes in saying DUH! lol oh boy I feel really stupid. Okay, but seriously thank you for one pointing that out and two, easing my concerns. A, I really did search, not to argue or anything but I just wanted to make that clear so I don't seem like.one of those people.. I don't know, every time I search something it says no results found, something to that effect. B, yep that's what I was thinking but it seemed like a pretty dumb assumption to make on my part considering my non-replaceable-atm-phone situation. C, heh I'm gonna hit your thanks button for this one cause I'm pretty sure that's the best advice you can give to anyone xD
Alright, I'm gonna go hide in embarrassment while I try to find a new rom. This ones gonna be for MY phone though, neat concept right?
And yep unfortunately haven't even read it yet, that comes after Sam's teach yourself android apps. Nowhere near that point yet but I thought it looked good just for a better generalized understanding of Android and reviews said it was good for a better understanding of the lifecycle of an app. So to confirm. I dont need to worry about the brickbug at all, I can just flash any ol' kernel I want?
Click to expand...
Click to collapse
No one has reported brick bug on uclf6 (official ics release). Well there was one but he was having issues before he factory reset and it ended up being hardware failure. I tried to find an informative post/thread on brick bug vincom had linked in one of his stickies but to no avail. To answer your q, you shouldn't have to worry. Just don't factory reset in ics to be sure. It is kind of the standard precaution these days. Anything in cwm can be done without issue. I have flashed many roms and kernels without issue as have many many others. I understand your worry as when I was first getting started (2 months ago) the brick bug had first started rearing its head up and info was limited and varied.
As for searching, I understand the actual search in xda app doesn't work well. Try Google with xda as a keyword on the end of your topic.
PS: I updated my op as you were responding. I didn't want to come off rude, but firm and to get the point across of how close you came to a paperweight. Best of luck
--------------------------------------------
Sent from my Skyrocket i727 running CM9
For a one stop shop 2 of Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398

Mike on XDA said:
No one has reported brick bug on uclf6 (official ics release). Well there was one but he was having issues before he factory reset and it ended up being hardware failure. I tried to find an informative post/thread on brick bug vincom had linked in one of his stickies but to no avail. To answer your q, you shouldn't have to worry. Just don't factory reset in ics to be sure. It is kind of the standard precaution these days. Anything in cwm can be done without issue. I have flashed many roms and kernels without issue as have many many others. I understand your worry as when I was first getting started (2 months ago) the brick bug had first started rearing its head up and info was limited and varied.
As for searching, I understand the actual search in xda app doesn't work well. Try Google with xda as a keyword on the end of your topic.
PS: I updated my op as you were responding. I didn't want to come off rude, but firm and to get the point across of how close you came to a paperweight. Best of luck
--------------------------------------------
Sent from my Skyrocket i727 running CM9
For a one stop shop 2 of Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Click to expand...
Click to collapse
Alright great, I don't think I've ever factory reset from ics anyway. And no you didn't come off as a jerk, I can understand where you're coming from as just trying to help and like you said, prevent more unnecessary bricks. I can definitely say I should've been on top of that, seriously do not know how I overlooked that. And yeah now that you mention it I did read that somewhere, forgot I'll have to try it out. Thanks much

Related

[Q] Firmware/ROM options?

So I just bought a Galaxy S 4G believing that it had CM7 support, because the supported devices page said "Galaxy S". Whoops.
So in the meantime, I gather that I can root it and use Titanium Backup Pro to strip out some of the bloat; are there any alternative firmwares or ROMs worth trying while I wait?
If the answer is yes, I've had trouble finding instructions on how to store a copy of the stock firmware for restoration, in case I screw up or need to return the phone or something.
Thanks.
-Robin
http://forum.xda-developers.com/showthread.php?t=1117554
You still have a heck of a phone... I'm running Black Ice, works well for me, I also have been test driving dsexton's "I can't believe it's not butter" rom and yes, it is as smooth as the name implies! I'm just not a fan of the stock theme. And it's very well tweaked... There's months of reading treads all consolidated in one single flash!
You can find it in the development section along with the specs
Sent from my SGH-T959V using XDA Premium App
As QUIETLYloud mentioned, there is a great implementation of MANY tweaks in a ROM he referred to.
Also, CM7 is in fact coming to GS4G within a week or two.
For progress, check here.
http://rootzwiki.com/archive/index.php/t-681.html?
You all are fantastic and all got Thank Yous.
Something I'm not seeing, even in the Bible thread, and I'm sure it's a FAQ but I still can't find it:
What do I need to do to make absolutely certain (assuming I don't brick it, anyways) that I can get back to the stock ROM/firmware, i.e. so that I can return it if I need to?
Thanks for any pointers to whatever obvious place I missed that you can provide.
-Robin
rlpowell said:
You all are fantastic and all got Thank Yous.
Something I'm not seeing, even in the Bible thread, and I'm sure it's a FAQ but I still can't find it:
What do I need to do to make absolutely certain (assuming I don't brick it, anyways) that I can get back to the stock ROM/firmware, i.e. so that I can return it if I need to?
Thanks for any pointers to whatever obvious place I missed that you can provide.
-Robin
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1062847
Stock is there if ever necessary.

[Q] How To Either Un-Root Or Mod Further?

I will do my best to keep this short and also hope it hasn't already been answered for the sanity of the fantastic developers on this site. I know you guys hate repetition.
I've recently gone through a breakup with my now-ex, and we are not on speaking terms because of his inability to maintain sanity in some situations. My problem here is that he enjoyed continuously staying updated with the most recent updates and mods for my Charge. I have no clue how to do any of this modding, and since we are not on speaking terms, I don't know what to do about my laggy, hasn't-been-modded-in-months phone.
Before I ended communication, he spoke of a possible ICS update for my Charge. He told me it was solely open-ended developer stuff, no official update or anything, but that it was surprisingly stable. Even with him not in contact with me at this time, I would still like to see if I could do this 'update' myself. Is it possible for a complete noob like myself to do it? Or should I just leave it alone and find someone entirely more experienced to help me through it? If it's going to brick my phone with the slightest mistake, I'd rather not even try. But, like I said, you guys are the experts.
I would enjoy any kind of assistance, if possible, to install this pseudo-ICS; unless I can wait another however long the official update is for Verizon, un-root back to stock, and have the official ICS.
I guess my basic questions are:
When will the official ICS become available for my Charge through Verizon? I know it's available stock with the Galaxy Nexus (which I want quite badly) already.
Could a complete noob like myself do this with the help of you guys giving me links and step-by-step instructions (if you would be so kind)?
How easy is it to mess up without clear instructions?
I really appreciate any kind of input. MANY thanks for reading!
-Megan
No ics. No word on official update for ics. If I were you I would go back completely stock. Links are in dev section
mmassacurr said:
I will do my best to keep this short and also hope it hasn't already been answered for the sanity of the fantastic developers on this site. I know you guys hate repetition.
I've recently gone through a breakup with my now-ex, and we are not on speaking terms because of his inability to maintain sanity in some situations. My problem here is that he enjoyed continuously staying updated with the most recent updates and mods for my Charge. I have no clue how to do any of this modding, and since we are not on speaking terms, I don't know what to do about my laggy, hasn't-been-modded-in-months phone.
Before I ended communication, he spoke of a possible ICS update for my Charge. He told me it was solely open-ended developer stuff, no official update or anything, but that it was surprisingly stable. Even with him not in contact with me at this time, I would still like to see if I could do this 'update' myself. Is it possible for a complete noob like myself to do it? Or should I just leave it alone and find someone entirely more experienced to help me through it? If it's going to brick my phone with the slightest mistake, I'd rather not even try. But, like I said, you guys are the experts.
I would enjoy any kind of assistance, if possible, to install this pseudo-ICS; unless I can wait another however long the official update is for Verizon, un-root back to stock, and have the official ICS.
I guess my basic questions are:
When will the official ICS become available for my Charge through Verizon? I know it's available stock with the Galaxy Nexus (which I want quite badly) already.
Could a complete noob like myself do this with the help of you guys giving me links and step-by-step instructions (if you would be so kind)?
How easy is it to mess up without clear instructions?
I really appreciate any kind of input. MANY thanks for reading!
-Megan
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App
Girls?! On the internet?!
If you're not comfortable with any of this stuff then just go back to stock. There isn't any ICS, and there probably won't be, at least for a long time. best you can do is flash a theme or something.
Sent from my SCH-I510 using xda premium
My vote? Just learn how to mod the phone! It's really not that hard. Here's a post to get you familiar: http://rootzwiki.com/topic/4847-guide-new-users-guide-everything-how-to-root-rom-kernels-radios-cwm/
Don't flash the Froyo or Gingerbread links at the bottom tho, they'd a bit dated. Just check that post out to get familiar with the terms and process. While you're there, download and install ODIN (there's a link in that post).
***Before we move on...do you have Titanium Backup in your app drawer? If not, spend the $7. It's so worth it because you can save the vast majority of your data. It's worth the $7 (you may have it already because the exbf may have bought it/installed it). Get it and Google how to use it--make a full backup of system apps, users apps, and data before doing anything else.**
So, once you've read that post on RootzWiki, have downloaded ODIN, and made a backup with Titanium Backup, come back here and flash THIS file (follow the link in the 2nd paragraph for detailed instructions): http://forum.xda-developers.com/showthread.php?t=1380430
OK. At this point you will be unrooted and have the latest Verizon updates on your phone. You can... choose to quit... or choose to mod more. Keep in mind, if you've figured out how to flash to stock, you know how to flash mods and can continue to mod.
If I were you, I'd check out TweakStock at this point. Flash the version WITHOUT the customized kernel. Probably your best bet. Themes should be coming out for TweakStock soon, so maybe you'll find something you like.
And yeah, regarding Ice Cream Sandwich... Not happening, at least for awhile. Don't worry about it--only the Galaxy Nexus has it right now anyway.
Thank you! This was very helpful. I'm glad you pointed it out; yes, I do have Titanium. He had the paid version, signed in my phone with his Google account, and DL'd it onto my apps.
But here is another problem I have thought of-- I don't know what kind of ROM or Kernal I have...at all. No clue. Like I said, he was the expert. He always tried to show me how to do stuff, but it always went in one ear and out the other. I'm a girl who needs to be shown something from the beginning, by trial and error, and he would simply show me something 'cool' if he came across it and show me how to install it. Haha. Not saying that was ever a bad thing, I'm extremely interested in learning, but we never really had the time, and I don't want to be alone if I screw up.
go to settings> about phone and look at your firmware version. If it's 2.3.x you're on gingerbread. (you should be, if not your bf was a noob)
If you go to Settings and you see TSM Parts you're on Infinity.
If you see poop brown as a main color theme you're stock rooted.
If you go to your lock screen and it says TweakStock in the upper right hand corner you're on TweakStock.
GummyCharged and Humble are hard to distinguish. But chances are if you're not on any of the above, you're running Humble.
For kernel: if you run a program called Voodoo Control and it says status: ext4 active near the bottom, you're running imoseyon's repacked kernel. Anything else, you're either on stock or imnuts' repack.
Sent from my SCH-I510 using xda premium
kvswim said:
go to settings> about phone and look at your firmware version. If it's 2.3.x you're on gingerbread. (you should be, if not your bf was a noob)
Click to expand...
Click to collapse
that made my morning! LOL
I agree, that made me LOL as well as the 'poop brown' color reference for stock root.
Well, I took a look and it turns out I have 2.3.4. Model number is GummyCharged GBE 2.0. Of course, I have no idea what this means at all. I'm just letting you guys be in the know in case you still feel like helping me. Haha.
mmassacurr said:
I agree, that made me LOL as well as the 'poop brown' color reference for stock root.
Well, I took a look and it turns out I have 2.3.4. Model number is GummyCharged GBE 2.0. Of course, I have no idea what this means at all. I'm just letting you guys be in the know in case you still feel like helping me. Haha.
Click to expand...
Click to collapse
Well, the name of the ROM you're running is GummyCharged GBE (Gingerbread Edition) 2.0. It's very outdated now. Have you ran the batch backup for everything in Titanium yet?
mmassacurr said:
I will do my best to keep this short and also hope it hasn't already been answered for the sanity of the fantastic developers on this site. I know you guys hate repetition.
I've recently gone through a breakup with my now-ex, and we are not on speaking terms because of his inability to maintain sanity in some situations. My problem here is that he enjoyed continuously staying updated with the most recent updates and mods for my Charge. I have no clue how to do any of this modding, and since we are not on speaking terms, I don't know what to do about my laggy, hasn't-been-modded-in-months phone.
Before I ended communication, he spoke of a possible ICS update for my Charge. He told me it was solely open-ended developer stuff, no official update or anything, but that it was surprisingly stable. Even with him not in contact with me at this time, I would still like to see if I could do this 'update' myself. Is it possible for a complete noob like myself to do it? Or should I just leave it alone and find someone entirely more experienced to help me through it? If it's going to brick my phone with the slightest mistake, I'd rather not even try. But, like I said, you guys are the experts.
I would enjoy any kind of assistance, if possible, to install this pseudo-ICS; unless I can wait another however long the official update is for Verizon, un-root back to stock, and have the official ICS.
I guess my basic questions are:
When will the official ICS become available for my Charge through Verizon? I know it's available stock with the Galaxy Nexus (which I want quite badly) already.
Could a complete noob like myself do this with the help of you guys giving me links and step-by-step instructions (if you would be so kind)?
How easy is it to mess up without clear instructions?
I really appreciate any kind of input. MANY thanks for reading!
-Megan
Click to expand...
Click to collapse
Megan... I love you...and I am sorry... I'm not sure if you were hoping i'd find your thread.
But heres the info needed incase.
It's the most recent rootzwiki gummycharged, it's outdated, but it's at least bloatfree. Stock leaked kernel from way back, but it was for sure 2.3. I don't play with ancient software.
When I said upadte, Verizon had finally gotten an Official 2.3, over the leaked, which I urged you to update to for stability, even with bloat, since most roms will now be based off the OTA. When I spoke of ICS, I meant on my phone, and I guess it's hard to exactly explain what open source is, roms, and ota's. But given a Dev and the right sources from Sammy and Google, it can run it. This phone just seems to lack the strong community it did with imnuts, like the fascinate.
Enjoy Inifinty. I'll be a better person someday in the long run, but right now, i've got a lot more to work on with myself rather than phones (which is why my ICS is kinda not a big deal to me as).
GL.
Windst said:
Megan... I love you...and I am sorry... I'm not sure if you were hoping i'd find your thread.
But heres the info needed incase.
It's the most recent rootzwiki gummycharged, it's outdated, but it's at least bloatfree. Stock leaked kernel from way back, but it was for sure 2.3. I don't play with ancient software.
When I said upadte, Verizon had finally gotten an Official 2.3, over the leaked, which I urged you to update to for stability, even with bloat, since most roms will now be based off the OTA. When I spoke of ICS, I meant on my phone, and I guess it's hard to exactly explain what open source is, roms, and ota's. But given a Dev and the right sources from Sammy and Google, it can run it. This phone just seems to lack the strong community it did with imnuts, like the fascinate.
Enjoy Inifinty. I'll be a better person someday in the long run, but right now, i've got a lot more to work on with myself rather than phones (which is why my ICS is kinda not a big deal to me as).
GL.
Click to expand...
Click to collapse
LMAO! Best.Post.Ever.
Sent from my SCH-I510 using xda premium
Well, ****. This is awkward. ABANDON THREAD!
Sent from my SCH-I510 using xda premium
Charge Insufficient Memory On Device
I rooted a Droid Charge for my boss using the altered beast method, and now no matter what I do. When I try to download from the market, it tells me there is insufficient space on the device. When there is plenty of room on the sd card, and internal. Can someone please help me, I've tried a reset, and clearing the cache, and download history in the market. Any help someone could offer would be much appreciated.

My first flashing... (no trenchcoat involved)

So, I finally flashed a ROM onto my Atrix 2 for the first time the other day.
Synopsis
​Long story short the twitter app crashed my phone and threw it into a boot-loop, I did some research, quickly learned the in's-and-out's of flashing ROM's, flashed the stock-ROM for my device, fully updated my device, and became a better man for it...okay, well maybe not that last part!
The nitty-gritty
​What happened was I was trying to update my twitter when the app locked up after hitting the 'submit' button. I tried to force-close the program but to no avail. Then I had the bright idea of shutting down my phone. This is where the fun began.
After re-booting my phone, I discovered that it was stuck in a boot-loop. Now, my phone has been rooted for a little over a month. There were no issues that occurred after I rooted my phone up until that point. This is what leaves me to believe that Twitter corrupted some app data.
After this happened I took to the internet and scoured over forums (this one chief among them), articles, videos, and even asked a few fellow-android users here in the real world. Everywhere I looked lead me to this term I had feared up until this point: Flashing.
I understood that flashing a ROM was just like installing a new operating system. I had toyed around with Linux before just a bit and am savvy-ish when it comes to computers. However, I was so terrified of bricking my phone in trying to flash a new ROM onto it (I would have been track-phoning for around a year until my next manufacturer subsidy came out on my account.)
After discovering terms like deodexed, CM7, stock, AP Fastboot, RSD Lite, and hardware-key reset, I felt like I was finally able to attempt the flashing. The first few attempts failed as I didn't realize I didn't have enough battery life to sustain the flashing process.
After charging it up, I flashed the stock ROM onto my phone. The moment it went from the red M puddle screen to the dripping AT&T sphere, then onward to the ROM was a moment of pure joy (not to sound corny.) I felt like I had beat-the-system. A problem that would have forced others to return their phone to the store was a problem that I fixed myself.
Final Thought
​I know this is rather cinematic for it being a simple flash job on an android device. But, for me, this was quite exhilarating. I'm not comfortable flashing anything lower than full-release ROM's (beta and alpha ROM's are a bit beyond my scope right now.) But, I do look forward to testing out various full-release ROM's as they become available.
AscottW said:
So, I finally flashed a ROM onto my Atrix 2 for the first time the other day.
Synopsis
​Long story short the twitter app crashed my phone and threw it into a boot-loop, I did some research, quickly learned the in's-and-out's of flashing ROM's, flashed the stock-ROM for my device, fully updated my device, and became a better man for it...okay, well maybe not that last part!
The nitty-gritty
​What happened was I was trying to update my twitter when the app locked up after hitting the 'submit' button. I tried to force-close the program but to no avail. Then I had the bright idea of shutting down my phone. This is where the fun began.
After re-booting my phone, I discovered that it was stuck in a boot-loop. Now, my phone has been rooted for a little over a month. There were no issues that occurred after I rooted my phone up until that point. This is what leaves me to believe that Twitter corrupted some app data.
After this happened I took to the internet and scoured over forums (this one chief among them), articles, videos, and even asked a few fellow-android users here in the real world. Everywhere I looked lead me to this term I had feared up until this point: Flashing.
I understood that flashing a ROM was just like installing a new operating system. I had toyed around with Linux before just a bit and am savvy-ish when it comes to computers. However, I was so terrified of bricking my phone in trying to flash a new ROM onto it (I would have been track-phoning for around a year until my next manufacturer subsidy came out on my account.)
After discovering terms like deodexed, CM7, stock, AP Fastboot, RSD Lite, and hardware-key reset, I felt like I was finally able to attempt the flashing. The first few attempts failed as I didn't realize I didn't have enough battery life to sustain the flashing process.
After charging it up, I flashed the stock ROM onto my phone. The moment it went from the red M puddle screen to the dripping AT&T sphere, then onward to the ROM was a moment of pure joy (not to sound corny.) I felt like I had beat-the-system. A problem that would have forced others to return their phone to the store was a problem that I fixed myself.
Final Thought
​I know this is rather cinematic for it being a simple flash job on an android device. But, for me, this was quite exhilarating. I'm not comfortable flashing anything lower than full-release ROM's (beta and alpha ROM's are a bit beyond my scope right now.) But, I do look forward to testing out various full-release ROM's as they become available.
Click to expand...
Click to collapse
In all technicality all you're doing when flashing a rom (at least now) is installing some tweaked files such as build.prop or some tweaked system files for themes. By no means is it a new OS. But once a main kernel Dec finished up with a CM7 kernel we should be able to flash a custom kernel which is the meat of what really runs your phone. Really the stuff we can do right now only really have to do withtl the UI.
But anyways welcome to the world of android development!
Sent from my MB865 using XDA
Congrats on flashing your first ROM . Sorry to hear it didn't completely work out for your. Quick question: did you wipe the Dalvik Cache as part of the flashing process?
By the way, most of the ROMs labeled "beta" are pretty stable. If a ROM has had more than a few updates and it's still in beta, it's mostly because the developer is either planning on adding more features for the full release or is a perfectionist
Well, as you can tell it's a sharp learning curve. But welcome to the world of Android hacking/modding/whateveryoucallit, and happy flashing
wait, are you telling me that there are actually people who do research before complaining about some little thing they don't know how to do?!?!?!?!?!?!?
FINALLY
Sent from my MB865 using XDA
LOL.. good story/nice read.. Welcome!
I would say it worked out pretty well. I will probably flash a custom ROM later on this week. I will also keep reading up on the whole process and the it's and out's.
I cleared both user data and the dalvik cache as well. Pretty much at that point I was desperate. Lolz
Sent from my MB865 using xda premium
lkrasner said:
wait, are you telling me that there are actually people who do research before complaining about some little thing they don't know how to do?!?!?!?!?!?!?
FINALLY
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Hahaha.. Well, with this involving my phone (for which I don't have the hundreds of dollars to buy one outside the manufacturers subsidy) I wanted to make sure I was doing things right.
Sent from my MB865 using xda premium
AscottW said:
I would say it worked out pretty well. I will probably flash a custom ROM later on this week. I will also keep reading up on the whole process and the it's and out's.
I cleared both user data and the dalvik cache as well. Pretty much at that point I was desperate. Lolz
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
its really easy, so you should go ahead, the roms we have are way better than stock. Lithium is y favorite right now.
alteredlikeness said:
LOL.. good story/nice read.. Welcome!
Click to expand...
Click to collapse
Glad you enjoyed it! I am happy that my twitter app decided to crash, now.
Sent from my MB865 using xda premium
AscottW said:
Hahaha.. Well, with this involving my phone (for which I don't have the hundreds of dollars to buy one outside the manufacturers subsidy) I wanted to make sure I was doing things right.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I second that.. better to take your time to research, and do things right the first time...
lkrasner said:
its really easy, so you should go ahead, the roms we have are way better than stock. Lithium is y favorite right now.
Click to expand...
Click to collapse
^Total opinion about stock and custom... I'm on stock/odex/modded/tweaked with some bells and whistles... nice, responsive, and stable..
Sent from my mind using XDA
alteredlikeness said:
^Total opinion about stock and custom... I'm on stock/odex/modded/tweaked with some bells and whistles... nice, responsive, and stable..
Sent from my mind using XDA
Click to expand...
Click to collapse
I agree. Spent this weekend working on the Stock 2.3.6 rooted/odexed. Added the Superv6, and other mods, hotspot wifi fix, removed bloat. Definitely more fun this way. Then again I had a buttload of practice on my original ATRIX.
And thank god for the bootstrap and FXZ !!!!
dicksteele said:
And thank god for the bootstrap and FXZ !!!!
Click to expand...
Click to collapse
Yes without that I would of had an expensive paperweight to many times
dicksteele said:
I agree. Spent this weekend working on the Stock 2.3.6 rooted/odexed. Added the Superv6, and other mods, hotspot wifi fix, removed bloat. Definitely more fun this way. Then again I had a buttload of practice on my original ATRIX.
And thank god for the bootstrap and FXZ !!!!
Click to expand...
Click to collapse
How exactly do I identify bloatware? I have two programs to do that Titanium backup and Rom Manager as well as a few 3p uninstallers. However, I never know exactly what to delete?
AscottW said:
How exactly do I identify bloatware? I have two programs to do that Titanium backup and Rom Manager as well as a few 3p uninstallers. However, I never know exactly what to delete?
Click to expand...
Click to collapse
DON'T ever delete any programs. It is better to use something like bloat freezer, and freeze these apps, than to delete them.
The updates check for missing "bloatware" and will fail to install the updates due to ANY missing apps, that came with the stock image.
If you want a debloated image, then use one of the more custom ROMS like lithium, or Supercharged, etc.
If you use a debloated ROM, then you can always flash the fxz back before any updates come out, we tend to start screaming pretty load on here when updates start to arrive as you may have already seen this week with the ICS leaks.
P.S. It is VERY hard to hardbrick this phone, it took me killing the signature on the kernel to get my first hardbrick, and I have had 3 more hardbricks. I have the warranty through att, so I never worry about things like that, since I am a dev and take my phones life into my own hands, and ATT always has exchanged my phone on the spot for over 12 years now.... You can softbrick (bootloop), but that is an easy fix with the FXZ (lifesaver). So not too much to worry about hurting your phone with flashing...
jimbridgman said:
DON'T ever delete any programs. It is better to use something like bloat freezer, and freeze these apps, than to delete them.
The updates check for missing "bloatware" and will fail to install the updates due to ANY missing apps, that came with the stock image.
If you want a debloated image, then use one of the more custom ROMS like lithium, or Supercharged, etc.
If you use a debloated ROM, then you can always flash the fxz back before any updates come out, we tend to start screaming pretty load on here when updates start to arrive as you may have already seen this week with the ICS leaks.
P.S. It is VERY hard to hardbrick this phone, it took me killing the signature on the kernel to get my first hardbrick, and I have 3 more hardbricks. I have the warranty through att, so I never worry about things like that, since I am a dev and take my phones life into my own hands.... You can softbrick (bootloop), but that is an easy fix with the FXZ (lifesaver). So not too much to worry about hurting your phone with flashing...
Click to expand...
Click to collapse
LOL, I was laughing so hard when XDA crashed last night. I was sure we caused it with our ICS Freak out!!!!
lkrasner said:
LOL, I was laughing so hard when XDA crashed last night. I was sure we caused it with our ICS Freak out!!!!
Click to expand...
Click to collapse
I though the same thing, and I was kind of glad it did crash though, so that I could find that article with the interview of cyanogen that was posted on the XDA-dev home page.
AscottW, I am like you -I read and researched and forum'd my evening/early morning hours away with regards to the whole rooting and flashing and so on. I have never done such things with a phone before, but being fairly computer savvy myself felt like after several hard weeks learning as much as I could, flashed MY first ROM. (Did a little happy dance myself when I saw the custom boot animation for the first time, think I even let out a little school boy squeal as well! -Glad no one was around to hear that)
Still reading and researching and forum'ing at every free moment I have (girlfriend and kids think my laptop has become permanently attached to my, well... lap!) and am really interested in possibly getting myself to a point where I can be of some usefulness in the dev world.
Admittedly, after flashing for the first time, I got foolish with CWM and did basically what seemed like deleting the system partition and told the Android OS to get lost. Big mistake. Got stuck in a crazy splash screen loop and wouldn't load Android OS for the life of me. That said, with the help of the good people here on this forum, I was able to be walked through a AP Fastboot FXZ file fix, updated back to 2.3.6, and started over -making damn sure I knew what I was doing before doing ANYTHING! lol
Feel like: "I just had sex"
http://www.youtube.com/watch?v=lQlIhraqL7o
PhoenixNghi said:
Feel like: "I just had sex"
http://www.youtube.com/watch?v=lQlIhraqL7o
Click to expand...
Click to collapse
lol @ this!

[Q] In your opinion what is the best ROM for the Galaxy Blaze 4G?

Hey guys,
I frequent the EVO forums since my current phone is the EVO 3D. My best friend has a Blaze 4G, which I rooted for him about a month ago. I know nothing of current Samsung ROMs and while I could search and read every thread in the Blaze section, I was hoping you guys could save me some time.
General requirements for any ROM to be considered:
1) Must have working camera/camcorder (He has a 7 year old daughter he just got custody of and Dads gonna want to take pictures.)
2) Must be "Stable". My friend is a great guy but not a computer/phone savvy as I am...I don't want his phone to **** the bed while I'm at work, I'd feel like an uber douche.
Please in your responses include any pro's/ con's and why YOU like it...Thanks a ton
ItzCrooK2UxD said:
Hey guys,
I frequent the EVO forums since my current phone is the EVO 3D. My best friend has a Blaze 4G, which I rooted for him about a month ago. I know nothing of current Samsung ROMs and while I could search and read every thread in the Blaze section, I was hoping you guys could save me some time.
General requirements for any ROM to be considered:
1) Must have working camera/camcorder (He has a 7 year old daughter he just got custody of and Dads gonna want to take pictures.)
2) Must be "Stable". My friend is a great guy but not a computer/phone savvy as I am...I don't want his phone to **** the bed while I'm at work, I'd feel like an uber douche.
Please in your responses include any pro's/ con's and why YOU like it...Thanks a ton
Click to expand...
Click to collapse
I understand completely what you are saying about a rom for your friends Blaze. I would recommend Dark KNight Build 8 and Tweaked ROM. Both are stable and run well. I have been using Dark Knight since the day it hit. No force closes, no random reboots, everything is working fine. Tweaked is also very stable and everything works. Also I would recommend flashing the scorched kernel as well.
Hope this helps
I agree, tweaked and dknight are probably your best options, although I think there is JMT, but I have never tried that.
Let me ask you though. Is there a reason your friend does not want the stock rom? If he's not to tech savvy as you say, if it were my friend I would let him stick with stock, all the roms have there small issues. And although some may not bother me, it may be something your friend would rather not deal with. Having said that, after setting up dknight with the torched kernel and running for quite some time now, I have not had any problems.
Sent from my SGH-T769
flyers00 said:
I understand completely what you are saying about a rom for your friends Blaze. I would recommend Dark KNight Build 8 and Tweaked ROM. Both are stable and run well. I have been using Dark Knight since the day it hit. No force closes, no random reboots, everything is working fine. Tweaked is also very stable and everything works. Also I would recommend flashing the scorched kernel as well.
Hope this helps
Click to expand...
Click to collapse
Thanks I will flash this tomorrow, after reading through both of those threads
LiveFaster said:
I agree, tweaked and dknight are probably your best options, although I think there is JMT, but I have never tried that.
Let me ask you though. Is there a reason your friend does not want the stock rom? If he's not to tech savvy as you say, if it were my friend I would let him stick with stock, all the roms have there small issues. And although some may not bother me, it may be something your friend would rather not deal with. Having said that, after setting up dknight with the torched kernel and running for quite some time now, I have not had any problems.
Sent from my SGH-T769
Click to expand...
Click to collapse
He wants something different. From what I've read about the Blaze 4G and its users y'all have the same issue EVO 3D users had with regards to ICS update (We were told Q1 2012...didn't get an official OTA until 7/31). We will hang out, drink some cold beers and he will play with my phone and say "Damn, Chris...I wish my phone would do that" or "Hey Chris...you think you can make my phone do *insert cm9/10 feature here*" So a few weeks ago I went ahead and rooted his phone, he loves that HE is in control of his device...even if he has no idea what it can do. I set up Titanium for him and did a NANDROID backup so that if something went wrong he has a known good flash point. He knows that when in doubt, don't mess with it or call me and we will go through it together. So in fairness to him, he is savvy enough to know not to really mess with it until he more knowledgeable...
Besides all that the man couldn't type until I got him addicted to a MySpace app, I am hoping that once he sees what his device can do with some mods he will take interest the same way and learns to do this for himself...just gotta get him that first hit ya know

Vibrant Similarities and Best ROM for first flash on S3 and

I had the Vibrant and flashed all kinds I'd ROMs with it. Moved to the iPhone 4s and then traded that for my new S3. It was a good choice. So now I'm planning to get started flashing on this phone.
Wanted to know what is the same and what is different from the Vibrant from previous Vibrant users.
What's the best place to start flashing? I'm looking for stability and speed. Preferably more stability than stock cause stock is a little buggy honestly.
Sent from my SCH-I535 using xda app-developers app
GoodVibrant-ions said:
I had the Vibrant and flashed all kinds I'd ROMs with it. Moved to the iPhone 4s and then traded that for my new S3. It was a good choice. So now I'm planning to get started flashing on this phone.
Wanted to know what is the same and what is different from the Vibrant from previous Vibrant users.
What's the best place to start flashing? I'm looking for stability and speed. Preferably more stability than stock cause stock is a little buggy honestly.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Please elaborate on what is buggy about stock?
My question was more about everything else I posted besides that statement but to answer the question, I am getting force closes on some apps and occasionally the home screen locks up. That's what I meant by buggy.
Sent from my SCH-I535 using xda app-developers app
there's a link in my signature that should help you id post it but im on my ipad using tapatalk right now.
In before the lock
Sent from my Galaxy SIII
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
And I was hoping someone could tell me what's stable and smooth right now. Stock has been touch and go for my device and I haven't done anything to it. I'm looking for a fast non-overclocked kernel matched with a stable daily driver ROM. Any help is appreciated, dickhead comments aren't. This place has turned all elitist. This is the General forums....thought I could get away with a few simple questions with answers based on experiences, after having read through all these threads.
Speaking of which NeverendingXin, I read a lot of that thread yesterday but it seemed to give descriptions of what AOSP vs AOKP vs CM10 vs MIUI. Which I learned a lot from and I appreciate. But I was looking for more advice on specific ROMs. Anyone that could say "This ROM with this kernel has worked for me and I like it's speed" or whatever would do.
You want to find out what's stable and smooth?
Man up and make a backup of your current rom and flash away trying different roms. You'll likely end up getting different responses from different people and it isn't likely you'll have their same experience. Just find out for yourself. The guide the person above directed to you to was made to prevent threads asking what rom is stable or to use.
Sent from my Galaxy SIII
GoodVibrant-ions said:
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
And I was hoping someone could tell me what's stable and smooth right now. Stock has been touch and go for my device and I haven't done anything to it. I'm looking for a fast non-overclocked kernel matched with a stable daily driver ROM. Any help is appreciated, dickhead comments aren't. This place has turned all elitist. This is the General forums....thought I could get away with a few simple questions with answers based on experiences, after having read through all these threads.
Speaking of which NeverendingXin, I read a lot of that thread yesterday but it seemed to give descriptions of what AOSP vs AOKP vs CM10 vs MIUI. Which I learned a lot from and I appreciate. But I was looking for more advice on specific ROMs. Anyone that could say "This ROM with this kernel has worked for me and I like it's speed" or whatever would do.
Click to expand...
Click to collapse
Well in that sense the best information I can give you is that for a touch wiz ics Rom I'd use synergy, I used that for a long time and it was always super stable and smooth for me. If your looking for aosp then I'd use either liquid smooth or slim bean I'm more familiar with liquid and it's really great, but I'm trying out slim bean and it's so far been good as well. I hope this helps
GoodVibrant-ions said:
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
Click to expand...
Click to collapse
I'm from the Fascinate but I've also worked on the Vibrant.
* You don't have to worry about bml/mtd here. Which means you can flash basically everything without having to odin.
* You do have to worry about the locked bootloader. CASUAL can unlock it. Droidstyle has a sticky thread here on xda to help you with this and many other processes.
* There are excellent stock and AOSP-based ROMS. AOSP-based ROMS aren't quite 100% (but close) on RIL issues though.
*On verizon, radios are typically flashed separately and only in certain circumstances (odin package) included with ROMS.
* You DO have to worry about the IMEI issue. There are numerous threads about backing up this information and a Sticky thread with a tool for recovering it.
* If you are looking for a custom kernel check out Leankernel which is linked to in the signature of the poster above me. note that it's an AOSP kernel. Find the touchwiz version in the same forum.
Something else to bote about unlocking the bootloader, if you are going to use EZ Unlock from the market DON'T!!!! Go to root wiki and download version 1.2. For some reason 1.3 & 1.4 are wonky. The older versions are on the same thread as 1.4.
My vote for a ROM is Paranoid Android, I had some bug issues on Liquid Smooth but on PA I have had none thus far. I would reccomend flashing Paranoid Android version 2.5 instead of 2.51, there seems to be an issue for some users with the latest commits in 2.51 from what I read earlier today.
I'm sure you know how to back up you IMEI but just in case use the terminal method and the synergy flash method.
Just trying to cover most bases, I didn't know what you knew and didn't know.
Sent by one of my many Anthromorphic Personifications
GoodVibrant-ions said:
My question was more about everything else I posted besides that statement but to answer the question, I am getting force closes on some apps and occasionally the home screen locks up. That's what I meant by buggy.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The reason I asked is because stock on the S3 is as stable as you are going to get. The most stable custom Roms are going to be the ones based of stock TW and you can get them with some added tweaks. They are no more stable then stock as stock is stable as a *****. If you are getting force closes and lockups there is probably an issue with what you have installed.
Any AOSP rom will still have bugs and will be the least stable out of all the options. No matter how many people say Liquid or AOKP or CM10 or PA or MIUI is running great, they run no where near as stable and perfect as any TW rom.
If you want stability, go with a TW rom. read the different threads, mostly the last couple of pages of each which are usually about the latest release and you will know what is good and what is not.
This is what I am running and it does not get any more stable then this but then again stock was stable as ***** as well...
http://forum.xda-developers.com/showthread.php?t=1904329
Thanks guys.... this is exactly what I was looking for. As far as backing up the IMEI, I've never had to do that. Not on the Vibrant or My HTC View....so I have some reading to do there. Any tips or links to threads on that would be appreciated.
And I did have to unlock the bootloader on the View, but it's not a process I know a lot about.... so reading to do there as well.
Thanks for the tips guys. Looks like I'm going back to do some more studying.
Sent from my SCH-I535 using xda app-developers app
A very very good post explaining how to flash recoveries, roms, and just about anything else you ever would need to know:
http://forum.xda-developers.com/showthread.php?t=1762709
IMEI Backup:
http://forum.xda-developers.com/showthread.php?t=1852255
EZ-Unlock for you bootloader, download version 1.2 it is towards the bottom of the first post:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Sent by one of my many Anthromorphic Personifications
Perfect. Thanks man. I'd seen the first two threads but not the ezunlocker thread. Should be all I need to figure out how to get started and which ROM to try.
Thanks for the help guys
Sent from my SCH-I535 using xda app-developers app
PaulG1488 said:
You want to find out what's stable and smooth?
Man up and make a backup of your current rom and flash away trying different roms. You'll likely end up getting different responses from different people and it isn't likely you'll have their same experience. Just find out for yourself. The guide the person above directed to you to was made to prevent threads asking what rom is stable or to use.
Sent from my Galaxy SIII
Click to expand...
Click to collapse
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
shangrila500 said:
Something else to bote about unlocking the bootloader, if you are going to use EZ Unlock from the market DON'T!!!! Go to root wiki and download version 1.2. For some reason 1.3 & 1.4 are wonky. The older versions are on the same thread as 1.4.
My vote for a ROM is Paranoid Android, I had some bug issues on Liquid Smooth but on PA I have had none thus far. I would reccomend flashing Paranoid Android version 2.5 instead of 2.51, there seems to be an issue for some users with the latest commits in 2.51 from what I read earlier today.
I'm sure you know how to back up you IMEI but just in case use the terminal method and the synergy flash method.
Just trying to cover most bases, I didn't know what you knew and didn't know.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
rampantandroid said:
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
Click to expand...
Click to collapse
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
shangrila500 said:
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Check the PA thread for the answer - go into PA settings, go to the app settings, find the settings app in there and hit reset. My guess is that it is a bug with the current version of the ROM.
GoodVibrant-ions said:
Perfect. Thanks man. I'd seen the first two threads but not the ezunlocker thread. Should be all I need to figure out how to get started and which ROM to try.
Thanks for the help guys
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
shangrila500 said:
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
rampantandroid said:
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
Click to expand...
Click to collapse
So what ROM did you end up using? Any that you'd recommend?
Please read forum rules before posting
Questions go in Q&A
Thread Moved
Thanks
FNM

Categories

Resources