Develop Bugs

[Q] No wifi, no bluetooth, and reception problems, please help?

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...

[Q] please help - did i brick my phone using exploid method

I followed the “how to root the HTC My touch slide (exploid method) (updated 01.26.11)” to the letter. (theunlokr.com)
Everything worked well until I got into clockworkmod Recovery
I then wipe data/factory reset in recovery mode
Then I installed zip from sd card ( I select slidemeroot2.zip)
After going through the process I get an “installation aborted” message
E: Failure at line 64 symlink busybox SYSTEM:xbin/zcip
(something to that effect. I'm out of town til tomorrow to verify the exact error)
Im very frustrated and afraid I may have bricked the phone
I had to turn the phone off and am scared of turning it back on until I have a fix
Please help

can you get into clockwork recovery???yes you tried to flash the wrong file

xoombie503 said:
can you get into clockwork recovery???yes you tried to flash the wrong file
Click to expand...
Click to collapse
Yeah i believe so.
After removing the battery last night i was able to get back into recovery i think
Will double check tomorrow when i get back home
What do you have in mind and how do i know the correct file to flash?
I'm just scared because it said during the method a few steps earlier: DO NOT REBOOT
I hope that i had past the stage where by rebooting it wont kill the phone

get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works

xoombie503 said:
get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works
Click to expand...
Click to collapse
Thnks so much will do that first thing when i get back in town tomorrow..
By the way this is with the assumption that by plugging my phone onto my computer via usb it will recognize my phone as a drive correct??
o btw im a newby at this, so that i understand correctly, i need to once in recovery cache wipe, then data factory reset before flashing the new room i would download. What is Dalvik cache etc..... is that another option i will see once in recovery?

xoombie503 said:
get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works
Click to expand...
Click to collapse
i tried it but no luck....
i did the wipe data/factory reset, i did wipe cache partition, then install zip from sd card, then choose zip from sd card, then picked haxspresso.zip i downloaded, then it says deleting files, then copying files, then i get E: can't symlink /system/xbin/su
E:failure at line 73: symlink /system/bin/su SYSTEM:xbin/su
installation aborted
Please help... im going crazy..
This is only my second rooting

pvalery00 said:
i tried it but no luck....
i did the wipe data/factory reset, i did wipe cache partition, then install zip from sd card, then choose zip from sd card, then picked haxspresso.zip i downloaded, then it says deleting files, then copying files, then i get E: can't symlink /system/xbin/su
E:failure at line 73: symlink /system/bin/su SYSTEM:xbin/su
installation aborted
Please help... im going crazy..
This is only my second rooting
Click to expand...
Click to collapse
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock

guitarist5122 said:
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock
Click to expand...
Click to collapse
interresting because the first part of this message is
"no app2sd partition found. Skipping format of /sd-ext.
data wipe complete"
I wonder if this has anything to do with it...
Please let me know

guitarist5122 said:
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock
Click to expand...
Click to collapse
you were so right!!!
i downloaded cmGinger 1.0_signed and flashed it and it worked
so what does this mean mtd partitions set up. Does this mean i can not get anyother rom or even the stock rom back in this fone??? how did u address it?

pvalery00 said:
you were so right!!!
i downloaded cmGinger 1.0_signed and flashed it and it worked
so what does this mean mtd partitions set up. Does this mean i can not get anyother rom or even the stock rom back in this fone??? how did u address it?
Click to expand...
Click to collapse
There is a thread in the dev section on how to setup custom mtd partitions. Basically you just assign memory where you want it. If you want stock roms you should assign the normal mtd setup (given in mtd partitions thread). Oh, you'll need s-off though. There is a guide for that too in the dev section. Its actually sticked at the top. Glad i could help
Sent from my T-Mobile myTouch 3G Slide using XDA App

Need help flashing Hboot to change partition layout

Hi, I've already S-offed my device and installed Leedroid. I don't have the SDK/ADB setup, so I downloaded the .zip file and attempted to install the zip through Recovery. I used the data++ partition layout. However, in Leedroid, when I go to Settings>Applications>Manage Applications, my total storage (All tab) is only 148 MB.
Is this normal, or what have I done wrong?

Its normal, you can increase the size from recovery. Or format the partition as ext4 and use SuperNova ROM instead of Leedroid

fterh said:
Hi, I've already S-offed my device and installed Leedroid. I don't have the SDK/ADB setup, so I downloaded the .zip file and attempted to install the zip through Recovery. I used the data++ partition layout. However, in Leedroid, when I go to Settings>Applications>Manage Applications, my total storage (All tab) is only 148 MB.
Is this normal, or what have I done wrong?
Click to expand...
Click to collapse
This is not normal. Don't mind the incompetent comment above. Settings->...blabla shows the size of the /data-partition and this should be 252 MB. Please do some reading on alpharev.nl!
It clearly says, that you DON'T flash hboot via recovery but have to rename the file, so hboot recognizes it and updates the partion-layout itself. Just follow the instructions.

Okay, thanks a lot. Have yet to tried it, but I have another question:
If a ROM does not specify the partition layout, does that mean I should flash the stock layout?
Btw I tried renaming it to PB99IMG.zip, booting into HBOOT, but it gives me an error about some CID thing and tells me update failed. I did some research and I think that's because I need a goldcard. Then I tried using the flasher tool and it works. But what's really strange is that I flashed the .img without reflashing my ROM or restoring my nandroid, and yet when I boot into my ROM, everything works, except that the /data has increased to 217MB (which is correct already). So do you need to restore nandroid or not?

fterh said:
Okay, thanks a lot.
Click to expand...
Click to collapse
No need, just hit the button.
If a ROM does not specify the partition layout, does that mean I should flash the stock layout?
Click to expand...
Click to collapse
in general, yes. But you can check the size of the system-Folder inside the rom.zip you want to flash and then choose a hboot-layout with sufficient /system-size. Then you should be fine. Maybe you have to flash a fix that moves market-downloads to sd-card (instead of /cache-partition, which may be too small for larger downloads, but afaik thats already built into most custom roms. However if larger market-downloads cause problems, you need to flash that fix).
But most of custom roms available in this forum clearly state in first post, which hboot-layout is best. But it's always down to the size of the /system-partition, so stock-hboot fits all.
But what's really strange is that I flashed the .img without reflashing my ROM or restoring my nandroid, and yet when I boot into my ROM, everything works, except that the /data has increased to 217MB (which is correct already). So do you need to restore nandroid or not?
Click to expand...
Click to collapse
If everythink works nice, then why bother?

Boot manager

I'm currently running DINC2HD, and was wondering how boot manager works exactly. I'm going to be camping on the 10th, and I'm not sure if I'll have a reliable charging source. I was planning on running MIUI while I was gone. I don't wanna have to restore a backup and take the extra time for that. Can someone please tell me exactly how boot manager works??
Sent from my DINC2HD

if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol

digitalsynner85 said:
if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol
Click to expand...
Click to collapse
I usually do too, but like I said, I'm gonna be camping, and I'm not sure when/where I'll be able to charge, so I was gonna use a ROM I KNOW has amazing battery life.
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?

tylerlawhon said:
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?
Click to expand...
Click to collapse
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, etc. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flashable backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.

ChrisDDD said:
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, etc. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flashable backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?

tylerlawhon said:
So, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?
Click to expand...
Click to collapse
I think it's recommended that you wipe all three images when you initially install a rom, but that's the 3 images Boot Manger creates. I was just making the point that you don't need to wipe anything on your phone's currently installed rom.
But yea, after that, Miui should install and run just fine. You will need to install GApps to get the market on MIUI, since Boot Manager needs to install itself on each new rom you instal. This is so you can manage and reboot to other roms from roms installed through it. After that, you should be able to reboot back and forth at will.

I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?

tylerlawhon said:
I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?
Click to expand...
Click to collapse
Sorry, I was thinking about CM7, which doesn't include with the market app.
I've always installed as Ext2... never had much luck with 4.

I tried Boot manager while running CM7 and I was able to install it but got a force close when I open the app, I also try it with MIK's Inc2 HD 3D rom and didn't work either.

[Q] Ext partition error. Unable to wipe data, install zips and restore backups

Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.

Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2

drixjp said:
Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.
Click to expand...
Click to collapse
Wrong section. Questions don't belong in the General Section. As for your problem, the best solution would be to just flash a stock ftf as mentioned by m1st3r1

m1st3r1 said:
Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app

drixjp said:
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot

m1st3r1 said:
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot
Click to expand...
Click to collapse
Like i said, it's a. 55 rooted with stock Rom. Boot loader unlock alowed: yes. I tryed every kind of fix in cwm already and nothing works.
Something I never tryed is via fastboot. How do I proceed with that?
Sorry, my android life just started yesterday, I don't have much knowledge
EDIT: Ok I solved. Actually it's not like a fix, it's just like putting a silver tape to handle the problem. For some reason I'm able to advance restore system backup via CWM recovery. Every time that I do that, my CWM recovery is fully functional again, i can install mod, rom, etc. But, when I reboot into system again, the problem comes back, but I can still use my android without any problems, I just can't install anything via CWM recovery. So basically, now, every time that I want to install something in recovery, first I need to advanced restore system, and than install the rom, mod or whatever. Than I backup again in case I want to install anything else in the future, to repeat the same procedure with the last backup.
I was just having some problems when I was trying to restore the system with a md5 missing error... something like that. I solved this problem by just creating a file.txt in the backup folder and than renamed it to nandroid.md5. Magically it was fixed.
Sent from my LT26ii using xda app-developers app