when I insert the sim
leave this message
FATAL ERROR
Data crashes. Please contact your service center
the phone cingular 3125 that the purchase was blocked and the sim cid not say who because I live here and nobody in bolivia unlock a cingular 3125 windows movile!
OMG it's you again. I already tried to explain you a couple of times that your "simlock data area" is corrupted. Ah well ...
Doesn't Solution Exist Then?
diego1x0 said:
Doesn't Solution Exist Then?
Click to expand...
Click to collapse
Try this:
Code:
"pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb"
Attach the file in this thread.
I have the same problem (Cingular 3100)
jockyw2001 said:
Try this:
Code:
"pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb"
Attach the file in this thread.
Click to expand...
Click to collapse
I'm having the same problem with my Cingular, can you help me please?
ASPcoder said:
I'm having the same problem with my Cingular, can you help me please?
Click to expand...
Click to collapse
Seems to me you didn't produce the file with this line:
pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb
Your filesize is 64 KByte, it should have been 128 Kbyte
jockyw2001 said:
Seems to me you didn't produce the file with this line:
pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb
Your filesize is 64 KByte, it should have been 128 Kbyte
Click to expand...
Click to collapse
sorry for the mistake, is attached better?
code error thc data crashes.please contact service provider
how to do you apply the zip file to solve the problem
Hi all,
I managed to successfully configure BT5, using the image, set up and managed to successfully use SSH and VNC (for ssh tunnel via adb).
But my need is a little different, I just need to open applications and export display over ssh (putty). Specifically Firefox you have installed Flash (FF's BT5 not have flash installed and when I execute the "dist upgrade" the FF stops working).
In summary:
I need to know if there is the possibility of running only Firefox's installed on my Webtop and export display over ssh.
What have a done:
I managed to solve the problem of xauth, copying what was already the "/ osh / usr / bin / xauth" to "/ usr/X11R6/bin/xauth."
FF running the command:
"export DISPLAY =: 0" after
"sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox"
I'm getting this:
"
root @ (unknown) :/ # export DISPLAY =: 0
root @ (unknown) :/ # sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Error: can not open display :: 0
root @ (unknown) :/ # uname-a
Linux localhost 2.6.35.7-g3798510 # 1 SMP PREEMPT Thu Oct 20 23:16:00 EDT 2011 armv7l unknown
"
I'm using a Razr GSM Droid
Android: 2.35
System Version: 651.73.240.xt910.Vivo.en.BR
Webtop: WT-2.0.0-82
Rooted and unblocked
Im good on network stuffs but just a newbie in linux.
Thanks in advance,
Storm
Did i post this question in wrong section?
stormclaws said:
Did i post this question in wrong section?
Click to expand...
Click to collapse
Will call someone that may help on this
See u
Sent from my XT910 using Tapatalk 2
I am a regulair Linux user but never used webtop.
The only reason I can get up with is that you try to run remote X as a non-authorised user, mostly after a sudo or su. So are you sure the autorisation (magic-cookie) is good?
Hope this points in the right direction.
That happens because you're using the wrong commands.
You're doing:
"export DISPLAY =: 0"
"sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox"
You have to enter:
export DISPLAY= :0
sudo -u adas dbus-launch
Thank you for answering me, but apparently not working.
---
[email protected](unknown):/# export DISPLAY=:0
[email protected](unknown):/# sudo -u adas dbus-launch
No protocol specified
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-xSUDt7Zo5x,guid=b3a4338d764e43e81d27d8b700007bc2
DBUS_SESSION_BUS_PID=7635
---
I could try something else?
Thanks in advance,
Storm
---------------------
kholk said:
That happens because you're using the wrong commands.
You're doing:
"export DISPLAY =: 0"
"sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox"
You have to enter:
export DISPLAY= :0
sudo -u adas dbus-launch
Click to expand...
Click to collapse
Guys, anyone coult gimme a hint?
stormclaws said:
Guys, anyone coult gimme a hint?
Click to expand...
Click to collapse
I can. Try asking kholk in his thread in the dev section. He did a webtop mod and probably have a solution.
Cheers
Sent from my XT910 using Tapatalk 2
Xperia Boot Menu v1.0
Disclaimer:
- Me (munjeni) is not responsible for anything related to the our project, you using our project on your own risk! If you no want to risk than don't play with Boot Menu! You can play with Boot Menu but on your own risk!
Feature:
- multiboot based on kexec
- posibility for defining: menu title, path to the kernel, path to the ramdisk, kernel cmdline
- posibility for defining max 10 menus
- autoreboot to the first kernel if menu is not moved (stop timer on menu move)
- graphic timer
Instructions:
- create folder "bootmenu", add settings.ini to these folder, modify settings.ini for your needs
- flash bootmenu using fastboot command (fastboot flash boot recovery.img)
- since internal sdcard is only supported by now, you can define only kernel and ramdisk from internal sdcard path! Make sure you define right path and make sure create folders in bootmenu on your internal sdcard
- make sure settings.ini is in internal sdcard in folder bootmenu!!!
- kexec can boot only kexec patched kernels, so your kernel need to have kexec patch!!! Complete kexec patch you can find on my git!
Simple settings.ini (example):
[rom-1]
menutitle=recovery touch white
kernel=/sdcard/bootmenu/examplerom/zImage
ramdisk=/sdcard/bootmenu/examplerom/initrd.gz
cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-2]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-3]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-4]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-5]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-6]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-7]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-8]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-9]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-10]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
Click to expand...
Click to collapse
Download:
- http://d-h.st/UXm
Kernel source code:
- https://github.com/munjeni/android_kernel_xperiago/tree/jb-dev
You're simply the best :beer: :beer: :beer:
Inviato dal mio Xperia U usando Tapatalk 4
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and my new CWM Touch Recovery v6.0.3.6 ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
00000000-05ffffff : System RAM
0005e000-008fa4c7 : Kernel text
008fc000-00f2e797 : Kernel data
06000000-06efffff : db8500-trace-area
08000000-09ffffff : System RAM
0e800000-1fdfffff : System RAM
1fe00000-1fefffff : kexec_hardboot
1ffe0000-1fffffff : ram_console
40010000-400107ff : lcpa
40010000-400107ff : dma40 I/O lcpa
Click to expand...
Click to collapse
So I am not sure about X-U
munjeni said:
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and recovery ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
So I am not sure about X-U
Click to expand...
Click to collapse
Xperia u have 512mb ram
Sent from my Xperia U using xda app-developers app
munjeni said:
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and recovery ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
So I am not sure about X-U
Click to expand...
Click to collapse
Here's the output..
And no XU has only 512 mb of ram
Boot menu download link ready, please let me know if booting!
First of all create bootmenu folder inside your internal sdcard, create settings.ini file in bootmenu folder:
Code:
[rom-1]
menutitle=recovery touch white
kernel=/sdcard/bootmenu/examplerom/zImage
ramdisk=/sdcard/bootmenu/examplerom/initrd.gz
cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
Since cmdline settings is from Xperia Go please edit these line and add cmdline for Xperia U !!!
Than create "examplerom" folder in your bootmenu folder, put initrd.gz and zImage from attachment to the example rom folder, reboot to the fastboot and flash bootmenu:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Reboot and let me know if working!
AD9295 said:
Here's the output..
And no XU has only 512 mb of ram
Click to expand...
Click to collapse
Thanks, so kexec will working I am sure Enjoy guys!
For example if you want to boot your android rom, simple extract ramdisk from boot image, create new folder in bootmenu folder for example my_stock_rom, add [rom-2 settings lines for your new rom, modify path to "my_stock_rom", use zImage from cwm.rar, use modules from cwm.rar and put into your android /system/lib/modules folder... new menu will apear in boot menu... etc Note: autoreboot is automatically set to the [rom-1] (first menu) so if you want to automatically boot "my_stock_rom" simple move them to the top of the settings.ini ... Enjoy!!!
munjeni said:
Boot menu download link ready, please let me know if booting!
First of all create bootmenu folder inside your internal sdcard, create settings.ini file in bootmenu folder:
Code:
[rom-1]
menutitle=recovery touch white
kernel=/sdcard/bootmenu/examplerom/zImage
ramdisk=/sdcard/bootmenu/examplerom/initrd.gz
cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
Since cmdline settings is from Xperia Go please edit these line and add cmdline for Xperia U !!!
Than create "examplerom" folder in your bootmenu folder, put initrd.gz and zImage from attachment to the example rom folder, reboot to the fastboot and flash bootmenu:
Reboot and let me know if working! If not working please give me output of the command "adb shell cat /proc/iomem"
Click to expand...
Click to collapse
I would like to help but I dont know hot add and modify settings.ini..
Edit: I learnt how to do that.. will post results when I get back from college.. Sorry but i have to attend today..
Another example:
Since I not sucesfully booted android from sdcard, we need to prepare ramdisk of the future sdcard rom boot, modify them to use partitions from sdcard instead of using partitions from emmc!!! Need help for them!!!
So example is:
kexec cwm which have modified partitions table (sdcard partitions) -> load them into bootmenu -> boot them -> since these cwm will load sdcard partitions we can install an rom.zip regulary to these partitions using these cwm (cwm will install android to these sdcard partition) -> rom.zip updater-script need allso modification because we need to edit for example all lines which contain for example /dev/block/mmcblk0p** and change for example to the /dev/block/loop**
Ramdisk cwm or rom need allso reparation -> /dev/block/mmcblk0p** need changes to the /dev/block/loop** since for sdcard boot we need to mount system,data,cache partitions to the /dev/loop devices.
ETC...BLABLA Thats all we need for multiboot!!!
AD9295 said:
I would like to help but I dont know hot add and modify settings.ini..
Edit: I learnt how to do that.. will post results when I get back from college.. Sorry but i have to attend today..
Click to expand...
Click to collapse
No problem mate, I am sure most experienced users will help and get them working, and post the results Good thing is we have boot menu and kexec working, so all other things will come soon, I am sure
Waiting your creations and modifications. Want to see message "sucesfully booted rom from sdcard" :laugh: First of all waiting confirmation about working Boot Menu v1.0 in Xperia U !
munjeni said:
No problem mate, I am sure most experienced users will help and get them working, and post the results Good thing is we have boot menu and kexec working, so all other things will come soon, I am sure
Waiting your creations and modifications. Want to see message "sucesfully booted rom from sdcard" :laugh: First of all waiting confirmation about working Boot Menu v1.0 in Xperia U !
Click to expand...
Click to collapse
How can I modify sdcard since its emmc,I dont understand.
How to create partitions on it for system,data,cache or this supports kernels only?
XperianPro said:
How can I modify sdcard since its emmc,I dont understand.
How to create partitions on it?
Click to expand...
Click to collapse
You no need to modify emmc! Simple create file based ext4 partition and mount them on boot time to the loop device For get these to work you need to modify ramdisk, fstab...etc of the rom
munjeni said:
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and my new CWM Touch Recovery v6.0.3.6 ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
So I am not sure about X-U
Click to expand...
Click to collapse
i know this is too noob but does xperia go have 1 gb ram?isnt it 512m?
can i flash the attached recovery.img in an unlocked xperia u running ics??
bibhu059 said:
can i flash the attached recovery.img in an unlocked xperia u running ics??
Click to expand...
Click to collapse
No, only JB !
chessmanyaki said:
i know this is too noob but does xperia go have 1 gb ram?isnt it 512m?
Click to expand...
Click to collapse
have 512 !
Guys, found a bug in Boot Menu! For example shifting trought menu failed to select right thing, for examle it select an submenu but boot another rom ...I will fix them in next version! You ca duplicate menus and experiment by now
munjeni said:
Guys, found a bug in Boot Menu! For example shifting trought menu failed to select right thing, for examle it select an submenu but boot another rom ...I will fix them in next version! You ca duplicate menus and experiment by now
Click to expand...
Click to collapse
I've got to say I'm really impressed anytimes you release/post something, many thanks for your progress
I guess that, at first look, it is not working for locked bootloader, but it seems your recovery handles the boot menu and kexec thing : would it be possible to port your recovery to our locked bootloader "a la" atis' patch ? I guess we won't be able to straight boot your recovery because of its' kernel, but would it be portable to ICS kernel&codes to, lets say => load your recovery by loading ramdisk like atis', then kexec to an unsigned kernel ?
edit: partially answered myself: we need to enable kexec support therefore I guess "official kernels" don't =/
Sympnotic said:
I've got to say I'm really impressed anytimes you release/post something, many thanks for your progress
I guess that, at first look, it is not working for locked bootloader, but it seems your recovery handles the boot menu and kexec thing : would it be possible to port your recovery to our locked bootloader "a la" atis' patch ? I guess we won't be able to straight boot your recovery because of its' kernel, but would it be portable to ICS kernel&codes to, lets say => load your recovery by loading ramdisk like atis', then kexec to an unsigned kernel ?
edit: partially answered myself: we need to enable kexec support therefore I guess "official kernels" don't =/
Click to expand...
Click to collapse
Stock kernel doesn't support it. He has said it earlier himself
Yup, I read too fast, was excited about this post and I've used to read "kexec could be our way out of locked bootloader" (@Xperianpro, some of his posts)
Anyone knows if an official kernel had kexec support in the past ? Even if it's GB *not really hoping*