Related
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
webmanya said:
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
Click to expand...
Click to collapse
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
silverwind said:
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
Click to expand...
Click to collapse
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
webmanya said:
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
Click to expand...
Click to collapse
In fact, I still can use Imilka's, Rafdroid and few other Nandroid ROM
But, I dont want to make it worse knowing that there is some badblock(because I want to sell it)
So, I am back with Winmo and SD Android. It is much safer for me
Cheers
I apologize if there actually is a thread explaining what I am talking about. But I have searched all over. And I just can not figure it out.
I have the Dandiest ROM
http://forum.xda-developers.com/showthread.php?t=881937
I am using v4.31.44.12
It's my first rom flash, everything went fine and all.
The problem is that everything goes much too slow. Booting isn't an issue. but Everything regarding apps and calls and such just goes really slow.
When I get called, I can pick up. but I can't hang up because the phone just freezes.
Every app I install (which always takes roughly 3-5 minutes per app, after download) I have to constantly wipe the screen to keep it awake, if the screen sleeps during install, the phone completely freezes and I have to pull out the battery.
I wonder what is causing this, and if anyone has/had this problem before on a different ROM?
I have ext4 on my SD, shared storage or whatever it is called.
I have read some stuff about speeding that up or something, but I don't understand it.
I'm thinking it has to do with that. I installed/done everything following tutorials, so I should've done everything right.
Basementnugget said:
I apologize if there actually is a thread explaining what I am talking about. But I have searched all over. And I just can not figure it out.
I have the Dandiest ROM
http://forum.xda-developers.com/showthread.php?t=881937
I am using v4.31.44.12
It's my first rom flash, everything went fine and all.
The problem is that everything goes much too slow. Booting isn't an issue. but Everything regarding apps and calls and such just goes really slow.
When I get called, I can pick up. but I can't hang up because the phone just freezes.
Every app I install (which always takes roughly 3-5 minutes per app, after download) I have to constantly wipe the screen to keep it awake, if the screen sleeps during install, the phone completely freezes and I have to pull out the battery.
I wonder what is causing this, and if anyone has/had this problem before on a different ROM?
I have ext4 on my SD, shared storage or whatever it is called.
I have read some stuff about speeding that up or something, but I don't understand it.
I'm thinking it has to do with that. I installed/done everything following tutorials, so I should've done everything right.
Click to expand...
Click to collapse
Have you dont the following ? its in his main post . it seems like what you are experiencing is common .
1.. DON'T expect it will work out of box.
2. DON'T expect it will be as light and fast as Gingerbread.
3. DON'T expect that some legacy problem will disappear
4. Reboot your phone at lease twice after flashing or installing, after 1st boot into setting screen, long press the right button to recall the boot menu, reboot. Can not use /Update_DL method to install app before 3rd reboot.
5. For this version, due to the base has been changed throughly, can not use previous data.img or ext4, remove existing data.img and set data_img=1 to let system generate one for you, or set format_ext4=1 to format your ext4 if you are using ext4
6. DON'T set any config for 1st installation except data_img=1(for data.img) or format_ext4=1(for ext4 user). if your have tmous phone, no need the config.txt.
7. For SD or magldr, if 1st installation failed, must delete the system.ext2 file under /Desire_DL to let system convert it again.
8. Use Windows notepad create a file named config.txt, save it under /Desire_DL, only need to put the necessary config inside it, say:
data_img=1
Click to expand...
Click to collapse
My advice go here http://android.hd2roms.com/ and pick a rom without issues like hyperdroid 5.8.0. Leave ICS alone for a while.
No offence intended to Dandiest but his last post was months ago
shanman-2 said:
My advice go here *Link* and pick a rom without issues like hyperdroid 5.8.0. Leave ICS alone for a while.
No offence intended to Dandiest but his last post was months ago
Click to expand...
Click to collapse
Thanks, It was my first rom I flashed, almost bricked my phone in the process, so I'm scared to flash again. haha.
elesbb said:
Have you dont the following ? its in his main post . it seems like what you are experiencing is common .
Click to expand...
Click to collapse
I'm not sure what I'm supposed to do.
Basementnugget said:
Thanks, It was my first rom I flashed, almost bricked my phone in the process, so I'm scared to flash again. haha.
I'm not sure what I'm supposed to do.
Click to expand...
Click to collapse
Read what I've quoted and follow . Like reboot a couple of times and such things as that . And this is an sd build correct ? From the link provided that's the impression I got .
Sent from my HTC HD2 using Tapatalk
elesbb said:
Read what I've quoted and follow . Like reboot a couple of times and such things as that . And this is an sd build correct ? From the link provided that's the impression I got .
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Oh, I'm sorry. I'm using NAND. I'm using the NAND version of the Dandiest.
Also, I've had this rom for like a month now.
There are plenty of guides out there, get the nand toolkit (it simplifies things a lot,thanks to ksubedi). Read the guides carefully !!
Have a look here...
http://forum.xda-developers.com/showthread.php?t=1402975
http://forum.xda-developers.com/showthread.php?t=929324
Best of luck.
By the way have you tried a factory reset.. if you can back up your apps and data this might solve your problem!!
Basementnugget said:
Oh, I'm sorry. I'm using NAND. I'm using the NAND version of the Dandiest.
Also, I've had this rom for like a month now.
Click to expand...
Click to collapse
Ohh well that changes a lot lol . was it laggy since day one ?
Hey guys, I need some quick suggestions if anyone has it. Currently I have a non working phone.
I have been running an ICS NAND rom on my hd2 for a while now, havnt had any issues (a few niggles with the rom, nothing major) so I thought today I would update to the latest version.
I used the hd2toolkit to resize the partition to the biggest size it would allow, then used ad recovery to flash the new .zip to the nand. This is where my problems started, whenever i booted it just showed the boot animation, (I waited over an hour and pulled the battery out and re booted / reflashed a few times).
I found with a differnet rom i tried, pulling out the SD car would allow it to get to the welcome screen, but no screen input was accepted. I thought this was a bit weird but pushed on. I tried a different rom and it stated after flashing that it was optimising applications and looked like it was stuck in a boot loop. I did some reading up about it and found that task29 should help. I ran this but then all the phone would do is show the green HTC on the white background, it wouldnt let me to get into magdlr menu.
I then decided to to a full restore and go back to the wm rom from th HTC site (The australia telstra version), this seemed to flash on fine, but now I can not slide or click buttons in wm, no screen input is accepted. Which is strange as it was doing this in an android rom, as I mentioned previously.
Any ideas on how I can get touch working / get a NAND android rom to work again.
Thanks in advance guys
First verify that you have hspl installed by powering on while holding vol down button to get to bootloader screen
Go back to the hd2 nand toolkit
1.task29
2. Select either cLK repartition or Magldr repartition and select size for your rom (not the maximum size). 200 mb is fine for ics using sdext partition.
3.Select magldr update recovery or cLK install recovery depending on your selection above.
4. Reboot phone by pressing power and holding to get to magldr or power and home button to get to cwm recovery.
5. Install ICS from sd card as before
Thanks for the help, I had to flash a different radio version to get magdlr to boot.
I now have android running of my NAND, but the screen is non-responsive now, as it was yesterday.
I doubt it is hardware related, because I have never had an issue before yesterday when I wanted to change the android version, any ideas how I could get it working?
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
htccraze said:
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
Click to expand...
Click to collapse
I have tried two different android roms and the stock wm image from htc's site, all of which the screen doesn't work on. I will have a try with a cyanogen ROM and see if that makes a difference. Thanks
http://forum.xda-developers.com/showthread.php?t=769026
I just tried this rom and still no deal. This is very weird as I haven't had any issues with the screen at all, the phone is still in new physical condition.
Does anyone want to have a stab in the dark, as I really need to use it as a GPS tomorrow and any help would be appreciated.
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
htccraze said:
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
Click to expand...
Click to collapse
When installing a new rom, I have resized the magdlr partition, then copied the .zip to the sd card, then in ad recovery installed the zip through there. This has worked fine in the past. I followed the videos you have linked and I'm pretty sure I'm doing everything right and yes ive used task29 several times. In AD Recovery every time it states that installation has been successful. I have also formatted my SD card many times.
The ROM you linked, I can find download links on the page, not sure if I'm just missing them.
I just tried an SD card rom, its doing the same thing, no touch input is accepted.
Does NAND roms and SD roms not working imply that it could well be hardware? I just dont understand as it stopped working when I was reflashing yesterday and it was not dropped or roughly handled in anyway during this process.
I am now going to investigate MTTY (for bad blocks) and try reflashing back to original WM again. Please post more suggestions if anyone has them.
Another update: I just restored to default using the method listed below.
http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/
It took around 40-ish minutes and still no input from the screen, this is seriously frustrating.
WM boots fine and everything, but still no input is accepted.
I'm sorry to say but if your having the same problem with all that then it sounds like the digitizer stopped working. Maybe someone else knows something I don't so I would wait to see if they could help out.
Sent from my HTC HD2 using XDA
Thanks mate, I am not sure why it would have just stopped last night. Appreciate all the help! I'll see if anyone else has any suggestions.
It's not a problem. I do have to admit that it does seem pretty odd the timing of it. Hopefully it's a not the digitizer and someone would be able to point out what might be the cause of everything.
Sent from my HTC HD2 using XDA
This may seem a little crazy, but after having a search online about my issue, it seems that a ribbon going to the screen / digitizer is behind the power button on the HD2s, which apparently can get loose and after a sharp press of the button it started accepting screen input again!
The issue for me now is that when the power button it will stop accepting input again, untill I press it firmly again. I think I may need to open up the phone and check all the connections now.
for some time, after restarting or turned on my leo, if I receive a call, the phone freezes and I have to restart it. but if after a reboot, I'm the first to make a call to someone else, I can talk quietly and the phone will not lock. this happens for all subsequent calls. I thought it would be a problem with the ROM I used, but also by changing the ROM problem occurs again.
What should I do?
my LEO:
HSPL 3.3 (I also tried 8.2 but I get the same problem)
radio 2.15.50.14
Bootloader CLK 1.5.0.3
ROM: Pixeldroid Jelly Bean AOPK 4.2.2 v 6.0 FINAL 20/05/2013 (with date and onext linuxswap)
thanks for your help
p.s . sorry for my english!
I was going to ask you to post your question here, in the ROM specific Q&A thread. But you said you changed the ROM and the problem is still there.
Try a fresh install, remove everything, install a new ROM and BEFORE restoring your apps or setting up the phone, try to reproduce the problem. It could be because of one of your apps, or one of the settings.
Marvlesz said:
I was going to ask you to post your question here, in the ROM specific Q&A thread. But you said you changed the ROM and the problem is still there.
Try a fresh install, remove everything, install a new ROM and BEFORE restoring your apps or setting up the phone, try to reproduce the problem. It could be because of one of your apps, or one of the settings.
Click to expand...
Click to collapse
Unfortunately, even after a fresh install, my LEO crashes when I receive an incoming call.
Moreover , i have no badblock
Your problem is weird. I have just made a search, and found about two people with a similar problem, but with a dead end, i.e. not answered.
I see that you have SWAP enabled, try to remove its partition from the sd card and reinstall the ROM without swap.
I had only troubles with Swap/Odex checking while inatalling ROM, so yeah, worth trying.
Also, it still can be HARDWARE issue as nothing (which should) helps.
If unchecking swap wont help, i'd suggest doing hard reset and if WM has same problem, go to HTC or any GSM store, maybe big heads can help with that then.
I hope You will get it sorted out!
Sent from my NexusHD2 using xda app-developers app
ZathuraPL said:
I had only troubles with Swap/Odex checking while inatalling ROM, so yeah, worth trying.
Also, it still can be HARDWARE issue as nothing (which should) helps.
If unchecking swap wont help, i'd suggest doing hard reset and if WM has same problem, go to HTC or any GSM store, maybe big heads can help with that then.
I hope You will get it sorted out!
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
I put WM 6.5, I saw that the phone does not freezes when I receive an incoming call. what do I do? I do not want to stay with WM, Android is much better!
marieto said:
I put WM 6.5, I saw that the phone does not freezes when I receive an incoming call. what do I do? I do not want to stay with WM, Android is much better!
Click to expand...
Click to collapse
Long time ago had similar issue. Problem was in phone and second factor slowly dying sdcard.
I fix my problem by flashing back to wm6.5 then after did install back MAGLDR used newer Cwm (dont use old 3.x.x version). Ofc bought new sdcard.
My advice would be try now while you are on Wm 6.5 this rom, its SRAM version, meaning you will run from wm and it will be loaded in RAM so no messing with sdcard: http://forum.xda-developers.com/showthread.php?t=1868306
If it works, try to flash Magldr, don't use HSPL 3.3 instead use older 2.8, also don't use Cwm 3.x.x use instead 5.x.x version.
When you install android allways follow instructions especially how much system, data partition size must be and if you install JB version try NativeSd if your card is good one.
Hope it helps.
Sent from my HD2 using xda premium
This happened to my phone also difference being it didn't freeze all the time but literally half of the time whenever i got an incoming call. I did all the stuff being suggested here and tried multiple roms without success. Then i removed task killer after a fresh install of "CM9ight_leo_v1.1a_div2" rom and my phone hasn't freezed since, been two months now.
Hello
So i was ready yesterday to install a new android rom, going from GingerBread to JB(Pixeldroid 4.2.2). Later that day, i encountered a Bootloop problem while still on the GB, so i decided to install JB. I did it succesfully. Before going to JB i installed stock WM 6.5 just for a bit, and had no bootloop problem.
Then i went to JB on NAND (GB was on NAND too ) and then it started to bootloop again :/ Now, i don't know what to do and i have an extra problem. My power/end call button is dysfunctional (completely). Please help!
EDIT: I can't help but notice there are a lot of bootloop threads from yesterday and today. Weird isn't it?
EDIT2: Well, now i can use the power button. Yay for copper wires!
EDIT3: Now i partitioned the system 360M/5M cache, just as written in the thread (didn't notice that bit before :/ )
Now, it's just stuck on the boot for quite some time, keeps going and no change. If it's significant, i noticed before, when the HD2 was plugged in to charge, first the LED light got orange, then the loop happens. Now it's not glowing orange.
Well ...
Accelerator46 said:
Hello
So i was ready yesterday to install a new android rom, going from GingerBread to JB(Pixeldroid 4.2.2). Later that day, i encountered a Bootloop problem while still on the GB, so i decided to install JB. I did it succesfully. Before going to JB i installed stock WM 6.5 just for a bit, and had no bootloop problem.
Then i went to JB on NAND (GB was on NAND too ) and then it started to bootloop again :/ Now, i don't know what to do and i have an extra problem. My power/end call button is dysfunctional (completely). Please help!
EDIT: I can't help but notice there are a lot of bootloop threads from yesterday and today. Weird isn't it?
EDIT2: Well, now i can use the power button. Yay for copper wires!
EDIT3: Now i partitioned the system 360M/5M cache, just as written in the thread (didn't notice that bit before :/ )
Now, it's just stuck on the boot for quite some time, keeps going and no change. If it's significant, i noticed before, when the HD2 was plugged in to charge, first the LED light got orange, then the loop happens. Now it's not glowing orange.
Click to expand...
Click to collapse
My friend ... As I got , you installed a JB ROM on a GB ROM ? ... If thats Right , Its not a bootloop it's a mistake because the ROM hadn't installed completely but you can do a Full wipe before installing any ROM then Your ROM should boot correctly ... Any you had better name the ROM you installed ... Good luck
With Best Wishes
Hitman1376
hitman1376 said:
My friend ... As I got , you installed a JB ROM on a GB ROM ? ... If thats Right , Its not a bootloop it's a mistake because the ROM hadn't installed completely but you can do a Full wipe before installing any ROM then Your ROM should boot correctly ... Any you had better name the ROM you installed ... Good luck
With Best Wishes
Hitman1376
Click to expand...
Click to collapse
Well, i did manage to fix the bootloop. I did a full wipe through CWM and then i made a partition, and simply installed using the NativeSD method. Thanks anyways!
Accelerator46 said:
Well, i did manage to fix the bootloop. I did a full wipe through CWM and then i made a partition, and simply installed using the NativeSD method. Thanks anyways!
Click to expand...
Click to collapse
So the problem should be from the ROM ... Why don't you try An other NativeSD ROM ?