Related
Hi all, back in the days I had a Raphael, we had a great thread going where you could ask quick cooking questions of other chefs. I am proposing that this thread be used BY CHEFS ONLY to get quick help with issues in ROM development.
I will start it off with a question of my own:
I think I may have messed up my runcc.lua file as I tried to add in the sdconfig.txt support and now whenever I boot my ROM i get a popup window that says "Error running script". I was wondering if a LUA file has to be in a particular encoding (ie Unicode, UTF-8, UTF-8 Signed etc).
I will do my best to help out people with what I know.
Regards,
B
So that went down like a sack of lead balloons! I do have another problem and not sure what caused it:
Whenever my phone goes into standby I cannot wake it and have to remove the battery to reset it. Have any other chefs had this problem?
sounds like some tweak you cooked is causing it... i had that once
After floating round the WM6.5 release thread in Dev and hacing, someone posted a link to a dumped 25005 xip that should hopefully resolve the problem (something about the rollup releases that causes issues. If it works I will let you know
Hmmm, there seems to be some incompatibilities between the 2.07 OEMXIPKernel and the newer MSXIPs that causes the device not to come out of standby. The older OEMXIPKernels seem to work just fine.
I even re-dumped the 2.07 TMo US rom to get a fresh OEM Kernel to see if I had made a mess of it at some point and no luck there
Please can anyone help out with this?
B4PJS said:
Hmmm, there seems to be some incompatibilities between the 2.07 OEMXIPKernel and the newer MSXIPs that causes the device not to come out of standby. The older OEMXIPKernels seem to work just fine.
I even re-dumped the 2.07 TMo US rom to get a fresh OEM Kernel to see if I had made a mess of it at some point and no luck there
Please can anyone help out with this?
Click to expand...
Click to collapse
I think it should be something else, cos I use the 2.07 kernel with the newer msxips and there are no problems with them.
I had the same issue with my earlier kitchen. I've spent hours to find the bug, but in vain...I couldn't find out what caused the issue, so I've rebuilt my kitchen from the scratch...
seatone said:
I think it should be something else, cos I use the 2.07 kernel with the newer msxips and there are no problems with them.
I had the same issue with my earlier kitchen. I've spent hours to find the bug, but in vain...I couldn't find out what caused the issue, so I've rebuilt my kitchen from the scratch...
Click to expand...
Click to collapse
Im thinking I might have to do that aswell Im trying an older build with new drivers, and new radio. If that works I might just stay at that build, I generally see not much difference between all the different builds and com branches anyway!
i doubt it is anything to do with ROM or OEM i suppose quick enough to rule them out , just disable all ext packages build a rom and see if problem is still there, ive had the same issue before im sure its one of the ext packages or a custom reg entry
I'm so tired of this phone right now but since my company only offers HTC phones with WinMo this is the only one that's "interesting".
It has actually worked kinda well the last month but after I changed ROM last Friday it has been totally unusable. After the ROM-change I couldn't hear anything when I made a call so I changed radio, problem solved... I thought.. The phone freezed after one hour so I had to take the battery out and when I tried to boot it again it took the phone 6-7 minutes to get past the screen with Rom and Radio information. When it got past it I got the first booting screen with the "Windows is setting up your phone" blahblah so it was like I have made a hard reset.
Ever since I have tried different ROMs and different radios but nothing helps, it keeps giving me these crazy problems. On some ROMs I'm unable to save and access my contacts etc. One thing that is persistent is the time to get pass the screen with ROM and radio information, it's really slow no matter which ROM or radio I'm on. Of course I haven't tried all ROMs and radios but around 4 ROMs and 3 radios.
Is there anything else then ROM and radio that can be updated or replaced because I'm on the edge here and I'm about to throw it in front of a car just to get rid of it.
I appreciate all the help I can get.
Hi, try out OzROM and Radio 2.08_2. This combination is very fast, stable and usefull. I have testet a very lot other Roms but OzROM is the best off all !
Never hang since 1.30, good phonequality and no big Problems.
And remember to make a hardreset after flashing !!!
HQ_seppel said:
Hi, try out OzROM and Radio 2.08_2. This combination is very fast, stable and usefull. I have testet a very lot other Roms but OzROM is the best off all !
Never hang since 1.30, good phonequality and no big Problems.
And remember to make a hardreset after flashing !!!
Click to expand...
Click to collapse
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Edit: is this the radio you suggest: 2.08.50.08_2 ?
scanie said:
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Click to expand...
Click to collapse
How many ROM's have you flashed since you got your HD2? were they from the same Cook?
I always Flash a Stock ROM (via USB of course so I don't lose HSPL) before flashing to a new ROM by a different Cook... (so If I was on LIA, before flashing Dutty's I flash the Stock ROM, before flashing Artemis, Flash the stock ROM, before flashing Miri... and so on...)
If I want to get a truly clean device, I do a task 29 via mtty, which is akin to formatting your PC before you install a new OS.
Try mtty, its fast, easy and the results are proven (head over to the stickied mtty thread on HD2 ROM Development)
mtty
scanie said:
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Edit: is this the radio you suggest: 2.08.50.08_2 ?
Click to expand...
Click to collapse
might be time to mtty mate while you still can becarefull downgrading the 2.0.8 roms some people are having problems read the site about those
DJGurth said:
might be time to mtty mate while you still can becarefull downgrading the 2.0.8 roms some people are having problems read the site about those
Click to expand...
Click to collapse
one of the reasons I have never flashed a custom ROM...the stock rom may have bugs but I have found that custom ROMS have so many more!!
I've yet to find a stable one, so now I don't bother with them...pity as they do have some nice features, but I can't live with the drawbacks
If its a company phone and, I assume, you use it for business purposes in the main and it was working ok, why did you upgrade the rom with the risk that you might break something?
How much reading have you done on here? Have you looked at the Hints & Tips thread fpr fixes or the "HD2 died- or did it" thread that deals specifically with the lockup issue?
If you are a secret rom junkie, flashing roms every 5 minutes, are you aware of the issues with doing so and the need for MTTY?
I tend to be very helpful to people in trouble; however I am struggling to understand why you fiddled around with a business phone that appears to be critical to you and was, as I understand it, working perfectly beforehand?
WB
scanie said:
Thanks for the reply. I will test what you suggested but I don't have that much hope
I always hard reset after flashing.
Edit: is this the radio you suggest: 2.08.50.08_2 ?
Click to expand...
Click to collapse
Jes thats it, you can download it on the OzRom Site
If you get Duttys HG ROM from my sig radio 2.08 is included so no extra flashing needed
In addition to the other recommendations in this thread (mtty/stock rom, etc.), I would recommend you stick to the 6.5 series (21xxx) rather than 6.5.x (23xxx) for added stability and speed.
wacky.banana said:
If its a company phone and, I assume, you use it for business purposes in the main and it was working ok, why did you upgrade the rom with the risk that you might break something?
How much reading have you done on here? Have you looked at the Hints & Tips thread fpr fixes or the "HD2 died- or did it" thread that deals specifically with the lockup issue?
If you are a secret rom junkie, flashing roms every 5 minutes, are you aware of the issues with doing so and the need for MTTY?
I tend to be very helpful to people in trouble; however I am struggling to understand why you fiddled around with a business phone that appears to be critical to you and was, as I understand it, working perfectly beforehand?
WB
Click to expand...
Click to collapse
Yes its a company phone and yes it worked "ok" after trying different custom ROMs. But I think that a phone in this price class should be working perfectly and not just ok. That's why I tend to flash a new ROM once in a while, because I want perfection. And we all know that HTC won't give us that.
Even though the last working ROM was ok, there still were some issues that didn't affect my daily use but that bugged me a bit, that's why I wanted to try a newer ROM.
I don't know that much about MTTY but I will look into it now. Thanks for the heads up.
no device will give you perfection - it's impossible as everyone has different perceptions of perfection
EddyOS said:
no device will give you perfection - it's impossible as everyone has different perceptions of perfection
Click to expand...
Click to collapse
True, but all programs and features that's implemented in the phone should work as designed. If they don't, the device isn't perfect imo.
Do you know how many issues Apple fix with the iPhone each week? All phones have issues, all PCs have issues, anything to do with tech has issues!!
End of the day you either try and fix it, send it back or wait for HTC to fix it (although some issues may be down to M$ themselves)...
LeoLite 2.3 with radio 2.08.50.08_2 is sweet!
The ROMeOS ROM is great as well - head to romeos.monx.biz for that one...
MTTY
I'd reiterate the advice about the MTTY, my device was utterly corrupted and flashing didn't help. After a MTTY format its back to 100%. Choose your ROM's carefully though, i still had some stability issues with some of the more exotic ROM's (even after a MTTY), I ended up choosing something closer to stock (Dutty) which was rock solid.
Hello everyone. I've beeing seying alot of people saying that before a ROM worked with a radio edition , wich GPS worked perfectly and later stoped working, and i decided to study the case in order to know, why is it working.
I've been testing diferent ROMs and Radios.
We've got the radio editions:
Radio_HTC_PVT_32A_6.35.10.18
Radio_HTC_PVT_32A_6.35.08.29
Radio_HTC_PVT_32A_6.35.07.29
And according to an article wich i read here on the forum, teoricly we can use any radio, and the phone wont brickitself.
So i've been using a radio 6.35.08.29, and tested on a ROM wich required the radio 6.35.10.18. As predicted nothing bad happened, worked perfectly . But when i tried the GPS it didnt work. Anyways i decided to test a ROM wich required a 6.35.07.29 radio. Happened the same thing. GPS didnt work.
I Flashed 6.35.07.29 radio on that rom. GPS worked without any problem. I changed radio again to 6.35.08.29 GPS didnt work again.
Once again i went back to my original ROM, and happened that my GPS didnt work, wich before have worked, like the situation most of us encounter here at the forum.
What can we conclude from this?
In my opinion, there are files from the radio wich when we make a backup or even install a new rom, wich wont complete the system instalation of the radio, and you'll have to reflash the radio edition compatible with the ROM you just instaled.
Another theory is that after installing an incompatible ROM, GPS is turned off automaticly .
Anyways, i would like to know your experience and your opinion, i'm sure here are people wich know more about this then i do
Thank you. Best regards everyone!
anyone?
This would be very interesting stuff if it could be proven correct.
Sent from my HTC Magic running Smoki using the XDA mobile application powered by Tapatalk
Thanks for the reply. i know. Also this would help to avoid bricks and unecessary procedures. The porpuse of this threat is to understand what makes this happen in orther to avoid, and make everything functional.
I have no idea whether this makes sense or not. I also don't agree that "Solution found" (as in the topic) - rom cooks usually don't state the required radio version beyond 6.35.whatever or the equivalent for old radio, I don't know about any of them being aware of such a (hypothetical) requirement.
My understanding was that the different 6.35 variants are regional editions, and that using the wrong one for your part of the world might make your cellular telephony and/or networking operate suboptimally. Not that I have seen any proof that this actually happens. I guess nobody knows whether the radio stores persistent state of any sort, but I suppose somebody familiar with the kernel source might know whether anything the kernel does depends on the radio version (or minor version). Otherwise the radio requirement would stem only from the origin of the RIL libs and libgps, right?
I don't know much about any of this, so the above is just guesswork. Hopefully someone more informed will contribute to this thread.
drbobb said:
I have no idea whether this makes sense or not. I also don't agree that "Solution found" (as in the topic) - rom cooks usually don't state the required radio version beyond 6.35.whatever or the equivalent for old radio, I don't know about any of them being aware of such a (hypothetical) requirement.
My understanding was that the different 6.35 variants are regional editions, and that using the wrong one for your part of the world might make your cellular telephony and/or networking operate suboptimally. Not that I have seen any proof that this actually happens. I guess nobody knows whether the radio stores persistent state of any sort, but I suppose somebody familiar with the kernel source might know whether anything the kernel does depends on the radio version (or minor version). Otherwise the radio requirement would stem only from the origin of the RIL libs and libgps, right?
I don't know much about any of this, so the above is just guesswork. Hopefully someone more informed will contribute to this thread.
Click to expand...
Click to collapse
I think you are right. Each version is about the region i didnt remember we had diferent GSM frequency around the globe.
what confuded me was that there was ROMS wich Devs said that in order to work we should have their Radio edition. Is this a real problem if we use other radio?
please I would request more cooperation on this post . Thank you!
The same thing happened to me today. I had tried a 2.1 ROM and returned to my 1,5 CursorSense and my GPS would not work. I found that reflashing the Radio cleared up the problem. There are several posts in the CursorSense thread that describe the problem and fix.
wjsturgis3 said:
The same thing happened to me today. I had tried a 2.1 ROM and returned to my 1,5 CursorSense and my GPS would not work. I found that reflashing the Radio cleared up the problem. There are several posts in the CursorSense thread that describe the problem and fix.
Click to expand...
Click to collapse
whats the fix provided? Could you please redirect me to that fix? Thank you
jgcaap said:
whats the fix provided? Could you please redirect me to that fix? Thank you
Click to expand...
Click to collapse
Do a search on the CursorSense ROM Thread for GPS:http://forum.xda-developers.com/showthread.php?t=592856
thanks i didnt know there was a button search for thread. Very helpfull, i've been searching i found no fix. But if there is i must find out to see if is related.
Just confirmed something, this patch is not related to the GPS fix. GPS wont find location unless you reflash the rom of the location wich the rom was made for. Wich respects again this teory. I would request if possible someone to assist in this ! thanks
anyone? Big please?
i request again more knowlege please
It worked for me!
I went to 2.1 roms, then switched back to Cursorsense and lost GPS, so I reflashed Radio_HTC_PVT_32A_6.35.10.18 and it works!
Mod. edit: not dev related, moved to general
so... if i understand... we must flash each of those versions to see witch works?
mine works but only after using gps status aplication to get a fix
Draken Korin said:
Mod. edit: not dev related, moved to general
Click to expand...
Click to collapse
How in the world is this not dev related???
Dont know ask the mods lol
Sent from my HTC Magic using Tapatalk
Hey all. Yes, before any of you say ANYTHING, I know this has been asked before...many times. But with searching, I have not been able to find a definitive answer to my query. We all know that if you run Android on the stock 2.13 T-Mobile ROM that you will get the whole robot voice through the earpiece...but my question is WHY does this happen? I have read that it is something to do with some .dll's within Windows...which would make sense as to why some ROMs work with it but others wont...but how is WinMo messing with Android if HaRET unloads WinMo from RAM before it starts Android. Maybe my understanding of it is wrong, I do not know. Basically I want to know for my own knowledge as to why it happens, and maybe offer some assistance. If it is something as "simple" as a .dll conflict, then maybe there is a workaround for existing users of the 2.13/.14 ROMs. I am one of those people, and through my flashing of the HD2, have found 2.13 to pretty much be the fastest and most stable for my uses, but I would also like to use Android. Anyways, in short, if someone can point me to exactly why this happens, maybe I can help out. Thanks.
i hope to get answer n solution for tis oso..
all i nd is jus HSPL + new radio or i nd a new cooked rom too?
thankz~
What is the best radio to flash if im going with the superclay superHD2? I just one that i can flash easy and not hear the robotic voice anymore
I have used radio 2.12 and 2.14 with success. I have never experienced the robot voice. However I never used android with stock roms.
I'm using vbn droid rom (minimal install of winmo) along with Hyperdroid build 1.6. I've used superhd2 build also successfully.
not sure about the robot voice
not sure why the sound gets screwed up but......I know you can run the newer stock 3.14 leaked update and it will work with android and you can keep a fully stock rom on your phone and get android too.
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