yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
OK, here you go, I am making a JTAG adapter PCB for galaxy s. I need to test my pcb, so I bought an as is I9000M from ebay to test my PCB. The phone is in prefect physical condition, except the infamous bootloop problem.

Jump to the steps: http://xdaforums.com/showthread.php?p=16044873#post16044873

Jump to the screen shot of his SD card size: http://xdaforums.com/showthread.php?p=16042946#post16042946

Jump to my progress -> I need some help, I have problem repack kernel Please help me -> http://xdaforums.com/showthread.php?p=16045474#post16045474

Jump to partition SD card on windows: http://xdaforums.com/showthread.php?p=16045880#post16045880

I haven't got my JTAG PCB yet, so i thought, hmm, why not try to fix the phone first? so I spent the last two days, read lots of posts and threads including many many informative posts from this site.... and the conclusion was: it can NOT be fixed.

I have tried many methods, the best method so far I had is to have external SD card plugged in, the flash I900XXJPU using odin, then flash speedmod kernel, after I can boot, I then rooted, and unlocked the phone.

By using this method, in Settings -> SD Card and sorage:

External SD Card:

Total Space: Unavailable

Available Space: Unavailable

Internal SD Card:

Total Space: Unavailable

Available Space: Unavailable

Internal Phone Storage:

Available Space: 1.84GB

The following things work:

1: can make calls or receive calls (using a 7-11 speakout sim card, I think it pigback on Rogers network)

2: can install most apps from market

3: most preinstalled apps work

The following do NOT work:

1: camera

2: video

3: can NOT install any app which require access to /sdcard

I almost gave up, one blog post from coolcode dot org caught my eyes, he has a Korean galaxy S (M110S) with a damaged internal SD card and HE FIXED THE PROBLEM!

this is the original post:

http://www.coolcode.org/?action=show&id=364

It is in Chinese, so I will continue and translate it here...
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Before I translate the steps he did, let me post a pic of the fixed phone.

translation:

Internal SD Card:

Total Space: 12.90G

Available Space: 12.90G

Internal Phone Storage:

Available Space: 1.88GB

Available RAM: 98.27MB
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
So his theory is, exchange the mounting point of the internal and external sd card.

His method is different then the posts below:

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

and another thread similar to the above but for I9000.

The above methods doesn't completely swap the internal and external sd card. His method involves kernel modification.
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
ok, this is what he did:

(His was modifying a 2.3.4 VG14 kernel)

Step 1:

Buy a fast micro SD card. Not sure has to be the same size as your internal SD card (I9000M is 16G, I9000 is 8GB), or can be larger. Class 6 or higher is recommended.

Create two partitions, one for /data and one for /sdcard.

partition 1 (mmcblk1p1) is for /sdcard, so it needs to be in FAT32 format.

partition 2 (mmcblk1p2) is for /data, so it needs to be in EXT4 format.

You can format your sd card in Linux or windows. in Windows, you can use Acronis Disk Director Suite.

Step 2:

You need a linux system, any linux is ok, SUSE, Redhat or Ubuntu.

Step 3:

Download samsung arm linux toolchain sdk, can be downloaded from here: http://cs.sch.ac.kr/~choicjy/entry/MV6410-Samsung-Arm-linux-toolchain

Step 4:

untar or unzip then move the whole directory to /usr/local/arm, if you don't have this directory, create it. (why this directory, because one script we will use has hardcoded the above path)

Step 5:

Find the kernel file (zImage) you want to modify (should be in the PDA file if odin format, or inside update directory of the update zip file)

Step 6:

Decompress the zImage file. We need a tool for that. you can download it from https://github.com/mistadman/Extract-Kernel-Initramfs

Step 7:

Run unpack-initramfs zImage, you will get a initramfs_root directory, it contains all the files we need to modify.
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Step 8:

Since we need to format /dev/block/mmcblk1p2 to ext4, however, we don't have mkfs.ext4 in initramfs_root, so we need to copy one from http://u.115.com/file/e6yxxut0 , use the same method to decompress zImage to a different directory, then copy mkfs.ext4 from tegrak directory to ROM ? initramfs_root/sbin of the original kernel we are going to modify.

Step 9:

Now, we need to modify the following 5 files:

init.rc
fota.rc
recovery.rc
res/encryption.conftab
res/recovery.fstab

Step 10:

The theory is to exchange external and internal sd card mounting point. for example, if you see this:

mount ext4 /dev/block/mmcblk0p2 /data rw nosuid nodev noatime nodiratime wait barrier=1,data=ordered

replace it to:

mount ext4 /dev/block/mmcblk[SIZE="7"][COLOR="Red"]1[/COLOR][/SIZE]p2 /data rw nosuid nodev noatime nodiratime wait barrier=1,data=ordered

Search mmcblk and replace one by one manually for all 5 files.

Also, there are some lines regarding to

/sdcard

in fota.rc,res/encryption.conftab and res/recovery.fstab. make sure to change them as well.

in encryption.conftab:

/ext_sdcard /dev/block/mmcblk1 /dev/mapper/extsdcard sdcard1 vfat PROTECTED_WITH_PASSWORD

replace mmcblk1 to mmcblk0.

Step 11:

add:

chown root root /sbin/mkfs.ext4
chmod 750 /sbin/mkfs.ext4

after

chown root root /sbin/fat.format
chmod 750 /sbin/fat.format

They appear in init.rc and recovery.rc. he is not sure if these are needed.. but he added it anyway.

Step 12:

Modify recovery.fstab to format /data in ext4, this is modified content:

[device]
# mount point fstype device format option mount option
/efs rfs /dev/block/stl3 default default
/system rfs /dev/block/stl9 default default
/dbdata rfs /dev/block/stl10 rfs16 default
/cache rfs /dev/block/stl11 rfs16 default
/sdcard vfat /dev/block/mmcblk1p1 default default
/data ext4 /dev/block/mmcblk1p2 ext4 default

[format]
#index option
rfs16 "/sbin/fat.format -F 16 -s 1 -S 4096"
rfs32 "/sbin/fat.format -F 32 -s 4 -S 4096"
ext4 "/sbin/mkfs.ext4"

[mount]
#index flags options
rfs_opt1 nosuid,noatime,nodev,nodiratime "check=no"
rfs_opt2 ro,nosuid,nodev "check=no"
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Step 13:

Now we need to modify vold.fstab and vold.conf. Since they are not in kernel, we need to workaround the problem.

first use adb shell or whatever way to get vold.fstab and vold.conf from system/etc to your pc and swap the mount point:

something like this:

vold.conf

0. ## vold configuration file for the emulator/SDK
1.
2. volume_sdcard {
3. ## This is the direct uevent device path to the SD slot on the device
4. emu_media_path /devices/platform/goldfish_mmc.2/mmc_host/mmc2
5.
6. media_type mmc
7. mount_point /sdcard
8. ums_path /devices/platform/usb_mass_storage/lun1
9. }

vold.fstab

0. ## Vold 2.0 Generic fstab
1. ## - San Mehat (san@android.com)
2. ##
3.
4. #######################
5. ## Regular device mount
6. ##
7. ## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
8. ## label - Label for the volume
9. ## mount_point - Where the volume will be mounted
10. ## part - Partition # (1 based), or 'auto' for first usable partition.
11. ## <sysfs_path> - List of sysfs paths to source devices
12. ######################
13.
14. # sdcard mount for the P1
15. # internal sdcard
16. {
17. ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
18. asec = enable
19. }
20. dev_mount sdcard1 /mnt/sdcard/external_sd 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
21.
22. # externel sdcard
23. {
24. ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
25. discard = disable
26. asec = disable
27. }
28. dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc2
29.
30. #end line ## keep this line

then, copy these two files to initramfs_boot/tmp directory.

search

mount rfs /dev/block/stl9 /system check=no

in init.rc file, you will see there are a few copy command after that, then you will see this:

exec umount

add the following after

exec umount

:

# switch external mmc & internal mmc
copy /tmp/vold.fstab /system/etc/vold.fstab
copy /tmp/vold.conf /system/etc/vold.conf

so the purpose is to copy these two files from /tmp to /system/etc when system boots.

Step 14:

Now we are done modifying. Time to repack.

First, we need to create initramfs.img file.

create a script in the same directory as the original zImage, lets call it pack-initramfs:

#/bin/bash
cd initramfs_root
find . | cpio -H newc -o > ../initramfs.img
cd ..

Step 15:

We need another script to do the repack, download from here:

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

unzip to the same directory as zImage, you will see a directory kernel_repacker is created.

Step 17:

Run:

./editor.sh ../zImage ../initramfs.img

You will get a new_zImage.

rename it to zImage.

If you just want to flash the kernel, package it in tar format and use odin to flash it:

tar cvf ExtSD-Kernel-for-M110S-2.3.4-VG14.tar zImage

or put back to the original ROM or update file and flash the whole ROM or update using recovery menu.
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
OK, I have finished translate of the original blog post. Let me continue with my own progress.

My phone is I9000M from bell.

This is my phone's symptom.

If I place my 16G external SD card in the slot and flash I9000XXJPU ROM, I can boot the system and I can see the following in /dev/block:

/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2

If I do NOT place external SD card in the slot, after I flash I9000XXJPU, it goes to bootloop. I have to flash the speedmod kernel, after the, system boots, but I do NOT see any files start with mmc in /dev/block.

I think this is different than the blog post.

Anyway, I went ahead and downloaded the JVP update.zip ROM for BELL I9000M from <link to be posted>, extracted zImage from it, now I am stuck at step 17. When I run this command:

./editor.sh ../zImage ../initramfs.img

I got this error:

##### My name is ./editor.sh #####
##### The kernel is ../../zImage #####
##### The ramdisk is ../../I9000M.JVP/updates/initramfs.img #####
##### 01. Extracting kernel from ../../zImage (start = 18324)

gzip: stdin: decompression OK, trailing garbage ignored
7034672+0 records in
7034672+0 records out
7034672 bytes (7.0 MB) copied, 32.3349 s, 218 kB/s
##### ERROR : Couldn\\\\\\\'t match start/end of the initramfs .

So I cannot repack the kernel. Anyone can help?
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
I also have a question, when we flash the ROM (PDA/Kernel, MODEM, CSC files), where are they resides? On good partition of the internal SD card, or a completed different hardware? If it is later, then in theory the method posted in this thread should work for everyone.
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
This is how to format you sd card in windows:
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Anyone has an I9000 with damaged internal SD card? can you please try it out? I am stuck at repack kernel step... :-(

BTW, you need to find the correct kernel for your model.
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
I asked the blogger why my external sd card showed up as mmcblk0 (not mmcblk1), he said that is for the model of my phone... I am not sure if he is correct, but in my original rc files, I do see the internal device id is mmcblk0.

why system do not see mmcblk0?
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
OK, I made some progress. I know why kernel_repack failed.

The cpio image in the kernel I have is gzipped. kernel_repack is expecting an uncompressed cpio image, thus it failed.

Now, I need to modify editor.sh in kernel_repack to read gzipped cpio.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Mr Woolf:
Interesting post, good luck mate.

S.U.R.F.A.C.E 2.something
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
ok, another update.

for some reason, my i9000m decided to shut down, when I power it up again, the internal storage becomes 0.0, so this is the new storage spaces:

External SD Card:

Total Space: 0

Available Space: 0

internal SD Card:

Total Space: Unavailable

Available Space: Unavailable

Internal Phone Storage:

Available Space: 0.0GB

Why?

B: found another script to do the repack of the zimage:

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

however the script did not work for me:

I always get this error:

./repack-zImage.sh -uv

Warning: there is aready an unpacking directory. If you have files added on

your own there, the repacking result may not reflect the result of the

current unpacking process.

mkdir -p /work/arm/1/zImage_unpacked

cd /work/arm/1/zImage_unpacked

repack-zImage.sh: Can't find a gzip header in file 'zImage'

Terminated

I am using openSUSE 11.2 "Emerald" - Kernel \r (\l).

I tried 2 zImages, one is from

http://derek.theblog.ca/galaxys-i900...rbread-upgrade

(file: http://www.multiupload.com/N8D9XZ1PIF)

and the speedmod kernel speedmod-kernel-k13e-500hz.tar

Both result the same error.

I tried both V6 and V4 of the script, same thing

Anyone can help?
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Now I know that you are really investing some time in this but it is a hardware failure so its not really fixed permanently, just permanently rerouted to external sd card?

Aren't even the oldest SGS i9000m's under a year old and thus still under factory warranty (provided you flash a stock rom to it - and then it will not boot).

I know you are supposed to have receipts but I think they can do without also. Have you tried that route or is this just about a challenge?
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Will yes, permanently route to external sd card.

I don't have a receipt, yes, I believe it is under one year old, on the back of the machine it has 10.09 printed.

So, how do I get it fixed by Samsung? Call samsung and tell them I lost receipt if they ask? Any recommendations or success stories?

Also, can you please point to me the stock ROM? Since my unit did not start when I got it, I don't know which ROM it has.

Thanks!

BTW, read a few more posts and figured the modified initramfs has to be equal or smaller than the original one. Most custom initrams from xda are already gzipped, thus if I want to add something in initramfs, the size of the initramfs is going to be larger than the original one, thus it won't work... or I need to delete some thing in the initramfs not important (I don't know which to delete), or modify a stock rom, people mention that the stock initramfs is not compressed thus I can add stuff in and gzipped.

Thanks!
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Stock roms are jh2 éclair, jl2 and kc1. The last two need dbdata.rfs to be complete for a flash with repartition ticked or you can flash jh2 with repartition and then the others without as I think it has dbdata.rfs.

And lots of people have gotten warranty without receipts. Read through I9000M links in stickies in general section.
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Thanks. called Samsung service number in Montreal around 9AM EST, gave serial number, asked when did I purchase it, I said I purchased 2nd hand, but the machine has 10.09 printed. Rep agreed to repair it for me. I was told that I would receive the instruction in 10 - 30 minutes and a UPS label in 12-24 hours/ However, 3 hours after, I still don't receive any emails from Samsung nor UPS.

Usually how long it takes to receive the instruction email from Samsung? and how long it takes to receive the UPS　shipping label?

Should I call them again?

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Sure why not?
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Thanks gfacer!

I got the label later, did not receive any instructions, so I just mailed the phone with battery. I took out my sim card and external sd card.

Hopefully they can receive it tomorrow and I will have the phone back next week!

thanks!
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Wasn't that easier? Though I was impressed by your enthusiasm!
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Yes, that is a lot easier!

Though I probably will get a working phone from Samsung, but I do hope the more experienced developers or users can continue to make progress on the method for their dead phones!

Thanks and have a nice one!
[Galaxy S I9000 Q&A, Help & Troubleshooting] alkalain:
Did you try this? It worked for me.

http://xdaforums.com/showthread.php?t=984140
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
I think that is for the dbdata error in mounting, its different from this error in cause and remedy unless you had the same partition error?
[Galaxy S I9000 Q&A, Help & Troubleshooting] alkalain:
My phone was partially bricked.

I got the message E: Can´t mount /dev/block/mmcblk0p2

I try a method describe in the forum ( didn't found the link) that consist to flash a old Eclair rom and a Froyo rom after. I was able to boot but not without my external SD card. My phone wasn't seeing any storage available, cant install any app, so each time i need reboot the phone, all settings were gone.

Now with the method in the link on my previous post, i recover my internal SDcard and i can boot whitout external SD card.

I flash DbData.rfs.tar, let the phone boot, it remount the internal Sd card, and after i flash ugjl2 rom that come with a bootloader.

Now i run Darky's rom 10.2.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Cool! I guess sometimes it is just corrupted...
[Galaxy S I9000 Q&A, Help & Troubleshooting] brisk5181:
Thanks for the information.

I think yours is different, the physical sd card is defective on mine, but yours is just corrupted partition or kind of "soft" defect.
[Galaxy S I9000 Q&A, Help & Troubleshooting] alkalain:
Oh!, isee.
[Galaxy S I9000 Q&A, Help & Troubleshooting] yellowlabdog:
How to determine whether it is a "soft" or "hard" internal SD problem. If it is a "Hard" problem I need to send it back to samsung HK to repair, shipping cost seem not cheap.
[Galaxy S I9000 Q&A, Help & Troubleshooting] phzi:
Samsung should cover shipping both ways.

If you flashed a ROM and it got "bricked" at that moment, it is very unlikely to be a real brick. most sdcards degraded over a period of time. There is lots of info on this, so do a search.

Ot: I originally remapped an external card for my failed internal sdcard last year. It does work, but is very pointless when Samsung is obligated to repair the phones under warranty. The faulty sdcards are such a well known issue that Samsung is likely to fix this even for a while after the 1yr warranty imo.
[Galaxy S I9000 Q&A, Help & Troubleshooting] mohamedinfis:
the link not work http://cs.sch.ac.kr/~choicjy/entry/M...inux-toolchain
[Xoom Q&A, Help & Troubleshooting] abello00:
Alright, So I just bought a US Wifi Xoom yesterday and got all the updates up to Android 3.2.. So far so good. Now I'm trying to tether it to my touch pro 2 (windows mobile 6.5). So the first obvious problem I came around was that the Xoom is not able to detect ad-hoc networks. I searched the forums and found that the only way around this was to root the xoom and change some files/settings not something that I am comfortable doing yet with android (I'm an android Noob). The other way around this would be to get the Touch Pro 2 to broadcast the SSID in infrastructure mode and I wasn't able to find any programs that were capable of doing that (I currently have Tom Codon's Wifi Sharing App and ICS Control 0.2.1) So I then went ahead and tried tethering via Bluetooth to find out that the Xoom only supports tethering to NAP devices and my Touch Pro 2 (as of now) is only able to set up a PAN.

Does anyone know of a way to tether these two things together preferable without rooting the Xoom?

If the only way for a Xoom to tether to a Windows Mobile 6.5 device is to root the Xoom, could someone provide me a link to a guide for Noobs rooting the Xoom (I did find the 1 Click app, however I wasn't able to download it.. it was a password protected file on mediafire.com) An app that rooted the device for me would be ideal.

Thanks in advance.
[Xoom Q&A, Help & Troubleshooting] 2ksilverbullet:
I'm using WMWifiRouter on my Win 6.5 phone (Omnia II - Verizon). You'll need to use the bluetooth tether option. It's not the fastest but it works.
[Xoom Q&A, Help & Troubleshooting] mr_wrong_0:
+1 to Bluetooth tether on the wifi router app for Winmo. That would be the only way to do it without rooting the Xoom.

If you do root the Xoom (which is easier than you probably think) you can flash the zip file in my signature (via ClockworkMod recovery) to add ad-hoc connectivity to the Xoom.

This is the best guide for beginners IMHO: http://xdaforums.com/showthread.php?t=1130996

Either way best of luck.
[Xoom Q&A, Help & Troubleshooting] abello00:
What version of WMwifirouter are you guys using? I know everything before 0.91 is free but I don't know if it supports bluetooth networking.
[Xoom Q&A, Help & Troubleshooting] mr_wrong_0:
I use Android myself but a google search lead me to this post on PPC geeks.

"go to settings-connections-wifi-network adapters

then go to remote NDIS HOST

For Bluetooth. go to the "Bluetooth PAN Driver"

use the settings below for Bluetooth tethering to work:

192.168.0.1

255.255.255.0

gateway: leave blank"

Thought it might help if you find a version of wifirouter to use.
[Xoom Q&A, Help & Troubleshooting] abello00:
I'm assuming the settings-connections wifi network adapators remote ndis host is for the windows mobile phone? I'm done see where remote NDIS Host shows up.

As for the Bluetooth PAN Driver, I tried running the wm6btpan and when I execute it on the phone, I get Error 1062.
[Xoom Q&A, Help & Troubleshooting] iNdioNicarao:
I have a TP2 and a Xoom.

I would suggest rooting, flashing CWR and then the ad_hoc enabling patch.

It is quite simple to do, follow the link someone posted above...
[Galaxy S II Themes and Apps] fosseperme:
TASKBAR CYANO STYLE FOR COGNITION S2!!!

Download here (apply zip from clockwork recovery)
[Galaxy S II Themes and Apps] xp3rto:
what clock is that ?
[Galaxy S II Themes and Apps] mach0boi:
Beautiful widget :)
[Desire Q&A, Help & Troubleshooting] Taqyon:
Hi all

I've just managed to do a Unrevoked root, and went in with ADB while in recovery and removed some APKs.

When I restarted my Desire would not reboot!! It just loops the HTC Screen - Vibrate - Blank and back!

I can still get into ClockworkMod recovery.

What can I do to fix!?

Many thanks
[Desire Q&A, Help & Troubleshooting] BigMrB:
reflash your rom or restore nandroid
[Desire Q&A, Help & Troubleshooting] Taqyon:
Thanks, but sorry no idea how to reflash. I've tried running the RUU exe from shipped roms, but it would not see my Desire. It's currently on the hboot menu. I can go into the ClockworkMod recovery menu, but it would not see it either.

I can connect over ADB.

Any links to some instructions on how to flash any working rom would be great - I'm desperate!!

Thanks!
[Desire Q&A, Help & Troubleshooting] p1yke:
Simply dowload a rooted 2.2 rom from the forum, then put this on your sd card and simply go to install zip from the recovery menu and that should do it.
[Desire Q&A, Help & Troubleshooting] Taqyon:
Yes thanks figured it out eventually ;) I tried Oxygen but it's Senseless, so to speak. I tried the stock roms again and could get it to work while in the fastboot menu. I'm now doing an OTA update.

Crisis averted.

No more rooting or flashing for me thankyouverymuch.
[Desire Q&A, Help & Troubleshooting] bortak:
Why? Have you tried any other ROMs? there are a lot of benefits with a rooted phone.
[Desire Q&A, Help & Troubleshooting] BigMrB:
I agree - try reflex s - has sense and is better than stock !!