Operation KRUSH KOUSH

[sammyz]

I'm guessing he forgot to build for both screens....

Stop Apple from abusing patents

 

[tvall]

It doesn't work. I have an old screen OV. I first tried installing with the app I made... it hung on the part where it flashes and then when I rebooted to recovery I got fastboot.

Then to make sure it wasn't my apps fault, I went the old manual terminal way and it flashed but upon reboot I got a black screen.

No cigar.

It hung at the LG logo when I used your app, then it booted into the rom (new phone, no fastboot apparently) when done manually.

Just wanted to see if others had issues

 

[anthonycr]

Yeah. This is a let down.

 

[sellers86]

It doesn't work. I have an old screen OV. I first tried installing with the app I made... it hung on the part where it flashes and then when I rebooted to recovery I got fastboot.

Then to make sure it wasn't my apps fault, I went the old manual terminal way and it flashed but upon reboot I got a black screen.

No cigar.

Now it sounds like he forgot the old screen drivers... but its using mrgs kernel...

Sent from my LG-VM670 using Tapatalk

 

[anthonycr]

Now it sounds like he forgot the old screen drivers... but its using mrgs kernel...

Sent from my LG-VM670 using Tapatalk

I don't know anything about recoveries... but I bet its hard to build them for a phone you don't own

 

[rukin5197]

I don't know anything about recoveries... but I bet its hard to build them for a phone you don't own

I've done it. Its not that hard. Lol. But really depends on the phone.

Sent from my PC36100 using Tapatalk 2

 

[tvall]

I don't know anything about recoveries... but I bet its hard to build them for a phone you don't own

Its hard to build a working anything for a device you don't own. But building cwm is as easy as

$ . build/envsetup.sh
$ lunch <DEVICE>
$ make recoveryimage

All he should have needed to do was drop in the new kernel. I guess he must have broke something in the newer version.

 

[anthonycr]

So now what since it didn't work....

 

[tvall]

So now what since it didn't work....

See if he tries again. Repeat until he either makes a working one, or he removes support

 

[LeslieAnn]

I've done it. Its not that hard. Lol. But really depends on the phone.

Try the Optimus Elite if you would like a challenge. LOL

We have root, we have roms, but no recovery.

 

[tvall]

Try the Optimus Elite if you would like a challenge. LOL

We have root, we have roms, but no recovery.

Um... roms but no recovery? No comprendo...

 

[anthonycr]

Um... roms but no recovery? No comprendo...

Leave it to LeslieAnn to build roms for a phone she doesn't own

 

[flapjack.fiasco]

Any way we could invite Koush into this conversation? It might help if he can see some feedback on what's working and what's not.

Sent from my LG-VM670 using Tapatalk 2

 

[sellers86]

Any way we could invite Koush into this conversation? It might help if he can see some feedback on what's working and what's not.

Sent from my LG-VM670 using Tapatalk 2

not a good idea... hed get pissed off and wouldnt help us at all haha

 

[flapjack.fiasco]

not a good idea... hed get pissed off and wouldnt help us at all haha

Okay, so maybe we could set up a front thread that says pleasant things about him, and then we could... nah. Someone would be sure to add something spiteful, and I couldn't blame them for it.

Sent from my LG-VM670 using Tapatalk 2

 

[koush]

+1, amendment accepted

And yes I agree. Koush not releasing sources is way uncool. Not illegal since it's not technically GPL, just uncool.

CWM is open source.
https://github.com/CyanogenMod/android_bootable_recovery

So is the device repo used to build the thunderc recovery:
https://github.com/CyanogenMod/android_device_lge_thunderc/tree/ics

Hell, I even provide resources (and my personal build server) to build CWM (and touch) from source:
Recovery Builder

Might I suggest less ...about what an ... I am, and more fixing. This is what most device communities do. If you provide a fix, I'd be happy to build and publish it.
Instead, all I get are remarks on my twitter about how I need to unpublish thunderc. Even though it *worked* when I originally published it. Absolutely no information beyond that as to what the problem is, let alone a fix.

Getting a recovery built (or updated) and published to ROM Manager is not a difficult process. Fix the problem, open an issue on github, ask me to build it. I do this many times a week, for various device maintainers. The process is very well detailed here:
My Brain Hurts: Porting Clockwork Recovery to New Devices

Hell, I just built and published 6 new device recoveries while responding to this.
https://github.com/koush/ROMManagerManifest/commit/0b7d56f9dd2e71138579c5c315a654ac82e35881

So, once again, provide me with a recovery image or device config repository that works, and I can probably fix the issue.

 

[sellers86]

CWM is open source.
https://github.com/CyanogenMod/android_bootable_recovery

So is the device repo used to build the thunderc recovery:
https://github.com/CyanogenMod/android_device_lge_thunderc/tree/ics

Hell, I even provide resources (and my personal build server) to build CWM (and touch) from source:
Recovery Builder

Might I suggest less ... about what an ... I am, and more fixing. This is what most device communities do. If you provide a fix, I'd be happy to build and publish it.
Instead, all I get are remarks on my twitter about how I need to unpublish thunderc. Even though it *worked* when I originally published it. Absolutely no information beyond that as to what the problem is, let alone a fix.

Getting a recovery built (or updated) and published to ROM Manager is not a difficult process. Fix the problem, open an issue on github, ask me to build it. I do this many times a week, for various device maintainers. The process is very well detailed here:
My Brain Hurts: Porting Clockwork Recovery to New Devices

Hell, I just built and published 6 new device recoveries while responding to this.
https://github.com/koush/ROMManagerManifest/commit/0b7d56f9dd2e71138579c5c315a654ac82e35881

So, once again, provide me with a recovery image or device config repository that works, and I can probably fix the issue.

... I linked you to a repo that works. I even linked you to a ... recovery! You completely refused to cooperate with me on twitter. Use github.com/BobZhome/android_device_lge_thunderc.

Sent from my LG-VM670 using Tapatalk

 

[koush]

... I linked you to a repo that works. I even linked you to a ... recovery! You completely refused to cooperate with me on twitter. Use github.com/BobZhome/android_device_lge_thunderc.

Sent from my LG-VM670 using Tapatalk

Thanks for effectively proving proving my point.

You seriously think twitter is the proper forum to collaborate on development work and report bugs? Do you think I go and read every single mention I get? In the past day, I've gotten around ~200 mentions.

...

Did you even read the "porting" guide? It explicitly states to report issues on github. That's actually how I found out about this thread. Someone actually knew how to be properly proactive about getting a fix (tvall43).
https://github.com/koush/ROMManagerManifest/pull/407#issuecomment-7503856

 

[sellers86]

Thanks for effectively proving proving my point.

You seriously think twitter is the proper forum to collaborate on development work and report bugs? Do you think I go and read every single mention I get? In the past day, I've gotten around ~200 mentions.

...

Did you even read the "porting" guide? It explicitly states to report issues on github. That's actually how I found out about this thread. Someone actually knew how to be properly proactive about getting a fix (tvall43).
https://github.com/koush/ROMManagerManifest/pull/407#issuecomment-7503856

I dont use github. and yeah i seen the pull request. and I used twitter because I figured it would be faster. and how did I "effectively prove your point?" Ill be happy with you if you get the issue fixed. you have been contacted before. thanks.

 

[koush]

I dont use github.

There's the problem right there.

You want a fix, but you don't use the proper channels to report a bug or submit a fix.