Database Info

Newly launched Micromax w900,Windows Mobile 6.1 looking for Android OS Flash Help.

Hi all, i m new here,
I have been reading this forum and couldnt find thread on how to flash/install Android OS on Windows Mobile 6.1 Professional for Micromax w900.
I have newly purchased a phone "MICROMAX W900" which comes with Windows Mobile 6.1 Professional OS and i m looking to install Android/Maemo OS on it.
So its my request to u all, please point me to it.
Features:
2.0 mega pixel CMOS camera
Windows Mobile 6.1
Pocket MSN
Windows Media Player
Bluetooth
ActiveSync
T-Flash card compatible (Micro SD upto 16 gb)
Touch screen with handwriting recognition
3.2-inch 65K color display
E-mail
Wi-Fi
GPS with integrated MAPS
FM Radio
Here is the Technical specification of phone.
Windows Mobile 6.1 Professional
CE OS 5.2.21041(BUILD 21041.1.6.0)
Processor: Hisilicon-K3
Memory: 81 MB
Expansion slot: In use
Device Info:
ROM VERSION : 01.001.18 IND
ROM DATE: 1/19/2010
RADIO VERSION: 1.07.9324
PROTOCOL VERSION: DV3.0
HARDWARE
CPU: Hisilicon-K3
speed: 460 Mhz
Ram size: 128 MB
Flash size: 256 MB
Data Bus: 32 bit
Storage size: 157.20 MB
Display Resolution: 240x400
Colors: 262144
Identify
Model No: NEXPERIA SY.SOL 5209
Platform: Pocket PC
Thanks for ur time,
Anyways i m happy to provide any more details of the phone, if needed.
Thanks .

just found
hi,
i just found out this.
press & hold
1) volume down + camera key + power key = Factory reset/clean boot
2) Volume up + volume down + power key = Some flashing utility
it gives me this
Checking valid image file
Step 3 error while updating
Card operate : Read retry timeout.
what to do next ?
c'mon guys please help me.
i m really tired of windows mobile os,

Latest update,
I guess i m very closer to find bootloader mode of the phone.
whenever i remove battery and plug USB, windows logo comes and goes and my XP says device not recognized and nothing happens at phone, no 3 stripes of bootloader.

Hello Dear
I am new here. I want to modify my current ROM on Micromax W900. I have surfed and got some info on Updating the ROM. But it says 'Download the ROM for your Device'. I just want to know that from where should I download the ROM for this device.
Thanks in advance...
Regards,
~alliwant

alliwant said:
Hello Dear
I am new here. I want to modify my current ROM on Micromax W900. I have surfed and got some info on Updating the ROM. But it says 'Download the ROM for your Device'. I just want to know that from where should I download the ROM for this device.
Thanks in advance...
Regards,
~alliwant
Click to expand...
Click to collapse
i m still trying to figure that out, but no luck.
i also contacted micromax for giving me technical datasheets of w900, but they said its matter of company protocol issue, IDK what does it means.
anyways, keep trying R n D

TCPMP crash report
i installed tcpmp and while starting it, it gave me crash.txt,
i think here is some useful info. of phone.
Access violation(c0000005) at 784549ec 784549ec)
Read from 784549ec
cpu dump:
R0 = 65bd6f9f
R1 = 00000000
R2 = 65bd6f9f
R3 = ffffcbac
R4 = 01a902d0
R5 = 00012000
R6 = 00012010
R7 = 00000003
R8 = 2595fed8
R9 = 2595fed8
R10 = 784026a8 (common:000016a8)
R11 = 2595fd04
R12 = 65bd6f9f
Sp = 2595fcd8
Lr = 78402798 (common:00001798)
Pc = 784549ec
Psr = 60000010
stack dump:
2595fcd8 783d3f20
2595fcdc 0001318c
2595fce0 2595fed8
2595fce4 86007150
2595fce8 c56d8fd2
2595fcec 783d3f48
2595fcf0 00000000
2595fcf4 66c2252e
2595fcf8 ffffc894
2595fcfc 2595fd04
2595fd00 00011108
2595fd04 00000000
2595fd08 00000000
2595fd0c 87f7b888
2595fd10 00000000
2595fd14 00011424
2595fd18 01ffcc94
2595fd1c 01ffc9e0
2595fd20 2595fed8
2595fd24 66c2252e
2595fd28 ffffc894
2595fd2c 81b05fb8
2595fd30 00000047
2595fd34 66c2252e
2595fd38 00000000
2595fd3c 2595fed8
2595fd40 00000005
2595fd44 87f7b888
2595fd48 00000000
2595fd4c 00011424
2595fd50 01ffcc94
2595fd54 01ffc9e0
2595fd58 2595fed8
2595fd5c 66c2252e
2595fd60 ffffc894
2595fd64 03f66a64
2595fd68 2595fe44
2595fd6c 03f67274
2595fd70 00011424
2595fd74 80000010
2595fd78 2595fdd4
2595fd7c 7c08f544
2595fd80 2595fdac
2595fd84 7c08f544
2595fd88 0000c31b
2595fd8c 03f6bbcc
2595fd90 ffffc894
2595fd94 00000000
2595fd98 0db6af68
2595fd9c 0da90000
2595fda0 0db40000
2595fda4 00000014
2595fda8 86e67de0
2595fdac 00000000
2595fdb0 00000000
2595fdb4 86042940
2595fdb8 81e06d10
2595fdbc 860b6680
2595fdc0 86e67de0
2595fdc4 00000000
2595fdc8 f000fe38
2595fdcc 2595fe10
2595fdd0 81b08744
2595fdd4 00000000
2595fdd8 00004000
2595fddc 00000010
2595fde0 ffffcb48
2595fde4 ffffc894
2595fde8 00000001
2595fdec 81b08c20
2595fdf0 00004000
2595fdf4 00000010
2595fdf8 ffffcb48
2595fdfc 65bd6f9e
2595fe00 66c2252e
2595fe04 00000001
2595fe08 81b05828
2595fe0c 03f66a64
2595fe10 00000000
2595fe14 00000010
2595fe18 66c2252e
2595fe1c 00000000
2595fe20 2595fed8
2595fe24 00000005
2595fe28 01ffc9e0
2595fe2c 00011450
2595fe30 87f7b888
2595fe34 00000000
2595fe38 00011424
2595fe3c 01ffcc94
2595fe40 03f67274
2595fe44 00010000
2595fe48 00000000
2595fe4c 00000000
2595fe50 00000000
2595fe54 00000000
2595fe58 00000001
2595fe5c 00000000
2595fe60 00000000
2595fe64 00000000
2595fe68 00000000
2595fe6c 00000000
2595fe70 00000000
2595fe74 00000000
2595fe78 00000000
2595fe7c 00000000
2595fe80 00000000
2595fe84 00000000
2595fe88 00000000
2595fe8c 00000000
2595fe90 f000fe3c
2595fe94 c203fe7c
2595fe98 81b2819c
2595fe9c 81b2820c
2595fea0 00000000
2595fea4 80000004
2595fea8 00000001
2595feac 00000004
2595feb0 87f7b888
2595feb4 00000000
2595feb8 00000000
2595febc 00010000
2595fec0 006c0070
2595fec4 00790061
2595fec8 00720065
2595fecc 0065002e
2595fed0 00650078
2595fed4 00000000
2595fed8 00000000
2595fedc 00000000
2595fee0 00000000
2595fee4 24000000
2595fee8 00000002
2595feec 00000000
2595fef0 00020000
2595fef4 00000000
2595fef8 2595d000
2595fefc 25940000
2595ff00 7c08f580
2595ff04 2595fe50
2595ff08 00000000
2595ff0c 00000000
2595ff10 00000000
2595ff14 01a919e0
2595ff18 00000000
2595ff1c 00000000
2595ff20 00000000
2595ff24 00000000
2595ff28 00000000
2595ff2c 00000000
2595ff30 00000000
2595ff34 00000000
2595ff38 00000000
2595ff3c 00000000
2595ff40 00000000
2595ff44 00000000
2595ff48 00000000
2595ff4c 00000000
2595ff50 00000000
2595ff54 00000000
2595ff58 00000000
2595ff5c 00000000
2595ff60 00000000
2595ff64 00000000
2595ff68 00000000
2595ff6c 00000000
2595ff70 00000000
2595ff74 00000000
2595ff78 00000000
2595ff7c 00000000
2595ff80 00000000
2595ff84 00000000
2595ff88 00000000
2595ff8c 00000000
2595ff90 00000000
2595ff94 00000000
2595ff98 00000000
2595ff9c 00000000
2595ffa0 00000000
2595ffa4 00000000
2595ffa8 00000000
2595ffac 00000000
2595ffb0 00000000
2595ffb4 00000000
2595ffb8 00000000
2595ffbc 00000000
2595ffc0 00000000
2595ffc4 00000000
2595ffc8 00000000
2595ffcc 00000000
2595ffd0 00000000
2595ffd4 00000000
2595ffd8 00000000
2595ffdc 00000000
2595ffe0 00000000
2595ffe4 00000000
2595ffe8 00000000
2595ffec 00000000
2595fff0 00000000
2595fff4 00000000
2595fff8 00000000
2595fffc 00000000
25960000 ????????
25960004 ????????
25960008 ????????
2596000c ????????
25960010 ????????
25960014 ????????
25960018 ????????
2596001c ????????
25960020 ????????
25960024 ????????
25960028 ????????
2596002c ????????
25960030 ????????
25960034 ????????
25960038 ????????
2596003c ????????
25960040 ????????
25960044 ????????
25960048 ????????
2596004c ????????
25960050 ????????
25960054 ????????
25960058 ????????
2596005c ????????
25960060 ????????
25960064 ????????
25960068 ????????
2596006c ????????
25960070 ????????
25960074 ????????
25960078 ????????
2596007c ????????
25960080 ????????
25960084 ????????
25960088 ????????
2596008c ????????
25960090 ????????
25960094 ????????
25960098 ????????
2596009c ????????
259600a0 ????????
259600a4 ????????
259600a8 ????????
259600ac ????????
259600b0 ????????
259600b4 ????????
259600b8 ????????
259600bc ????????
259600c0 ????????
259600c4 ????????
259600c8 ????????
259600cc ????????
259600d0 ????????
259600d4 ????????
common 78401000-7844c000 obj:0 class:30
General (0x01a917a0)
Language(16)=1600081477
Platform(23)=PocketPC
Ver(25)=502
OS Version(27)=5.02
OEM Info(24)=Hisilicon
TypeNo(26)=1
Model(18)=0
Caps(19)=0x00008001
Processor(17)=ARM 926E
Clock speed(34)=400
ICache(20)=16384
DCache(21)=16384
(37)=10
(38)=0
Advanced (0x01a91ac0)
No backlight keepalive for video(32)=No
Home Screen time out with music playback(45)=No
Old style toolbars(31)=No
No wireless MMX usage(40)=No
Slow video memory(37)=No
Less rotation tearing (slower)(41)=No
Prefer lookup tables over arithmetic(38)=Yes
D-Pad follow screen orientation(56)=Yes
Prefer less buffering over smooth video(54)=No
Use system volume(52)=No
Benchmark from current position(48)=No
Override AVI frame rate based on audio(53)=No
Widcomm BT Audio button support(58)=No
Disable AVC deblocking filter(65)=No
Manual A/V offset +/-(44)=0.00 ms
Soft-drop tolerance(42)=54.99 ms
Hard-drop tolerance(43)=699.95 ms
(59)=No
System Timer (0x01a91e10)
Time(96)=0
Speed(98)=100.00%
Play(99)=No
Wave Output (0x01a91fc0)
Input(32):IN=empty packet format
Input(32):IN=NULL
Output(33):OUT=empty packet format
Total(34)=0
Dropped(35)=0
Volume(81)=100
Mute(82)=No
(89)=0
Quality(83)=2
(90)=No
(91)= (0x01a91fd0)
NULA AOUT p:1 r:1 c: e: p: m:common
OVLA VOUT p:1 r:1 c: e: p: m:common
RAWA FMTB p:1 r:1 c: e: p: m:common
FMTB FMT_ p:1 r:1 c: e: p: m:common
CODC FLOW p:1 r:1 c: e: p: m:common
CCID FLOW p:1 r:1 c: e: p: m:common
NODE p:0 r:1 c: e: p: m:common
FILE STRM p:1 r:1 c:file e: p: m:common
WAVE AOUT p:1 r:1 c: e: p: m:common
RAWI FMTB p:1 r:1 c: e: p: m:common
FMTL FMTM p:1 r:1 c: e: p: m:common
STRM NODE p:1 r:1 c: e: p: m:common
FMTM NODE p:1 r:1 c: e: p: m:common
ADMO CODC p:1 r:1 c: e: p: m:common
STRP FMTM p:1 r:1 c: e: p: m:common
OUTP FLOW p:1 r:1 c: e: p: m:common
ADVP NODE p:1 r:1 c: e: p: m:common
TIMR NODE p:1 r:1 c: e: p: m:common
MEMS STRM p:1 r:1 c: e: p: m:common
PLAT NODE p:1 r:1 c: e: p: m:common
IDCT FLOW p:1 r:1 c: e: p: m:common
SYST TIMR p:1 r:1 c: e: p: m:common
AOUT OUTP p:1 r:1 c: e: p: m:common
VOUT OUTP p:1 r:1 c: e: p: m:common
NULV VOUT p:1 r:1 c: e: p: m:common
FLOW NODE p:1 r:1 c: e: p: m:common
RASX FMTL p:1 r:1 c:
e:asx;wmx;wmweb;wmwebasf;wmwebasx;wvx:V;wax:A
p:and(text,scan(64,stri('<ASX'),0,fwd)) m:common
PLS_ FMTL p:1 r:1 c:audio/x-scpls,audio/scpls els
p:and(text,scan(64,stri('[playlist]'),0,fwd)) m:common
FMT_ FMTM p:1 r:1 c: e: p: m:common
M3U_ FMTL p:1 r:1 c:audio/x-mpegurl,audio/mpegurl e:m3u
p:and(text,gt(512,length),or(eq(lines,1),eq(lines,0))) m:common

This is an Update:
I'm able to successfully extract all the 'dump' files including (Part00.raw, Part01.raw, Part02.raw) and also the '.bin' files from my Micromax using the proper utilities like 'itsutils'. I even successfully converted these files to appropriate 'OS.nb' file. But still i am suffering with some issues and can't able to integrate WM 6.5!
Moreover i think we have to copy the files necessary for Update (.nbk etc.) to the SD Card so that when we enter the Flashing Utility (i.e. Volume Down + Volume Up + Reset) it can automatically update the ROM.
If anyone need help in this beginning procedure please POST a Request here and if anyone would like to help me out for the further procedure please POST a Reply.
Thanks

alliwant said:
This is an Update:
I'm able to successfully extract all the 'dump' files including (Part00.raw, Part01.raw, Part02.raw) and also the '.bin' files from my Micromax using the proper utilities like 'itsutils'. I even successfully converted these files to appropriate 'OS.nb' file. But still i am suffering with some issues and can't able to integrate WM 6.5!
Moreover i think we have to copy the files necessary for Update (.nbk etc.) to the SD Card so that when we enter the Flashing Utility (i.e. Volume Down + Volume Up + Reset) it can automatically update the ROM.
If anyone need help in this beginning procedure please POST a Request here and if anyone would like to help me out for the further procedure please POST a Reply.
Thanks
Click to expand...
Click to collapse
i love u man, u did it.,
if u can copy firmware then, u can upgrade it too., i guess so.
i still couldnt find the key combinations to start bootloader,
I m dying to install any linux distro on it.(maemo/android/dsl)
yes, I would be grateful if u post the method how to do it.
and also i would like to help u by doing experiments on my phone, though i dont know much about it., coz i think i have ****ed my phone already,
it normally doesnt wakes up from sleep mode when battery is less than 40 %.
i also did some reg, changes.
so i m gonna send it to company for sw fix.
and about that, windows 6.5 install, i guess u r right, u have to put files on memory card and boot it in that menu. it will auto upgrade phone.
Thanks a lot. for ur help.

Hello Dear
Well thanks for your Reply. According to me Volume Up + Volume Down + Power is the Bootloader but it automatically skips to Setp:2 or Step:3 and asks for an Update rather than showing the Tri-Color Boot Screen. I think there might be a registry fix or so to fix this problem.
And for extracting the dump follow the Hermes Guide.
Link:
===
wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
If you still face any problem feel free to contact me!
Regards,
~alliwant

wooo hooooo...... am so excited!!!
this finally brings a ray of hope for all W900 users to be able to upgrade their ROMs. Awesome work guys......

yup, my fone does the same. skips straight to
Step 3 Error while updating:
File operate : File does not exist.
Restart the machine?
The only option to select is YES.
Can we ever get WM6.5 or Android or WM7 on this phone??

Well the only problem is to how to Flash the cooked ROM? We don't know the file name and format to be stored in the SD Card so that it automatically Updates when we enter into the Flashing Utility by pressing Volume Up + Volume Down + Reset!

can any of you give a short review of this device. I am thinking of buying this.
How is the performance with stock ROM and especially during navigation ?

Upgrade success to wm6.5
Phew ok guys have successfully upgraded to wm6.5 finally after a long research...
hmmmm so guys now the issue is am stuck with wm6.5 chinese looking to cook a an english rom for the micromax w900. any help to cook will be appreaciated. i tried to cook my own rom from the dumps of the phone but it kind of bricked my phone but was kind of lucky as only the flash area was overwritten.
oh guys one more try to upgrade only if you r really frustrated with the wm6.1. the rom which they had given is far more stable and looks good with spb software.
wm6.5 is fast on micromax.haven't checked much of the software's in wm6.5 as am researching on cooking with english. will give a detailed explanation on how to flash and dump later.on to chinese fix hehe
oh yeah just keep your heads up to get a new phone if it gets bricked
alliwant: alliwant i had done the update with a new rom not with my raw files.. could you give a heads up on how you did it... i got the the os.nb files after using the ruu_signed_rom.nbh and also placing the files part01 and 02 in the same directory..let me know if its a new procedure..
thanks,

Update on micrmx w900
alliwant said:
Well the only problem is to how to Flash the cooked ROM? We don't know the file name and format to be stored in the SD Card so that it automatically Updates when we enter into the Flashing Utility by pressing Volume Up + Volume Down + Reset!
Click to expand...
Click to collapse
alliwant i had done the update with a new rom not with my raw files.. could you give a heads up on how you did it... i got the the os.nb files after using the ruu_signed_rom.nbh and also placing the files part01 and 02 in the same directory..let me know if its a new procedure..
Update: ok never mind.. i did a new rom but with part of my raw files ..it was chinese changed it to english but the rom has minor bugs...anyway thinking to port a wm6.5 rom now ...

Hey i have a micromax w900 and tired with the old OS 6.1. Was desperately looking for an upgrade to 6.5. But im a n00b related to flashing and stuff. How safe is upgrading? Bricking the phone means it can never be recovered to working state? Even by Micromax service center??
If you do create a ROM please share it with us so that all W900 users can benefit from it.
Thanks.

[email protected] said:
Hey i have a micromax w900 and tired with the old OS 6.1. Was desperately looking for an upgrade to 6.5. But im a n00b related to flashing and stuff. How safe is upgrading? Bricking the phone means it can never be recovered to working state? Even by Micromax service center??
If you do create a ROM please share it with us so that all W900 users can benefit from it.
Thanks.
Click to expand...
Click to collapse
sharan.blore: have a look at my post at this thread..
http://forum.xda-developers.com/showthread.php?p=7350563&posted=1#post7350563
i have cooked only 6.1 successfully..i will post it once i get some time in the office
it can not be recovered by you..though service center could replace the logic board on the phone so no issues if you have the warranty intact..

Hi Guys, Great work... so far so Good... As a W900 user with 6.1 let me tell you that this phone serves no purpose.
Reason is .... will not sync with Systems running Windows 7.
I demanded an upgrade to win 6.5 at the service center, where they after making various calls advised me not to,,, compatibility issues with the screen... Goes blank they say.
Your inputs would be much appreciated & do keep up the great work.
P.s, has there been any hardware mods in the phone ?

try this
Micromax w900 phone To enter Factory reset menu
just follow the steps....
press & hold volume down + camera + power i get factory reset option on screen
then just press volume UP to confirm..
then all is done ur set is ok now
if u like my post just press thanks button

unlock vibrant, stuck :S

ok so i followed ALL the steps in this
-thread http://forum.cyanogenmod.com/topic/4999-howto-sim-unlock-your-vibrant-galaxy-s/
I created a bml3.bak, and copied it into my c:/, downloaded sgux.exe also put it in my c:/. however when i open cmd and type, "c:\sgux.exe bml3.bak" It says
Searching code block...
found...
searching codes..
then it returns to normal state, where the code?!
i even tried it with a backup of my nv_data.bin, but i get the same results

no help on this one? , I could pm you a link to my nv_data.bin, and bml3.bak and would also donate if you help me find the code.! =(

I have the same issue!
HEX editing of nv_data.bin helped!! No sim lock anymore
mount the internal SD Card on your computer
make a backup copy of the nv_data.bin file on your computer
using your favorite HEX editor open the nv_data.bin on the sdcard
jump to address 0x181468
you should see a string like this
ff 01 00 00 00 00 46 46
there are 5 different types of locks in 5 different bytes
the FF byte should be left alone
the first byte after the FF is the network lock
the next byte is the network subset lock
the next byte is the sp lock
the next byte is the cp lock
the last byte appears to be a data lock.
the 46 46 should be left alone
Change any 0x01 to 0x00 (or 0x00 to 0x01 to lock for warranty)
save and close file
unmount SD Card
Click to expand...
Click to collapse

[HOWTO] build Kernel for I9001

1) Get the stock kernel sources GT-I9001 from Samsung Open Source Release Center
2) Go into the top kernel directory and execute
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" ariesve_rev00_defconfig
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" -j4
3) The resulting kernel is in arch/arm/boot/zImage
4) Use the following command to pack the boot image
> mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=null androidboot.hardware=qcom androidboot.emmc=true hw=6" -o myBuiltBoot.img --base 0x00400000 --pagesize 4096
5) Copy myBuiltBoot.img to the sdcard. Then open a shell on the phone
# dd if=/sdcard/myBuiltBoot.img of=/dev/block/mmcblk0p8
# sync
6) With the next restart, your kernel will be booted.
Here you can find the original ramdisk + boot.img. I extracted it from a stock-rom smd package.
http://www.eidelen.ch/android/bootGTI9001.zip
Note I: It's possible that your device doesn't start anymore. In such a case I just used Odin for flashing a original stock-rom, which includes a boot.img.
Note II: During step 5) -> I'm not sure if the 'sync' is necessary. It no harm.
Note III: During step 5) -> I compared the memory blocks on the device against an extracted boot.img. Like that I found out which one is the boot-partition (/proc/emmc is empty). Possible that it could be different on your device.
Good Luck,
eidelen
Adds:
Building modules
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" modules_prepare
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" modules

eidelen said:
1) Get the stock kernel sources GT-I9001 from Samsung Open Source Release Center
2) Go into the top kernel directory and execute
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" ariesve_rev00_defconfig
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" -j4
3) The resulting kernel is in arch/arm/boot/zImage
4) Use the following command to pack the boot image
> mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=null androidboot.hardware=qcom androidboot.emmc=true hw=6" -o myBuiltBoot.img --base 0x00400000 --pagesize 4096
5) Copy myBuiltBoot.img to the sdcard. Then open a shell on the phone
# dd if=/sdcard/myBuiltBoot.img of=/dev/block/mmcblk0p8
# sync
6) With the next restart, your kernel will be booted.
Here you can find the original ramdisk + boot.img. I extracted it from a stock-rom smd package.
http://www.eidelen.ch/android/bootGTI9001.zip
Note I: It's possible that your device doesn't start anymore. In such a case I just used Odin for flashing a original stock-rom, which includes a boot.img.
Note II: During step 5) -> I'm not sure if the 'sync' is necessary. It no harm.
Note III: During step 5) -> I compared the memory blocks on the device against an extracted boot.img. Like that I found out which one is the boot-partition (/proc/emmc is empty). Possible that it could be different on your device.
Good Luck,
eidelen
Click to expand...
Click to collapse
What is the advantage of doing all this?

It's only required if you want to modify the kernels source code. For example enabling overclocking or something else.

thanks........are the sources complete?or u face the same problems as 19003?
also,does i9001 have bln?and what is the minimum freq?
also,how do u pack a tar?

The kernel sources are complete, but the 4 modules are not built. It doesn't seem to be a problem, since module version check is off.
I'm not experienced with other Samsung devices; I don't know about bln & freq. I didn't pack a tar (for odin?), I'm flashing the boot.img with the shell command "dd".

i have a noob query....
1)What do i type in "path to cross compiler'?where is it found?
2)how do i install codesoucery toolchain?
sorry this is my first time!

sakindia123 said:
i have a noob query....
1)What do i type in "path to cross compiler'?where is it found?
2)how do i install codesoucery toolchain?
sorry this is my first time!
Click to expand...
Click to collapse
On following page, codesoucery installation is quickly mentioned
http://developer.sonyericsson.com/wp/2011/05/06/how-to-build-a-linux-kernel/
I'm using the cross-compiler from the Android Open Source project. There is a good manual from cyanogenmod:
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
Br,
adrian

eidelen said:
1) Get the stock kernel sources GT-I9001 from Samsung Open Source Release Center
2) Go into the top kernel directory and execute
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" ariesve_rev00_defconfig
> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" -j4
3) The resulting kernel is in arch/arm/boot/zImage
4) Use the following command to pack the boot image
> mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=null androidboot.hardware=qcom androidboot.emmc=true hw=6" -o myBuiltBoot.img --base 0x00400000 --pagesize 4096
5) Copy myBuiltBoot.img to the sdcard. Then open a shell on the phone
# dd if=/sdcard/myBuiltBoot.img of=/dev/block/mmcblk0p8
# sync
6) With the next restart, your kernel will be booted.
Here you can find the original ramdisk + boot.img. I extracted it from a stock-rom smd package.
http://www.eidelen.ch/android/bootGTI9001.zip
Note I: It's possible that your device doesn't start anymore. In such a case I just used Odin for flashing a original stock-rom, which includes a boot.img.
Note II: During step 5) -> I'm not sure if the 'sync' is necessary. It no harm.
Note III: During step 5) -> I compared the memory blocks on the device against an extracted boot.img. Like that I found out which one is the boot-partition (/proc/emmc is empty). Possible that it could be different on your device.
Good Luck,
eidelen
Click to expand...
Click to collapse
Thank you mate!
This provides A LOT OF INFO for CWM

yet other n00b query!
arm-2011.03-42-arm-none-eabi.bin.......how do i install this cross-compiler?

sakindia123 said:
yet other n00b query!
arm-2011.03-42-arm-none-eabi.bin.......how do i install this cross-compiler?
Click to expand...
Click to collapse
here's the readme from samsung:
1. How to Build
- get Toolchain
From Codesourcery site( http://www.codesourcery.com )
Ex) Download : http://www.codesourcery.com/sgpp/li...09-51-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
recommand :
Feature : ARM
Target OS : "EABI"
package : "IA32 GNU/Linux TAR"
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
Ex) ARCH ?= arm
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi- // You have to check compiler path
- command
$ cd kernel
$ make ariesve_rev00_defconfig
$ make
2. Output files
- Kernel : kernel/arch/arm/boot/zImage
just unpack the toolchain and you're good to go!

sakindia123 said:
thanks........are the sources complete?or u face the same problems as 19003?
also,does i9001 have bln?and what is the minimum freq?
also,how do u pack a tar?
Click to expand...
Click to collapse
To pack a tar, use
Code:
tar
For details on how it works
Code:
man tar

eBug said:
To pack a tar, use
Code:
tar
For details on how it works
Code:
man tar
Click to expand...
Click to collapse
thanks..i had already got that working...
i am just unable to sync repo android source

i edited the makefile acc. to my toolchain location,but i get error"not found"
could anyone tell me an exact path (where u placed it) to place the toolchain bin?its called arm-2011.03-42-arm-none-eabi.bin
last of all,how to unpack boot.img?

sakindia123 said:
i edited the makefile acc. to my toolchain location,but i get error"not found"
could anyone tell me an exact path (where u placed it) to place the toolchain bin?its called arm-2011.03-42-arm-none-eabi.bin
last of all,how to unpack boot.img?
Click to expand...
Click to collapse
Install tje toolchain
Figure out yourself how.
Sent from my GT-I9100

sakindia123 said:
i edited the makefile acc. to my toolchain location,but i get error"not found"
could anyone tell me an exact path (where u placed it) to place the toolchain bin?its called arm-2011.03-42-arm-none-eabi.bin
last of all,how to unpack boot.img?
Click to expand...
Click to collapse
I learned from following page about android images. http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
It's the first search result for "unpack boot.img". But boycotting google is kind of rebelling
You have to be careful when packing the boot.img - the arguments have to be right. That works for S+
mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=null androidboot.hardware=qcom androidboot.emmc=true hw=6" -o myBuiltBoot.img --base 0x00400000 --pagesize 4096
If you work with a different Kernel, the base-address might be different. You can find that value in your Kernels .config file. I wasted a lot of time by watching none booting kernels because of that

Noob question...
GT-I9001_Kernel.tar.gz contain over 35 000 files...
All files involved in creating zImage ?
Or is it possible to reduce only for mandatory involved/included files?
For GT-I9001...
Thanx in advance.
Best Regards

adfree said:
Noob question...
GT-I9001_Kernel.tar.gz contain over 35 000 files...
All files involved in creating zImage ?
Or is it possible to reduce only for mandatory involved/included files?
For GT-I9001...
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
Yes, you'll need all those. All kernel drivers are there including touchscreen, touch keys, GPU, i2c, CPU, board and many many more. It's cross-compiling
The zImage will basically be a combination of all the kernel modules.

Thanx.
For my "Porting" journey... it's Copy & Paste Action...
http://forum.xda-developers.com/showthread.php?t=2116846
But, how to identify files mandatory for:
1.
Hardware Keys like:
Code:
Volume +
Volume -
Home
Power
2.
Touch keys
Code:
Menu
Back
3.
Touchscreen input generally...
My idea is to use existing "drivers" from similar devices... and test if my S8600 explode or by luck do something...
I9001 Touch drivers from I9001 do nothing on my S8600...
No event... via ADB getevent visible.
http://forum.xda-developers.com/showpost.php?p=54929846&postcount=698
Code:
GT-I8150B_GB_Opensource.zip
GT-I8150T_Opensource.zip
GT-I8150_CHN_CHN(1).zip
GT-I8150_CHN_CHN.zip
GT-I8150_HK.zip
GT-I8150_Opensource(1).zip
GT-I8150_Opensource(2).zip
GT-I8150_Opensource.zip
SGH-I847_ATT_Opensource.zip
SGH-I847_Opensource_Update1.zip
SPH-M840_BST_JB_Opensource.zip
SPH-M840_NA_JB_Opensource.zip
SPH-M950_ICS_Opensource(1).zip
SPH-M950_ICS_Opensource.zip
SPH-M950_ICS_Opensource_Update1.zip
SPH-M950_JB_Opensource.zip
SPH-M950_NA_JB_Opensource.zip
Any help is welcome.
Thanx in advance.
Best Regards

adfree said:
Noob question...
GT-I9001_Kernel.tar.gz contain over 35 000 files...
All files involved in creating zImage ?
Or is it possible to reduce only for mandatory involved/included files?
For GT-I9001...
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
Not all of them are compiled ; The kernel source contains drivers for many hardwares and support of architectures which aren't really needed for I9001.so only some thousands of them are compiled. If sb compile all of those drivers (not arch files) it will be a +200mb zimage .
Sent from my GT-I9001 using Tapatalk

Please, I need help to fix "few" problems on GT-S8600... with I9001 Firmware
Because not supported Hardware...
Maybe I can start with "easier" task...
Volume + key on S8600 do nothing...
But I can see result of getevent:
Code:
# getevent
getevent
add device 1: /dev/input/event2
name: "ariesve_keypad"
add device 2: /dev/input/event8
name: "melfas_touchkey"
add device 3: /dev/input/event7
name: "7k_handset"
add device 4: /dev/input/event6
name: "light"
add device 5: /dev/input/event5
name: "proximity"
add device 6: /dev/input/event4
name: "orientation"
add device 7: /dev/input/event3
name: "quantom-touchscreen"
add device 8: /dev/input/event1
name: "dock"
add device 9: /dev/input/event0
name: "sec_jack"
/dev/input/event2: 0004 0004 00000000
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000008
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000010
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000018
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000020
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000000
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000008
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000010
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000018
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000020
/dev/input/event2: 0000 0000 00000000
I9001 Android detect that Volume + is pressed... on my S8600...
But 000 seems have no function or is wrong...
Volume - is same like I9001
Code:
/dev/input/event2: 0004 0004 00000001
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000009
/dev/input/event2: 0001 [B]0072[/B] 00000001
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000011
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000019
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000021
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000001
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000009
/dev/input/event2: 0001 [B]0072[/B] 00000000
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000011
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000019
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000021
/dev/input/event2: 0000 0000 00000000
/dev/input/event6: 0003 0006 000000c8
HEX Value 0072 in DEC is 114...
Volume + if I remember correct is 115... so:
0x73
Logged key event on bada leads to my theory...
That maybe 113 could work, if defined...
Taken from bada... Volume + has lower Value...
Code:
Volume +
CAppSndKey::IsMutedKeytone: iKeyType ([B]42[/B]) cause by AUI
Volume -
CAppSndKey::IsMutedKeytone: iKeyType ([B]43[/B]) cause by AUI
Any help or suggestion is welcome.
Thanx in advance.
Best Regards

[Q] Can somebody help me interpret this debug screen? (Wave GT8500)

A while ago I received a free Wave S8500 running Bada 1.2. Since this OS was pretty awful I decided to upgrade having done the process before on another phone of the same model. Unfortunately I was stupid and managed to flash the wrong files so my phone ended up in a boot loop. I found the correct set of files and tried to flash them but Multiloader only works up to SHP APP, at this point it fails with a "serial port open error". When I try and boot the phone I reach a blue screen full of the following debugging information:
Page: 1/2 <Pic #>
S/W version: S8500+XP+KJ1
Modem: Q6270B-KPRBL-1.5.45T
SHP: VPP R5 2.1.1
Build Host:s1-AGENT08
BuildAt:2011/10/05 22:44:23
App Debug Level l: 0
ASSERTION_REQUIRE:m_hLib != IN
VALID_HOBJ failed/ (file WinLibDllMgr.cpp, line 40)
Cannot load (shpWindow)
<Callstack information>
PC = 40318BEF OemDumpRegister
LR = 403118 OemDumpRegister
<Running Task(InvalidTask) Call stack>
_SysAssertReport
GWES:WinLib::CDI I Mgr::LoadLibrary
WinLibDllProxyInit
WinLibDispatch
OemBmPrelnitMochaTask
mochaTaskPreInit
Page: 2/2 <* #>
All HW Information:
HW VERSION: S8500_REV07
IMEI VERSION: Not Active
RF CAL DATE: Not Active
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = 2, Current BMPs = 0
Nucleus Task Information:
Running Task name = SHP_PRE SI
ices = 00000000
Wait = 00000000
Signal = 00000000
Priority = 0
To exit
Press 0 for 2sec
After pressing the home key it goes to a screen I've never previously seen with yellow text stating "UPLOAD to pc". Clearly the phone has a problem with the SHP_APP file and the Windows system it's connected to but beyond that I'm completely out of my depth. Can somebody shed some light on what is wrong with my phone and how I might go about fixing it?
Thanks in advance.

[Q] Attempt to open device /dev/radio0 yields EBUSY

I have a rooted Xperia E C1504 on which I would like to access the FM receiver chipset for a custom FM radio app I'm working on. Trouble is that my fcntl open() call to /dev/radio0 keeps returning EBUSY (errno 16: device or resource busy). Here is the code I'm using to try to open the device (executed in a root shell):
Code:
#define DEFAULT_RADIO_DEVICE "/dev/radio0"
...
radio_fd = open(DEFAULT_RADIO_DEVICE, O_RDWR);
I verified that the radio device is functional with the stock FM Radio app, which was able to tune to a frequency and receive PCM successfully. I turned this app off via its power button icon (this should release /dev/radio0, correct?) and explicitly force-stopped the stock FM Radio app from the Settings->Apps menu, and even deleting Radio.apk (the stock FM Radio app package) from /system/apps with Root Browser and then rebooting the phone, but my program continues to return EBUSY when it executes the above instruction.
What is the best way to investigate what process might be holding a lock on /dev/radio0 and kill it? I tried [adb shell "su -c 'lsof /dev/radio0'"] but the returned list didn't have any entries exactly matching /dev/radio0. There were quite a few cases of '/dev/log/radio' and almost 300 cases of just the word 'radio', but I was expecting to see something listed as using exactly /dev/radio0. I also tried [adb shell ps | grep radio] which returned
Code:
root 79 2 0 0 ffffffff 00000000 S kfmradio
radio 155 140 20416 3232 ffffffff 00000000 S /system/bin/rild
radio 178 140 7820 2472 ffffffff 00000000 S /system/bin/cnd
radio 215 140 6152 500 ffffffff 00000000 S /system/bin/qmuxd
radio 231 140 7288 752 ffffffff 00000000 S /system/bin/netmgrd
radio 610 157 311448 35704 ffffffff 00000000 S com.android.phone
the kfmradio process looked suspicious so I tried killing it, which didn't return any errors, but re-running the filtered ps list above showed that kfmradio was still in the process list (I suppose the OS restarted it?) Any advice regarding troubleshooting EBUSY returns from fcntl open() calls would be very helpful.
Device Model: Sony Xperia E C1504
Linux kernel: 3.4.0
Android OS: 4.1.1
Firmware version: Stock Kernel Xperia E C1505_11.3.A.0.47 (supposed to work for the C1504 as well)
Rooted with: SRSRoot and the 'Gandalf' exploit.