yashsingh1/xdaforums huggingface dataset:
[GT540 Optimus Android Development] kretos:
Yes, but what I ment was that only maintainers of device will introduce changes in device kernel so everything depends on mike and pebe. Cyanogen creators will make goodies but that won't speed up our phone or extend its capabilities.
[GT540 Optimus Android Development] simon194:
BT headsets work fine on my GT540 with both RC4 and ASIS. ASIS is better because the BT volume is much higher than RC4.

Did you use the recovery method for updating or fastboot? I used fastboot.
[GT540 Optimus Android Development] revilo34:
if we get an official rom thats a good news for our gt540 it means that it is a stable rom right?
[GT540 Optimus Android Development] rusgard:
mh...i used the *.bat to flash the image, which was included in the download-packet...don't know exaktly, if it was fastboot or recovery method :/
[GT540 Optimus Android Development] m4nu4l:
Could we get some feedback from mike and pebe ? Hows the progress overall ? Whats going on ?
[GT540 Optimus Android Development] jasper580:
I guess they're to buzy to answer :p
[GT540 Optimus Android Development] Mur4ik:
LG GT540 is not on official list of CM supported devices, there are even no request for adding our device yet, so not be so sure in your words ;).

not exactly, CM team would not make anything for our device, it should do a maintaners (Mike, pebe and anyone else who interested on that). Its not a LG support :).

Only differences is that you can get support in ROMManager and can freely download new builds from CM servers, and maybe our dev's can get some little help from CM team devs in development.
[GT540 Optimus Android Development] jhonnyx1000:
It's fastboot since it's on the computer. Recovery does the installation from a local directory and on the phone.
[GT540 Optimus Android Development] koolxs:
Hi guys. Keep up the good work!

2-3 questions:

- BT headsets work correctly? Wearing Mur4ik's ASIS and RC5 I could not hear the voice of the incoming caller.

- Wifi hotspot works?

- Can I flash the ROM over my ASIS or RC5 without wiping data?

Thanks!
[GT540 Optimus Android Development] jhonnyx1000:
Native Wifi Hotspost is supported.

We need to wait until the ROM is out. I recommend wiping data for each release but you may not need to wipe data.
[GT540 Optimus Android Development] koolxs:
I need that because I want to keep on working with the same setup. Titanium did not work for me as I expected.

Maybe I dont know how to use it correctly. And it is too much time to set up all apps from the beginning.

So I might do it for a ROM that really solves the problems that matter a bit more.
[GT540 Optimus Android Development] s-u-f-f-e-r:
Before flashing do a full backup via Recovery, after that just clean Dalvik Cache аnd install the new version.

If there are problems you can return to a previous version or... after full wipe you can install clean new version again
[GT540 Optimus Android Development] jasper580:
Actually Mike PM'ed kmobs:

So it will be official, it just take some time ;)
[GT540 Optimus Android Development] androidboss7:
Whats the time zone in other countries??

It seems like no one is on xda..

There hasn't been much people on lately.. :)
[GT540 Optimus Android Development] -Grift-:
yeah ikr for me its +8GMT
[GT540 Optimus Android Development] bataya:
+1GMT in Belgrade, Serbia. :-)

Sent using Tt.
[GT540 Optimus Android Development] jhonnyx1000:
+13GMT here with DST in Auckland, New Zealand.

The frequency of posts especially on the Development has dramatically decreased.
[GT540 Optimus Android Development] androidboss7:
closet to me.. !! ;)

i live in sydney australia !! :cool:
[GT540 Optimus Android Development] jhonnyx1000:
Danzano also lives here :)
[GT540 Optimus Android Development] m4nu4l:
wheres mike, wheres pebe? we kinda would like to hear news :s
[GT540 Optimus Android Development] -Grift-:
someone count how many devs we have now :( i need to bump the forum randomly if not it is really dead!
[GT540 Optimus Android Development] cccb010:
Not until our phones get stolen
[GT540 Optimus Android Development] sponky514:
cant wait to install on my gt540, once i get home, i will update my rom to this one!!!! keep such a good work!!!! guys thanks for all your efforts
[GT540 Optimus Android Development] m4nu4l:
so the project is dead? Mike and Pebe didnt posted anything in a while
[GT540 Optimus Android Development] liamwli:
I don't think so.

Sent from my LG GT540 running mur4ik's swiftDroid 2.0 ASIS.
[GT540 Optimus Android Development] s-u-f-f-e-r:
Don't press the devs :)

Тhe weekend is just starting. Just give 'em some time.

After the good news about official cyanogenmod support, we will wait for a new topic from mike and after few weeks - first version :)
[GT540 Optimus Android Development] jasper580:
I think we should be happy with all those devs. And BTW: it aren't that much if you don't count the soft-mod devs! ;)

I think he just didn't post anything because he is working on his roms :) He is atm buzy with his AOSP for example (altough i hope also on CM ;) ).
[GT540 Optimus Android Development] jasper580:
Ice Cream Sandwich source is released! :D @Mike Will you port Cyanogen 9 if it becomes available?
[GT540 Optimus Android Development] martin255:
So what about the official CM7/9? I don't see the GT540 on cyanogenmod's website...
[GT540 Optimus Android Development] andreas__:
we need a maintainer .. nobody wants to do it
[GT540 Optimus Android Development] jasper580:
Mike want to do. He's gonna release it. It IS official, but the ROM isn't ready...
[GT540 Optimus Android Development] G00fY2:
I think till now nothing is official. It's only official when it is on the CM website.
[GT540 Optimus Android Development] jasper580:
Not really. Mike has confirmed it with the CM Team, he's just tweaking it before he release it ;)
[GT540 Optimus Android Development] Dilbao:
Technically, that is correct, and I agree. It is semi-official as far as I know about the situation. There is nothing on the public channels yet.
[GT540 Optimus Android Development] jasper580:
Read my post before. :P
[GT540 Optimus Android Development] liamwli:
When will it be ready. I really am not very patient.

Sent from my LG GT540 running mur4ik's swiftDroid 2.0 ASIS.
[GT540 Optimus Android Development] jasper580:
When Mike and Pebe decide to release it.
[GT540 Optimus Android Development] :
Well mates, you I'll have to wait. Now I resync sources, prepare to finally make a pull request of initial support to GT540 in CM Repo.
[GT540 Optimus Android Development] liamwli:
Thanks for the update

Sent from my LG GT540 running mur4ik's swiftDroid 2.0 ASIS.
[GT540 Optimus Android Development] :
Now someone must accept this (from Gerrit moderators), and i will be able to made other changes.
[GT540 Optimus Android Development] jasper580:
Great! BTW: @mike i've put your website in the startpost, but CM isn't on it! :(
[GT540 Optimus Android Development] mikegapinski:
I told you to remove this stupid thread :P
[GT540 Optimus Android Development] jasper580:
And I told you it would be a (stupid :P) talkabout thread :P
[GT540 Optimus Android Development] airbus360:
Talk about threads go into the General Section.
[GT540 Optimus Android Development] jasper580:
Well, I can't move it, and the moderator happens to be never online, so...
[GT540 Optimus Android Development] eoghan2t7:
Just pm the mod he will get it
[GT540 Optimus Android Development] -Grift-:
I tried -.- our mod never onlines we have to pm some guy called scots man or something like that who acctually closes a thread or two
[GT540 Optimus Android Development] androidboss7:
Yeah Jasper i think u should just close this thread,, :)

Write like thread moved to ( LINK ) ! :)
[GT540 Optimus Android Development] airbus360:
Yeah , re-write the start post to just say thread moved than link and sorted, the thread will become inactive and removed :)
[GT540 Optimus Android Development] liamwli:
Any update on this?
[GT540 Optimus Android Development] mail2eswar:
I am having a problem with this ROM. 2G data and Wifi is not connecting to internet. Both are showing status as connected but actually data is not coming.
[T-Mobile myTouch 4G Slide] dirtyreturn:
Why doesn't busy box recognize root? I am s off
[T-Mobile myTouch 4G Slide] blackknightavalon:
Did you flash the Superuser .zip file?? This is what got me stuck at first, too.
[T-Mobile myTouch 4G Slide] dirtyreturn:
i had trouble flashing so i dled it from the market, wrong thing to do?
[T-Mobile myTouch 4G Slide] blackknightavalon:
Keep trying to flash it. It'll hold after the seventh or eighth time.
[T-Mobile myTouch 4G Slide] dirtyreturn:
thanks for the tip. it worked!
[T-Mobile myTouch 4G Slide] blackknightavalon:
I think that step gets people stuck more often than they care to admit.
[T-Mobile myTouch 4G Slide] dirtyreturn:
too proud i guess., maybe. Anyways, i really appreciate it -
[Galaxy S II Q&A, Help & Troubleshooting] highaltitude:
Has anyone figured out how to fix the market problem with some apps. My wife plays Paradise Island all the time and it says to update. When I try to update the game, it says ther eis insufficient space available. Well I have ton of extra space both internally and externally (SD card wise). I have heard its a problem with the market. I updated to the newest market this morning. Still same problem. I have done a search for about a week now, and still have not found the solution anywhere so I ask the question here now. Anyone?
[Galaxy S II Q&A, Help & Troubleshooting] curioct:
That one is easy if the phone is rooted?

Simply delete .apk files from the /cache folder not entirely sure why but failed updates and downloads from the market sometimes stay there

if the phone is not rooted I would probably try force stopping, clearing data from market in application manager and rebooting.

market will then act as if freshly installed, this might work I have not tested it asmy phone is rooted
[Galaxy S II Q&A, Help & Troubleshooting] curioct:
if you have a backup the easiest way I have found is to use root explorer.

go in to the /efs folder, set to read/write, mark everything and delete (not scrictly necessary simply copying over will work) but if you have been tinkering probably better.

then paste all the back up files and folders in

finally reboot (in my experience when something has gone wrong even this is not necessary)

Root explorer is worth every penny

and keep multiple backup's of your /efs on different drives

If this does not work you are screwed. The file contains your IMEI encrypted and the only way to get that restored is by returning it.

oh I just realised you are saying the back up you have is only of it in the current state?

If that's the case you are probably screwed, have you ever used any apps like nitrality or any unlocking tools? they will create copies of your efs folder on the scard in various locations. have you run a file seach on you sdcard to see if there is any copies at all?

if you have no backups of this folder then I think you will find its a return to manufacturer / sevice centre / provider issue.
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
I *think* I have restored the files -- and the dates look reasonable, as if they were the originals.

I've now flashed an old ROM (KE5) for good measure, but still no signal

One discrepancy I did notice is that after installing a rom there was some bootup message about csc and XEU when copying files.

My original sales code was VOD (UK vodafone). I had then run XEU firmware and just recently tried to set the sales code to XEU using a *# code. I subsequently flashed back to vodafone firmware today.

So somewhere there's a lingering reference to XEU -- this prod code incompatability could be causing the error?

I definately feel I should have the data to fix this -- after all I have the encrypted file, but am not quite sure of all the factors involved (one being "you're stuffed I know")
[Galaxy S II Q&A, Help & Troubleshooting] curioct:
type *#06# this should display you IMEI number

if this does not match your IMEI from the box then you have not fixed this

if it shows all zeros or 004999010640000 then you are on a generic IMEI number

strangely when I screwed mine up and got the generic one above I was still able to use mine with a vodafone (UK) sim but not an orange on

if this is the case, and there is no efs backup prior to this you might well be screwed.

if this backup is all you have an you believe the .bak file is intact then I believe you will find solutions for deleting the primary version of the file and keeping only the backups and rebooting

the log file should give you more information on how successful this was, but if this was the result of flashing you probably overwrote both primary and backup
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
*#1234# is returning a reasonable CSC I9100VODKE2

Checking the nv data files, it appears

- the new ones modded today contain XEU

- the original ones contain VOD

This is consistent with what happened, so I am still confused why the renamed original files do not work, and why there's a reference to multi-csc XEU during bootup.

Some remnant of XEU?
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
*#06# is currently showing blank -- but those .bak files looked fine.

Annoyed and frustrated...
[Galaxy S II Q&A, Help & Troubleshooting] curioct:
In that case I would try deleting nv_data.bin and nv_data.m5 and rebooting

(assuming you have copies of everything

with just nv_data.bak nv_data.bak.md5

At least with the SGS1 this would work provided those bak files are the originals but the nv.log file will tell you more after the boot.

HOWEVER the SGSII has a lot more in this folder and I do not claim to fully understand them all but if you have a back up it's worth a shot
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Took some inspiration from http://www.communityhosting.net/sgsunlock/i9000.html and decided to check permissions & recreation of md5.

md5 wasn't recreated, so no matter, I had a backup. that is restored, but I don't know if the .bak files are needed. Yet trying to create them I get:

# mv nv_data.bin.md5.orig nv_data.bin.md5

mv nv_data.bin.md5.orig nv_data.bin.md5

# cp nv_data.bin .nv_data.bak

cp nv_data.bin .nv_data.bak

cp: write error: Read-only file system

#

This isn't a space issue.

There could be another cause -- /efs/imei/mps_info.dat contains the 3 characters "XEU" even though the file is dated Jan 2011

So either

- the date has been manually fudged

OR

- the code always was XEU -- unlikely.

I'm currently working on the basis that fundamentally the IMEI is intact, that the original nv_data.bin is intact & that the phone is validating the CSC in mps_info.dat (XEU) against nv_data.bin (VOD) and failing.

Though this wouldn't explain why before the fix, with XEU in the nv_data.bin, it wasn't working

Unless the issue is the filesystem itself. could it be corrupt? Is this in fact why it switched to R/O mode each time? I've tried multiple kernels including insecure. surely they wouldn't all "protect" this fs.

But if this is the case where is fsck? maybe I need to copy the fs image to another linux box with ext4 & inspect/correct before shipping back and dd'ing
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Continuing.

Found /system/bin/e2fsck -- ran this against /efs with

# /system/bin/e2fsck /dev/block/mmcblk0p1

/system/bin/e2fsck /dev/block/mmcblk0p1

e2fsck 1.41.11 (14-Mar-2010)

ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determini

ng whether /dev/block/mmcblk0p1 is mounted.

/dev/block/mmcblk0p1 contains a file system with errors, check forced.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

/lost+found not found. Create<y>? y

yes

Pass 4: Checking reference counts

Pass 5: Checking group summary information

Block bitmap differences: -(3202--3203) +4104

Fix<y>? yes

/dev/block/mmcblk0p1: ***** FILE SYSTEM WAS MODIFIED *****

/dev/block/mmcblk0p1: 60/1280 files (1.7% non-contiguous), 2188/5120 blocks

**** >>> I NOW HAVE AN IMEI <<< ****

AND SIGNAL

LOGGED ONTO VODAFONE

WOOOHAY.

THIS HAS BEEN FUN. LOOK AND LEARN..

and seriously thanks to all the other articles and some moral support here tonight.

Going to put back proper firmware , remove dodgy kernels and GET A BIG BEER OR THREE
[Galaxy S II Q&A, Help & Troubleshooting] curioct:
and make several backups of the /efs folder in its current state :D one would assume
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Phone seems working. restoring over a HSPA connection happily, recognized voda sim.

now reinstalling titanium backup and copying down from dropbox...
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
The final step was restoring from titanium backup.

I had erased my sdcard -- though my backup was on dropbox.

However titanium backup is awful at copying files to/from dropbox -- as is IMO the phone when in "phone/kies" mode.

Finally I simply copied the dropbox directory back in USB debug=mass storage mode which was quick and reliable -- and then restored most items en-masse (I have a pro license).

For the record so far phone is fine - and indeed I've since run a new efs backup

The key takeaways from this are

* Backup efs and save it somewhere offline

* get titanium backup pro. it's good (better if it backed up efs too!)

* usb mass storage mode is the most reliable way for file xfer

* backup efs (again)

* don't get complacent

And of course if you do get a similar problem to mine

a) take a backup of efs with dd if=/dev/mmcXXX of=/mnt/scard/myefs.img (check name - I forget)

b) copy files you can to sdcard

c) copy both of this to a seperate pc

d) Just try running fsck (as above) - If I'd done this sooner I'd have saved hours. I should have gone with the obvious -- I've seen this on enough linux systems in the past to know what was happening but was thrown by no kernel messages.
[Galaxy S II Q&A, Help & Troubleshooting] Freakgs:
Thanks for letting us know, might be a nice reference for future problems, especially the filesystem check.
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Writing about it also helped keep me sane.giving up and hitting the beer was becoming increasingly attractive.

I do think making the warning about efs clearer would help.backup really should be a must at the earliest opportunity
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Another thought.do unmount /efs before fsck
[Galaxy S II Q&A, Help & Troubleshooting] jcrompton:
Unable to restore

I know I had a valid IMEI during the last week or so.

I have flashed several ROM's during the last month.

Last night lost IMEI

Now , no matter what I try, I can't seem to restore my IMEI. I have the fake one that ends in a bunch of zero''s

My SDCARD has a folder called EFS_BACKUP with multiple efs_xxxxxxx.tar.gz files in it. If I extract any of these and try to restore them to the /EFS folder I still have the fake IMEI number.

Please help - I didn't understand all the adb code in this post
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Hi there,

/efs is fairly new to me too, to be honest it took hours of careful rooting before I gained some useful knowledge in how that area works.

-- what I would suggest before *anything else* is to copy anything you do have left in /efs. You will need to be root to do this. I found the gui root explorer type tools a bit clunky so I used the android SDK (adb is one of the tools in this package) to help. IF YOU NEED HELP WITH THIS SAY. You need to copy the files to multiple places for safety. Someone OFF your phone, ie on a PC. This is just in case things get worse. Do the same with any of those .gz backups you have. Maybe you'll need them *if* you make things worse...

If you're familiar with linux/unix systems this is all fairly easy, but if you're not it can be quite scary. For example you have to be able to write to /efs as well as list files and move them around. One wrong step and you could make things worse.

If you're unsure perhaps you could find a friend who knows *nix well to help you out. The bottom line is that you need to

a) ensure the right files are in there

b) The filesystem itself was intact

I definately suffered from b -- less sure about a.

What you need to do will depend a fair bit on what files you find in there, and what dates they are.

You said you had some backup files. Are you sure you have some from before the problem started? Can you look inside those backup files (I think winzip or similar will expand them for you). WIthout divoluging the actual contents (since you don't want to share your IMEI with anyone), is there an nv_data.bin file in there? Out of all the files it seems to be the most critical. When's it dated (mine was Jan 2011). If you cant' find that file how about .nv_data.bak - is that a good size, and again an old one.

If you have either of these -- even without anything else I think you can probably recover.

If you can get up and running with adb, a good start would be

adb shell

ls -laR /efs
[Galaxy S II Q&A, Help & Troubleshooting] Bloodrainer:
Thank you very much, fsck method fixed my efs. Phone just broke it while doing nothing :/
[Galaxy S II Q&A, Help & Troubleshooting] Armisael:
I love you :D

You just saved my Galaxy S2
[Galaxy S II Q&A, Help & Troubleshooting] planetf1:
Yay. Brilliant news
[Galaxy S II Q&A, Help & Troubleshooting] unlockberry:
hi out there!

i'm having a rooted SGS 2 with no imei & no signal & unfortunately no efs backup! can anybody please help me restore the nv_data.bin, it's corrupted as it seems, thanks.
[Galaxy S II Q&A, Help & Troubleshooting] Casey Rain:
When I get to this bit, adb dramatically beeps at me and says

THE FILESYSTEM IS MOUNTED, IF YOU CONTINUE YOU **WILL** CAUSE **SEVERE** FILESYSTEM DAMAGE

What now?
[Galaxy S II Q&A, Help & Troubleshooting] Bloodrainer:
maybe you forgot about:

good luck :)
[Galaxy S II Q&A, Help & Troubleshooting] Casey Rain:
thanks... I tried that and it told me it couldn't unmount efs because the device or resource was busy...
[Galaxy S II Q&A, Help & Troubleshooting] Bloodrainer:
i remember i also got that kind of error, that it was busy or something, i rebooted or something and kept trying to unmount/umount/whatever it, so be tough :)
[Galaxy S II Q&A, Help & Troubleshooting] Casey Rain:
For anyone in the future who might google this thread -i found this solution in another thread and this finally fixed it for me.
[Galaxy S II Q&A, Help & Troubleshooting] formes:
Many thanks planetf1!

I've been spending many hours, maybe 12, trying to get my SGS2 back. There was no signal amb got many problems with batery.

After reading your post I've solved the signal issue!

(Now I got the original batery working but the new and bigger one does not charge and seems to be dead).

Thanks again! :D
[Galaxy S II Q&A, Help & Troubleshooting] formes:
Eventhouh the problem with phone signals seems to be OK, I'm still in trouble with USB port.

It does not recognise data cables at all and when I try to charge batery I have to reboot the phone with the charger plug in order to start charging.

If I unplug, no way to charge till next reboot.

With the phone powered off, if I plug it, instead on start charging, the phone boots (and then start changing) :eek:
[Galaxy S II Q&A, Help & Troubleshooting] Maverick3113:
Hi, Im from Argentina, having the same problem. It happened suddenly, it says IMEI unknown, baseband Unknown, Phone number Unknown.

No sim is read, could you help me,? the problem is that I don´t know enough to do what you did, is there any posibility for someone to help me remotely?
[Galaxy S II Q&A, Help & Troubleshooting] Sergeant Droid:
Can prefer me a backup method. I have found some but I want some advice.
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
You want an EFS backup method ? Get Hellcat's kTool from Market, then go to this thread & buy Hellcat a beer ;) Quick and easy, keep one copy on your PC or external drive, and another copy on your external SD card in your phone. That way if the worst ever happens, you'll be able to fix it.
[Galaxy S II Q&A, Help & Troubleshooting] DHeart:
Same problem. Help?