@koe1974:
I cant seem to download your link regarding the .tar on page 7 that you posted...
Files will be available for 24 hours
1pm KST
@koe1974:
I cant seem to download your link regarding the .tar on page 7 that you posted...
@appagom
Must have missed something in the trail here, but I haven't found your solution to #3 above regarding the exploit. Please elaborate. Tks.
@Justin
Jumped the gun a little...
I managed to Root (both soft and permanent) and I managed to get the lag fix. But after the lag fix, you must get the root back (since they use the same exploit, they overwrite the same file).
No need for concern first, anyone trying this should just get the temporary root thing to work, just a matterr of pushing and running one file. If it works you're good. You can ALWAYS get root this way and undo things. The rest is just a matter of customizing the bootup to run everything you want including automatically giving you a root prompt again.2) you can apply the lag fix, but it overwrites the root exploit, leaving it unrooted (which also means you cannot un-lag)
#!/bin/bash
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb push joeykrim-root.sh /sdcard/joeykrim-root.sh
adb push jk-su /sdcard/jk-su
adb push playlogo /sdcard/playlogo
#make a backup copy of the original playlogo
# only do it once to make sure it doesn't get overwritten by a modified version$
if [ ! -e playlogos1-orig ]; then
echo "backing up playlogo file"
adb pull /system/bin/playlogos1 playlogos1-orig
fi
adb shell sync
#push the backup onto the sdcard so it can still be used
adb push playlogos1-orig /sdcard/
adb shell sync
#!/bin/bash
adb shell << EOF
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp
./rageagainstthecage-arm5.bin
EOF
#!/bin/bash
adb shell << EOF
mount -t rfs -o remount,rw /dev/block/stl9 /system
cat /sdcard/joeykrim-root.sh > /system/bin/joeykrim-root.sh
cat /sdcard/jk-su > /system/bin/jk-su
cat /sdcard/playlogo > /system/bin/playlogos1
cat /sdcard/playlogos1-orig > /system/bin/playlogo-orig
chmod 755 /system/bin/playlogo-orig
chmod 755 /system/bin/playlogos1
chmod 755 /system/bin/joeykrim-root.sh
exit
EOF
#!/bin/bash
adb shell << eof
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
exit
exit
eof
adb push playlogos1-orig /system/bin/playlogos1
adb shell sync
adb shell << eof
su
chmod 755 /system/bin/playlogos1
exit
exit
eof
adb shell << eof
su
rm /system/bin/joeykrim-root.sh
rm /system/bin/jk-su
rm /system/bin/playlogos1
rm /system/bin/playlogo-orig
rm /etc/passwd
rm /etc/group
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit
exit
eof
For those who might be faced with having to deal with A/S in Korea I thought I might tell my story as things progress.
First, you have to understand my wife was pissed because I always break my phones and it means she has to deal with it, but I told her I am going to handle it. I know enough Korean to get around but hardly enough to talk a Samsung Tech. through what I did to my phone. Let alone do I want admit to them I have been flashing more than a drunk 21 year old college girl at Mardi Gras.
09/25/2010
While trying to restore by primary and secondary bootloaders I bricked it. Yes, really. Tried AC, new battery, fully charged batteries...nothing. No power, no download mode, no nothing. Completely dead. So for future reference it can be bricked. It wasn't easy but I did it.
09/26/2010
Brought my phone to the local Samsung Store, not the shop I got the phone from. The phone shops only deal with contracts and most do not have the resources or knowledge to fix a phone. They will just send it to a Samsung store so save yourself a day of waiting.
I thought I would play dumb and I said very simply in English, "Software Upgrade", pushed all the buttons, showed him that nothing happened, shrugged my shoulders and made a sad face.
He took the phone, pushed all the buttons, took out the battery, plug it into a charger and upon seeing it was dead grabbed the stack of service tickets.
He asked for my name and phone number. I told him to make a note on the service ticket that I only speak English by saying, "Memo" and made a writing gesture. "No Korean, only English." He understood and jotted some Korean on the ticket. He told me it would be 1 week.
09/27/2010
Someone from Samsung generally calls the next day but I didn't get a call today. So far so good.
09/28/2010
Samsung called today at around 1pm. The guy spoke English relatively well. He asked, kind of jokingly but with and annoyed tone, "What did you do?".
I said, "I updated with Kies but it failed."
It was silent for a few seconds and then, "Change memory, will don't save memory, 'couldn't understand' mainboard. Original settings, okay?"
"Okay", I replied.
"Finish Samsung Store tomorrow, night time." he said.
"Do I have to pay?", I asked.
He chuckled, "No pay."
We said good-bye.
At 7:45pm the guy at the Samsung Store gave me a call and told me my phone was done. I have it back in my possession. Written in Korean on the Service ticket is Mainboard Changed.
All in all it was painless and fast.
Anyone know the correct registry settings for the m110s to perform the Kies hack?
keo1974,
I'm having a smiliar issue with you -- flashed a HK ROM (bml1&bml5 is sadly overrided). Although I've had it flashed back to Korean ROM, but only DH23 works, DH09 and other versions don't :-(
Now the problem is the DH23 on my phone cannot do GPRS or 3G (I'm in China). I don't know what's wrong with it. I was thinking to fix bml1&bml5 by flash a stock image dump from others and then it should be able to flash an older ROM. Many times I was just about to flash them, but just not brave enough :-D And then I read about your story ...
So there is no known and reliable way to fix bml1 and bml5 without help from Samsung? Not sure if Samsung in China can do it ... anyway, I'm using a Korean version.
I'm also curious why Korean ROMs do not have boot.bin and Sbl.bin while Hongkong ones have ..
congratulations that you have your phone fixed :-D
Your situation is same to me and I fixed it by enable the 3G Data setting widget. Try this, I'm sure it works
Final Solution:-Other methods deleted by Mod
[highlight]Mod Edit: While I understand that the purpose of this guide is to help those who have lost their IMEI's while flashing ROMS, this opens up a whole new can of worms as far as what can be done with it. The outcome is illegal in most countries in fact. Sorry.[/highlight]
Last edited by egzthunder1; 28th August 2012 at 09:05 PM.
Using Repair Kit to Unbrick M110SFirst stage :- For every Stage of Flashing RESTART ODIN and always use Fresh ODIN
1) download repair kit and unzip it (you will have 6 tar files)
2) put phone into download mode after battery pull
2) run odin and select m110s.pit under PIT (Re-partion option will be automatically ticked)
3) select M110S-PDA-PHONE-MOVI-REV03-DG23-1409-USER.tar.md5 under PDA
4) connect phone and Press start (within 10 min your phone will reboot into Eclair Firmware)
you will have a fully working phone after this, only needs further updates, so continue to stage 2
Second stage:-
1) put phone into download mode after battery pull
2) run odin select S1_KOR_DE09.pit under PIT (make sure you UNTICK the re-partition option in Odin)
3) select M110S-BOOT-DG23-1409.tar.md5 under CSC
4) connect phone and press start (within a few min phone will reboot)
Third Stage:-
1) put phone into download mode after battery pull
2) run Odin select M110S-NPS-IMAGE-REV03-DG23-1409-USER.tar.md5 under PDA
3) selct M110S-PHONE-REV00-DG24.0151_Develop.tar.md5 under PHONE
4) Connect Phone and select start ( within few min phone will reboot )
Fourth Stage:-
Your Phone is currently running its FIRST out of the box Firmware used in 2010 , so now you need to upgrade to the latest 2012 Stock ROM or Custom ROM of your choice so repeat Flashing Procedure to upgrade to Latest Firmware
IF unable to complete repair procedure
Final Solution:-
After receiving many requests for help, concerning stage 2 of the repair procedure, Failing or unable to complete as it gets stuck on Boot-loader upgrade or similar
My advice is to proceed to stage 4, meaning you Flash a Latest stock or custom after the Eclair ROM, this will solve the issue and you would be able to USE the phone .
so if it get stuck after stage 1 ( meaning phone functions using the oldest ROM ) , just continue to stage 4 and flash the latest ROM
Welcome to Pit StopEverything for and about the Korean Anycall Galaxy S from SamsungComments, Suggestion, Errors and Omissions are welcome.
Just register at XDA and post on Anycall forum
Be Advised that Most Mobile Phones have their own WIKI page on XDA Forum providing compiled knowledge about that particular phone and using them can provide many details that you may not be aware of, so always do a search first on the Wiki page for your unit.
Whatever you have done or may do with your phone because someone said so, is still your responsibility ...so take your time READ carefully to avoid making mistakes in haste, be calm and recheck the details.
Tested on FroYo firmware versions DI29 and SK05
Prerequisites:
rooted (I also recommend SuperUser)
busybox installed
You understand the benefits of being able to connect to a stateside OpenVPN server.
openVPN server account
-Removing the SIM card
-Placing it in another phone that has the "My Number" option (I used an iPhone, heard that older Sony Ericssons work too.)
-Entering my own number in international format (+63917~) (Prior to this, "Unknown" was also shown in the iPhone.)
-Inserting the SIM back to the M110s.
TouchKey F/W Info - *#86824#
- Has an "F/W Update" Button
- Can set the "Menu" and "Back" key sensitivity
From the dialer enter: 319712358
You will be prompted for a pasword: 774632