Hi all,
This after noon I wanted to take a photo with the camera 8Mpx my Razr i (the large, not the front one) and my phone told me "Camera is Unable to initialize."
The front camera works fine however.
I deleted the cache and data from the "Camera" app and it worked once.
Some hours later, I had the same problem, deleting data changed nothing. I rebooted, no change either.
My phone is modded a lot, I started it in safe mode to avoid starting all my Root apps. Apparently it works, the camera starts up just yet.
I have a lot of Xposed module. The only one that is likely to use the camera is Snapchat. I disabled it and she still did not work.
I don't think I am going to bother uninstalling my applications one by one. I'll flash a clean ROM and test the long term.
I read on a forum that someone had the same problem he had opened his mobile phone and re-tensioned springs that serve as connectors between modules attached to the casing and the motherboard.
Before flashing a new ROM and disassemble it, can someone advise me some tests?
Maybe we can identify the issue before using "the hard way".
In advance, thank you
Titus.
EDIT :
I rectify, in safe mode it does not work either.
Hard issue then I guess ...
some details
I found an application that shows me the remaining space in all partitions, the problem does not seem to be there.
"Camera is Unable to initialize." came back, I managed to get the log this time:
Process App. photo(com.motorola.camera)
W/13:06:20.815 :0: gralloc_unregister_buffer: ID: 11016 handle: 0x617503c0 size: 540 x 903 fmt: 5 usage: 0xb00
W/13:06:20.815 :0: gralloc_unregister_buffer: ID: 11014 handle: 0x6174ce30 size: 540 x 903 fmt: 5 usage: 0xb00
W/13:06:20.815 :0: gralloc_unregister_buffer: ID: 11013 handle: 0x61575220 size: 540 x 903 fmt: 5 usage: 0xb00
W/13:06:20.445 :0: gralloc_unregister_buffer: ID: 11019 handle: 0x61753f30 size: 513 x 251 fmt: 1 usage: 0x933
E/13:06:20.425 loading failed!
E/13:06:20.425 Preference group is null!
D/13:06:20.415 caller of unregisterListener:15357,sensor type: ALL
W/13:06:20.405 :0: gralloc_register_buffer: ID: 11019 handle: 0x61753f30 size: 513 x 251 fmt: 1 usage: 0x933
W/13:06:20.405 :0: gralloc_unregister_buffer: ID: 11018 handle: 0x6174f9c0 size: 513 x 251 fmt: 5 usage: 0xb00
W/13:06:20.405 :0: gralloc_unregister_buffer: ID: 11017 handle: 0x61757e60 size: 513 x 251 fmt: 5 usage: 0xb00
W/13:06:20.405 :0: gralloc_unregister_buffer: ID: 11015 handle: 0x6174e180 size: 513 x 251 fmt: 5 usage: 0xb00
W/13:06:20.265 :0: gralloc_register_buffer: ID: 11018 handle: 0x6174f9c0 size: 513 x 251 fmt: 5 usage: 0xb00
W/13:06:19.275 :0: gralloc_register_buffer: ID: 11017 handle: 0x61757e60 size: 513 x 251 fmt: 5 usage: 0xb00
W/13:06:19.265 :0: gralloc_register_buffer: ID: 11016 handle: 0x617503c0 size: 540 x 903 fmt: 5 usage: 0xb00
W/13:06:19.225 :0: gralloc_register_buffer: ID: 11015 handle: 0x6174e180 size: 513 x 251 fmt: 5 usage: 0xb00
W/13:06:19.195 :0: gralloc_register_buffer: ID: 11014 handle: 0x6174ce30 size: 540 x 903 fmt: 5 usage: 0xb00
W/13:06:19.135 :0: gralloc_register_buffer: ID: 11013 handle: 0x61575220 size: 540 x 903 fmt: 5 usage: 0xb00
D/13:06:19.075 caller of registerListener:15357,sensor type:1
=============================================
And I have also this one:
E/13:18:22.935 Camera_ControlThread(15037)
Error initializing ISP with id 0
E/13:18:22.935 Camera_ISP(15037)
Failed to open first device!
E/13:18:22.935 Camera_ISP(15037)
V4L2: capture_open failed: Invalid argument
W/13:18:22.935 Camera_ISP(15037)
Open device 0 with fd -1
E/13:18:22.935 Camera_ISP(15037)
Error opening video device /dev/video0: Invalid argument
D/13:18:22.935 Camera_ISP(15037)
Kernel with multiplexed preview and main devices detected
D/13:18:22.935 Camera_HAL(15037)
ATOM_OpenCameraHardware
I/13:18:22.935 CameraService(15037)
Opening camera 0
D/13:18:22.935 Camera_HAL(15037)
ATOM_GetCameraInfo
I/13:18:22.845 ActivityManager( 452)
START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.motorola.camera/.Camera u=0} from pid 15357
=============================================
Although we see there is a problem ...
Can someone help me? I am a little lost
some details
The reboot by removing the cache and data of 'Camera' makes it usable for about 1 hour.
I questioned a Snapchat plugin with Xposed but even by uninstalling it changes nothing.
Xposed installs something in '/ system'. Perhaps the plugin uninstaller does not remove this?
I compared my logs with another phone with a camera works, there is clearly no log out of the apk Camera.
We must not consider the warning "gralloc" which is also present when my camera works.
Up, still relevant
RBeal said:
Up, still relevant
Click to expand...
Click to collapse
i have the same problem.. did anyone solve this problem???
No sorry...
I still search
New logs... :
-------------------------------------------------
Process Camera(com.motorola.camera)
E/08:34:03.307 loading failed!
E/08:34:03.307 Preference group is null!
D/08:34:03.297 caller of unregisterListener:27155,sensor type:ALL,listener:[email protected]b3fc58
I/08:34:02.007 Total arena pages for JIT: 18
I/08:34:02.007 Total arena pages for JIT: 17
I/08:34:02.007 Total arena pages for JIT: 16
I/08:34:02.007 Total arena pages for JIT: 15
I/08:34:02.007 Total arena pages for JIT: 14
I/08:34:02.007 Total arena pages for JIT: 13
I/08:34:01.997 Total arena pages for JIT: 12
I/08:34:01.997 Total arena pages for JIT: 11
W/08:34:01.857 Camera service died!
W/08:34:01.857 media server died
E/08:34:01.857 Unable to load sample: (null)
E/08:34:01.847 Unable to load sample: (null)
W/08:34:01.847 An error occurred while connecting to camera: 0
D/08:34:01.727 caller of registerListener:27155,sensor type:1,listener:[email protected]b3fc58
E/08:33:44.847 loading failed!
E/08:33:44.847 Preference group is null!
D/08:33:44.847 caller of unregisterListener:27155,sensor type:ALL,listener:[email protected]c4c9d0
D/08:33:43.527 caller of registerListener:27155,sensor type:1,listener:[email protected]c4c9d0
D/08:33:43.447 GC_CONCURRENT freed 1064K, 9% free 14555K/15984K, paused 5ms+4ms, total 43ms
W/08:33:43.417 An error occurred while connecting to camera: 0
E/08:33:29.707 loading failed!
E/08:33:29.707 Preference group is null!
D/08:33:29.707 caller of unregisterListener:27155,sensor type:ALL,listener:[email protected]c12ac0
D/08:33:28.487 caller of registerListener:27155,sensor type:1,listener:[email protected]c12ac0
W/08:33:28.467 An error occurred while connecting to camera: 0
-------------------------------------------------
Related
Hi there,
a few days ago I updated my Razr i to version 81.5.31002 via RSD lite and then to 81.5.40002 via custom recovery. I have an unlocked bootloader and it all went well, except for the radio. After the update, I couldn't get any service any more. I have a EU retail phone and am currently in Australia, I don't know if that makes any difference regarding carriers, etc...
Anyways, I tried restoring a nandroid backup but it still didn't work, so I'm assuming it has to do with the radio that was updated while flashing the new version. Wifi still works, but I guess that doesn't mean anything. My dad owns another Razr i which still has the old version running, so I will try to extract it from his phone and flashing it onto mine, but I don't know what block to extract. Here's the output for adb shell su cat /proc/partitions:
[email protected]:/proc # cat /proc/partiti
cat /proc/partitions
major minor #blocks name al
[email protected]:/proc # cat /proc/partitions
cat /proc/partitions
major minor #blocks name alias
179 0 7766016 mmcblk0 (null)
179 1 11264 mmcblk0p1 bos
179 2 11264 mmcblk0p2 bosbackup
179 3 1024 mmcblk0p3 ulogo
179 4 1024 mmcblk0p4 logo
179 5 11264 mmcblk0p5 boot
179 6 11264 mmcblk0p6 recovery
179 7 128 mmcblk0p7 cid
179 8 2048 mmcblk0p8 sp
179 9 8192 mmcblk0p9 panic
179 10 512 mmcblk0p10 devtree
179 11 512 mmcblk0p11 devtreeBackup
259 0 8192 mmcblk0p12 pds
259 1 512 mmcblk0p13 misc
259 2 655360 mmcblk0p14 cache
259 3 153600 mmcblk0p15 cdrom
259 4 1253376 mmcblk0p16 system
259 5 5599471 mmcblk0p17 userdata
179 12 7761920 mmcblk1 (null)
179 13 7757824 mmcblk1p1
Any ideas which one could be the radio? Or does anyone have any further suggestions how I can fix my problem?
Thanks a lot!
Edit:
Here are some possibly interesting lines from logcat:
12-03 21:57:20.599 1491 1491 D LSAPP_LSDet: hasPoi:...no POIs !
12-03 21:57:20.599 1491 1491 D LSAPP_Beacon: notifyAllCallers : notify caller
POI=null caller:Handler (com.motorola.contextual.virtualsensor.locationsensor.Lo
cationDetection$MessageHandler) {212391b0}
12-03 21:57:20.599 1491 1491 E LSApp_App: Sending Message to Handler (com.moto
rola.contextual.virtualsensor.locationsensor.LocationDetection$MessageHandler) {
212391b0}: msg :1010002
12-03 21:57:20.599 1491 1720 D LSAPP_LSDet: matchBeacons: Beacon no match any
poi...:
12-03 21:57:20.599 1491 1720 D LSAPP_LSDet: startDetection: celltower changed
: do nothing because not in a poi and cells are not POI cells ::{"Lac":"0","Cntr
yISO":"","NetTyp":"GSM","NetOp":"","Cid":"0"}
12-03 21:57:20.609 1491 1720 D LSAPP_TimerTask: stopPeriodicalUpdate : network
provider:false wifiscan: true
12-03 21:57:20.639 588 907 D NetworkLocator: null cell state delivered
12-03 21:57:20.649 1491 1491 D LSAPP_TelMon: onCellTowerChanged:: GSM :: cur_v
al : {"Lac":"-1","CntryISO":"","NetTyp":"GSM","NetOp":"","Cid":"-1"} new_val: {"
Lac":"-1","CntryISO":"","NetTyp":"GSM","NetOp":"","Cid":"-1"}
12-03 21:57:20.649 1491 1720 D LSAPP_LSDet: hasPoi:...no POIs !
12-03 21:57:20.649 1491 1708 D LSAPP_LSMan: hasCellTowerChanged :: Yes :start
tracking : cur cell :{"Lac":"0","CntryISO":"","NetTyp":"GSM","NetOp":"","Cid":"0
"}:: new cell :{"Lac":"-1","CntryISO":"","NetTyp":"GSM","NetOp":"","Cid":"-1"}
12-03 21:57:20.649 1491 1708 D LSAPP_LSMan: celltower changed... new cell..we
are moving.. :: NO timer because -1 cell id with pending intent
12-03 21:57:20.649 1491 1720 D LSAPP_LSDet: startDetection: celltower changed
: stop location detection...no POIs
12-03 21:57:22.689 276 331 I WifiHW : CMD: SIGNAL_POLL
12-03 21:57:22.689 4281 4281 D wpa_supplicant: nl80211: survey data missing!
12-03 21:57:22.689 276 331 I WifiHW : REPLY: RSSI=-83
12-03 21:57:22.689 276 331 I WifiHW : LINKSPEED=1
12-03 21:57:22.689 276 331 I WifiHW : NOISE=-97
12-03 21:57:22.689 276 331 I WifiHW : FREQUENCY=2462
lol you need to go to system/etc/firmware/modem and copy radio_firmware.bin from your razr to pc then flash it whilst your phone is in fastboot
fastboot flash radio radio_firmware.bin
rickwyatt said:
lol you need to go to system/etc/firmware/modem and copy radio_firmware.bin from your razr to pc then flash it whilst your phone is in fastboot
fastboot flash radio radio_firmware.bin
Click to expand...
Click to collapse
Wow didn't know it was that easy...
Sorry for starting a whole thread for that... Anyways, I'll try that and see if it works.
Thanks!
Edit:
It worked!
Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
================================================== ====
Sending AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE AMSS CERTIFICATE SUCCESS
Sending AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : AMSS WRITE SUCCESS
Sending ADSP Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 449 Bytes
Status : WRITE ADSP CERTIFICATE SUCCESS
Sending ADSP Data Blocks
(Please Wait for 25 Seconds...)
Status : ADSP WRITE SUCCESS
Sending MDM AMSS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM AMSS CERTIFICATE SUCCESS
Sending MDM AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM AMSS WRITE SUCCESS
Sending MDM DSP1 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP1 CERTIFICATE SUCCESS
Sending MDM DSP1 Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM DSP1 WRITE SUCCESS
Sending MDM DSP2 Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 447 Bytes
Status : WRITE MDM DSP2 CERTIFICATE SUCCESS
Sending MDM DSP2 Data Blocks
(Please Wait for 100 Seconds...)
Status : MDM DSP2 WRITE SUCCESS
Sending WPOS Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 1652 Bytes
Status : WRITE WPOS CERTIFICATE SUCCESS
Sending WPOS Data Blocks
[BLOCK 1 0x00000000~0x00FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8D9F6A1AF69045EC0339C2EFFC2527D
---------- : D1CAECCFCFC39F1F44C67A5AD3F6C050
Status : WPOS WRITE SUCCESS
[BLOCK 2 0x01000000~0x016573FF]
Data Size: 0x00657400 Bytes
SHA-256 : 98D712C48E828E9816D3F7E84CFDE5DB
---------- : 2C32011C24D4615234D0F613F4EF7B52
Status : WPOS WRITE SUCCESS
[BLOCK 3 0x01697400~0x01FFFFFF]
Data Size: 0x00968C00 Bytes
SHA-256 : 80EB94E3FB5AE03E9091361275A3138E
---------- : 2D0370E5C2A497C74BEA6BEAA43A9E21
Status : WPOS WRITE SUCCESS
[BLOCK 4 0x02000000~0x02FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 07BE87B2AF4D1386F4C6CA136F3E5A57
---------- : 71DC6DDB330A07AAB4493C8AA329BB58
Status : WPOS WRITE SUCCESS
[BLOCK 5 0x03000000~0x03FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2A3DE5C7CB693B00E257A4E7FB03E834
---------- : 11FAA597F94B220E69E25BD4653BE9B5
Status : WPOS WRITE SUCCESS
[BLOCK 6 0x04000000~0x04FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 16A3B764DD2CCBE5D144B504A919A847
---------- : 2F5DDCBBE2506ACEF6A39800E4DC5124
Status : WPOS WRITE SUCCESS
[BLOCK 7 0x05000000~0x05FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 4A508131A19FC499F19529C55D5D69B8
---------- : D85FA016F8CADE240FA88FA175159699
Status : WPOS WRITE SUCCESS
[BLOCK 8 0x06000000~0x06FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 9E494B017FB7E00D9245C8AEF0F01467
---------- : F3A10341E7441CBEBDE04399AFDD8C5E
Status : WPOS WRITE SUCCESS
[BLOCK 9 0x07000000~0x07FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 2AA1C1C01BA5F8825796F134753C7651
---------- : ABAC4C024CF30CE60B624C4E6C8CD665
Status : WPOS WRITE SUCCESS
[BLOCK 10 0x08000000~0x08FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 6F6EA7A66C4AE1A05CF643378A07E1A8
---------- : 523B29D66201C2FBD4053B19E785DE14
Status : WPOS WRITE SUCCESS
[BLOCK 11 0x09000000~0x09FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 017C4DB9A69575E684BADB7515DBBF59
---------- : 67A6F0DA20F034470D6148B12A1013F4
Status : WPOS WRITE SUCCESS
[BLOCK 12 0x0A000000~0x0AFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 1EFE884A458C910A768D6A60FF74BA8B
---------- : 58F546EB92737ACD1A59169E583CD407
Status : WPOS WRITE SUCCESS
[BLOCK 13 0x0B000000~0x0BFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 713CF0944BA46C6820DCEB7A210C365A
---------- : 7F8A1B0C3E168DE07B46E14907F511FC
Status : WPOS WRITE SUCCESS
[BLOCK 14 0x0C000000~0x0CFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 425A9ED14D4A78F21CDD261AB87F2CF1
---------- : 37080DD8E63F6A9BBBC4E9181AF7B9D2
Status : WPOS WRITE SUCCESS
[BLOCK 15 0x0D000000~0x0DFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 0C09DA5584E22D2709C548F2E5CD05F5
---------- : CFB62CE93C7DAF202A4B92299072B4FB
Status : WPOS WRITE SUCCESS
[BLOCK 16 0x0E000000~0x0EFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : CC14545EF5F62DA50EFADEC5E077FA15
---------- : FE6723E61D703468E0F2B88A3A77008E
Status : WPOS WRITE SUCCESS
[BLOCK 17 0x0F000000~0x0FFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 75D352196D46AC4FED27B84844D89D27
---------- : A8E6C4BD07D46537FA1D66BC533BF017
Status : WPOS WRITE SUCCESS
[BLOCK 18 0x10000000~0x10FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D6847541FEB0C828C7BE18F045FD2602
---------- : D31D627E75BAA24AD9EBE13E111DCD96
Status : WPOS WRITE SUCCESS
[BLOCK 19 0x11000000~0x11FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 3512321DD2C8349BF40BF6ACD45B82A8
---------- : 970E7902252853F1C75FD6DA3B07416C
Status : WPOS WRITE SUCCESS
[BLOCK 20 0x12000000~0x12FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 970B38B361801866AEB1F9D0E2A6E5FB
---------- : 28066FD1BCF0EF794B57E56439B29152
Status : WPOS WRITE SUCCESS
[BLOCK 21 0x13000000~0x13FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C8E0BAEDBCFC0A13A125FF17A9DDDA0E
---------- : 91AC3DD74B6E738F3AD53D269F12CFFD
Status : WPOS WRITE SUCCESS
[BLOCK 22 0x14000000~0x14FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D786A1406E5AF5D0B5354003197BCE87
---------- : F34053A66DF8375001E2DB59D528B21D
Status : WPOS WRITE SUCCESS
[BLOCK 23 0x15000000~0x15FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 47A2B984B6D9C39AF4131C9ED8DB949A
---------- : 82CBC84E0019ECB0E1BABB61E0F47790
Status : WPOS WRITE SUCCESS
[BLOCK 24 0x16000000~0x16FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : D4CEA61B44087F662387735C6AF3F626
---------- : D0A782BCFC893D7CD19A1895A2503AE8
Status : WPOS WRITE SUCCESS
[BLOCK 25 0x17000000~0x17FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 93D0DB4DA824CE4660B96A99A1F65989
---------- : CA45F500E83FC9A53D1D8330B150A80E
Status : WPOS WRITE SUCCESS
[BLOCK 26 0x18000000~0x184A17FF]
Data Size: 0x004A1800 Bytes
SHA-256 : 0CE0CCDE41E4E40B170207CABCE6AA18
---------- : 8FD44C00E21833E6B5926A1F0CDFA40A
Status : WPOS WRITE SUCCESS
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
otchere said:
Windows Phone Flashing Started
AMSS File Found:
RM823_12w30_1_prod_generic_amss.esco
ADSP File Found:
RM823_12w30_1_prod_generic_adsp.esco
WPOS File Found:
RM823_12301_prod_238_02_boot.esco
MDM AMSS File Found:
RM823_12w30_1_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM823_12w30_1_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM823_12w30_1_prod_generic_mdm_dsp2.esco
USER AREA ERASE File Found:
RM823_12w30_1_prod_generic_user_area_erase.esco
WARNING: OSBL File is not Loaded
================================================== ====
Windows Phone Lumia Flasher
================================================== ====
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
Sending USER AREA ERASE Certificate
HASH: 6898A268F71233A06C3082728DB725A38679C21C
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS
Erasing USER AREA
Status : ERASE SUCCESS
Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:06:17
plz i have one the same problem.
it was work good only whatsapp app was not working
after i flashed it hang on nokia logo
Click to expand...
Click to collapse
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
thals1992 said:
Well, RM823 is a Lumia 900. What was your purpose for flashing your phone? To debrand it? Usually the rom thats on it is just fine.
Click to expand...
Click to collapse
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
otchere said:
plz i want to know if the the boot is destroyed or what because the phone powered on.....but hang on nokia logo
Click to expand...
Click to collapse
Did you first try the hard reset method with the VolDown + Power first? The only other method I'd recommend is using the Nokia Care Suite instead of what you are using. Its much simpler. Just remember to download the latest edition with the CareSuite External cfg file.
One other thing: what phone are you flashing this *onto*? If you tried flashing a Lumia 900 ROM onto a Lumia 920, for example, there is no possible way it will work (although the flashing tool should detect the discrepancy).
By the way, to get to appropriate forums for the Lumia 900, you should go to the WP7 forums (not WP8, such as this) or possibly to a device-specific forum
Oh, and title your thread properly! Seriously, people... if somebody posts a thread with a title like "plz help me" my default response is "No. Go read the forum rules and come back when you can make posts distinguishable from spam."
Hey, I'm using noname81s lmt-launcher. Yesterday for no apparent reason the app crashed and won't work any more. I wiped my phone with cwm. And tried to restore a working backup, too. But without success... Any ideas?
wayne int.
Just install the latest version please and it will work again.
I tried several versions, at the moment I'm using v1.99. The Error appears on stockRom, as well as on Omars Rom. Logcat shows no error. Dunno if this helps. It's like bewitched. :/
09-05 08:45:55.841 I/ActivityManager(441): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.lmt/.LMT u=0} from pid 678
09-05 08:45:55.865 W/ApplicationContext(441): Unable to create files directory /data/data/com.android.lmt/files
09-05 08:45:55.913 I/ActivityManager(441): Start proc com.android.lmt for activity com.android.lmt/.LMT: pid=6765 uid=10076 gids={3002, 3001, 1028}
09-05 08:45:56.137 D/dalvikvm(6765): Trying to load lib /data/data/com.android.lmt/lib/libTouchServiceNative.so 0x420a9f20
09-05 08:45:56.285 D/dalvikvm(6765): Added shared lib /data/data/com.android.lmt/lib/libTouchServiceNative.so 0x420a9f20
09-05 08:45:56.285 D/dalvikvm(6765): No JNI_OnLoad found in /data/data/com.android.lmt/lib/libTouchServiceNative.so 0x420a9f20, skipping init
09-05 08:45:56.565 I/ActivityManager(441): Displayed com.android.lmt/.LMT: +667ms
09-05 08:46:00.517 D/su (6813): 10076 com.android.lmt executing 0 /system/bin/sh using binary /system/bin/sh : sh
09-05 08:46:12.113 D/LMT::TouchService(6765): TouchService created
09-05 08:46:12.121 D/LMT::TouchService(6765): TouchService started
wayne int.
Henning84 said:
I tried several versions, at the moment I'm using v1.99. The Error appears on stockRom, as well as on Omars Rom. Logcat shows no error. Dunno if this helps. It's like bewitched. :/
Click to expand...
Click to collapse
Here works lmt launcher v1.99 fine. without problems except gestures. I'm on stock ROM.
I've used it, since I routed my phone. No problems until now... on stockrom the app crashes. on Omars Rom the app won't crash but nevertheless it didn't work. Can't stop the process within the app, only start.
wayne int.
Think i logged the failure... But I doubt that it'll help...
09-05 22:12:05.150 W/IMGSRV (1572): :0: gralloc_register_buffer: ID: 897 handle: 0x76de4900 size: 540 x 906 fmt: 5 usage: 0xb00
09-05 22:12:05.290 W/IMGSRV (1572): :0: gralloc_register_buffer: ID: 898 handle: 0x76f9aff0 size: 540 x 906 fmt: 5 usage: 0xb00
09-05 22:12:05.534 W/IMGSRV (1572): :0: gralloc_register_buffer: ID: 899 handle: 0x75c42d50 size: 540 x 906 fmt: 5 usage: 0xb00
09-05 22:12:06.930 D/LMT::TouchService(1572): TouchService started
09-05 22:12:06.986 W/IMGSRV (1572): :0: gralloc_register_buffer: ID: 900 handle: 0x76cff010 size: 325 x 77 fmt: 1 usage: 0x933
09-05 22:12:08.038 W/IMGSRV (1572): :0: gralloc_unregister_buffer: ID: 897 handle: 0x76de4900 size: 540 x 906 fmt: 5 usage: 0xb00
09-05 22:12:08.038 W/IMGSRV (1572): :0: gralloc_unregister_buffer: ID: 898 handle: 0x76f9aff0 size: 540 x 906 fmt: 5 usage: 0xb00
09-05 22:12:08.038 W/IMGSRV (1572): :0: gralloc_unregister_buffer: ID: 899 handle: 0x75c42d50 size: 540 x 906 fmt: 5 usage: 0xb00
09-05 22:12:08.934 W/IMGSRV (1572): :0: gralloc_unregister_buffer: ID: 900 handle: 0x76cff010 size: 325 x 77 fmt: 1 usage: 0x933
09-05 22:33:28.102 D/LMT::TouchService(1572): New orientation: 1
09-05 22:33:28.150 D/AndroidRuntime(1572): Shutting down VM
09-05 22:33:28.150 W/dalvikvm(1572): threadid=1: thread exiting with uncaught exception (group=0x41851a50)
09-05 22:33:28.178 E/AndroidRuntime(1572): FATAL EXCEPTION: main
09-05 22:33:28.178 E/AndroidRuntime(1572): java.lang.NullPointerException
09-05 22:33:28.178 E/AndroidRuntime(1572): at com.android.lmt.TouchService.rotate(TouchService.java:203)
09-05 22:33:28.178 E/AndroidRuntime(1572): at com.android.lmt.TouchService.onConfigurationChanged(TouchService.java:196)
09-05 22:33:28.178 E/AndroidRuntime(1572): at android.app.ActivityThread.performConfigurationChanged(ActivityThread.java:3778)
09-05 22:33:28.178 E/AndroidRuntime(1572): at android.app.ActivityThread.handleConfigurationChanged(ActivityThread.java:3907)
09-05 22:33:28.178 E/AndroidRuntime(1572): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1359)
09-05 22:33:28.178 E/AndroidRuntime(1572): at android.os.Handler.dispatchMessage(Handler.java:99)
09-05 22:33:28.178 E/AndroidRuntime(1572): at android.os.Looper.loop(Looper.java:137)
09-05 22:33:28.178 E/AndroidRuntime(1572): at android.app.ActivityThread.main(ActivityThread.java:5031)
09-05 22:33:28.178 E/AndroidRuntime(1572): at java.lang.reflect.Method.invokeNative(Native Method)
09-05 22:33:28.178 E/AndroidRuntime(1572): at java.lang.reflect.Method.invoke(Method.java:511)
09-05 22:33:28.178 E/AndroidRuntime(1572): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:792)
09-05 22:33:28.178 E/AndroidRuntime(1572): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:555)
09-05 22:33:28.178 E/AndroidRuntime(1572): at dalvik.system.NativeStart.main(Native Method)
09-05 22:33:32.510 I/Process (1572): Sending signal. PID: 1572 SIG: 9
wayne int.
And a screenshot:
wayne int.
Die you test LMT 1.912? This version should work.
That's it. Thank you! I think I tried only versions above this release. But still I don't understand why...
wayne int.
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Rastikan said:
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Click to expand...
Click to collapse
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Do you see small text appear on the screen after loading it?
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
jcsullins said:
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Click to expand...
Click to collapse
Ok, from the 'Palm mode' ( POWER + HOME + VOLUME-UP ) for about 30 seconds ...
Code:
dfu-util -d 0830:8070 -R -D moboot-dfu-20150128
jcsullins said:
Do you see small text appear on the screen after loading it?
Click to expand...
Click to collapse
Yes!!! Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time ( although I was getting some access through SSH )
jcsullins said:
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
Click to expand...
Click to collapse
Code:
(bootloader) [2100] a6_test: batt valid=1 percent=0 voltage=3225680
(bootloader) [2110] a6_test: batt temp=19 current=-312 coulombs=0
Although it does says 0 percent, I did let it charge the whole night ( as your tpdebrick tool suggests )
jcsullins said:
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
Click to expand...
Click to collapse
Yes, I see ( finally) stuff on the screen! Again, Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time.
http://forum.xda-developers.com/attachment.php?attachmentid=3139872&stc=1&d=1422547266
Now can I go ahead and load-up or run your full toolbox software and reformat/setup the entire flash device for Android ?
My phone got bricked, can't enter to download mode, recovery. Display GT-i8190n logo in a loop. Could someone explain in what order partitions below are booted ? I mean those:
==== PARTITION INFORMATION =====
ID: MBR,GPT ( 1) DEVICE: MMC FIRST UNIT: 0 NO. UNITS: 256 USED UNITS: 0
ID: MasterTOC ( 2) DEVICE: MMC FIRST UNIT: 256 NO. UNITS: 768 USED UNITS: 0
ID: PIT (70) DEVICE: MMC FIRST UNIT: 1024 NO. UNITS: 2048 USED UNITS: 0
ID: MD5HDR (71) DEVICE: MMC FIRST UNIT: 6144 NO. UNITS: 2048 USED UNITS: 0
ID: STEboot1 ( 3) DEVICE: MMC FIRST UNIT: 8192 NO. UNITS: 1024 USED UNITS: 0
ID: STEboot2 ( 4) DEVICE: MMC FIRST UNIT: 9216 NO. UNITS: 1024 USED UNITS: 0
ID: Dnt ( 5) DEVICE: MMC FIRST UNIT: 10240 NO. UNITS: 1024 USED UNITS: 0
ID: reserved ( 6) DEVICE: MMC FIRST UNIT: 11264 NO. UNITS: 1024 USED UNITS: 0
ID: CSPSAFS ( 7) DEVICE: MMC FIRST UNIT: 16384 NO. UNITS: 2048 USED UNITS: 0
ID: CSPSAFS2 ( 8) DEVICE: MMC FIRST UNIT: 18432 NO. UNITS: 2048 USED UNITS: 0
ID: EFS ( 9) DEVICE: MMC FIRST UNIT: 20480 NO. UNITS: 32768 USED UNITS: 0
ID: ModemFS (10) DEVICE: MMC FIRST UNIT: 53248 NO. UNITS: 32768 USED UNITS: 0
ID: ModemFS2 (11) DEVICE: MMC FIRST UNIT: 86016 NO. UNITS: 32768 USED UNITS: 0
ID: Fota (12) DEVICE: MMC FIRST UNIT: 118784 NO. UNITS: 102400 USED UNITS: 0
ID: IPL Modem (13) DEVICE: MMC FIRST UNIT: 380928 NO. UNITS: 128 USED UNITS: 0
ID: Modem (14) DEVICE: MMC FIRST UNIT: 385024 NO. UNITS: 28672 USED UNITS: 0
ID: Loke4 (15) DEVICE: MMC FIRST UNIT: 417792 NO. UNITS: 4096 USED UNITS: 0
ID: 2ndLoke4 (16) DEVICE: MMC FIRST UNIT: 421888 NO. UNITS: 4096 USED UNITS: 0
ID: PARAM (17) DEVICE: MMC FIRST UNIT: 425984 NO. UNITS: 32768 USED UNITS: 0
ID: Kernel (18) DEVICE: MMC FIRST UNIT: 458752 NO. UNITS: 32768 USED UNITS: 0
ID: Kernel2 (19) DEVICE: MMC FIRST UNIT: 491520 NO. UNITS: 32768 USED UNITS: 0
ID: SYSTEM (20) DEVICE: MMC FIRST UNIT: 524288 NO. UNITS: 2457600 USED UNITS: 0
ID: CACHEFS (21) DEVICE: MMC FIRST UNIT: 2981888 NO. UNITS: 1720320 USED UNITS: 0
ID: HIDDEN (22) DEVICE: MMC FIRST UNIT: 4702208 NO. UNITS: 655360 USED UNITS: 0
ID: DATAFS (23) DEVICE: MMC FIRST UNIT: 5357568 NO. UNITS: 9891840 USED UNITS: 0
Click to expand...
Click to collapse
Additionally in oposite to other android phones I had, after reinserting baterry phone is booting instantly - I don't need press power button. Is it normal for GT-i8190n ?