Building recovery

---

I've started a device tree for the GT-P6200 on github. Right now it's very basic, but it does build a working `recovery` binary for the PT-6200. You still need to drop it into an initramfs and compile a kernel with said initramfs (I'll publish my initramfs on github this week, it's basically kanged from garyd9's PT-6210 one anyways). Thanks to garyd9 for getting the ball rolling on ClockworkMod Recovery for these tabs.

btw, this is the first step of porting CyanogenMod 9 (ICS) to the GT-P6200. Right now my device tree is very basic, with a lot of the initial stuff being kanged from teamhacksung's Galaxy SII device tree. It doesn't build anything that you can flash to your device (yet!). I'd love for input (preferably code!) and help. Keep an eye on the repository, and fork it if you're interested:

https://github.com/alanorth/device_samsung_galaxytab7p

how about the new "touch" recoveries??

Originally Posted by chrisrotolo

how about the new "touch" recoveries??

Yeah, I was thinking about that myself. I think it'd be nice to have a touch recovery. ClockworkMod is really easy and portable... but there are other really cool recoveries out there, like TeamWin's recovery.

Edit: Ooh, "porting" touch recovery was really simple: extract sbin/recovery from some CWM Touch initramfs out there (such as this one for Nexus S), stick it in a PT-6200 initramfs, and rebuild your kernel with said initramfs. Bingo.

I've attached a working Touch Recovery for GT-P6200. Be warned, it's not compatible with backups you've made in previous versions; you'll have to recreate backups!

Flash like this, from Download Mode:

heimdall flash --recovery p6200_cwm_5.8.0.2_touch.img

Don't ask about Odin. I don't use that closed-source stuff, and I don't use Windows. Booya. Someone could make a zip I guess... any volunteers? I'm too cool for zips.

awesome, I thought it would be fairly easy.

functions OK otherwise beside said issue?

EDIT: .ZIP Pulled -- stuck at backing up data. I know its usually the longest, but I just flashed stock yesterday. I will wipe caches and retry once more.

very nice I have to say.

hangs at backing up data... for a while now, (10+ minutes) and I just returned to stock yesterday, there cant be that much data.
Will pull the .zip if it doesnt finish. (progress bar is @ 90+%)

Perhaps we could get this to display the realtime info: To see if its actually moving or not? It may be there just cut off the screen. Thanks!

this is a working.zip with root and busy-box
enjoy....

sure, but did you try making a nandroid? mine gets stuck at backing up data.

Originally Posted by chrisrotolo

sure, but did you try making a nandroid? mine gets stuck at backing up data.

I actually only tried flashing a zip, rebooting recovery, navigating the menus etc. Didn't try a backup!

I can't think of why the backup wouldn't work, as long as the right partitions are mounted. All I've done is repackage our existing recovery kernel with a new sbin/recovery binary. Everything else is the exact same, including the recovery.fstab, which list the block devices and their mount points.

Maybe I'll try to compile from source instead of stealing the pre-compiled binary from another device's recovery.img. This one came from a Nexus S recovery. I'll look around for the source... though I get the feeling it hasn't been released...?

@chrisrotolo... regarding your log, I see this repeating a few times:

failed to open /sys/class/android_usb/android0/state: No such file or directory

Well in Linux /sys is not a real file system (it's populated by the kernel, and contains various devices, parameters, and kernel tuneables)... and that sysfs node doesn't appear to be anything related to recovery. Let me try to do a nandroid on my tab and I'll get back to you.

Something work verifying, though, is the output of `adb shell mount` in both garyd9 and my recoveries. In "traditional" ClockworkMod Recovery the source had to be customized to set the buttons which control the select, etc. With touch, I don't think there's anything we have to configure (and like we said, we're using the same recovery.fstab as the old CWM).

Originally Posted by aorth

@chrisrotolo... regarding your log, I see this repeating a few times:

failed to open /sys/class/android_usb/android0/state: No such file or directory

Well in Linux /sys is not a real file system (it's populated by the kernel, and contains various devices, parameters, and kernel tuneables)... and that sysfs node doesn't appear to be anything related to recovery. Let me try to do a nandroid on my tab and I'll get back to you.

Something work verifying, though, is the output of `adb shell mount` in both garyd9 and my recoveries. In "traditional" ClockworkMod Recovery the source had to be customized to set the buttons which control the select, etc. With touch, I don't think there's anything we have to configure (and like we said, we're using the same recovery.fstab as the old CWM).

it is fully working for me i have backed up and restored

damn.. so its just mine? I just odined back to stock2 days ago, havent downloaded anything. wiped cache and dalvik, hangs at backing up data.

will try fac reset and try to backup again.

thanks for the help guys.