Help For Installing On Galaxy Tab 2 10.1 GT-P5113
Is it possible to install the Galaxy Tab 2 10.1 GT-P5113?
Because when I run the cmd in my 'Downloads' directory on my linux box where all the files are at;
~/Downloads/Replicant $ ls
boot.img p5110.md5 recovery.img system.ext4.img
In the above /path I run;
sudo heimdall flash --BOOT recovery.img --RECOVERY recovery.img
It complains about there not being a BOOT /path...
Please see the attached file heimdall print-pit output
Apparently, yes, using the p5110 images. We haven't tested ourselves but it theory, it seems possible.
Apparently the correct command line is:
sudo heimdall flash --KERNEL recovery.img --RECOVERY recovery.img
I must check whether this is a mistake I made on the guide or something specific to your version of the tablet.
Well I don't want to be the guinea pig here and brick this thing, if I was rich and could afford I'd say the hell with it and have at it...
Does anyone working on Replicant have a GT-P5113 at their disposal, if not, any plans on when it might be before having a working image for this version?
You can take it for my word that you will not brick your tab. Even if it doesn't work, if follow the instructions, you cannot possibly brick the tablet. You may have to reinstall something like CyanogenMod which is known to work, but that's as far as it gets.
Apparently I have to review the install guide, so if the heimdall command fails, retry by replacing BOOT with KERNEL
Does anyone working on Replicant have a GT-P5113 at their disposal
No, and I doubt that's going to happen.
if not, any plans on when it might be before having a working image for this version?
About as long as waiting for 1/n == 0
A software error can cause a brick, bricking isn't by simply missing steps.
So could you please explain why you think it can't be bricked?
And cm runs on the tablet...
Frankly, I don't see how a software error would brick the device. It would have to somehow erase the bootloader partition or flash to the wrong partition, which has no reason to happen if you follow the instructions. Anything like a segfault in the middle of the transfer would not be able to brick the device.
Basically, as long as the bootloaders are in place, there is a way to recover easily (through USB). What you do with the system and kernel partitions doesn't change anything to that.
I already have cm with twrp.
Can I use twrp to install Replicant, if so how would I do this?
Most roms I'm aware of that use twrp are zipped as just directories, apps and files, etc to install from...
Please follow the installation instructions (which involve flashing CWM recovery). Most likely, only our recovery image will work to install the Replicant images (only Replicant uses that format of images instead of zips).
Would it be difficult to eventually change Replicant for a zip to work this way?
If it's not to difficult to change for my device that would be great and I can test this out for you.
I have a lot going on with my tablet that I don't want to change, to much work at the moment to change everything.
Frankly, I don't see any advantage of using a zip instead of images except that they could be installed by any recovery (but is that really an issue, given that we provide our own recovery anyway?). I really don't like the idea of the zip packages containing the bare files and scripts to install them. Using a filesystem image looks a lot cleaner to me. Moreover, that makes it possible to flash the images directly through the bootloader on devices that support it.
The thing I like using twrp and it seems to be widely supported.
So I'm trying to stick to a bit of a standard way of doing things, otherwise I have to wipe everything out install the Replicant Recovery, then I don't know if that works for other roms and if not, well, a lot of bouncing back and forth and work.
Since you mention you don't like zip you might want to consider carefully what you just said. What is a zip, it's an archive, what is a .tar file in Linux? Both of them Archives and in Linux there are distributions just like the one I use Slackware that installs an entire OS from archives. So in all honesty there's nothing wrong with it and I've yet to see any computing OS install from one single image file either.
Actually there's nothing cleaner about an img file or zip, just different formats, differnet ways to skin a cat is all, LOL. It's just a preference and what your goals are really and both accomplish the same end result.
Look at it like this, this should all work on any Android Distro like any Linux PC Distro when it comes to installing the system. All the various Android Distros should not be requiring special recovery systems built only for that particular distro, that just locks people in.
So maybe in newer releases, I'll consider using zip packages, but it means that:
- I have to check that it all works correctly on all devices and doesn't include anything nasty
- I have to make it produce replicant-looking names
- And mostly, I have to rewrite the installation guides
So the answer I'll give you is that I have better things to do currently, but I'll keep that it mind and we'll probably get there someday :)
I have the same tablet, and when I installed Replicant about a month ago, I got the same error. I just tried omitting the --BOOT argument, and it worked.
Thanks Paul, sounds good, look forward to it, then it will also be nice to build it too...
Ahh Legimet, good thanks...
Well, you'd better replace --BOOT with --KERNEL, so that it can boot directly to recovery (instead of just flashing the recovery partition).
Note that the installation instructions have been fixed now.
Well, I used Power+Volume Down to boot into the recovery partition.