Related
Yesterday I've HSPL'd my leo.
Then I flashed the Dutty0.3v and thought everything was fine. Until this morning the device was unlocked with S2U2 and hung afterwards (not able to show manila page). After a softreset, device hung at white bootscreen (three red version lines bottom). Several softreset later, it actually lost all its settings, windows welcome center was welcoming me. So it did a hardreset.
Then I flashed another rom, the freyberryROM.V5.3. After flashing, I always hardreset the phone of course.
After two hours configuring and installing, all of a sudden some application weren't starting anymore, so I thought let's do a softreset, to see, if it fixes things. The same happened, device hung a bootscreen. After softreset, a hardreset occured again....
First I wanted to put the blame on the HSPL, but I think it was coincidence. But thinking over and over about my procedure and reading the dutty rom's thread, I think this has to do with S2U2. Maybe some of you experienced this as well, and we can put together what might be the culprit.
Details:
Using S2U2 v2.24 (video rawbuffer mode) - imported settings from reg-file.
Using T2Pro-Theme on SD-Card
Manila and every other HTC/WM setting concerning language set to German.
Hooked on Exchange2010 - Pushmail activated.
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
ROM
I have had the same too with my former Blackstone, as I flashed it with T2M PDViet, I thought it is a virus, however I solved it by downloading a new version and installed it all over again, good luck
Donald24 said:
Yesterday I've HSPL'd my leo.
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
Click to expand...
Click to collapse
We had to do this on all the WM6.5 cooked roms for Kaiser, not heard of it being required for HD2 yet, why not post this in the thread for the ROM you are using?
Before flashing another custom ROM, flash an official stock ROM (1.42/1.48).
I encountered these issues on my TytnII and this weekend, I got the same problem on the HD2. Flahing 1.48 WWE before flashing custom ROM solved the issue for me.
Also: flashing 2.xx ROMs using 1.42xxx SPL may result in unexpected issues.
tomasz said:
Before flashing another custom ROM, flash an official stock ROM (1.42/1.48).
I encountered these issues on my TytnII and this weekend, I got the same problem on the HD2. Flahing 1.48 WWE before flashing custom ROM solved the issue for me.
Also: flashing 2.xx ROMs using 1.42xxx SPL may result in unexpected issues.
Click to expand...
Click to collapse
I've had this on my TytnII as well, but I never heard it for the HD2. So Custom to Custom ROM flashing is a NO GO?
?? Is there any other SPL? SSPL and HSPL are both 1.42 based....
In the diamond and other devices like tynt you could fix this with MTTY but dont know if it will work with the hd2
I thought MTTY was for recovering a device after a bad/interrupted flash??
Can you really use it to fix the non-boot situation and recover your installation?
So, when talking about stock-rom flashing is SoftSPL-flashing enough, or is a full HSPL- or even CID-ID-corresponding flash (incl. radio-rom) necessary?
Can somebody shed some technical background around this issue? I don't understand that there are mysterious areas, which don't get flashed and updated when flashing from custom to custom rom. There is no logic that this works for ONE flash ONLY.
Viewing this post : http://forum.xda-developers.com/showpost.php?p=4798017&postcount=1 , I think a task 32 in MTTY after flash must be a solution (official RUU seem to make it). But never tried.
xvx45 said:
Viewing this post : http://forum.xda-developers.com/showpost.php?p=4798017&postcount=1 , I think a task 32 in MTTY after flash must be a solution (official RUU seem to make it). But never tried.
Click to expand...
Click to collapse
Nope, officially hardresetting a device is recommended after flashing custom rom, I even ran into these issues without hard-resetting after flash (actually forgot it) , so leaving it intentionally out won't fix it.
Are you using CustomRUU to flash your device. I'm sure I read somewhere that flashing from the MicroSD card can cause problems but can't remember what they were now....just a thought
Donald24 said:
Nope, officially hardresetting a device is recommended after flashing custom rom, I even ran into these issues without hard-resetting after flash (actually forgot it) , so leaving it intentionally out won't fix it.
Click to expand...
Click to collapse
Ok, so, we have to found the "Format BINFS" task for HD2 bootloader. It's the command "task 29" on the Diamond (1) and the HD (BlackStone).
So for my experience on the Diamond, we have to do a task 29 before to flash to have a fully cleaned storage before write on this.
So I'ven't found any documentation on this for the HD2, I still investigate with IDA and original RUU, but it's my first attempt to decompile a soft...and it's not really easy to understand.
So we need people with two phone and able to practice JTAG to test a task 29 on Leo bootloader without risk to brick it...and it's not my case.
ps : sorry for my poor English.
crazyman1 said:
Are you using CustomRUU to flash your device. I'm sure I read somewhere that flashing from the MicroSD card can cause problems but can't remember what they were now....just a thought
Click to expand...
Click to collapse
It's not the flashing, me thinks. I experienced the issues only after flashing from custom TO custom rom. So I just think, it's like to old KAISER's times:
Always flash stock rom before!
Has anyone else noticed this?
I've never flashed a stock rom between custom roms and never had any lock up problems. I always use sspl or customRUU. Just thinking it might be the way you're flashing as I'm sure I read somewhere on the forum that there were problems with flashing from the MicroSD card.
xvx45 said:
Ok, so, we have to found the "Format BINFS" task for HD2 bootloader. It's the command "task 29" on the Diamond (1) and the HD (BlackStone).
So for my experience on the Diamond, we have to do a task 29 before to flash to have a fully cleaned storage before write on this.
So I'ven't found any documentation on this for the HD2, I still investigate with IDA and original RUU, but it's my first attempt to decompile a soft...and it's not really easy to understand.
So we need people with two phone and able to practice JTAG to test a task 29 on Leo bootloader without risk to brick it...and it's not my case.
ps : sorry for my poor English.
Click to expand...
Click to collapse
I am absolute unfamiliar with this tasks you do with the RUU....
So task 29 did solve any "leftovers" and freaky behaviour on a diamond?
Donald24 said:
I am absolute unfamiliar with this tasks you do with the RUU....
So task 29 did solve any "leftovers" and freaky behaviour on a diamond?
Click to expand...
Click to collapse
yup, diamond, hd, tynt and i think all htc devices... but nobody have tryed with the hd2... be carefull if you try but i think there shouldnt be any problem.. anyways at your risk
makeveral said:
yup, diamond, hd, tynt and i think all htc devices... but nobody have tryed with the hd2... be carefull if you try but i think there shouldnt be any problem.. anyways at your risk
Click to expand...
Click to collapse
hey - we're getting closer. thinking about a sub-forum about flashing techniques, they will surely get device-dependant at some point.
if a call of task 29 would not make any problems, should it not be made and considered as standard for custom flashing?
did ever anybody brick his device with it? there must be something, causing that fear...
nobody on xda normally shows this respect for trying out undocumented functions
Donald24 said:
hey - we're getting closer.
if a call of task 29 would not make any problems, should it not be made and considered as standard for custom flashing?
did ever anybody brick his device with it? there must be something, causing that respect
nobody on xda normally shows this respect for trying out undocumented functions
Click to expand...
Click to collapse
ya some people have bricked his device because of this... but well it can usually get fixed! problem was that they used mtty without having a hardspl and then they couldnt flash any rom... but if you have hardspl then no problem because you can flash from bootloader!
And if you dont have hardspl then you should also be able to flash HTc official rom(or the official rom that came with your device)
Anyways i wouldnt be first one to try it on my hd2 xD (only if i had problems)
makeveral said:
Anyways i wouldnt be first one to try it on my hd2 xD (only if i had problems)
Click to expand...
Click to collapse
Why hesitating? I'd love to see a "call task 29" as a menu item in your BSB tool I woke up this morning, and I felt for yelling "Task 29" to my girlfriend. No, to be honest, I didn't, I said "69" and enjoyed the morning.
I am going to try this method out and report back, but as it seems, it will be seen as a hack, that doesn't fit for everybody. But I would prefer this against always preloading a stock rom, if it would do the job.
Thanks for putting light on this!
Donald24 said:
Somebody in Dutty's thread said, that those hard-resets get quite common with the newer ROMs, and it would help to flash a stock rom before, can somebody comment on this?
Thanks for any input!
Click to expand...
Click to collapse
Hi,
this is correct, you can stop this happening by flashing a OFFICIAL rom before your cooked rom.
Although i have just posted a thread on MTTY, which is the EXACT answer to all problems in this thread.
THREAD HERE - (It is Under Construction so please dont use until the big red warning has gone, you cant miss it!!)
MG
I was having the same exact problems with softspl and hardspl and with any custom rom. My cousin has the same issues too. I flashed back to stock 1.61 and dont have hardresets anymore.
ok well i just put the FroyoStone with HTC Sense V2 - Release Date: 02.Sep.2010 on my HD2 and it works just fine but i do have a problem with making calls like it freezes and crashes the caller app. its not a problem with the radio i dont think so but does anyone can help me with this? i used the searched but could not find anything but problems with radios. so i would greatly appreciated
daniel18616 said:
ok well i just put the FroyoStone with HTC Sense V2 - Release Date: 02.Sep.2010 on my HD2 and it works just fine but i do have a problem with making calls like it freezes and crashes the caller app. its not a problem with the radio i dont think so but does anyone can help me with this? i used the searched but could not find anything but problems with radios. so i would greatly appreciated
Click to expand...
Click to collapse
What radio are you using and did you run CLRCAD.exe?
Radio versions are responsible for almost every problem running android on HD2. You should really upgrade to version 2.12 and compare. Also try upgrading your winmo rom to one of the other winmo rom's on the this site, since they tweak and change minor things which may have an impact. I use ChuckyROM, which is nice because it has a cool loader for launching android with the click of a button.
What are some reliable radios yall recommend to use and I have a cooked winmo Rom already but I can do everything on the Android but make a call I can receive text emails and surf but can't make calls :/
Like the above poster already suggested, use 2.12. This is the newest radio. It works great for me.
I am using radio 2.15.50.14 and cannot get android to run
I run HARET and it shows a couple of lines of code, then within 3 or 4 seconds of running it, I get lots of static horizontal white lines and the device basically bricks and I have to remove the battery.
Any ideas?
markish99 said:
I run HARET and it shows a couple of lines of code, then within 3 or 4 seconds of running it, I get lots of static horizontal white lines and the device basically bricks and I have to remove the battery.
Any ideas?
Click to expand...
Click to collapse
I had this same problem when I first started reading about droid on HD2.
Make sure you flash your phone with HSPL and make sure you format your memory card as FAT32.
problem calling, american suffix added
hi,
i have recently upgraded my hd2 with the latest winmo (oct 2010) and install Android 2.2 with sense. that works fine, but i have sometimes a problem when i'm trying to make call, the phone add automatically the usa suffix to my number :s
example if i try to call a 06xxxxxxxxhe will try to call the 00106xxxxxxxx.
can someone please help me to resolve that.
thank you very much.
hi,
i have succesfully boot android to my hd2, but when i turn my phone off and turn it on it starts with my standard rom (winmo 6.5)
can somebody help me?
thanks!
Maybe you didn't you understand that its the way it should be ?
You have installed a SD build, which means your WM 6.5 ROM has not been touched in any way, and everytime you reboot then your phone will boot in WM first.
By the way, this is a great advantage of SD builds, because if anything goes wrong in Android, you can quickly go back to WM.
Fortunately, you can automate the work to restart Android at each boot by installing an app like EBL (Exceller boot loader). Search here on xda, or google it for more information.
Ok thanks for the reaction,
I have one problem. When i turn on the music on my phone, it's going faster than normal. I have read some things, but it stil there.
My radio version is now: 2.10.50.26
hi plz help
hi
I have a problem when i tried to run android on sd card the problem in the voice of the call whatever the win rom is or the radio i still have the same machine like voice on the call sooooooo plz plz can any on help me
hi
i have htc hd2 windows mobile im convert it to android 2.3.2 but i have some problem with dealer and it frozen when im make call and say forced close pls help me soon thnks alot.
@castro2020
More details please (NAND or SD, kernel, radio version…). Some apps like Viber or Shazam can cause this issue after using them.
Hello,i installed a few wp7 roms on my hd2,including XBMOD and HD2O,but all of them have the same problem-too low in call volume-when i speak with someone they cannot hear me.I tried changing the registry value as described in the sticky thread ,but it did not help at all.I also tried switching between 2g and 3g but it didn't help either.So is there any way to fix this,because i'd like to use wp7 for a while,but if it cannot be fixed i'm moving back to android?
I've used win7 for helf a year now and didn't face that problem
Anyone else have such a problem???
Not me. have you tried to do task29 and reinstall magldr and Wp7? Or maybe to change the radio version? Or try with different ROM.
spike15_mk said:
Not me. have you tried to do task29 and reinstall magldr and Wp7? Or maybe to change the radio version? Or try with different ROM.
Click to expand...
Click to collapse
I changed 3 different radios ,none of them is better than the others.I tried 3 different roms-they have the same issue.I tried full wipe and clean install-no effect.
When i flash android back- the incall volume if perfect-loud,clean.
Ideas?
spookhc said:
I changed 3 different radios ,none of them is better than the others.I tried 3 different roms-they have the same issue.I tried full wipe and clean install-no effect.
When i flash android back- the incall volume if perfect-loud,clean.
Ideas?
Click to expand...
Click to collapse
Ok try this:
1. Do task29
2.Install WinMo 6.5 (I prefer Dutty's V25)
3.Now install MAGLDR and Wp7 without Task29 (Install over it)
I have some issues with installing Wp7, but I learned that Task29 mess-up with Wp7 installation.
Now if this failed try reverting to stock ROM, and install everything again.
It didn't work.
Then i did task29,installed maglrd and wp7(yuki's rom),and still no effect.Strange thing is that when i turn on the speaker,they hear me well,but when i turn the speaker off-they hear me as if i am 10 metres away from the phone-very very silently.
Ideas?
mine is too loud,to an extend that sound sounds crappy,
its something to do with the builds only,Yuki is working on it,(i dont noe abt others,m sure they must be working as well ),check out his thread as well..
btw m using XMOD v.1.11, and i LOVE it (gnna try out yuki's tonight as well)
spookhc said:
Hello,i installed a few wp7 roms on my hd2,including XBMOD and HD2O,but all of them have the same problem-too low in call volume-when i speak with someone they cannot hear me.I tried changing the registry value as described in the sticky thread ,but it did not help at all.I also tried switching between 2g and 3g but it didn't help either.So is there any way to fix this,because i'd like to use wp7 for a while,but if it cannot be fixed i'm moving back to android?
Click to expand...
Click to collapse
I'm having the same problem:
- overall phone sound is to loud
- incall mic volume is low to the point that the person on the other end can barelly hear me.
Is there a reg key for the mic volume?
As far as i know,there is not.There is a reg key to increase in call volume,but it actually increases in call volume of the hd2,not the mic.I still haven't found a fix for this bug
We should post here all we do. I have tried to flash 2 radios, and nothing, also i have flash WM6.5 HD2O and I came from Android 2.3, i don't remember the rom name . Anyone have tried to re-flash HSPL-2.08?
Greetings
It is true that NoDo roms for HD2 have new radios from HD7? If this is true, we can flash 2.15.50.14, unless, this post could be interesting http://forum.xda-developers.com/showthread.php?t=1080950
Greetings
Ive been using wp7 since dft first released it and ive also tried all the roms, never had this problem, although ive seen a few people reporting this.... so ive have a look around.
...btw task29 is overrated and ive never done it
Same problem of low mic ...
I ahve a APAC HD2 & currently using Pdamatejam V5 & radio 2.15.
I too hav the same pproblem of low mic. this problem did not exist in XBmod ROM.
Any solutions anyone ?
tusharch said:
I ahve a APAC HD2 & currently using Pdamatejam V5 & radio 2.15.
I too hav the same pproblem of low mic. this problem did not exist in XBmod ROM.
Any solutions anyone ?
Click to expand...
Click to collapse
I said the same, anybody knows the fix? I want to use WP7, i love this, it seems so sexy.
Greetings
I have just flash WP7 7592 with marketplace by elfinlazz and all works correctly, only the camera with flash but the mic seems works fine, this is really big, the HD2 will never die.
Greetings.
bringing this back...
I'm using the latest mango rom from HD20 1.23B1 and have this issue. The speaker volume is too high even at 1 and the mic is too low. The other person in the call can't hear me unless I'm talking really loud. I might go back to android if there's no fix...everything is just so good except this bug. Any help is appreciated. Thanks.
I just bought a used euro HD2 because i tought that new phones on the market don't have what it takes to justify their 600€ price (sensation lacks gs II's power, gsII lacks sense).
Well i've been searching and reading for 6days at xda, tried over 5 SD roms and at least 10 NAND roms.
I'm starting to think that those hd2 forums, as deep as they can be, are a big FAKE.
My problems : no g-sensor and freezes while calling. I've tried a lot of fixes and tutorials and still nothing.
Also, the search thread tool is a real pain since it doesn't use the google search system anymore.
Now please, i'm everything but a noob and still i can't manage to find a solution to these problems. This is my last attempt for getting help. Can anyone link me to the solutions if they are obvious (or not).
Also i'd like to ask, is it REALLY possible to use a nand rom as a daily driver? I'm not looking for anything fancy, just some basic Froyo with htc sense.
Thanks in advance for anyone who at least reads this.
im not entirely sure why this is happening to you but my hd2 only lags on sense roms (because I have a euro hd2 and some system parts are installed to the sdcard). If you really want a sense rom and froyo then just install the stock desire rom. And yes NAND roms can easily be used as a daily driver (I see no reason to use a SD Rom unless u want to dual boot two different android roms).
IMO the best roms however are CM7 & MIUI roms with sense skins & widgets (which you can find if you search), they run so much faster than sense roms and use less system space (Hyperdroid CM7, Typhoons CM7, Any Miui Rom are some to look at). This is coming from a person whose HD2 has been dropped in water twice, with keypad lights than NEVER turn off. If my HD2 can run roms fast without issue even though its been submerged in water (and definitely taken some damage) then surely yours can. I suggest you list the roms you've actually tried and then we can take steps to help you from there
DramatikBeats said:
im not entirely sure why this is happening to you but my hd2 only lags on sense roms (because I have a euro hd2 and some system parts are installed to the sdcard). If you really want a sense rom and froyo then just install the stock desire rom. And yes NAND roms can easily be used as a daily driver (I see no reason to use a SD Rom unless u want to dual boot two different android roms).
IMO the best roms however are CM7 & MIUI roms with sense skins & widgets (which you can find if you search), they run so much faster than sense roms and use less system space (Hyperdroid CM7, Typhoons CM7, Any Miui Rom are some to look at). This is coming from a person whose HD2 has been dropped in water twice, with keypad lights than NEVER turn off. If my HD2 can run roms fast without issue even though its been submerged in water (and definitely taken some damage) then surely yours can. I suggest you list the roms you've actually tried and then we can take steps to help you from there
Click to expand...
Click to collapse
I agree. I find the CM7 by boyppc, tyween, sokolik315; MyTouch by Motoman234; Stock DesireHD 1.1.18 by cmylxgo; NexusHD2-Gingerbread by Tytung ROMs the best. Any of these can be daily drivers and very reliable.
You can also put WP7 Mango or NoDo on your HD2 and have a superb experience.
I have flashed quite a few NAND Roms and have found a few to be disappointing but for the most part I have been really happy with a lot of the time and effort that these developers have put into there Roms. I am currently using Dungphps Sense 3.0 Pyramid Rom and it still has a few bugs but has only gotten better and better with each update
http://forum.xda-developers.com/showthread.php?t=1075703
Also check out these following links. Mainly Angeldeath's Rom. I am waiting for his next and most likely final update (July 22nd) which should be nearly bug free and as up to date as possible
http://forum.xda-developers.com/showthread.php?t=1112810
http://forum.xda-developers.com/showthread.php?t=1062881
Hope this helps and don't give up yet
Thanks a lot guys for replying so fast, i'm amazed.
I will make a list of all the nand roms i've tried.
I'm also thankful for all those efforts developpers are putting into their works.
But my primary problems are freezes during calls and g-sensor issues. For the rest, i don't expect a "bug free" rom since i know that the HD2 wasn't made for android and that there are of course no official android roms for this device. Besides, everything else works fine with all the roms i've tried : smoothness, speed, market, camera, data, wifi, gps (since i've applied the recently releases gps fix by tytung)...
I had no call and g-sensor issues in wm6 and wp7.
Also what wonder is why do we have to modify the flash.conf file when mentionned while there are already 3 different packages (from 150mb to 400mb).
My config is: euro hd2 / spl 2.08/ radio 2.14/ mag ldr 1.13 (maybe it is radio dependent, but i also tried with 2.08 radio)
(True2you) Out of curiosity, what is your current Rom btw?
i just flashed coredroid (about 20mins ago) and still, same problems. Now i'm about to try
http://forum.xda-developers.com/showthread.php?t=915159&highlight=stock+desire
LITE version
BTW I've already tried this method for the g-sensor
http://www.addictivetips.com/mobile/fix-g-sensor-problem-on-htc-hd2-running-android-nand/
true2you said:
i just flashed coredroid (about 20mins ago) and still, same problems. Now i'm about to try
http://forum.xda-developers.com/showthread.php?t=915159&highlight=stock+desire
LITE version
BTW I've already tried this method for the g-sensor
http://www.addictivetips.com/mobile/fix-g-sensor-problem-on-htc-hd2-running-android-nand/
Click to expand...
Click to collapse
You should have no problems with the CMYLXGO Rom. I have used it in the past and it was great. Good luck!
nope, didn't work either. Still had call issues and g-sensor issues.
Now i went back to a stock wm rom just to make sure. I can confirm that it's not a harware issue, both phone and g-sensor (+ auto landscape) calibrating are working in WM6.5.
I'm really lost. I think that the problems are coming from somewhere else.
I'm through testing roms, as i said, they're all running just fine except for those two things. I'll try another approach. For example, i'll scan xda "entirely" to try and find g-sensor fixes and call freeze fixes.
But then again, every time i search the "g-sensor" term in rom or general threads, the results alwas show things about "proximity sensor"...
Just trying to troubleshoot.....
The G-sensor and call problems you are experiencing are very odd. I'm sure you have already done this but if you are using CWR to install Rom's, are you wiping all of the previous information like Data, cache, system, sd-ext, dalvik cache. I am just wondering if these problems could be caused by previous Rom's that were installed on your phone. I have used CMYLXGO's Rom and found very minor issues and the current Rom I am using (Dungphp Pyramid Sense 3.0 v1.4) has neither call or G-sensor issues anymore. Sorry for all of the trouble you seem to be dealing with....
Just to chip in on this thread some I use HyperDriod-CM7-v2.0.1 for my daily ROM and have been for some months now. Check out my sig for a link to it. I have also tested a great number of ROMs on my HD2 and they all seemed to work pretty good. I have even tested several MIUI ROMs and they would be good for a daily driver also. But as member Yerdan said it is strange you are having this issue.
I've tried most every rom Pre-Sense 3 and I've never experienced these problems, the only 'call' problems I've had is the Dialer process freezing sometimes when answering a call and that was fixed by flashing Raf 1.8 instead of using the 1.9OC that the roms came with...mic gain is also an issue on Android but http://forum.xda-developers.com/showthread.php?t=860850 fixes that issue. G-Sensor is something you're doing wrong, no offense.
Start from scratch, SD Flash an Official rom then go through the steps, flash hspl 2.08, Task 29, flash .50.14 radio, flash magldr, flash recovery (WITH THE APPROPRIATE SIZE FOR YOUR ROM) and then flash your rom; if all that is done correctly, it's a user/hardware issue, the only other problem you can run in to by starting fresh is not flashing the proper things, not flashing the proper sizes or not clearing out the proper data on your SD card (Android/Data folders and such on your SD card can cause it not to boot)
hd2k10 said:
G-Sensor is something you're doing wrong, no offense.
Click to expand...
Click to collapse
That brought to mind something about these Android ROMs on HD2...never calibrate the G-Sensor. If anyone does, lay if face down to calibrate it. Otherwise it will be funky if calibrated normally.
true2you said:
i just flashed coredroid (about 20mins ago) and still, same problems. Now i'm about to try
http://forum.xda-developers.com/showthread.php?t=915159&highlight=stock+desire
LITE version
BTW I've already tried this method for the g-sensor
http://www.addictivetips.com/mobile/fix-g-sensor-problem-on-htc-hd2-running-android-nand/
Click to expand...
Click to collapse
For the Coredroid. Don't download V3. Go for V1.6 Froyo. Best Rom, bug free to the point of only one issue that i know off, USB connection thingy, but on Pc you just click "Continue without Scanning."
But if that is what you have then, i Fails xD.
hd2k10 said:
I've tried most every rom Pre-Sense 3 and I've never experienced these problems, the only 'call' problems I've had is the Dialer process freezing sometimes when answering a call and that was fixed by flashing Raf 1.8 instead of using the 1.9OC that the roms came with...mic gain is also an issue on Android but http://forum.xda-developers.com/showthread.php?t=860850 fixes that issue. G-Sensor is something you're doing wrong, no offense.
Start from scratch, SD Flash an Official rom then go through the steps, flash hspl 2.08, Task 29, flash .50.14 radio, flash magldr, flash recovery (WITH THE APPROPRIATE SIZE FOR YOUR ROM) and then flash your rom; if all that is done correctly, it's a user/hardware issue, the only other problem you can run in to by starting fresh is not flashing the proper things, not flashing the proper sizes or not clearing out the proper data on your SD card (Android/Data folders and such on your SD card can cause it not to boot)
Click to expand...
Click to collapse
Just to clear things : Here are the steps i follow -
-stock wm6 flashing via "usb loader"
-panasonic sd formater (not every time)
-hspl 2.08 + radio (2.15.50.14) (not every time - only after stock rom)
-task 29 (not every time)
-magldr 1.13
-flashing recovery via magldr usb flasher option
-installing zip via sd card
What i never do (or don't get) is the switching of kernels. I'm guessing that it's already in the ROM's zip package and that it shouldn't be replaced because they're made to use as they are (my guess).
did you check to make sure you partitioned your sd correctly? also do you system partition correctly when going from 1 rom to the next? some ppl tend to skip over this so that could be a possible cause. i know there are a couple roms that if i take the sd card out while using it it wont reset my phone so maybe you could test to see if maybe something is going on with your sd card. i think Bluetopia HD found here is 1 if im not mistaken.
im not sure how you would have the same problem with so many different roms but i can say bluetopia is practically bug free. I haven't came across any as of yet.
if you want a easier list to look for android roms listed on xda go here.
to check how you partitioned your sd and fix it if needed you can use this free tool by going here.
Ok for the record of the OP
1. Did you buy a used HD2
if Yes
There are numerous threads complaining that the G sensor ( and by extension the other sensors ) DO NOT work ONLY on Android after a touch screen replacement.
They work PERFECTLY on WINMO
Perhaps thats your ISSUE...
Link http://forum.xda-developers.com/archive/index.php/t-1069578.html
IF NO and your is a NEW Device get it fixed By HTC
IF your is a USED device and does not have a Touch Screen replacement...
lets continue with the discussion
just how has xda failed you?
true2you said:
I just bought a used euro HD2 because i tought that new phones on the market don't have what it takes to justify their 600€ price (sensation lacks gs II's power, gsII lacks sense).
Well i've been searching and reading for 6days at xda, tried over 5 SD roms and at least 10 NAND roms.
I'm starting to think that those hd2 forums, as deep as they can be, are a big FAKE.
My problems : no g-sensor and freezes while calling. I've tried a lot of fixes and tutorials and still nothing.
Also, the search thread tool is a real pain since it doesn't use the google search system anymore.
Now please, i'm everything but a noob and still i can't manage to find a solution to these problems. This is my last attempt for getting help. Can anyone link me to the solutions if they are obvious (or not).
Also i'd like to ask, is it REALLY possible to use a nand rom as a daily driver? I'm not looking for anything fancy, just some basic Froyo with htc sense.
Thanks in advance for anyone who at least reads this.
Click to expand...
Click to collapse
First of all sire, I would say BALLS TO YOU. Having said that, I cant help but imagine your idiocy and laugh on people like you.
1) There are already numerous threads on what all is not working, You should have done your Homework before getting a 2 year old device then running free software made by people who have a life of their own and then Complaining on their face.
2) If you want perfect experience, go to WM6.5 and vent your anger at HTC support.
3) No matter what or how painful it is to search, you must do so. Failing to do so just expresses your idiocy and how much of a noob you are.
4) Having less than 200 posts and just a single thanks, i suggest you quit xda forums as you are of no use to us. And we don't owe you anything.
5) The best Sense froyo rom i found is from Qaliza Desire HD v3.0 with some tweaks from v4.0 (Figure it out yourself, SEARCH) which works no prob on my EU LEO.
I hope you will go through the following video and learn a thing or two:
XDA hasnt failed me. but maybe it may be a problem with magldr. i used maglr over and over again and i faced alot of problems my phone would freeze to the point of having to pull the battery. Gettting bootloops when watching youtube and i get an incoming call, but my solution was CLK. i used kay's hd2 toolkit and now im on clk with no problems. i switch roms alot not cause im not satisfied but because i like customization. the best rom in my opinion is Tytungs NexusHD2 gingerbread rom, but also i used Hyperdroid 2.1.0 HoneyBadger, and langthangs MIUIROM. Just read all the directions before proceeding and find the right Rom for you. PEACE
Hi,
G sensor in my HD2 didin't work, I have a NAND ROM from AmeriCanAndroid AOSP HD2 GB2.3.5 CM7 | bk2sdext [KERNEL:ACA823].
I reading this topic, I try this metod
-*GSensor-Calibration tool: To use it
In terminal emulator type, su (return)
bma150_usr( lay phone flat on back and hit return )
exit(return), exit(return and close
Click to expand...
Click to collapse
But still is not working, I download from market app Buble for calibrating,- dosen't work.
Do you have any answers for fix it?
I checking sensor three SD rom, still not working, and this NAND rom, but in WM g sensor works great.
Brothers help me
I had that problem happen to me when i first released SuperCM(WP)7. It was a converted sd build from isaiah12345 and there was problems. Thats why i had to compile from scratch with my build cause certain builds are perfect in winmo because the build uses all the calibration from winmo but straight nand it has to be built differently. I would read the thread to see if anyone else complained about the same problem than see what the solution is. if not than try another CM 7 build. They have the nightly CM 7 and TYPHOONS CM 7 which are both good roms. I would recommend my builds but they have a slight bug when i compiled it. the usb wont mount unless you use multi mount lite or pro if you decide to support the developer and it mounts it. Hope that helps.
Unless the problem was fixed and I missed the info, we can't calibrate the g sensor in Android rom. It didn't work last time I tried.
You will need to reflash the rom again and don't touch the calibration routine. The sensor will use calibration file provided from within the rom.
Thanks for any answers. I flashed this NAND rom http://forum.xda-developers.com/showthread.php?t=769026
I don't touch calibration routine.
G sensor still not work, meybe my HD2 it's not compatibile with Android? I mean work G sensor.
Nobody can help in any way, I do not know what to do.
Wait for the rest of the answers.
You will get more and better answers when you ask in the right forum/thread
This is the DEV forum. Ask in the Q&A or in the ROM-thread.
Who help me?
Sent from my HTC HD2 using Tapatalk