Greetings.
I have phone for several hours, but already had some strange behaviour. I am using modified image by xda-developers -- RC4-RC30. I can't say if bug I am talking appear after or before puting modified OS on my device.
So about the bug itself. Sometimes my phone became to react on pressing "Menu" button just by vibrating. And not poping menu. Sometimes if you press "Menu" several times you getting it finaly (while you already a bit stressed of this vibrating beast on your hands), sometimes not. Some time phone working ok after reboot. But then after time it's start to vibrating again. Sometimes it's also vibrating on pressing other keys (like home). If you press "Home" and hold it for a while to get list of active app, it list could be with just only "Gmail" while phone is already became to vibrating-mad.
Anybody have a idea what's it? Kinda annoying and making my device nearly useless (it's still also the phone, it should work all the time fine).
Regards.
UPD: This **** appers sometimes even before SIM PIN Code entered, right after reboot.
just to solve some questions.
Yes I did hard reset (Rebooted with Home+Back down, ALT-L, ALT-W), and no it didn't helped.
reflashing didn't helped as wel.. Next step is flashing to native R29 i think.
anyone any idea, how pressing button could cause vibrate? It's probably standard indicating of some kinde of internal kernel faults or hardware errors or something like this? Or it's probably just hardware problem this causing comutation vibrating engine to power when i pressing button?
Btw, it's not only happen with "Menu" button, but with all. And sometimes it's just vibrating. Rebooting is solving problem for a while.
If we see dmesg on phone after getting my problem you could see this:
Code:
<6>[ 1743.833185] binder: 825:910 transaction failed 29189, size 0-0
<6>[ 1743.833572] binder: send failed reply for transaction 89479, target dead
<6>[ 1743.836898] binder: 825:1207 transaction failed 29189, size 0-0
<6>[ 1743.837508] binder: send failed reply for transaction 89399, target dead
<6>[ 1744.943429] binder: 825:830 transaction failed 29189, size 0-0
<6>[ 1744.943572] binder: send failed reply for transaction 89600, target dead
I can't remember is see this message before getting this problem. So we come to idea it's an hardware problem, or bug in modified OS.
Related
Hello! I encounterd this problem and i'm really scared because the pda is not mine. The thing is that when i tried to tap on the Messages icon - no rezult. i made a soft reset but after that i couldn't enter my pin code. reset again and this time i managed to enter the pin but then my charmer began to thing for so long that it didn't seem to end.What should i do? I hope this sounds familiar to you. Thank you in advance
Can be due to incompatible software issues, I guess. Since the phone is not yours, it is difficult to say what the owner has done on the phone, or probably it ought to be like that. As for the PIN, I heard that, it has an exponential time delay safety on it to prevent bruteforce entry, e.g. 1st time incorrect PIN = 2 seconds delay, 2nd = 4 seconds, 3rd = 8 seconds, 4th = 16 seconds, etc. Probably thats what it is doing?
Hard reset fixed everything
Hi all,
I had a terrible catastrophic failure today with my 1-month old HTC Wildfire. I bought my device new, unlocked, in Singapore.
Here's what happened:
Today I received an ordinary SMS (like I have hundreds of times before in the past few weeks) and when I picked up the phone off of the desk, flipped on the screen, and slid my finger to unlock it, I saw a brief error message in a dialog on top of the Messages app. It was something like "com.something .... ", I didn't get a good look at the error but it didn't really mean anything to me at the time. The SMS that I received was then lost (I knew who it was from, but the message was not showing up). A few minutes later, I heard another SMS notification. No error message this time, but again the message did not show up in my Messages app.
So, I pressed the power button to power cycle the phone. After I shut it down, I turned it back on, saw the white screen with HTC logo, then black. It was dead. No amount of pressing buttons did anything.
After a few minutes, I removed the battery and it turned on again. Again, white splash screen and then darkness. Repeated this several times and same result.
Finally, I googled how to do a hard reset. I followed the instructions, held the volume down button while pressing power, cleared the memory, after it restarted it went right back to the white bootloader screen, flashed some error messages, and now I'm stuck in the bootloader. When I select the RECOVERY option, I get a quick screen with something like:
SD Checking ...
Loading [SOMEFILE.zip] ...
No Image!
Loading [SOMEFILE.zip] ...
No Image!
....
....
No Image or Wrong Image!
Can anybody help??! I don't know what to do now. I've searched for this "No Image or Wrong Image" message on these forums, but all the results are about rooting and loading different ROMs. I've never rooted or anything out of the ordinary, I just want the stock OS back and operational.
Btw ... I'm an Android noob, but an experienced Linux/Mac user and 10-year software developer.
Any help is greatly appreciated.
Thanks,
Nate
Recovery mode is something else.
To do a hardreset try the following:
Performing a factory reset using phone buttons
If you cannot turn on your phone or access the phone settings, you can still perform a factory reset by using the buttons on the phone.
1. With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
Note: If you are not sure whether your phone's power is turned off, remove and then reinsert the battery.
2. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
3. Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
4. Press VOLUME UP to start the factory reset.
Click to expand...
Click to collapse
Source : http://www.htc.com/www/howto.aspx?id=3567&type=1&p_id=316
Call HTC support. I had a problem with my previous HTC phone, and they took me through diagnositcs over the phone, and when they diagnosed a hardware fault, sent a courier to pick it up from me the next day. This was when the phone was 18 months old. No receipt was necessary, they used the serial number/manufacture date.
Downside: the phone was gone a week, and came back still broken. It was sent away again, and came back fixed. So painfully without it for two weeks, but not a bad experience.
(edit: it was a similar problem: I upgraded to windows 6.1, and my phone wouldn't get past the initial hardware/boot screen)
I tried the hard reset procedure several times. Every time it's the same thing. After it clears the memory, it says "Reboot in 5 seconds..." and then when it reboots, it goes back to the bootloader screens.
I've contacted HTC support via email, and I'm bringing it in to their support center in Singapore tomorrow. I really hope it doesn't take a week ... I'll keep you updated.
Fixed.
I just got my Wildfire back today after a full week in the repair center. Apparently they replaced the main system board. No other explanation for the problem was given.
The repair process itself was hassle free, although I was frustrated by not having my phone for a week. Ended up having to buy a cheap basic phone for $55 to get by on SMS and voice.
Ok so I have been having issues for a while with my G1. Most likely my fault. Most recently it started not reacting to the touch screen (nothing worked at all with the screen only the trackball) then txt messages would not send so I reset the phone. At that point it never re-booted. I am currently un able to acccess any nandroid or any boot at all. Not a single function will boot my phone. Pushing power does not produce anything. No vibrate not even an led when its plugged it. Any one have nay ideas how to fix this? Thanks
Power = no action at all
Ive tried Power + Camera = no action
Power + home = nothing still
Ive removed battery and tried again... nothing...
Remove SD card... nothing...
Hi everyone,
Just got a brand new Lumia 1020 (bought on ebay to a German retailer, so that's some Polish version whereas I'm in France, but whatever), and the camera ain't working. Somehow I can get it to take some pictures sometimes, but most of the time it's just like the camera app just doesn't detect any camera (rear or front).
I guess it's some kind of software failure, since whenever the camera app does actual detect the camera, the picture will freeze at some point exactly when I receive a notification or other kinds of actions (opening some menus, opening another app, ...).
I went through all upgrades, it didn't give any result. Hard reset doesn't work either. So I suspect some kind of corrupt file in the original files. Could happen after all.
My last option is to flash the damn thing, and I followed the tutorial, however when I reach the point to start the actual flashing, the phone isn't detected. I gathered that it should be in "flash mode", which you reach by shutting down the phone and pressing "vol down + power" for a few seconds. I did that, but it will only power up the phone as usual.
The question is : how the **** do I get into that stupid flash mode? Is it even real?
Many thanks
Xowap said:
Hi everyone,
Just got a brand new Lumia 1020 (bought on ebay to a German retailer, so that's some Polish version whereas I'm in France, but whatever), and the camera ain't working. Somehow I can get it to take some pictures sometimes, but most of the time it's just like the camera app just doesn't detect any camera (rear or front).
I guess it's some kind of software failure, since whenever the camera app does actual detect the camera, the picture will freeze at some point exactly when I receive a notification or other kinds of actions (opening some menus, opening another app, ...).
I went through all upgrades, it didn't give any result. Hard reset doesn't work either. So I suspect some kind of corrupt file in the original files. Could happen after all.
My last option is to flash the damn thing, and I followed the tutorial, however when I reach the point to start the actual flashing, the phone isn't detected. I gathered that it should be in "flash mode", which you reach by shutting down the phone and pressing "vol down + power" for a few seconds. I did that, but it will only power up the phone as usual.
The question is : how the **** do I get into that stupid flash mode? Is it even real?
Many thanks
Click to expand...
Click to collapse
make sure the phone is fully booted and all that jazz then you hold the power button and volume down. The second it vibrates click retry on nokia care suite
lolwutwin said:
make sure the phone is fully booted and all that jazz then you hold the power button and volume down. The second it vibrates click retry on nokia care suite
Click to expand...
Click to collapse
Well, if I do that when the phone is booted, it lowers the volume down to "vibrate", then I feel a vibration and the "pull down to shut down" thing.
Hitting "retry" at this time gives no results
Sometimes, I get this error though:
Code:
DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
Exception:
System.Runtime.InteropServices.COMException (0x8400AC35): DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
at FuseLib.DtlConnectionClass.ConnectToMedia()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryConnectionManager..ctor(FuseLoader fuseLoader, IConnection connection, UserInteractionDelegate userInteractionDelegate)
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
Xowap said:
Sometimes, I get this error though:
Code:
DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
Exception:
System.Runtime.InteropServices.COMException (0x8400AC35): DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
at FuseLib.DtlConnectionClass.ConnectToMedia()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryConnectionManager..ctor(FuseLoader fuseLoader, IConnection connection, UserInteractionDelegate userInteractionDelegate)
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
Click to expand...
Click to collapse
I'm assuming you're using Nokia Care to flash the phone, i would recommend to use Nokia Software Recovery tool, as it does all the work for you, you just press the install button.
If you get errors even then, i'd recommend checking/changing (in case it's not an original one) the USB cable, also if the USB ports are working properly.
VSparxx said:
I'm assuming you're using Nokia Care to flash the phone, i would recommend to use Nokia Software Recovery tool, as it does all the work for you, you just press the install button.
If you get errors even then, i'd recommend checking/changing (in case it's not an original one) the USB cable, also if the USB ports are working properly.
Click to expand...
Click to collapse
Changing the USB cable and the USB ports already has been done, however I did not know about Nokia Software Recovery, thanks for the heads up I'll try that
G'day everyone!
First time posting to XDA, from what I've read and seen you guys are an awesome community and I hope that you will be able to help me out with my bootloader error!
My phone has bricked itself for a couple of hours now.
Information about the bootloader error:
' Bootloader exception
[RST_STAT=0x10000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
[...]
- There is a completely black screen with red text at the top specifying the error
- I have attached a photo of the exact error
- This specific type of error I've only seen only twice on the internet, a couple of years back without a confirmed solution. It seems to be quite rare...
- I understand that my aim is to get it to download mode by holding vol down, power and home. I've been trying this for hours. What's different to when I try it compared to other people is that the screen doesn't periodically go black, then back to the error. People say you keep trying and eventually it will work. But mine is not even periodically going to a black screen.
- I've tried many other combinations, even some really dodgy youtube videos but nothing is even budging it off this error screen.
- I have let it go dead multiple times, put on charge and hold the buttons to attempt download mode but it still won't budge.
I'm at a loss of what I can do. I bought the phone quite a while ago now (6 years), second hand but it was pretty much brand new. I've never had an issue with it. I will add that the bootloader error seemed to crop up after putting in on charge briefly. I've seen info about doing OTA updates when putting it on charge can cause this issue, but I'm pretty sure I never used OTA updates...
Screenshot of the error: 'https:// ' + 'imgur.com/0KICjVv'
Any help or ideas that you have would be very appreciated. Cheers
Danyon Farrell said:
G'day everyone!
First time posting to XDA, from what I've read and seen you guys are an awesome community and I hope that you will be able to help me out with my bootloader error!
My phone has bricked itself for a couple of hours now.
Information about the bootloader error:
' Bootloader exception
[RST_STAT=0x10000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
[...]
- There is a completely black screen with red text at the top specifying the error
- I have attached a photo of the exact error
- This specific type of error I've only seen only twice on the internet, a couple of years back without a confirmed solution. It seems to be quite rare...
- I understand that my aim is to get it to download mode by holding vol down, power and home. I've been trying this for hours. What's different to when I try it compared to other people is that the screen doesn't periodically go black, then back to the error. People say you keep trying and eventually it will work. But mine is not even periodically going to a black screen.
- I've tried many other combinations, even some really dodgy youtube videos but nothing is even budging it off this error screen.
- I have let it go dead multiple times, put on charge and hold the buttons to attempt download mode but it still won't budge.
I'm at a loss of what I can do. I bought the phone quite a while ago now (6 years), second hand but it was pretty much brand new. I've never had an issue with it. I will add that the bootloader error seemed to crop up after putting in on charge briefly. I've seen info about doing OTA updates when putting it on charge can cause this issue, but I'm pretty sure I never used OTA updates...
Screenshot of the error: 'https:// ' + 'imgur.com/0KICjVv'
Any help or ideas that you have would be very appreciated. Cheers
Click to expand...
Click to collapse
Yeah its been posted multiple times.. this is mostly not a hardware issue but just a wrong bootloader flashed or such..
The solution that worked for me was :
Hold home button, and you will get to sbl upload mode
Hold vol down+home+power button while on this upload mode, phone will try to reboot.
The moment phone goes black (before it starts rebooting) , immediately release and re-hold the vol down+home+power button and you would be in download mode..
Immediately flash the correct firmware for your phone now.. and it should become alive again..
Sent from my hero2lte using XDA Labs
Connect usb from the pc and hold the the volume buttons. If boot into download mode is successful, flash the correct boot loader along with the other firmware files. If that doesn't work, try using fastboot to reboot. Good luck :good: