• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root SLOW Work in progress, porting custom recovery over

strumcat said:
I uploaded the archive86304ef9982d045fd52d904a2b9a5740.zip, a screenshot of the Jenkins page, and the console output from the build to 4squared. Please be aware that I haven't tried these files out and I have no idea if they work or not.

Use them at your own risk.

Just go to 4shared folder - My 4shared (free signup) and download away.
Click to expand...
Your recovery works fine, thanks.
zw0tjo.jpg


We need a build of this with a custom recovery.fstab so that it can access the filesystem properly.

UPDATE: I have made a recovery.fstab, and so far I can access everything but /sdcard. You can find my recovery on builder.clockworkmod.com
 
Girlfriend just got this phone, so it looks like I'm jumping in right as the breakthrough is happening!

I tried mounting /dev/block/mmcblk1p1 as vfat and it mounted the sd card. Could that be the missing entry in the recovery.fstab?
 
chui101 said:
Girlfriend just got this phone, so it looks like I'm jumping in right as the breakthrough is happening!

I tried mounting /dev/block/mmcblk1p1 as vfat and it mounted the sd card. Could that be the missing entry in the recovery.fstab?
Click to expand...
This is what I needed to fix the recovery. I'll post the changes to builder.clockworkmod.com

Update: Here it is.
http://builder.clockworkmod.com/downloads/9c04800ec6b5c5ea58365b92efa669bf.img
I can't access the sdcard from the shell, but no more errors.
 
Will someone download the recovery, load it to their phone, make a nandroid backup, and post it here for us?

To do this, download the file, rename it to recovery.img and push it to the phone using
Code: 
adb push recovery.img /sdcard
flash_image doesn't work on our phones, since the layout is much different.
To install, run
Code: 
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17
from terminal or adb shell as root.

If you are not rooted, you should be able to acquire root from the default recovery and adb shell, though I haven't tried it.
 
The recovery works no E: misc errors but i can't backup
i get "ClockworkMod Recovery v5.8.4.5
SD Card space free: 2977MB
Backing up boot image...
Eroor while backing up boot image.

This is how i flashed
adb reboot bootloader
fastboot erase recovery
fastboot flash recovery C:\recovery.img
 
OK, so in recovery, the sd card shows up as /dev/block/mmcblk1 (no p1). probably need to update the fstab to reflect this to allow the mounts and storage menu to work. the line will probably read something like

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

I get the error while backing up boot image as well. It makes the directory on the sd card but doesn't write any files.

It seems there's an error mounting the /boot partition. I can't go in and manually mount it from the shell, either. It seems that mount doesn't like the mtd fstype?
 
chui101 said:
OK, so in recovery, the sd card shows up as /dev/block/mmcblk1 (no p1). probably need to update the fstab to reflect this to allow the mounts and storage menu to work. the line will probably read something like

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

I get the error while backing up boot image as well. It makes the directory on the sd card but doesn't write any files.

It seems there's an error mounting the /boot partition. I can't go in and manually mount it from the shell, either. It seems that mount doesn't like the mtd fstype?
Click to expand...

No errors are good. You have my build. :)
Fixing the fstab is trial and error, really. And I don't have a normal filesystem at the moment (cause I'm devvin' :p) so I didn't know how accurate my result was.

I'll add your suggestions and build again. Just a moment....
 
I don't know if this will help but here is the partitions list

major minor #blocks name

7 0 40572 loop0
7 1 4190 loop1
7 2 7308 loop2
7 3 5229 loop3
7 4 24980 loop4
7 5 5229 loop5
7 6 16664 loop6
7 7 11466 loop7
179 0 1765376 mmcblk0
179 1 1024 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 4096 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 28672 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 462848 mmcblk0p15
179 16 1048576 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 102400 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 4096 mmcblk0p24
179 32 1902592 mmcblk1
179 33 1901568 mmcblk1p1
254 0 40572 dm-0
254 1 4189 dm-1
254 2 7308 dm-2
254 3 5229 dm-3
254 4 24979 dm-4
254 5 5229 dm-5
254 6 16663 dm-6
254 7 11466 dm-7
 
Code: 
# busybox fdisk -l /dev/block/mmcblk0p7

Disk /dev/block/mmcblk0p7: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p7 doesn't contain a valid partition table

Sounds to me like the mtd fstype is right, but the recovery kernel doesn't contain mtd support. I'm trying to figure out how to build recovery.img myself... but all i can find is how to build the cm9 recovery. not very helpful.

Although, if we could pull the cm9 recovery image from the e739 we might be able to use it!
 
chui101 said:
Code: 
# busybox fdisk -l /dev/block/mmcblk0p7

Disk /dev/block/mmcblk0p7: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p7 doesn't contain a valid partition table

Sounds to me like the mtd fstype is right, but the recovery kernel doesn't contain mtd support. I'm trying to figure out how to build recovery.img myself... but all i can find is how to build the cm9 recovery. not very helpful.

Although, if we could pull the cm9 recovery image from the e739 we might be able to use it!
Click to expand...
I have that recovery. I'll add the fstab to it, and see what happens.
 
chui101 said:
AHHHHH. Uh, better not do that, on second thought. Looking back on page 1, looks like there had to be a few boardconfig.mk tweaks to get it to boot...

i've already got the cm7 and cm9 sources for my vibrant, so i'll try following koush's instructions here: My Brain Hurts: Porting Clockwork Recovery to New Devices
Click to expand...

You can use the latest source, clockworkmod builder does, and we've had boots with it.
All we need is mtd support in the kernel, plus the custom recovery.fstab.

When I unbrick my phone, I'll work on it if nobody's done it by then.
 
i can send you a dump of my /system partition if that would help - if you can get to a shell so you can dd it...?
 
chui101 said:
i can send you a dump of my /system partition if that would help - if you can get to a shell so you can dd it...?
Click to expand...
I flashed old recovery and I have a shell.
Also, if we have this dump, and it works, I'll make a thread for unbricking without the updater program.
 
PM sent. This isn't the fully stock /system partition though, some of the bloatware has been removed. It' should hopefully restore to a functional state though!
 
OK, I figured it out. In the recovery.fstab, the /boot and /recovery should be fstype emmc, not mtd. this should let nandroid backup the boot partition properly as a block device, not an mtd.

this is what i have for a recovery.fstab:
Code: 
# mount point   fstype          device                  [device2]

/cache          ext4            /dev/block/mmcblk0p18
/data           ext4            /dev/block/mmcblk0p16
/sdcard         vfat            /dev/block/mmcblk1p1       /dev/block/mmcblk1
/system         ext4            /dev/block/mmcblk0p15
/boot           emmc             /dev/block/mmcblk0p7
/recovery       emmc             /dev/block/mmcblk0p17
 
chui101 said:
OK, I figured it out. In the recovery.fstab, the /boot and /recovery should be fstype emmc, not mtd. this should let nandroid backup the boot partition properly as a block device, not an mtd.

this is what i have for a recovery.fstab:
Code: 
# mount point   fstype          device                  [device2]

/cache          ext4            /dev/block/mmcblk0p18
/data           ext4            /dev/block/mmcblk0p16
/sdcard         vfat            /dev/block/mmcblk1p1       /dev/block/mmcblk1
/system         ext4            /dev/block/mmcblk0p15
/boot           emmc             /dev/block/mmcblk0p7
/recovery       emmc             /dev/block/mmcblk0p17
Click to expand...
Here. http://builder.clockworkmod.com/downloads/d65aa666b636f43e0e304d4fccf0e3f1.img
 
Fully working CWM is now here! Bring on the CM9!!!!!!!!

Doing a nandroid backup as we speak! Probably can't post this one though, since the juicy details of my girlfriend's life may be on there ;)

Edit: Started a new thread on this! MyTouch Q is ready for prime time!
 
You must log in or register to reply here.
Back
Top Bottom