Related
Hello,
i have problems with random reboots since the Android NAND Version.
My HD2 just reboots automatically after a few hours or also sometimes after a few minutes (it doesnt matter which android rom I installed..) - I also updated on MAGLDR 1.12 but the bug is still here.
Does anybody know, how to fix this bug?
Thanks!
same here i doo task 29 no problem .....
always use task 29 and no problem
do task 29 no more problems trust mi its easy and safe i do thet..radio is same but at the and put in boot loader and install rom what you wish
BUT can be also radio what rom and what radio you have
Well, what do you mean with task 29?
I'm using MDJ's Cyanogenmod 2.6 NAND with the newest radio (2....whatever lol)
hd21337 said:
Well, what do you mean with task 29?
I'm using MDJ's Cyanogenmod 2.6 NAND with the newest radio (2....whatever lol)
Click to expand...
Click to collapse
Use this tool and select the Task29 only. Task29 formats the NAND memory area. After completing the Task29 the phone will reboot, as it does hold the volume down button so you boot back into bootloader mode (if you miss this the phone will hang as there is no longer any rom to boot into - it's been formatted ) If this happens just remove the battery and boot into bootloader mode yourself. You will then need to reinstall magldr and reflash your Android rom.
Are you using setcpu to overclock? Going higher than what your device can stand can cause reboots. Also make sure you are not low on memory.
Sent from my HTC HD2 using XDA App
Thank you for your tipps guys.
I just used Task 29, installed MAGLDR 1.12 and installed MDJ's Cyanogenmod 2.6, thought that it worked but he rebootet two times in the last 3 hours again.
So is there anything else i can try? I mean, a friend of mine has the same bug, but with MAGLDR 1.11 and an older version of Cyanogenmod... :/
Oh and im not overclocking my phone, just use it with the default settings etc.
same here.
Random reboots ever since nand.
Yeah, it just sucks.
Would be interesting to know, why it works on other devices without problems... i dunno but maybe its the radio?
+1
i also have the same problem.. the frequency of the reboots vary from radio to radio, i have flashed ALL the available radios and ended up on 2.14.50.04, this giving me around 40-60 hours between the reboots.. my solution to the annoyance was to turn of PIN lock thus eliminating the need to enter PIN code when the phone resets.
no solution to the problem yet..
problem started before NAND in my case.
i have noticed that the reboots happen more frequent at night when the phone is charging (checking this by looking at the uptime).
solutions to this problem would be awesome!
MAGLDR 1.13
Radio 2.14.50.04
MDJ cyanogen 2.6
EU-HD2 (norway)
Didn't read this thread too carefully but I saw someone mentioning overclocking. It seems a very likely cause to me too, don't forget some (kernel) devs overclock by default. Download SetCPU (its free on xda) and limit your clockspeed to something like 900 MHz and check if that fixes it.
StephanV said:
Didn't read this thread too carefully but I saw someone mentioning overclocking. It seems a very likely cause to me too, don't forget some (kernel) devs overclock by default. Download SetCPU (its free on xda) and limit your clockspeed to something like 900 MHz and check if that fixes it.
Click to expand...
Click to collapse
i dont know if MDJ overclocks, but when i downloaded SetCPU and clocked to 1267mhz and the speed difference is just astonishing !!! 7 hours uptime and counting.. i will update on next random reboot.
Overclocking is exactly what you don't want to do...
StephanV said:
Overclocking is exactly what you don't want to do...
Click to expand...
Click to collapse
that might be, ill underclock next time the phone reboots and see if it makes any difference..
my hd2 = tried task29, tried ALL the nand roms, NEVER overcloced my phone...tried different radios etc.....still reboot reboot reboot.
matt
try this: Change your mobile network mode from WCDMA/GSM auto --> GSM. If this helps i think it's not software problem. this fault is also happens stock wm
@heitaas:
i tried your "workaround" and i'm happy to say that it helped. no reboots since 2 days for now (and i had a lot of them)!
maybe some of the dev's out there could use this information to fix this problem!
edit:
sorry.... bad news.... i had a f...... reboot again
Well, I tried it to underclock my HD2 with SetCPU but i didnt helped - any new ideas?
Maybe an another Radio or whatever?
hd21337 said:
Well, I tried it to underclock my HD2 with SetCPU but i didnt helped - any new ideas?
Click to expand...
Click to collapse
You could try switching off the automatic network selection. I had these same rebooting issues, but when I switched to manual network selection, I haven't had any more random reboots. It has worked for some of us.
i've flashed CM7, and i reboot it, .. after 15min, the screen is the same, what should i do now?is it normal? i'm getting panic
What screen, if it's HBOOT screen, maybe something wrong in the boot process.
If it's CM7 splash, it was being installed.
use adb and type in "adb shell" and then type "logcat -C", if the log is running, the phone is booting
Funnnny said:
What screen, if it's HBOOT screen, maybe something wrong in the boot process.
If it's CM7 splash, it was being installed.
use adb and type in "adb shell" and then type "logcat -C", if the log is running, the phone is booting
Click to expand...
Click to collapse
i reflashed it, and my WF rebooted again and again, is it normal?
did you try a full wipe (wipe data/factory reset) before reflash ?
as I say, try to go into shell and use logcat, it'll provide you the log process and maybe you will know if there's something wrong
Funnnny said:
did you try a full wipe (wipe data/factory reset) before reflash ?
as I say, try to go into shell and use logcat, it'll provide you the log process and maybe you will know if there's something wrong
Click to expand...
Click to collapse
yes, i wiped my WF before flashing.. sorry i'm just a newbie here, i dont know what is logcat..
my phone freezes now on the cyanogemod screen.. what should i do next? should i wait?
I've been stuck at bootanimation often too... solution: flash hcdr kernel 4.1 before and after installing cm7, reboot system now and that should do it!
Sent from my HTC Wildfire using XDA App
lol8888 said:
I've been stuck at bootanimation often too... solution: flash hcdr kernel 4.1 before and after installing cm7, reboot system now and that should do it!
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
can you give me the link pleaassee?
what should i do?flash hdcr before cm7 right?
should i remove my battery now?
4.2 kernel is fine, but you can flash 4.1 if you want:
http://forum.xda-developers.com/showthread.php?t=798471
flash CM7 first, and then flash 4.1 kernel.
Just wait, the first boot when you flash ROM can very long (around 20min, usablly 5,10min for me)
Funnnny said:
4.2 kernel is fine, but you can flash 4.1 if you want:
http://forum.xda-developers.com/showthread.php?t=798471
flash CM7 first, and then flash 4.1 kernel.
Just wait, the first boot when you flash ROM can very long (around 20min, usablly 5,10min for me)
Click to expand...
Click to collapse
hopes it work.. i'm getting panic here..
am i allowed to connect my charger in case my battery gets low?
the bootanimation shows now..
ijestan said:
hopes it work.. i'm getting panic here..
am i allowed to connect my charger in case my battery gets low?
the bootanimation shows now..
Click to expand...
Click to collapse
my phone is ok now!!! thanks a lot!!!
can you give me some instruction of how can i make battery last? actually this is the reason wwhy i flashed this rom
okay, first try to install setCPU, free for xda member, search in the forum
set the min around 160 or >200Mhz and max ~600 or anything you want.
set 3 profile
Screen off: 160-~300
Baterry<20%: 160-~400 or 500
Temp >45: 160-~400
it'll help because you optimize the CPU use.
turn-off some animation, don't use live wallpaper (CM7 use it by default, so turn it off)
Funnnny said:
okay, first try to install setCPU, free for xda member, search in the forum
set the min around 160 or >200Mhz and max ~600 or anything you want.
set 3 profile
Screen off: 160-~300
Baterry<20%: 160-~400 or 500
Temp >45: 160-~400
it'll help because you optimize the CPU use.
turn-off some animation, don't use live wallpaper (CM7 use it by default, so turn it off)
Click to expand...
Click to collapse
thanks!!! CM7 is soooo awesooommee!!!
how about openvpn?
ijestan said:
thanks!!! CM7 is soooo awesooommee!!!
how about openvpn?
Click to expand...
Click to collapse
do i need to flash the gapps?
ijestan said:
do i need to flash the gapps?
Click to expand...
Click to collapse
If you want Google Apps like Market, GMail etc. Then yes.
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...
Here is whats happening to me..I rooted my Galaxy tab 10.1 soon as i got it…no problem…I then tried to set it up to recognize ad-hoc..using the tutorial from another site…when i rebooted ..the Samsung log appeared followed by multi colored horizontal lines all accross the screen..
I restored it back to factory settings and was good to go exept now I have a yellow exclamation point at boot up. So Then I rerooted no problem….I was able to set up for ad-hoc using a tutorial from this site…then i tried to overclock and install Starburst and back to Horizontal lines when I rebooted..
Luckily this time I backed up the rom..so I reverted to that and was ok…This is my 1st andriod , please help ..I want to over clock and put in a new rom but im scared.
I really hope this is something simple that Im doin wrong and can resolve.
sounds like the wrong kernel was loaded up bro. Do this install task650s rom, and install pershoots OC kernel. Do you have a wifi tab? if so, then you need the TW UX version from pershoot. After you install pershoots kernel, then DL setcpu from XDA ( its free here ) and then auto detect , run the slider to 14 and tick the box for set on boot. Reboot and you're golden.
Ok sounds Awesome...yes its the wifi only 10.1...im totally new to android..do i do it in that exact order rom then kernal and so on?
Ok download these
1. Tasks rom : http://www.multiupload.com/F6K6JNJ46V
2. Pershoots kernel ( correct on already ) : http://droidbasement.com/galaxy/ker...-cm_2636.4_ux-oc-xtra-vfpv3-d16_fp-091011.zip
3. Setcpu and set it up as I said above : http://forum.xda-developers.com/attachment.php?attachmentid=648354&d=1310073004
You have to be rooted, and Im sure you still are. Its late here and Im super tired, so forgive me haha
Your THE MAN thank you bro..get some sleep..I swear this is last question..I dont reboot untill the end? or after each thing i install? I swear thats it lol.
ITs cool bro, Im not the typical forum browser. I'll try and help even the simplest question that has been asked 1000 times. Anyway, What I would do is get into recovery ( btw a good app for this is called Quickboot, its free and puts the tab right into recovery with one click )
What I was saying haha, is get into recovery. Do a system wipe/factory reset. Once that is done flash Tasks, then pershoots kernel. Once that is done back out and reboot. Its going to take around 10 mins or so. But it may only take a few. Depends, but let it sit until its done. Once its done. Let the kernel set in and works its way thru the code. Then reboots for ****s. Once its rebooted load the setcpu program. When that comes up accept the superuser popup, adjust the slider bar to 1400mhz and then slick the box that says set on boot. Then restart again, and well thats it bro.
WOW!!! You sir are a Scholar.....All worked perfect....Happy guy here, thanks again..where do I send the xmas card too lol?
God you got it figured out bro.
Sent from my Galaxy Tab!
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?