Develop Bugs

Ox's noob corner (work in progress)- everything you need to get started right here

Well everyone the dinc2 community has treated me well but I have moved on to the htc rezound please do not hesitate to still pm questions though I'm hoping I can find a volunteer to take over this thread. I'll miss you guys cuz for the most part it was a very mature forum and ill pop in once in awhile to say hello. Good luck if anyone would like to give back to this community and take over this thread pm and ill pm a mod. god bless
I thought it maybe fun to have a light and humorous side to this also so everyone keep your eyes out for funny posts that can make our quote of the day:
if you guys see any posts that make you chuckle pm me and I will put it here and credit you for finding it
Anyone looking to root your incredible2 that is on 2.3.4 with the.98 hboot please see here: http://forum.xda-developers.com/showthread.php?t=1298990 then after your hboot is downgraded follow the instructions on rivera82falcons thread,linked below
hey guys I'm attempting to get a thread started to get all the basic info out to the newcomers that they will need to start there modding a flashing journey. I'm also hoping this will help cut down on the repetitive questions and useless posts mucking up our forums. This is and always will be a work in progress, so this is just a start there will be much more info added as time goes on.
First thing if your not rooted yet everything you need to know is in this thread by rivera82falcon http://forum.xda-developers.com/showthread.php?t=1219246
Next up is how to flash a custom rom: http://forum.xda-developers.com/showthread.php?t=1263756 by AgalychnisCallidryas
Another thing is the gingerbread ruu. If your phone comes with froyo I would reccommend following the directions on this page before trying to root because unrevoked is becoming increasingly harder to find. Also this can get you out of some pretty sticky situations if you mess up badly enough: http://www.androidpolice.com/2011/0...8-605-4-same-as-the-official-gingerbread-ota/
wanna try a different radio? Head over to gu1dry's thread: http://forum.xda-developers.com/showthread.php?t=1134451
Its my opinion that every flasher should have adb setup on their computer, it will bail you out of a bootloop, tell you why its happening and do all kinds of other awesome stuff. here is an excellent thread from nephron to get you on your way, its from another phones forums but everything except the drivers apply to us, obviously install the correct drivers for your phone: http://forum.xda-developers.com/showthread.php?t=532719
for those of you who use aosp roms, just about everyone prefers the miui camera over the aosp stock one and here it is with instructions. Thanks pacerguydon: http://forum.xda-developers.com/showpost.php?p=17691395&postcount=11
if your market is missing apps, check this out: http://forum.xda-developers.com/showthread.php?t=1275574 thanks knipp
those of you who want to learn java and general scripting here is a few good tutorials that artvandelay440 dug up:http://forum.xda-developers.com/showpost.php?p=17691710&postcount=13
for the up and coming themers here is where to get brut.alls apktool:http://code.google.com/p/android-apktool/ if anyone can find me a good noob friendly tutorial for apktool let me know and I'll post it.
tommytomato created a fantastic super tool called android utility, you can decompile apks sign them and do all kinds of good stuff. Really the ultimate themeing tool: http://forum.xda-developers.com/showthread.php?t=1167623 if your thinking of doing mods and themes of your own you should check this out, tommy is a modding master and extremely helpful to new themers
wanna changer your splash screen or boot animation? Have a look at 06stangs thread here: http://forum.xda-developers.com/showthread.php?t=1161543
if your running an aosp rom you can change the carrier label here's how: http://forum.xda-developers.com/showthread.php?t=1221882 thanks to artvandelay440
running a sense rom? Go here for a new lockring: http://forum.xda-developers.com/showthread.php?t=1260128 thanks to jwhetstone02
our friend knipp21 has started modding miui lockscreens check it out: http://forum.xda-developers.com/showthread.php?t=1288566
before getting my incredible2 I had an inspire, the one thing I missed about the inspire was 4ext recovery,well now we have it. Big thanks to madmaxx80 for the awesome recovery: http://forum.xda-developers.com/showthread.php?t=1267540
here is a great tool for undervolting, it provides an easy to use gui, please read up on the pros and cons of undervolting before attempting and remember you must have a kernel that supports undervolting to use this. It will not work on the stock kernel. Thanks to chad0989 for this: http://forum.xda-developers.com/showthread.php?t=1190004
here is setcpu a tool for overclocking, your kernel must support overclocking and this should not be used in conjunction with any other overclocking apps. Thanks to coolbho3000 for this, and please guys consider purchasing the donate version of this: http://forum.xda-developers.com/showthread.php?t=505419
here is a very educational thread similar to this one, its from the thunderbolt forums but most of the info applies to us as well. Its a very well put together thread and super informative. I reccommend you guys check it out because its a good read. Big thanks to loonatik78 for putting it together: http://forum.xda-developers.com/showthread.php?p=16695064#post16695064
another thing I would like to stress to the new people, xda has a thanks button, and now you can even use it right from the xda app, don't be greedy with it guys if someone helps you click thanks.
I would like this thread to become a community effort, if there is anything you guys feel should be here dont hesitate to let me know. This is my small effort to give back to a community that gave me so much so I will gladly try to answer any and all questions in an effort to keep our forums clean. No matter how stupid you think the question may be pm me and I'll try to help. I may not always have your answer but will most likely be able to point you in the right direction. see post three for frequently asked questions

Pm me for any and all questions as well.
Sent from my Incredible 2 using xda premium

this q and a section will be a work in progress as well. If anyone has suggestions for questions that you think should be here, by all means let me know.
Q: I think I bricked my phone what should I do?
A: calm down 99 percent of the time people think they are bricked they really aren't. If your device shows any sign of life your chances are good that your ok. If you can access hboot by holding volume down and power while the device is off your in good shape you can still flash the ruu and get back to stock.
Q: I put the ruu on my sdcard but hboot cannot find it
A: when flashing anything from hboot it must be named exactly PG32IMG.zip and yes it is case sensitive. Also if you have to rename the file, if doing it on a computer be careful because a computer will automatically add a .zip to the end of it and hboot will not recognize it.
Q: I flashed a kernel a now my "insert issue here" don't work
A: did you flash an aosp kernel on a sense Rom or vice versa? If so things will not work as they should always make sure the kernel you are flashing is compatible with your Rom.
Q: will sense apps and widgets work on aosp roms?
A: short answer is no
Q: my phone is stuck in a bootloop what should I do?
A: some time in your flashing career you will encounter a bootloop, there are a couple of ways to fix this number one is start adb (which every Rom flasher should have set up in my opinion) and type adb reboot recovery and hit enter then once in recovery you can reflash and try again. Your other option is to pop the battery out, put it back in then hold volume down and power to get into the bootloader once there select recovery. If you can not navigate in the bootloader that means the PG32IMG.zip is on your sdcard still. Remove that and it will let you navigate the bootloader. If you have no way to remove that .zip pop out your sdcard boot into bootloader select recovery then pop your card back in.
Q: what is the best Rom out there?
A: there is none its all a matter of opinion. Just a warning, don't start a new thread asking this question you will be flamed into oblivion and the mods will lock it. I've seen it a million times
Q: I just flashed an aosp Rom (miui, cm7, omgb) why is my earpiece volume so low?
A: as of now this is a known issue for our aosp Roms, the tiamat kernel is said to fix it.
this is the start of my q and a and it is far from complete, if you think there is something important that is not here by all means let me know.
Ok guys here is some basic terms you should be familiar with before rooting and flashing
1. Flash or flashing, basically just means to install something from recovery or bootloader
2. Rom- the word rom is kind of an outdated term (read only memory) because we can in fact write to it, nonetheless a rom in the simplest of terms is basically your operating system.
3. Kernel- the kernel is the heart of your o.s. It basically communicates with your software and hardware, wifi and processor speed are a few examples of things your kernel controls among many other things. Sense kernels should not be used on aosp roms and vice versa things will not work as they should.
4. Overclocking- to increase your processors stock speed to increase performance
5. Underclocking- pretty self explanatory underclocking is used to help save battery
6. Undervolting- to decrease your voltage to save battery. Undervolting is a slightly controversial topic some people swear by it and others say it can actually decrease your battery life. Undervolting can cause stability issues so educateyourself before attempting.
7. Radio- basically the software that works with your hardware to give you your signal and mobile network, on other phones they are also reffered to as modems
8. Aosp- android open source project, aosp roms are roms built from the original google source code, some examples of these are cm7, miui, omgb, these are typically lightweight roms that you can customize yourself, they are preffered by many users because of the great battery life and performance
9. Sense roms- these are roms based on an original htc rom, sense is th ui that htc adds to android, sense roms have many nice apps and widgets, and usually are packed with eyecandy, however many people say that sense it a resource hog and needs a lot more ram to run than aosp roms
10. Port- a port is a rom or theme originally made for another device but made to work with ours
11. Wipe- it is usually recommended to wipe before flashing a rom, but not always mandatory, read the forum of the rom your flashing to see if a wipe is recommended or not. Some roms will wipe data automatically some will not. A wipe is just basically giving you a clean start like when you first got the device and is done in the recovery menu. When in doubt wipe, you will run into less issues.
12. Ruu- an ruu is a stock signed rom that is flashed in hboot, an ruu is your get out of jail free card, if you mess your phone up too bad an ruu will bring your device back to its stock state
13. Hboot_ this is basically your bootloader from hboot you can enter recovery, do a factory reset, and flash an ruu, a radio, and other things not flashable in recovery
there is some more basic definitions that I overlooked, see post 28 by artvandelay440

How about some basic definitions? Sense, AOSP, Rosie, kernel, recovery, md5 sum, etc.
How, when, and why to wipe.
How to perform a battery calibration.
Don't restore system data when moving to a different ROM or updating to a new framework.

ontophantoms said:
How about some basic definitions? Sense, AOSP, Rosie, kernel, recovery, md5 sum, etc.
How, when, and why to wipe.
How to perform a battery calibration.
Don't restore system data when moving to a different ROM or updating to a new framework.
Click to expand...
Click to collapse
yes good idea. Definitely will do. I also plan to add a miscellaneous goodies section including commonly used apps like miui camera. And links to kernels and other good stuff. Like I said this thread is a wip I just wanted to get a start on it tonight. I'm not at home now and I'm doing this on my touchpad so its quite tedious. Will work on it a lot more tomorrow. Thanks for the input

Love this idea for a thread. I know this will be a stop that noobs and even seasoned vets will make. Thanks for taking the time to put something like this together!

Thanks for setting this up!
It's really helpful to us newcomers, who inevitably ask a question that will annoy the seasoned members. There is so much info buried in threads with many pages that it's hard to read it all and not overlook something along the way.
Having all the start-up info, and maybe a list of well-known bugs for each rom, in one place will be great!

Woot! Got a sticky!
Sent from my Incredible 2 using xda premium

+1 For the best idea ever. Great job.

I think you should spice it up a bit I'll add more later lol. Good thread guys.
For the first post you can start it like this:
Rooting your phone (Achieving S-OFF)
Please read and re-read rivera82falcons execellent write up located here:
http://forum.xda-developers.com/showthread.php?t=1219246
Flashing a custom ROM to your device
Please read AgalychnisCallidryas thread on how to manually flash a ROM located here:
http://forum.xda-developers.com/showthread.php?t=1263756
Please note that you don't need to back up every user app with titanium backup, some people only like to backup apps that have data, such as games.
It's also important not to back up system apps (apps that came with the phone). Restoring those apps may cause system failure.
Setting up ADB
Nephron has a full set of instructions on how to set up ADB, you can find the thread here:
http://forum.xda-developers.com/showthread.php?t=532719
Finding the ROM that's right for you
This is one of those threads that may be sensitive to some. I find that finding the best ROM depends on your tastes. When ROMs are released they generally have bugs. Some may be deal breakers, like not having MMS working, or something small like not having a particular tweak installed or an application force closing. You really have to download the ROM and take it for a test drive.
Read through the threads on feedback. Generally, if you see the same bug being mentioned it probably is plagued through every ROM install.
GSM functionality of the phone is important to some, but not most. Generally, if you download a ROM that's based off of the original ROM it should work fine. But if you are downloading a port from another device expect that feature not to work.
Don't be afraid to flash a ROM. The worst that can happen is it will throw your phone into a soft brick (bootloop). Simple way to fix it is restore a backup you made or flash a ROM that you know is solid.
Creating a backup (nandroid) of your device
Your phone at this point must be rooted, and the ROM you are running has to be rooted.
Get Rom Manager from the market. Install the latest recovery that it prompts you with - If you've already installed clockwork mod then proceed.
In ROM Manager:
1. Scroll down to Backup Current ROM
2. Name it what you like, like backup_09192011
3. Let it back up. The more data you have the longer it takes.
In recovery: (You cannot assign names in recovery)
1. Boot into recovery
2. Go to backup and restore
3. Choose backup
To restore a nandroid backup - Wiping data, cache, and dalvik isn't necessary.
1. Boot into recovery
2. Go to backup and restore
3. Choose restore
Useful Applications:
http://androidcommander.com/ great for deleting or replacing apps on the fly. Windows interface, simple to use.

Here are a few more additions:
Replacement camera app for those that don't like to use the stock camera that came with CM 7 or other AOSP Roms.
This Click me Miui camera app works great, just remember to go into the camera settings after installing and select 8mp as the picture size. It can be installed as either a separate camera app or as a replacement to the stock camera.
To install as a add on, just install the apk as a you would any other app. Download to your sd card and install.
To replace the stock camera app, rename the downloaded apk to "camera" (without the quotes) and using root explorer (make sure and select R/W) move the renamed apk to system/app and replace the stock camera apk (first though, make a copy of the stock camera app and add .bak onto the end and store this copy on your sd card, I make a folder named storage so I know where my .bak files are at).
Now that the camera apk is in the system/app folder, the permissions and ownership will need to be changed.
Long press on the camera apk and in the popup menu select permissions,
You will want to change it to look like this:
Read Write Execute
Owner x x
Group x
Others x
After changing the permissions, scroll to the bottom of the popup menu and select "change owner"
You will want to change the ownership so that it reads"
Owner 0 - root
group 0 - root
Select OK and your done. Reboot and you will know have the Miui camera installed.
Wallpapers:
Click me
More to follow later.

Awesome guys keep em coming. I didnt expect this thread to explode so quickly great job guys. Anyonr tutorials or info you guys add i will link to in the op. I will typically update the thread every night around midnight eastern time. Thanks guys.
Sent from my Incredible 2 using xda premium

I always see lots of beginning android users who want to learn Java/xml/whatever to begin building. I made a list of some coding tutorials-they might be of some help to a newcomer who wants to learn.
JavaScript for Android:
http://www.youtube.com/playlist?list=PL34F010EEF9D45FB8
General Introduction to learning Android development:
http://developer.android.com/guide/developing/index.html
General Coding:
http://www.codecademy.com/#!/exercise/0
From around XDA:
making your own boot animations: http://forum.xda-developers.com/showthread.php?t=1096068
ADB workshop and guide, including edited path variables: http://forum.xda-developers.com/showthread.php?p=9959449
How to decompile/edit/sign/recompile apks with APK Manager:http://forum.xda-developers.com/showthread.php?t=695701
how to use APK Edit (apk tool with custom GUI): http://forum.xda-developers.com/showthread.php?t=890199
Editing with NinePatch (.9.png) images: http://forum.xda-developers.com/showthread.php?t=1192207

Great thanks!
Sent from my Incredible 2 using xda premium

Add how to change boot animations and splash screens? (my thread)
Sent from my ADR6350 using Tapatalk

Sure will thanks
Sent from my Incredible 2 using xda premium

oxlong27 said:
Sure will thanks
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Maybe the how to on hulu? I dont think many use it...but it won't take up too much space right and the how to for renting movies from the market (posted somewhere as changing permissions to mu from Su temporarily)
But seriously this is a great job. I didn't expect all this lol. I'm glad we are trying to save our community.
I came to the Eris and it already had a community. We built this one and it needed some leadership. Way to take charge bro
Unlike the Eris all our devs would rather have their own site and that's ok. But ppl haven't been mature about it. I like the devs like tazz and the way he does things. Just the way I am lol.
Sent from my Incredible 2 using xda premium

I never expected it to take off like this either, but im definately glad everyone likes this and will continue to work hard on it thanks again guys. Will update tonight with links to your suggestion
Sent from my Incredible 2 using xda premium

Another thing.
Some questions would be answered of you tried it yourself.
Like "how does this app work" open the darn thing and find put...if you're still lost in the sauce come ask here. Please research and try yourself first.
Sent from my Incredible 2 using xda premium

knipp21 said:
Another thing.
Some questions would be answered of you tried it yourself.
Like "how does this app work" open the darn thing and find put...if you're still lost in the sauce come ask here. Please research and try yourself first.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
yes very good point knipp I want this thread to be informative and educational not a hand holding experience. I have no problem helping anyone that is willing to help themselves but it makes my skin crawl when I see a post that says “wanna root someone please give me detailed instructions" and I have seen a lot of them.

Should I ICS yet? is it safely done yet? worth it?

i'm rocking callulins e4gt 2.9.2 ...
i mean... its good. But i (obviously) want ICS
I've tried using Rom Manager to put the ICS blend on my 4g Touch, it just hasn't worked (i'm assuming that prog is made for the google phones like nexus s.... i think this because it worked great on my nexus s). when i attempt to install, it gets aborted and i have to restore from a backup. I'm wondering if i'm just not going to the right place in clockwork recovery (team rogue, i have avoided touch because it has a brick stigma)
i rooted my nexus S inside out, custom rome out the wing wang, but the epic has proven more difficult. like... get root was cake, but everything after that has proven more complicated. thats why i want some professional opinions. is ICS worth it at this point and can i do it easily?

I personally love ICS and had issues at first. but i been using VeNuM's new rom AnaKonda that just released. So far 24 hours and im loving every minute of it and no major issues. People are saying theres bluetooth issues with the new modem tho but have not had this issue yet.
worse comes to worse just Odin back down to EL29 or something like that.

i'm thinking odin is the better way to do this when i do it.
also, has wireless hotspot functioned well for you?

questions should go in the "Q & A" thread........just saying

kevin_msu said:
i'm rocking callulins e4gt 2.9.2 ...
i mean... its good. But i (obviously) want ICS
I've tried using Rom Manager to put the ICS blend on my 4g Touch, it just hasn't worked (i'm assuming that prog is made for the google phones like nexus s.... i think this because it worked great on my nexus s). when i attempt to install, it gets aborted and i have to restore from a backup. I'm wondering if i'm just not going to the right place in clockwork recovery (team rogue, i have avoided touch because it has a brick stigma)
i rooted my nexus S inside out, custom rome out the wing wang, but the epic has proven more difficult. like... get root was cake, but everything after that has proven more complicated. thats why i want some professional opinions. is ICS worth it at this point and can i do it easily?
Click to expand...
Click to collapse
You do know that Rom Manager can be a brick stigma as well.. I know you may want to get ICS but if you are using Rom Manager one that scares me and tells me your knowledge of flashing may be more on the noob side. If not, I apologize but also if you have read any bricking or rom installing posts in this forum nowhere do you see to use Rom Manager.
Flashing an ICS rom is as easy as the OP says is it. Odin it if you prefer or flash it but please follow the OP's direction and honestly get rid of Rom Manager and learn how to get into recovery, bootloader or flash a rom the good old fashioned way. It may help you out in the long run

Odin back to stock rooted EL29 and then use Calk's full wipe. Flash ICS rom and you're good to go. I'm loving it and the bugs are so few, I can live. You learn to manually manipulate the notification bug. I have had insane battery now that it's settled in. I'm on agat63's tFD02. Even using inverted apps for more battery savings.

it works great but you have to remember its not a final version. still has a few bugs. but worth it for me i love ICS

playya said:
You do know that Rom Manager can be a brick stigma as well.. I know you may want to get ICS but if you are using Rom Manager one that scares me and tells me your knowledge of flashing may be more on the noob side. If not, I apologize but also if you have read any bricking or rom installing posts in this forum nowhere do you see to use Rom Manager.
Flashing an ICS rom is as easy as the OP says is it. Odin it if you prefer or flash it but please follow the OP's direction and honestly get rid of Rom Manager and learn how to get into recovery, bootloader or flash a rom the good old fashioned way. It may help you out in the long run
Click to expand...
Click to collapse
OT--Hey playya, haven't seen you around Xoom...we're on ICS 4.0.4 now. Come and play.
On topic...ICS is awesome on the E4GT! Huge leap IMHO.

I'm on CM9 alpha 2 and it's awesome. It just feels much smoother than gingerbread and much cleaner looking than TWiz. I definitely recommend trying it out, I can't go back to the gingerbread now that I've had some ICS.

Ics safe? Id wait for jelly bean coming out soon.. Ics borked my windows computer! If this is any help to you then id suggest staying away from ics.. .. Or read some of the ics threads and stop being lazy
Sent from my SPH-D710 using XDA

Yea just read the post or look at qbkings review videos they are stable and very good just wait for sfhub to use one click root for fd02

Ics is worth it since using i can't see myself going back to gbroms... Just follow the op instructions on how to install the rom that you choose many issues have been cause of user error
I'm using blend ics 3.2 working good.. Before that i was using blend gb rom
Also you should try flashing with cwm or rogue recovery instead of rom manager.. Its ver easy.
Rogue recover but not the touch screen version
Just do a nAndroid backup first in recovery then wipe everything then use calks wipe everything zip
Then flash rom reboot and let it settle for about 10 minutes before you do anything then do a reboot and your good . Havent had issues

playya said:
You do know that Rom Manager can be a brick stigma as well.. I know you may want to get ICS but if you are using Rom Manager one that scares me and tells me your knowledge of flashing may be more on the noob side. If not, I apologize but also if you have read any bricking or rom installing posts in this forum nowhere do you see to use Rom Manager.
Flashing an ICS rom is as easy as the OP says is it. Odin it if you prefer or flash it but please follow the OP's direction and honestly get rid of Rom Manager and learn how to get into recovery, bootloader or flash a rom the good old fashioned way. It may help you out in the long run
Click to expand...
Click to collapse
i would put myself slightly past noob, but not that much.
Rom manager was great for the nexus... ass for the epic touch.
to clarify, i'm on team rogue CWM and calk. 2.9.2. ; GO launcher.
had several versions of ICS on my nexus... i like the feel of it but every build had its little issues. and the nexus S is just too little. i'm a whore for a glorious, sexy big screen.
i think my biggest problem is i'm not used to the EPIC set up, mem card, usb card, internal. its a mess when i'm trying to get through the rogue menus.

I had epic for 4 months now but never even tried to flash ics yet.As far as i see ics still has some lag even on nexus and probably is a resources hog,i could be wrong but from what i learned ics is like vista and gb is xp.
Plus extra steps needed just to flash it without bricking,once real and stable ics cwm comes out and samsung releases ics ota then i will give it a try because i dont think its as smooth,lag free and stable as my Blazer 4.0 or even gb miui yet.It took many updates even for gb to be as stable as it is now.

well... you make a good point. i just... get the itch. new is always sexy and better in my eyes.
and if the mods want to lock this or move, thats fine, poster was right, this should be Q & A ... but whatev's.. i think its relevant conversation.

just installed the blend after backing up my 2.9.2 GB....
ICS is so sexy. i missed the visuals. I will keep a mental note of the snags, but right now, the ics blue and this big sexy screen were just meant for each other.... so good even the iPeople could be jealous.
quick point, as if i have any, i'm a Mac user, but i boot into Win 7 for anything android. i didn't use Odin, i just put the zip on my sd card, but just... always use windows. whenever i use OSX, things get pointlessly complacated... things just dont work right. Windows? no prob.
so bootcamp it boys!

Seriously CM9 is the best ROM for this phone! I hate TouchWiz with a passion. This is how Android SHOULD be! I haven't had any issues with Alpha2, I consider it stable. Once you go CM, you never go back.
http://forum.xda-developers.com/showthread.php?t=1563658

atomb said:
I'm on CM9 alpha 2 and it's awesome. It just feels much smoother than gingerbread and much cleaner looking than TWiz. I definitely recommend trying it out, I can't go back to the gingerbread now that I've had some ICS.
Click to expand...
Click to collapse
GB is butter compared to ics at least till we get an official release. ICS still has a lot of lagginess scrolling thru screens and app drawer, dont experience any lag on GB roms. I will admit ics roms are improving and very fun to play around on.
Sent from my SPH-D710 using xda premium

I disagree. Though mortal kombat is a good game, donkey Kong is the best game ever

[please sticky] Gonna flash an ICS build? Check here before you brick yourself!

Due to an error in the kernels we've been flashing to our devices, a lot of users have been experiencing a FULL BRICK. Full brick meaning you may as well play golf with your phone, it's dead.
I've been told there is a fix, BUT YOU MUST NOT FLASH ANYTHING FROM CWM. The bug is originating from flashing a corrupt kernel from CWM or mobile ODIN.
Here's a cut from the article:
Thanks to XDA Elite Recognized Developer Entropy512, we have learned that most devices that are receiving leaks are at a very high risk of never waking up after a flash. It turns out that there is a major bug in the leaked ICS kernel that affects the /data partition in the eMMC chip, which apparently gets corrupted during certain operations such as wiping and flashing. This was originally believed to be affecting only operations performed in custom recoveries such as CWM. However, there have been reports of hard bricks being produced from the flashing from stock recoveries as well. The affected devices are:
All Epic 4G Touch (SPH-D710) ICS leaks
All Galaxy Note (GT-N7000) ICS leaks
The AT&T Galaxy S II (SGH-I777) UCLD3 leak – and probably all others
Korean SHW-M250S/K/L official releases and any kernel built from their source
Entropy and other devs have posted several warnings scattered throughout the site, in which they explain in detail what is happening. Our suggestion is that users should stay away from flashing ICS from leaks until the bug in the kernel has been completely fixed—unless of course, you are looking to hard brick your device. Remember, this is not something that can be resurrected via Unbrickable Mod or even via JTAG, as this is a firmware error in the eMMC.
Click to expand...
Click to collapse
Just like you, I don't wish to brick my E4GT. xST4T1K has posted a comprehensive guide to find your options on removing the affected ICS kernels from your device, and hopefully resulting in you not bricking the crap out of your phone. Go check this page: http://forum.xda-developers.com/showthread.php?t=1525495
I DO NOT take credit for finding this bug, credit goes to Entropy512 and XDA TV's EGZTHUNDER1 for alerting me of this bug. I have safely removed the affected ICS kernel from my phone and custom builds, now it's your turn.
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Please, once again, GO TO THIS PAGE and explore the options of returning your phone back to dry land.
As a reminder, DO NOT FLASH ANYTHING FROM CWM OR MOBILE ODIN.
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Safe flashing, XDA members.

Maybe this sticky from the general forum should just be moved over to here.
http://forum.xda-developers.com/showthread.php?p=23149990
Sent from my SPH-D710 using Tapatalk 2

Weve kinda known this for a while now since the February leaks... js. Still, safe flashing everyone lol.

first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Edit: just to clarify... Wiping cache/dalvik cache from stock or cwm repacked recoveries is safe.
The issue is Wiping Data (Don't use the option)

bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2

bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
In a world where users flash before they research, common sense doesn't have a stronghold.

DjKurt said:
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
The issue is from Wiping Data from stock and cwm recoveries, you can wipe cache and dalvik with no worries. Those don't mess with partitions.
Sent from my SPH-D710 using xda premium

You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.

scarmon25 said:
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
Click to expand...
Click to collapse
That sucks, sorry to hear that...
I was one of the first to test cwm repacked recoveries for agat63 since FE10 and have flashed 37 times to and from different roms and done backups and restores countless times and I've been fine.
I haven't been fearful of any bricks since I tested these repacked kernels.
Hope it does get figured out once source hits though.
Edit: btw what kernel (with or without cwm repack?) did you brick in?
Sent from my SPH-D710 using xda premium

It was back when CM9 first was released. I was using the el26 cwm kernel to flash. I was on one of the ice builds I can't remember. I odined the kernel cwm combo el26 and then ran a format all and flashed cm9 and ggot the blue light special haha
Its all good though. I have read alot of info in this including the one mentioned. One thing that was mentioned in one of them is that the bug had been triggered be deleteing a large file off the internal memory. That worried me. So I've been weary of ICS builds since. The fact that the issue seems to be that info getting wrote to a certain block of the emmc has me worried that it could be triggered by more then wiping of flashing. I have ran agats ROMs and I have to say he seems to be doing something right. Whether it is because he is staying TouchWiz or what for some reason his users seem tto not have many issues. But just keep in mind that it may not just be kernel/recovery related.
Safe flashing is key and I never want to see someone brick. Just be careful in whatever you do.

Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.

xST4T1K said:
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.
Click to expand...
Click to collapse
I couldn't have said it any better, my friend!
As far as those who've bricked their phones, it is truly unfortunate.. Google themselves has been brought into light on this situation, and are working to correct this issue in the kernels that they've been adding in with their firmware.
As far as your useless phones go.. Try filing for an insurance claim, I guess! NOT my professionally recommended advice.. But IF someone were to have stolen that useless phone of yours and you were to never see it again.. Well, who am I to say that's not a reason to get a replacement from asurion! Lol!

By the way, xST4T1K.. Bumped you thanks count up a little more.
Thank goodness I ran into these threads before I decided to flash anything else.. Been running a solid ICS rom for a few weeks, now. But I'd rather get back to safe land on GingerBread Island and use Apex Launcher. Wouldn't care for the huge difference in the settings menu. Would miss the lockscreen, though.. Not aiming my finger at an unlock tab has gotten habitual!

crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA

elliwigy said:
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I would never want to scare anyone away from trying these great builds on XDA. What I do want though is to make people aware that no matter how many tines you flash something. Always treat the flash your about to do as if it was your first. Sometimes we get to comfortable in what we're doing. We have to remember that this is a pretty expensive device and if something happens you may be buying a new one outright. Not everyone has insurance or can throw out that kind of cash. Do safe flashing practices and make sure you read the OP. When flashing leaked software make sure to flash from stock or the most current OEM released build such as EL29 in this case. Verify the right files are in the right slots of Odin. Make sure you're flashing files in the right sequence when in a custom recovery. Thing like that. I believe in the openness of android and never want to see anyone say they aren't going to flash something because they are scared. With the right ammount of reading and precautions. There is no reason to be scared.
Just for example. And this is not an exaggeration. Between this phone,my wife's phone, my last phone, my wife's last phone, and numerous friends phones. I have well over 200+ flashes. I have only had one actual brick. And that brick was because I got too comfortable in what I was doing. So, odds are if you take tthe time to do it right. You will succeed. Also.

i cant figure out why this is not locked yet....

i agree scarmon.. you said it better than i could.. if i wasnt tech savvy and i read the op i would have been scared away.. it says in all caps not to flash in cwm and says many have experienced bricks.. it can be worded differently but its freedom of speech.. when the initial leak came out and we had rogue ics kernels and the LOSt kernel we werent sure why people were having bricks until we figured out what was causing it.. we've known this for a while and since then hard bricks have dropped drastically.. and every single developer insisted not flashing from ics kernels and every rom has a disclaimer in the op for this reason.. only bricks ive read have been user error for a while ie. unplugging device during odin flash or battery dieing during mobile odin flash etc.. plus this is in the dev thread.. right now most people come here for ics roms since thats what devs are working on.. and many have gone safely back to gingerbread many times.. the ics roms have hundreds of thousands if not millions of hits and how many posts about hard bricks?
Sent from my SPH-D710 using XDA

I've been flashing ICS roms since FB17 and haven't had any bricks. I've been making sure to only flash things from EL26 and it's been smooth sailing.
Now I'm running the most recent AOKP and it's running very well.

Your credit is pretty thin too. Entropy is a big name in this issue but him and some random dude that apparently notified you very very late about this issue doesn't even cover half of it.
The front page news on the issue was pretty late as well. Just lets the general population know about it.
ijoshv2 said:
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Click to expand...
Click to collapse
Its things like this "While I have heard" that is the problem with your post. That and begging for a sticky, talk to a moderator if you feel its important.
Flashing a non-ics kernel through ODIN does not fix any issue. Flashing from a safe Kernel avoids the issue, If your on ICS flashing the GB Kernel from ODIN would be the safe method. Gingerbread as far as we have known and hundreds of flashes per person per hundreds of phones later. No one has been known to trigger the eMMC firmware bug though gingerbread. So yes flashing from a Gingerbread kernel as we have since the phone came out is the safest known way. You don't need anyone to tell you that.
You come in and say "Do not flash anything from CWM". This is inaccurate it suggests one can not flash from EG30+ CWM which has never been a known danger. Obviously EK02 would be more popular due to supporting full modems rather than patch. EL26 was the last to have true CWM which is why EL29 Rogue is less often suggested.
ijoshv2 said:
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Click to expand...
Click to collapse
The danger is not in flashing ICS. The unknowing user is going to be flashing ICS from EL29 which is safe. The danger is after they are there, and they try a factory reset, or install a CWM or Unlocked Recovery Kernel and flash something, or flash an update.zip through stock recovery. Yes they need to know, the information should be accurate however.

If anyone wants details of this emmc firmware bug, there's some really knowledgeable people in this thread.
http://forum.xda-developers.com/showthread.php?t=1644364
The info is very detailed, but these are the individuals to watch. OP if your serious about helping our community with this emmc bug, I hope you join in that conversation instead of asking to sticky this thread.
Sent from my SPH-D710

Why is it that ROM developers just can't seem to make ROM's that can boot up properly

I just can't figure it out. Every Jelly Bean ROM I have used so far has had the same problem. After using the ROM for a few days, and I decide to do a quick reboot to refresh the system, after only a few times doing this ever, the phone will either begin to boot-loop, or most of the time get stuck at the Google logo splash screen. Every time this happens I am forced to open the Toolkit and flash back to stock, and then reflash CWM recovery and install a different ROM and try again. Is it just me that is having this problem? I don't understand how it is so difficult for a ROM developer to create a ROM that can successfully boot up the OS every single time. Someone please give me a straight answer to this, because I can't figure it out.

If you are talking about 4.1 yeah I have noticed all of the ones Ive tried do it, something to do with the way the partitions are handled on jellybean.
It doesn't actually get stuck on the Google screen if you wait it out it'll eventually boot (usually 3+ mins here but I've read can take up to 10 minutes) worst I've had to do is clear the cache not actually reflash the rom. Now the OTA is here for GSM once they build from them instead of the dev version and AOSP they should get better same for CDMA whenever it comes

So you blame ROM devs?
Shame on you.

SocialReject said:
So you blame ROM devs?
Shame on you.
Click to expand...
Click to collapse
It's very frustrating for someone who is new to this. I have only very recently started installing custom ROM's. I had no idea who is to blame, although atleast now I get an idea of what the reason for this problem is.

Regardless of whether or not the problem you are having is caused by ROM developers(by the way, it isn't), don't act like an ungrateful douche.

WOW!!!

Touche. Ungrateful sucks. Glad you're learning something, though, I hope.
Sent from my EVO using xda premium

Definitely the wrong way to go about getting help... The fact that you just started flashing ROMs is the issue. You think the Dev would upload the ROM if it wasnt booting? I wouldnt

No way I would be ungrateful to a dev. This is time consuming **** and I didnt do anything but download and compile the source. Must take much more time to add in tweaks and theme them and all the other stuff they do

dude really???? Wrong way to do this dude....and its you messing up I have been on a jelly bean Rom and have never had a boot loop, I have flashed multiple roms and mods with these roms and have never had a boot loop read the instructions and wipe your cache also don't use reboot apps,,,,, if you want a better Rom take your computer sync your repo and build it from source your self and stop whining
Sent from my Galaxy Nexus using Tapatalk 2

To be able to learn something first you need to throw the arrogance into the dust bin.
Developing something is not everyone's cup of tea. If you are not happy with a particular ROM keep on trying the others but first give the developers a chance to rectify the bugs by reporting it to them.
Starting a thread like this will neither help you nor the developers.

My sig.
Post 2.
That'll show you how to install a rom, to make sure you're doing it correctly.
Enough bashing, guys...he's new.

Stop being lazy and dirty flashing roms.. Start clean, Wipe everything , only restore user apps via TB.. or just stay away from installing kernels and keep the stock one
You can't blame the Dev because the rom won't boot.. 9/10 its the user problem

Are you using the proper version? Only time I loop is because I skimmed the thread and didn't pay attention, tried acting smarter than I am, or messed with things i shouldn't have. Research before...avoid potential disaster later. And in either case, I quietly restore and nobody knows about it.
Android is updating...

New to GN2

Hi folks,
Just decided to retire my old S3 and when looking for a new phone my main requirement was to get a good DAC built in without breaking the bank or renewing my contract, ended up with the Sprint Note 2. Naturally I was excited but quickly put off by the stock ROM so I decided to root/flash, etc. This is what happened so far;
-Rooted with newest TWRP and root verified on stock rom (followed NK2 instructions)
-Made the big mistake of flashing now without backup, after trying a couple of roms I kept having the same problem (phone gets stuck in load animation indefinitely regardless of rom flashed)
-Gave up on custom roms so I flashed a rooted stock NE2 rom and phone turned on wooohooooooo
-But wait, no network connection, no voice or data, tried to flash modem zip file from http://forum.xda-developers.com/showthread.php?t=2139889 but it keeps saying zip is corrupt, redownloaded & recopied to SD with the same result.
Now I have a working phone but not so working since I can't place calls. What went wrong? any help is very very appreciated.

Phone works after flashing Alliance ROM but somehow now TWRP recovery is gone and phone is UnRooted which is less than ideal but it works nevertheless...
Now before I go off wasting a whole day flashing & waiting for battery to recharge can anyone please point me in the right direction?
I need to figure out the following:
-Root method that works, I'm on Alliance NE2 now
-Which recovery is best recommended for current ROMs?
-Need a kernel that enables audio features like Direct DAC & upsampling
-ROM that actually works with said Kernel and functions at least 90% with wifi tethering etc.?
Surprised it's this difficult with this phone coming from the S3 which took me no more than an hour first time rooting/flashing.

hhmmm 63 views and nobody able to help?
Currently stuck on this ROM, which is horrible because maps doesn't work well, pandora crashes, UI fc's left & right and to top it off the phone is sluggish in every way possible.
Unified Toolkit not working, drivers installed properly, ADB visible in device manager, debugging enabled yet phone can not be seen by Toolkit.
I really don't want to switch back to my cracked S3 but I'm not left with many options considering my note 2 is barely usable now.
Is anyone out there... there.... ere... ere... ere.....
lol seriously feeling like I'm the only person left in these forums.

Use odin to flash recovery but make sure you uncheck reboot option. Once flashed remove battery and while doing the recovery hotkeys insert battery. Now wipe everything and flash another rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app

here's what I've done now;
-Flashed newest TWRP via Odin
-Wiped & flashed Rwilco12's NE2
-Rebooted and phone booted yipeeee
-No cellular connection, crap phone i hate you
-Rebooted to recovery & flashed NE2 Modem
-Rebooted again and recovery is now gone
So either I get root but can't use the phone as a PHONE
or I loose Root and get basically the same POS I started with.
I've given up on eye candy, custom rom, custom settings and my expectations have dwindled down to just ANY ROM + Root + Tether yet that can't even be accomplished. I know I'm doing something wrong but at this point I'm over 10 hours into trying to figure this out and have no idea what to do next. Anything?

Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM

oceanisbleu said:
Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM
Click to expand...
Click to collapse
Twrp 2.8.6.x works for almost every rom but you will find most users recommend philz. I as a wantabe dev will suggest philz 6.0.7.9 expect in a few rare cases with aroma installer needing twrp. Personally I have philz 6.9.7.9, twrp 2.8.6.0, shift dual recovery and devil dual recovery zip on my external sdcard. This way I always have what I need depending on what I am doing.
All this info along with solutions to every problem is here on xda already. It may take some time to find everything but really the users should do his homework before doing anything to the phone anyways.
Also if you read the rom thread (Alliance) you would know why you lost root. Simply put you updated supersu app and binary. It is a known issue on every ne2 based custom rom for this device.
Sent from my GT-N7105 using XDA Premium 4 mobile app

Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!

oceanisbleu said:
Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!
Click to expand...
Click to collapse
I will read every page myself even if it takes a week. You say reading it is more trouble than it is worth which is why you had that issue with Alliance. Same goes for your omni issue.
If you don't want to read that is up to you. A google search will normally help with common issues. I dont mind helping but you have to help yourself first. Not to be rude but I wont answer your omni question because you have not looked. Ypir issue is the number 1 issue omni users have.
Sent from my GT-N7105 using XDA Premium 4 mobile app

won't argue with your opinion as I have my own

oceanisbleu said:
won't argue with your opinion as I have my own
Click to expand...
Click to collapse
I see you edited that a bunch. I dont mind helping. I have been helping so far. Now about the omni gps. I only know on possible fix bit it is a pain.
1. Flash stock/stock based rom
2. Get gps lock
3. While locked and in app reboot to recovery
4. Wipe and install aosp rom & gapps or restore aosp backup
Then you might get gps lock.
Sent from my GT-N7105 using XDA Premium 4 mobile app

reading back I realized some clarity on my part would have been helpful rather than make a general statement.
So the issue with reading 25, 50 or a 100 pages isn't by choice (may have sounded arrogant the way I said it at first) but I work 50 hrs a week, I do work on my home myself, I rent out rooms to students, I have other projects going, etc. so a very very busy lifestyle. Not to mention the daily crap that tends to come up all the time the moment I get home from work so in short, I really can't afford the time to read in that much detail whether I want to or not.
Regardless, by no means am I lazy when it comes to research, notice my post count? yet I've been here since 2009, and since 09 I've had at least 8 different phones (windows phones too) I really try to figure out everything I need on my own so in this case I spent 3 days working on my initial issues, after that I posted this thread which was 8 days ago and had it figured out and finished yesterday (a few bugs aside), that's easily 10 days I spent at least an hour or two a day working on one thing. Surely you understand how frustrating that must begin to feel.
Regarding my last reply, haha I had to delete most of it because I realized I was beginning to take my frustration out on you when in fact you're the only person who actually offered help (still very very thankful) and to top it off I screwed up the rest of the reply when I mentioned GPS, got that mixed up with the topic we were actually discussing (losing root) this happened because I was reading through the GPS issues before I got to your reply and yah mixed it all up, so again apologies for the lack of clarity and thanks for your last reply, it's more straight forward than all the comments I found on that issue.
You won't have to explain anything else I promise haha and I did all this just now but want to verify I did it correctly so I don't come back to it again. After flashing ROM/Gaps/Kernel & supersu, never update supersu after running rom correct?. Root verified as of 30 minutes ago.
GPS, this one is a big big deal because I use it for work but I had already found the answer pretty quickly as I had read something about it before I even flashed Omni.

I do know how frustrating it can be. I have been in worse spots and had to create my own fixes which I have shared here. As far as time goes I understand that being a parent of 7 children.
I am still active here and always willing to help others long as they help themselves also. We seem to have gotten off badly. While some of your post seemed you had done nothing to help yourself. So lets forget earlier stuff and move on.
Yes you seem to have all the steps correct.
FYI android 5.0-5.0.2 all have gps issues but there is a flashable fix. Most new 5.1.1 builds have gps fixed.
If you run into any issues feel free to ask but include steps you have taken to fix the issue. The more you tell the better help you can get. Plus others wont think you are wanting to be spoon fed.
Sent from my GT-N7105 using XDA Premium 4 mobile app

haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn

oceanisbleu said:
haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn
Click to expand...
Click to collapse
Well I personally have a Frankenstein device. It started out as a sprint l900 but I removed the sdcard/sim board and put a n7100 board so I can use a cricket sim. This causes issues with calls on aosp so I run modified t0lte (n7105 international) roms.
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Sent from my GT-N7105 using XDA Premium 4 mobile app

jlmancuso said:
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile, I believe Phill'z CWM download link is down as well.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Click to expand...
Click to collapse
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:

oceanisbleu said:
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:
Click to expand...
Click to collapse
Well the donation would be nice but understand when you hit my donation button/link it will take ypu to the Red Cross donation site. That is not a mistake. I personally dont take donations and feel of someone wants to donate something it should go where it can be used by those who need it.
Sent from my GT-N7105 using XDA Premium 4 mobile app