[chambejp]

EDIT: 2/4/2012

Here is the link to the latest recovery. This does not include an actual rom, when you flash this you will only have the recovery and it's only for testing purposes. We have yet to release a rom with this for a recovery image though we likely will soon. As Always YMMV bricks are always possible

http://www.mediafire...7yf2hk9g6721o4z

BIG HUGE SHOUTOUT TO BIOHAZARD AND KADALUFI FOR HELPING ME STAY WITH THIS PROJECT SINCE I BRICKED MY WPDN Thank you both very much! I'll figure out some way to work a thanks into the program lol


So randomblame and I have been working on a new recovery today and it turns out we have been able to boot into a recovery mode from rhodium, courtesy of randomblame

http://www.mediafire...jeita6dbxktpbtl

EDIT:

So this one is not functional at all. it shows the screen and you can navigate. I wouldn't choose any options beyond navigating menus as it apparantly bricked my WPDN either with rebooting from within CWM or attempting to create a backup. touchscreen makes selection. vol up is up vol down is down. power button is back at least it should be It bricked before I could flash this recovery and test my button changes.

http://www.mediafire...bj9lst04tn14340

If you try this and turn your WPDN into a paperweight, You've been warned!

after flash,

adb shell
chmod 777 /system/bin/load.sh
load.sh

So thanks to RB for continuing to work on this thing while I'm out of commission we have the first ever flashable recovery. Flashing this will replace the stock recovery system with Clockworkmod recovery.



http://www.mediafire...jwup30w2pku3i60

Complete instructions are found on this post:
http://www.slatedroi...post__p__309411

Be careful, we don't promise anything. Even though it's been tested, it's only been tested by RB, so YMMV. We are NOT responsible if you have a white paper weight in the end.
Happy flashing! Oh do NOT flash a normal rom, recovery.img at the least must be removed from it prior to flashing. We will be putting up CWM safe version's of rom's soon.

This post has been edited by chambejp: 05 February 2012 - 12:16 AM

[randomblame]

it's totally useless still at this point but it's proof that we can boot a recovery from the system partition to test and leave our stock recovery alone. This allows testing of custom recoveries without all that risk of generating bricks

[terminander]

My first experience with a custom recovery was yesterday. I've been checking into Bluetooth tethering ever since I found out the Playbook tethers off a BB phone through bluetooth. Basically wifi tethering kills my phone in an hour. I needed to root my phone for the BT tethering app to work.

My Acer Liquid E supports the standard boot loader which allows the adb reboot bootloader commands. From there I just used the flashboot command to flash a custom recovery. The custom recovery menu allowed rooting.

So my Asus Transformer now tethers off my phone through BT and I'm am seeing 1.7meg download speeds....

Anyhow, I suspect a custom recovery has some sort of kernel/mini kernel in it. It appears the white recovery, jumps to recovery, which loads our kernel that uses the recovery as a custom file system.

Damm, gota fix my white novel now and replace the flacky wifi with BT.

[chambejp]

a Real recovery uses a kernel in the recovery image. the WPDN recovery does not have a kernel in the image. I'm working right now on putting clockwork mod, well after it downloads anyway, not sure what to do about the kernel thing.

[chambejp]

so apparantly we can ignore some of that crap from the directions to porting cwm. recovery.img does not contain recovery.fstab at least not as pulled directly from wpdn memory

[randomblame]

Still need recovery.fstab

[chambejp]

I'm using your recovery.fstab in one of your images

[chambejp]

needs alot of work to get this to work. You can't follow the part that pulls the info and sets it up from recovery.img

[chambejp]

So I got it to attempt to build recovery, unfortunately when I used the make -j4 recoveryimage it gives me "make: Nothing to be done for `recoveryimage'." what I need is to build for another phone model with our processor. These are the ones that came with the cyanogen repo:

including device/advent/vega/vendorsetup.sh
including device/bn/encore/vendorsetup.sh
including device/geeksphone/one/vendorsetup.sh
including device/htc/ace/vendorsetup.sh
including device/htc/bravoc/vendorsetup.sh
including device/htc/bravo/vendorsetup.sh
including device/htc/buzz/vendorsetup.sh
including device/htc/click/vendorsetup.sh
including device/htc/desirec/vendorsetup.sh
including device/htc/dream_sapphire/vendorsetup.sh
including device/htc/espresso/vendorsetup.sh
including device/htc/glacier/vendorsetup.sh
including device/htc/heroc/vendorsetup.sh
including device/htc/hero/vendorsetup.sh
including device/htc/inc/vendorsetup.sh
including device/htc/legend/vendorsetup.sh
including device/htc/leo/vendorsetup.sh
including device/htc/liberty/vendorsetup.sh
including device/htc/mecha/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/saga/vendorsetup.sh
including device/htc/speedy/vendorsetup.sh
including device/htc/supersonic/vendorsetup.sh
including device/htc/vision/vendorsetup.sh
including device/htc/vivo/vendorsetup.sh
including device/htc/vivow/vendorsetup.sh
including device/huawei/u8150/vendorsetup.sh
including device/huawei/u8220/vendorsetup.sh
including device/lge/p999/vendorsetup.sh
including device/malata/smb_a1002/vendorsetup.sh
including device/malata/smb_b9701/vendorsetup.sh
including device/motorola/droid2/vendorsetup.sh
including device/motorola/droid2we/vendorsetup.sh
including device/motorola/jordan/vendorsetup.sh
including device/motorola/morrison/vendorsetup.sh
including device/motorola/motus/vendorsetup.sh
including device/motorola/olympus/vendorsetup.sh
including device/motorola/shadow/vendorsetup.sh
including device/motorola/sholes/vendorsetup.sh
including device/motorola/zeppelin/vendorsetup.sh
including device/pandigital/s3c6410/vendorsetup.sh
including device/samsung/captivatemtd/vendorsetup.sh
including device/samsung/cooper/vendorsetup.sh
including device/samsung/crespo4g/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/epicmtd/vendorsetup.sh
including device/samsung/fascinatemtd/vendorsetup.sh
including device/samsung/galaxys2att/vendorsetup.sh
including device/samsung/galaxys2/vendorsetup.sh
including device/samsung/galaxysbmtd/vendorsetup.sh
including device/samsung/galaxysmtd/vendorsetup.sh
including device/samsung/mesmerizemtd/vendorsetup.sh
including device/samsung/showcasemtd/vendorsetup.sh
including device/samsung/sidekick4g/vendorsetup.sh
including device/samsung/tass/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/zte/blade/vendorsetup.sh
including device/zte/v9/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh

[randomblame]

tom3qs jithub has all his files to build cm7 for the spica which also runs s3c6410

[chambejp]

hmmm I think I actually have that.

[chambejp]

I'm on the irc channel

[chambejp]

actually I didn't have that. I had the kernel part. cloning the git now

[randomblame]

Woot clockwork mod


TEST IMAGE FOR TESTING PURPOSES ONLY NOT INTENDED FOR USERS IF YOU FLASH THIS AND HAVE TROUBLE I WILL JUST LAUGH AT YOU
http://www.mediafire...ah0k5m7b630vdd6

I put that together with your recovery.img files basically all that needed done was copying /system/sbin to /system/bin and yaffsing it

from adb shell run /system/sbin/recovery

This post has been edited by randomblame: 29 January 2012 - 07:17 PM

[panengineer]

Looks like a big breakthrough in rom and kernal development for the WPDN.

[randomblame]

it will be if we get it working properly

new version with working bitmaps and a lot less errors
http://www.mediafire...10yua8zeop4l023

flash and then in adb shell run load.sh

This post has been edited by randomblame: 29 January 2012 - 09:48 PM

[chambejp]

So we're are stuck at the menu because we can't find the recovery keymaps

EDIT:

I think I just found it in default_recovery_ui.c

This post has been edited by chambejp: 29 January 2012 - 11:20 PM

[randomblame]

If it is trying to read input stuff from the kernel maybe we need an older version to compare

[chambejp]

No I'm sure its in recovery_ui.c almost positive. Has if volume up return highlight down

At least it does now. Before it had like menu return highlight down

[chambejp]

Its compiling while I'm putting kids to bed