yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] wang1chung:
worked some long hours, so i didn't have a chance to try it.

i went to try it today, and all i get is "cp: not found" when i'm in adb shell. i just installed the sdk packages, and still nothing. anyone else want to try this, i won't have much more free time to figure this out till the weekend

edit: figured it out, hadn't re-installed busybox since the jh2 update. just got the backups, going to swap it now.
[Galaxy S I9000 Android Development] wang1chung:
well, that was a fail........note, i copied my backups, and renamed these 3button versions as my original backups, but they are 3button backups.

adb shell

$ su

su

# mv /sdcard/nv_data.bin.md5.bak /efs/nv_data.bin.md5

mv /sdcard/nv_data.bin.md5.bak /efs/nv_data.bin.md5

failed on '/sdcard/nv_data.bin.md5.bak' - Cross-device link

# mv /sdcard/nv_data.bin.bak /efs/nv_data.bin

mv /sdcard/nv_data.bin.bak /efs/nv_data.bin

failed on '/sdcard/nv_data.bin.bak' - Cross-device link

# exit

exit

$ exit

exit
[Galaxy S I9000 Android Development] hmanxx:
Not related to this bootloader thing however the error could be just command problem.

Perhaps you can try using busybox cp command

# busybox cp /sdcard/nv_data.bin.md5.bak /efs/nv_data.bin.md5

Last time when i used the mv command.to move contents out from /data/data folder .the same error of cross-device link error. Busybox cp command worked fine without error..
[Galaxy S I9000 Android Development] irkkso:
3 buttons disabled phones

Please can any one tell me how to get 3 buttons download mode on my "3 buttons disabled phone" easy method I mean how to update bootloader easely?

thx:(
[Galaxy S I9000 Android Development] Senorclean:
That's what we're trying to work out... at this stage, there is no known way to get the 3 button mode - and it is possible that there never will be.
[Galaxy S I9000 Android Development] phoenixdigital:
Odd... You could try to move the backups to /efs... however I am pretty sure there is not enough room on the partition for them..

To be safe try the following on the neutered device... first copy your 3button one onto your /sdcard

Backup the original

cp /efs/nv_data.bin /efs/nv_data.bin.bak

cp /efs/nv_data.bin.md5 /efs/nv_data.bin.md5.bak

Copy across your 3 button one to

cp /sdcard/nv_3button.bin.bak /efs/nv_3button.bin.bak

cp /sdcard/nv_3button.bin.md5.bak /efs/nv_3button.bin.md5.bak

Check that all are in /efs and are all the same size

cd /efs

ls

If they are then copy them all back off to the /sdcard.. then to be triple sure.. move them to your PC/Mac and compare them with previous backups... If they have not been truncated or filled with zeros then you can safely do the mv commands from /efs

Basically testing the above by copying is a safe way to see if there is enough room on that partition while leaving the original file intact.

I have run into similar issues when modding TiVo's where you need to patch a binary file however there is not enough space on the partition for more than 2 copies of the file. So I always make sure the files are not truncated before rebooting my TiVo.

I am testing backing up two versions now... I think I ran into the same busybox problem you had.. will report back.

wang1chung can you pm me your backups between two phones to compare please?
[Galaxy S I9000 Android Development] phoenixdigital:
Yeah I got an error when doing the backup to /efs something about numerical data out of range... I think it's related to space issues..

CRAP!

So then I am not sure how those people in the other thread are restoring backups if there physically shouldn't be enough space on the /efs partition to even hold a backup...
[Galaxy S I9000 Android Development] aboad20:
backup this files to /sdcard

Then delete it from /etc

finally copy your new files to /etc
[Galaxy S I9000 Android Development] phoenixdigital:
That could possibly work too... its /efs we are looking at though...probably just a typo ;)

From looking at the errors that wang1chung was getting it looks like it was an issue with the /efs partition was mounted as read only???

You can check all the mount points by typing this into a terminal

su

mount

In hunting around for answers I found a really good post which answers my initial question at the beginning of this thread. To copy a BML from one device to another you do just have to run

Backup

su

dd if=/dev/block/bml3 of=/sdcard/bml3.bak

dd if=/dev/block/stl3 of=/sdcard/stl3.bak

Restore

su

dd if=/sdcard/bml3.bak of=/dev/block/bml3

probable reboot required then running the restore of stl3 (see linked thread below)

su

dd if=/sdcard/stl3.bak of=/dev/block/stl3

So if anyone wants to play around copying whole partitions from one phone to another... go nuts... don't hold me responsible if you brick though ;)

This post is where I found this information.

It appears /efs is mounted from /dev/block/stl3.... which this says is bml3... wow... confusing...

So if anyone feels game backup your entire BML3 from a working 3 button phone then restore it to a non 3 button working phone.... it will probably munt the IMEI as its encrypted somewhere... but at least you can see if 3 button comes back... when your done just restore your backup again..

I feel like I'm running in circles looking for this bug... I wish Samsung would give an official response.
[Galaxy S I9000 Android Development] aboad20:
why you don't use Root Explorer to copy , mount , backup ??

I can see this files , copy , paste
[Galaxy S I9000 Android Development] wang1chung:
root explorer looks like it might work.......i just installed it, and i have a backup copy of nv_data and an original copy of nv_data on my efs partition, with (according to root explorer) 1.59 megs free?

so i copied the original md5 file (nv_data.bin.md5) to my sdcard, then to my computer, and checked it against the backup i made yesterday, and it doesn't match. i then compared it to my 3button backup, and it doesn't match.............not good me thinks?

i'll make another backup via root explorer tonight if i have time and try again

edit: and there is an option in root explorer to change from r-o to r-w
[Galaxy S I9000 Android Development] phoenixdigital:
It is possible that some settings got changed since you made the backup? Like call usage, uptime etc... if that is where that info is stored.

The critical things to check are

a) Are they the same size

b) Are they basically similar (ie no massive chunks different)

c) Is the beginning or end padded with zeros compared to the other(similar to above)

PS Samsung Australia are getting hammered on Facebook.
[Galaxy S I9000 Android Development] Gad13:
I suspect the number in *.md5 file is calculated in different logic.

Both my *.md5 on my Vibrant have numbers that doesn't match to the check sum calculated using md5sum.

I've verified nv_data.bin and .nv_data.bak.

Other possible case is the md5 file to have a checksum from only a certain part of the corresponding nv_data file.

Judging on the time stamps I do believe the md5 file is generated after changing the nv_data file.
[Galaxy S I9000 Android Development] phoenixdigital:
Yeah I would say it's the protection they use incase someone tries to change their IMEI in nv_data.bin that would invalidate the .md5 file which would cause the IMEI to flick back to a 'dev' IMEI which people have reported seeing on their phones in these forums.

Hopefully it's just an md5 (possibly salted) of the IMEI portion of nv_data.bin because then IF the 3 button recovery setting is stored there we can change it without having to work out how to regen the md5... which would be near impossible.
[Galaxy S I9000 Android Development] wang1chung:
didn't work...........root explorer worked to move everything, but download mode wasn't accessible with the 3 button combo........i even took out the battery and waited a minute before trying it............hmmm, i think i tworked cause it says i have no service now.........****, ok, getting scared now. going to set it back to the way it was before.

EDIT: ****KKKKKKKKKKKKKKKK............ok, need help now please!!!!!!!!!!!

phone number: unknown

network: unknown

service state: out of service

mobile network type:unknown

ok, wtf. i thought everyone was doing this fine over in the other thread without an issue
[Galaxy S I9000 Android Development] phoenixdigital:
You copied everything back and it's still not working?

Was your girlfriends phone still on when you did that file copy over? It's possible that two of the same IMEI was on the phone network at the same time and that IMEI got blocked??? (Doubtful but thats a worst case scenario)

You also need to reboot fully after restoring those files.

Try putting your SIM in a working phone (none of the ones you have been playing with) and see if it is still active.

I have other options for you based on that link above. Will do them via PM though as it involves sensitive files from my own phone.
[Galaxy S I9000 Android Development] wang1chung:
YES! i don't understand why it wouldn't work. i specifically made different directors on the sdcard for my nv_data files and the 3button nv_data files, so it's impossible. i'm going to copy the current nv_data file and compare it with my backup and make sure it's mine and not corrupted or whatever.

edit: i'm screwed. the files are identical. something must have been messed up when i did that.........ok, no more messing with my phone once i get it fixed........what a scam. how the hell did everyone else in the other thread do it without issues?
[Galaxy S I9000 Android Development] phoenixdigital:
you dont have a copy anywhere of your old nv_data.bin and nv_data.bin.md5?

Or do you have an old backup of BML3 from your phone anywhere?

done with the command

dd if=/dev/block/bml3 of=/sdcard/bml3.bak

We can still try something. Just the BML3 probably isn't enough though.

Edit: Your in the same boat as me... One brick... no more testing
[Galaxy S I9000 Android Development] wang1chung:
well, in the efs partition, there is a backup from july 26th of my nv_data.bin and md5 plus my current nv_data.bin and md5 which matches a hex compare of the copy i made just 15 minutes before.

and yes, i have my bml3 backup i made with that dd command
[Galaxy S I9000 Android Development] phoenixdigital:
So your saying your girlfriends nv_data.bin and nv_data.bin.md5 now matches all of your backups?
[Galaxy S I9000 Android Development] wang1chung:
no, my nv_data.bin and md5 (in the efs partition) match my backup of that same files from my phone i made 15 minutes before this
[Galaxy S I9000 Android Development] phoenixdigital:
Odd... does your SIM work in another phone?

If all else fails and your ready to send it back you could try the following

a) Make sure the permissions are correct for the nv files

adb

chmod 644 /efs/nv_data.bin

chmod 644 /efs/nv_data.bin.md5

reboot

Edit: See step 12 and 13 here.. might need to pull the battery after permission change.

b) Delete everything from /efs.. copy in your backups... do permission thing above...reboot

c) Reflash with ODIN

d) (Last chance)

However I think you should have also backed up the stl3 before you started messing with it as mentioned in my post lastnight..

Backup your stl3 (Should have done this before messing with it but no harm in doing it now)

su

dd if=/dev/block/stl3 of=/sdcard/stl3.bak

Restore bml3

su

dd if=/sdcard/bml3/bak of=/dev/block/bml3

reboot

Restore stl3

su

dd if=/sdcard/stl3.bak of=/dev/block/stl3

Copy over your old files nv_data.bin and nv_data.bin.md5 to /efs ... do permissions check in part (a) then reboot.

Absolutely last possible case.... BRICK it by ticking re-parition in ODIN and choosing no files then flash it.. then take it back for service...

Hope you get it sorted.
[Galaxy S I9000 Android Development] Gad13:
Don't panic.

1. Check your IMEI first. *#06# will show it.

2. On my phone I have 2 hidden files, which I do believe are original settings as the phone was shipped.

they are "/efs/.nv_data.bak" and "/efs/.nv_data.bak.md5"

You may want to replace your current nv_data.bin and nv_data.bin.md5 with them.

And always make a backup before you delete/replace files/partitions.
[Galaxy S I9000 Android Development] phoenixdigital:
Also my options above a, b, c and d are all to be tried seperately...

Good to know about the .nv_data.bak files... they should still be intact.
[Galaxy S I9000 Android Development] wang1chung:
yeah, i said i saw the bak files in the efs partition, but they have different info in them compared to the regular nv_data files i backed up..........the IMEI is still intact and correct..........my sim card works in my gf's phone.

i am going to check the file permissions i guess.......nv_data backups in that same directory, then i'm going to smash it......or bring it in for repair, depends on my mood
[Galaxy S I9000 Android Development] Gad13:
The IMEI is not part of the SIM card.

It is ID of the device /Phone/. Your phone is not working. It could be mismatch between the hardware and the configuration /most likely/.
[Galaxy S I9000 Android Development] wang1chung:
well, the imei is correct when i check it under phone info and the special code *#06#

i did also notice my apn's were gone.......i can manually re-enter them, but it doesn't even see my phone number, so i don't see how it'll help

well, before the chmod, i could access the apn page, but now after the chmod command and a reboot, my phone is in flight mode and i can't access it
[Galaxy S I9000 Android Development] Gad13:
Your apn's are gone because for some reason your modem doesn't work and the phone can't read them from your provider.

If you are 100% sure your nv_data.bin and nv_data.bin.md5 are original ones, then I'd suggest to flash some firmware and see what happen. Keep in mind you may lose root, but I guess you can always root it again if the adb works.

BTW is the adb works?
[Galaxy S I9000 Android Development] wang1chung:
well, it works again........kinda weird, but it's working now after i copied the backup files in the efs partition to the dev partition (had like 168 megs free), renamed it to .bin, then copied back.........i can make phone calls again, i just wish i didn't delete everything before hand..........i don't understand why though. if i backed everything up before hand, then copied it all back the exact same as before, why is it working now. i'm not complaining, just annoyed.
[Galaxy S I9000 Android Development] phoenixdigital:
You sir deserve the big brass balls award for attempting 3 button recovery mode reenable..

Glad you got it working now. Take a seat on the bench with me. No more testing for you.

So we have ruled out

/efs

bml1 (boot.bin)

bml4 (Spl.bin)

/mnt/.lfs

Not sure where else to look... someone did suggest nvram but I think that might have been the /efs files wang1chung was just messing with.

It's looking like its a hardware fault... more so since people are claiming they can get into that mode by heating up their phones.

Well unless anyone else has any ideas I am going to wait till the froyo release and hopefully they can fix it then... Alternatively see what Samsung Canada say about it since Samsung Australia have their heads in the sand... If it's still not resolved within a month or two I am selling my Galaxy S for something that is actually tweakable AND recoverable... or going back to the iPhone land..
[Galaxy S I9000 Android Development] daml:
I can confirm that they use a jtag interface to reflash. No recovery mode needed
[Galaxy S I9000 Android Development] phoenixdigital:
Any idea whether a full reflash with whatever firmware they have will re-enable recovery mode? If so I will bring it in and pay for it ;)
[Galaxy S I9000 Android Development] daml:
Yes. And we need more. Did you post?
[Galaxy S I9000 Android Development] Gad13:
How about the modem driver?
[Galaxy S I9000 Android Development] Senorclean:
If this is the case, maybe it is a timing issue - the controller is moving ahead before the datapath catches up with the key combination. This would also explain why some can get in to it sometimes and not others.

Maybe a modification can fix it in this case - just have to make sure the boot process waits long enough for the button combo.

EDIT: If it is a fault, you would expect it to crop up in other markets though..
[Galaxy S I9000 Android Development] phoenixdigital:
Modem driver was replaced by wang1chung when he upgraded firmware to a European version. JM6???

Something Samsung will have to fix :(

It is happening in Canada as well. Also someone who bought one in Hong Kong had the same issue too.

From what I have read in these and other forums Samsung are renowned for crap support so I am not holding my breath.

Edit: I have posted to Samsung Facebook page.. I suggest anyone that hasn't and has a facebook account does... I think it might require some persistence because they are going to launch their tablet tonight so we may get drowned out by talk about that... Just means we have to post once a week to keep the pressure on...
[Galaxy S I9000 Android Development] daml:
Yes everyone needs to make a scene of this. I just got a reply from samsung.

"Hi, our support team is currently looking into the problem and we will inform you on any progress as soon as we can."

It's a start.

Phoneix are you cameron?

Oh also, I am not sure weather re-flashing via jtag fixes the 3 button combo but i assume not. Others have got their phones back without this problem fixed.
[Galaxy S I9000 Android Development] phoenixdigital:
Yup thats me.

I have been contemplating buying one of these when they support the Samsung Galaxy S

http://www.jtagbox.com/

At least I wont have to pay $50 everytime I stuff up a firmware update.

I know a guy that used to do phone unlocking for a mobile phone retailer. I recall seeing this box on his desk.

I really hope Samsung come to the table and offer a solution.

Edit: Hmmmm.... downloaded the software related to riffbox and a virus was detected when it installed.... will have too look into that a bit more before I actually run it...jut a warning to others incase they wanted to look at it.
[Galaxy S I9000 Android Development] daml:
I'm contemplating selling my phone. This lag has become unbearable and I'm too scared to root and install a lag fix without the button combo.

More on this issue tho.

Apologies for being a little off-topic.

I sent optus a message via the social contact form (optus com au/aboutoptus/About+Optus/Help/Social+Media) and they called me today. Apparently I can walk into any optus shop and they will exchange my handset. Having said that I'm not too sure they know exactly what I was talking about. They may have thought I have a broken/faulty phone. My message was as follows:

Hi there. I have one of a bad batch of the handset "samsung galaxy s" that cannot go into recovery/download mode. This is on your 59 cap. Can I swap this under warranty? I would like the reassurance of it not being "bricked", so to speak, if and when I will be updating to the official "samsung android froyo 2.2 rom" that's due for release next month. I understand that others have successfully swapped their handset. I believe the handsets should never have been shipped with something like this omitted. How long should my warranty last?. I have had this handset for less than a month. Will I be covered by warranty in the case of a failure whilst re flashing. Will there ever be a fix to allow a button combination to boot into recovery/download mode? It is very important to me, considering I am signed up for 2 years, that my phone lasts the entire length of my contract and that it runs as good as it can with up to date software. As you can understand the thought of "bricking" my expensive phone is daunting. Thank you.

Damian Lang

I am going to go into an optus shop tomorrow I will let you know how I go.

The people at optus support did leave a note on my account saying exchange was OK.

Apologies again for being off-topic.
[Galaxy S I9000 Android Development] phoenixdigital:
Not really that off topic as its related to this stupid issue. I am keen to know how you go because I am seriously contemplating the same.

I am pretty sure there is a cooling off period for new contracts... I am seriously considering cancelling it. This phone is seriously laggy.
[Galaxy S I9000 Android Development] s4int:
good news....hope they keep their word:

"Some of you have reported to us that there is an intermittent software issue affecting the Galaxy S and “recovery mode” functionality. We’ll be announcing a downloadable software update shortly. Thank you for your patience."

source: "Bell phones and the lack of 3 button combo" thread post #264

samsung mobile canda facebook

(as this is my first post, i'm not aloud to post links...sorry)
[Galaxy S I9000 Android Development] marvi33:
wang1chung:

Bit late but the solution to /efs/.nv_data and .nv_data.md5 problem is posted here by Richthofen and its a very easy solution. You might want to delete files you have now and make system to rebuild them.

Read 1st post after **Read this if you are downgrading from I9000XXJPC rom**

http://xdaforums.com/showthread.php?t=770821
[Galaxy S I9000 Android Development] wang1chung:
my solution was one that he mentioned in that page that wouldn't work, but it did............he has suggested that copying the nv_data files will change their signature, and not work, so how am i supposed to copy a 3button enabled nv_data file to my phone to test it? maybe the attempt i made meant nothing as it wasn't done right? doesn't matter i guess since samsung said they're coming out with a fix, just been thinking about it.
[Galaxy S I9000 Android Development] aziztcf:
These advices I'm getting! First they tell me to bake my phone and now they want me to fsck up the partition table on purpose! What next, "Oh yeah the bug is actually in the accelometers, try throwing it from a moving car going at least 60Mph, oughta do it!" ;)

Let's hope they'll push the update they promised to the canadians to the rest of the world with broken phones.
[Galaxy S I9000 Android Development] Kasha:
I've turned my SGS into a brick just the way you described (don't worry, not by following your advice, but on my own :) ):

I decided to take the risk and flash the new firmware with help of the adb reboot script. I entered the download mode successfully and flashed the s1_odin_20100513.pit file, after which my phone turned into a complete brick - the screen lights up a little bit and basically that's it. Only at that moment I realized that to get to the second flashing stage I needed to enter the download mode again (which i obviously can't do), so the idea was a bad one from the start. :(

I tried your method, I assume it should have worked as I have a new PIT file flashed, but it basically just reboots - the screen turns black and then lightly lit again.

I have a second SGS with 3 buttons combo working and I currently have a dilemma what to do with the first one: To go to Samsung service center for a re-flash or to try 'the oven method' :D
[Galaxy S I9000 Android Development] Daneshm90:
Have u tried turning the phone off, keep it connected, let the battery charging screen come up, then try the 3button ? Have heard certain users had success with that.

Hehe "oven method" hehe :rolleyes:
[Galaxy S I9000 Android Development] BackfireNL:
It must be that Samsung disabled the combo intentionally...

Because my friend has a brand new SGS with JM2 and i can´t use the 3 button combo! AND i can´t root it even if i go in recovery through ADB!

So my update.zip is completely useless for newer phones... so thats the second problem...
[Galaxy S I9000 Android Development] phoenixdigital:
I had a look at the original description and Richthofen never mentioned to use the 513.pit file... which firmware did you use? Was it one that needed the 513.pit... most recent firmwares are using the 512.pit... you must match the pit to the firmware as mentioned on

http://www.samfirmware.com/WEBPROTECT-i9000.htm

I think thats what caused your bricking.