Hi all,
I'm facing a strange problem from my WM6.1 phone (HP614c), the WAV1 doesn't start automatically at startup (therefore the speaker is not enabled), also the keypad-wheel is disabled.
At first I believed that its a hardware problem but I can have it fixed after a factory reset. The problem is that after installing one or two programes (I'm pretty sure that its not related to the prog that I want to install), it always ends up with the same result. The WAV1 doesn't start at boot.
I will appreciate any help in tackling this problem, or in writing a boot script to start WAV1.
Thanks in advance,
Santiago
Hello
I have unlock and root my phone.
In the beginning everything was OK, but when I have try to change my ringtone the phone have freeze and after that is restarting.
I have the same problem if I try to start the iGo software - it starts, but on the first window where I have to select the language it freeze and restart after that.
The same problem if I try to look some movie in internet!
I have made a test with the HTC test program and have find out that every time when the loudspeaker is involved the phone is restarting!
Some ideas?
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).
Hello everybody,
First, sorry for my english. I am actually an exchange student in Canada (Montréal) and i come from France so my english is not that good.
Secund, i have a big issue with my Asus Zenfone 2. I explain, today i was hoping to install the update wich bring Marshmallow on my smartphone, it did not come by the update system so i download it. I was also hoping that this update can correct some problem that i experience since a little fall of the phone.
(There was two problem, the time to fulfill the battery increased, it's more than 8 hours now, before in 4 hour it was done and the sim card isn t recognized anymore so it is really boring even if i don t take a canadian number yet and the computer seems to do not recognize my phone anymore (before the cache problem.)
So i downloaded the update and try to install it in the recovery but at this moment i had my first real problem, i have an error before the recovery menu. I read that i need to push alternatively the sound button and the power buton to resolve that issue (i also read that it comes from a cache problem) and indeed i arrived in the recovery. And i did here one big mistake i think. In order to don t have this error anymore, i choose to reinitiate the cache, so it begun but it was really slow and i thought that a bug occure so i pressed the power button until it stop.
Since i have an error and i can t go in the recovery anymore even if i press both of the buttons like before, i just have this error : e:/ can't mount cache/recovery/last_locale and an alternative dark screen and error image.
Thank you so much by advance,
Elanakin
Hi i have bootloop problems on this device. When i do factory reset in recovery mode samsunf logo blinks as it wants to start system but it restarts. Then second time samsung logo doesnt even finish until i do factory reset then logo blinks again and restarts after some time.
The code is (reboot recovery cause is check_boot_mode recoverybootmodewithkey)
Block based ota
Ive tried to flash device multiple times with different stock roms with same results.
If i flash with oreo its the same error code but with addition when doing fastory reser something about some cache in first deletion and a number 0
In pie that code is not present which i assume that device is ment for pie. Both frp and oem are locked.
When i flash combination file its rpmb provisioned and rpmb fused 1. In z3x box there is no option to fix that. And that is strange because as i remember while i was doing repair on samsung s8 it was easy. Factory binary was there but not on this budget model which is strange. I even tried to force error so it triggers emergency recovery mode for smart switch but smart switch is just aweful. I dont even get recognition in that program. It shows as unsuppported model. I reinstalled drivers as well it just doesnt work. Now i would be glad and it would be awesome to get into fastboot mode just so i write down commands. Adb sideload doesnt have those options. Since i understood adb and fastboot for me its number one solution for everything. But how the hell am i supposed to get into fastboot on this model. Im pretty sure block based ota is sign that its blocked becuase of oem unlock aka locked bootloader. Its a friends phone and i tell people dont do stuff if you dot know ehat you are doing. But even locked bootloaders and frp locked are fixable. Especially with multiple brains on XDA and GSMforums.
Does anybody have any solutuon to this problem because this is some kind of new security method which was not present on like 2 years before.
P. S Is there any combination out there made out of Pie?
I fixed the issue. Front camera was defected. Some type of short circuit. Main camera auto focus mechanism also defected. It works allright as soon you detach all cameras. The only problem which i have with this device is that Samsung is using same concept as HTC. One camera defected all cameras not working. This is new from Samsung because in past when one camera brakes camera app still works. Autofocus mechanism can break with fall of the phone. Its not an software issue!!!
i have a similar problem do find solution?
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you