yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] XeLLaR*:
AW: [TWRP 2.4.1.0 works, but ATTENTION: Do not use CWM 6.0.2.7 !]

Hmmm. Older kernel. Why dont we just ask arco what kernel he used at that time to compile his cwm creation? I think it would be easier for us to make a fully working recovery for us if we know what ingridients we need.

Its kind of easy to compile cwm, just head over to build.clockworkmod.com and upload your sources. No need for linux anyway. TWRP is another thing..but i think its possible that we can make a stable recovery.
[Galaxy S Plus I9001 Android Development] edisile:
R: [TWRP 2.4.1.0 works, but ATTENTION: Do not use CWM 6.0.2.7 !]

God damn it... i flashed cwm 6 touch yesterday... now can i flash cwm 5 without f#ckin' up my phone?

Inviato dal mio frigo a pedali.
[Galaxy S Plus I9001 Android Development] hiej:
it does not matter, I've tried starting in recovery also after battery removal, same behaviour: most of time I have shut downs.

as said before with version 2.4.4.0 if I dont restore cache partition the process go to the end correctly.

With 2.5.0.0 there's no way to go to the end.
[Galaxy S Plus I9001 Android Development] Jonboy2011:
buffo why are there two Version of recovery , cm9 and cm10 ? what will happen if i flash cm9 Version while i'm on cm10 and vice versa ?
[Galaxy S Plus I9001 Android Development] buffo1987:
You can use any version with any rom. It is just the code base it was compiled from. I started building on cm10 but as i do not own a i9001 i can not test if that version is more stable or performant than cm9. You have to test that.
[Galaxy S Plus I9001 Android Development] buffo1987:
If you need USB-Storage please try 2.4.4.0 Versions from OP. There it should work. Looks like the last change in code about partition handling is wrong. TWRP 2.5.0.0 has been officially released with the same sources I compiled it.

Please check the 2.4.4.0 Versions usb etc works. If not have to check my building environment.
[Galaxy S Plus I9001 Android Development] Sepp-Wurzel:
TWRP 2.5.0.0

Hi

this morning I flashed TWRP-2.5.0.0-ariesve_2013_04_09_kernel_2.6_cm10 after phone shut down while playing solitair..

I flashed Cache and dalvik and afterwards I wanted to backup the system to external SD. Here the recovery also shut down, tried it once more, again shutdown. Than I rebooted and had a shut down while reboot.

Now tried again, first backing up to internal SD, everything ok, than to external SD, also ok.

Greetings,

Sepp
[Galaxy S Plus I9001 Android Development] OverClockeD_GR:
anyone know what maybe the problem for shutdown on backup? trying to do a backup and every time phone just shutdowns.
[Galaxy S Plus I9001 Android Development] magicw:
Which version?

Try rebooting into recovery either from recovery itself or from ROM prior to backing up or restoring.
[Galaxy S Plus I9001 Android Development] OverClockeD_GR:
cwm 5.5.0.4

cwm 6.0.2.8 kernel 2.6

twrp 2.4.4.0 /2.5.0.0

all shutdown on backup i enter recovery with vol up+power

before i had cwm 6.0.1.9 had some backup before entering cm10 i remember before lot time.. now i flashed it again to check and it gets shutdown when trying to backup...
[Galaxy S Plus I9001 Android Development] magicw:
try starting recovery per restart as proposed already
[Galaxy S Plus I9001 Android Development] matthias1203:
I still using twrp 2.2.1. I never had any problems, reboots, or anything else.

Is there any reason for move to 2.5.0.0?
[Galaxy S Plus I9001 Android Development] Jonboy2011:
more functions but never touch a running system , if you are happy , keep twrp 2.2.1 :)
[Galaxy S Plus I9001 Android Development] OverClockeD_GR:
i was always with cwm and first time tried twrp 2.5 its nice its touch!!! i like the looks of it.. is 2.2 touch too? well still trying to find a recovery that i can do backup without shutdown....
[Galaxy S Plus I9001 Android Development] Jonboy2011:
yes its touch too and it backup and restore wirhout reboot :)
[Galaxy S Plus I9001 Android Development] OverClockeD_GR:
ok mate this is amazing!! i did reboot to recovery from the rom. and i did a full backup !!!!!!!!!!! woooooooooooow first time!!!!!!!

so the problem for shutdown during backup was because i was entering recovery with vol up and power buttons!!

thnx a lot
[Galaxy S Plus I9001 Android Development] smeroni68:
@buffo1987:

is it possible to report on first post with BIG TEXT that using the

reboot to recovery

option of the rom, seems stabilize the recovery working?

This hint has been given many times, but I think is not highlighted over there!!!
[Galaxy S Plus I9001 Android Development] buffo1987:
Can someone please test the 2.4.4.0 versions on OP (under Old Versions), as i cleaned my building environment, and recompiled the latest (and last) 2.4.4.0 Versions. It would be interesting if at least in these last Version USB mounting is working. Otherwise there is something wrong with my sources.

Thanks in advance
[Galaxy S Plus I9001 Android Development] sv2hqx:
on cm10 there isnt usb storage

on cm 9 i yes
[Galaxy S Plus I9001 Android Development] kasper_h:
Isn't that related to recovery.rc/recovery.fstab used during compiling the recovery?
[Galaxy S Plus I9001 Android Development] sv2hqx:
i just downloaded both of them on cm9 there is a tab

on 10 nop

on cm10 pc can see the storages but cant open it
[Galaxy S Plus I9001 Android Development] echoff666:
I'm wondering why is there this difference?
[Galaxy S Plus I9001 Android Development] smeroni68:
Don't really knows why... but it give a big difference to users that had problems of reboot and so on...
[Galaxy S Plus I9001 Android Development] sv2hqx:
talking about usb mount

a friend call me and said that on win7 and win8 cant recognize android devices when switch to recovery cwm or twrp

anyone know something about that???
[Galaxy S Plus I9001 Android Development] Aliante:
2.4.4.0 final cm10: mount NOT OK (button is missing)

2.4.4.0 final cm9: mount OK

2.5.0.0 2013_04_09 cm10: mount NOT OK (button is missing)

2.5.0.0 2013_04_09 cm9: mount OK (but does not seem 100% reliable)

With 2.5.0.0 cm9, at first attempt, mount was not working, then after further attempts it started working (maybe after deleting .twrps)

Additionally, using the Unmount button does nothing (the phone folders remain available on my PC)

So on my side cm9 is working on both version, even if 2.5.0.0 seems still a bit "unreliable" for daily use.

EDIT: inverted CM9 and CM10 results to report correct findings
[Galaxy S Plus I9001 Android Development] Aldokazer:
Yeah that's true for me too.

But, why so? What is its root cause?
[Galaxy S Plus I9001 Android Development] echoff666:
I have tested it and works for me, but I can't use it when I have a broken rom and I can't restart by power menu. What a pity! I like this version, but I will come back to twrp 2.2.2.1 for EMMc matter.

By the way, is this matter true? Do I solve it using the 2.2.2.1?
[Galaxy S Plus I9001 Android Development] miloytyn:
You can also do it from recovery by selecting reboot to recovery from there. It seems to have same effect as booting to recovery from ROM.
[Galaxy S Plus I9001 Android Development] smeroni68:
OK, your point of view is clear... but for what reasons you rom is broken? If you experiment a lot, I can imagine, but normally how much times you get this situation of "broken rom"?

I had only a couple of times over an year...
[Galaxy S Plus I9001 Android Development] smeroni68:
@buffo1987:

another useful information to highlight on first post...
[Galaxy S Plus I9001 Android Development] echoff666:
I like to try some modification done by my self, and they don't always work :( . But restarting by recovery, as suggested, it's a good solution :good:
[Galaxy S Plus I9001 Android Development] smeroni68:
Now is clear... I had the right idea... you are an experimenter!!! Good luck!!
[Galaxy S Plus I9001 Android Development] buffo1987:
To be on the safe-side i advice to first eject the device on your pc and second unmount within recovery.

So i will switch to CM10 for future releases.

(Of course these releases can be used with any rom (just to prevent questions :D))
[Galaxy S Plus I9001 Android Development] XeLLaR*:
Hey buffo, i have a question regarding this reboot the recovery to be stable thing.

Isnt it possible to make the recovery reboot itself after boot?

I mean if you press VolUP+Power the recovery starts, and then directly a reboot to be stable. Is that possible?

Greetz

Xellar

Gesendet von meinem GT-I9001 mit Tapatalk 2
[Galaxy S Plus I9001 Android Development] Aldokazer:
Why the f*** didn't I think of this before?

+1 mate.
[Galaxy S Plus I9001 Android Development] buffo1987:
I will look at that, but how can we manage to not get into a boot-loop?
[Galaxy S Plus I9001 Android Development] XeLLaR*:
Hmm, a very good question. Ill search for an answer this weekend.

Gesendet von meinem GT-I9001 mit Tapatalk 2
[Galaxy S Plus I9001 Android Development] buffo1987:
It would also be helpful if someone can provide logs of shutdowns.
[Galaxy S Plus I9001 Android Development] XeLLaR*:
Where can i find the log?

Gesendet von meinem GT-I9001 mit Tapatalk 2
[Galaxy S Plus I9001 Android Development] buffo1987:
You can use adb logcat (perhaps you need to wait a little bit after booting twrp to let adb start)

http://developer.android.com/tools/help/logcat.html

adb logcat > log.txt pipes the output to a file, which you can post

Good Night, hope tomorrow or the next days there will be some usefull logs, thanks for testing XeLLaR*
[Galaxy S Plus I9001 Android Development] IceTe:
Are you sure? sv2hqx reported it the other way round if I understood it right.
[Galaxy S Plus I9001 Android Development] sv2hqx:
i downloaded again and i tried again

and at my past 2 posts i said that on 2.4.4 cm9 there is a usb button and it works

on 2.4.4 cm10 there is no usb button

pc can see sd card and external sd but cant open it
[Galaxy S Plus I9001 Android Development] sv2hqx:
another thing too

in the versions 2.2.1 2.3.2.1 and 2.4.4.0 if you boot in recovery and stay there in about a minute

screen has a time out

goes black and locks

have to press home and swipe to unlock,but its stay in this mode

so in 2.5.5.0 if you stay in recovery at home screen ,phone reboots to rom

if you have chose another function like install or usb mount ect phone shuts down and charge
[Galaxy S Plus I9001 Android Development] buffo1987:
And what is your report?
[Galaxy S Plus I9001 Android Development] sv2hqx:
sorry wrong post
[Galaxy S Plus I9001 Android Development] Aliante:
Looks like logging is not available when in recovery:

Z:\ADB>adb logcat
/sbin/sh: exec: line 1: logcat: not found

To work around this problem I have mounted the system partition and taken the logcat command from system/bin to sbin:

Z:\ADB>adb shell
~ # cp /system/bin/logcat /sbin/
cp /system/bin/logcat /sbin/
~ #

Afer that, logcat is working, but I get only few (useless) lines:

Z:\ADB>adb logcat
--------- beginning of /dev/log/main
I/ARMAssembler( 108): generated scanline__00000077:03545402_00000000_00000000 [ 30 ipp] (44 ins) at [0x408741e8:0x40874298] in 91552 ns
I/ARMAssembler( 108): generated scanline__00000077:03545402_00000A02_00000000 [ 31 ipp] (53 ins) at [0x408742a0:0x40874374] in 91552 ns
I/ARMAssembler( 108): generated scanline__00000077:03545402_00000A01_00000000 [ 31 ipp] (52 ins) at [0x40874378:0x40874448] in 61035 ns
I/ARMAssembler( 108): generated scanline__00000077:03545402_00000A08_00000000 [ 31 ipp] (53 ins) at [0x40874450:0x40874524] in 61036 ns

I have tried to copy the service command from system/bin to sbin to see if I could use it to enable the logcat service manually:

Z:\ADB>adb shell
~ # cp /system/bin/service /sbin
cp /system/bin/service /sbin
~ # service
service
link_image[1916]: 184 could not load needed library 'libutils.so' for 'service' (link_image[1916]: 184 could not load needed library 'li
bcorkscrew.so' for 'libutils.so' (reloc_library[1331]: 184 cannot locate 'tgkill'...
))CANNOT LINK EXECUTABLE

It looks like something which is falling outside of my knowledge needs to be done to enable logcat in recovery... :(

---------- Post added at 01:02 PM ---------- Previous post was at 12:56 PM ----------

SORRY MY FAULT: I messed it up

CM9 - OK

CM10 - NO BUTTON
[Galaxy S Plus I9001 Android Development] IceTe:
Sorry, have no means to test right now.

But as aliante states in his post, the cm9 version seems to be the working one.
[Galaxy S Plus I9001 Android Development] buffo1987:
New Versions for download - all compiled with kernel 2.6

TWRP-2.5.0.0-ariesve_2013_04_14.zip - 4.91 MB

CWMRecovery-6.0.3.1-ariesve_14.04.2013.zip - 4.44 MB

CWMRecovery-6.0.3.1-touch-ariesve_14.04.2013.zip - 4.13 MB

These are my last releases, i'll stop cause of lack of time and device.

Perhaps someone else can continue. I have updated my guides for compiling recoveries, if someone needs help he can pm me

http://xdaforums.com/showthread.php?t=2132672

http://xdaforums.com/showthread.php?t=2132718
[Galaxy S Plus I9001 Android Development] XeLLaR*:
Thanks for all of your work Buffo!!
[Galaxy S Plus I9001 Android Development] Stefano187:
Thank you very much for your hard work made for the i9001's community. Best wishes

Regards

Stefano

Inviato dal mio IdeaTab A2107A-H usando XDA Premium HD app
[Galaxy S Plus I9001 Android Development] anuseb89:
Thanks to u for all ur contributions to our small community..
[Galaxy S Plus I9001 Android Development] davidteri91:
OK I tested the new twrp 2.5 but I can't see option to mount memroies from recovery anyway thanks buffo

Inviato dal mio GT-I9001 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] mACSman:
TWRP-2.5.0.0-ariesve_2013_04_14 - USB mount NOT worked (no USB mount button) :(
[Galaxy S Plus I9001 Android Development] buffo1987:
I think i can fix that. Problem seems to be the same that we had before with roms + kernels + usb:

rom compiled from 2.6 sources + kernel 3.0+ => no usb

rom compiled from 3.0+ sources + kernel 2.6 => no usb

usb only when rom + kernel compiled for same base. So the fix by ivendor makes recovery "brick-save" but kills usb.

I guess CWM 6.0.3.1 has also Problem with USB? CWM Touch maybe not.

Fixed (at least i hope so) TWRP 2.5.0.0

TWRP-2.5.0.0-ariesve_2013_04_15.zip - 4.83 MB
[Galaxy S Plus I9001 Android Development] XeLLaR*:
How can this be?

I am using a CWM 5.5.0.4 Recovery, made when the first CM9 build from arco was released. And i use CM10 R1 from ivendor....

Usb mounting is working.

2.6 Recovery + 3.0 Rom = USB Mount possible here.

Gesendet von meinem ariesve mit Tapatalk 2
[Galaxy S Plus I9001 Android Development] davidteri91:
OK buffo this build working very well and I can mount my memories thanks for all

But this build is compile with kernel 2 or 3 ????

Inviato dal mio GT-I9001 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] tsirhcitna:
Isn't he talking about the rom where he compiled? Not your actual rom...
[Galaxy S Plus I9001 Android Development] rickvrolings:
I also doubt about the 2.6+3.0 not working part.

As far as i know, all the aspects of recovery are independent from the system partition and the system kernel. The recovery has his own independent kernel.

Btw. Im just a guy that reads some stuff around xda. I might be wrong.
[Galaxy S Plus I9001 Android Development] buffo1987:
You are right. And cause the new 2.5 works, I guessed right. Perhaps you can test usb on latest cwm versions and give feedback.

Cm9 branch 2.6.

The build before was cm10 branch 3.0 compiled with kernel 2.6 for Recovery, so usb failed.

All versions on first post are kernel 2.6 versions
[Galaxy S Plus I9001 Android Development] Sepp-Wurzel:
Hi,

is it possible to restore a recovery of TWRP with CWM? I have instand switch offs when restoring with TWRP 2.5.0.0. So I would like to try CWM.

Thanks,

Sepp
[Galaxy S Plus I9001 Android Development] buffo1987:
Try the big red hint on first post. TWRP and cwm is not compatible.
[Galaxy S Plus I9001 Android Development] Sepp-Wurzel:
I did so, when I wanted to restore at first time. But right now I have no starting system. I´m trying to restore only system and boot and than go back to recovery from system.

Update:

Restoring worked after I rebooted the recovery out of the recovery itself.
[Galaxy S Plus I9001 Android Development] mACSman:
TWRP-2.5.0.0-ariesve_2013_04_15.zip - 4.83 MB => perfect worked usb-mount :laugh: thanks buffo :good:
[Galaxy S Plus I9001 Android Development] EB20XY:
Sounds good. But did you a backup and restore with the new 2.5 from 15.4. already ?

Can you restore olde backups from 2.4 and older ?
[Galaxy S Plus I9001 Android Development] davidteri91:
I make and restore backup without SOD

Inviato dal mio GT-I9001 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] mACSman:
I did 2x full backup and restore, no SOD (new 2.5 from 15.4)

Old backup not testing.
[Galaxy S Plus I9001 Android Development] EB20XY:
TWRP 2.5.0.0

OK.

The new version 2.5.0.0 from 15.4. really seems to work fine.

Thanks !
[Galaxy S Plus I9001 Android Development] stepie22:
Hey guys (and gals), I don'y know if the shutdown problem has been fixed or not. I just skimmed through the unread posts, becouse its *very* late right now.

I no longer have the shutdown problem, and I know for sure now TWRP is the cause of it. I'll quickly tell you how I got it working:

but first, why i did it. accedentally restored a incomplete backup from TWRP ( ment to delete it ). Because of that, I had a 8mb system partition. Of cource I couldn'y boot. So what I did to fix it ( i couldn't use recovery-it would shutdown in the middle of a flash). SO i used Odin (tutorial). I flashed BroodROM RC5. It included it own recovery ( I think feamod - I cant remember). It had no shutdowns. I flashed CWM 6.0.3.0, still no shutdown. Then TWRP, I tried backing up - that caused a shutdown. I don't think a shutdown happeded while not backing up, but I cant be sure. Afther bout 2 backups shutdowns, the random shutdowns were back, and flashing back to CWM didn't help. So I flashed odin again and then CWM. I am dissapointed that I cant use TWRP, but atm I'm fine with CWM.

ps. You should factory reset/wipe data when you flash BroodROM RC5 with Odin, otherwise it won't boot.
[Galaxy S Plus I9001 Android Development] buffo1987:
Perhaps you can try latest cwm (touch) 6.0.3.1 from first post, it would be nice to get some feedback.
[Galaxy S Plus I9001 Android Development] OverClockeD_GR:
I guess you did reboot to recovery from inside twrp or from the rom itselff??sorry for asking but this solved my backup shutdown...
[Galaxy S Plus I9001 Android Development] stepie22:
Ok, I'll try it out, will report back tomorrow.

Edit: I tried it, everything works. (backup, restore, fix premissions, wipe cache's, etc. I just didn't test the factory reset.)

Which one?? :confused: Both work for me atm.

Odin rebooted into recovery. After that I flashed CWM and re-rebooted into recovery. I never left recovery. Now I can go to recovery from CM10.1 and with the buttons.

If anyone can get logcat working completely I'll try it out gain with TWRP. Just on weekends, I do not need to accedentally lose my phone again.:eek:
[Galaxy S Plus I9001 Android Development] davidteri91:
Buffo if you can compile a twrp with kernel 3 for me because I see Arco deleted MMC_CAP_ERASE from code if you want I can Test

Inviato dal mio GT-I9001 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] buffo1987:
Here you go:

TWRP-2.5.0.0-ariesve_2013_04_21_davidteri.zip - 5.26 MB

It is save to use on all i9001, please test usb.
[Galaxy S Plus I9001 Android Development] davidteri91:
Ok works and USB works too thanks bro
[Galaxy S Plus I9001 Android Development] alexisguitarra:
Sorry for asking this but I want to be sure due to the risk of bricking my phone, Is version 15-04 totally safe?
[Galaxy S Plus I9001 Android Development] davidteri91:
Arco delete the code in kernel 3 "MMC_CAP_ERASE"
[Galaxy S Plus I9001 Android Development] buffo1987:
All versions are save to use. Versions until 15.04. Are compiled with kernel 2.6.

All newer versions are compiled with fixed kernel 3.

Save to use means that it should be as save as any software on xda. Use at your own risk!
[Galaxy S Plus I9001 Android Development] davidteri91:
Buffo I installed my Beta 4.2 and Gapps , kernel without SODS make a backup and restore without SODS thanks for last version :)
[Galaxy S Plus I9001 Android Development] spaazm:
I've been on TWRP 2.4.1.0 (2.4.4.0 was restarting recovery wedge I tried fixing permissions, so I downgraded immediately), but since I've diagnosed my emmc chip as a bad one I had to change it. I couldn't recall what kernel was it built on and the thread I downloaded it from removed it from OP.

I've flashed your TWRP 2.5.0.0. So far I've cleared cache, dalvik, fixed permissions, backed up and restored nandroid. Installed new kernel. I can get to recovery by hard keys combination and both rebooting from recovery and ROM. It all works fine.

If I ever discover any bugs I'll let you know.

Thank you!

⇜ SGS+ ↭ SlimBean 4.2.2 build 3 ↭ K^Kernel JB V1.7 OC exUV 390MB ↭ InfinityEngine V2.1 ⇝
[Galaxy S Plus I9001 Android Development] EB20XY:
What 2.5 variant do you use ? The one from post #452 ? Or from post #1 from 15.04.2013 ?
[Galaxy S Plus I9001 Android Development] spaazm:
It's TWRP-2.5.0.0-ariesve_2013_04_15 from first post. Why?

⇜ SGS+ ↭ SlimBean 4.2.2 build 3 ↭ K^Kernel JB V1.7 OC exUV 390MB ↭ InfinityEngine V2.1 ⇝
[Galaxy S Plus I9001 Android Development] ktulu84:
because the one from post #452 is compiled over a 3.0.x kernel but it should be safe because arco removed the MMC_CAP_ERASE code in the source
[Galaxy S Plus I9001 Android Development] spaazm:
I've read it, but is there any reason I should update? I mean I can flash all ROMs at 2.6.x based one and it works fine for me.

⇜ SGS+ ↭ SlimBean 4.2.2 build 3 ↭ K^Kernel JB V1.7 OC exUV 390MB ↭ InfinityEngine V2.1 ⇝
[Galaxy S Plus I9001 Android Development] ktulu84:
i think he would like to know if it is really safe, since you said you have a bad chip (as me :D) and you said your recovery worked well if it was the one compiled over 3.0 kernel this could be a proof of the safety of this recovery (i will continue to use CWM 5 because i'm not brave enough)
[Galaxy S Plus I9001 Android Development] buffo1987:
To remove "MMC_CAP_ERASE" is the official solution by samsung in their sources
[Galaxy S Plus I9001 Android Development] davidteri91:
+1
[Galaxy S Plus I9001 Android Development] spaazm:
Thank you.

Both versions of 2.5.0.0 TWRP in this thread are now safe if I understand that correctly. The one compiled with 2.6.x and 3.0.x kernels.

But is there any reason whatsoever that I should switch from the one with 2.6.x to the one with 3.0.x kernel? Maybe except the satisfaction. ;)

⇜ SGS+ ↭ SlimBean 4.2.2 build 3 ↭ K^Kernel JB V1.7 OC exUV 390MB ↭ InfinityEngine V2.1 ⇝