Related
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
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
Intro
Code:
/* Last Time i got multiple Requests how to FIX Ril in CM9/CM10 Based Roms
/* Now, i figured out how to get the Mic working and how to port the
/* CM10/CM9 Based Roms, with extended explaining how to and
/* logcats with the problem what needs to be fixed!
/* This Thread tell you all Informations and will show Picture based
/* Informations also ;)
Now lets start ^^
Step 1
Its quietly easy:
-extract both Roms in two folders, like the base Rom (CM9/CM10 from your Device) in a Folder named Port and the (CM9/CM10 based) Rom from the Device from that u wanna port in a Folder like "Orig/Original"
Picture:
{
"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"
}
- Now delete the following Folders in "Port" Folder (the specific folders are placed in /system): /app ; /framework ; /fonts ; /media
Picture:
- Open both Folders once more and move the /app ; /framework ; /fonts ; /media folder from "Original/system" Folder in the "Port/system" Folder
Picture:
-Now u have the basic thing in it
Click to expand...
Click to collapse
Step 2
- now delete from the "Port/system/lib" Folder this File: android_runtime.so
- Now move the android_runtime.so from the "Original/system/lib" Folder in the "Port/system/lib" Folder ^^
Picture:
- Now u need to modify the build.prop (Notepad++)! Open both in Notepad+ and delete the "ro.build.description=
ro.build.fingerprint=" Line from the original build.prop!
- Open the build.prop from the "Original/system Folder" and copy the "ro.build.description=
ro.build.fingerprint=" Lines
- Now re-open the build.prop from the the "Port/system" Folder and paste the lines below "# Do not try to parse ro.build.description or .fingerprint" Line!
Picture:
Now save it
-Zip all Folders and Files in the "Port" Folder!
-Try to flash it and try to BOOT it ... (I think that it wont boot)
Click to expand...
Click to collapse
Step 3
I think it wont boot (U will see a long time the Bootanimation and nothing will happen)
Its just a lib related error:
Code:
F/libc ( 449): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 117): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 117): Build fingerprint: 'lge/thunderg/thunderg:2.3.3/GRI40/LG-P500-V20h.19D34B612E:user/release-keys'
I/DEBUG ( 117): pid: 449, tid: 449 >>> system_server <<<
I/DEBUG ( 117): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 117): r0 deadbaad r1 0000000c r2 00000027 r3 40000000
I/DEBUG ( 117): r4 00000000 r5 00000080 r6 4b048987 r7 be9f9778
I/DEBUG ( 117): r8 40813200 r9 00000006 10 46218e1c fp fffffe50
I/DEBUG ( 117): ip ffffffff sp be9f9740 lr 4001f377 pc 4001b7c2 cpsr 00000030
I/DEBUG ( 117): d0 3fe99999a0000000 d1 3ff0000000000000
I/DEBUG ( 117): d2 bebbbc6c1a570a20 d3 3f1155e54e7e8408
I/DEBUG ( 117): d4 bfb1be5a93a83e1d d5 4000000000000000
I/DEBUG ( 117): d6 4a066ec000000000 d7 000000344d520d0c
I/DEBUG ( 117): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 117): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 117): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 117): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 117): scr 80000010
I/DEBUG ( 117):
I/DEBUG ( 117): #00 pc 000177c2 /system/lib/libc.so
I/DEBUG ( 117): #01 pc 0000c658 /system/lib/libnativehelper.so (jniRegisterNativeMethods)
I/DEBUG ( 117):
I/DEBUG ( 117): code around pc:
I/DEBUG ( 117): 4001b7a0 1c2bd00c 2d00682d e027d1fb 2a0068da ..+.-h.-..'..h.*
I/DEBUG ( 117): 4001b7b0 4b16d004 447b2001 47906018 22274814 ...K. {D.`.G.H'"
I/DEBUG ( 117): 4001b7c0 70022580 ef6ef7f4 f7f62106 aa01e80c .%.p..n..!......
I/DEBUG ( 117): 4001b7d0 05692400 60546091 20061c11 f7f59401 .$i..`T`... ....
I/DEBUG ( 117): 4001b7e0 a905ebc8 20022200 ebd0f7f5 ef5af7f4 .....". ......Z.
I/DEBUG ( 117):
I/DEBUG ( 117): code around lr:
I/DEBUG ( 117): 4001f354 4b0db5f0 447bb083 681c2600 68a59001 ...K..{D.&.h...h
I/DEBUG ( 117): 4001f364 e0086867 5ea8220c dd032800 99011c28 gh...".^.(..(...
I/DEBUG ( 117): 4001f374 43064788 3f013554 6824d5f4 d1ee2c00 .G.CT5.?..$h.,..
I/DEBUG ( 117): 4001f384 1c30b003 46c0bdf0 0002818e 1c0fb5f0 ..0....F........
I/DEBUG ( 117): 4001f394 b0891c3d a9064355 604d9103 90064914 =...UC....M`.I..
I/DEBUG ( 117):
I/DEBUG ( 117): memory map around addr deadbaad:
I/DEBUG ( 117): be9da000-be9fa000 [stack]
I/DEBUG ( 117): (no map for address)
I/DEBUG ( 117): (no map above)
I/DEBUG ( 117):
I/DEBUG ( 117): stack:
I/DEBUG ( 117): be9f9700 00000002
I/DEBUG ( 117): be9f9704 7b4c2d14
I/DEBUG ( 117): be9f9708 40047774 /system/lib/libc.so
I/DEBUG ( 117): be9f970c 4004c8bc
I/DEBUG ( 117): be9f9710 00000000
I/DEBUG ( 117): be9f9714 4001f377 /system/lib/libc.so
I/DEBUG ( 117): be9f9718 4b04753a /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f971c 4001e0dd /system/lib/libc.so
I/DEBUG ( 117): be9f9720 ffffffff
I/DEBUG ( 117): be9f9724 00000000
I/DEBUG ( 117): be9f9728 00000000
I/DEBUG ( 117): be9f972c 4b048987 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9730 be9f9778 [stack]
I/DEBUG ( 117): be9f9734 4001e4f5 /system/lib/libc.so
I/DEBUG ( 117): be9f9738 df0027ad
I/DEBUG ( 117): be9f973c 00000000
I/DEBUG ( 117): #00 be9f9740 00000002
I/DEBUG ( 117): be9f9744 00000100
I/DEBUG ( 117): be9f9748 4b045169 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f974c 7b4c2d14
I/DEBUG ( 117): be9f9750 0000002b
I/DEBUG ( 117): be9f9754 fffffbdf
I/DEBUG ( 117): be9f9758 0000f2c8 [heap]
I/DEBUG ( 117): be9f975c 40849fdd /system/lib/libdvm.so
I/DEBUG ( 117): be9f9760 0000f2c8 [heap]
I/DEBUG ( 117): be9f9764 401d665b /system/lib/libnativehelper.so
I/DEBUG ( 117): #01 be9f9768 40849fdd /system/lib/libdvm.so
I/DEBUG ( 117): be9f976c 401d665b /system/lib/libnativehelper.so
I/DEBUG ( 117): be9f9770 4b04aac4 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9774 00000004
I/DEBUG ( 117): be9f9778 0000f2c8 [heap]
I/DEBUG ( 117): be9f977c 74800019
I/DEBUG ( 117): be9f9780 00000028
I/DEBUG ( 117): be9f9784 4b048987 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9788 0000f2c8 [heap]
I/DEBUG ( 117): be9f978c 00012830 [heap]
I/DEBUG ( 117): be9f9790 00000000
I/DEBUG ( 117): be9f9794 4b04522d /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f9798 00012b88 [heap]
I/DEBUG ( 117): be9f979c 4b0473c1 /system/lib/libandroid_servers.so
I/DEBUG ( 117): be9f97a0 001fc710 [heap]
I/DEBUG ( 117): be9f97a4 00012830 [heap]
I/DEBUG ( 117): be9f97a8 00000000
I/DEBUG ( 117): be9f97ac 4b0473ef /system/lib/libandroid_servers.so
D/Zygote ( 408): Process 449 terminated by signal (11)
I/Zygote ( 408): Exit zygote because system server (449) has terminated
What is easy to fix: Replace the android_servers.so in "Port/system/lib" Folder with the one in Original/system/lib Folder
Picture:
Now re-zip all Files and Folders in the /Port Folder and it should boot now after u flashed it!
Click to expand...
Click to collapse
Step 4
Maybe u get always a Phone FC Error or no one can hear u while u are calling someone! :silly:
Thats an Ril related error
Now u think, what should i do, right?
Hmm u need to decompile both framework.jar´s from "Port/system/framework/" and the one from ur base zip like CM9 or CM10 from your device!
u need apktool for that, its not related for framework.jar´s when u have a gingerbread apktool (1.4.3) or an ics one! its only related that u know how to decompile, recompile and repack the jar (winrar)
rename the framework.jar from your CM9 or CM10 (your Device, NOT FROM THE "PORT" Folder) to framework-orig.jar and put it in apktool folder!
Place the framework.jar from the "Port" folder also in the apktool folder
Now 2 simple commands in apktool cmd window:
Code:
apktool d framework-orig.jar
and
Code:
apktool d framework.jar
let it decompile and close the window only when there is a word: "Done"!
Now open framework.jar.out folder and framework-orig.jar.out folder, yet open in both folders: /smali/com/android/internal/telephony ^^
copy all files which start with RIL and end with .smali and placed in the framework-orig.jar.out/smali/com/android/internal/telephony Folder and put it in the framework.jar.out/smali/com/android/telephony Folder (replace them all)
Some Devices have in build.prop a specific Ril Class Path! Mine is: "ro.telephony.ril_class=JellaxyRIL" urs can variate after the "="! If this is the case, look once more in framewok-orig.jar.out/smali/com/android/internal/telephony and search for "JellaxyRIL" or how ur´s is called after "=" in the RIL Class
Now copy the "JellaxyRIL.smali" (Its the one from my base Rom) or whatever in the other Folder "framework.jar.out/smali/com/android/telephony" !
Now re-compile it:
Code:
apktool b framework.jar.out
let it compile, it takes a few minutes (depends on ur PC Speed)
Now open the framework.jar from "apktool" Folder with WinRAR
and move the classes.dex from "apktool/framework.jar.out/build/apk in the opened WinRAR Window and let it re-pack, now close the Windows (WinRAR) and move the new framework.jar from /apktool in "Port/system/framework"
Voila, Mic Working and no more Phone FC´s!
If u have a problem with it, pm me with the following files:
framework.jar (from the Rom u wanna port), framework.jar (from your base CM10 or CM9) and your build.prop (from ur base CM10 or CM9)
Click to expand...
Click to collapse
Step 6
May barebone your Rom will improve the stability
Some apps u can remove:
*QuickSearchBox.apk
*STK.apk
*GoogleMail.apk (Mail.apk is still included, so why there should be 2 Mail Apps )
*Term.apk (Terminal Emulator)
*Voice Dialer (Its not the phone and takes also no effect to it)
*VideoEditor.apk (WTF who wants to cut Videos over android 0.o
oh i forgot about that step:
move from "Port/system/etc/permissions" Folder, all Files to "Original/system/etc/permissions" Folder (Replace them) and move them all back to "Port/system/etc/permissions" Folder! One more Thing: if Superuser isn´t working, take the "su File from "Original/system/xbin" and move it to "Port/system/xbin" Folder and replace it!
Click to expand...
Click to collapse
In case the Rom wont boot or u cant do any step bcoz u wont understand it:
My support: Only over Facebook
Click to expand...
Click to collapse
For the reply "Rom wont boot! Pls help me ", i wont read it!
U need to add the related things i provide now:
Code:
Logcat:
Rom (u wanna port):
Rom Link:
Base Rom:
Base Rom Link:
Your Device:
Click to expand...
Click to collapse
nice guide. gonna try this sometimes
Syfer_Fever said:
nice guide. gonna try this sometimes
Click to expand...
Click to collapse
can u explain me if i want to port CM 10 from mini to my fit so what do i do.
which is the port rom and original rom.
totally confused.
don't understand base rom and etc stuffs. lil explanation need. plz help
creativeguy09 said:
can u explain me if i want to port CM 10 from mini to my fit so what do i do.
which is the port rom and original rom.
totally confused.
don't understand base rom and etc stuffs. lil explanation need. plz help
Click to expand...
Click to collapse
i think you just replace "usr" folder from cm10-beni to ROM you wanna port and replace the kernel with ours, if the ROM dosen't boot try Step 2
if you still confuse maybe you can ask the OP
Syfer_Fever said:
i think you just replace "usr" folder from cm10-beni to ROM you wanna port and replace the kernel with ours, if the ROM dosen't boot try Step 2
if you still confuse maybe you can ask the OP
Click to expand...
Click to collapse
IN FOLDER PORT Put in the Rom from your device! and in ORIGINAL the Rom u wanna port
To Syfer_Fever: Should i ad a video that u understand it? :silly:
It takes no effect if u replace the /usr folder with the same /usr folder!
DQiB said:
IN FOLDER PORT Put in the Rom from your device! and in ORIGINAL the Rom u wanna port
To Syfer_Fever: Should i ad a video that u understand it? :silly:
It takes no effect if u replace the /usr folder with the same /usr folder!
Click to expand...
Click to collapse
video? for me? for what?
to get soft key button works because mini don't have soft button
hi dqib can you make guide how to port stock based rom from other device like gio,y etc...waiting for guide
Syfer_Fever said:
video? for me? for what?
to get soft key button works because mini don't have soft button
Click to expand...
Click to collapse
last time i tell it u!
All files out of /app ,/framework ,/media ,/fonts
are completely the same (BCOZ YOU USE THE LATEST CM9 OR CM10 for GALAXY FIT and not the ROM FROM GALAXY MINI )
DQiB said:
last time i tell it u!
All files out of /app ,/framework ,/media ,/fonts
are completely the same (BCOZ YOU USE THE LATEST CM9 OR CM10 for GALAXY FIT and not the ROM FROM GALAXY MINI )
Click to expand...
Click to collapse
lol relax "mr.all know everything" you are using capslock seems your childish is out
don't be arrogant, you should tell people who don't know nicely
yes my friend yes sir if u will make a video i would be really thankful and grateful to u. i'm following your instructions but a video would be helpful. great work thanks.
by the way as a personal thought which is the best rom to use for fit. i'm using CM7 currently original one.
I make a kitchen for porting ...
It should be easier for u
Sent from my GT-S5660 using xda app-developers app
? Sorry what u saying kitchen? I don't understand
Sent from my GT-S5670 using xda app-developers app
it helps u t odo it! (porting)
U only need to edit the build.prop and zip the rest ^^
(RIL Fix also, thats manual) :laugh:
Please give the link of working kitchen for our Samsung galaxy fit and apktool also. I have a kitchen file but it's only for HTC roms
Sent from my GT-S5670 using Tapatalk 2
---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------
DQiB said:
I make a kitchen for porting ...
It should be easier for u
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
Please give the link of working kitchen for our Samsung galaxy fit and apktool also. I have a kitchen file but it's only for HTC roms
Sent from my GT-S5670 using Tapatalk 2
everthing I read refers to load adb driver.
what do you do if you dont have the driver?
adb drivers == nothing found
any attempt with adb
error: device not found
trying to root Audiosonic 7"
every program refers to loading the adb driver no adb driver to load
I've rooted other devices the easy way, someone advises howto
I WOULD like to learn how to root the device, without a know adb driver.
can someone point me to the RIGHT information to read or do please
android 4.0.4
Kernal version :
3.0.36 +
[email protected] #76
Build number :
RK292X_ANDROID4.0.4-SDK-v1.00.00
rk2926sdk-eng 4.0.4 IMM760 20121215.042649 release-keys
There is a way to make your device compatible with adb, even if you can't find driver for it. Below is how I made my old Creative Ziio compatible with adb:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add the folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart adb server
You can get vid&pid from the DeviceManager.
knutson said:
There is a way to make your device compatible with adb, even if you can't find driver for it. Below is how I made my old Creative Ziio compatible with adb:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add the folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart adb server
You can get vid&pid from the DeviceManager.
Click to expand...
Click to collapse
Very informative post. That's what we like to see
well the audiosonic in normal mode shows up as T-07B in recovery it shows as rk2928sdk
added the vid/pid I got from each (different)
unmerged/merged
nomal mode adb devices finds nothing
recovery mode adb devices finds 0123456789ABCDEF RECOVERY
tried adb shell in recovery and got exec '/system/bin/sh' folder or file not found
ok need a break and try attacking this again
singleadbinterface
compositeinterface
best to use both? 1? looking through android_winusb.ini seem like a mixed bag some both, one etc
Yes, both singleadbinterface and compositeinterface are needed. Also do not forget to modify adb_usb.ini.
Also, make sure that USB debugging is enabled on your device, note that this option should be changed only when device is disconnected from USB.
To check that adb is working,try to install something with
adb install ./some_application.apk
knutson said:
Yes, both singleadbinterface and compositeinterface are needed. Also do not forget to modify adb_usb.ini.
Also, make sure that USB debugging is enabled on your device, note that this option should be changed only when device is disconnected from USB.
To check that adb is working,try to install something with
adb install ./some_application.apk
Click to expand...
Click to collapse
so, just to be specific, and not presuming
to root the device I should be in normal mode or recovery? (last 2 roots I did was in normal mode but they where design root methods)
if normal mode, how can you install if the device not found (which device)
device set and confirmed in debugging mode
thanks for the help, even just confirming things for me
just to advised
I tried installing an app
in normal mode error device not found---- waiting on device
in recovery mode seemd to load but got exec '/system/bin/sh' folder or file not found (interestingly enough, got twice)
so either still a driver problem or need to solve the error (god i've been at this for a few days now)
wolfbite.aus said:
just to advised
I tried installing an app
in normal mode error device not found---- waiting on device
in recovery mode seemd to load but got exec '/system/bin/sh' folder or file not found (interestingly enough, got twice)
so either still a driver problem or need to solve the error (god i've been at this for a few days now)
Click to expand...
Click to collapse
Are you mounting /system partition with ADB prior to trying to push files to the partition?
cant mount /system
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
is there a sh file somewhere I can push and try???
but adb pull /system gave me bin/busybox
adb pull /data gave me
But each clue you give me gives new ideas (mount got me looking into push/pull
seems I can
adb push so found a su and did adb push /system/bin/su
seemed to work
# adb push su /system/bin/
4576 KB/s (91980 bytes in 0.019s)
then tried
# adb pull /system/
pull: building file list...
pull: /system/bin/busybox -> ./bin/busybox
pull: /system/bin/su -> ./bin/su
2 files pulled. 0 files skipped.
2443 KB/s (1899036 bytes in 0.758s)
adb pull /
pull: building file list...
skipping special file 'rknand_sys_storage'
skipping special file 'ppp'
skipping special file 'network_throughput'
skipping special file 'network_latency'
skipping special file 'cpu_dma_latency'
skipping special file 'rk29-ipp'
skipping special file 'xt_qtaguid'
skipping special file 'galcore'
skipping special file 'binder'
skipping special file 'device-mapper'
skipping special file 'i2c-dev'
skipping special file 'alarm'
skipping special file 'uinput'
skipping special file 'keychord'
skipping special file 'usb_accessory'
skipping special file 'mtp_usb'
skipping special file 'android_adb'
skipping special file 'pmem'
skipping special file 'ion'
skipping special file 'fuse'
skipping special file 'ashmem'
skipping special file 'verifyid'
skipping special file 'vcsa1'
skipping special file 'vcs1'
skipping special file 'vcsa'
skipping special file 'vcs'
skipping special file 'ptmx'
skipping special file 'tty63'
skipping special file 'tty62'
skipping special file 'tty61'
skipping special file 'tty60'
skipping special file 'tty59'
skipping special file 'tty58'
skipping special file 'tty57'
skipping special file 'tty56'
skipping special file 'tty55'
skipping special file 'tty54'
skipping special file 'tty53'
skipping special file 'tty52'
skipping special file 'tty51'
skipping special file 'tty50'
skipping special file 'tty49'
skipping special file 'tty48'
skipping special file 'tty47'
skipping special file 'tty46'
skipping special file 'tty45'
skipping special file 'tty44'
skipping special file 'tty43'
skipping special file 'tty42'
skipping special file 'tty41'
skipping special file 'tty40'
skipping special file 'tty39'
skipping special file 'tty38'
skipping special file 'tty37'
skipping special file 'tty36'
skipping special file 'tty35'
skipping special file 'tty34'
skipping special file 'tty33'
skipping special file 'tty32'
skipping special file 'tty31'
skipping special file 'tty30'
skipping special file 'tty29'
skipping special file 'tty28'
skipping special file 'tty27'
skipping special file 'tty26'
skipping special file 'tty25'
skipping special file 'tty24'
skipping special file 'tty23'
skipping special file 'tty22'
skipping special file 'tty21'
skipping special file 'tty20'
skipping special file 'tty19'
skipping special file 'tty18'
skipping special file 'tty17'
skipping special file 'tty16'
skipping special file 'tty15'
skipping special file 'tty14'
skipping special file 'tty13'
skipping special file 'tty12'
skipping special file 'tty11'
skipping special file 'tty10'
skipping special file 'tty9'
skipping special file 'tty8'
skipping special file 'tty7'
skipping special file 'tty6'
skipping special file 'tty5'
skipping special file 'tty4'
skipping special file 'tty3'
skipping special file 'tty2'
skipping special file 'tty1'
skipping special file 'tty0'
skipping special file 'console'
skipping special file 'tty'
skipping special file 'kmsg'
skipping special file 'urandom'
skipping special file 'random'
skipping special file 'full'
skipping special file 'zero'
skipping special file 'null'
skipping special file 'kmem'
skipping special file 'mem'
skipping special file 'ttyGS3'
skipping special file 'ttyGS2'
skipping special file 'ttyGS1'
skipping special file 'ttyGS0'
skipping special file 'video0'
skipping special file 'rtc0'
skipping special file 'mma8452_daemon'
skipping special file 'ttyS2'
skipping special file 'ttyS0'
skipping special file 'ttyS1'
skipping special file 'property_service'
skipping special file 'event2'
skipping special file 'event0'
skipping special file 'event1'
skipping special file 'fb1'
skipping special file 'fb0'
skipping special file '001'
skipping special file '001'
skipping special file 'timer'
skipping special file 'controlC0'
skipping special file 'pcmC0D0c'
skipping special file 'pcmC0D0p'
skipping special file 'system'
skipping special file 'radio'
skipping special file 'events'
skipping special file 'main'
skipping special file 'mtdblock10'
skipping special file 'mtdblock9'
skipping special file 'mtdblock8'
skipping special file 'mtdblock7'
skipping special file 'mtdblock6'
skipping special file 'mtdblock5'
skipping special file 'mtdblock4'
skipping special file 'mtdblock3'
skipping special file 'mtdblock2'
skipping special file 'mtdblock1'
skipping special file 'mtdblock0'
skipping special file 'loop7'
skipping special file 'loop6'
skipping special file 'loop5'
skipping special file 'loop4'
skipping special file 'loop3'
skipping special file 'loop2'
skipping special file 'loop1'
skipping special file 'loop0'
skipping special file 'mtd10ro'
skipping special file 'mtd10'
skipping special file 'mtd9ro'
skipping special file 'mtd9'
skipping special file 'mtd8ro'
skipping special file 'mtd8'
skipping special file 'mtd7ro'
skipping special file 'mtd7'
skipping special file 'mtd6ro'
skipping special file 'mtd6'
skipping special file 'mtd5ro'
skipping special file 'mtd5'
skipping special file 'mtd4ro'
skipping special file 'mtd4'
skipping special file 'mtd3ro'
skipping special file 'mtd3'
skipping special file 'mtd2ro'
skipping special file 'mtd2'
skipping special file 'mtd1ro'
skipping special file 'mtd1'
skipping special file 'mtd0ro'
skipping special file 'mtd0'
^C
# adb pull /system
pull: building file list...
pull: /system/bin/busybox -> ./bin/busybox
1 file pulled. 0 files skipped.
2736 KB/s (1807056 bytes in 0.644s)
# ls
bin
# ls bin
busybox
adb ls /
still no sh
any ideas?
what about
000081a4 0001e9ff 00000000 rk29xxnand_ko.ko.3.0.8+
000081a4 0001e995 00000000 rk29xxnand_ko.ko.2.6.32.27
# adb ls /
000041ed 00000000 51470583 .
000041ed 00000000 51470583 ..
000041ed 00000000 51470583 cache
000041ed 00000000 51470583 mnt
000081a4 000006f9 00000000 ueventd.rk29board.rc
000081a4 00000f71 00000000 ueventd.rc
000081a4 00000110 00000000 ueventd.goldfish.rc
000041ed 00000000 51470585 tmp
000041ed 00000000 00000000 system
000041ed 00000000 51470583 sys
000041e8 00000000 00000000 sbin
000081a4 0001e9ff 00000000 rk29xxnand_ko.ko.3.0.8+
000081a4 0001e995 00000000 rk29xxnand_ko.ko.2.6.32.27
000041ed 00000000 00000000 res
0000416d 00000000 00000000 proc
000081e8 00000626 00000000 init.rc
000081e8 000191ac 00000000 init
000041ed 00000000 00000000 etc
000081a4 00000908 00000000 default.prop
000041ed 00000000 51470d4e data
000081e8 0003abe4 00000000 charger
000041c0 00000000 4fd5637e root
000041ed 000009b0 51470585 dev
# adb ls /sys
000041ed 00000000 51470583 .
000041ed 00000000 51470583 ..
000041ed 00000000 514718d3 fs
000041ed 00000000 51470583 devices
000041ed 00000000 514718d3 dev
000041ed 00000000 514718d3 bus
000041ed 00000000 51470583 class
000041ed 00000000 514718d3 firmware
000041ed 00000000 514718d3 kernel
000041ed 00000000 514718d3 power
000041ed 00000000 514718d3 module
000041ed 00000000 51470583 block
000041ed 00000000 514718d3 android_gsensor
000041ed 00000000 514718d3 sd-sdio
# adb ls /sbin
000041e8 00000000 00000000 .
000041ed 00000000 51470583 ..
0000a1ff 00000007 00000000 ueventd
000081e8 0001dd74 00000000 resize2fs
000081e8 00046330 00000000 recovery
000081e8 0002da68 00000000 mke2fs
000081e8 00012700 00000000 mkdosfs
000081e8 0004345c 00000000 e2fsck
000081e8 00022d40 00000000 adbd
.s
tried copying over the sh from second android
pushed to 1st android
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
still fails
wonder if file permission thing, if so howto chage without shell capability
# adb root
adbd is already running as root
wolfbite.aus said:
tried copying over the sh from second android
pushed to 1st android
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
still fails
wonder if file permission thing, if so howto chage without shell capability
# adb root
adbd is already running as root
Click to expand...
Click to collapse
As for the sh script, there isn't one that I know of. Sorry.
You must also apply file permissions with chmod for each file that you push to the device. Most file permissions are going to be 0644 or 0755.
All the Linux commands you are using are actually symlinked to busybox in your /system/bin folder. I would recommend updating your busybox installation while you are in the process of rooting with this method.
You should also update the SuperUser.apk in /system/app since you updated/replaced the su binary in /system/bin. A wise precautionary measure is to also install a copy of the su binary in /system/xbin.
the adb command seems to work push, pull, /
adb shell still gives me
- exec '/system/bin/sh' failed: No such file or directory (2) -
tried pushing busybox (succesful)
but getting same error with shell
how do you apply chmod without shell?
can you break down what the hexidecimal values mean (tried searching)
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
tried setting file permissions befor pushing, didnt work
tried upgrading img but got signature verification errors no matter what I through at it
(not worried about bricking this one, slight kid damaged screen and another to use for final results
theres probably mor i can do with adb but its learn as we go
wolfbite.aus said:
the adb command seems to work push, pull, /
adb shell still gives me
- exec '/system/bin/sh' failed: No such file or directory (2) -
tried pushing busybox (succesful)
but getting same error with shell
how do you apply chmod without shell?
can you break down what the hexidecimal values mean (tried searching)
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
tried setting file permissions befor pushing, didnt work
tried upgrading img but got signature verification errors no matter what I through at it
(not worried about bricking this one, slight kid damaged screen and another to use for final results
theres probably mor i can do with adb but its learn as we go
Click to expand...
Click to collapse
Permissions must be set after pushing to the device.
guess thats it then
if I cant get a shell, then nothing else to do
[Failed] ROOT without adb driver?
close thread
useful post
but afraid of the codes
What i Did
I took the google usb driver, then downloaded the (supposed) usb drivers from my manufactuer. The maker of my phone, totally screwed up their usb drivers, they didn't have the right vid/pid 's for it( checked the drivers in a linux distro) . Opened the manufactuer's driver, changed the vid/pid's to what was supposed to be there, in it, and the google driver too. Opened the device manager(windows) and ran the "have disk" option, to get the right recognition, and all of the (ADB interface, Bootloader Interface, Composite..) intalled correctly.SDK, eclipse, QtAdb, run great, the only problem is not recognizing what bootloader is in phone( it's locked). I think you're doing a little too much, for your problem.
wolfbite.aus said:
guess thats it then
if I cant get a shell, then nothing else to do
Click to expand...
Click to collapse
hang in there brah i rooted my 2 days ago. i got the a/sonic 10.1 rk2928 chip
how i did it? hrmm i downloaded the rk29 root tool its some where on xda forums. find it.! once i plugged the usb cable into my tablet from pc all drivers installed only one didn't that one t-22b i think. so i used my samsung s2 drivers that was already installed. and walla! adb started working the rest i left for the root kit runme.bat hope that helped good luck!
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.