yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] davidvanwijk:
only download mode available

Hi,

I am hoping for some advice.

I had working cm13 on galaxy s2. Recovery was "recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100".

I made a big mistake. I updated this recovery to "twrp-3.0.2-1-i9100".

Now my phone does not boot anymore. I get stuck in the familiar screen with triangle. It is however possible to bring the phone in download mode. Recovery is not possible anymore.

What to do? I use a linux computer and am familiar with the command line.

Thanks for help,

David
[Galaxy S II Original Android Development] Lanchon:
that is not a big mistake, it's not a mistake at all.

did you flash the new TWRP on the boot partition instead of the recovery partition?

-if not, then your phone could be failing.

-if yes, then you need to flash a kernel img file via download mode. use Heimdall (an old version might be in your distro repo) to flash the kernel partition. you can use the kernel img from the CM zip package if you are using CM, or download one of my kernels and extract the img from the zip. google a heimdall thread or create one, heimdall is off-topic this here, thanks!
[Galaxy S II Original Android Development] davidvanwijk:
Thank you for your reaction. I used heimdal (phone in download mode) to replace recovery with updated one. I suppose this will be on the recovery partition...

If so I have to flash a kernel? Do you have a link for one of them?

Thanks again, David

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S II Original Android Development] Lanchon:
you need to flash a kernel like i said. i didn't say flash a recovery! google my trim kernels.
[Galaxy S II Original Android Development] davidvanwijk:
I tried and failed. See what happened.

root@groenwijk-Vostro-1500:~/Downloads/kernel-lanchon-i9100# sudo heimdall flash --kernel boot.img --no-reboot

Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Claiming interface...

Setting up interface...

Initialising protocol...

Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.

Please be patient!

Session begun.

Downloading device's PIT file...

PIT file download successful.

ERROR: Partition "kernel" does not exist in the specified PIT.

Ending session...

Releasing device interface...

What did I do wrong?

Thanks again,

David
[Galaxy S II Original Android Development] Lanchon:
the name of the partition is KERNEL, not kernel. please do not post anything else Heimdall related to this thread, i WILL NOT answer. look for a proper thread or create one. thanks
[Galaxy S II Original Android Development] davidvanwijk:
how to update recovery to "twrp-3.0.2-1-i9100"

Thanks for your answer. I had succes in installing this kernel and my phone is working again with CM13.

However, now I am back at the position I was: with recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab). I wanted to update to "twrp-3.0.2-1-i9100.img".

How do I do this? Is this question appropriate in this thread? I am relatively new here ... :confused:

And again: thanks for your help!

David
[Galaxy S II Original Android Development] Lanchon:
not really, there is a i9100 TWRP thread here. if you just googled...

but hey, just follow the official install instructions!

"TWRP Install (Requires TWRP 2.8.4 or higher already installed)"

https://twrp.me/devices/samsunggalaxys2i9100.html
[Galaxy S II Original Android Development] nospamboz:
Some more info. The new Gello browser downloads from twrp.me fine, but the regular CM13 browser still only 5.1K, so not fixed on the server side.
[Galaxy S II Original Android Development] AddictedToPlaying:
I'm actually on 2.8.2.0 TWRP and i'm trying to flash 2.8.7.0 isorec. When i flash it it says completed, but when i restart recorvery there's still old one.

Tried to update by flashing .img file of twrp 3.0 but i have no select button to choose .img files becoz im on 2.8.2..
[Galaxy S II Original Android Development] the.gangster:
And you are very likely on a non-IsoRec-supporting kernel...
[Galaxy S II Original Android Development] daniu:
Hi

Which kernel?

Just a theory: are you using a pre-isorec-twrp-kernel?

Regards

Sent from my x-phone using brain 2.0
[Galaxy S II Original Android Development] the.gangster:
Sure he does. Or are there ones with an 2.8.2.0 out there?
[Galaxy S II Original Android Development] IAndrikaXC:
Hey everyone

i want to ask , i am still on stock rom JB and stock Recovery

which one i must flash first , top up CM13 / CM12.1 ?

i being confused , they are 2 type in first post

kernel and recovery and the name have CM11 , CM12 , CM13

so which one i must too flash , i am still on stock

thanks
[Galaxy S II Original Android Development] chhapil:
You can use my Dorimanx build for JB, it has isorec support.

Check arnab's thread for twrp recovery.

Both have to be flashed separately
[Galaxy S II Original Android Development] IAndrikaXC:
Btw can dorimanx kernel flash with stocl kernel ?

After install thay , what should i do next ? Install cm13 or what ?

Sorry many ask bro , i just confused with this samsung hehe
[Galaxy S II Original Android Development] Lanchon:
hi [MENTION=5194378]McConnor[/MENTION],

please always post on a public thread and never PM, thanks!

regarding your request for IsoRec for the i9100g, i made changes to the 3 recent branches of CM's kernel so that it can boot an IsoRec recovery:

http://review.cyanogenmod.org/#/c/148391/

http://review.cyanogenmod.org/#/c/148392/

http://review.cyanogenmod.org/#/c/148393/

it's your responsibility:

-to lobby to have these changes accepted into CM.

-to lobby to have these changes cherry picked into whatever unofficial CM ports or CM-based kernels you care about.

-to ask anybody who builds recoveries for the i9100g that they release IsoRec versions. (I will help them do this if they approach me.)

-to ask an i9100g TWRP builder to shoot for official TWRP support.

i won't build any i9100g recoveries, sorry about that.

please report your progress if any to this thread.

thank you!
[Galaxy S II Original Android Development] McConnor:
Thanks for your reply! As I don't know of any Person who builds Recoveries for the i9100G I think we are stuck here. While searching I also couldn't find a thread here for our phone only for the i9100.

I hope anyone monitoring this thread might jump in for help - maybe [MENTION=414800]arnab[/MENTION] who builds for the i9100 might lend a Hand - we i9100G owners would be delighted...

Gesendet von meinem GT-I9100G mit Tapatalk
[Galaxy S II Original Android Development] :
[MENTION=5194378]McConnor[/MENTION]

Sorry for OT, but HERE you will find development for the G
[Galaxy S II Original Android Development] Lanchon:
I entered further changes to CM:

http://review.cyanogenmod.org/#/c/148396/

http://review.cyanogenmod.org/#/c/148397/

http://review.cyanogenmod.org/#/c/148398/

these changes the standalone recoveries produced by the CM tree so that they are IsoRec compatible.

(without these changes the produced recovery files are basically trash: just exact duplicates of the official kernel.)

the standalone recoveries are published here:

https://download.cyanogenmod.org/?device=i9100g

these changes are a necessary step to have official TWRP some day.

again it's your responsibility to lobby for these changes to be accepted. if they are, you'll immediately have working cm-11 recoveries to use with any newer CM build.
[Galaxy S II Original Android Development] McConnor:
Thanks, I am regularily active there already. It is just that there is nobody deleveloping an TWRP Recovery for this phone.....

---------- Post added at 10:04 AM ---------- Previous post was at 09:37 AM ----------

Thank YOU very much! That is much more than we could have hoped for! I directed this info to the most active dev for our phone - perhaps he can make something of it. Nobody should say we didnt at leas try :). I will report back I something comes of it.
[Galaxy S II Original Android Development] adxamg:
I'm building unofficial cm13 and cm12.1 roms for i9100g. I'm using own repos. I will implement these patches.

In cm12.1 builds we are already using twrp, based on omnirom sources. After adding device-tree patch, it should produce a flashable isorec-compatible recovery.img.

Will test this and report back.
[Galaxy S II Original Android Development] Lanchon:
yes. the second patch will produce isorec recovery.img files that you can dd or root adb push straight over the RECOVERY partition: /dev/block/mmcblk0p6 (if you adb push, you must use this device node and not the 'by-name' symlink to it).

but in order for any isorec recovery to boot, you need the first patch applied in the kernel ramdisk.

thanks!
[Galaxy S II Original Android Development] Lanchon:
just a detail to bear in mind:

TWRP has an "install image" button in the install zip section to flash raw kernel and recovery images. after pressing it and selecting an image file, TWRP will ask for the destination partition: either kernel or recovery.

TWRP must be configured at build time so that the right partition is flashed in either case. please test this functionality as it will probably be preferred means to upgrade TWRP once IsoRec is merged in your builds.
[Galaxy S II Original Android Development] Lanchon:
and another tidbit that you may find useful:

through arnab's and Dees_Toy's work we found that TWRP images for i9100 built on a CM13 kernel will not boot on CM12.1 kernels. the reverse works fine, as kernels are supposed to be backwards compatible with respect to userland.

for this reason, the official i9100 TWRP is built against an Android 5 kernel. (and it apparently works fine on all kernels since CM11.)
[Galaxy S II Original Android Development] adxamg:
Unfortunately build stopps after applying these patches. When i revert change to usr/i9100g_initramfs_files/init it's building normally. Did i miss something?

Construct recovery from boot
mkdir -p /android/system/out/target/product/i9100g/obj/PACKAGING/recovery_patch_intermediates/
PATH=/android/system/out/host/linux-x86/bin:$PATH /android/system/out/host/linux-x86/bin/imgdiff /android/system/out/target/product/i9100g/boot.img /android/system/out/target/product/i9100g/recovery.img /android/system/out/target/product/i9100g/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p
source and target don't have same number of chunks!
source chunks:
chunk 0: type 0 start 0 len 17610
chunk 1: type 2 start 17610 len 15892468
chunk 2: type 0 start 8399893 len 67
target chunks:
chunk 0: type 0 start 0 len 3484082
build/core/Makefile:1054: die Regel für Ziel „/android/system/out/target/product/i9100g/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p“ scheiterte
make: *** [/android/system/out/target/product/i9100g/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p] Fehler 1
make: *** Auf noch nicht beendete Prozesse wird gewartet …
make: Verzeichnis „/android/system“ wird verlassen
[Galaxy S II Original Android Development] Lanchon:
the init file in question is not processed on build time (but it is executed on boot), it is just compressed and included in the ramdisk. this means that the contents of this file should not be able to alter the flow of the build (but it does affect boot).

are you sure you reverted the init patch and not the makefile patch?

can you provide links to your repos?

thanks!
[Galaxy S II Original Android Development] adxamg:
github.com/xdaamg

I first removed changes to shbootimg.mk in device tree and it did not work. Then i removed patch to usr/i9100g_initramfs_files/init and build was ok again.

init is the same as i9100.
[Galaxy S II Original Android Development] Lanchon:
it probably was the makefile change. you might have needed to force a clean build and you didnt, maybe.

normally kernel and recovery are very similar, the both carry a kernel (the same kernel) and a different ramdisk. for this reason, stock android (that usually flashes recovery on boot to ensure recovery gets updated to the version that matches the current OS), instead of carrying a full recovery image, it carries just the binary difference between kernel and recovery, and uses the current kernel + diff to flash recovery.

the bin diff file is "recovery_from_boot.p", which is what is failing to build. this is reasonable, since kernel and recovery are now completely different! (no shared kernel, the recovery is just a compressed packed ramdrive.)

in i9100 we use:

https://github.com/CyanogenMod/andr...-common/blob/cm-13.0/BoardCommonConfig.mk#L48

you should use it too in i9100g because i9100g (until now) did not have a separate recovery! however i see recovery downloads here:

https://download.cyanogenmod.org/?device=i9100g

but not here:

https://download.cyanogenmod.org/?device=i9100

so the i9100g CM tree seems to be misconfigured. it tries to create the diff file, and fails. i dont know why.

solution:

1) either add:

https://github.com/CyanogenMod/andr...-common/blob/cm-13.0/BoardCommonConfig.mk#L48

2) or experiment by trying this:

https://github.com/CyanogenMod/andr...common/blob/cm-13.0/BoardConfigCommon.mk#L128

the second option seems to skip the binary diff, it takes effect here:

https://github.com/CyanogenMod/android_build/blob/cm-13.0/core/Makefile#L1045

i am fairly confident that 1) may work. about 2), i really don't know.

3) you can leave the makefile patch out. you won't produce an isorec recovery, but you can make one by hand by compressing with lzop -9 the recovery .cpio file. this is worse solution by far.

please tell me what happens. thanks!
[Galaxy S II Original Android Development] adxamg:
Just checked it again. As soon as i apply patch to shbootimg.mk, build fails.

Build was started with deleted out-dir.

TARGET_NO_SEPARATE_RECOVERY := true was already set in BoardConfig.mk
[Galaxy S II Original Android Development] Lanchon:
ok so it's the makefile patch as i suspected.

-well you can try option 2) above

-or this setting: TARGET_NOT_USE_GZIP_RECOVERY_RAMDISK

ideally the recovery_from_boot.p file should not be generated, as recovery and kernel are completely different. instead android should bundle a full recovery.img if needed.
[Galaxy S II Original Android Development] adxamg:
I implemented kernel change in a cm13 test build. Modifying shbootimg.mk did not work, so i will make isorec recovery based on ramdisk-recovery.cpio (cm12.1 build) with lzop by script now. twrp source is omnirom android-6.0.

Should it work like this?
[Galaxy S II Original Android Development] Lanchon:
yes! booting of isorec in your kernel should work. and the recovery image should work with other kernels that implement isorec for that device, BUT only as long as they are android 6+ kernels. probably wont work with LP kernels.
[Galaxy S II Original Android Development] adxamg:
Building recovery based on omnirom twrp 2.8 branch android 5.1 seems to work.

But when i try to build isorec recovery based on my cm12.1 build, including omnirom/twrp sources branch android 6.0, i'm running into build errors. Can not build target shared libraries 'libbase' needed for 'uncrypt' and 'minadbd'.

Not shure how they managed to build twrp 3 isorec on i9100?
[Galaxy S II Original Android Development] Lanchon:
but does this have anything to do with isorec? building isorec recovery is exactly the same as building a kernel with recovery, only that you capture the intermediate recovery-ramdrive.cpio file.

so are you having problems building twrp in general or something specific about isorec? if a general problem, i cant help, i never built twrp. you can ask Dees_Troy, twrps author. also, arnab built twrp 3 for i9100, and now is maintaining the official twrp for i9100.
[Galaxy S II Original Android Development] adxamg:
Latest builds of unofficial i9100g cm12.1 and cm13 supports isorec boot support.

Flash instructions and isorec twrp recovery for i9100g can be found here.

It was tested and confirmed to work.
[Galaxy S II Original Android Development] playitlouder:
//delete please
[Galaxy S II Original Android Development] kamal.rana:
I am on resurrection remix rom 6.0... I flashed the TWRP zip file and now have the same as recovery... I wanted to know is it the same as ISOREC and of permanent nature or my recovery would change when I flash rom again?
[Galaxy S II Original Android Development] November Rain:
Hi, I'm new here.

Sorry if it's been asked. I'm on stock 4.1.2, which kernel should I flash?.

Thanks so much.
[Galaxy S II Original Android Development] ssanjy:
Once you are on IsoRec compatible recovery, which I think almost all MM ROMs support, then your recovery should not change unless you flash IsoRec disabler...

You should flash unofficial dorimanx by [MENTION=4354573]chhapil[/MENTION] here
[Galaxy S II Original Android Development] Lanchon:
not exactly. if you flash isorec compatible KERNELS (or roms with such kernels), then your previously flashed isorec recovery will remain in force.
[Galaxy S II Original Android Development] hewhomustnotbenamed:
Hey bro.. How do I install the latest official 3.0.2.1 ISOREC TWRP for i9100 on n7000?

You say in the OP that it can be used for n7000 also.

what do I need to do before flashing it? (I cannot flash it directly I suppose)
[Galaxy S II Original Android Development] Lanchon:
please dont quote any unrelated post!

please read the appropriate section in the OP
[Galaxy S II Original Android Development] Lanchon:
note that the n7000 patcher is untested so far and i imagine it can fail. the n7000 has a different display resolution (i didnt know this when i made the patchers) and it is possible that the screen might be messed up. if you want to try it, make sure you have access to root in android so you can erase the isorec recovery partition from there in the worst case. you might also be able to adb shell to TWRP from a PC to recover, even if the screen is garbled.
[Galaxy S II Original Android Development] hewhomustnotbenamed:
Apologies

---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------

I might not want to take this risk cz I do not have that much knowledge. So, I guess I would refrain from using the i9100_official_3.0.2.1_TWRP for now.. Will go ahead with the one provided by Bauner
[Galaxy S II Original Android Development] MLDamazigh:
hi every one i need some help please

i am on stock 4.1.2 and i want to flash CM13 but i must increase system partition first, should i flash IsoRec ??? should i use another kernel than stock before flashing this recovery??? and which one????

please help me i am confused
[Galaxy S II Original Android Development] Lanchon:
you don't even say which device you have! this is the isorec development thread. read, then post on some appropriate thread if necessary. there is a lanchon REPIT thread.
[Galaxy S II Original Android Development] MLDamazigh:
I9100

Envoyé de mon GT-I9100 en utilisant Tapatalk
[Galaxy S II Original Android Development] Lanchon:
flash official CM13 **without gapps** which supports isorec, then flash some version of isorec TWRP via flashable zip (dont ask me where to get it!), then reboot recovery and you are in TWRP. now upgrade TWRP to latest version via img file and reboot recovery again. now start repartitioning with my REPIT.
[Galaxy S II Original Android Development] MLDamazigh:
Ok but before flashing CM13 i need to flash recovery first ???

Envoyé de mon GT-I9100 en utilisant Tapatalk
[Galaxy S II Original Android Development] Droidriven:
If you don't have custom recovery yes. If you already have it then just follow what he told you.
[Galaxy S II Original Android Development] Lanchon:
this is the IsoRec thread, no posts on how to flash CM here!!! go and ask in the right thread as i told you please
[Galaxy S II Original Android Development] jamu08:
[MENTION=4141005]Lanchon[/MENTION].....I have got isorec 3.0.2-1 installed in i9100 running RR 6.0.1 after repit 1GB /4GB partition. Can i flash any type of rom/kernel irrespective of isorec compatibility? or i have to careful choosing rom/kernel. In some thread there is a discussion on isorec disabler. When and what circumstances one should disable isorec. Is isorec is only for TWRP? or CWM also support isorec. which one to consider Isorec TWRP or isorec CWM How to confirm that i have got isorec installed. Please clear the doubt
[Galaxy S II Original Android Development] the.gangster:
[MENTION=7538263]jamu08[/MENTION]

check the opening post for links where you find both, TWRP and CWM-based isolated recoveries.

The disabler is especially for one purpose:

- you have a kernel that supports IsoRec recoveries

- you have installed an IsoRec recovery in the past (usually no matter when as they survive the standard flashing actions)

- you want to use the kernel embedded recovery instead of the IsoRec recovery

(all above have to apply)

So the best example I can currently think of:

- You have a DorimanX kernel installed (newer builds support IsoRec recoveries)

- still have a full-size preload partition

- want to use dual boot

Again: All above have to apply.

:)

Maybe it got clearer now.
[Galaxy S II Original Android Development] Lanchon:
if you flash a non-isorec kernel, your currently flashed isorec recovery will not boot anymore. only the recovery bundled with the new kernel will boot.

you could say that an isorec kernel includes a 'loader' that can load an isorec recovery (if it finds one that was previously flashed). a loader is necessary to boot an isorec recovery. no loader, no fun!
[Galaxy S II Original Android Development] fireburner-de:
[MENTION=7538263]jamu08[/MENTION] Maybe it could be added, that an IsoRec Recovery does not influence a non-IsoRec ROM at all.
[Galaxy S II Original Android Development] hksaaa:
[MENTION=4141005]Lanchon[/MENTION]

can you explain how to install step by step for n7000. Thanks.
[Galaxy S II Original Android Development] McConnor:
How many more steps than already in the opener would you like to see? I don't know if I ever have seen a more thourough op than this one - I am sure you can make something of it by reading it very carefully...

Gesendet von meinem SM-G930F mit Tapatalk
[Galaxy S II Original Android Development] Lanchon:
please note that the n7000 TWRP patcher is untested so far untested. i have my doubts that it will work correctly, given that the device has a different screen resolution, but somebody has to try it sooner or later. make sure that you are able to recover using download mode (by flashing another isorec recovery using heimdall or by flashing a non-isorec compatible kernel), or by zeroing the RECOVERY from android itself using dd, or from android by using a recovery flashing app (flashify maybe?).
[Galaxy S II Original Android Development] hksaaa:
I found this TWRP http://xdaforums.com/devdb/project/dl/?id=18063 , flash from philz and everything works
[Galaxy S II Original Android Development] DaveX2012:
Will this work on I9100 ?

---------- Post added at 02:46 PM ---------- Previous post was at 02:40 PM ----------

just installed lastest cm 12.1 from HERE and installed your kernel but can't reboot into recovery it's loops in recovery. Suggestion? [MENTION=4141005]Lanchon[/MENTION]
[Galaxy S II Original Android Development] the.gangster:
[MENTION=4715058]DaveX2012[/MENTION]

Why don't you simply take the native ones for i9100 linked already in the OP???

EDIT:

btw don't use 12.1 snapshot as it still suffered from freeze bug. Check the 12.1 thread to find either latest nightly (20160203) where all that was fixed already or even current (inofficial) builds that even got patched with latest security fixes.
[Galaxy S II Original Android Development] DaveX2012:
Can't find cm 12.1 thread. That's the only cm 12.1 i can find. Can you point me to cm 12.1 thread?
[Galaxy S II Original Android Development] the.gangster:
[MENTION=4715058]DaveX2012[/MENTION]

These are the official threads for i9100: CM12.1 and CM13