yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] HellcatDroid:
That is correct, as of yet it does not work on the older "S1" I9000.

However, I'd figure these things are rather similar on the two devices, unfortunately I don't have an I9000 to try and test things, and I am not fond of putting low level things like this into the wild without having it tested myself first.

On the bright side, a buddy of mine has an I9000, maybe I can convince him to let me root it and try/test a few things.

If there is want/need/demand/interest, I can surely try :)
[Galaxy S II Android Development] CatalystWon:
Thanks anyway.

In that case, can you suggest a reputable tool to Backup+Restore EFS for the i9000m? I understand the importance of this and want to do it properly.
[Galaxy S II Android Development] HellcatDroid:
Sorry, no idea about I9000 tools....

But my buddy just agreed on rooting his and to let me try not to totally kill it :D

i.e. in time kTool will be compatible to the I9000 series models as well.
[Galaxy S II Android Development] ricey1986:
Just curious, but ive backed up my efs folder several roms ago with this tool and just ran a check on the backup. It came back at 92%. What would of changed and will the backup still work? Cheers for any info.

Ricey
[Galaxy S II Android Development] HellcatDroid:
Yep, that is perfectly normal.

From what I've seen so far it changes by 80 bytes on each reboot and even more after flashing a ROM.
[Galaxy S II Android Development] Wollired:
Danke für die sehr gute Arbeit!!!

und nu auch die Sicherheit für mein Note :-)
[Galaxy S II Android Development] HellcatDroid:
:)

BTW: kTool has been updated to v1.35:

- added "advanced options" page with first function to format EFS for cases where you want to restore a .tar or other individual files but /efs is stuck/locked in read-only due to filesystem corruption

- should work on AT&T's S2 variant as well now.
[Galaxy S II Android Development] :
Add a confirmation to the button.. N00bs may screw up their efs just to see what that option does.. Confirmation will make it securer :D
[Galaxy S II Android Development] HellcatDroid:
Pff, long done already :p
[Galaxy S II Android Development] :
Always a step ahead :D

Keep up your amazing work mate!
[Galaxy S II Android Development] guitarz:
i did some backup, but after few hours, i check the file and only 99% matches.

I9100 tried on several rom already
[Galaxy S II Android Development] HellcatDroid:
Try to read this thread, the answer to this has been given about 3 to 4 times, incl. in the first post.
[Galaxy S II Android Development] Damienoid:
I prefer this tool for flashing zips now to CWM, so thanks to hellcat, but what I want to know if I can flash .tar files with this tool.

If so, how do I go about this?

I'm just testing some modems, and some are in .tar format, I want to switch modems on the go in different locations.
[Galaxy S II Android Development] HellcatDroid:
Huh? Don't you mean the other way round?

It can open .tar files now and you can flash the kernel, modem or param.lfs from it.

What kind of .ZIP do you mean? CWM .ZIPs or just "normally" zipped kernels?
[Galaxy S II Android Development] Damienoid:
Double Huh? Not sure I know what you mean there :rolleyes:

That's what I was asking, how do you do it?

It has an 'Open .tar update pack' and the first time I opened it, it told me to create a folder on my SD card called /sdcard/Update.tar which I did, but 'Open .tar update pack' still can't find it.

So I was asking for help here.

All zips work wonderful on your tool, there is no issue there with HC-kTool, or CWM for that matter ;)
[Galaxy S II Android Development] HellcatDroid:
Ah, I see.

Nono, don't create the /sdcard folder, /sdcard refers to the internal storage.

Just drop it onto the internal storage, without any subfolders.

For example, if your PC sees the int. storage as E:\ copy it it to E:\update.tar :)

Ok :)
[Galaxy S II Android Development] GadgetCheck:
?? :confused: what do u mean
[Galaxy S II Android Development] Damienoid:
Ok I must still be missing something as that is what I'm trying to do as far as I understand it, but it doesn't work for me.

First you say Just drop it onto the internal storage, without any subfolders.

Then you say copy it to update.tar, is that not a folder you create in your internal storage?

Either way I do it, whether I copy my .tar files directly to my internal storage just as I do with my zips, or put them in a folder I created called update.tar, your tool shows nothing when I open .tar update pack option in your tool.

So obviously I'm missing a step here...:confused:
[Galaxy S II Android Development] HellcatDroid:
Rename the .tar to update.rar and copy it to the internal storage with no subfolders what so ever.
[Galaxy S II Android Development] x9745:
Hi I have the backup file and I try to reinstall back the imei, but can't do it. I think i also mess up the back up (cos rename a few time) , pls anyone could help, by doing step by step? thanks in advance.
[Galaxy S II Android Development] HellcatDroid:
How did you make the backup? This tool or another one or manual?

And do have a c.tar.gz or .img backup file?
[Galaxy S II Android Development] Damienoid:
Sorry I still can't figure out how to flash a .tar with your tool, no matter how/what/rename I try to place the tar file on my internal storage.

The tool simply does not see any tar files.

I'm not that nOObish, but I can't make it work following your instructions, which was hard to find in the first place.

Nevermind, I'll just zip everything and save myself the hassle.

HC-kTool is still my preferred choice for flashing zips, as it's never let me down before, where CMW has, so I thank you for that...
[Galaxy S II Android Development] cholywell:
GT-I9100M

Would it be possible to add support for the GT-I9100M? It is the Bell Canada version. It is 100% identical to GT-I9100 international. I had to edit the model number in the build.prop file to get this to work.

Thanks!
[Galaxy S II Android Development] HellcatDroid:
I'll see to get an update done tonight with the 9100M added to the list of supported devices.

Or maybe I'll just rewrite the model detection completely to detect all GT-I9100* variants as vaild.
[Galaxy S II Android Development] Si14:
Thank you for your interesting app. Mine is also GT-I9100M, Android 2.3.3. I wonder if I can use it on this Android version or I need to upgrade it?
[Galaxy S II Android Development] HellcatDroid:
Should work fine :)

If do run into troubles thoug, just let me know and we'll them :D

// EDIT

Just pushed the update that should now also work on the I9100M to the market.

Please let me know if it does/doesn't work :)
[Galaxy S II Android Development] xinfinityoO:
i get

/sdcard/efs.img found

---------------------

mount returned: 255

(unable to mount image - image corrupted?)

/!\nv_databin NOT FOUND in backup !!!

the efs.tar.gz seems to be ok

whats with that error message
[Galaxy S II Android Development] HellcatDroid:
What version of kTool are you using?

Update to the latest one and try again.

If it still doesn't work:

- what ROM?

- what kernel?

- what exact version of kTool

- tried to create a new backup and check again, maybe the .img IS corrupted?
[Galaxy S II Android Development] xinfinityoO:
the latest version fro the market ..just updated today..

using turkbey rom 29.2

pda xwkk5

phone xxkl1

kernel is siyah 2.4.2

i tried the backups 3 times.. still the same issue
[Galaxy S II Android Development] HellcatDroid:
OK, I'll try it on Siyah 2.4 and see what's happening.

// EDIT

OK, flashed Siyah 2.4.2 and tryed with an existing .img and also making a new one, everything worked fine.

This is rather weird....
[Galaxy S II Android Development] xinfinityoO:
bummer.. i tried again..same problem..oh well

edit

worked finally

i think the problem was that superuser was nit able to give it permssion fast enough before it attempted to mount the image..maybe u can put a sleep command or somethng
[Galaxy S II Android Development] HellcatDroid:
That is very interesting, thanks for the info.

Will definitaly address that!
[Galaxy S II Android Development] x9745:
Sorry, was away for two days. Yes I am using this tool and found a efs backup folder with a few back up xxxxxxxtar.gz, as xxxx is the date. Next what should I do?

Thanks for your reply.....
[Galaxy S II Android Development] jonny_ftm:
Just came across a severe security issue here

- I updated from 1.30a to 1.35b through market

- Run a backup job and run the check

- After that, phone locking with pattern is disabled and only stock unsecure locking remains

- After reboot, pattern lock is activated again

Tried uninstall and new install, same issue, pattern lock disappears each time a backup is completed with the check after that. Reboot needed to reset the lock

I can't understand what your app plays with to alter the phone security???

Phone is SGS2 KI4 v2.3.4 rooted with CF-Root v4.2

Please fix and mainly tell us how come it plays with the security access? More investigations needed.

I uninstall and won't put it back in the phone unless clarified

Many thanks
[Galaxy S II Android Development] HellcatDroid:
@x9745:

Those backups are not from kTool.

Use the backups kTool made to /sdcard/efs.img and/or /sdcard/efs.tar.gz for the most easy restore.

@jonny_ftm:

Why do I have the feeling you just want to hype some random panic here?

First off, kTool doesn't touch any security settings at all, besides the EFS that it is backing up.

Then, I just tried what you just said, made a few backups, checked them and all - my lockpattern still works as supposed to.

Maybe somthing else is going wrong in the background on your phone.

So, please stop claiming the app would prepare your phone be stolen or whatever you are ttying to say there.

I WILL look into this, as I have an idea what could cause the lockscreen to disappear, but since you are rather unwillingly to help it will take some longer.
[Galaxy S II Android Development] jonny_ftm:
Sorry for any misunderstanding. I maybe posted on the angry of discovering that issue. I'm not a programmer and couldn't see why a simple backup tool would alter my security settings without any prompt.

I found it enough serious, but could use other words indeed, sorry as I agree you're surely providing one of the most useful tools around.

And yes, I can help with providing any info you like, by PM or on this post.

I'll try to be more regarding with my next posts on this topic

Thanks again for your help and support
[Galaxy S II Android Development] HellcatDroid:
:)

Sounds cool.

What would help me:

What kernel are you running while experiencing this?

Can you paste me the output BEFORE and AFTER it happens of

mount

Does the check succeed or fail when the lockscreen disappeared?

(Maybe re-run the check once it has happened)

Lock PIN, password or pattern?

To try to repproduce:

- fresh boot up

- make backup and check

- BANG! Lockscreen gone here?
[Galaxy S II Android Development] cholywell:
It works great! Thanks for this great tool.
[Galaxy S II Android Development] jonny_ftm:
Firmware info:

Kernel is:

CF-Root-SGS2_XW_NEE_KI4-42-v4.2-CWM4

Outputlog: this is what you mean by /code?

The check succeeds even when I run it again

The lock is with pattern

After fresh boot, problems happens every time, even after fresh reinstall after a reboot, tested many times and again tonight

Also, only a reboot will restore my pattern lock

Simply launching Ktool, no backup job, won't affect the pattern lock security

No need to run "check" for the bug to happen. The lock pattern security is disabled just after the backup job finished, even without touching the dialog at the end prompting to switch to check mode

Edit: Now, after a reboot, I start Ktool and only run the check, no backup job: the check will fail -80 bytes differ- (but this is expected I believe as EFS is written on every reboot). However, the lock pattern security remains active. It seems the backup job is the culprit here

Hope it helps you

If more info is needed, let me know
[Galaxy S II Android Development] xethor:
If I stole your Galaxy SII I would just wipe and flash a new rom. The pattern would be useless! ;)
[Galaxy S II Android Development] HellcatDroid:
lol, that too, yeah.
[Galaxy S II Android Development] jonny_ftm:
delete the message please
[Galaxy S II Android Development] HellcatDroid:
Well, out of 6000+ downloads, this is the only report about this I got.... so kinda hard to figure out or even reproduce....

Can you please do the following things:

fresh reboot

In a terminal shell (app or via adb) BEFORE running kTool type this:

su
mount

make kTool mess up your lock pattern

go to a terminal shell again and once more run the above commands

su
mount

paste me the output (or a screenshot) of BOTH times you ran the "mount" command.

If you're up for some more "debug help", please also try this:

fresh reboot (=lock OK)

terminal shell:

su
busybox umount /efs
busybox mount /dev/mmcblk0p1 /efs

try if screenlock works, if the "mount" gave any error message, please paste it here

It seems (eps. judging after the edit of your other post) that the EFS isn't remounted anymore after making the backup (to make the .IMG dump it has to be unmounted to get a "clean" dump, "unclean / not properly unmounted" filesystems tend to corrupt and the backup would be useless).

Okaaaay, and last but not least (or maybe this actually should be the FIRST thing) just for the sake of trying everything possible, could you try the test-build I attached to this post?

Yeah, that's it so far.

Oh, and thank's for the 1-Star rating, that REALLY motivates one to spend his personal free time to hunt for those phantoms in a FREE app (BTW, that was sarcasm).
[Galaxy S II Android Development] HotlipsH:
Keep up the good work. Ignore those who rather pay and get zero support from corporate apparently. Merry Christmas!
[Galaxy S II Android Development] HellcatDroid:
:) Thanks :)

And will surely do, this kind of stuff is way too much fun for me :D

YES!

You too! And everybody else! HAVE HAPPY HOLIDAYS EVERYONE!
[Galaxy S II Android Development] jonny_ftm:
Before the tests you asked for, I have more interesting results:

I just got a new SGS2 for my wife and tried ktool on it, the market version. It is same firmware, official KI4 v2.3.4. But, this time the root was made through zergRush method.

**

Well, 3 interesting things:

1- the bug is the same, still present, despite the 2 phones don't have same other apps installed. Lock pattern is disabled until reboot

2- the efs.tar.gz file is only 17 KB and these folders are spread on sdcard:

- .tmp.untar

- .tmp.f

- .tmp.mnt.efsimg

The check though say 0 bytes differ!

3- When trying to mount SD card on PC through the microUSB, the phone logo shows it mounted, but it doesn't show on PC. After clicking on unmount button on phone and unplug USB cable, the lock pattern is back without a reboot. So yes, it seems to be related to a bad mount

**

Now back to my SGS2 phone, the one rooted with CF_Root

:

1- using your new attached Ktool Test1 still gives the lock pattern bug

2- the efs.tar.gz file also is only few KB but I don't see the tmp folders as on the second SGS2 rooted with zergRush

3- also, mounting sd card on PC fails after Ktool, but unmounting through phone resuscitates the pattern lock

All tests on both phones were conducted 3 times, after a complete reboot each time

**

Another user on market confirms my same issue

on SGS2 with a different firmware than mine, so not only me and my phones

**

EFS Pro doesn't show that issue with both my i9100 phones

**

I also have a major question

:

Since you say Ktool did unmount my EFS folder and not remounted it, would it mean the phones affected are messed up? Have I to fix something now? Does it mean the app can f**k up the IMEI it is supposed to backup?

Hope that with these info you can get it sorted.

Let me know if you still need the logs via su

Sorry, I respect your work and consider well it's on your free time and a free app. But why should I give a misleading rating? It just doesn't work and even messes up thing. I always rate apps and edit my rating after things are fixed, corporate or free.

And you'll just see a new 1 star rating from the phone of my wife, to prove it :D

Also I see another user reported the issue on SGS2 with another firmware

I will continue to support you through debugging it, also on my free time :) (I have an EFS backup through another way on the forum)

Good luck

No need to troll. Why should we consider it is working perfect when it fails + bugs on SGS 2 (tried 2 i9100 and another user on market just reported it too, so not only me)

That's the purpose of it, most users will have to wipe it and don't get in my data as they like
[Galaxy S II Android Development] HellcatDroid:
1) stop needlessly panicing AGAIN, no, it can NOT mess up your IMEI, STOP MAKING USELESS PANIC HYPES!

2) Oh, ANOTHER 1-Star rating, just because of a bug? On a FREE app no one is forcing you to use?

OK, you know what, have fun trolling the market, for the time beeing this story is over for me.

1-Star ratings are for apps that totally don't deliver what they promise, not for BUGREPORTS.

Having my free time dissed like this is not worth it.
[Galaxy S II Android Development] HellcatDroid:
You didn't even bother runnjng the shell commands, thanks a lot for the help....
[Galaxy S II Android Development] jonny_ftm:
Sorry you take it that way. I try to be constructive and I didn't post any comment about your app messing IMEI on market :(

On both phones app DOESN'T WORK, at least the tar file seems too small. Also it puts so many tmp files on my second phone. I personally won't try a restore if I have issues until it is fixed. I'd go with EFS Pro.

Look at the length of my previous detailed post: you think I'm trolling here or I'm taking my free time to help you debug it? EFS Pro works for me, so just doing it free for helping, just like you are doing with your app.

Anyway, I can't trust a developer that get pissed off if someone reports even a bug about his app. And like it or not, it seems not working as expected on SGS 2 and it is not only me.

I also won't loose my time on debugging it. Wish you good luck with someone else having an SGS2

Merry Christmas and best regards

---------- Post added at 11:47 PM ---------- Previous post was at 11:34 PM ----------

I took much time to detail you with more info and tests about the issue in my post. And now, I'm taking even more time to debug the communication and misunderstanding...

Was willing to complete the su commands...

Anyway, good night and luck
[Galaxy S II Android Development] HellcatDroid:
"The app doesn't work" is a lie, it does backup the EFS and everything, it just has a bug that admittedly has to be worked on - yes, also with high priority.

I'll work on this, don't worry.
[Galaxy S II Android Development] HellcatDroid:
doublepost ! net lag
[Galaxy S II Android Development] androidkid311:
Instead of reading a lot and backing up. People panic. 1 star is a piss take. He will be back lool. They always come back :D
[Galaxy S II Android Development] jonny_ftm:
I stop justifications, waste of time
[Galaxy S II Android Development] HellcatDroid:
testing time

OK, going to try a few things in the near future, as I am totally unable to reproduce the bug on my phone no matter what I do, I need people with the bug happening to run all those testbuilds :o

So, if someone with the "lockscreen bug" can please test the build attached to this post, thank you :)

Oh, and the "Check" function is kind of broken in this build as I am also trying to fix the "no PC mount after EFS-backup-check" bug, so don't mind "mount" returning 255 and failing :rolleyes:

Oh, and I also found (I think) the reason why in some situations the temp folders are not cleaned up (tho, not fixed in this build yet).

Well, then, have a nice xmas eve everyone, read ya soon.
[Galaxy S II Android Development] HellcatDroid:
Any feedback?

I think I also have an idea for a workaround/alternate dump method that the one affected by the lockpattern issue can enable.... but I need it tested by those getting this bug.
[Galaxy S II Android Development] thanksgiving60:
lol

why was my post deleted without any reasons given?
[Galaxy S II Android Development] HellcatDroid:
???

What did you post?
[Galaxy S II Android Development] thanksgiving60:
why dont you ask the mod who deleted my post? ;)

but i'll say one thing, this is a great little tool, i have never encountered any of the problems that "someone" claimed there to be
[Galaxy S II Android Development] HellcatDroid:
Gotta check who said mod is.... :confused:

But well.... let's drop the fuzz ;)

:) thanks :)

And here's a little status update on everything:

looks like I fixed the "problem USB mounting to PC after EFS-Backup check"

adding (mostly done already) an "alternate EFS dump method" for those getting the "lockscreen bug".

I hope that would fix/workaround it, as it never actually unmounts /efs but rather flushes caches and remounts read-only and after the .img dump back to read-write.

Also gotta test how reliable a partition dump in that state is (the whole unmounting actually has a technical reason).

Thinking about adding a "skip .img dump all together and only do .tar backup" - just to cover everything.

(after all, it's all gonna be options, so everyone can choose whatever he likes.)

And I added the "SPH-D710" and "SGH-T989" variants to work.
[Galaxy S II Android Development] s2d4:
Thank you sir for doing some real development on sgs2.

It looks funky but that is just personal tastes, a must app for all flashers.
[Galaxy S II Android Development] HellcatDroid:
Glad you like it :)

Well, I'm open for suggestions, with all the options that were added over time the UI is kind of a patchwork and due for a redo anyways :rolleyes:

Esp. when I eventually get around to make it compatible with the I9000 "S1".
[Galaxy S II Android Development] s2d4:
hopefully this would be helpful, a couple of ways of doing it maybe. :)

1. re-use some code from your bootlogo app where it choose a pic. People can have whatever they want.

2. has an option to go from white background to black background with corresponding text inversion similar to the Any.Do app.

https://market.android.com/details?id=com.anydo&hl=en

black is probably plenty as it goes with upcoming ICS.

I like option 1. :D
[Galaxy S II Android Development] sea_salt:
hi HellcatDroid :-)

I just wanted to ask, if I can use your kTool v1.35 to backup my stock kernel?

I'm running still completely stock at the moment... and of course I would use a temp-root (via zerg-rush) to get root, then install you kTool and hit "dump kernel"... would I then get a perfect backup of my stock-kernel?
[Galaxy S II Android Development] HellcatDroid:
@1:

Not exactely sure what you mean, you mean like making the mainscreen "themed" like the bootscreen app, or more like being able to choose any picture as custom background (which would be pretty cool, to be honest :D)

@2:

Ah, so like two themes, like "light" and "dark" theme?

Hmm, not bad.

How about "custom background and then can choose if dark or light theme (to match the background and personal taste)"? :)

Hm, yeah, should work.

The market version of kTool comes with it's own busybox included and most thigs were tested on plain stock kernel.

I you end up with a 8MB zImage file after the dump, 99% chance all is good :D
[Galaxy S II Android Development] sea_salt:
sounds nice... I think this would be very noob-user-friendly... we should include this in our upcoming guide :-)
[Galaxy S II Android Development] s2d4:
Right on the mark there. :D

I think the ability to choose pics is an awesome touch.
[Galaxy S II Android Development] HellcatDroid:
Couldn't agree more, that idea is really cool! :cool:

People like customisation, so why stop at app level :D