Why, in thors name, do people keep posting here?! :banghead: sh1t, I just did too, lol

Sent from my EVO using xda premium

Since this is now the last page of the thread (as of this post...)
Just so anyone knows this conversation has offically moved to:
http://forum.xda-developers.com/show....php?t=1851912


Here is a summary of frequent questions to this forum:


Q1: How do I get this JB Rom?
A1: As of Now the link is in the first post of the continuing thread, and is being updated by Deck:

http://forum.xda-developers.com/show....php?t=1851912


You can find up the minute updated Links in the IRC Channel (as per page 149 of the thread):

http://webchat.freenode.net/?channel...-4g-lte&uio=d4


Or a list of the history of the IRC links here (as per page 201 of the thread):

http://irc.netsplit.de/channels/deta...e&net=freenode


Q2: Is <name feature> working?
A2: A list of known issues is in the first post of the continuing thread

http://forum.xda-developers.com/show....php?t=1851912


There is also (as of this post and historically) a link to "known issues/progress" in the IRC:

http://webchat.freenode.net/?channel...-4g-lte&uio=d4
or
http://irc.netsplit.de/channels/deta...e&net=freenode


Q3: Proximity sensor issues....
A3: There were some issues for some users on some builds --- but users had these issues on sense too.
Most often, removing any case you had on the phone, or verifying your screen protector was cut properly to not cover the sensor would
fix or at least minimize the issue.
Holding your phone up directly to bright light was known as a quick one time fix to get the screen to turn back on.
Also under settings: Accessibility menu: select "power button ends call." Which helps with the primary irritant for most.


Q4: 1x/3g data issues...
A4: Most can be fixed by switching to airplane mode, and then turning airplane mode back off.
This can also be caused by a bad download.


Q5: Having issues flashing this rom...
A5: First off make sure you check the MD5 of the downloaded file against the MD5 listed at the download site. One easy way to do this is using ES File Explorer: Long press the downloaded file, choose Properties, press Show Checksum, check MD5, click calculate


Another thing that can cause this is the Firmware on your phone. If you accepted an OTA (over the air) update, or you got your phone recently it may have updated your HBOOT. (as of this posting that would be HBOOT 1.15. Also as of this posting there is no easy way to revert to HBOOT 1.12) Below are a few quick (summarized) possibilities, if you need more help search the thread --- answers are there, before you post in the new thread or ask in IRC.


1. My HBOOT is 1.12, but I haven't rooted or Gone S-OFF yet.

-- You can go S-OFF using LazyPanda (see IRC for links) to go S-OFF, however it will mark you phone as Tampered --- There are posts in other threads on how to revert to stock non-tampered with a stock RUU rewipe if you ever need to (google is your friend).


WHY do you want S-OFF? -- it allows flashing all parts of your phone including Radios... there are ways to do it S-ON, but they are a pain.

Once you are S-OFF you can use TWRP (see IRC for links) to flash this rom.


IF YOU PREFER TO STAY S-ON -- It is recommended you avoid HBOOT 1.15 for now (in case you change your mind and WANT to go S-OFF --- as of this post LazyPanda doesn't work on HBOOT 1.15) You will need to flash the boot.img through fastboot before you flash the rest of the rom (search this thread -- instructions are there)


2. My HBOOT is 1.15, and I cannot use LazyPanda to go S-OFF (or you want to stay S-OFF)
You will need to flash the boot.img through fastboot before you flash the rest of the rom (search this thread -- instructions are there)


Q6: Any other questions

A6: Search through this thread -- AND through the new thread that's what the search tool is for, before asking in the new thread or on the IRC


Hope that helps.

Closed until op lets me know he wants it open.