Related
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
Please mention your RADIO, HSPL and the last Android Rom in which this happened!
If your phone is booting, it's not bricked. Did you try another SD card? Have you tried doing a low level format on your SD card? If it were me I'd Format the SD card with an adapter on my PC, low level. Then I would put it back in the phone then run Task29. Then flash MAGLDR 1.1. Then Flash the CMY 1.4n Desire HD Nand build in the HD2 Nand Android Development forum. It's the most stable Nand build up there right now.
I would use the 2.15 radio that comes with the newest Tmobile ROM. You might have to download the 3.14 ROM from Tmobile and flash it first to get the Radio in there. Then Task29 after that. MAGLDR, Then the NAND build. Make sure you find the Task29.exe that doesn't have a radio paired with it. it's on this site somewhere.
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
hd2 running MIUI freezing up too
I'm a complete noob here so bare with me. I'm currently experiencing the same probs as lewy255 with the hd2 freezing up. It happens every now and then when I'm accessing certain apps. When the hd2 does freeze up, i have to take the battery out, wait, then boot up again. Once it tries to boot up it freezes on magldr, then i got to take out the battery again, wait, then power it on again. It seemed to happen when i first rooted my hd2. The first ROM i flashed after rooting was typhoon CM7. Currently have:
HSPL 2.08
radio 2.15.50.14
MIUI version: 1.5.27
I hope this isnt a hardware issue cause i bought this phone from one of my friends and he didn't have the receipt. Please advise on what i can do to fix this freezing issue.
Thanks
Sounds like cpu overheat freeze. When you were playing music and charging it the first time it froze, was the phone and/or battery hot?
It's very possible that it got too hot once, and now the cpu its self gets too hot much easier now that it has already happened once.
Sent from my HTC HD2 using XDA App
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
germotlp said:
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
T-Macgnolia said:
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
Click to expand...
Click to collapse
t-mac
I tried installing setCPU and adjusted the temperature setting so if got too hot then the speed of the phone would be reduced, but still no luck.
What if i unrooted the phone and put everything back to stock? I think that way i will know for sure that its a hardware issue. I dont know much about phones but your probably right. I'll try running task29 and reinstall everything and see if that works, if not then i will un-root and put everything back to stock and test.
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Kailkti said:
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Click to expand...
Click to collapse
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
i have same problem with miui roms. I think this problem is about Miui Roms. Miui developers must solve this issue, there is no way..
When i try other Roms, there is no problem like this issue..
germotlp said:
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
in my opinion and its just my opinion, but you should flash a winmo 6.5 build than boot android from sd its safer because theres no need to worry about battery dying in magldr. and if theres a nand rom you want to try out i suggest using port a droid. im using now with the new nexus 2.8 with a 1gb data.img and it runs great plus i have 3 other builds on there also.
the phone is freezing often
slow touch responce
programs force closing
yahoo mail doesnt work anymore
its shutting down on its own randomly
and some other problems i cant remember.
its a nand CMYLXGO stock desire HD v1.1.3
is this a common problem, if so where can i find info aout it i searched for dead battery and didnt show much.
Maybe some data got corrupted. So you should reflash or flash another build. Maybe even your radio to be sure.
why does it happen? i thought we wouldnt have this problem with nand builds.
fuzzysig said:
why does it happen? i thought we wouldnt have this problem with nand builds.
Click to expand...
Click to collapse
well, lot of roms use the data2sd method for storing data on SD, for me its pure nonsense (app2sd is fine). With data2sd the risk is very high that you get data corruption and then all the weird force close madness begins. Now if you run out of battery your device doesnt shut down properly/cleanly, its the same as you would just pull a cable to shut down a pc. So running out of battery is the same as pulling the battery.
wow
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
kiki_tt said:
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
Click to expand...
Click to collapse
That's what it does for everybody.
the phone also started to have SOD.
i plug it in at night to charge, in the morning it would not wake up.
the alarm would go off but the screen is blank.
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Been there. The only solution that worked for was to flash it from scratch once again.
Dunno why the phone is acting this way but now I always charge or turn off my phone when my battery is down on 10 %. Better to be safe than sorry.
I'm using MDJ's CM7 v. 2.6 so I think this is an issue on many builds if not on everyone.
fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Since u are aware u can reinstall it again then simply do so...Yeah its a real pain but just tk time out n do it...I've been using CMY's builds for so long and have never encountered such an issue..but dats just me...
i see u r still using V 1.1.3, CMY has released a much more better build (but then u already know that), so go download dat...perform a Task 29 ,install MAGLDR ( u know d works) etc...
As 4 y a dead battery will cause this on a custom build and not on a factory installed ROM? ...Me thinks u already know d answer (stick 2 stock WinMo if u think its better)..
P.S. Remember charging ur battery to 100% b4 starting..gives u a fairly calibrated battery.
you could also try to wipe the battery information via magldr?
you choose recovery in magldr > clockworkmod recovery > advanced > wipe battery stats.
tried that didnt work
isnt there another way besides reinstalling everything over and over?
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
fuzzysig said:
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
Click to expand...
Click to collapse
?! it has been answered in this thread...
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
joostnl said:
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
Click to expand...
Click to collapse
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Buy her an iphone, then she can't pull the battery! :-D
Sent from my HD2 using XDA App
malybru said:
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Click to expand...
Click to collapse
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
lol, hahaha
joostnl said:
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Click to expand...
Click to collapse
ive seen a few posts where people have struggled with getting past boot logo, think it was fine after using a different partition in recovery but as your device is for the sd build am not quite sure how that works as Ive never had sd android or if having sd requires clockwork mod recovery? if so try different partition as i said earlier if not hang on till someone has the answer
johnerz said:
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
Click to expand...
Click to collapse
haha great answer, my girlfriend doesn't touch my hd2 or she gets alot more than a double dose with the tazer method, HD2 is not the solution for a women... you take the hd2 of her and buy her a iphone surly they are women material.
Ignore Post
Problems almost always occur after a few weeks or months of use for me, just reflash the ROM, and you'll good to go.
removing the battery is not recommended, it can corrupt files on the sd-card. Try to boot without sd-card and see if it helps. If your ROM does boot, it means the SD card is corrupted, you can try to backup the SD card and restore it after completely wiping the sd-card.
If your rom doesn't boot, than it meant there's something else going on, maybe corrupted flash, so reflash and try again. This will delete all your data, so be careful
if your girlfriend is not an daily flasher also might i suggest using a daf build. All the configuration is done for you. if you are using a sd build from magldr than make sure you change the name of the build than edit the startup txt like this "rel_path=whatever you name the build(example: "rel_path=MIUIROM nand_boot=1") the 1 for magldr 0 for windows 6.5. the reason for me saying this is all android builds create a folder android when they boot up with all your info like data and cache is in there. So its best to separate the two just in case you want to boot up more than two builds from sd.
Same here.
could be a bad block in your NAND memory. you can check this with cLK and fastboot.
see this post: http://forum.xda-developers.com/showpost.php?p=13600733&postcount=9
i checked mine and there was a bad block in the userdata. i think that is wy my phone was freezing.
now i have flashed cLK and untill now its working great!
Hey guys,
I know everyone is going to first think, What the hell, this is too easy what a noob.
Anyway, point is, ive been looking for a tutorial on this for ages and just can´t find one.
On all Android Roms they always just write things like "Also make sure to intall the kernel" and thats it or when you look through generall ROM tutorials for android you just see "Don´t forget to install the coresponding kernel"
Nothing on how to do it.
So I have the following questions please:
1. I want to install this ROM on my HTC HD2
http://forum.xda-developers.com/showthread.php?t=1316632
Click to expand...
Click to collapse
How do I install the kernel for it?
2. It tells me to partition the SD card, I really don´t get what they mean with all of those numbers?
Please send me to a tutorial where it is explained or explain it, it would really be a great great help. Thank you!
Well.
First thing - it depends on whether you want to flash the Magldr or cLK version.
I highly recommend cLK, with it you can use ClockworkMod Recovery, which will allow you to easily install pretty much everything that's in correct zip format.
So if you flash the cLK version, afterwards you just download the kernel (that's in the thread you provided) in the .zip format and save it on your sdcard. Then go into Clockworkmod Recovery (if you don't know what it is, search the net, and study) and flash zip from sdcard. That's it for the kernel.
If you want to use Magldr, I can't help with that, I'm using cLK.
About SD partitioning - there is a good guide here https://docs.google.com/document/d/1dhXJZPjZzBHcAtIE_jfEeuG988UDUaP7GfZk909nNCc/edit?hl=en&authkey=CLDJw80N&pli=1
It's a guide made especially for AmeriCan Android ROM, but the partitioning part is well written and it should work for all ROMs like that.
Just check it out, if you need anything more, let me know.
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Edit.
I need some help on this ROM. I tried to post this question in the ROM thread but it wont let me so im hoping someone can help me here.
My phone won´t boot anymore. It just gets stuck at the HTC logo with this ROM installed.
What I did was:
1. Wiped data and cleared cache
2. Installed kernel via CWM (from SD)
3. Installed ROM via CWM (from SD)
4. After succesful install (with out errors at least) i press reboot now.
And from then on its just suck at the HTC logo.
Ive left it for over an hour now just to be sure but nothing.
Can someone tell me what is wrong with it?
Thanks!
Cheesus182 said:
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Click to expand...
Click to collapse
No problem mate, if anything more, just ask - here or PM.
Edit:
P.S. if you wanna confirm that you have the new kernel installed, just go to settings, about phone and there you see the kernel info.
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Just flash Rom again in Recovery mod then flash kernel later on. It's gonna be fine, I believe.
Sent from my Desire HD using xda premium
Why should I do a recovery flash of my ROM and then flash kernel afterwards instead of just flashing the kernel right now if that is possible?
The ROM was flashed friday afternoon, so it's a pretty clean ROM.
You can flash kernel at anytime, you don't have to reflash anything.
Also, it might not be the kernel, which is responsible for your battery life.
Search for thread called something like ultimate battery guide for android and there are all things you can do to check what's wrong and make your battery life great. I did that, and am very satisfied.
DaneX said:
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Click to expand...
Click to collapse
I'm currently running the existing ROM on my SD card, and I'm not experiencing any battery drain what so ever...
I've also installed the ROM in NAND previously and didn't experience any heavy battery drain as well.
But to answer your question, no you weren't suppose to install the kernel before installing the ROM; The ROM (in SD or NAND format) already comes with a compiled kernel (It's a file called zImage).
You can install the kernel and you should just be dandy. Just remember that your battery life is heavily influenced by your cell reception and by the synching that occurs in the background.
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
g.s said:
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
Click to expand...
Click to collapse
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
DaneX said:
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
Click to expand...
Click to collapse
That means that you have a lurking app that keeps your phome from going into standby,so called partial wake.
Go into you app Spare Parts, click on battery history, choose other usage, since last boot or unplugged.
The screen on and running percentages tell you about the wake lock.
If it is nearly the same, that means you have almost no partial wakes.
If running is much higher, than screen on, that means you have some app that keeps phone awake.
Now choose partial wake usage in Spare Parts and it'll show you the apps.
And now you either uninstall them or change settings.
I'm on AmeriCan Android rom, getting 1-4mAh consumption in standby.
DaneX said:
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
Click to expand...
Click to collapse
Yep, this is with the NexusHD2 ROM. My phone during standby, only draws about 2-4mA.
55-60mA during sleep/standby is not normal. Are you in an area with bad cell reception?
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
I believe you're answering yourself. If you wiped everything and flashed different ROMs, but problem persisted - it means that your phone is most likely faulty.
k15goose said:
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
Click to expand...
Click to collapse
The question is, what other roms have you tried? I seem to get the same problems on sense 3.5 roms which is why i am not using them currently. If this is happening on a clean install of cm7 or miui as well as sense then you may genuinely have a problem.
Things to try: full wipe system/data/cache/dalvik/sdcard
reboot recovery after wipe to start clean. verify md5sum of the rom you are flashing to eliminate possibility of error. dont install any of your own apps for 1 to 2 days and then if you still have the problem then you may want to unroot and try to get a warranty exchange if at all possible. Good Luck!
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
k15goose said:
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
Click to expand...
Click to collapse
Well that's good to hear that it isn't happening on all roms. I usually fix the market problems by doing a data wipe and then force close it. Usually will start being able to download after a fc. To check the md5sum on a file download mand5 free from the market and check the file that way.
Sent from my HTC Glacier using xda premium