yashsingh1/xdaforums huggingface dataset:
[HD2 Windows Mobile 6.5 ROM Development] kurt-willems:
First of all thanks fore communication, (but it was communicate already before :o)

Secondly if you need a download mirror you can find it here.

Thirdly, all Stock Rom versions 3.14 need to be install without HSPL.
[HD2 Windows Mobile 6.5 ROM Development] kurt-willems:
Eh?? isn't this not without HSPL???

I mean you mention to have SPL, so not HSPL!?
[Nexus One Android Development] mikerackhabit:
I'm very close to having a working sshfs setup. I've got:

working fuse.ko module

working version of openssh ssh client

working version of sshfs

I can happily mount remote file systems and use them just fine, but when I try to unmount them, my phone just locks and then reboots. I'd like to try and debug this, but I get no messages in any log that I can see.

So my question is, if I'm getting some kind of kernel panic, where can i see what's actually happening to try and debug this.

Any thoughts on what might be causing this would also be much appreciated.

I'll post full instructions once I get everything working of course.
[Nexus One Android Development] Alex240188:
can you not run "adb shell cat /proc/kmsg" to check for any Kernel Panic's
[Nexus One Android Development] charnsingh_online:
cat /proc/last_kmsg will get u the details of kernel panic and help u debug

if u want to save it to a file then type

cat /proc/last_kmsg > /sdcard/kmsg.txt
[Nexus One Android Development] endomurat:
hope this helps, remove spaces (since I am new user not allowed to post external links )

www rt-embedded com / blog / archives / resolving-alignment-traps /
[Nexus One Android Development] gubacsek:
Any news with this? I would be more than happy to have a working sshfs on my phone :P

Wish You best luck!
[Nexus One Android Development] waspbr:
ditto, has anyone managed to get sshfs working?
[Nexus One Android Development] mkasick:
I run sshfs on my Epic. I compiled the FUSE kernel module (fuse.ko) from the stock Samsung kernel sources and installed the pre-built userland dependencies (sshfs, fuse-utils, openssh-client, etc.) in a Debian chroot. I mount sshfs "volumes" in the chroot using the "allow_other" option, so that any Android uid/gid can access them.

The chroot probably isn't necessary, but I didn't want to bother compiling the userland dependencies myself. This article gives some directions on how to build a Debian chroot. I don't wase time with the unionfs stuff though, I just bind mount /dev, /dev/pts, /proc, & /sys.
[Nexus One Android Development] waspbr:
thanks, gonna have a go at it once my schedule clears up
[Nexus One Android Development] r2DoesInc:
any progress? ive been thinking of using something like this on a Galaxy tab, make it a portal to my remote developer machine.
[Nexus One Android Development] kdb424:
Sorry to bring up a dead thread, but it seems that there is at least a chance at sshfs. Seeing as I have a need or at least a strong desire to get this working, any chance someone figured it out?
[Nexus One Android Development] Phk:
Aaaaaaaaand, reviving this Thread again... sorry...

Anyone managed to get SSHfs properly working?

Thanks!
[Galaxy Tab General] Clowneh:
I've got an annoying problem that I don't know how to fix.

I have a script that uses handbrake to encode videos for me and spits them out as a .mp4 file. I used to view these from a local open web directory so I could stream them while I was in the bath or in the kitchen or having a dump or whenever I wasn't in front of my TV.

They work on my iPhone, iPod touch and on the various Android things I put on my HD2. How can it work on a flashed WinMo phone and not on a proper Android device?

What's frustrating is that they work when I transfer them over using Astro or downloading them in the browser. I assume it would work if I put them on a memory stick but all of these solutions take more time.

I was thinking I should root the Tab and put a custom Android on it, but is there anything else I can do without re-encoding a bunch of files?
[Galaxy Tab General] ftgg99:
What exactly is the problem? How are you trying to stream them?
[Galaxy Tab General] Clowneh:
I have an open web directory which is basically just a list of .mp4 files. I open the browser and point it to my site, 192.168.1.3/movies, and then click on whatever I want to watch.

Then usually it gives me an option of what app I want to play it in and I usually just pick the default video player.

This doesn't work on the Tab where it does on my other devices (Android and iOS).
[Galaxy Tab General] mklass:
So the problem is that its not giving you an option to pick which app to open the .mp4 with?

Maybe you dont have any other apps that can play the file?-
[Galaxy Tab General] Clowneh:
It does give me an option, it just refuses to play saying that the type is not supported. I've tried the built in video player, rockplayer, meridian. I've also tried it on a file manager like Astro.

The files just refuses to play like they do on my hacked HD2 and iPhone.
[Galaxy Tab General] cmloo:
Are you trying to emulate this like the AllShare program? Cant seem to get this to work too on the network media
[Galaxy Tab General] Clowneh:
I don't know what AllShare is unfortunately. Did it work on a previous device?
[Galaxy Tab General] ftgg99:
Allshare is sammys DLNA client. Its pretty good for small folders on a LAN server. But it doesn't understand headers very well. Search is your friend.
[Galaxy Tab General] Clowneh:
Someone pointed me in the right direction on another board.
[Android General] tweakradje:
Okay. It is quiet here but lets continue. Now I found the service menu of the phone.

*#*#197328640#*#* (works on more phones?)

MAIN MENU

[1] DEBUG SCREEN

[2] VERSION INFORMATION

[3] UMTS RF NV

[4] GSM RF NV

[5] AUDIO

[6] COMMON

[7] QXDM LOGGING

When entering into COMMON sub menu I have

[1] FTM

[2] DEBUG INFO

[3] RF SCANNING

[4] DIAG CONFIG

[5] WCDMA SET CHANNEL

[6] NV REBUILD

[7] FACTORY TEST

[8] FORCE SLEEP

[9] GPS

NV in the menu's stand for Non Volatile RAM I suppose.

Menus control can be clicked or use the menu button for BACK

2Bcontinued...
[Android General] tweakradje:
Some codes for typing in from the firmware:

#*2886#
*#*#28346#*#*
*#0*#	lcd test
*#0002*28346#
*#0002*28347#
*#0011#
*#0228#
*#0283#
*#0289#
*#03#	NAND Flash uniek nummer (80590001238648)
*#0368#	FM Radio test
*#0588#	Proximity test
*#0589#
*#0599#
*#06#
*#0673#	MelodyTest
*#07#	Test History
*#0782#	PDA RTC Get
*#0842#	Vibration Test
*#1*#
*#1111#
*#1234#	Version
*#1472365#	Gps2 setup
*#147852#
*#1478963#	Test app settings
*#1575#	Gps setup
*#197328640#	Main Menu Service Mode
*#2222#
*#2263#
*#22736224#	Acc calibration
*#232331#	BT Test
*#232332#	BT On
*#232337#	BT Mac
*#232338#	WLAN Mac
*#232339#	WLAN Engineering mode Tx Rx Status
*#2424#
*#2454#	Ram dump mode (ARM9) take battery out
*#2580#	Integrity control
*#2663#	Touch screen version
*#2664#	Little paint programm
*#272*
*#273283*255*3282*#	Data create, fill up sms phonebook callog etc
*#273283*255*663282*#	Data create, fill user/systemspace image mp3 video voice memo
*#2767*2878#	servicemode nothin?
*#3214789#	GcfMode settings
*#32489#	Ciphering control
*#3264#	Ram version
*#3282*727336*#	overview data usage
*#34971539#
*#367#
*#3695147#
*#369852#
*#4238378#	GCF settings
*#42663#	Brightness setting
*#44336#	Internal version build time changelist
*#46744674#
*#4736767*738#	Acc sensor min/max
*#4986*2650468#	Version
*#526#	WLAN test
*#528#	WLAN tes
*#6854123#
*#6984125*#
*#7263867*6633# RAM Dump mode Enable/disable
*#7284#	DIAG config serial/usb
*#7298#
*#7412365#
*#742690#
*#745#	Sec Ril Dump !!! log en mms settings
*#746#	Debug Dump
*#7465625#
*#7594#	Enable Shutdown on End call Long press
*#7780#	Standaard gegevens herstellen
*#80#	Factory Test
*#865625#
*#872564#	USB (DM) Logging En/Disable CP AP CP+AP
*#9090#	DIAG config serial/usb
*#9900#	SysDump RIL Ramdump mode Off

*2767*3855#	factory reset !!!
*2767*4387264636#	Sellout SMS PCode Mode:Test
*2767*738767633#
*2767*73876766#
*2767*7387677763#
*2767*7387678378#

*7465625*27*#
*7465625*638*#
*7465625*77*#
*7465625*782*#

#7465625*27*#
#7465625*638*#
#7465625*77*#
#7465625*782*#
[Android General] giri.rao:
Did you try the setprop on the gsm.sim.state by setting it to null/empty.
[Android General] tweakradje:
SP unlock your i5500 (probably more)

EDIT: Phones has been bricked with this stl5 method. Do use supersafe bml5 method.

http://xdaforums.com/showpost.php?p=17148825&postcount=334

Since I can't give up on this one I digged a little further into my i5500 memory.

Guess what? I f.ckin did it. Big hoora. I'am good I know ;) Thank you!

- root your phone
- adb shell
- su
- cd /
- mount -o remount,rw -t rootfs rootfs / (or do it before adb with root explorer)
- mkdir /efs
- mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
- cat /efs/mits/perso.txt
- umount /efs
- reboot

EDIT: stl5 is es-tee-el-five (like STL5)

EDIT: /efs on the Galaxy the /etc/fstab says: mount rfs /dev/block/stl5 /efs nosuid nodev check=no

You will see some numbers: In my case 20404 for Vodafone NL.

Then you will see your SP unlock code followed by some 000000000 codes and another

code. Write the first one (and second just in case) down.

Shut down the phone and put it a "locked" sim. Start your phone, input the pin, and when asked for a unlock code give it the first code. Your phone is now unlocked.

Cheers

EDIT:

Rooting: http://blog.23corner.com/2010/08/30/universal-androot-1-6-2-beta-5/

Rooting newer roms: http://xdaforums.com/showthread.php?t=803682. Need reboot after.

Adb and USB drivers: see attachement

EDIT: possible fix for bad imei after doing above procedure:

http://xdaforums.com/showpost.php?p=15408191&postcount=4

EDIT: nice tutorial for my method - http://xdaforums.com/showthread.php?p=16597429
[Android General] rlewis2737:
Mine is a bunch of 01234567s
[Android General] tweakradje:
using dd command on stl5 is bricking the phone: UNSAFE METHOD

Ok. For good comparison I attached both perso.txt: before and after unlock.

Perhaps that helps. My network was locked to 20404 and the unlock code is 61493638

and there is another code in the file: 92427358 but I don't know what that one does.

Perhaps it is better practise to follow this road for getting the codes:

- adb shell

- su

- dd if=/dev/block/stl5 of=/sdcard/stl5.rfs bs=4096

Then use winimage or similar to examine /sdcard/stl5.rfs as FAT16 image file.

Cheers
[Android General] kill3r000:
- mount root rw (did it with root explorer)

Cannot get passed this step. It only gives me cmd line help. Please describe in more detail on how you did it. Thanks!
[Android General] tweakradje:
Root explorer is a program I installed. It has a "Mount R/W" button for the root.

But you can also use a complete other folder that is already mounted rw.

Type command mount in adb shell. Think /data is rw mounted.

So create /data/efs folder and mount -t vfat /dev/block/stl5 /data/efs

Cheers
[Android General] kill3r000:
For my problem this cmd worked:

mount -o remount,rw /data /system

Let's see if it really works for me 2.

After doing all the steps, my phone cannot turn on Phone, Wifi, cannot do any kind of format, install a new firmware (does not go to step 2 - pass the CS, even if odin reports it Passed). Half bricked it!
[Android General] tweakradje:
WARNING

Strange and sounds dangerous. Better not mount /dev/block/stl5 then and

use dd if=/dev/block/stl5 of=/sdcard/stl5.rfs and use windows program winimage (or similar)

to get the info from mits/perso.txt

But did you unlock?

Cheers
[Android General] kill3r000:
I already did that. No effect, because my WIFI, data, network connections and all audio (don't know about music) do not respond in any way, so, now, my great phone is at Vodafone Romania for repairs. Hope they did not notice any meddling with the firmware and re-flash it to it's original state. It didn't matter if i inserted another network sim or the one registered.
[Android General] BlocK240:
Thanks for this useful info, tweakradje.

Albeit I had run into the same problem as kill3r000, I managed to restore my phone back on track by simply running dd if=/sdcard/stl5.rfs of=/dev/block/stl5.

It ain't relevant at all, but when I retrieved the stl5.rfs from the phone I just did it from a root terminal on the phone, not via adb.

Anyways, thanks again for helping me unlock my phone. :-)

kill3r000, daca aia de la vodafone iti cer bani, nu le da si ia-ti telefonu' ca si eu tot de la voda il am si aceeasi figura mi-a facut-o.
[Android General] kill3r000:
How come i didn't think of backtracking that command? :(( I suppose i was too tired of trying endless methods.

Block240 - Multumesc mult de tot pentru sprijin. Asa am sa fac. Mai tii minte cam cat ti-au cerut? Niste maralni.

Pe mine m-au sunat de la Regenersis ca il mai tin pentru mai multe teste amanuntite :P Pe bune... Va hotarati cat sa taxeze (nici nu se mai pune problema; deja au hotarat: IESIT DIN GARANTIE scrie pe saracutul meu)!
[Android General] vampires.remembered:
Worked like a charm!

Thank you very much for this. Finally, 2.2. ;)
[Android General] tweakradje:
Thanks for the feedback.
[Android General] robilaur:
Hy ... Block can u make a little tutorial for Romania Vodafone users ...step by step or can u contact me on PM and tell me exact steps

Multumesc,
[Android General] kill3r000:
It's better, IF he or other wants to do that, to post it on the topic so can others see it. When i'll have it back from service (if they want money for repairs) i'll try again and then i will ask somebody here for a little tutorial for all this not happend again.

(Multe) Multumiri anticipate!
[Android General] BlocK240:
Nu am ajuns in punctul in care sa trimit telefonul la garantie. Am stat o noapte sa-i scriu diferite ROM-uri si sa-i sterg efs-ul pana mi-am amintit si multumit ca aveam stl5.rfs si pe calculator si pe /sdcard. Fiind un utilizator cat de cat obisnuit cu unix-urile, mi-am dat seama ca un dd salveaza bit cu bit totul. Acum daca as sti si de ce or aparea figurile astea cand e citit efs-ul as fi un om fericit.

Nonetheless, there's nothing special regarding VF Ro users or any other network carriers. I just followed these steps:

su
dd if=/dev/block/stl5 of=/sdcard/stl5.rfs

Copied the stl5.rfs on my computer, opened it up with WinImage (obviously, any other application that can read FAT images would work just as good) and went to /mits/perso.txt.

It's full of gibberish, but do keep in mind that the 8-digit number is the unlock code. Note it down on a paper or something, power down the phone, get its sim out, power it on (don't insert any other sim). Mine went to ARM11 recovery mode (shows the samsung logo and says that on the top left). Should it do that, just throw the battery out and back in, then power it up again. The phone will boot up normally and now run

su
dd if=/sdcard/stl5.rfs of=/dev/block/stl5

wait for it to end, power down the phone, insert a sim that would send the phone in its network locked mode, and se that 8-digit number. That's all about it, you now have an unlocked gt-i5500.

Thank you again, tweakradje.

(dati o bere :) )
[Android General] marcelorider:
yes i know that, and it is not really fully functional, fails 3G and GPS, others are working great :D

Somehow i need to manage some way to change the IMEI and Product Code back to original, there must be some way, im just gonna try for it, if someone's want to help just contact...

Yes i know it's a bad move, but somehow they are great news, theres some bricks here on the forum that are somehow like this one... but my error was in not backing up the /EFS/ because it was already currupted and was saving me a 256kb file with nothing inside =/

Well, im open for testing, because i have nothing to loose, and i love learning so, if someone want's to give a try, contact please :D
[Android General] psyke83:
First: check the IMEI your phone is currently using: *#06#. Write this down somewhere.

Second: check your phone's real IMEI. Turn off the phone, remove the cover and battery, and you'll see the IMEI and serial number. Again, write down the IMEI number.

Third: find a way to edit the stl5.rfs file. You can mount it in Linux via "mkdir efs; mount -o loop stl5.rfs efs/". If you're using Windows, I have no idea.

Fourth: when you have access to the files on the efs partition, do a search for the first IMEI (the one that you "stole" from another user) inside the contents of the files.

Fifth: Replace all occurances of the stolen IMEI with your real IMEI in all the necessary files.

Sixth: put the modified efs.rfs back on your phone.

No guarantees this will work!
[Android General] BlocK240:
UimEfsAPDULog.txt seems to contain everything encoded in hex. Whoever is handy with a hex editor and has time to tinker with that file could probably find where the imei is written and rewrite it with any imei.
[Android General] tweakradje:
IMEI on a cdma phone should be somewhere in the stl5.rfs in the \nvm\num folder.

The number of the file I don't know (there are 760 binary files in there)

Cheers
[Android General] Benjamin Dobell:
I've had a few private messages from various people trying to use Odin to flash/fix their EFS partition with a backup.

Based on the log subpsyke uploaded.

Putting these two bits of info together:

1 - mibib

2 - qcsbl

3 - oemsbl

4 - amss

5 - fota

6 - arm11boot

7 - ???

8 - ???

9 - ???

33 - ???

34 - ???

35 - efs2

36 - ???

37 - nvbackup

You can probably work out more IDs based on the OPS files you already use.

EDIT: For the Galaxy S Odin will totally ignore the selected PIT file (OPS replacement) because it retrieves a copy of the PIT file stored on the device. The copy on the device is only updated when you repartition. If the I5500 is the same then you will need to repartition in order to get your custom OPS file on the device, repartitioning will delete all your personal data though (apps, contacts, messages etc.)
[Android General] wavezhang:
Thank you for your reply. But how to repartition?
[Android General] psyke83:
Thanks for the information, Benjamin.

Here's our OPS file that we normally use:

0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,

There appears to be some discrepancies compared to your reconstructed version (such as the position of fota).

Our version of Odin (v4.28) does not have a repartition option. You can see the available options here (again, sorry for having to obfuscate the link): hxxp://img13.imageshack.us/f/odin428.png/

Typically when flashing a ROM, we enable Auto Reboot and Protect OPS, and disable all debug options. The One Package is used if you have a .tar containing all the individual components.
[Android General] Benjamin Dobell:
Hmm I think I may have made a mistake. I'm out at the moment so I'll take a look in a couple of hours. But you want to match the offsets to the 1stVun.
[Android General] Benjamin Dobell:
Nope, no mistake. The values I gave are correct, at least they are the partition IDs. It's possible the OPS are using some other identification system.
[Android General] psyke83:
Is there any other information from a running phone that may help us find out? Surely if the Odin application was coded with an EFS button, the partition is flashable... but the partition layout reported by the android kernel doesn't match the OPS, so it's hard to know how to modify it.
[Android General] s2003r:
Hi all,

i'm a bit confused as was looking for galaxy ace unlock and found:

http://xdaforums.com/showpost.php?p=12431231&postcount=101

- most replies are related to i5500 mentioning bricks when DD used to get the codes.

Can anybody please confirm if unlock for ace bricks it too ?

Thanks
[Android General] BlocK240:
Safest bet is to run that from recovery mode.
[Android General] s2003r:
Thanks for your reply.

i've seen your thread :

http://xdaforums.com/showpost.php?p=12772293&postcount=174

maybe you could give us the steps taken by you ?

I've also checked :

http://xdaforums.com/showpost.php?p=12688230&postcount=156

did google translate but it did very poor translation.

question:

dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
dd if=/sdcard/stl5.rfs of=/dev/block/stl5

is that a copy from the phone to sd and then back ... what for ? as i understand it should be enough to make a copy of stl5 on sd then analyse it in hex for unlock code.

thanks
[Android General] mihaivt:
Hello,

I have similar problem:

- my phone has no IMEI (cannot connect to network)

- no wifi (because of no wifi MAC)

- no camera

- cannot connect to kies

- phone restarts every 15 minutes

- after I input *#*#197328640#*#* there is no menu. Is just blank

- shutdown phone does not work (screen gets blanked but still power on) > i have to remove the battery in order to start again

What I can:

-start the phone

-enter download mode (and flash successfully)

-connect with adb

How it happened:

- I bought a new sdcard, partition on my computer to include ext2 partition (to use with app2sd)

-restart the phone in recovery mode

-run a script that will create a bunch of small files on sdcard (with the purpose of benchmark)

DON'T DO THIS

for i in `seq 100` do ;dd if=/dev/random of=file$i bs=50k count=1;done

When playing with the script I can see at one moment the phone restart by itself. I did not pay attention to that and continue with my script. (sometime using /dev/urandom instead of /dev/random)

When I started the phone: I cand see I have problems listed above.

So this topic is to warn other people of other possible ways to (semi)brick the phone
[Android General] psyke83:
PLEASE, read this thread fully. Hell, even the first post. Running the commands you quoted will brick your phone. Don't say you haven't been warned.
[Android General] mihaivt:
additional info

I try to recover using posted stl5.rfs

1. first try to backup my existing /dev/stl5

It fails in normal or recovery mode

# dd if=/dev/stl5 of=/sdcard/broken.rfs
dd if=/dev/stl5 of=/sdcard/broken.rfs
[b]/dev/stl5: read error: I/O error[/b]
504+0 records in
504+0 records out
258048 bytes transferred in 0.138 secs (1869913 bytes/sec)

finaly I managed to do some backup like this:

mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
tar -cvf /mnt/sdcard/efs_back2.tar /efs --exclude=2603 --exclude=2635

/efs/nvm/num/2603 and /efs/nvm/num/2635 were broken and give error when try to copy/tar

2. after backup my broken efs i proceeded with recovery from posted stl5.rfs

I receive error when try to write to /dev/stl5

# dd if=/sdcard/stl5.rfs of=/dev/stl5
dd if=/sdcard/stl5.rfs of=/dev/stl5
[b]/dev/stl5: write error: I/O error[/b]
505+0 records in
504+0 records out
258048 bytes transferred in 0.123 secs (2097951 bytes/sec)

after trying different values for bs=xx I find the winning combination (bs=4096)

# dd if=/sdcard/stl5.rfs of=/dev/stl5 bs=4096
dd if=/sdcard/stl5.rfs of=/dev/stl5 bs=4096
5248+0 records in
5248+0 records out
21495808 bytes transferred in 2.303 secs (9333828 bytes/sec)
# dmesg > /sdcard/transfer.log

However I can see that I have the same proble after phone reboot. Moreover, the files 2603 and 2635 (from /efs/nvm/num) are still corrupt.

Although no error during dd using bs=4096 I can still see in dmesg lots of errors like this:

<3>[ 267.857291] end_request: I/O error, dev stl5, sector 39072
<4>[ 267.857349] [SIF:ERR] The partition (PartID 23) is locked by STL
<4>[ 267.857369] LinuStoreIII_NERR: _fsr_dup_write[102] stl: transfer error=80040005
<4>[ 267.857383]
<4>[ 267.857396] LinuStoreIII_NERR: stl_transfer[174] STL: fsr block device transfer error =ffffffff
<4>[ 267.857411]
<3>[ 267.857423] end_request: I/O error, dev stl5, sector 39080
<4>[ 267.857481] [SIF:ERR] The partition (PartID 23) is locked by STL
<4>[ 267.857501] LinuStoreIII_NERR: _fsr_dup_write[102] stl: transfer error=80040005

Some conclusions:

- reading/writing from dev/stl15 always fails after 504 blocks of 512K (I see this on the log posted by the other user who recovered from web stl5.rfs)

- according to my log it seems there is some process who puts a lock on /dev/stl5 (no matter is normal or recovery mode). Using fuser /dev/stl5 was not much of a help

- my only hope is to find a way to recover /dev/stl5 using Odin.

(I tried already using debug, parameter clear, phone efs clear, pda format, but no result)