Develop Bugs

How do you verify NAND is unlocked/How to verify you are fully rooted

I have searched the Evo 4g forums, and I am finding it difficult to verify NAND is unlocked/if I am fully rooted. I can confirm that I have partial root. I flashed the latest version of FRESH 1.0.1 with RADIO: 2.05.00.06.10 and WiMax Radio 25641. I also flashed netarchy-toastmod 'fix' for Epson AND Nova - Version 3.6.4 to increase my FPS. Everything seems to work ok.
I did find one post that stated I can run "adb remount rw" in a terminal emulator to check if I am unlocked. The emulator has su access, but I get an access denied and I can not create a folder in the system directory.
Is there an easy method for me to check if NAND is unlocked/if I am fully rooted? Thanks for the help.
Kurt

Unlocked NAND gives access to the system partition as far as I understand. From the shell, run.
Code:
mount
Find what device is your system partition. Should be something like /dev/block/mtdblock4. Then try this.
Code:
mount -o rw,remount -t yaffs2 /dev/blco/mtdblock4 /system
That will remount your system partition into read/write mode. If that works your NAND is unlocked. You can remount your system partition back into read only mode by changing the rw to ro and running the command again.

Thanks
It took me a few minutes to figure this out, but it looks like I am fully rooted.
I opened terminal emulator on my phone then typed the following:
su
<enter>
mount
<enter>
I big list of things appeared, and I saw what you were referencing. The line reads the following:
/dev/block/mtdblock4 /system yaffs2 ro 0 0
If I understand correctly the system partition is in "ro" or read only. I then typed what you wrote. I think you had a typo because it errored out. I typed the following:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
<enter>
I then typed the following:
mount
<enter>
The line in the list now reads the following:
/dev/block/mtdblock4 /system yaffs2 rw 0 0
The "rw" means that I have read/write access to the system partition. I then typed the following to change it back to "read only".
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
<enter>
mount
<enter>
The line now reads the following:
/dev/block/mtdblock4 /system yaffs2 ro 0 0
I am now back in read only mode, and this verified that I have full root access. If my reasoning is wrong, please let me know, and I will edit this post.
Hopefully, this will help others determine whether or not they are fully rooted.
Thanks for your help.
Kurt

Everything in you post looks correct. Using the 'adb remount' command acomplishes the same thing but your rom has to support it and most don't because they are based off the stock sprint rom.
So just to reiterate, just because 'adb remount' doesn't work on your rom doesn't necissarily mean you don't have nand unlocked. There are also some tools like 'spare parts' you can use to remount your system partition from within the gui.

The easiest way is to determine which HBOOT version you have installed. Full root means you hane NAND unlocked which allows you to do anything.
79.00 = locked
76.20 = unlocked
Reboot and upon startup hold down the volume down and power buttons at the same time until the white screen appears. HBOOT version will be listed at the top in green letters I believe

[Q] Correct path in Terminal Emulator?

I have spent hours trying to find an answer to what I thought was a simple question, but I just can't seem to find it...
I wanted to familiarize myself more with Terminal Emulator, so I used it to delete a system app that needed to go.
I used these commands:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
# rm /system/app/xxx.apk
It appears to have worked perfectly after a reboot, but my question is: what is the correct code to mount your system partition in TE? I have seen several variations of the line I used. Often they vary at 'mtdblk3.' I have seen it 'mtdblock5,' for example. Is there a particular line I should use for my specific device? Is it dependent on what I am specifically trying to do?
Any information is greatly appreciated; even/especially a link toward my answer. Thank you very much.

I've always used 'mount -o remount,rw /dev/block/mmcblk0p25 /system'
as far as 'correct' code I don't think there is as such. But I think different devices would have different partitions and mount points for system.
-Nipqer

I think it will depend on where your system is mounted, although I don't know why that would vary for the G2. It might be different for the DZ and certainly for other devices.
You can type "mount" in the terminal to see where everything is mounted.

Ditamae said:
I have spent hours trying to find an answer to what I thought was a simple question, but I just can't seem to find it...
I wanted to familiarize myself more with Terminal Emulator, so I used it to delete a system app that needed to go.
I used the code:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
# rm /system/app/xxx.apk
It appears to have worked perfectly after a reboot, but my question is: what is the correct code to mount your system partition in TE? I have seen several variations of the line I used. Often they vary at 'mtdblk3.' I have seen it 'mtdblock5,' for example. Is there a particular line I should use for my specific device? Is it dependent on what I am specifically trying to do?
Any information is greatly appreciated; even/especially a link toward my answer. Thank you very much.
Click to expand...
Click to collapse
i use this command:
# mount -w -o remount /dev/block/mmcblk0p25 /system

Thanks for the replies... I see now, that the path I should have used is: /dev/block/mmcblk0p25 /system. And that "code" was the wrong word. I was asking about commands & paths not code. Sorry - still learning.
edit: If anyone knows of a good and thorough resource of Terminal commands, I'd love it if you'd share... I've found bits and pieces of info, but something more comprehensive would be great. Thanks again.

Wow you guys are going about it using the long hand method. If you're just deleting a system app, to mount the /system as rw just enter:
Code:
$su
#mount -o remount,rw /system
#rm -f /system/app/xxxx.apk
The -f command isn't really needed but I use it to make sure the job gets done. Not sure if the pm uninstall command is used anymore. I'll have to look into that. I know some phones required you to mount yaffs and mmcblockXX but for just deleting an app I don't believe it's required. Never had an issue not typing that.

Here's the correct way to delete the app:
mount -o rw,remount /system
rm /path/to/app
reboot
Click to expand...
Click to collapse
Or you could use remount,rw. It's the same command. I threw reboot in there to reload the app list in your launcher correctly.

[Acer A200] GUIDE FOR ICS OTA ROOT

Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or getting flammed because you re-rooted your phone instead of your tablet because you forgot to unplug your phone from the computer while the tablet was plugged in...
Please do some research if you have any concerns about rooting your device! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Ok, this was a pain in the arse!
I hope I can remember the steps I took in order to get this done.
By the way, I'm using windows
adb push mempodroid /data/local
adb push su /data/local
adb shell
$ chmod 777 /data/local/mempodroid
Click to expand...
Click to collapse
Then I went to here as directed,
http://rkeene.org/projects/info/wiki/210
but didn't follow the steps as they were shown because I got stuck many times and had to start over.
So here are my steps.
1.
$ /data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
which then should turn the $ into a #
2.
# mkdir /data/x-root /data/x-root/bin
Click to expand...
Click to collapse
3. Download this,
http://www.rkeene.org/projects/info/resources/diatribes/root-toshiba-thrive/busybox
and then move the file to where you have mempodroid and su so you can adb push them easier
4.
adb push busybox /data/x-root/bin/busybox
adb push su /data/x-root/bin/su
adb shell
Click to expand...
Click to collapse
5. This is where it got tricky. If you don't pay close attention, you will most likely do what I did and put files where they aren't supposed to go. So please, PAY ATTENTION!
If you still have the # in the shell, move forward. Otherwise,
/data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
and then move forward once # is confirmed.
# cd /data/x-root/bin
# chmod 755 busybox
# ./busybox bash
Click to expand...
Click to collapse
Now, there is no doubting it, you will get the "bash: precmd: not found" error.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
# PATH="${PATH}:/data/x-root/bin"; export PATH
Click to expand...
Click to collapse
6. AGAIN, PAY CLOSE ATTENTION HERE!!
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
Click to expand...
Click to collapse
7. This is where I ran into another problem, so pay attention.
# cd /
# mkdir /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
You will see nothing as the steps describe. This is because we skipped a step. Why? Because mount -o ro -t ext4 /dev/loop0 /dev/tmpdir for some strange reason wouldn't unmount so I could mount the next step. So instead, we move on and then check again.
Here is the removed step
# mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
# umount /dev/tmpdir
Click to expand...
Click to collapse
You can try this but I advise not to or you could very well run into the same issue I had where you can't unmount in order to move on with the root process
# mount -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
And now you will see /system mounted.
8.
# cp /data/x-root/bin/su /dev/tmpdir/bin/
# chmod 4555 /dev/tmpdir/bin/su
# umount /dev/tmpdir
# losetup -d /dev/loop0
# sync
# reboot
Click to expand...
Click to collapse
9. Now once your A200 reboot and displays the home screen, we will confirm.
adb shell
[email protected]:/ $ su
Click to expand...
Click to collapse
If the $ doesn't turn into a #, you did something wrong...
Thank you hexmare, for opening this thread and giving the guidance.
Thank you d10369319, for "/data/local/mempodroid 0xd9f0 0xaf47 sh", I would have never figured this out.
Thank you RKeene, for writing out the guide to Root the Toshiba Thrive
And Thank you Saurik along with zx2c4, for mempodroid

Ok, for some reason, /system still refuses to mount with "mount -o remount,rw /system"
So my solution is this,
$ su
# cd /data/x-root/bin
# chmod 755 busybox
# unset PS1 PROMPT_COMMAND
./busybox bash
# PATH="${PATH}:/data/x-root/bin"; export PATH
# cd /
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
# mount -t ext4 /dev/loop0 /dev/tmpdir
Click to expand...
Click to collapse
You will have to go to /dev/tmpdir in order to do anything with /system but it is the secret passage way for now...

Why is there still no A200 forum?

agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
Maybe there will be now that we have made some progress...

agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
+1 A200 Forum

Enjoy your ICS A200 owners. I just saw a tweet from AcerAmerica that ICS is being rolling out to A200

Hello to all,
My A200 has been upgraded today 'OTA' , to ICS (V: 4.0.3) , so Europe/France seems to be available, now.
Applying this procedure, all goes fine, and my A200 is rooted.
I'm very happy
A lot of thanks to people having discovered this procedure, particularly mempodroid which set all of this possible.
Greetings

the last time when you do losetup -d /dev/loop0
returns No such device or address?????
ive been through it twice now
*EDIT* Nevermind I figured out my problem...I was typing in reboot instead of using the hardware power button. Got root now, sweet!

I am sooo glad we can now root the a200, but I cannot get mine to work. I have went through the steps 3+ times and had issues each time. I thought I had it twice and then tried Titanium backup root and it said it didn't work.
I can't see at all where I've gone wrong..

That's very strange because Titanium Backup works just fine for me...

rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though

ran into a mounting issue
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance

what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
D:\android-sdk-windows\platform-tools>adb push mempodroid /data/local
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Ghorn

ghorn222 said:
what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
Ghorn
Click to expand...
Click to collapse
Go download the drivers from Acer's website for this device

johnsonj067 said:
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance
Click to expand...
Click to collapse
You have to follow the guide to the T or you will run into numerous problems and stop signs. Try again

daimerion said:
rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though
Click to expand...
Click to collapse
That's because we don't have a custom kernel yet. Just wait a little while.

Unfortunate the root isn't 100% cool my boot loader Is unlocked though.
Droid 3 bldr is locked down however changing numbers in rom toolbox works w/o custom kernals or modules.
http://www.acertabletforum.com/foru...iscussions/3649-how-unlock-boot-loader-4.html
^this Does work

su file?
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.

shwilson24 said:
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.
Click to expand...
Click to collapse
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on

daimerion said:
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on
Click to expand...
Click to collapse
I tried using the power button. Same result. Where did you get the su file from?

[ROOT ICS] The hard way && Digging for roots

For anyone that doesn't want to root the hard way crossix has come up with a double click root for Windows forum.xda-developers.com/showpost.php?p=23052186&postcount=105
Update 2/26/12
/system can now be mounted writable see the bottom of this post.
So the old Honeycomb exploit has now been patched in ICS. But there was an exploit found in the newer ICS kernels. Written by saurik,: called mempodroid
There is an offset needed as an argument to the binary, for the a100 we'll use what has worked for the a200 as noted in sauriks github linked above.
The issue with this is mounting /system as writable. I'm not sure if it's something in ICS, but it appears to be write protected. As noted here and here we will loop mount the system partition.
The tools needed are:
1. mempodroid under Usage Instructions, download pre-compiled
2. busybox 1.20 snapshot 3-10-12
3. su the latest from androidsu.com, extract from system/bin
4. mount.txt script
After downloading and extracting place them all in a folder called tools.
This must be done with adb. Issue the following from cmd or a terminal:
Code:
$ adb shell mkdir /data/local/tools
$ adb push tools /data/local/tools ; adb shell
$ cd /data/local ; chmod 755 tools/*
$ cd tools ; ./mempodroid 0xd9f0 0xaf47 sh
If all went well you should be at a hash # prompt. This is temp root.
mount /system rw the new way:
Code:
# PATH=$PWD:$PATH
# sh mount.txt -o remount,rw /system
Copy su and busybox to /system
Code:
# ./busybox cp busybox /system/xbin; ./busybox cp su /system/xbin/
# chmod 6755 /system/xbin/su
Install busybox
Code:
# cd /system/xbin
# for i in $(busybox --list); do ln -s busybox $i; done; sync
Copy the mount script
If busybox is updated this step must be run again
Code:
# cp /data/local/tools/mount.txt /system/bin/mount
# cp /data/local/tools/mount.txt /system/xbin/mount
Done your a100 should be rooted
the old way:
Now lets loop mount /system
Code:
[b]This is no longer needed[/b]
# ./busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0
Code:
# ./busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
# mkdir loop ; mount -t ext4 /dev/block/loop7 loop
Copy su and busybox to the new mount point.
Code:
# ./busybox cp su loop/xbin/ ; ./busybox cp busybox loop/xbin/
# chmod 6755 loop/xbin/su ; sync
If it worked your a100 is fully rooted. Make sure to install SuperUser from the Market.
Either get busybox installer from the market, and install it to /data/local/tools/loop/xbin
Or:
Code:
# cd loop/xbin
# for i in $(busybox --list); do ln -s busybox $i; done; sync
The mount point won't survive a reboot so in order to write to /system again run:
Code:
# busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
# mount -t ext4 /dev/block/loop7 /data/local/tools/loop
[update 2/26/12]
To mount /system as writable do the following from adb. We'll just make a directory called /data/loop for easy access.
Code:
$ adb shell
$ su
# stop
[b]your screen will go black[/b]
# mkdir /data/loop
[b]skip this if the loop is already set up
# busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3[/b]
# mount -t ext4 /dev/block/loop7 /data/loop
# mount -o bind /data/loop /system
# start
You can write to /system with any app but /system can't be remounted ro then back to rw.
This can be added to /etc/install-recovery.sh to make it permanent
Code:
busybox losetup /dev/block/loop7 /dev/block/mmcblk0p3
mount /dev/block/loop7 /data/loop
mount -o bind /data/loop /system
Thanks to crossix as the first to get temp root, and Icewyng for pointing out the exploit and helping with the magic number.

Ill be testing this when I get home, if it works Ill attempt to write a 1 command script to do it.
Sent from my MB860 using XDA App

OK...
Testing this out and found there were a couple of bugs.
You didn't have a "loop" folder created so I made one in the "tools" folder.
and, when mounting, you need to specify -t ext4.
Here are the revised commands for # mount /dev/block/loop7 loop
mkdir loop;mount -t ext4 /dev/block/loop7 /data/local/tools/loop
I noticed that the files /data/local/tools/loop/xbin/su and /data/local/tools/loop/xbin/busybox don't exist on /system/xbin until after a restart.
Finally, the busybox we are using to install doesn't seem to make all of the links to all of the nice commands we are used to, so things like grep, cp, etc... they won't work. I'm trying to figure out how to re-run the GUI busybox installer and point it to the loop folder, but haven't had much success.

danifunker said:
OK...
Testing this out and found there were a couple of bugs.
You didn't have a "loop" folder created so I made one in the "tools" folder.
and, when mounting, you need to specify -t ext4.
Here are the revised commands for # mount /dev/block/loop7 loop
mkdir loop;mount -t ext4 /dev/block/loop7 /data/local/tools/loop
I noticed that the files /data/local/tools/loop/xbin/su and /data/local/tools/loop/xbin/busybox don't exist on /system/xbin until after a restart.
Finally, the busybox we are using to install doesn't seem to make all of the links to all of the nice commands we are used to, so things like grep, cp, etc... they won't work. I'm trying to figure out how to re-run the GUI busybox installer and point it to the loop folder, but haven't had much success.
Click to expand...
Click to collapse
You beat me to the punch... was about to point it out.
Not sure what version of busybox this is but I will try with 1.19.2 and see how it goes.
Edit: Got root! It works great... for Busybox, use Busybox Installer to be able to get the latest version (1.19.4) I confirm that system is R/O for now.

danifunker said:
OK...
Testing this out and found there were a couple of bugs.
You didn't have a "loop" folder created so I made one in the "tools" folder.
and, when mounting, you need to specify -t ext4.
Here are the revised commands for # mount /dev/block/loop7 loop
mkdir loop;mount -t ext4 /dev/block/loop7 /data/local/tools/loop
I noticed that the files /data/local/tools/loop/xbin/su and /data/local/tools/loop/xbin/busybox don't exist on /system/xbin until after a restart.
Finally, the busybox we are using to install doesn't seem to make all of the links to all of the nice commands we are used to, so things like grep, cp, etc... they won't work. I'm trying to figure out how to re-run the GUI busybox installer and point it to the loop folder, but haven't had much success.
Click to expand...
Click to collapse
I did have some typos, think it's right now. That is an old busybox, it was just a quick find and it includes losetup but it's not one to use full time. Maybe sync is needed at the end so files are written properly. I didn't have to use -t ext4 with HC, but Ill add it to the OP
[edit] you have to use "busybox cp or busybox grep" I didn't include a way to add all the symlinks. Wow I have typos everywhere it's the end of the day for me, working nights.

Ok ... Got root!
Titanium works, Busybox Installer works, Superuser works, Root Explorer works...
Only thing is that System is R/O but we will work on it.

Waiting for a R/W system...and then, no one will stop my update

I can't get it to root :-(
It say not found
Sent from my A100 using xda premium

jondi23 said:
I can't get it to root :-(
It say not found
Sent from my A100 using xda premium
Click to expand...
Click to collapse
At what point, need some more details.

The tools folder gets pushed (the 3 files are copied) but then it says there is no such folder.
edit: never mind - i created the folder manually and pushed the files into the folder
edit2: rooted - thakns guys

Brilliat work, will try this later (need to get the sdk all set up again, I've been distro swapping). Got a pool match tonight too, so will try as soon as I can, will give whatever feedback I can later.

myprecious27 said:
The tools folder gets pushed (the 3 files are copied) but then it says there is no such folder.
edit: never mind - i created the folder manually and pushed the files into the folder
Click to expand...
Click to collapse
I forgot adb can't push a whole directory, it instead only copies the files within the directory.

wait how is it rooted if it's r/o I thought point of root was to make the file system r/w... er is root just allowing you to view all directories? Sorry for a noobish question, but you gotta start somewhere right?

rando152 said:
wait how is it rooted if it's r/o I thought point of root was to make the file system r/w... er is root just allowing you to view all directories? Sorry for a noobish question, but you gotta start somewhere right?
Click to expand...
Click to collapse
Well I think if we have su working we will be able to mount /system rw in some way if not directly. I cant imagine not being able to.
In any case though being able to write to /data as root is very useful. Example: Hulu flash fix.

You can't view /data if you're not root. That's one thig. Also, other functions may require root, like advanced networking things, etc.
I agree, not being able to write to /system is a major inconvenience, but most of the root programs will still work, as long as you're not writing to /system.

Since this is a temp root, does it mean that I will have to reroot every time I reboot? Will apps like Adfree work on this?

better yet is there a way we can do this solely on the tab? im away for work for another 4 weeks and only have my cell and a100 with me :-(
Sent from my SGH-I897 using xda premium

I get
Code:
255|[email protected]:/data/local/tools # mount -t ext4 /dev/block/loop7 /data/local
/tools/loop
lock/loop7 /data/local/tools/loop <
mount: Invalid argument

simoneser said:
I get
Code:
255|[email protected]:/data/local/tools # mount -t ext4 /dev/block/loop7 /data/local
/tools/loop
lock/loop7 /data/local/tools/loop <
mount: Invalid argument
Click to expand...
Click to collapse
I noticed the same thing happen after you root it and restart... not sure what to do next. Are you at temp loop?

simoneser said:
I get
Code:
255|[email protected]:/data/local/tools # mount -t ext4 /dev/block/loop7 /data/local
/tools/loop
lock/loop7 /data/local/tools/loop <
mount: Invalid argument
Click to expand...
Click to collapse
danifunker said:
I noticed the same thing happen after you root it and restart... not sure what to do next. Are you at temp loop?
Click to expand...
Click to collapse
try:
Code:
# busybox losetup -d /dev/block/loop7
# busybox losetup -o $((512 * 51200)) /dev/block/loop7 /dev/block/mmcblk0
# mount -t ext4 /dev/block/loop7 /data/local/tools/loop
The first line may produce
losetup: /dev/block/loop7: No such device or address
If it's not looped
After you are rooted the above can be run without adb from a terminal as su.
The mount point can be anywhere ex. /sdcard/loop instead of /data/local/tools/loop

[Q]

Hi
Today I tried to remove the simlock from my new Samsung Galaxy Gio, but something went wrong.
Unfortunately I can't remember completely what I did, but I know that I followed a tutorial. I think I used the file 'update.zip' to root the phone and then (I'm sure about this I used ADB to get the unlock code:
C:\ADB>adb shell
$ su
su
# cd /
cd /
# mkdir /efs
mkdir /efs
# mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
#
Type: cat /efs/mits/perso.txt
I remember something about an error with stl and efs..
The problem is now that the phone boots and it can be used, BUT I can't fill in a unlock code. Besides that, when I try to get the IMEI number (*#06#) I get an empty string (just "IMEI: ____") and when I vies the phone stats, I see "Phone: unknown" (the rest is normal).
Sometimes the phone just shuts down..
Can somebody help me out by telling me how I can fix this?

Please remove Topic.. double post..

send a pm to the op and ask of he will close the thread