SLOW Work in progress, porting custom recovery over

misterfamilyguy · February 27th, 2012, 08:01 PM

All frustrated c800s,
Hi, I'm learning as I go, have been trying to port clockworkmod recovery to our phone for about a month now. I was working in subforum for e739 (MyTouch) and c800 (MyTouch Q) but it was just getting too crowded, also a lot of pessimism, we need optimism for this. There is currently a working recovery and dev for the e739, everyone has stayed away from the c800. I don't know why, everyone ignores me. So, I'm reaching out the the community and hoping that with some organization and pooled thoughts we can get this accomplished. I will summarize what I have learned so far:

To root, set up adb, run

Code:

adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit

Then run superoneclick newest version, which is 2.3.3. This is from

HTML Code:

http://forum.xda-developers.com/showthread.php?t=1407961

It's best to then install a different Home program, then Titanium Backup and freeze or uninstall apps that are t-mo branded or you know don't matter. I sent the moderator a list. Just be sure not to delete the LG Home, If you soft brick you will need that on there to not get stuck in Force-close loop.

If you root and get stuck, try wiping, which is power down, power up with F+A+VOL DOWN+POWER BUTTON, let go power button when first LG logo shows up, the stock 3e recovery loads and wipes /data and /cache. It doesn't wipe /system, so thats why you need the LG Home in there. I think you can get around that by renaming your replacement home the same as the LG one, or placing the actual app file into /system/app, but I haven't tried either.

While on the 3e screen, if you hit the softkey button for Home, you get into the user selectable version, there is an option to flash update.zip. I BELIEVE this is pretty much our best bet at flashing a custom recovery.

So,
Currently I had some computer issues and had to delete my ubuntu install, so when I"m done moving I'll set that back up. But I've been working off of koush's directions for porting. The main quibbles are setting up and getting the recovery built.

For anyone wanting to start, you can find out how to set up your build environment from reading the info in koush's post, and

HTML Code:

http://forum.xda-developers.com/showpost.php?p=12878950&postcount=2

Some other helpful links:

HTML Code:

http://forum.xda-developers.com/showthread.php?t=986059

HTML Code:

http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html

HTML Code:

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images#Unpacking.2C_Editing.2C_and_Re-Packing_the_images

Some notes. The partition structure is
major minor blocks name

179 7 8192 mmcblk0p7 =boot
179 15 462848 mmcblk0p15 =system
179 16 1048576 mmcblk0p16 =data
179 17 8192 mmcblk0p17 =recovery
179 18 102400 mmcblk0p18 =cache
179 20 8192 mmcblk0p20 =lgdrm
179 21 8192 mmcblk0p21 =multimedia

So the recovery.fstab is the same as for e739/e730, however, when flashing the already built custom recovery for those phones into my recovery partition, it won't boot. I can flash back the stock one, and it boots and wipes /data /cache, and flash the custom, nothing. I think there is something to that in the phones init.rc file, however I haven't had the time to check.

Last thing I did before I had to delete my ubuntu install was I was getting errors making the recoveryzip to try to do the fake-flash method. It was saying that the file size was too large. I think it can be compressed further, but haven't found too much info. Maybe the xda subforum for the gt450 or other optimus phones will shed light on that.

So, I'll check back in when I get back up and running.

**update 03/17/2012
Got my build environment set back up. I am uploading stock boot.img and recovery.img compressed in .zip format. Including md5sums for accountability issues that may arrise later:
86da068132b4c44afcb3bc31a96148b3 boot.img
00b5010e915b6f26a33a143f868dd2f9 recovery.img
6c88d56e952c0a2028c6fae36eebea37 recovery.img.zip
8245e47601ab3c56154207383acf9730 boot.img.zip

ace7196 · February 27th, 2012, 08:10 PM

Joined this forum just to be a part of the amazing-ness to come!

laphoneuser · February 27th, 2012, 09:23 PM

Although I have no real technical expertise to offer, I own this phone, and wanted to show my support.

Thanks for starting the thread, and for your efforts with what I think can be a solid phone with some speed tweaks.

I'll be checking in now and then to see if there's anything I can do to help.

Brendantron · February 27th, 2012, 10:45 PM

In post #476 of the thread on xda, deltacity describes a very similar situation with flashing the e739 recovery on our c800 as you're facing right now: it didn't boot.
He noticed the stock c800 recovery was 8mb while the e739 was 4mb. I'm not sure what that could signify since our recovery partition ought to be larger than needed, not smaller (which obviously would be a barrier).
Why is it larger? Is there something contained in it that the c800 system requires??

ace7196 · February 28th, 2012, 03:47 PM

Currently using the SuperCharge V6 script. Using the multitasking minifree setting performance has gone up pretty substantially.the multitasking minifree setting performance has gone up pretty substantially.

Using Spare Parts Plus I sent wifi to never sleep, so I do not use up my 4g data (not a problem, but at least wifi is faster). Some say it helps battery life.

Use Ti Backup to freeze all apps (NOT REMOVE). If you did remove (like I did before misterfamilyguy's revelations), the system/app folder is here. Credit here.

I'm using LauncherPro Plus. Fastest launcher with nice built-in, skinable widgets.

Boat browser seems the best for me. Mostly an updated Miren browser. I've tried Opera mobile/mini, dolphin, stock, firefox, and other random ones. Boat actually has the UA as android, so I get all the pretty formatted pages. The tabs and customizability is nice as well. If you're stuck on opera, you can grab a custom UA to make it try to load Android friendly pages, but the engine they use doesn't play nice with a lot of stuff.

Anyone have any other tweaks?

vxbinaca · February 29th, 2012, 08:40 AM

Remove (yes I said remove thats the one safe thing to remove) LG Home and replace it with Zeam for max performance.

I think the instability I see is from removing any trace of that stupid car mode/Genius stuff. Was glad to get rid of it. Sick of hitting the button mid call and sending it into car mode. They make bluetooth headsets for a reason.

misterfamilyguy · February 29th, 2012, 02:19 PM

If you remove LG Home research about puting your replacement into system/apps, or not its up to you. When testing I got a boot loop that I managed to turn into a force close loop because it couldn't locate a home app. I have also posted a list of apps I have frozen in the rooting post, you have to click the HIDE button to display them, one was the genius button and dragon dictation.

misterfamilyguy · February 29th, 2012, 02:46 PM

ace7196,
I use adwlauncher, v6 doesn't seem to work with it. I get a lot of "not found" prompts instead of what I should be getting. I'm going to test out launcherpro and zeam

Brendantron,
I'm not sure if/why the file size matters, but to answer your question the c800 recovery image is quite a bit bulkier that the e739 from what I can tell because there are literally more files. There are double the .rc files and such.

I'm still moving, doing the big push this weekend, so hope to get my build environment back up by next thursday,,nobody else wants to do it along with me?

vxbinaca · February 29th, 2012, 04:06 PM

Quote:

Originally Posted by misterfamilyguy

If you remove LG Home research about puting your replacement into system/apps, or not its up to you. When testing I got a boot loop that I managed to turn into a force close loop because it couldn't locate a home app. I have also posted a list of apps I have frozen in the rooting post, you have to click the HIDE button to display them, one was the genius button and dragon dictation.

I know that already about the launcher, learned that lesson the hard way with my G1 a few times.

vxbinaca · March 2nd, 2012, 01:33 PM

misterfamilyguy: What do you need to start working on CWM within the next week. I will FedEx you a laptop with a burned ubuntu (why? just use Debian) CD. I'm dead serious.

If you're not working on it, lemme know so I can toss this turd in the trash and get a real phone.

Edit:

In the pane below I have the MyTouch Q a half star rating. I wish it the system would let me rate it lower.

misterfamilyguy · March 3rd, 2012, 02:15 AM

Vx I'm moving right now. My computer isn't even hooked up. Hope to be done by next Friday. I think I'm going to try to port rzrecovery first. If you hate the phone that much sell it on craigslist. You gotta remeber once we get recovery working we then hav e to make roms, which I imagine is more difficult

Brendantron · March 12th, 2012, 07:26 AM

Quote:

Originally Posted by misterfamilyguy

I'm still moving, doing the big push this weekend, so hope to get my build environment back up by next thursday,,nobody else wants to do it along with me?

I just got my PC set up again. I'm willing to dev along side you. At this point I'd really just be "monkey see, monkey do" but I will gamble this phone.

I saw an XDA interview with a real dev called Toastcfh.
Interview with Toastcfh – XDA TV | xda-developers
In it he says you have to thank the trolls for telling you "you can't do it" because it motivates you to prove them wrong. So, I don't know if vxbinaca here is going to keep wordplaying with himself to feel better than anyone with a better attitude than his, or if this offer of material support shows he can actually do something... productive. Either way, his little post back on XDA is *delicious*! Or I certainly hope so, since he's going to be eating those words.

misterfamilyguy · March 12th, 2012, 02:50 PM

Quote:

Originally Posted by Brendantron

I just got my PC set up again. I'm willing to dev along side you. At this point I'd really just be "monkey see, monkey do" but I will gamble this phone.

I saw an XDA interview with a real dev called Toastcfh.
Interview with Toastcfh – XDA TV | xda-developers
In it he says you have to thank the trolls for telling you "you can't do it" because it motivates you to prove them wrong. So, I don't know if vxbinaca here is going to keep wordplaying with himself to feel better than anyone with a better attitude than his, or if this offer of material support shows he can actually do something... productive. Either way, his little post back on XDA is *delicious*! Or I certainly hope so, since he's going to be eating those words.

Cool,
I appreciate the help. In my first post I linked a few things that will help you get the build environment set up. I have to re-set mine up. I'm mostly done unpacking now and have my puter set back up. I was looking at porting over rzrecovery to try that out. His seems like it may have a little more response from the dev. If you get your environment set up maybe we can IRC or something to work this out. A few things that were worked out by someone else in xda, sorry don't recall name for credit. When I get environment back up, supposedly if you run unpackbootimg.pl on the boot img, it'll output most of this, I'll do this later to verify and fill in the gap.

base kernel address=0x00200000

the boot command line=console=ttyMSM1 androidboot.hardware=lgc800 lge.rev=rev_10 lge.reboot=pwroff uart_console=disable lge.frst=flag3 lge.hreset=off androidboot.emmc=true androidboot.baseband=msm

the page size=????

the partition layout =
179 7 8192 mmcblk0p7 =boot
179 15 462848 mmcblk0p15 =system
179 16 1048576 mmcblk0p16 =data
179 17 8192 mmcblk0p17 =recovery
179 18 102400 mmcblk0p18 =cache
179 20 8192 mmcblk0p20 =lgdrm
179 21 8192 mmcblk0p21 =multimedia

Quixote · March 15th, 2012, 04:46 PM

Unlike some other users of that other forum, I am willing to risk my Q for science!

Worst case scenario I go buy something that CWM already supports.

So... that said.

What can I do to help?

misterfamilyguy · March 17th, 2012, 01:33 AM

Quote:

Originally Posted by misterfamilyguy

Cool,
I appreciate the help. In my first post I linked a few things that will help you get the build environment set up. I have to re-set mine up. I'm mostly done unpacking now and have my puter set back up. I was looking at porting over rzrecovery to try that out. His seems like it may have a little more response from the dev. If you get your environment set up maybe we can IRC or something to work this out. A few things that were worked out by someone else in xda, sorry don't recall name for credit. When I get environment back up, supposedly if you run unpackbootimg.pl on the boot img, it'll output most of this, I'll do this later to verify and fill in the gap.

base kernel address=0x00200000

the boot command line=console=ttyMSM1 androidboot.hardware=lgc800 lge.rev=rev_10 lge.reboot=pwroff uart_console=disable lge.frst=flag3 lge.hreset=off androidboot.emmc=true androidboot.baseband=msm

the page size=????

the partition layout =
179 7 8192 mmcblk0p7 =boot
179 15 462848 mmcblk0p15 =system
179 16 1048576 mmcblk0p16 =data
179 17 8192 mmcblk0p17 =recovery
179 18 102400 mmcblk0p18 =cache
179 20 8192 mmcblk0p20 =lgdrm
179 21 8192 mmcblk0p21 =multimedia

Here is output from split_bootimg.pl ::

Code:

Page size: 4096 (0x00001000)
Kernel size: 4026480 (0x003d7070)
Ramdisk size: 541470 (0x0008431e)
Second size: 0 (0x00000000)
Board name: 
Command line: console=ttyMSM1 androidboot.hardware=lgc800
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.

So, I think the Page size is what was referred to for rzrecovery, and I think the Command line is the correct command line for ''boot command line'' required by rzrecovery. No idead how the other person got the one before...

misterfamilyguy · March 17th, 2012, 01:34 AM

Quote:

Originally Posted by misterfamilyguy

Here is output from split_bootimg.pl ::

Code:

Page size: 4096 (0x00001000)
Kernel size: 4026480 (0x003d7070)
Ramdisk size: 541470 (0x0008431e)
Second size: 0 (0x00000000)
Board name: 
Command line: console=ttyMSM1 androidboot.hardware=lgc800
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.

So, I think the Page size is what was referred to for rzrecovery, and I think the Command line is the correct command line for ''boot command line'' required by rzrecovery. No idead how the other person got the one before...

Here is the output for stock recovery.img, somwhat similar

Code:

Page size: 4096 (0x00001000)
Kernel size: 4026480 (0x003d7070)
Ramdisk size: 780510 (0x000be8de)
Second size: 0 (0x00000000)
Board name: 
Command line: console=ttyMSM1 androidboot.hardware=lgc800
Writing recovery.img-kernel ... complete.
Writing recovery.img-ramdisk.gz ... complete.

misterfamilyguy · March 17th, 2012, 02:05 AM

I'm now trying to figure out how to start working on rzrecovery and/or get cwm to work. Whenever I try to build recovery for cwm i get:

Code:

out/target/product/MyTouch_Q/boot.img total size is 4186112
error: out/target/product/MyTouch_Q/boot.img too large (4186112 > [3784704 - 270336])
make: *** [out/target/product/MyTouch_Q/boot.img] Error 1
make: *** Deleting file `out/target/product/MyTouch_Q/boot.img'

So, it makes it, then deletes it. Even though the original boot.img is 8.4mb and the supposed output is 4 mb.. I dunno.

misterfamilyguy · March 17th, 2012, 02:12 AM

Last one was with the boot.img.. this one is with recovery.img:

Code:

out/target/product/MyTouch_Q/boot.img total size is 4186112
error: out/target/product/MyTouch_Q/boot.img too large (4186112 > [3784704 - 270336])
make: *** [out/target/product/MyTouch_Q/boot.img] Error 1
make: *** Deleting file `out/target/product/MyTouch_Q/boot.img'

I can't figure out why it won't do it....

misterfamilyguy · March 17th, 2012, 06:58 PM

i think i figured out why getting too large errors. need to configure boardconfig, which i was skipping.

for some reason keep having to do this too when get unpackbootimg error. dunno why its not staying in my bashrc

Code:

export PATH=$PATH: (droidbuilddirectorybase)/out/host/linux-x86/bin

misterfamilyguy · March 17th, 2012, 07:52 PM

Ok, so I think I figured out the boardconfig.mk issue.
I searched [FINAL] 3/18/2011 CWM Recovery on Dell Streak 7 - xda-developers
and found that someone suggested using

Code:

BOARD_BOOTIMAGE_MAX_SIZE := $(call image-size-from-data-size,0x00280000)
BOARD_RECOVERYIMAGE_MAX_SIZE := $(call image-size-from-data-size,0x00500000)
BOARD_SYSTEMIMAGE_MAX_SIZE := $(call image-size-from-data-size,0x07500000)
BOARD_USERDATAIMAGE_MAX_SIZE := $(call image-size-from-data-size,0x04ac0000)

I then ran

Code:

make -j4 recoveryzip

And didn't get an error. So, hopefully it worked. It even gave an output that was in the correct update.zip format, so seems good. I'm not going to flash on my phone right now cause gotta prepare dinner, but will test tomorrow. For anyone wanting to test it. Use the method to get into our stock 3e recovery. VOL DOWN - F - A- then when android pops up hit softkeys. then select flash update.zip. Do this at your own risk. If you got work early tomorrow, don't do it, if you got some important use for your phone coming up, don't do it. Just wait a bit until I can test it.
md5sum for this update.zip is

Code:

f38092c48c853bd51382d38f5439f75c

vxbinaca · March 18th, 2012, 06:13 PM

I think LG released the code for the C800. 607 meg zip coming my way.

Edit:

https://docs.google.com/open?id=0B-4VZvQ8gAQEczVSWmtnWnBRdXE1YlpLQ1VCNUp4QQ

misterfamilyguy · March 19th, 2012, 01:30 AM

I ran it. It gets past verifying update package, says installing update, says replacing stock recovery with ClockworkMod recovery, then freezes and after a while reboots....anyone have any ideas?
On a side-note. Since when you boot into 3e recovery it wipes /data, and before that I replaced the stock LGHome with zeam home renamed and proper permissions set, it booted zeam just fine.

misterfamilyguy · March 19th, 2012, 12:21 PM

I tried making the recovery image first, then the update.zip to see if that helps, but I don't have time to flash either today.

md5sum for update.zip

Code:

1604054821137b7a981cfaeffa6c1ec7

md5sum for zipped recovery.img

Code:

11c8118a3ebc341c1fc9304f9766f59b

Vx,
I've downloaded the source before, I just don't know how that is helpful. I've searched on how to build a recovery from source but couldn't find anything useful. Maybe you'll have more luck?

miniman1013 · March 20th, 2012, 08:55 AM

Quote:

Originally Posted by misterfamilyguy

I tried making the recovery image first, then the update.zip to see if that helps, but I don't have time to flash either today.

md5sum for update.zip

Code:

1604054821137b7a981cfaeffa6c1ec7

md5sum for zipped recovery.img

Code:

11c8118a3ebc341c1fc9304f9766f59b

Vx,
I've downloaded the source before, I just don't know how that is helpful. I've searched on how to build a recovery from source but couldn't find anything useful. Maybe you'll have more luck?

So... I'm new to the whole ROM thing, so don't be too hard on me, but.... what do I do to test this?

ace7196 · March 20th, 2012, 10:05 AM

Quote:

Originally Posted by miniman1013

So... I'm new to the whole ROM thing, so don't be too hard on me, but.... what do I do to test this?

As awesome as volunteering is, if you do not know the difference between a recovery and a rom, I'm not sure how much help you can be.

vxbinaca · March 20th, 2012, 02:38 PM

Quote:

Originally Posted by misterfamilyguy

I tried making the recovery image first, then the update.zip to see if that helps, but I don't have time to flash either today.

md5sum for update.zip

Code:

1604054821137b7a981cfaeffa6c1ec7

md5sum for zipped recovery.img

Code:

11c8118a3ebc341c1fc9304f9766f59b

Vx,
I've downloaded the source before, I just don't know how that is helpful. I've searched on how to build a recovery from source but couldn't find anything useful. Maybe you'll have more luck?

Which am I flashing?

Edit:

Same thing as MFG described before, runs through the steps and halts while flashing. Crossing my fingers I still have a phone.

Edit 2:

Phone not ruined. I'm down for testing.

misterfamilyguy · March 20th, 2012, 06:14 PM

YA, i'm not sure what steps to take next as far as figuring it out. I think it is odd that the update.zip is 1 meg, the recovery image zipped is over 5. I feel like I am missing something there. But, still on my own as far as figuring it out, unless someone here can find the right keyphrase to search for.

mini man and vx. In my post where I posted the first attempt at update.zip, i ran down the simple instructions. The reason I put the recovery.img.zip was for if anyone wanted to unpack it and play with it.

ace7196 · March 22nd, 2012, 07:49 PM

Quote:

Originally Posted by misterfamilyguy

YA, i'm not sure what steps to take next as far as figuring it out. I think it is odd that the update.zip is 1 meg, the recovery image zipped is over 5. I feel like I am missing something there. But, still on my own as far as figuring it out, unless someone here can find the right keyphrase to search for.

mini man and vx. In my post where I posted the first attempt at update.zip, i ran down the simple instructions. The reason I put the recovery.img.zip was for if anyone wanted to unpack it and play with it.

Any update? Has the RZrecovery guy given any help?

misterfamilyguy · March 23rd, 2012, 02:37 AM

nothing back from rzrecovery guy. I think he is just living life. I have not worked on this lately. I just can't find any info on where to go now.

vxbinaca · March 26th, 2012, 08:26 AM

Quote:

Originally Posted by misterfamilyguy

nothing back from rzrecovery guy. I think he is just living life. I have not worked on this lately. I just can't find any info on where to go now.

Ask that MysteryEmotionez guy on XDA, he seems to be the only one who gives a damn about this handset or anything that isn't HTC on Verizon.

misterfamilyguy · March 27th, 2012, 08:09 PM

I posted a request for help thread over at xda, we'll see if it gets anywhere.

misterfamilyguy · March 28th, 2012, 07:29 PM

HTML Code:

http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/

will try some of the customization parts at the bottom when get home later into weekend. For anyone wanting to attempt to build, this guid is pretty much on spot, any quibbles can be handles by just reading the terminal output and adjusting the input.

misterfamilyguy · March 28th, 2012, 11:44 PM

Tweaked a bit ref that other post. Not much changed I think though, but here are the outputs.
md5sum for update.zip

Code:

fa3297f8e41bf90fcecb95c686202524  update.zip

mdsum for recovery.img.zip

Code:

33c28b347a5865da451a1a241a220c59  recovery.img.zip

[edit 1]I tried using dd command to flash the recovery.img. Nothing...anyone with stock recovery want to try out the update.zip? Remember to backup your stuff first since it automatically wipes /data

[edit 2] boot looped my phone again. stupid. luckily i know enough now to just attach usb. push the original recovery to sd card. get into shell, then dd the orig recovery and i'm back. the crappy thing is it wiped everything. Since I did do a really good backup with titanium last time I shouldn't have an issue getting back, but dang...

[edit 3] tried the update.zip. still freezes.... bang.. head.. on .. desk...going to play xbox now.

vxbinaca · March 29th, 2012, 08:21 PM

Why not just test it before you post? Just to see if it works (spoilers: The next 5 bakes will do the exact same thing).

Android devs are such an awesome community. Abandoning an entire handset to only be worked on by novices out of sheer frustration, refusing to help them, focusing only on HTC handsets on Verizon networks.

I think I can safely unwatch this thread since this is going nowhere. June is a 3 check month, I'll get a new handset after serious research and confirmation CWM and CM await my phone when I get it home and kiss this turd goodbye. Into the trash it will go.

Spoilers: That stock ICS update promissed by TMO, not coming for the Q.

miniman1013 · April 6th, 2012, 09:41 AM

...is this dead then? :'(

vxbinaca · April 6th, 2012, 01:18 PM

Quote:

Originally Posted by miniman1013

...is this dead then? :'(

Yes. None of the devs support phones with keyboards anymore, or phones that aren't Samsung/HTC-Verizon. As valiant as as his efforts are he's a novice and no ones helping him, because all the real experienced devs are working on Samsung/HTC-Verizon handsets

Chuck that hunk of shit into a river and go out and get a real phone.

Lesson learned: don't ever buy LG hardware no matter how tempting the price point.

strumcat · April 7th, 2012, 01:09 AM

Misterfamilyguy, I just wanted to say thank-you for all your efforts. This is a valuable thread even though you didn't get Clockworkmod Recovery ported like you wanted. Just being able to root the MyTouch Q and know some of the things to be careful about are a lot better than nothing. You made a valiant effort and that deserves credit. Thanks.

vxbinaca · April 7th, 2012, 03:47 PM

Quote:

Originally Posted by strumcat

Misterfamilyguy, I just wanted to say thank-you for all your efforts. This is a valuable thread even though you didn't get Clockworkmod Recovery ported like you wanted. Just being able to root the MyTouch Q and know some of the things to be careful about are a lot better than nothing. You made a valiant effort and that deserves credit. Thanks.

You'd better be real ****in' careful with what you do to your phone, theres no way to undo most of it, a since the software only does a /data wipe, and not a full restore of the phone.

You've been warned. You should have been warned to not buy the phone in the first place.

misterfamilyguy · April 7th, 2012, 11:50 PM

Yes, sorry all but i've given up. Couldn't figure it out. I don't know why devs don't jump on keyboard cells . Even the HTC retouch 4g slide isnt well supported. I don't think the new Huawei slide will be deved . So , I gotta get my q warranty replaced from messing with it and sell it on craigslist for quarters on the dollar. I got myself a HTC sensation 4g . It has a lot of devs currently I got ics Rom on it. Sorry to all but I just don't know enough to figure it out .

vxbinaca · April 8th, 2012, 01:17 PM

Quote:

Originally Posted by misterfamilyguy

Yes, sorry all but i've given up. Couldn't figure it out. I don't know why devs don't jump on keyboard cells . Even the HTC retouch 4g slide isnt well supported. I don't think the new Huawei slide will be deved . So , I gotta get my q warranty replaced from messing with it and sell it on craigslist for quarters on the dollar. I got myself a HTC sensation 4g . It has a lot of devs currently I got ics Rom on it. Sorry to all but I just don't know enough to figure it out .

See, even the self-appointed guy who was supposed to dev for this piece of shit, ended up selling it.

Anyone reading this: Don't root your Q, sell it and get a real god damned phone.

Mr Biggles · April 10th, 2012, 07:43 AM

Quote:

Originally Posted by vxbinaca

See, even the self-appointed guy who was supposed to dev for this piece of shit, ended up selling it.

Anyone reading this: Don't root your Q, sell it and get a real god damned phone.

You seem a little bitter, amigo.

I like my Q. I rooted it, paid for the pro version of Titanium Backup, froze the bloatware and all the things I don't use. My battery life doubled and the phone works great. Slider or not, it's an entry level phone with somewhat out of date specs. I did a little research so I knew that when I got it. I'm not surprised the devs don't support it. I got it anyway because it was the only android phone they'd give me on a cheap-ass no data talk and text plan. In a way, I'm somewhat thankful that there aren't numerous ROMs and whatever available for it. It will keep me from messing with it so much that I finally brick it.

Quixote · April 12th, 2012, 09:17 PM

At the risk of beating a dead horse (Hiding his baseball bat), I am wondering if anyone wants to resurrect this now that LG has released the source code.

Additionally I think I found someone interested in working on a CWM-R port. But I need the following information, and my phone is soft-brick'd.

/system/build.prop
/proc/partitions
/proc/mounts
/proc/mtd (if exists)
/proc/emmc (if exists)

Stock recovery.log -- Check /cache/recovery/last_log or /tmp/recovery.log

miniman1013 · April 13th, 2012, 11:14 AM

there's no emmc, but everything else is here - THANK YOU for trying this dude!!!!!!

ThatIndianGuy · April 15th, 2012, 05:34 PM

I looked at the XDA forum that OP posted and realized he put it in the "Upgrading, Modifying and Unlocking" section. I think that section is for network unlock/hardware mods. Someone should move it to the "Android Software and Hacking General"

Quixote · April 17th, 2012, 07:31 PM

I have received a recovery image to test (build1.img) but I am not sure what I need to do to go from the img to the update.zip

Thoughts?

miniman1013 · April 17th, 2012, 09:53 PM

Quote:

Originally Posted by Quixote

I have received a recovery image to test (build1.img) but I am not sure what I need to do to go from the img to the update.zip

Thoughts?

I personally am out of my league, but I think mrfamilyguy mentioned a xda thread about making a recovery/update.zip earlier... here [FINAL] 3/18/2011 CWM Recovery on Dell Streak 7 - xda-developers

vxbinaca · April 19th, 2012, 08:11 PM

>dude takes up Q dev.
>figures out how hard it really is.
>realizes theres no stock image to flash back to, and mobile support tool is utterly worthless. russian roulette every time he flash_images.
>none of the CWM devs want to help, are focused on Samsung/HTC Verizon phones.
>makes a couple of update.zips that do nothing based on instructions for an entirely different phone (don't even use that Del Streak thread it's ****ing useless and didn't help MFG).
>gives up like misterfamilyguy and mysteryemotionez did, sells their turd phones on CL to get a real handset. does better things with life.

That how it happenes. Every single time. And how it will end up the next time.

It's over guys. Give up already.

brettvanpelt · May 19th, 2012, 02:40 AM

i know this is off key, but here i go. does anyone know how to edit the build.prop the right way so the "stock" android lock screen works right? everytime i change "user.feature.lock_sui=true" to this "user.feature.lock_andy=true" the phone loads the stock lock screen. however;when i go to unlock it, the damn thing restarts back to the lock screen every time. what really pisses me off is i got to reflash "V10D_00.kdz" using some program i found online called "updater", what it does is let me reinstall the .kdz file again. this little program i found is not same as the mobile tool lg has for us to use if u cared to know. so who ever made this program your awesome u saved my phone about 5 times now. and if anyone has found any hope of an half ass recovery let me know thanks

vtinoc · May 19th, 2012, 06:00 AM

Quote:

Originally Posted by brettvanpelt

i know this is off key, but here i go. does anyone know how to edit the build.prop the right way so the "stock" android lock screen works right? everytime i change "user.feature.lock_sui=true" to this "user.feature.lock_andy=true" the phone loads the stock lock screen. however;when i go to unlock it, the damn thing restarts back to the lock screen every time. what really pisses me off is i got to reflash "V10D_00.kdz" using some program i found online called "updater", what it does is let me reinstall the .kdz file again. this little program i found is not same as the mobile tool lg has for us to use if u cared to know. so who ever made this program your awesome u saved my phone about 5 times now. and if anyone has found any hope of an half ass recovery let me know thanks

I know this is not what you hope for but can you link to that "updater"
program im bricked.

brettvanpelt · May 19th, 2012, 12:52 PM

here is the zip file hope it un bricks phone, did mine lol. u well need to find the .kdz file to flash i got it but its to big to post on here. how u use, u click the exe file to get it to run.