Related
hello all.
i purchased my htc hd2 before last christmas due to all the features and potential the device possesses (fast, ability to boot to android)
ive been sitting back doing research from this site for weeks now, in preparation to installing android. i finally decided i was ready, and started the operation yesterday.
to begin with, my phone displays this at startup:
2.15.50.14
15.42.5011u
3.14.04666 8g
i admit that i am very confused; many guides and videos show completely different steps for installing the same type of builds.
what i did was:
downloaded several builds-
dan1j3l-LeoFroyo-1.0
darkstone_HD2Froyo_v1
SuperRAM_Froyo_v1
ChuckyROM-Tabtastic.Dec.15 (did not use this one yet- not sure yet of what it does)
formatted my sd card, installed the build to the root directory, as in /my device/sd card/android
installed dualboot app (mskip_Android_Loader_V6.0%20Final.cab) to my device
ran clrcad
ran haret
each build (dan, darkstone, super ram) managed to load android somewhat successfully.
the problem i encountered with each build, is the robo-voice. regular sound works (media player apps).
during phone calls, the voice sound is robotically distorted.
also, my youtube app doesnt work on any build, and gps is iffy.
i become confused when i see some guides suggesting that i do not need to tamper with the radio, while others require that i do.
so my questions are, what am i doing wrong, as far as the radio is concerned?
do i need to tamper with my radio for this device to work with android?
what difficulties can i expect in trying to accomplish this?
if i mess up, can i fix it?
also-- which builds are known to work with youtube/ gps?
finally, if i hard reset my hd2 for whatever reasons, will i have to redo the whole process of installing android again?
the_mask313 said:
hello all.
i purchased my htc hd2 before last christmas due to all the features and potential the device possesses (fast, ability to boot to android)
ive been sitting back doing research from this site for weeks now, in preparation to installing android. i finally decided i was ready, and started the operation yesterday.
to begin with, my phone displays this at startup:
2.15.50.14
15.42.5011u
3.14.04666 8g
i admit that i am very confused; many guides and videos show completely different steps for installing the same type of builds.
what i did was:
downloaded several builds-
dan1j3l-LeoFroyo-1.0
darkstone_HD2Froyo_v1
SuperRAM_Froyo_v1
ChuckyROM-Tabtastic.Dec.15 (did not use this one yet- not sure yet of what it does)
formatted my sd card, installed the build to the root directory, as in /my device/sd card/android
installed dualboot app (mskip_Android_Loader_V6.0%20Final.cab) to my device
ran clrcad
ran haret
each build (dan, darkstone, super ram) managed to load android somewhat successfully.
the problem i encountered with each build, is the robo-voice. regular sound works (media player apps).
during phone calls, the voice sound is robotically distorted.
also, my youtube app doesnt work on any build, and gps is iffy.
i become confused when i see some guides suggesting that i do not need to tamper with the radio, while others require that i do.
so my questions are, what am i doing wrong, as far as the radio is concerned?
do i need to tamper with my radio for this device to work with android?
what difficulties can i expect in trying to accomplish this?
if i mess up, can i fix it?
also-- which builds are known to work with youtube/ gps?
finally, if i hard reset my hd2 for whatever reasons, will i have to redo the whole process of installing android again?
Click to expand...
Click to collapse
I'll back-track:
No, you won't have to redo if you do a hard reset, the Build is locate on the SD card, you just might have to reinstall the boot loader.
You just may have to try several radios to see what fits you. It's just a matter of reinstalling another radio, this process does not affect anything else.
I always have recommended "Tytung's" builds; there are links and keen info in my thread.
Some builds offer explanations and fixes for various issues, including robo-voice. You might want to check the thread of the build that you are currently using. Sometimes, just a restart or two solves the problem.
i meant to ask-
what is the difference between a rom and a build?
do i use (in my case) a build in addition to running a rom (in my case, chucky_rom)
the_mask313 said:
i meant to ask-
what is the difference between a rom and a build?
do i use (in my case) a build in addition to running a rom (in my case, chucky_rom)
Click to expand...
Click to collapse
A ROM usually refers to to Windows Mobile software in the phone: like in the SD setup I recommend you would use the VBN ROM, as it's simplified, in conjunction with TyTung's Nexus Android Build.
A BUILD is the Android application that you are using, like in my case Tytung's Nexus Android.
the_mask313 said:
2.15.50.14
15.42.5011u
3.14.04666 8g
Click to expand...
Click to collapse
and also, from what i have, do i need to change the radio?
the_mask313 said:
and also, from what i have, do i need to change the radio?
Click to expand...
Click to collapse
You shouldn't, but that depends on where you're located and what service.
I want to know have can i solve my wifi problems without installing new rom on it.
What is the wireless driver, where are they in my system files?
We can fix the camera issues with changing camera lib files. Can i do that for wifi?
Wifi Problem is ;
I can connect wifi, first it was work fine. After several minutes it dropped and not connect any internet, after several seconds it reconnectted. It always keep going this way.
Can you please help me on this?
What ROM version are you running?
B137 stock and modaco.com/content/huawei-u8800-ideos-x5-u8800-modaco-com/342205/23-june-b137-r3-flb-custom-rom-for-the-huawei-u8800-with-online-kitchen/
I have two of them on my clockwork recovery. Both of them have same issue. I want to try other roms, but its too hard for me to give the time for each rom. So i want to try other roms wifi libs, driver, firmwares.
Not a fan of 137s I've tried so far...You should try these versions:
- V100R001C00B136 (Overseas General version) 2011-05-17
- V100R001C17B160CUSTC17D002 (China Unicom) 2011-04-29
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800
To install any of the ROMs, just download the Huawei Firmware you want and unzip it, there should be a folder called "dload" copy that folder and its contents to your sdcard.
Power off phone then hold both volume buttons while powering on the phone, the update should start.
I don't understand why you think it's easier to change a lib/driver and spend a huge amount of time trying to get it to work, when it takes 30 minutes to install a new ROM and all previous applications, if synced with a Google account. When I first got the phone, I've installed like 6-7 ROMs in a matter of hours...
So, in my opinion, you should try the B160 or B136 before you actually start fiddling around with libs.
katu2006 said:
Not a fan of 137s I've tried so far...You should try these versions:
- V100R001C00B136 (Overseas General version) 2011-05-17
- V100R001C17B160CUSTC17D002 (China Unicom) 2011-04-29
To install any of the ROMs, just download the Huawei Firmware you want and unzip it, there should be a folder called "dload" copy that folder and its contents to your sdcard.
Power off phone then hold both volume buttons while powering on the phone, the update should start.
I don't understand why you think it's easier to change a lib/driver and spend a huge amount of time trying to get it to work, when it takes 30 minutes to install a new ROM and all previous applications, if synced with a Google account. When I first got the phone, I've installed like 6-7 ROMs in a matter of hours...
So, in my opinion, you should try the B160 or B136 before you actually start fiddling around with libs.
Click to expand...
Click to collapse
Are you read my first post ? I Don'T want to try roms. Install new rom, try wifi, over and over. End when find it, wait for the all install downloaded. Chancge launcher and other apps to what you want. It is just boring. I try 4 different froyo roms and nothing seems worked. If i know the what file i must replace, i just have time. Many many more time.
Özgürce said:
Are you read my first post ? I Don'T want to try roms. Install new rom, try wifi, over and over. End when find it, wait for the all install downloaded. Chancge launcher and other apps to what you want. It is just boring. I try 4 different froyo roms and nothing seems worked. If i know the what file i must replace, i just have time. Many many more time.
Click to expand...
Click to collapse
So, stock rom doesn't work too?
Özgürce said:
Are you read my first post ? I Don'T want to try roms. Install new rom, try wifi, over and over. End when find it, wait for the all install downloaded. Chancge launcher and other apps to what you want. It is just boring. I try 4 different froyo roms and nothing seems worked. If i know the what file i must replace, i just have time. Many many more time.
Click to expand...
Click to collapse
) I've read your post, but if you think this is windows, where you can just change the wifi drivers, you're in for a treat . The newer ROMs wifi is fine, so whatever you're doing, you're obviously not doing it right or you have a faulty phone.
katu2006 said:
) I've read your post, but if you think this is windows, where you can just change the wifi drivers, you're in for a treat . The newer ROMs wifi is fine, so whatever you're doing, you're obviously not doing it right or you have a faulty phone.
Click to expand...
Click to collapse
I don't understand a thing from your post. Are you understand me?
IF IS A WINDOWS, I CAN CHANGE DRIVER FROM SYSTEM32/DRIVERS. Or install new driver for it. Newer roms are for WHO ? Mine and other my friends in turkey, have same problem. Even they updated the B137 with updata.app from original sources.
Please if you don't know or understand my post, just leave it to be. Obviosly i can't decribe my problem to you.
The whole windows thing was a comparison...All I was trying to say is that upgrading drivers is NOT EASY, as the problem may not be in the lib file.
You better go and learn some ENGLISH, before you try and understand the answers you're given. ) quote "Are you understand me?"
Very very few people have wifi problems like you are experiencing. This isn't to say it doesn't happen as obviously you are having issues, but it's not a rom issues. It's likely that your problem is either a hardware issue with the phone or an issue with your router settings.
Currently there aren't any alternative wifi libs you can try since all the roms are using exactly the same wifi libs which are located in the kernel image, not the system.
I've been experiencing the same problem -international B136 ROM- however I think it may be the router that is the cause of it. Whilst in the main house with the new wireless g router, no issues, everything works fine. In my extension with the old wireless b router the problem happens all the time.
The problem doesn't really bother me to much, but I thought I'd add my 2 cents just in case you were after some more information on the issue =)
guys, I recommend reading my post in the general section with subject "Wifi Client Tuning ... solve connection problem "
Sent from my IDEOS X5
i have simillar wifi problem. When i connect my airties modem,my internet connection is vere very slowly(60-80kpps as speedtest program) How can i fix this problem? Do you think b136 or b160 could fix it?
fukul2027 said:
i have simillar wifi problem. When i connect my airties modem,my internet connection is vere very slowly(60-80kpps as speedtest program) How can i fix this problem? Do you think b136 or b160 could fix it?
Click to expand...
Click to collapse
Definitely, if you've got something like B133, the first thing you have to do is upgrade to 136-137 or 160. You will see huge improvements in terms of Wifi.
is there any problem in b136 or b160? Which one should i apply?
In my view, the best of stock ROMs is B160. The battery lasts longer and it's got less problems.
how can i see my rom version? and do u send offical b160's link?
Go to Settings >>About Phone and scroll down to Build Number. It should look like this U8800V100R001C00B133SP01 and the bit that interests you is B133 or whatever version you've got.
Since Modaco Wiki is down, try this link:
http://www.filefactory.com/f/0f067250fb54623e/
B160 is called China Unicom in that list.
I've managed to get a cached version of Modaco Wiki that is currently down.
http://webcache.googleusercontent.c...&hl=en&ct=clnk&gl=au&source=www.google.com.au
A direct link to b160 from Huawei - http://www.huaweidevice.com/tcpsdow...me=U8800 V100R001C17B160CUSTC17D002(中国联通).zip
My rom seems to b136 is it change anything?
Hi,
I've used CM7 and CM9 before with no major problem. But probably did something wrong because after flashing couple of ICS ROMs my phone (Defy-red lens) became unusable with 2 problems:
- no mobile network connection (no phone-calls, no SMS, no 2/3G)
(Wifi and Bluetooth are OK)
- it does not save the setup, each boot is a new phone with new configuration setup.
I've tried different ROMs (CM9, Quarx, Skanky, etc) with different Kernels (7 & 9), but nothing seems to change this behavior.
The phone also doesn't recognize the IMEI and can't search of operators. I've attached some screeshots.
I was wondering if someone else could share their experience with me or, somehow try to help me. I'm willing to try out things....
Cheers.
You tried changing your baseband??
Sent from my Defy+ using Tapatalk 2
Baseband is not initialized/installed. In the first pic, it shows the baseband as 'unknown'. Select proper baseband matching your country from Baseband Switcher (settings -> Advanced->Baseband Switcher) and reboot your phone.
andr0idfreak said:
... Select proper baseband matching your country from Baseband Switcher (settings -> Advanced->Baseband Switcher) and reboot your phone.
Click to expand...
Click to collapse
Baseband is by default on Europe > Central Europe > 3.4x 900/2100 MHz which is not right for me. Should be America > Brasil > TIM 3.4.2-107-9 850/2100 Mhz.
The problem is, as I mentioned, that the phone does not save any settings. After the reboot the Baseband comes back to the default setting.
I already did the wipe factory/reset, wipe cache partition and wipe dalvik cache many times before/after flashing a ROM (and event deleted the dalvik cache folder via terminal emulator since it wasn't asking for confirmation when deleting via cwm) but didn't really change anything...
Any idea what's leading to the settings not being saved?
Thank you for helping.
PS: I didn't play with partitions, but as I've read in this post, of a similar problem, that this might be the case, I'll post the screenshot of the command df just in case...
fbugnon said:
Baseband is by default on Europe > Central Europe > 3.4x 900/2100 MHz which is not right for me. Should be America > Brasil > TIM 3.4.2-107-9 850/2100 Mhz.
The problem is, as I mentioned, that the phone does not save any settings. After the reboot the Baseband comes back to the default setting.
I already did the wipe factory/reset, wipe cache partition and wipe dalvik cache many times before/after flashing a ROM (and event deleted the dalvik cache folder via terminal emulator since it wasn't asking for confirmation when deleting via cwm) but didn't really change anything...
Any idea what's leading to the settings not being saved?
Thank you for helping.
PS: I didn't play with partitions, but as I've read in this post, of a similar problem, that this might be the case, I'll post the screenshot of the command df just in case...
Click to expand...
Click to collapse
Though the problem seems quite different but it might be your baseband switcher..
try BBs_v4
It might work.
neo.ank said:
Though the problem seems quite different but it might be your baseband switcher..
try BBs_v4
It might work.
Click to expand...
Click to collapse
Thanks. I was able to change the baseband with this app (and somehow keep this setting after a reboot - see screenshots), but under "About phone" still shows as Baseband version Unknown. And I still have no network signal...
Meanwhile... the matter with partitions and settings lost after reboot:
I know a litte of Linux, but I don't understand Android's structure or how it deals with partitions, but I might have found something:
In Bootmenu Recovery > Advanced > Show Log reads:
Bootmenu Recover v.5.0.6
I:Chechinkg arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adv.enable=0
ro.factorytest=0
ro.usb_mode=normal
ro.bootmode=reboot
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x0000
ro.hardware=mapphone_umts
ro.revision=0
I:Cheching for extendcommand...
I:Skipping execution of exetendcommand, file not found...
W: failed to mount /dev/block/mmcblk1p25 (Invalid argument)
As I see that in the system there are others blocks with similar names (screenshots in post #4), I was wondering if this might be related to the problem I'm dealing with (loosing settings after reboot).
I see some people had problems with this block/partition, for instance in this post - Issue with /dev/block/mmcblk1p25, but I couldn't figure out how they fixed.
Any help is much appreciated.
Hi fbugnon,
I have the same problem on my Defy. I've tried to use 2 differents builds from wdscript.fr (120613 and 120610), installed baseband switcher, but the problem is the same as yours.
Everytime the phone restarts, it resets all settings.
I'm trying to use a build from quarx (quarx2k.ru, build 120305) now, let's see if that helps.
I'll keep you updated.
Hi tiagomelo,
I've tried many differents ROMs but no one was able to change this behavior. I'm not sure, but I believe the problem is related to the partition error mentioned on my last post -- do you also have the same problem?
I was forced, eventually, to do a full SBF with Tim's original system so that I could use my phone and now I'm using CM 7.2 rc3.... Waiting for ICS to solve the calendar sync bug which is crucial for my work and then I'm back on.
Wish you good luck! And please keep us posted, I would like to know where this will lead you to.
Cheers
[B]it does not save the setup[/B], each boot is a new phone with new configuration s
fbugnon said:
Hi,
I've used CM7 and CM9 before with no major problem. But probably did something wrong because after flashing couple of ICS ROMs my phone (Defy-red lens) became unusable with 2 problems:
- no mobile network connection (no phone-calls, no SMS, no 2/3G)
(Wifi and Bluetooth are OK)
- it does not save the setup, each boot is a new phone with new configuration setup.
I've tried different ROMs (CM9, Quarx, Skanky, etc) with different Kernels (7 & 9), but nothing seems to change this behavior.
The phone also doesn't recognize the IMEI and can't search of operators. I've attached some screeshots.
I was wondering if someone else could share their experience with me of, somehow try to help me. I'm willing to try out things....
Cheers.
Click to expand...
Click to collapse
I have same problem with my phone also...........I search but not able to find out any fix for this...
Can any one help me fix it. I am not able to use my phone
Please help me out .... .....
Ajitnegi said:
I have same problem with my phone also...........I search but not able to find out any fix for this...
Can any one help me fix it. I am not able to use my phone
Please help me out .... .....
Click to expand...
Click to collapse
What ROM are you using? Your build version. And is the problem exactly as described in OP, then I see that its been resolved.
A bit same like yours
Guys i dont know if if i can help you over here but i was some issues with the call/data/3g ... for me as soon as i tried using them they froze completely, not the phone but the signals .. its was related to my baseband settings and stuff,
so i found a solution for this ...
go into recovery cpu settings,
Status: enable
Enable all modules
Scaling: Conservative
dont forget to save at bottom and reboot
if these settings worked for you then it should be alright
This is just a suggestion to the issue .. u can try it .. I don't know if it is %100...
for me it works
ibtihaaz said:
Guys i dont know if if i can help you over here but i was some issues with the call/data/3g ... for me as soon as i tried using them they froze completely, not the phone but the signals .. its was related to my baseband settings and stuff,
so i found a solution for this ...
go into recovery cpu settings,
Status: enable
Enable all modules
Scaling: Conservative
dont forget to save at bottom and reboot
if these settings worked for you then it should be alright
This is just a suggestion to the issue .. u can try it .. I don't know if it is %100...
for me it works
Click to expand...
Click to collapse
That's a different thing. The reason for your freeze would be something with your CPU/chipset.
Good to see someone who is familiar with this issue of mine ..
so would u b able to tell me why i was having this problem with the chipset/cpu related to calls and data download ...
i know its not the right thread but i tried other thread but no answers yet
i came across this solution after a lot of seaching .. trial n error
u dont know what i've been through ... but using this settings doesnt give me good downloading speed in google play though
Ajitnegi said:
I have same problem with my phone also...........I search but not able to find out any fix for this...
Can any one help me fix it. I am not able to use my phone
Please help me out .... .....
Click to expand...
Click to collapse
Hi Ajitnegi,
As mentioned before, the only solution I could find to this problem was restoring the orignal ROM (Motorola's) by doing what they call a full SBF (you can read a bit about sbf in here or in posts on this forum).
Sorry not being able to help any further. Good luck.
Cheers.
Same problem | No network connection
Hi
I am also facing the same problem, no network connection. After going through this post where you had asked to change the baseband settings to the country specific, I did change it. Unfortunately, even after changing the baseband settings, after reboot it changes to default value (.i.e. Central Europe).
While going through this forum, I could not find any final settings provided by the developer, did you get any ? If so, can you point out to it.
Thanks,
Nash
fbugnon said:
Hi,
I've used CM7 and CM9 before with no major problem. But probably did something wrong because after flashing couple of ICS ROMs my phone (Defy-red lens) became unusable with 2 problems:
- no mobile network connection (no phone-calls, no SMS, no 2/3G)
(Wifi and Bluetooth are OK)
- it does not save the setup, each boot is a new phone with new configuration setup.
I've tried different ROMs (CM9, Quarx, Skanky, etc) with different Kernels (7 & 9), but nothing seems to change this behavior.
The phone also doesn't recognize the IMEI and can't search of operators. I've attached some screeshots.
I was wondering if someone else could share their experience with me of, somehow try to help me. I'm willing to try out things....
Cheers.
Click to expand...
Click to collapse
Ajitnegi said:
I have same problem with my phone also...........I search but not able to find out any fix for this...
Can any one help me fix it. I am not able to use my phone
Please help me out .... .....
Click to expand...
Click to collapse
Hi Ajitnegi
I don't know if this is the only way to fix it, but In order to recover MY phone I had to flash a full SBF, which is -- as I understand -- basically a Motorola Recovery that works pretty much like a factory reset. Search the forum and I'm sure you'll find someone explaining how to do it.
Or if you rather take some time to better understand what's going on with your phone before you start flashing it, you might want to take a look at this excellent "All-in-one Defy Beginner's Guide".
Cheers
i have the same issue, i have No Network and No Wifi
after flashing CM9 on my SGW from stock ROM
Help please .
Re: new "developer's edition" N910V ROM compatability
From the few ROMs I've tried to flash so far, I've gotten a lot of error 7s in TWRP
As far as I can tell from some googling, this means that the updater-script in the ROM isn't allowing it to be installed on the device because it's not one of the ones in it's approved list based on some prop file somewhere
I think the fix to this is to edit the updater-script file by making it a .txt doc, deleting some amount of lines after the "assert," and changing it back to a file before putting it back into the ROM... so I'm trying to learn enough about coding to find out where exactly I should stop the deletion at. Or, alternatively, what I'd have to add.
It's also possible that I'm totally wrong and I'm getting this error for another reason entirely.
If anyone knows what they're doing here, I'd definitely be open to suggestions. If this is what the problem is, I imagine it won't be hard for devs to edit though.
I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Thebluemace said:
I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Click to expand...
Click to collapse
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
tsongming said:
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
Click to expand...
Click to collapse
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Thebluemace said:
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Click to expand...
Click to collapse
Its a bug, with the current version of the msm8996Pro base, which all Roms use
The developers are aware of the bug and it will be fixed on the next build. For now you can row back to an earlier rom that didn't have that issue or wait for the next build of the Rom you are using.