Database Info

Unable to flash new SPL +more

I made the major mistake of flashing the vodafone hero rom to my 32A SHIP S-ON H (nordic htc branded sapphire). After figuring out that I made a bad move, I tried flashing the superhero v2 that I had before, but it still got stuck at the HTC Magic logo right after boot.
Since then, I've tried a lot of things like re-rooting, flashing a different SPL and doing a restore from Nandroid files.
Flashing a different SPL doesn't change the SPL number at the HBOOT screen (tried both the out-of-the-box SPL, the .2005 engineering SPL and the modded .2004 SPL, but when I reboot it's back to HBOOT-1.33.0009.
restoring from nandroid fails with "FAILED (remote: signature verify fail)"
I'm running out of ideas, though I have a hunch that I'm not flashing the SPL correctly
Any help would be very much welcome

HBOOT-1.33.0009 will not let you fastboot flash nandroid images, Although you still should be able to use a modded recovery to reinstall the system.
Did you try installing superhero via the update.zip?

I only tried that once - here goes another try...
EDIT: Shouldn't I still be able to flash a new SPL?
EDIT2: using a modded recovery and flashing superhero gives no errors (though the progress bar stops at ~80% for a while then all of a sudden, it's complete). After rebooting it it gets stuck on the very first "HTC Magic" screen, so it's not getting very far since superhero loads with the "T-mobile G1" screen

losludvig said:
I made the major mistake of flashing the vodafone hero rom to my 32A SHIP S-ON H (nordic htc branded sapphire). After figuring out that I made a bad move, I tried flashing the superhero v2 that I had before, but it still got stuck at the HTC Magic logo right after boot.
Since then, I've tried a lot of things like re-rooting, flashing a different SPL and doing a restore from Nandroid files.
Flashing a different SPL doesn't change the SPL number at the HBOOT screen (tried both the out-of-the-box SPL, the .2005 engineering SPL and the modded .2004 SPL, but when I reboot it's back to HBOOT-1.33.0009.
restoring from nandroid fails with "FAILED (remote: signature verify fail)"
I'm running out of ideas, though I have a hunch that I'm not flashing the SPL correctly
Any help would be very much welcome
Click to expand...
Click to collapse
Try this :
1. Switch your device into fastboot mode.
2. Fastboot this recovery. (fastboot boot recovery-RAv1.0H.img).
3. Perform a data wipe.
4.
- $adb shell flash_image boot /sdcard/<yournandroidbackupdir>/boot.img
- $adb shell flash_image system /sdcard/<yournandroidbackupdir>/system.img
- $adb shell flash_image recovery /sdcard/<yournandroidbackupdir>/recovery.img
- $adb shell flash_image userdata /sdcard/<yournandroidbackupdir>/userdata.img

I get the error /sbin/sh flash_image: not found
I know of the command "which <command>", but when running "adb shell which flash_image" I get only a blank line.
If I do "adb shell which" I get an explanation of the command, so I don't get why it doesn't work...

If you get a blank line it means that busybox can not find the flash_image binary in the directories specified in your PATH variable.
Try the following :
1. Switch your device into fastboot mode.
2. $fastboot boot recovery-RAv1.0H.img
3. Perform a data wipe.
4. $adb shell mount -a
5.
- $adb shell flash_image boot /sdcard/<yournandroidbackupdir>/boot.img
- $adb shell flash_image system /sdcard/<yournandroidbackupdir>/system.img
- $adb shell flash_image recovery /sdcard/<yournandroidbackupdir>/recovery.img
- $adb shell flash_image userdata /sdcard/<yournandroidbackupdir>/userdata.img
If you still get the same flash_image not found error try this :
1. Get the flash_image binary somewhere (if you don't find it I'll upload it later today).
2. Switch your device into fastboot mode.
3. fastboot boot recovery-RAv1.0H.img
4. Perform a data wipe.
5. Push the flash_image binary to your sbin : adb push flash_image /sbin/flash_image
6. Check if it is actually found : adb shell which flash_image
4.
- $adb shell flash_image boot /sdcard/<yournandroidbackupdir>/boot.img
- $adb shell flash_image system /sdcard/<yournandroidbackupdir>/system.img
- $adb shell flash_image recovery /sdcard/<yournandroidbackupdir>/recovery.img
- $adb shell flash_image userdata /sdcard/<yournandroidbackupdir>/userdata.img

can you post the files? I have the same problem with no back up
thanks

I still can't find flash_image, so I would love it if you posted it
EDIT: found flash_image here: http://jf.odiness.com/v1.50/JFv1.50_ADP1.5.zip
pushing flash_image works fine, but "adb shell which flash_image" still returns a blank line.
Also "adb shell flash_image" returns "/sbin/sh: flash_image: Permission denied"

just tried running a "adb shell mount -a" before doing the flash_image command - that made the command work (finally!)
Flashing boot works fine, but flashing system gives some errors:
Code:
C:\Temp\tools>adb shell flash_image system /sdcard/system.img
mtd: erase failure at 0x013c0000 (I/O error)
mtd: erase failure at 0x013c0000 (I/O error)
mtd: skipping write block at 0x013c0000
mtd: erase failure at 0x02d60000 (I/O error)
mtd: erase failure at 0x02d60000 (I/O error)
mtd: skipping write block at 0x02d60000
... Any ideas?
EDIT: After flashing sytem (with errors) and boot, I went ahead and rebooted... After vibrating and displaying the HTC magic bootscreen for a moment it looks like it's changing image (the screen refreshes), though it's to the same HTC magic logo...
Question - are the errors I'm getting when flashing system because two processes are running (flash_image and shell)?

nordic is htc branded right? if so your going to need a rom from here http://forum.xda-developers.com/showthread.php?t=531837

sammypwns said:
nordic is htc branded right? if so your going to need a rom from here http://forum.xda-developers.com/showthread.php?t=531837
Click to expand...
Click to collapse
correct... However I am not able to boot any of the three roms posted there - it's stuck at the very first "HTC Magic" screen after turning on

flash_image does help me a bit - If I flash my back up'ed boot.img I have root access via adb when the phone enters a loop.
Not sure if this is any help but I get this code from doing "adb logcat"
Code:
D/AndroidRuntime( 329):
D/AndroidRuntime( 329): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 329): CheckJNI is OFF
I/dalvikvm( 329): DexOpt: Some deps went away
E/dalvikvm( 329): /system/framework/com.htc.android.easopen.jar odex has stale
dependencies
I/dalvikvm( 329): Zip is good, but no classes.dex inside, and no valid .odex fi
le in the same directory
D/libc-abort( 329): abort() called in pid 329
I/DEBUG ( 31): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 31): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRB43/148830
:user/ota-rel-keys,release-keys'
I/DEBUG ( 31): pid: 329, tid: 329 >>> zygote <<<
I/DEBUG ( 31): signal 11 (SIGSEGV), fault addr deadbaad
I/DEBUG ( 31): r0 00000003 r1 deadbaad r2 00000027 r3 ffff6180
I/DEBUG ( 31): r4 ffff6158 r5 afe2ff28 r6 afe39dd0 r7 afe39dd0
I/DEBUG ( 31): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 31): ip 0000001a sp be8a54e8 lr afe1ff33 pc afe1066a cpsr 200
00030
I/DEBUG ( 31): #00 pc 0001066a /system/lib/libc.so
I/DEBUG ( 31): #01 pc 0000afae /system/lib/libc.so
I/DEBUG ( 31): #02 pc 00042198 /system/lib/libdvm.so
I/DEBUG ( 31): #03 pc 0005c276 /system/lib/libdvm.so
I/DEBUG ( 31): #04 pc 0005c330 /system/lib/libdvm.so
I/DEBUG ( 31): #05 pc 0005c4b2 /system/lib/libdvm.so
I/DEBUG ( 31): #06 pc 0003c926 /system/lib/libdvm.so
I/DEBUG ( 31): #07 pc 00040f44 /system/lib/libdvm.so
I/DEBUG ( 31): #08 pc 0002b7a6 /system/lib/libandroid_runtime.so
I/DEBUG ( 31): #09 pc 00008bf2 /system/bin/app_process
I/DEBUG ( 31): #10 pc 0001fd22 /system/lib/libc.so
I/DEBUG ( 31): #11 pc 0000bcb2 /system/lib/libc.so
I/DEBUG ( 31): #12 pc b000157e /system/bin/linker
I/DEBUG ( 31): stack:
I/DEBUG ( 31): be8a54a8 0000a000 [heap]
I/DEBUG ( 31): be8a54ac 00069b95 [heap]
I/DEBUG ( 31): be8a54b0 00069b53 [heap]
I/DEBUG ( 31): be8a54b4 00000000
I/DEBUG ( 31): be8a54b8 00069b53 [heap]
I/DEBUG ( 31): be8a54bc fffe637c
I/DEBUG ( 31): be8a54c0 ad083e1c
I/DEBUG ( 31): be8a54c4 250c8c5b
I/DEBUG ( 31): be8a54c8 00000002
I/DEBUG ( 31): be8a54cc ffff6158
I/DEBUG ( 31): be8a54d0 afe2ff28 /system/lib/libc.so
I/DEBUG ( 31): be8a54d4 afe39dd0
I/DEBUG ( 31): be8a54d8 afe39dd0
I/DEBUG ( 31): be8a54dc afe10663 /system/lib/libc.so
I/DEBUG ( 31): be8a54e0 df002777
I/DEBUG ( 31): be8a54e4 e3a070ad
I/DEBUG ( 31): #00 be8a54e8 000699b0 [heap]
I/DEBUG ( 31): be8a54ec afe0e940 /system/lib/libc.so
I/DEBUG ( 31): be8a54f0 000699b0 [heap]
I/DEBUG ( 31): be8a54f4 afe3c980
I/DEBUG ( 31): be8a54f8 00002bb0
I/DEBUG ( 31): be8a54fc fffffbdf
I/DEBUG ( 31): be8a5500 afe39dd0
I/DEBUG ( 31): be8a5504 000699a8 [heap]
I/DEBUG ( 31): be8a5508 00002bb0
I/DEBUG ( 31): be8a550c afe0afb3 /system/lib/libc.so
I/DEBUG ( 31): #01 be8a5510 afe3c980
I/DEBUG ( 31): be8a5514 afe39dd0
I/DEBUG ( 31): be8a5518 afe3c980
I/DEBUG ( 31): be8a551c afe39dd0
I/DEBUG ( 31): be8a5520 0000a000 [heap]
I/DEBUG ( 31): be8a5524 be8a55a0 [stack]
I/DEBUG ( 31): be8a5528 ad083e1c
I/DEBUG ( 31): be8a552c ffffffff
I/DEBUG ( 31): be8a5530 ad083e1c
I/DEBUG ( 31): be8a5534 00000000
I/DEBUG ( 31): be8a5538 fffe637c
I/DEBUG ( 31): be8a553c ad04219b /system/lib/libdvm.so
"adb get-state" returns "device", so I guess it thinks that It's booted up fine.
I was wondering if adb push'ing the system folder of a rom could make my troubles go away, but when I do "adb push /Temp/system/ /system/"
I get "cannot stat '/Temp/system/': No such file or directory" even though the folder exists...
Please help as I'm starting to get desperate

I don't like those erase failures you're getting...

I don't like those erase failures you're getting...
If I were you I would try to perform an erase in fastboot mode first.
Find an update.zip (HTC branded) which includes a full boot and system and copy the update.zip to your sdcard. Maybe try a lite version of one here
1. Switch your device into fastboot mode.
2. Perform an erase (hopefully you don't get any errors while doing this) :
$fastboot erase boot
$fastboot erase system
$fastboot erase recovery
$fastboot erase cache
$fastboot erase userdata
3. $fastboot boot recovery-RAv1.0H.img
wait for a while...
4. update
5. reboot

I have a similar problem. Can set the phone in fastboot usb mode, but my computers wont show anything in devices list. My computer finds and installs the phone as HTC Bootloader when in fastboot usb mode.
Any clue why my computer wont detect my phone propery?
DVT32B
HBOOT-1.33.2005 (SAPP10000)
CPLD-10
My computer finds my G1 as normal if I connect it showing it as HTC Bootloader in Device Manager.
Any help and I'll be very grateful.

perhaps try on ubuntu?

Have tried with XP, Vista, Win7 and Mac.
Not tried Unbuntu yet. Was hoping not to install Unbuntu on any of my computers.

Amon_RA said:
I don't like those erase failures you're getting...
If I were you I would try to perform an erase in fastboot mode first.
Find an update.zip (HTC branded) which includes a full boot and system and copy the update.zip to your sdcard. Maybe try a lite version of one here
1. Switch your device into fastboot mode.
2. Perform an erase (hopefully you don't get any errors while doing this) :
$fastboot erase boot
$fastboot erase system
$fastboot erase recovery
$fastboot erase cache
$fastboot erase userdata
3. $fastboot boot recovery-RAv1.0H.img
wait for a while...
4. update
5. reboot
Click to expand...
Click to collapse
Sadly, that doesn't work either

what i did when i had mine stuck at the first splash (i thot i'd killed my phone too, all partitions were erased at this stage with stock SPL & recovery):
1. enter fastboot
2. $fastboot boot recovery-RAv1.0H.img
3. on phone screen apply update.zip, where update.zip is haykuro's 2005 engineer SPL (dont have the actual filename handy, sorry but u can find it in the SPL collection)
4. power off, enter fastboot again
5. $fastboot flash nandroid backed system, data, misc, boot in order.
6. finally i applied stock SPL update.zip back, not necessary tho.

assembledinnz said:
what i did when i had mine stuck at the first splash (i thot i'd killed my phone too, all partitions were erased at this stage with stock SPL & recovery):
1. enter fastboot
2. $fastboot boot recovery-RAv1.0H.img
3. on phone screen apply update.zip, where update.zip is haykuro's 2005 engineer SPL (dont have the actual filename handy, sorry but u can find it in the SPL collection)
4. power off, enter fastboot again
5. $fastboot flash nandroid backed system, data, misc, boot in order.
6. finally i applied stock SPL update.zip back, not necessary tho.
Click to expand...
Click to collapse
Sadly, I can't flash my SPL (as indicated by the title of the thread)
I guess that it's a hardware fault, and I'm returning my phone...
EDIT: just got home from the store, I got a new phone - no questions asked

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

[ROM][2.3.8][OFFICIAL][BUILD #1] CyanMobileX Compiled From Source [15/01/2013]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the Cyanmobile eXperience
Hey there peeps, I compiled a new ROM for the HTC Sapphire -- CyanMobile!
It's made by the CyanMobile team, led by Squadzone.
Here's a short description (according to https://raw.github.com/CyanMobile/android_cyanmobile/gingerbread/Definitions.txt) with grammar edited by me:
What is CyanMobile?
CyanMobile is an aftermarket ROM like CyanogenMod, MIUI, JoyOS, LewaOS and others that are built from source. It is based on CyanogenMod 7 (Gingerbread v2.3.7) and uses modifications from AOSP and AOKP
Thanks To CyanogenMod Team, AOKP Team, and AOSP Team for Their Work
**********************************************************************************************************************
** CyanMobile is Short of " *Cyan* (CyanogenMod) *Mob* (Mobiling) *I* (Improving) and *L* (Let's) *E* (Experiment)" **
**********************************************************************************************************************
All features are based on what uses do and what users need with a lots of improvement here and there.
This ROM optimizes Gingerbread, but uses updates from other branchs (ICS stuff, AOSP and AOKP) with reverse engineering or backporting skill.
It can be used without needing to have any Google application installed....
Let us show you what is in CyanMobile:
====================================================================================================
1. Statusbar :
* Date
- Show/Hide Date
- Date Colour
* Notications
- Ticker Color
- No Title Color
- Latest Title Color
- Ongoing Title Color
- Clear Label Button Color
- Title Color
- Item Color
- Time Color
- Tile View [ Android 4.2 ]
* Icons
- Show/Hide Notification Icons
- Show/Hide Statusbar Icons
- Show/Hide Headset/Alarm/Bluetooth/Gps/Sync/Wifi/3G/4G Icon
* Clock
- 4 Clock styles (Right, Left, Center and Hide)
- Clock Color
- Clock Font Size
* Carrier label
- Show/Hide Carrier Label
- Bottom Carrier Label
- 3 Carrier Label On Statusbar Styles (Right, Left and Center)
- Carrier Label Color
- 4 Carrier Logo Styles (Right, Left, Center and Custom Logo)
* Signal
- 5 Different Styles (Bars, Text, Text w/dBm, text w/Auto Color and Hide)
- Wifi Signal Text
* Battery
- 7 Different Styles (Icon, Percentage, Top Statusbar, Side Bar, Behind Statusbar, Navigation Bar and Hide)
- 3 Different Battery Percentage Format (Default, Percentage and Full Color)
- Statusbar Battery Color
* Power Widget
- 4 Different Layouts (Default, Bottom, Grid and Tab)
- Music Widget
- Grid Layout Customizing
* Misc
- Refactor New Statusbar Layout
- Power Clock
- Power Date
- Weather PopUp
- Shortcut Button
- Show/Hide Statusbar
- Reverse Statusbar Icons And Layout
- Statusbar Brightness Control
- Statusbar Fonts Size
- Statusbar Icons Size
- Statusbar Height Size
- Statusbar Background
- Statusbar Background Color
- Notification Background
- Notification Background Color
====================================================================================================
2. Framework :
* Lockscreen
- 7 Different Lockscreen Styles (Sliding Tab, Rotary, Lense, Ring, Honeycomb (beta), Circular (alpha) , Sense (Beta) , Jellybean Glow (Beta) and Jellybean Pad (BETA) )
- Lockscreen Widget Color
- Sms/Call Notifications
- Fuzzy Clock
- Kanji Clock
- Custom Text Lockscreen
- Widget Layouts
- Pattern Styles
* Power Saver
- Screen Off Data Action
- Data Action Delay
- Sync Action
- Sync Time Interval
- Screen Off Wifi Action
- Sync Data Usage
- Mobile Data Preference
* Application
- Native A2SD Framework Core
- Installation Place
* Display
- Bravia Engine
- Rotation Animation
- Window Animations
- Transition Animations
- LCD Density
* Input
- Quick Key Behavior
- Enable/Disable Vibrate on Shutdown
- Explorer Key
* Power Menu
- Show/Hide Power menu/Silent/Airplane/Profile/Screenshot/Power saver/Hibernate/Suspend Toggles
* Fonts
- Change Fonts System
- Change Fonts Type
* OverScroll
- Effect
- Color
- Weight
* Core Replacer
- Change System Apk
- Change Framework Apk/Jar
* Boot/Shutdown animation and Sound
- Preview
- Change Bootanimation
- Change Shutdownanimation
- Change Bootsound
- Reset
* Misc
- New Notifications Design
- Intruder Alert is Life
- New Dialog Design
- Backported Some Apis From Jellybean
- Clear Market Data
- Global Text Color Change
- Global App Background Change
- Soft Button Statusbar
- Navigation Button Bar
- Choose Navi Button
- Navigation Button Bar Size
- Navigation Bar Background
- Extend Power Menu
- Remap Volume Keys
- Lock Volume Keys
- Volume Key Beeps
- Swap Volume Keys
- Task Switcher
====================================================================================================
3. Sound :
* Features
- Loop Ringtone
- Flip Down To Mute Ringer/Snooze Alarm
- Increasing Ringtone Volume
- Less Frequent Notification Sound
- Battery Full/Low Alert
- Charging Plug/Unplug Sound
====================================================================================================
4. Tethering :
* Features
- Bluetooth Tether
- Auto Usb Tether
====================================================================================================
5. Phone :
* Features
- Smart Phone Call
- Back Button To End Call
- Menu Button To Answer Call
- Reject Call with Message
- Allow Incall UI Touch
- Call Me Louder While Inside Bags
- Speed Dials
- Video As Ringtone
- Ring Delay
- Export/Import SIM Contacts
====================================================================================================
6. Messaging :
* Features
- Bubble/Black/Transparent Theme
- Smart Phone Call
- Hide Avatar
- Strip Unicode
- Emoji Support
- Convo List/Subject Font Size
- Sms Vibrate Morse
- Brutal Sender
- Sms PopUp
====================================================================================================
7. Music :
* Features
- Shake To Next/Prev/Play/Pause/Shuttle Track
- Favorite Folder
- Flip To Play/Pause
- Smooth Play Track
====================================================================================================
8. Locations :
* Features
- Enable/Disable Assisted GPS
- GPS Tracker Performance
- Security Device Finder
====================================================================================================
9. Performance :
* Features
- New I/O Scheduler Option
- New Dithering Support
- Enable Bootsound
- Bootsound Volume
- Enable Shutdownanimation
- Gmaps Hack
- KSM Settings
- Battery Polling
- Low Mem Killer Option
- Scrolling Option
- SD Read Ahead Size option
- Screen Off Max CPU Freq
====================================================================================================
10. Misc :
* Features
- ADWLauncher Improved
- Browser Improved
- Calculator Improved
- FM Radio Improved
- File Manager Updated
- SIM ToolKit Improved
- Screenshots Improved
- Task Manager
- Voice Dialer Improved
====================================================================================================
11. All Binary and Library is up to Date
====================================================================================================
That's it, other features not mentioned here came from CyanogenMod 7
Don't Use Any Scripts Like Link2SD, Bravia Hack, Xloud etc They Are Inbuilt !!
Click to expand...
Click to collapse
To Find OUT the features, YOU NEED TO PLAY AROUND WITH THE ROM xD
CyanMobile tries to improve all hardware functions and is always adding new features so it may have some bugs and requires user feedback to fix the bugs.
DONATION:
Donate to Keyur Maru
Donate to Squadzone
Check Next Post For What's Working ! and What's Not !

=======================
Cyan MoBiLe eXperiance
=======================
What's Working in it ? [ Hope so ]
-Network
-HW
-Audio
-Video
-Cam
-DAMM SMOOTH
-Sensors
What's Not Working ? [ Hope so ]
-You Need to Tell me xD
For Change Log Check Next Post

Change Log for Build #1 [16/01/13]
Initial Release for Sapphire
*****Please Read the Flashing Instructions !*****

Screenshots From Wildfire Buzz , LGE P500 And Galaxy Fit
This are From Other Devices Please Provide me From Sapphire Thank you !

DownLoadS
Current Version
Click to expand...
Click to collapse
update-CyanMobile-eXperience-DS-20130116-Release.zip
Click to expand...
Click to collapse
Click that image to start download of latest rom
Google Apps
Click me to Advance the Exploit [ Google APPS ]

***Important***​
How To Flash The Rom xD * IMPORTANT *
-Click Thanks , Rate The Thread And Press Newsworthy Thread ( OPTIONAL BUT * HIGHLY RECOMMENDED * )
-Download The Rom
-Wipe ALL
-Flash The Rom
-Reboot From Recovery
-Now Wait for 3-4 Minutes
-Rom Will Not Boot
-Now Remove Battery
-Reinsert Battery
-Now Start The Phone
-It will Boot up Now
-Enjoy The Rom

Hello,
CMX Users Now I had setted up CMX BuildBot !! Now you could always check status of the builds !!
Keep your eyes here : http://builder.pecancm.insomnia247.nl/job/CyanMobile-Builds/
It is Not Building Only for Sapphire It is Building LG P350 , LG P500 , HTC Buzz and More Devices to be added in future !!
DONATION:
Donate to Keyur Maru For Buying this Phone So I can Provide Further Updates
Donate to Sqadzone

I will be ur tester. sound like a good ROM.
could you include some pics or screen capture? thanks for your effort on our magic.

I want to test this rom. But I can't see link of the rom.

It is released

I have a HTC magic 32A device but I could not find rom for it.

hanntbk said:
I have a HTC magic 32A device but I could not find rom for it.
Click to expand...
Click to collapse
there is important information missing...
is this for 32A or 32B?
if it is for 32A, is it for old radio or new radio?
Thanks!

blizard80 said:
there is important information missing...
is this for 32A or 32B?
if it is for 32A, is it for old radio or new radio?
Thanks!
Click to expand...
Click to collapse
Is official cm7 for 32A or 32B !! it is same as cm7!

Cm7 is not officially available to sapphire.
So I can flash that file in either a 32A old radio or new radio? Has auto kernel?
I will test later.
Thank you!
Sent from my BlackBerry 9900 using Tapatalk

blizard80 said:
Cm7 is not officially available to sapphire.
So I can flash that file in either a 32A old radio or new radio? Has auto kernel?
I will test later.
Thank you!
Sent from my BlackBerry 9900 using Tapatalk
Click to expand...
Click to collapse
What the hell!!!! I compiled with mods to this device config it says it is for dream_sapphire https://github.com/CyanogenMod/android_device_htc_dream_sapphire
so this is not for this device ?

first, thanks for releasing this for the sapphire.
what i was saying is that CM7 is not supported by cyanogen as you see here:
http://get.cm/?device=dream_sapphire
there are differences in kernel for 32A and 32B... thats why i'm asking.
i can't test it right now but i will do it later and i will report.
thanks for this release.

blizard80 said:
first, thanks for releasing this for the sapphire.
what i was saying is that CM7 is not supported by cyanogen as you see here:
http://get.cm/?device=dream_sapphire
there are differences in kernel for 32A and 32B... thats why i'm asking.
i can't test it right now but i will do it later and i will report.
thanks for this release.
Click to expand...
Click to collapse
But i can see gingerbread tree here https://github.com/CyanogenMod/android_device_htc_dream_sapphire/tree/gingerbread
I don't know why cm is not releasing gb builds ? please someone test it and tell me results !!

I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF

katurras said:
I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF
Click to expand...
Click to collapse
If you can flash CM7 you should be able to flash this!

katurras said:
I can not install ...
(status 7)
Instalation aborted
HTC Magic 32A Eng S-OFF
Click to expand...
Click to collapse
What hboot and/or radio?
I get that error, but updated the hboot and radio et voila!
It works
BTW I installed the hboot and radio from here
PD: I flashed the ROM but it does not boot.
I get many errors.....
D/AndroidRuntime( 145): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
I/AndroidRuntime( 145): Heap size: -Xmx16m
D/AndroidRuntime( 145): CheckJNI is OFF
W/dalvikvm( 145): Exception Ljava/util/regex/PatternSyntaxException; thrown whi
le initializing Landroid/graphics/Rect;
I/dalvikvm( 145): Rejecting re-init on previously-failed class Landroid/graphic
s/Rect; v=0x0
E/dalvikvm( 145): Class lookup Ljava/lang/NoClassDefFoundError; attempted while
exception Ljava/lang/ExceptionInInitializerError; pending
I/dalvikvm( 145): DALVIK THREADS:
I/dalvikvm( 145): (mutexes: tll=0 tsl=0 tscl=0 ghl=0 hwl=0 hwll=0)
I/dalvikvm( 145): "main" prio=5 tid=1 RUNNABLE
I/dalvikvm( 145): | group="main" sCount=0 dsCount=0 obj=0x40196198 self=0xce4
0
I/dalvikvm( 145): | sysTid=145 nice=0 sched=0/0 cgrp=default handle=-13450024
00
I/dalvikvm( 145): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 145): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 145):
E/dalvikvm( 145): VM aborting
I/DEBUG ( 79): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 79): Build fingerprint: 'tmobile/opal/sapphire/sapphire:2.2.1/FRG8
3/60505:user/release-keys'
I/DEBUG ( 79): pid: 145, tid: 145 >>> zygote <<<
I/DEBUG ( 79): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00
d
I/DEBUG ( 79): r0 fffffec4 r1 deadd00d r2 00000026 r3 00000000
I/DEBUG ( 79): r4 aca9e5c0 r5 0000ce40 r6 aca9e5c0 r7 00000000
I/DEBUG ( 79): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 79): ip aca9e720 sp bef529d0 lr afd19919 pc aca3fb66 cpsr 200
00030
I/DEBUG ( 79): #00 pc 0003fb66 /system/lib/libdvm.so (dvmAbort)
I/DEBUG ( 79): #01 pc 00064a52 /system/lib/libdvm.so
I/DEBUG ( 79): #02 pc 00064cee /system/lib/libdvm.so (dvmFindSyst
emClassNoInit)
I/DEBUG ( 79): #03 pc 00064d06 /system/lib/libdvm.so (dvmFindSyst
emClass)
I/DEBUG ( 79): #04 pc 0003f2ba /system/lib/libdvm.so (dvmThrowCha
inedException)
I/DEBUG ( 79): #05 pc 0003f31c /system/lib/libdvm.so (dvmThrowCha
inedExceptionWithClassMessage)
I/DEBUG ( 79): #06 pc 000628d4 /system/lib/libdvm.so
I/DEBUG ( 79): #07 pc 0006476a /system/lib/libdvm.so (dvmInitClas
s)
I/DEBUG ( 79): #08 pc 00046e2c /system/lib/libdvm.so
I/DEBUG ( 79): #09 pc 000585e8 /system/lib/libandroid_runtime.so
I/DEBUG ( 79): #10 pc 0005863a /system/lib/libandroid_runtime.so
(_Z34register_android_graphics_GraphicsP7_JNIEnv)
I/DEBUG ( 79): #11 pc 000357f6 /system/lib/libandroid_runtime.so
I/DEBUG ( 79): #12 pc 0003582c /system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime8startRegEP7_JNIEnv)
I/DEBUG ( 79): #13 pc 000358f6 /system/lib/libandroid_runtime.so
(_ZN7android14AndroidRuntime5startEPKcb)
I/DEBUG ( 79): #14 pc 00008ca2 /system/bin/app_process
I/DEBUG ( 79): #15 pc 000153e0 /system/lib/libc.so (__libc_init)
I/DEBUG ( 79):
I/DEBUG ( 79): code around pc:
I/DEBUG ( 79): aca3fb44 2006447a ecc8f7d1 20004c09 edf0f7d1
I/DEBUG ( 79): aca3fb54 447c4808 6bdb5823 d0002b00 49064798
I/DEBUG ( 79): aca3fb64 700a2226 ee5cf7d1 000435c5 00045183
I/DEBUG ( 79): aca3fb74 0005ea66 fffffec4 deadd00d b510b40e
I/DEBUG ( 79): aca3fb84 4c0a4b09 b083447b aa05591b ca026b5b
I/DEBUG ( 79):
I/DEBUG ( 79): code around lr:
I/DEBUG ( 79): afd198f8 447b4a0d 589cb083 90012600 686768a5
I/DEBUG ( 79): afd19908 220ce008 2b005eab 1c28d003 47889901
I/DEBUG ( 79): afd19918 35544306 d5f43f01 2c006824 b003d1ee
I/DEBUG ( 79): afd19928 bdf01c30 00028c26 ffffff88 1c0fb5f0
I/DEBUG ( 79): afd19938 b0871c3d a9044355 1c16ac01 604d9004
I/DEBUG ( 79):
I/DEBUG ( 79): stack:
I/DEBUG ( 79): bef52990 00000000
I/DEBUG ( 79): bef52994 00000000
I/DEBUG ( 79): bef52998 afd4372c
I/DEBUG ( 79): bef5299c afd436d8
I/DEBUG ( 79): bef529a0 00000000
I/DEBUG ( 79): bef529a4 afd19919 /system/lib/libc.so
I/DEBUG ( 79): bef529a8 00000000
I/DEBUG ( 79): bef529ac afd18985 /system/lib/libc.so
I/DEBUG ( 79): bef529b0 00000000
I/DEBUG ( 79): bef529b4 0005ea66
I/DEBUG ( 79): bef529b8 0000ce40
I/DEBUG ( 79): bef529bc aca9e5c0
I/DEBUG ( 79): bef529c0 00000000
I/DEBUG ( 79): bef529c4 afd189e3 /system/lib/libc.so
I/DEBUG ( 79): bef529c8 df002777
I/DEBUG ( 79): bef529cc e3a070ad
I/DEBUG ( 79): #00 bef529d0 aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef529d4 aca64a57 /system/lib/libdvm.so
I/DEBUG ( 79): #01 bef529d8 41d1dd8d
I/DEBUG ( 79): bef529dc 41d5b7db
I/DEBUG ( 79): bef529e0 00080f40
I/DEBUG ( 79): bef529e4 aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef529e8 000001b4
I/DEBUG ( 79): bef529ec 00000000
I/DEBUG ( 79): bef529f0 00000000
I/DEBUG ( 79): bef529f4 00000000
I/DEBUG ( 79): bef529f8 00000000
I/DEBUG ( 79): bef529fc aca85ffb /system/lib/libdvm.so
I/DEBUG ( 79): bef52a00 00080f40
I/DEBUG ( 79): bef52a04 00000000
I/DEBUG ( 79): bef52a08 0000ce40
I/DEBUG ( 79): bef52a0c aca64cf3 /system/lib/libdvm.so
I/ServiceManager( 76): service 'media.camera' died
I/ServiceManager( 76): service 'media.audio_policy' died
I/ServiceManager( 76): service 'media.audio_flinger' died
I/ServiceManager( 76): service 'media.player' died
I/Netd ( 147): Netd 1.0 starting
I/ ( 146): ServiceManager: 0xad50
I/HTC Acoustic( 146): libhtc_acoustic.so version 1.0.1.1.
E/HTC Acoustic( 146): Fail to open /system/etc/AudioPara_VODA-Spain.csv -1.
E/HTC Acoustic( 146): Fail to open /system/etc/AudioPara4.csv -1.
E/HTC Acoustic( 146): read audio para from file failed -1
E/AudioHardwareMSM72XX( 146): Could not set acoustic parameters to share memory
: -1
D/AudioHardwareMSM72XX( 146): mNumSndEndpoints = 13
D/AudioHardwareMSM72XX( 146): BT MATCH HANDSET
D/AudioHardwareMSM72XX( 146): BT MATCH SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH BT
D/AudioHardwareMSM72XX( 146): BT MATCH CARKIT
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_FULL
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_VCO
D/AudioHardwareMSM72XX( 146): BT MATCH TTY_HCO
D/AudioHardwareMSM72XX( 146): BT MATCH NO_MIC_HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH FM_HEADSET
D/AudioHardwareMSM72XX( 146): BT MATCH HEADSET_AND_SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH FM_SPEAKER
D/AudioHardwareMSM72XX( 146): BT MATCH CURRENT
D/AudioHardwareInterface( 146): setMode(NORMAL)

[S4][DEVs only] Zoe development

Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> very important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz

pirlano said:
Using this mod: http://forum.xda-developers.com/showthread.php?t=2436347
we are currently stuck here (no front camera and zoom bug), enabling front camera we got this:
Code:
[COLOR="Red"]E/ ( 274): [AWB Calibration] read fuse ID fail
E/mm-camera( 274): [sensor_getVersion] get version fail
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL[/COLOR]
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
D/Vold ( 245): Receive camera burst event
E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
W/S_CameraController( 4045): OIS is not supported.
W/S_CameraController( 4045): Video slow motion is not supported.
W/S_CameraController( 4045): Video Stabilization is not supported.
W/S_CameraController( 4045): Video 720p 60fps is not supported.
W/S_CameraController( 4045): Video HDR is not supported.
W/S_CameraController( 4045): Photo HDR is not supported.
E/S_CameraController( 4045): SupportedList.FlashMode == null
W/S_ZoeController( 4045): exitZoeMode() - Zoe mode is not entered
D/Property( 4045): [ICaptureResolutionManager.PhotoResolution] PHOTO_16_9_3264x1840(3264x1840) -> PHOTO_4_3_640x480(640x480)
D/Property( 4045): [ICaptureResolutionManager.VideoResolution] QHD(960x544) -> VGA(640x480)
E/S_CameraController( 4045): not support FlashMode !!
E/QCameraHWI_Parm( 260): Video HDR mode is not supported for this sensor
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): setVideoMode is not supported if PHOTO MODE
W/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::captureModeInitConfig(): other capture mode 1
[COLOR="Red"]E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setFocusMode(const android::CameraParameters&):Could not look up str value
E/QCameraHWI_Parm( 260): Invalid focus mode value: continuous-picture[/COLOR] [COLOR="Blue"]-> need framework fix, but it's not a big problem[/COLOR]
E/QCameraHWI_Parm( 260): android::status_t android::QCameraHardwareInterface::setParameters(const android::CameraParameters&): 2171, rc = -22
D/Vold ( 245): Receive camera burst event
[COLOR="Red"]E/mm-camera( 274): MCTL_COMPID_ACTUATOR handle is NULL
E/S_CameraController( 4045): setParameters exception[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
E/mm-camera( 274): camif_client_set_params: camif has associated with obj mask 0x1
E/mm-camera( 274): config_MSG_ID_RESET_ACK CAMIF_PARAMS_ADD_OBJ_ID failed -1
[COLOR="Red"]F/libc ( 274): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 4116 (mm-qcamera-daem)[/COLOR][COLOR="Blue"] -> i think it's crashing because of other problems[/COLOR]
I/DEBUG ( 257): debuggerd: 2013-09-20 03:00:40
I/DEBUG ( 257): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 257): Build fingerprint: 'htc/htc_europe/ville:4.2.2/JDQ39/240250.1:user/release-keys'
I/DEBUG ( 257): Revision: '3'
I/DEBUG ( 257): pid: 274, tid: 4116, name: mm-qcamera-daem >>> /system/bin/mm-qcamera-daemon <<<
....
I/DEBUG ( 257): backtrace:
I/DEBUG ( 257): #00 pc 00000000 <unknown>
I/DEBUG ( 257): #01 pc 0005ce0d /system/lib/liboemcamera.so
I/DEBUG ( 257): #02 pc 0002484d /system/lib/liboemcamera.so
I/DEBUG ( 257): #03 pc 0000e4b8 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 257): #04 pc 0000dba4 /system/lib/libc.so (pthread_create+160)
I/DEBUG ( 257):
I/DEBUG ( 257): stack:
I/DEBUG ( 257): 4078e800 0003eed4
I/DEBUG ( 257): 4078e804 4043ce21 /system/lib/liboemcamera.so (vfe_config_mode+732)
I/DEBUG ( 257): 4078e808 00000005
I/DEBUG ( 257): 4078e80c 404a32c0
I/DEBUG ( 257): 4078e810 00000001
I/DEBUG ( 257): 4078e814 4078e88c [stack:4116]
I/DEBUG ( 257): 4078e818 00000000
I/DEBUG ( 257): 4078e81c 407b738c [stack:4116]
I/DEBUG ( 257): 4078e820 40436179 /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e824 4043909d /system/lib/liboemcamera.so
I/DEBUG ( 257): 4078e828 40438e7d /system/lib/liboemcamera.so
...
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 4144): Cannot init Gesture library[/COLOR] [COLOR="Blue"]-> missing libs? not a big problem btw[/COLOR]
W/S_OperationTimeoutController( 4045): [Timeout] Name : Start preview
W/S_OperationTimeoutController( 4045): [Timeout] Start time : 1379638840004
W/S_OperationTimeoutController( 4045): [Timeout] Timeout : 5000
W/S_OperationTimeoutController( 4045): [Timeout] Call-back executor : [email protected]
W/S_HTCCamera( 4045): notifyCameraThreadBlocked(BlockedInCameraDriver)
W/S_HTCCamera( 4045): onCameraThreadBlocked(BlockedInCameraDriver)
W/S_AutoFocusController( 4045): unlockAutoFocus() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoExposure() - Null handle
W/S_ImageSettingsController( 4045): unlockAutoWhiteBalance() - Null handle
W/S_HTCCamera( 4045): onPause() - mIsUIReady = false
W/AudioService( 920): stream was not muted by this client
E/AudioService( 920): Could not get client death handler for stream: 5
W/S_HTCCamera( 4045): onPause mIdle is false
W/S_HTCCamera( 4045): OnPause - Freeze UI !!!
W/S_HTCCamera( 4045): doOnPause() - start
W/S_HTCCamera( 4045): stopAccelerometer() - isAccelerometerStarted = false
W/S_HTCCamera( 4045): OnPause - hide UI, set mMainLayout invisible
W/S_HTCCamera( 4045): doOnPause() - end
[COLOR="Red"]E/mm-libcamera2( 260): mm_camera_stream_fsm_reg: ioctl VIDIOC_STREAMON failed: rc=-1
E/mm-libcamera2( 260): mm_camera_ch_fn: Failed in STREAM ON
E/mm-libcamera2( 260): mm_camera_action_start: rc=-1[/COLOR] [COLOR="Blue"]-> i don't think it's too much important[/COLOR]
E/QCameraHWI_Still( 260): android::status_t android::QCameraStream_Snapshot::startStreamZSL(): Failure starting ZSL stream
[COLOR="Red"]E/mm-camera( 4144): qcamsvr_find_mctl_inst: no match for mctl_id = 1
E/mm-camera( 4144): qcamsvr_process_server_node_event: MSM_V4L2_* - cannot find mctl, id = 1[/COLOR] [COLOR="Blue"]-> it should be important[/COLOR]
is there a dev that already encountered this problem, and can help us?
@ImagioX1 @E.Cadro @olvrick @Turge @Zarboz
Click to expand...
Click to collapse
grep is your friend
MCTL_COMPID_ACTUATOR

Zarboz said:
grep is your friend
MCTL_COMPID_ACTUATOR
Click to expand...
Click to collapse
i know, the problem is in liboemcamera.so, mctl_init & sensor_init are changed, and i'm looking at this
i was just asking if One XL devs already solved this problem in the past or not, or if you have some hints
In One S liboemcamera there is one only "MCTL_COMPID_ACTUATOR handle is NULL" reference:
.rodata:000BBAEA aMctl_compid__0 DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
In One liboemcamera there are three reference:
.rodata:000AAB54 aMctl_compid_ac DCB "MCTL_COMPID_ACTUATOR handle is NULL",0xA,0 ; DATA XREF: sub_1F240+A64o
.rodata:000C650C aSMctl_compid_0 DCB "%s MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
.rodata:000C7EF4 aSMctl_compid_2 DCB "%s: MCTL_COMPID_ACTUATOR handle is NULL",0xA,0
the one causing the error is the first
in dmesg, error happens beetween this two lines:
<6>[ 141.009064] c1 4731 [CAM] mt9v113_ioctl, cfgtype = 10
(reached with original cam and zoe mod)
it's in drivers/media/video/msm/sensor/mt9v113_v4l2.c
function: int mt9v113_sensor_config(void __user *argp)
<6>[ 141.009430] c1 4731 [CAM] vfe32_proc_general: cmdID = START
(start is not reached with Zoe mod)
it's in drivers/media/video/msm/vfe/msm_vfe32.c
function: static int vfe32_proc_general(
struct msm_cam_media_controller *pmctl,
struct msm_isp_cmd *cmd,
struct vfe32_ctrl_type *vfe32_ctrl)

Will be great to be ported this feature and new [ROM] MaximusHD 10.0.0 - 4.2.2 Sense 5 -> will be the best one for ONE S
Will wait this with big impatience to be fixed and work of my favorite phone - One S
Thanks

i'm using this tutorials to try to debug liboemcamera.so:
http://forum.xda-developers.com/showthread.php?t=2050393
http://forum.xda-developers.com/showthread.php?t=1374345
but i'm currently stuck here:
http://forum.xda-developers.com/showpost.php?p=45827106&postcount=13
EDIT: solved few problem
but now, i'm stuck, again
ptrace: I/O error.

If someone want to try to debug native android library using IDA Pro...
[console 1] -> one time only
adb push the gdbserver from ndk to data/local/tmp
adb shell su
adb chmod 755 gdbserver
[console 2] -> don't forget it or debug client will not connect!
adb forward tcp:1111 tcp:1111
[console 3] -> start binary you want to debug (or binary that load library that you want to debug liboemcamera.so in my case, using mm-qcamera-app) -> leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (this is to disable ASLR, that cause library to be loaded at random address)
cd system/bin
./mm-qcamera-app
1 or 2
[console 4]->leave it opened
adb shell
su
echo 0 > /proc/sys/kernel/randomize_va_space (just to be sure)
ps (look at PID of mm-qcamera-app)
cd data/local/tmp
./gdbserver --attach :1111 PID_NUMBER_of_mm-qcamera-app
[console 5]
(adb pull system/lib and system/bin here->C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin)
(start gdb from ndk from command line)
gdb.exe
(gdb) set height 0
(gdb) set solib-search-path ./
(gdb) directory C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64/bin
(gdb) target remote 127.0.0.1:1111
Remote debugging using 127.0.0.1:1111
0x4005fe48 in ?? ()
(gdb) info sharedlibrary
Reading symbols from C:/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/preb
uilt/windows-x86_64/bin/mm-qcamera-app...done.
WARNING: no debugging symbols found in C:/android-ndk-r9/toolchains/arm-linux-an
droideabi-4.6/prebuilt/windows-x86_64/bin/mm-qcamera-app.
Either the binary was compiled without debugging information
or the debugging information was removed (e.g., with strip or strip -g).
Debugger capabilities will be very limited.
For further information: http://wiki/Main/GdbFaq#No_debugging_symbols_found
From To Syms Read Shared Object Library
0x40003240 0x4000b978 No C:/android-ndk-r9/toolchains/arm-linux-andro
ideabi-4.6/prebuilt/windows-x86_64/bin/system/bin/linker
0x40055940 0x40085d0c No libc.so
0x400a07f4 0x400a0998 No libstdc++.so
0x400a4e80 0x400b5164 No libm.so
0x40044180 0x40045d44 No liblog.so
0x40027a18 0x4003059c No libcutils.so
0x4025f6a0 0x40263008 No libgemini.so
0x4022f578 0x402543cc No libmmjpeg.so
0x400ca8b0 0x40161250 No liboemcamera.so
0x40296638 0x40296b50 No libmmstillomx.so
0x402a1494 0x402a1630 No libimage-omx-common.so
0x4029a658 0x4029e414 No libimage-jpeg-enc-omx-comp.so
0x4028a284 0x40291a5c No libmmcamera_interface2.so
(gdb)
NOW you have information about library base address! Nice! Copy and paste these information
Now you can just use CTRL+C on console 4, and execute instruction for console 4 again, so we can debug using IDA this time
(IDA)
for new versions->Debugger, Debugger option, option, uncheck "Use hardware temporary breakpoints"
Debugger,Switch Debugger,Remote GDB debugger and check Set as default debugger
Debugger, Process option, applicazion path (../system/bin/blabla), input file (same or ../system/lib/libblabla.so if debugging lib), Hostname: localhost, Port 1111 (or select youself, you will need to use it for all commands) and check "Set as default network setting"
Now load the file you want to debug
File->Open->liboemcamera.so in my case->Ok/Load->Check "Manual load" from the popup->OK->Input 0:400ca8b0 in my case (base address)->Load all section or section that you need->Yes
Wait for autoanalysis, and do some static analysis by yourself, set some breakpoint, etc,etc
When you are ready to debug: Debugger,Start process, Yes
TADA! The ****ing IDA+gdb should now be able to do step by step debug, but i got a ****ing ptrace: I/O error.

using HTC One Mini libs + updating kernel camera parts from HTC One Mini source, front camera is working good, but rear camera quality is really really bad, need a fix
i'll post an alpha mod soon
zoom bug (green rectangle on jpeg) is still present
EDIT: quality became bad because of wrong Auto White Balance not working good with M4 libs, so with a clean installation it will still working good, but if you came from Zoe fix from Magio, you will need to go back to stock libs/camera apps or do a fresh installation
zoe is working but need camera.apk modding to force it (it should be easy, since apk can be decompiled almost to source code)

install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side

pirlano said:
install over a stock camera
kernel with M4 kernel camera patch: http://www.4shared.com/zip/CRNRFvCD/fabane_ville_m4_cam_26_09_13_v.html
test M4 libs+camera: http://www.4shared.com/zip/wW302ToJ/FixedZoeMagioV4_M4_ville.html
front facing camera is working, zoe needs to be enabled camera.apk side
Click to expand...
Click to collapse
Well this work over your old kernel to make the one xl roms boot
Sent from my HTC One S using Tapatalk 2

yes, camera part only is changed, tomorrow i'll work on camera.apk

pirlano said:
yes, camera part only is changed, tomorrow i'll work on camera.apk
Click to expand...
Click to collapse
Ok cool need any help send me a pm
Sent from my HTC One S using Tapatalk 2

Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app

razlack said:
Hey guys, I know this is still in development but when finished will it work with the Maximus Rom?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
the question is not "when", but, "if"
i'll start lessons next week, so i will be unable to continue
EDIT:
today, instead of looking at m4 camera.apk, i tryed to fix ffc with stock kernel and m7 libs, i think i have found the solution, don't know if it will work, but it's the better idea that i have found until now
EDIT2:
mt9v113 seems to be incompatible with m7 libs, cannot found a solution, we need an experienced arm hacker or hex-rays arm decompiler (if someone use it at work, license is too expensive for home users)
an ather way it's to create a mt9v113_act.c driver, but i think i'm not able to do that, and if it will work, but maybe a dummy one will work too, will try when i have time
for now the only way it's to use m4 libs, so camera.apk needs hacking (this is much more easy), i will try tomorrow
I'm also trying to understand what's causing the zoom bug...
also with both m4 and m7 libs (with kernel patches to make camera working) manual touch autofocus seems to be buggy with slow motion mode and with 60fps mode
and camera auto white balance need a fix, i'm starting to think that it's better to mod our stock camera, without zoe...****ing close source libs...

Unfortunately, Camera has stopped CM12s

CameraNext crashes on most ROMs I install. I am currently on a stock rom and still crashing. Normally I would just use another camera app but if it's fixable - awesome. Google Camera works fine.
I have attached 2 crash reports. I cannot generate the second one again, which it a bit odd.
Is there a fix? TIA
Kind regards
Benjamin
Android:
12.0 YNG1TAS17L
5.0.2
Camera
CameraNext
2.0.004
Crash 1
java.lang.RuntimeException: Media server died.
at com.android.camera.Y.onError(SourceFile:33)
at android.hardware.Camera$EventHandler.handleMessage(Camera.java:1195)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Crash 2
Build fingerprint: 'oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 10164, tid: 10181, name: Binder_2 >>> com.cyngn.cameranext <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 00000000 r1 ad32209c r2 00000025 r3 00000000
r4 a3018040 r5 b6ba5de1 r6 ad320080 r7 00002000
r8 adde7b54 r9 00000000 sl 00002000 fp adde7bf0
ip b6bb5ec0 sp adde7b38 lr b6ba5ea5 pc b6e261f8 cpsr a0000030
backtrace:
#00 pc 000981f8 /system/lib/libandroid_runtime.so (JNICameraContext::copyAndPost(_JNIEnv*, android::sp<android::IMemory> const&, int)+35)
#01 pc 00098353 /system/lib/libandroid_runtime.so (JNICameraContext:ostData(int, android::sp<android::IMemory> const&, camera_frame_metadata*)+102)
#02 pc 0001e995 /system/lib/libcamera_client.so (android::Camera::dataCallback(int, android::sp<android::IMemory> const&, camera_frame_metadata*)+54)
#03 pc 00022321 /system/lib/libcamera_client.so (android::BnCameraClient:nTransact(unsigned int, android:arcel const&, android:arcel*, unsigned int)+220)
#04 pc 00017fc5 /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android:arcel const&, android:arcel*, unsigned int)+60)
#05 pc 0001cf7b /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+582)
#06 pc 0001d09f /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+38)
#07 pc 0001d0e1 /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+48)
#08 pc 0002124b /system/lib/libbinder.so
#09 pc 0000ef11 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+112)
#10 pc 0005a62d /system/lib/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+72)
#11 pc 0000ea81 /system/lib/libutils.so
#12 pc 00013a1b /system/lib/libc.so (__pthread_start(void*)+30)
#13 pc 00011a0f /system/lib/libc.so (__start_thread+6)

* Cleared Data and Cache, no bacon.

I hit this bug constantly. For me, the camera is effectively unusable. I've also tried clearing cache &c.

My cameras have stopped too & I don't know how to remove or try better camera software pkg. If someone could help me to do this it would be great. Thankyou Currently running 1+1,
Resurrection Remix, 5.5.6 with slim0 gapps,+ latest cm12.1 nightly Don't have ear speaker on phone calls working either but I need my cameras back first.

wel for best results flash the K1 Color Os package in recovery.
amazing.
also you could install the A Better Camera app, its equally good if you know how to play with the light.
lastly, the Moto V3 camera port is superb..
u need to try all three to know which works best for u.
regards
---------- Post added at 01:38 PM ---------- Previous post was at 12:43 PM ----------
here are the links for the cams I use which are tested working on OP1 and LG G2 and Nexus 5.
superb apps..
COS Cam Port - http://d-h.st/gskk
here is the original thread of the port - http://forum.xda-developers.com/oneplus-one/themes-apps/coloros-camera-port-t3034148
Moto Cam port - http://d-h.st/SF8S
(remove - http://d-h.st/Prw9)
here is the original thread of the port - http://forum.xda-developers.com/android/apps-games/flashable-port-moto-camera-fullfilled-t3172783
all credits to the original devs, i am just sharing....
regards