yashsingh1/xdaforums huggingface dataset:
[HTC One X] Guich:
You can take the Unlock_code.bin from htcdev, follow the steps and you are done.

However, when you go to flash ARHD, you lost all your apps and data (don't the sd) and you have to download it :)
[HTC One X] tomascus:
Don't worry, HTC have made it so that it's almost impossible to screw up your phone
[HTC One X] mrxclusiv.au:
welp its screwed stuck at white htc o1e screen - thanks for the help greatly appreciated :crying:
[HTC One X] Alex240188:
Re: [Q] htc one x revolution HD 9.40 -&gt; rev 18.1

Did you flash the boot.img for arhd18 after installing it.

What point in the process did you get stuck at.

Relock - fastboot oem lock

Ruu mode - fastboot oem rebootRUU

Flash firmware - fastboot flash zip firmware.zip

Flash firmware again.

Reboot into fastboot

Unlock - fastboot flash unlocktoken unlock_code.bin

Flash recovery - fastboot flash recovery name of recovery.IMG

Flash boot.img of new ROM - fastboot flash boot boot.img

Boot into recovery

Copy new ROM and install
[Captivate Q&A, Help & Troubleshooting] dragonflame8712:
i have recently installed remICS-jb - 4.2.1 rom on my captivate .. and m loving this rom. but the thing is, it doesnt come with google play store installed.. so yes, i tried to flash Gapps but it gets stuck into bootloop . so i had to clean install the rom again (factory reset, wipe, install) ...

i installed many playstore.apk (every version) but they just start and then force closes (no dialouge is shown... it just closes itself after like 2 seconds) . i even copied the playstore.apk in /system/apps but that didn't help. i even rebooted many times after installing the apk.

So, finally i figured the only way left is to flash it via CWM . is there any google android market.zip file to flash via CWM ? if not, please give alternate ways.
[Captivate Q&A, Help & Troubleshooting] dragonflame8712:
oh... noob me. i was flashing older version of gapps.. just downloaded 4.2 updated version of gapps and flashed. its all good now :D
[Captivate Q&A, Help & Troubleshooting] JCibrianS:
Hey... is there some tutorial for install gapps? I installed cyogenmod Jelly Bean 4.1.2 and like your ROM it does not have google play.

Please help.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Grab their specific Gapps and flash them in recovery.
[AT&T LG Optimus G] xsaqzw:
So, I understand the process of it.. but not really as to why.

Are you able to install anything N4 you want? Roms, kernels, etc? Or is it just the N4 converted roms from the dev section?

Is everything working? I've read mixed reports.

Thanks,

Nicholas
[AT&T LG Optimus G] Dr0!dFreek:
The lgog and the nexus 4 are fairly similar phones. The reason we can't run nexus 4 ROMs is because some differences in the partitioning. Flashing the modified tot for the conversion converts your partition layout to that of a nexus 4 and installs the stock nexus 4 rom with an unlocked bootloader.You are supposed to be able to use nexus 4 ROMs and kernels. I've flashed like a 3 different nexus 4 ROMs

The problems that you might run into are with lte but that is fixable.

There is a fix for capacitive keys , nfc , and the external SD card which I were originally not working. The fix is a ROM so if you want all those things working you have to use it or properly patch another ROM with some of its files. There is also a flash able zip that but it is only compatible with certain ROMs.

The only "issue" in not having the full internal SD storage. You only have 8gb in comparison to 16gb but having large external SD should help storage wise.

However, apparently the conversion breaks the camera for the jelly bean stock port from the lg e973http://xdaforums.com/showthread.php...an LG-E973/1/5/0 CANADA / ATT / INTERNATIONAL. Camera works fine on every other stock based ROM when you convert back but apparently not on the jellybean port. It has not been proved but it has many claims supporting it. My camera does not work and I have converted.
[AT&T LG Optimus G] jimi_pooh:
Dr0!d thanks for explanation. I have a question. Ever time I come back to stock I get an encryption error. What am I doing wrong?
[AT&T LG Optimus G] Dr0!dFreek:
I got that error once. lgpnst doesn't really wipe partitions correctly before flashing ROMs. NownI wipe all of my partitions in recovery and then fastboot -w in command prompt before flashing back to stock . A data and cache is probably all that's needed but the flashing process takes a minute and I haven't had time to try it out. I think there is also something you can do at the encryption screen . it says like reset phone or something I think I've read that if you keep hitting it it will reset your phone or something idk sorry.
[AT&T LG Optimus G] jimi_pooh:
Dude thanks a bunch. I'm going to try wiping like u suggested
[AT&T LG Optimus G] tdnick:
That's what did the trick for me when I came back. Good luck

Sent from my Nocturnal'd Optimus G
[AT&T LG Optimus G] ph0dacbeit:
I tend to go back and forth doing the N4 conversion and back to At&t stock. I get this fail to encryption screen,some times after I LGNPST back to stock. Pressing the "reset phone" repeatedly never does anything for me. What i've been doing is when this happens is, I'll shut the phone down and press the Vol down and HOLD first and then hold the power button. It will bring you to some kind of factory recovery where it says "HARD RESET MODE" Just press the power button to confirm the reset and it essentially just wipes the phone and brings it back to stock.

Hope that helps!
[AT&T LG Optimus G] xsaqzw:
Thanks so much man!

Are there going to be any AOSP roms coming out native for the LGOG soon? If so, I'll hold off on the conversion. But if not, then I think I'll go ahead and do the conversion and flash Ginsex or one of the other JB ports. Are the cameras working on this if you flash the fix?

Nicholas
[AT&T LG Optimus G] Dsmforlife92:
Yes there are a couple of people working on aosp ROMs right now just give them a little more time
[AT&T LG Optimus G] peaceburn:
I know some people are against the conversion as such, but I think in the long run, this will be the only benefit of this phone - I'm expecting LG to do its thing where they don't provide any updates once their newer phones come out.

And here comes the nexus4 conversion - we'll be able to advance our phones thanks to the actual updates for nexus4 that google and the community will provide. Probably we'll lose LTE at some point when the modems will no longer be compatible with newer android versions.

My previous phone, the captivate was in a similar scenario - slightly different from the international galaxy s, but the devs worked out a set of patches to be applied against the galaxy s roms to make them work on the captivate and the captivate has long lived since, becoming one of first phones to get cm10.1 nightlies and enjoying more than a few 4.2.1 roms. It's definitely slowing down, it's been more than 2 and half years since the phone launched and people have moved on to newer devices.

So if it wasn't for the nexus4 conversion, I wouldn't have jumped on the lgog for my upgrade - the phone shipped with ICS, might get a 4.1 update eventually, but I don't expect LG to follow up with further stock updates after 4.1.

I know there is speak of AOSP roms coming to the LGOG, and I'm really thankful for the all the devs who work bringing these, and hoping we'll even see official cm10.1/cm11 :) then probably we won't need the conversion at all, but if it doesn't happen, or devs give up on the lgog the conversion will be the only path to newest android.
[AT&T LG Optimus G] whiteguypl:
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.

There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
[AT&T LG Optimus G] C2fifield:
While I personally don't really agree with the first comment (I feel as though stock LG development has its place and there are dangers to the conversion), I definitely agree with the secrecy, on my old inspire I knew just about everything the devs were working on, what was and wasn't working, as well as which problems they were facing. With the LGOG I feel like I'm in the dark quite often.

Sent from my "Canadian" LG-E970
[AT&T LG Optimus G] SnowLeopardJB:
This phone is already essentially a N4. We are working on methods of porting the nexus 4 kernel to our phone that do not require any modifications, so we will always be able to run anything the n4 can run anyway. Basically, there will be a longer wait because this is harder to do, but it will be better in the long run, as we fully understand what is going on.
[AT&T LG Optimus G] whiteguypl:
Accept that the problem still stands with a ported kernel doesnt it? You guys leave and we need a new kernel and are s.o.l. . Also please dont take what im saying as any kind of insult, its not. Just looking to understand better.

Though i guess the same could be said for a perfected conversion is something in that needed changing.
[AT&T LG Optimus G] Dr0!dFreek:
There is now a fix for jelly bean rons after converting back to stock

http://xdaforums.com/showthread.php?t=2146816

[FIX][Re-stock after N4][E970] Camera Fix for JB !!!ALPHA!!!
[AT&T LG Optimus G] SnowLeopardJB:
Of course both would need kernel changes to make everything work 100%. Either way, someone would need to fix things. Fixing the kernel to boot with full stock may take more work, but I would consider something that does not require modifying the non "normal" partitions of the phone to make work better than something that modifies the base bootloader of the phone.
[AT&T LG Optimus G] dvhexer:
You're so right about the veil of secrecy!
[AT&T LG Optimus G] sk8erwitskil:
HA! thank you! i HATE this stupid secrecy thing that alot of people in this community have. i have also never experienced anything like it. it really keeps things from expanding. people in here know that they run the risk of damaging their phone anytime they flash anything. the reason these people are keeping things secret is because they think that "dumb people will brick their phone". i have personally been running a solution to running n4 roms/aosp stuff without having to do any conversion for multiple weeks without any harm to my phone. i have a completely working cm-10.1 rom with full internal (16gb), full access to external, cap buttons, led lights, LTE, etc. everything works but i was told by members of team codefire that if i release it then i am an effing moron.
[AT&T LG Optimus G] Dsmforlife92:
Who cares what team codefire thinks just keep doing what you are doing and thanks for everything can't wait to try something out. If you need more/any tester just let me know I have best buy insurance so not worried about bricking.
[AT&T LG Optimus G] Shelnutt2:
I'd like to just chime in and say 1) one person said you'd be an effin moron and he is far from the whole of team codefire. His words and actions don't represent the team as a whole, and his words were uncalled for. He could have said things in a nicer way. 2) The cm-10.1 you have relies on a testing version of freegee that was developed, but since abadonded. The reason it was abadonded was quickly we discovered that it bricked sprint radios. We had 4 people, including myself, loose radio. Thus this new freegee method was dropped.

We are instead working with 3.4 lge kernel source. I've also narrowed down what I believe the issue is on mako kernel not booting stock, to be the lge power management vs caf/mako power management. We'd probably have lge 3.4 working by now, but all of us, sk8 included jumped on using mako kernel once it was discovered about this slightly different freegee method. However like I said, after we bricked 4 radios on sprint, we didn't expand the testing any further and stopped.
[AT&T LG Optimus G] dvhexer:
Wow :) But seriously, they don't own the forum and are not (demi)gods. I don't know what you and houston did to make mako kernels boot. I bought this phone after I saw the thread about the conversion and converted in couple of hours after I've got the phone. That was my intention to have N4 firmware and I don't even know why stock bootloader chain can not/will not boot mako kernels. Still, although I'm not coming back to stock, I'm curious what was the problem and what you did to solve it and I will appreciate if you give me any information.

And I'd like to ask you, don't be like some other people, give credits to people(me :D) who worked on things like ext_sd/nfc/capacitive keys(of cause only if it's based on my work)
[AT&T LG Optimus G] sk8erwitskil:
i completely understand where you are coming from with the whole sprint phones getting bricked. but i was never interested in deving for sprint phones so that never crossed my mind. i have an att phone and ran that method for a while with no issues. i get the benefit in releasing things that work for all devices at once but its not imperative. if some variants can have a working solution now that works great then why not release that?

and how is anybody supposed to know what you guys are working on when you dont tell anyone? this is the first ive heard of what you think the issue is in the kernel. it sounds like youve been working on it for a while yet you havent reached out to anyone but your few close devs you work with im assuming. i would love to help but am limited to working on what i actually know about. the reason i jumped to the partition update method was due to that being the easiest method at the moment. there are alot of talented people in this community that can help speed up the process of getting a native aosp solution if given the oppurtunity to help. one of those people being dvhexer. i had never even heard of him until he released that n4 conversion rom with the fixed cap buttons, ext sd etc. and if that n4 conversion was never released (like you guys had wanted) then we still wouldnt have those issues fixed. but now we have those issues fixed thanks to dvhexer. the n4 conversion has only been a benefit to this community and i am thankful for rohan releasing it.

that said...i am all for having a native aosp solution and i respect your work. i just feel like this community needs to be a bit more open.
[AT&T LG Optimus G] C2fifield:
Sk8, while I completely understand to withhold things to protect those that don't know what they're doing, I still am a pretty firm believer of the, "you know the risks, your fault," so I know my opinion holds no gravity, and you really have no reason to even care what I say, but I'd just say do whatever you feel is best. We all greatly appreciate all the hard work you do (as well as all of the other developers as well as team codefire for that matter) but I think developers shouldn't have to be responsible for those "dumb users." Hell I choose android so I can feel informed and know everything about what I can do to my phone, despite what the carriers decide./rant

TLDR: Do whatever you feel is right sk8.

Sent from my "Canadian" LG-E970
[AT&T LG Optimus G] blenkows:
I completely agree about the secrecy thing. I fully understand why the devs aren't releasing the builds just yet, but I never really understood why there is such a huge secrecy about keeping the public updated. I'm not talking like exact ETA's here. But I mean like telling them what problems they're running into. In fact, people on these boards are knowledgeable and might be able to help. :) (not me but smart people)

____

Sent from my LG Original Gangsta
[AT&T LG Optimus G] drwario:
I'm no developer. At the same time I'm not a dummy. I like to tinker. But everything is so top secret. Most seem so uptight. I think broken or not. Things should be released. That is how the community fixes things. These behind closed door shenanigans are counter productive I believe.
[AT&T LG Optimus G] Shelnutt2:
In all honesty I don't think most of us keep many secrets, besides stuff in private testing. I think it's more we just don't talk alot. I know I don't post much on xda, but I'll answer any question on irc. I've also become quite busy since this year started. So I work randomly here and there, and work with a few others closely, make them do the hard labor for me :laugh:. But you guys do make some good points, and again I don't think that things were meant to be secret. It's just not a lot of the discussions make it to xda.

See above about some of the openess. As far as the kernel, goes I just finished a few days ago a rebase of LGE's sources to caf jb_2.5 branch. However it doesn't boot, thats where I've gotten the idea of LGE's power management from. It was one of the major differences in rebasing as I went through everything. This kernel is on my github under the "test" repo. Github wasn't letting me push to the gee_3.4 repo and I haven't had time to fix it yet. Nor to merge back the LGE Power management code into 3.4 rebase. Or merge it into mako for testing. I'm more than open to all the help people can give on this. I have many ideas on narrowing down things but just time is always the enemy.

Now as far as releasing the freegee-testing, while it is working for you on att, and it worked for houstonn, we'd need a larger sample to confirm it works fine on other varients. And it very well might, sprint is going to be different because of CDMA and they way it's handled. The other issue, and for me this was the main issue before we realized about the radios, is it relies on extra 4 partitions being flashed and these have to flash perfectly. If any of the 4 don't flash perfectly, then on the first boot or a subsequent boot (depending on which didn't flash correctly) the phone is hard bricked. It's the same as the "special" freegee I give out to people that can't unlock normally. Its not public because before I give it out I'll spend as long as it takes checking with the person to make sure this is their last resort. The "special" freegee also flashes additional partitions (sbl1-3) and the risk for a hard brick is there. It's slim, but a slim chance is a lot more than a 0 chance of normal freegee.

I know you guys say if we warn people the risk is their own, but we do have a responsibility to make sure things are as safe as we can get them first. When people b0rk things we end up spending a lot of time helping the people on irc. Now I'm not complaining about helping people, don't get me wrong. It's more just if we can wait a fix/fool proof things more than then in the long run it's just better for everyone.

As a last note yes, defiently props to dvhexer for completely merging in the DS4 drivers for touch screen. I had tried but didn't have time to finish it up, and we need more talented people like dvhexer, sk8, et al. Right now the main thing stopping us is time, so the more people we can get working in uniform, and spread the project load, the better.
[AT&T LG Optimus G] blenkows:
I know there are some of you that aren't too bad, but I remember one specific time, someone posted in a thread asking what was the hold up only because they wanted to see if they could help. The devs response was "we aren't releasing any information until we figure this out" or something like that. They basically completely shunned away some help because of this "secrecy".

Like the guy wasn't asking for an ETA or anything, he just want to help. I know not all of you do this, but this one particular dev did. I can understand where they're coming from when it comes to ETA's but not things like this.

____

Sent from my LG Original Gangsta
[AT&T LG Optimus G] sk8erwitskil:
OK I get that. If you would like me to be like a dedicated relay between you guys and the public I can do that since you guys are busy. I don't mind dealing with people on xda. I really would like to help any way I can.
[AT&T LG Optimus G] whiteguypl:
To be honest I get the sense that this has a whole lot less to do with time then it does " brought to you by". Release known information time isn't a factor because anyone can chip away at a problem. Don't release it and yeah time is limited....After what sk8 said he was told I kinda don't buy this time stuff.

Edit: Also this is an att forum.. It shouldn't matter if something that bricks a sprint phone is posted here.
[AT&T LG Optimus G] houstonn:
don't get on att forums much.. but where's the party..........
[AT&T LG Optimus G] bleached45:
I have to say, this is probably the most exciting thing I've heard since the N4 conversion. :p

On my old phone's forum there were even "think tank" threads on things like root and bootloader unlocking.

I know placeholder threads are not allowed, but maybe a "state of the ROMdom" address thread in general with a

"hey user X is currently working on XX Rom, they have it built but touch isn't working, drivers need to be updated blah blah.

Team XX is looking into porting over the N4 kernel but blah..."

I realize a lot of this stuff is going on in irc, but just as a lot of the irc discussion doesn't make it to xda, a lot of xda doesn't make it to irc.

While it isn't the Devs job to tell us everything, it would be really cool if once every now and then somebody who has been following development can come over with a more in depth post than "it is being worked on."

Just my thoughts, I'm not important to development though, just an enthusiastic user who wishes he knew so much more about Android in general.
[AT&T LG Optimus G] :
This thread, starts with big bold letters saying no ETA's, no testers, etc; and bam. I think if we can get the community to cooperate and not bog down the thread with "OMG WHEN? CAN I TEST!?" it will work, and keep people excited. I can vouch for big things coming though.
[AT&T LG Optimus G] Jank4AU:
Why can't we do like Entropy did over on the SGH-I777 (AT&T Galaxy SII) forums and start a thread in development that only recognized developers or contributors can post in? That way the rest of us can read about it, you guys can collaborate, and you won't get any posts from the general public that bog down the discussion. Can't a mod set those permissions?
[AT&T LG Optimus G] :
I like this idea, but a lot of the devs working on it aren't recognized.
[AT&T LG Optimus G] Jank4AU:
Is it possible to post in a thread by invite only? Can any moderators or anyone else in the know answer this?
[AT&T LG Optimus G] whiteguypl:
Is a thread with a list of things being worked on and ideas on how to deal with issues in the development forum considered a place holder? Sounds like a development thread. Or the subforum should be renamed from "development" to "developed" if all that can be posted are already working things.
[AT&T LG Optimus G] :
Yeah it doesn't even have to be there. Put it anywhere even in the general section. Just somewhere for the devs to keep everyone up to date and stop the millions of posts of speculation and fighting.
[AT&T LG Optimus G] Jank4AU:
I would think you could start a thread about ongoing work in order to drive the thought process and collaboration. What you can't do is start a thread called: "My New ROM" - Coming Soon!

That's a place holder and is not allowed. This forum came to be in order to foster development through an open forum of communication about topics being worked on. I see no reason why a thread desinged to update people as to the progress of "development" wouldn't be allowed.
[AT&T LG Optimus G] dvhexer:
Thanks man, I appreciate it. I'm a rookie in android development, but have lots of development experience in general.

Some good news: I've got MHL working, need to do some testing (mirroring does not work in CM10.1 as of now) and then will push my changes to github.
[AT&T LG Optimus G] gunnyman:
So if I understand everything I have read today I can convert my phone to a 16GB nexus 4 and have external sd support, lte, and capacitive buttons?
[AT&T LG Optimus G] C2fifield:
Yep that about sums it up

Sent from my Nexus G LTE

(Hah it rhymes)