Lanchon / REPIT

A Device-Only Data-Sparing Repartitioning Tool For Android
159 stars 25 forks source link

Installation fails with latest TWRP/repit on a I9100 #66

Closed markusfisch closed 7 years ago

markusfisch commented 7 years ago

Installation of the latest lanchon-repit-20160923-system=1G-data=6G-sdcard=max-preload=min+wipe-i9100.zip from the download link in the README.md fails with:

...
Installing update...
E:Can't run /tmp/update_binary (No such file or directory)
E :Error in /tmp/sideload/package.zip
(Status 255)

The reason seems to be that the shebang in /tmp/update_binary references #!/sbin/sh which does not exist.

The device is a standard I9100 with the latest official updates from Samsung:

Model: GT-I9100
Android-Version: 4.1.2
Baseband: I9100XXLS8
Kernel-Version: 3.0.31-889555 dpi@DELL228 #3 SMP PREEMPT Thu Jan 31 14:48:54 KST 2013
Buildnumber: JZO54K.I9100XWLSD

I tried the latest repit release for the I9100 from the linked androidfilehost.com:

lanchon-repit-20160923-system=1G-data=same-sdcard=max-preload=min+wipe-i9100.zip
806KB Oct 02, 2016 | 01:16PM

As well as

lanchon-repit-v0.1-sys1GB-data6GB-i9100.zip
8.9KB Feb 13, 2016 | 06:56PM

from oldfiles/. Same result. I renamed the first file according the README to have data partition of 6G:

lanchon-repit-20160923-system=1G-data=6G-sdcard=max-preload=min+wipe-i9100.zip

The flashing procedure was as follows:

Am I missing something important here?

PS: sorry for the piggybacking of #20 but I'd thought you'd rather like to have one issue for a problem and not multiple issues for the same problem.

the-gangster commented 7 years ago

You missed the fact, that the recovery you finally launched is not the TWRP-recovery that you flashed in the step before, but still the stock recovery, as the recovery in the recovery-partition is only launched by kernels that support IsoRec. One option would be flashing an IsoRec-supporting DorimanX kernel for your 4.1.2 JB. This one should work

markusfisch commented 7 years ago

Ah, thank you very much! So many pitfalls...

Lanchon commented 7 years ago

thanks so much, @the-gangster.

@markusfisch, why do you use stock? the stock kernel is severely broken by a couple of high profile bugs such as fpbug. the old android don't even trim the emmc.

you should at a minimum use CyanogenMod kitkat, the latest nightly that was available (or even better, a newer unofficial build) with a trim-enabled kernel such as mine. CM 13 apparently works well too.

markusfisch commented 7 years ago

@Lanchon yes, I've already updated the kernel. I just wasn't aware the stock kernel wouldn't boot the recovery partition and tried to change as little as possible.