Hi there,
I have a HTC Desire Z and I"m having troubles with wifi, bluetooth and reception.
Whenever I turn on the wifi, it says "turning on.." and after few seconds "error"
For blue tooth it says "turning on..." and then it disappears as if I didn't press it.
Also, a lot of times when I make an outgoing call, the person on the other end cannot hear me the first time. I have to usually hang up and make the call again and they can hear me.
I've tried updating the RUU, rooting the phone and changing ROMS (cyanogen), but nothing worked so I returned it to stock and have it on the latest RUU.
I really don't know what to do any more PLEASE HELP ME!!
Thank you!
Anyone?????
Some more details would help.
Were these things ever working? When did they stop working? Any drastic changes prior to that?
ROM version?
I bought it used so im not sure of its history. Im sure it worked before.
its software number is 1.72.466.4
Kernel 2.6.32.21-geb0da35
Baseband 12.28e.60.140fU_26.04.02.17_M2
When the phone was on 1.35 I rooted it and tried cyanomod but the problem persisted. I upgraded from 1.35 to 1.72 and still the same problem
anyone have any ideas???
Ok so I rooted the phone and tried flashing different radios but the problem persists! Could this be a hardware issue?
You are wiping everything clean, aren't you? wipe data/factory reset - wipe davlik - format system - format boot. It could be that you are overlooking one small but important thing.
Ive tried data wipe
How dyu do wipe davlik, format system, format..?
Make sure you have the ROM that you want to flash on the root of the sd card before you do the following:
If you haven't done this already, download ROM Manager from the market, install it and then select from within to flash clockworkmod recovery. Once that is installed, then reboot into recovery. You'll have options there and you scroll through the options in recovery by using the volume up and volume down bar. to select an option, click on the track pad. To go back to a previous menu, use the power button.
first wipe data/factory reset, the go to advanced and look for the option to wipe Davlik, then go back to mounts and storage and format system and format boot. That should clean your system up completely for a new install.
Then find the option in the menu to install zip from sd card, and reboot your system.
when i try to wipe davlik, it says
"E:Can't mount /dev/block/mmcblk1p2"
(File exists)
then when i try to install the ROM from my sdcard,
it says
"E:Can't open /sdcard/rom/zip (bad)
Installation aborted"
help?
wadokai said:
when i try to wipe davlik, it says
"E:Can't mount /dev/block/mmcblk1p2"
(File exists)
then when i try to install the ROM from my sdcard,
it says
"E:Can't open /sdcard/rom/zip (bad)
Installation aborted"
help?
Click to expand...
Click to collapse
The ROM zip file shouldn't be in a folder on your sd card...not sure it will flash that way. Move it out of that folder and put it directly on your sd card...in no folder. You may have to use a card reader on your computer to do that. You may also have a bad sd card, a bad zip file (the ROM), or your sd card may not be formatted correctly. It needs to be in the fat32 format. The first error re mmcblk1p2 is not a problem.
Sent from my HTC Vision using XDA App
Okay so i tried official roms and it didn't work, so I tried a custom rom
i put it in the main sd card (not in any folder)
the custom rom installed
tried wifi/bluetooth but still nothing :-(
wadokai said:
Okay so i tried official roms and it didn't work, so I tried a custom rom
i put it in the main sd card (not in any folder)
the custom rom installed
tried wifi/bluetooth but still nothing :-(
Click to expand...
Click to collapse
You may have to reboot first. Try that if you haven't. Do you have a Desire Z or a G2?
It's the desire Z
okay so I wipe/data factory set, wipe davlik, format system, format boot, and then reboot?
Then enter into recovery by vol down + power, then recovery?
and then install the custom rom or try another official rom?
wadokai said:
It's the desire Z
okay so I wipe/data factory set, wipe davlik, format system, format boot, and then reboot?
Then enter into recovery by vol down + power, then recovery?
and then install the custom rom or try another official rom?
Click to expand...
Click to collapse
no, that was only to install the ROM, just try a reboot to see if that fixes the wifi issue. nothing more. reboot=restart
Okay so I reboot the phone after installing the custom rom,
still no dice. no wifi or bluetooth
Wow! The only thing that you could try to see if its not a hardware issue in my opinion is to change the radio. You can read more about it in this thread: http://forum.xda-developers.com/showthread.php?t=799208
I checked back and in one of your previous posts you said that you are using the radio that appears first on the list in the first posting in that thread - Vision_RADIO_12.28e.60.140f_26.04.02.17. You could try re-flashing the radio you have now, or you could try another one.
You have to understand, as what's posted in that thread, that if you don't do everything correctly you could brick your phone meaning that it will be nothing more than a paperweight if you don't do everything correctly.
Please read that thread carefully. You have to understand the risk you are taking...and you'll have to know how to flash using the fastboot method.
AND...after all that trouble, it could still be a hardware issue!
With normal rom, i tried flashing different radios...didn't solve anything.
Means hardware then, yes?
wadokai said:
With normal rom, i tried flashing different radios...didn't solve anything.
Means hardware then, yes?
Click to expand...
Click to collapse
I think so.... is the phone receptions still bad? can you go online at all?
edit: if you know how to flash a radio, try flashing another radio now with a custom ROM installed....who knows?
I tried with custom rom too, it didn't work :-(
I don't know about the reception but the internet always works regardless.
Fml.... I don't know what i can do to fix the hardware...
I was wondering if anyone can help me. I have looked at the other posts which relate to a very similar problem, but none of them have quite the same problem as me. Basically, all the phone will do is show the 'HTC Quietly Brilliant' loading screen and it is stuck in a reboot cycle. I can access the bootloader and I have tried to factory reset with no luck.
I was watching a YouTube tutorial on how to flash CM10 onto my One X (I do have ClockworkMod and all of that stuff installed already). Everything was going well, but the video only briefly (for maybe a second) mentioned the fact that you have to put the CM10 zip folder onto the phone storage before you flash the boot.img. I went on and followed the steps and tried to flash the boot.img, but as I said earlier, all the phone will do is reboot over and over again. I have charged it to full battery so this should not be a problem when I go to fix it.
I would be really grateful for any help on the subject as I contacted the person who made the tutorial, and he has not responded. Thanks in advance.
Havoc2510 said:
I was wondering if anyone can help me. I have looked at the other posts which relate to a very similar problem, but none of them have quite the same problem as me. Basically, all the phone will do is show the 'HTC Quietly Brilliant' loading screen and it is stuck in a reboot cycle. I can access the bootloader and I have tried to factory reset with no luck.
I was watching a YouTube tutorial on how to flash CM10 onto my One X (I do have ClockworkMod and all of that stuff installed already). Everything was going well, but the video only briefly (for maybe a second) mentioned the fact that you have to put the CM10 zip folder onto the phone storage before you flash the boot.img. I went on and followed the steps and tried to flash the boot.img, but as I said earlier, all the phone will do is reboot over and over again. I have charged it to full battery so this should not be a problem when I go to fix it.
I would be really grateful for any help on the subject as I contacted the person who made the tutorial, and he has not responded. Thanks in advance.
Click to expand...
Click to collapse
Have you placed the ROM's zip file in your phone's root?
If you haven't, go to fastboot and flash CWM 5.8.4.0 and then go into recovery > mounts and storage > mount USB. Now place your ROM into the storage and flash it via install zip from SD card. Don't forget to wipe data partition, cache partition and Dalvik cache.
If this wasn't your case, just try erasing data partition, cache and Dalvik cache again.
If it still doesn't work, try flashing another ROM.
Thank You!!!
SidDev said:
Have you placed the ROM's zip file in your phone's root?
If you haven't, go to fastboot and flash CWM 5.8.4.0 and then go into recovery > mounts and storage > mount USB. Now place your ROM into the storage and flash it via install zip from SD card. Don't forget to wipe data partition, cache partition and Dalvik cache.
If this wasn't your case, just try erasing data partition, cache and Dalvik cache again.
If it still doesn't work, try flashing another ROM.
Click to expand...
Click to collapse
Thank you so much. I had CWM 5.8.4.0 already, all I had to do was mount USB and put the CM10 zip on the phone storage! I also wiped the caches, the phone works better now than it ever has . Thank you so much again, really appreciate the help
I started having this problem ever since I upgraded my phone to 4.1.2 T989UVMC6. Sometimes when the power button gets accidentally pressed for 10 seconds in my pocket, the phone vibrates 3 or 4 times, then gets to the Galaxy SII screen and gets stuck there. A couple of times it got to the glowing Samsung logo, but then it got stuck there. I tried everything to get it to boot (rebooting, wiping cache, dalvik, fixing permissions) but nothing worked. I searched everywhere for a solution but got nothing. Some people said it's caused by the Preload partition, but that got me nowhere. The only thing I could do at that point was to restore my latest backup. I would lose all my changes since the backup but at least it would boot and even reboot normally.
After many experiments, I realized the problem is with the Data partition... So my current solution when it gets stuck at boot:
1. Reboot into recovery.
2. Create a backup of just the Data partition (you can do a full backup if you want but this way is just faster).
3. Restore the backup you just created.
4. Run the Infamous Cache Wipe (probably not necessary, but doesn't hurt).
5. Reboot and enjoy!
The only problem I noticed so far, when doing the backup to external SD, I would lose all my messages (SMS and MMS). Doing the backup to internal SD, everything gets restored normally.
If anyone has more insight into this issue, or has a better and more permanent solution, please share.
If this helps you as much as it helps me, please hit Thanks
I never heard that before!!! Thanks! :s
Sent from my cell phone telephone
Dont mean to start a new thread but no one is answering me.
My phone just boots to the "Saumsung Galaxy Note II" screen and is stuck there.
If I do volume up and home, it goes into the recovery screen but I m afraid using odin would erase everything.
I want to save my data, what should I do?
i cant do anything within recovery.
now i have a bunch of of failures..
i can reboot, apply update from adb, or external storage, wipe data, wipe cache.
i did what you told me, to wipe cache, the bootloop persists.
which rom do i use? i dont remember what i used.
Please specify what I need to download in order to save my data, thanks!
Hey guys!
I have flashed my Samsung Galaxy Nexus (i9350) with CM-12.1-20160117-NIGHTLY. I first installed the new CM recovery (with the same build date) via Fastboot, wiped Cache (but not Dalvik Cache, since the new Recovery had no option for this).
My device was then stuck in some sort of "bootloop". It gets to the "Android is updating ..." screen, where it says it compiles "app X of Y", then reboots and starts over again.
So I booted the device back into the bootloader, flashed back the old CM recovery (with build date 2016-11-17) via Fastboot, formatted System, Cache and wiped Dalvik Cache, then installed the old ROM only to find it being stuck in a bootloop too with the AMOLED display increasing and decreasing in brightness, but the ROM's not getting anywhere (not even to the point where it says "Android is updating ..." - it's just showing the boot animation and the screen "goes mad").
So I went back to the "old" CM recovery, formatted System, Cache, wiped Dalvik Cache, rebooted to bootloader, flashed the "new" CM recovery via Fastboot, flashed the "new" ROM again, wiped Cache again with the "new" Recovery ("new" recovery does not offer to format System or wipe Dalvik Cache, which is why I did it with the "old"), again "Android is updating ..." loops.
Now since System, Cache and Dalvik-Cache are basically "clean", I'm afraid that Data might be corrupt and thus my data on the phone might indeed be lost. (I have backups, but they are four months old.) Formatting Data might make the device bootable again, but I'd really like to do some sort of "data recovery". I mean "normally" flashing a ROM doesn't corrupt your data partition, right?
I don't know how to access the data partition though, since the device won't boot. The recoveries I have unfortunately don't allow ADB access either. Any chance? Or should I hit "wipe data / factory reset" and kiss the data goodbye? (Like I said, it's not "much" that will be lost, though I'd really like to keep it if it's "somehow" possible.)
Thanks a lot for your advice!
EDIT: I managed to gain MTP and ADB (root) access by booting into TWRP via Fastboot.
I now backed up the entire MTP storage, as well as the following:
- "/data/data/com.threema.app"
- "/data/data/com.android.providers.telephony"
- "/data/data/com.android.providers.contacts"
- "/data/data/com.android.providers.userdictionary"
Will this be sufficient to get my SMS, contacts (stored on phone), custom dictionary (for swipe recognition) and Threema messages back?
TWRP has a mount as MTP functionality that will allow you to access data.
You can also use adb while you're in fastboot adb pull allows you to pull anything as long as you have the path so adb pull /data should be able to pull those contents.
For me TWRP mount as MTP is a much easier and reliable option.
Thanks! I managed to pull off "/data" using TWRP, wipe "/data", restore files selectively. Works, even on the new nightly, which now runs like a charm.
Do you have an idea, why CWM does not support ADB access? I remember that it used to support it some years ago.