Related
My phone works perfectly except I can't answer calls, when I press answer/ignore it freezes until it goes to voicemail and then comes back. I've flashed multiple roms and had the problem with all of them. I'm not using any special themes or anything, and the only software I ever install are HD Tweak and Finger Keyboard 2.1 and my radio 1.14.25.24. Here's a list of what I've done since I had the phone:
1. Bought phone. Flashed HSPL. Flashed Laurentius L26, no problems. Was being lazy so I didn't hard reset after flashing.
2. Flashed Dutty R14. Didn't hard reset after flashing. No problems for awhile and then the problem of not being able to answer calls appeared.
3. Flashed EnergyRom wm6.5 rom. Hard reset twice after. Still having problem where I can't answer calls.
4. Flashed Dutty 3.9XT wm6.1 rom. Hard reset twice after. Still having problem where I can't answer calls.
If anyone can help me figure out why my phone is doing this I'd really appreciate it, I'll even pay you some money on PayPal if you like because I really want to fix it. Here are some ideas I had as to why it's not working:
- Problem with rom flash. No, because I tried it with 3 different roms so far and had the same problem.
- Touch HD isn't fast enough to run wm6.5 and be stable. No, because I tried it with a wm6.1 rom too and had the same problem.
- Someone suggested it might be a problem with the battery. No, because I ordered new replacement batteries and tried them and had the same problem.
- Some of the settings in HD Tweak are incompatible with something in the roms I'm using. Maybe, is this possible? I don't really change much, just the softkeys and the highlight color and things like that.
- Screwed up something in the SPL or something because I didn't hard reset after flashing the first 2 roms. Maybe, is this possible?
- Dropped my phone and somehow managed to break nothing but the mechanism involved in answering calls. Maybe, is this possible?
Today I'm going to reflash HSPL, flash the stock HTC rom, hard reset twice, and see if I still have the problem. I don't know what else to do or what other possibilities there are. If anyone can shed some light on this issue, that would be great, because I really don't want to have to buy a new phone. Thanks
Did you try another SIM?
rpimps said:
My phone works perfectly except I can't answer calls, when I press answer/ignore it freezes until it goes to voicemail and then comes back. I've flashed multiple roms and had the problem with all of them. I'm not using any special themes or anything, and the only software I ever install are HD Tweak and Finger Keyboard 2.1 and my radio 1.14.25.24. Here's a list of what I've done since I had the phone:
1. Bought phone. Flashed HSPL. Flashed Laurentius L26, no problems. Was being lazy so I didn't hard reset after flashing.
2. Flashed Dutty R14. Didn't hard reset after flashing. No problems for awhile and then the problem of not being able to answer calls appeared.
3. Flashed EnergyRom wm6.5 rom. Hard reset twice after. Still having problem where I can't answer calls.
4. Flashed Dutty 3.9XT wm6.1 rom. Hard reset twice after. Still having problem where I can't answer calls.
If anyone can help me figure out why my phone is doing this I'd really appreciate it, I'll even pay you some money on PayPal if you like because I really want to fix it. Here are some ideas I had as to why it's not working:
- Problem with rom flash. No, because I tried it with 3 different roms so far and had the same problem.
- Touch HD isn't fast enough to run wm6.5 and be stable. No, because I tried it with a wm6.1 rom too and had the same problem.
- Someone suggested it might be a problem with the battery. No, because I ordered new replacement batteries and tried them and had the same problem.
- Some of the settings in HD Tweak are incompatible with something in the roms I'm using. Maybe, is this possible? I don't really change much, just the softkeys and the highlight color and things like that.
- Screwed up something in the SPL or something because I didn't hard reset after flashing the first 2 roms. Maybe, is this possible?
- Dropped my phone and somehow managed to break nothing but the mechanism involved in answering calls. Maybe, is this possible?
Today I'm going to reflash HSPL, flash the stock HTC rom, hard reset twice, and see if I still have the problem. I don't know what else to do or what other possibilities there are. If anyone can shed some light on this issue, that would be great, because I really don't want to have to buy a new phone. Thanks
Click to expand...
Click to collapse
Hi rpimps,
I think that would be a good idea, flash back to stock, check for any differences, if everything works ok, then try flashing to a custom ROM again.
It might be an idea to try out a different radio version, for example, try 1.17 as this could improve certain built in feaures of your phone, especially since radio versions are known to work only in specific regions, it may work out better for you overall
Also, if not already cooked into the custom ROM of your choice, you should also install the RIL version that matches your radio version - 1.17 Radio supports RIL version 1.14 (1.14.25.24), which you can download the RIL via this link, at the bottom of post #1 - read this section as it also explains how to install the RIL.
I recently remember another member mention that their phone would sometimes hang when/after receiving a call, this was solved by installing the associated RIL - a layer in an operating system which provides an interface to the hardware's radio and modem.
Best regards.
Just to see if call mechansm works;
- try to record something (to check mic)
- try front speaker (i dont know how to do this)
- check if vibration works. (vibrate on connect may be on)
I guess your gsm radio works well since you can receive calls. Try to use windows original phone canvas instead of touchflo 3d. Dont know what to check more Its strange.
simplistian said:
Did you try another SIM?
Click to expand...
Click to collapse
I did that just now and it had the same problem (on the HD) no matter what sim I put in it.
Mastoid said:
Hi rpimps,
I think that would be a good idea, flash back to stock, check for any differences, if everything works ok, then try flashing to a custom ROM again.
It might be an idea to try out a different radio version, for example, try 1.17 as this could improve certain built in feaures of your phone, especially since radio versions are known to work only in specific regions, it may work out better for you overall
Also, if not already cooked into the custom ROM of your choice, you should also install the RIL version that matches your radio version - 1.17 Radio supports RIL version 1.14 (1.14.25.24), which you can download the RIL via this link, at the bottom of post #1 - read this section as it also explains how to install the RIL.
I recently remember another member mention that their phone would sometimes hang when/after receiving a call, this was solved by installing the associated RIL - a layer in an operating system which provides an interface to the hardware's radio and modem.
Best regards.
Click to expand...
Click to collapse
Here's what I did today:
1. Reflashed HSPL. Hard reset.
2. Couldn't find a working stock rom so I just reflashed Dutty 3.9XT. Hard reset.
3. Installed 1.17 radio and rilphone 1.14 like you recommended.
4. Didn't install anything else. Tested phone right after install and it's still having the problem.
barisahmet said:
Just to see if call mechansm works;
- try to record something (to check mic)
- try front speaker (i dont know how to do this)
- check if vibration works. (vibrate on connect may be on)
I guess your gsm radio works well since you can receive calls. Try to use windows original phone canvas instead of touchflo 3d. Dont know what to check more Its strange.
Click to expand...
Click to collapse
I can call other people and it works fine. And actually about 10% of the time I CAN answer calls, and when it works it works perfectly. But 90% of the time it won't let me answer.
I might just have to put this phone on ebay and go back to my Diamond
rpimps said:
I can call other people and it works fine. And actually about 10% of the time I CAN answer calls, and when it works it works perfectly. But 90% of the time it won't let me answer.
I might just have to put this phone on ebay and go back to my Diamond
Click to expand...
Click to collapse
that's a shame dude, not sure what else to suggest... it sounds like a hardware related issue as you have repeatedly tried flashing different firmware one on the phone... i suppose it's not under warranty?
Mastoid said:
that's a shame dude, not sure what else to suggest... it sounds like a hardware related issue as you have repeatedly tried flashing different firmware one on the phone... i suppose it's not under warranty?
Click to expand...
Click to collapse
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
rpimps said:
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
Click to expand...
Click to collapse
Unfortunately, it breaks the warranty aggreement. So e-bay is a good idea, I guess.
P.S: I heard from someone that you can go back to stock rom then you can still use your guarantee. But I'm not sure if they can see that you reflashed it or not.
rpimps said:
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
Click to expand...
Click to collapse
From what I have read, if you flash back to the exact stock ROM which was installed on your phone when you had received it, then this will not affect your warranty - if you decide to return your phone (assuming it is still under warranty) just make sure you downgrade to Stock ROM and Radio version, with no trace of HSPL or USPL also, or else you will have to pay them money if they (HTC) find out
EDIT: Please follow these steps to restore back to your stock ROM version:
1. First, be sure to restore your stock OS, and then the stock radio. The Stock SPL is always to be done last!
2. Download your choice of a stock spl package from the link shown below. (currently 1.13, 1.14, 1.15, 1.54)
3. Also download the original hardspl from the link shown below.
4. Run the hardspl exe but do not click anything in RUU yet. Just let the hardspl EXE extract the files for flashing.
5. The SPL you want to revert to is a .NBH file, put the stock SPL NBH in the extracted hardspl package, overwriting the original NBH file in it!
6. Continue with the RUU (or if needed, run SSPL-Manual.exe manually, then run RUU when it goes to tricolour 1.07.OliNex screen), it goes to 100%, reboots, done.
7. To verify, enter bootloader mode, see version number on tricolour screen, should now just say 1.14.0000 or any other version ending in .0000, but not ending in OliNex!
that's it.
Please refer to the following link for more information and the necessary files you will require to re-flash back to Stock (see and read the last section of post #1):
http://forum.xda-developers.com/showthread.php?t=431217
Regards.
p.s. also remember to flash back to the original Radio version of the phone, if required.
There are several stock ROMs linked in the Blackstone Wiki, flash back to one of those and see if your problem is still there. If it is, send it back for a Warranty repair - as long as there is a stock SPL and ROM image on your phone, you Warranty will be intact.
what i dont see is mention of ho u are answeing the calls.
there or at least three ways
1. the on screen prompt. i assuming this is the one that freezes
2. the answe key at the bottom left of the phone
3. the htc headphones im assuming you have
have u tried using all three of these methods to answer calls??
Hello,
I have been reading quite a bit here including all the stuff about ensuring that I don't brick the phone and which roms to install etc. etc.
Anyhow, I couldn't find any detailed threads about folks who might've tried installing Android on stock windows.
I went ahead and tried using it today and android did load up fine. Everything seems to work perfectly. The only issue is that the dialer freezes when I am dialing numbers and I can't hear anyone and they can't hear me. So I will try another android flavor.
What I wanted to confirm was that if I am using Android on default windows, is there a chance I can brick my phone?
Any help is appreciated.
Thanks
Impossible to brick your phone because its just running off the mem card I've been running android on a stock rom for about a month now, just make sure you've got an appropriate radio version etc...
cool..thanks for your response..
also, what do you mean by the radio version? I basically installed, http:/ /forum.xda-developers.com/s howthread.php?t=740963
that's all i did. Do you mean to say I have to install a radio version separately?
Thanks
spoofy420 said:
cool..thanks for your response..
also, what do you mean by the radio version? I basically installed, http:/ /forum.xda-developers.com/s howthread.php?t=740963
that's all i did. Do you mean to say I have to install a radio version separately?
Thanks
Click to expand...
Click to collapse
What version of the HD2 do you have? T-Mobile US?
I used my stock UK O2 172. ROM
1st HSPL
2nd Updated Radio
3rd Loaded Darkstone Froyo
I haven't had any probs and android is running fine.
RReckless
Sent from my HanDroid2 using XDA App
rp-x1 said:
What version of the HD2 do you have? T-Mobile US?
Click to expand...
Click to collapse
I should've been more specific. Yes it is a tmobile US version.
I just recently go android working on my tmous phone using stock rom. I had to do the following to get it 100% functional
1) Install HSPL3 and flash the radio to version 2.12 (it actually said something like 2.08 in the HSPL app)
2) Flash to ChuckyROM lite
3) Copy darkstones Froyo 2.2 build to sd card
Thats it, everything works now. I had the same problems as you so I would take this route if I were you. Keep in mind that flashing to chuckrom is going to replace the windows theme you normally see when you start your phone. From there you can use the included Android launcher utility so you can then quickly boot up android instead of windows.
Personally I could care less what windows rom/theme is loaded since my goal is to convert to Android completely. Although I will say that I immediately noticed an improvent in windows overall thanks to the ChuckyROM tweaks. If you choose to run chucky isntead of android it's a nice breath of fresh air, much more responsive, faster, and logically laid out.
Couple of caveats:
1) Bluetooth phone use is a little wonky. For instance, sometimes when I'm streaming music to my car stereo and I receive a phone call, the mic shuts down and I cant place any more phone calls without rebooting, even though music streaming continues to function.
2) On occasion the touchscreen will lock up. All I have to do is hit the windows key to bring up a context menu and then close it, touchscreen starts responding again.
3) I've been running stable for 3 days, however the phone did reboot itself for no reason and get stuck once. I had to do a battery pull to boot back into chuckyrom/android.
All in all it's been a dream though and well worth the experience. Windows 6.5 is so utterly broken as a phone OS words cannot describe. I feel like I've been using Windows 3.1 on my PC compared to this. The few glitches in the Android ports are entirely worth the hassle, and very minor. And to think, it's only going to get better!
Hi, I need some help from you guys, I'm a noob in these things, anyway I was on Windows mobile 6.5 (Not a T-mobile) , and thought about changing into an android. I found some tutorials on youtube, and tryied to do It exactly as It said. Ok, so I found this video on youtube with a link on It, I clicked It, which directed me to one website. I installed the Hard HSPL folowing the instructions, then It said to install a Windows Mobile ROM, I downloaded and installed "Chucky Droid Rom" and now my phone Is like in between the Windows and Android, some kind of weird screen like theres no OS on it. Then it says to download and put Android Rom into my SD card, after downloading "FroyoStone_Sense_V2", I also deleted everything from the SD card except the Android directory. After i push CLRCAD, I start "haret", but it just shows me very little text on top of the screen, which fades away in like 5 seconds. After that i get "Sleep of Death" the screen just keeps black, unless i restart my phone. I tryied to wait for like 40minutes hoping it will start somehow, but the situation didn't change... So can somebody please help me? How do i boot my phone to android, what should I do to get that penguin with a lot of flashing text on my phone instead of this "Sleep of Death" What am I doing wrong? Thanks for answer guys.
What is your intention with running Android, do you just want to experiment with it and use it as a dual boot, ie still have winmo and then boot to Android, or would you like to replace winmo with Android? If the first option, then you will need to flash a full winmo rom as AFAIK ChuckyDroid is an extremely light rom that basically just allows you to boot to an Android rom.
If your intention is to only run Android then you should be looking at the NAND Android roms as this replaces winmo totally and the phone boots straight to Android. If you would like to do this, then follow the link in my signature on Flashing NAND roms, it is a very good tutorial and gives you step by step instructions on what to do.
Does it work on European HD2? Because i think i have the problem, because my HD2 is not a T-mobile and i did everything as it said step by step, which would give directions for a T-mobile. I think thats the issue to the problem...
Vettelis said:
Does it work on European HD2? Because i think i have the problem, because my HD2 is not a T-mobile and i did everything as it said step by step, which would give directions for a T-mobile. I think thats the issue to the problem...
Click to expand...
Click to collapse
The process is practically the same the only difference is that with NAND TMOUS get more storage then EU HD2, unless you have EXT partition on SD card. Anyway what radio are you currently running this could be why android wont run off SD card.
Ricey
Thanks for the help guys, after I installed the correct radio it works perfectly.
I'm sorry i know it's against the rules to be starting a new thread but it's been a week i've been asking for help and no one noticed. This is just a try to come noticed.
I installed task 29 on my blackstone. I had olinex 1.56 installed and later did the task29 with radio 1.13, 1.14 and 1.17 After successfully doing it i went on step 2 that is installing a clean rom. I tried these roms
blackSTONEhengeHyPerSlim_4_1
RUU_TOUCH_HD_MARYONE_23148_WWE_191110
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship(3)
They get installed but after i store the contacts and everything it gets stuck if kept for like half an hr. The screen doesn't respond but power button and the volume button works.
I took my phone to a repair center and they couldn't fix it. So please help me i've just got only one phone.
I don't mean to offend any moderators by this but i'm just asking for your help. Thank You
Try reinstalling stock ROM after Task 29.
Restore ONLY contacts, and then try using device for several days.
DO NOT install any other software!!!
If it works, then problem is in some data or software you're restoring.
If not, restore original SPL and original ROM and try again.
If it does not work... and service can not help you... then sorry...
Hello i did reinstall the stock rom after task 29 and i was using pimbackup for restoring but that freezed my phone so i installed the stock rom again and thought of not using it. Did that but nothing much helped.
I hope believe these are the correct shipped roms
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.3 4_1.13.25.24_Ship(3)
Everything on xda has worked like wonders for me. Be it android on any other rom but right after task29 nothing seems to be working on my phone.
One thing i've noticed after installing any rom after task29 is if i get to the bootloader it gets me to a 1 sec white screen saying no image found. I hope what's causing a problem.
Do you understand WHAT Task 29 is?
It formats the partition drive of your device where the ROM resides. Meaning, it wipes any data regarding ROM.
So of course it would say "No image found".
I don't know which ROM is stock for your device. Try to update ROM via HTC site.
If lucky, it will suggest / let you find adequate ROM.
For my device it's 1.56.407.2 (German)!
If unlucky, it will say "Not supported" or something like that - then go for Orange 1.59.61.2 ROM.
And you might try one 1.5x ROM flash WITHOUT Task 29...
Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.
Thanks will do it and keep yu updated with it..
simplistian said:
Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.
Click to expand...
Click to collapse
Thanks i tried installing the stock rom like you told me but then got stuck on the screen alignment screen. I later installed blackSTONEhengeHyPerSlim_4_1 and now it's responding to every touch. Thanks alot. I hope this stays like this and yes instead of restoring i forwarded all the contacts through bluetooth. Owe you a BiiiiiiiiiiiiG thanks..
Too soon to be happy as same again..I don't think there should be a problem with touch as it works fine for first 1hr but right after something gets stored by something i mean contacts it stops reponding after sometime. The volume and power button work all fine. I can't make out the problem. Any ideas or suggestions. Shall i make a video and post ??
FIRST you have to make it work with factory settings - stock SPL and stock ROM.
After that flash what you like...
I think you have to follow Bodisson's suggestion, do everything as stock and retest without restoring anything. If it still failed...... you should have it repaired
Good luck!!
I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...
Bodisson said:
I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...
Click to expand...
Click to collapse
Glad to see somebody researching things out and settling on a radio he prefers due to performance rather than those just going for latest
I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.
kulwant said:
I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.
Click to expand...
Click to collapse
All rom's should work with each radio to be honest. Glad your device is working better, though still a little baffled why you're still having difficulties
EDIT - You are on a wm6.1 rom. Is the rom based on 1.56+, if not you may need to revert to HSPL 1.14
I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers
kulwant said:
I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers
Click to expand...
Click to collapse
I'm baffled but still want to get to the bottom of your issue and would appreciate any help from other members who may have idea's on how to solve your issue. From what I've read everything you have done is correct, but I don't like being stumped!!
If we start from the start, we may get to the bottom of this........
Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.
kulwant said:
Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.
Click to expand...
Click to collapse
Well as you know a T29 formats device so you need to flash a rom or you'll be stuck at boot screen. Before you do a T29 it states you must have HSPL on your device first. Now from what I've read you did have HSPL on first and your T29 worked as you where stuck at boot screen afterwards.
I'm assuming you turned device off, booted into bootloader then flashed youir rom (blackSTONEhengeHyPerSlim_4_1) which is based on 1.56+ as was your HSPL.
This all seems correct so I'm not sure what went wrong.
Is above all correct?
Did you try a T29 again and flash different rom or did you just flash different rom over existing?
I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.
kulwant said:
I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.
Click to expand...
Click to collapse
Right, I never put any files in same folder as it only confuses flashing process and can cause issues. I.e. put T29 in its own folder, radio 1.14 in its own folder and then rom in another folder.
Do a T29 and when its complete, I.e. stuck in smart mobility screen. Then you take out battery to turn phone off. After this put phone into bootloader and flash rom. Then flash radio after it as a lot of roms have a radio file included
...........................
Sent from the improved version of Tapatalk, better known as Forum Runner
Hi,
I've been on Android 2.2 for a while now, and decided to give others a go.
I've changed to multiple different Android Gingerbread and MIUI roms, and on each one i cannot make a call!! This is what happens:
-The first call i make after turning on the phone has sound but it is like robotic sound so you cannot make out what the other person is saying!
-After this first call, any other call i make it will dial and the other person will receive me calling them, but i cannot hear anything, it's just blank, and they cannot hear me either.
What is the problem here? I haven't seen anyone else with this problem but on Android 2.2 i do not have the problem.
Cheers
Danjaye said:
The first call i make after turning on the phone has sound but it is like robotic sound so you cannot make out what the other person is saying!
..........
I haven't seen anyone else with this problem
Click to expand...
Click to collapse
really? you haven't seen any reference to robot voice at all? even though practically every rom has suffered / suffers from it until recently? and its mentioned all over? (Sorry, couldnt resist 43 thousand results on "hd2 robot voice" in google )
after a fresh flash, make a call, anything will do, switch on the loudspeaker, switch off the loudpeaker, hang up. Problem should be gone until next flash.
Ive also seen reference to turning off audible touch tones but the above method has always worked for me, so i never investigated.
Yes perhaps the robot voice call, but not the afterwards bit where i cannot hear anything at all!!
Ok so i should make the 'robot' first call, wait till answer, switch on loudspeaker, switch off loudspeaker and hang up? I'll try it later on and get back to you.
Danjaye said:
Yes perhaps the robot voice call, but not the afterwards bit where i cannot hear anything at all!!
Ok so i should make the 'robot' first call, wait till answer, switch on loudspeaker, switch off loudspeaker and hang up? I'll try it later on and get back to you.
Click to expand...
Click to collapse
Hehe I was ignoring the second part in the hope that it's an effect of not clearing the robot bug and will hopefully go away once you try the above.
Firstly as stated "robot voice" is a rediculous topic to create about and you obviously havent even bothered to use search before creating this topic. Remember 99.9% of all questions/issues you can have etc have already been asked and resolved in some way or another and its best to first have a little research. We all need to create help topics now and again but its much better to bring the info to yourself then to create a topic and wait.
Second, which ROM are you currently on, Which Radio do you currently have? Are you running from SD or NAND?,
My guess would be to try a different radio, Preferably 2.15.
Another thing you can try is doing a completley clean install, ie doing Task29 and properly formatting your SDcard, anything less will leave residual files on nand and card. Use Panasonic SDFormatter with full/overwite format and size adjustment on.
To make thinsg easier for you get the HD2 tools 3.9 that is in sticky in nand section.
I am on android 2.2 and it works fine but if i change to say 2.3.3 it does it.
When i have updated my radio and im ready to put the new ROM on, can i just use full data wipe in AD Recovery before installing the rom from sd, will this be good enough?
And could anyone show me where to get the newest Radio file
ps when i run NAND Android 2.2 the calling is fine, but when installing the MIUI or Gingerbread rom i want with Recovery from SD card, it does this problem.
Danjaye said:
I am on android 2.2 and it works fine but if i change to say 2.3.3 it does it.
When i have updated my radio and im ready to put the new ROM on, can i just use full data wipe in AD Recovery before installing the rom from sd, will this be good enough?
And could anyone show me where to get the newest Radio file
ps when i run NAND Android 2.2 the calling is fine, but when installing the MIUI or Gingerbread rom i want with Recovery from SD card, it does this problem.
Click to expand...
Click to collapse
If you are having these sorts of issues with various roms you need to do exactly as I said.
Clean install, task29, FULL format sd card and then start over.
Download the HD2 NAND Tools.
Device:
Put device into bootloader
flash task29
Put back into bootloader
flash magldr
SDCard:
Load SDFormatter
FULL Format/ERASE
Size Adjustment ON.
im really new to all this i don't understand how to do that?
You want me to install 'task29' to the computer then how do i full format SD?? Start over from what? Im very new to it
I have MAGLDR113 and can access the boot screen and do usb flasher etc
a step by step guide would be very appreciated.