a coupla days ago I flashed my I9505 with latest rom foxhound 2.0. I did double wipe before flashing. After it's done, I went into system, everything was fine, but when it came to screen unlock, it had very serious lag problem. for example, when I used the pattern unlock and swiped, it took about 5-10 secs to get into the system. when I turned off the screen and tried to turn it on, the power button or the home button all had lagging problem, took about 10 secs to turn the screen on!
Is this a base band problem or kernel problem or simply just the ROM problem?
Could anybody help?
ehe12 said:
a coupla days ago I flashed my I9505 with latest rom foxhound 2.0. I did double wipe before flashing. After it's done, I went into system, everything was fine, but when it came to screen unlock, it had very serious lag problem. for example, when I used the pattern unlock and swiped, it took about 5-10 secs to get into the system. when I turned off the screen and tried to turn it on, the power button or the home button all had lagging problem, took about 10 secs to turn the screen on!
Is this a base band problem or kernel problem or simply just the ROM problem?
Could anybody help?
Click to expand...
Click to collapse
Why don't you reflash the ROM or flash another ROM and answer your own question?
kingzain900 said:
Why don't you reflash the ROM or flash another ROM and answer your own question?
Click to expand...
Click to collapse
because I don't know what's causing the problem. reflash the ROM would simply repeat the same mistake, why bother? have you seen how many are using this ROM? It means not everyone experienced what I experienced. To most of them this is really a good ROM. I don't wanna give up a good ROM, I want an answer to solve the problem so that I can enjoy it, like most of the others.
ehe12 said:
because I don't know what's causing the problem. reflash the ROM would simply repeat the same mistake, why bother? have you seen how many are using this ROM? It means not everyone experienced what I experienced. To most of them this is really a good ROM. I don't wanna give up a good ROM, I want an answer to solve the problem so that I can enjoy it, like most of the others.
Click to expand...
Click to collapse
No, reflashing might not repeat the mistake. It could have been a bad flash. It could have been a hundred different reasons. Reflashing is ALWAYS the first step anyone should take when encountering such issues. Flash a different kernel and check. The exact point you mentioned that not everyone experienced what you experienced is what indicates that it's a problem on YOUR end and not the ROMs. So if you reflash the problem might clear. If not try a different kernel or ROM. How can anyone solve the problem if you don't want to take the steps to help yourself. Take a logcat and see what happens when you lock the screen and turn it back on.
kingzain900 said:
No, reflashing might not repeat the mistake. It could have been a bad flash. It could have been a hundred different reasons. Reflashing is ALWAYS the first step anyone should take when encountering such issues. Flash a different kernel and check. The exact point you mentioned that not everyone experienced what you experienced is what indicates that it's a problem on YOUR end and not the ROMs. So if you reflash the problem might clear. If not try a different kernel or ROM. How can anyone solve the problem if you don't want to take the steps to help yourself. Take a logcat and see what happens when you lock the screen and turn it back on.
Click to expand...
Click to collapse
Very interesting point... I haven't experienced a bad flash so far. Anyway I will take your advice and try it again. hopefully it will go smoothly...
Related
When i make a call, for some reason the screen locks up and doesnt allow me to press any buttons. the only way for me to hang up the phone is to press the actual call end button. Does any one know wat the deal is with this..
Hi, It's a good idea to say if you are using a stock or cooked ROM and mention the version as it can siometimes be relevent. Also, has it ever worked or did it stop working after you installed an application? When you put the phone to your ear when in a call does the screen go blank then come back on when you take it away from your ear? Do you have any "Slide down fro more options" text on the screen? This is a Microsoft base so soft and hard resets do sometimes help
Regards.
Im using the stock rom that comes on the Tmobile USA HD2. I dont recall if it was working before I loaded any programs on to it. The screen does turn black when I put it to my face but none of the button work.
Are you using BSB? I had a similar problem. Took me hours to work out what it was.
BSB? I dont know what that is but ive decided to just flash in a custom rom later on today. My battery drains too fast and that freezing isnt helping so i might as well get something that better utilizes this hardware
am having same problem - NEED TWEAK
when I'm on the phone I can't push any buttons. today is the first time I've been using the phone, so I can't tell if it was happening before I installed anything. help, please....
I'm just using the tmobile installed rom not cooked one.
drbmbay said:
when I'm on the phone I can't push any buttons. today is the first time I've been using the phone, so I can't tell if it was happening before I installed anything. help, please....
I'm just using the tmobile installed rom not cooked one.
Click to expand...
Click to collapse
Have you tried doing a soft reset (red button inside device - HTC tech support told me taking the battery out for 10 seconds does the same thing though).
OK, if you can't tell if it was happening before you installed any additional applications / utilities.try unistalling everything you have installed. If that doesn't work try doing a hard (factory) reset, that will reset you phone to factory defaults (back up texts etc. first). It might be quicker doing a factory reset first actually. Details are in you manual (well at least in the Euriopean manual). Here is a link to details oi how to do soft and hard reset for the HD2. http://www.hardreset.eu/htc_hd2_leo_hard_reset_soft_reset_en.html.
Try it after a factory reset before you install anything else. If it still doesn't work you might have a faulty unit.
Hope this helps.
Hi all, iv got the same problem. Am using Energy.Leo.23549.Sense2.5 with MaxManila. Have tried a soft and hard reset but no luck.
It was working fine before i installed the EnergyRom, any1 have any ideas?
ROM: EnergyROM
Radio: 2.08.50.08_2
HSPL: 1.42.HSLP by DFT
Shum97 said:
Hi all, iv got the same problem. Am using Energy.Leo.23549.Sense2.5 with MaxManila. Have tried a soft and hard reset but no luck.
It was working fine before i installed the EnergyRom, any1 have any ideas?
ROM: EnergyROM
Radio: 2.08.50.08_2
HSPL: 1.42.HSLP by DFT
Click to expand...
Click to collapse
OK. Have a look at the ROM section of XDA and see if this is a known issue with that ROM. You could flash back to a stock ROM and see if it it no longer functions, showing a coincidental fone failure requiring a warranty fix.
Regards.
cMMY69 said:
OK. Have a look at the ROM section of XDA and see if this is a known issue with that ROM. You could flash back to a stock ROM and see if it it no longer functions, showing a coincidental fone failure requiring a warranty fix.
Regards.
Click to expand...
Click to collapse
Oh, you cuold try umistalli Maxmanilla on the EnergyROM too. Just a thought.
Working now
cMMY69 said:
OK. Have a look at the ROM section of XDA and see if this is a known issue with that ROM. You could flash back to a stock ROM and see if it it no longer functions, showing a coincidental fone failure requiring a warranty fix.
Regards.
Click to expand...
Click to collapse
Thanks for all your help got it sorted now
I flashed a different rom and it worked, so i flashed it again to the EnergyRom and that worked. It must have been a bug.. Glad its sorted now as it was annoying me..
did hard reset, and reinstalled everything, piece by piece. problem has not reoccurred and it's not locking up (for now). thanks.
Problem fixed
I just flashed my TMO USA HD2 to the NRG rom and its working faster and better than ever.
Hello everybody,
I came from a nrg on a leo512.
I have installed MAGLDR 1.11 in order to use Android in my NAND.
But I've some random reboot from my device and most of them are when I'm standby mode when I woke up the morning the phone asks me for the pin code...
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
That's why I'm wondering If you think my HD2 NAND is clean ?
Should I make a task29 ? I heard that tools earses all the data...
All your helps are welcome !
Regards
ditto
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?
Sammy88 said:
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
Click to expand...
Click to collapse
This is normal.
The custom ROM you were using has flashed a custom boot screen. As MAGLDR is installed AFTER this in the chain (Boot1->Magldr->Radio & NAND), it does not alter the screen. You can actually install a custom boot screen to replace this. Check Here for some.
As for the reboots, check the sticky link in my sig. There is a FAQ in there which may offer some help.
Also try post 2 of THIS
looks promising
Cptrucker said:
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?
Click to expand...
Click to collapse
Update: Ended up on 2.11.50.20 and its been 20 hours since i flashed the radio.. still no reboot... looks promising, ill update if the situation changes...
Update: 2.11.50.20 was no success, 2.15.50.04 seems to be the best radio in my case.. about 60 hours between reboots has been quite consistent
lately.. i wonder what causes this. ideas and\or sollutions are recieved with gratitude. Disabled the SIM lock so its nothing to worry about but it stil gives me headache.
Although the posts above me may be right, it seems that after I disabled over clocking on my hd2, the issue was no longer present.
As always, remember what your mommy taught you; it's proper to say "please and thank you".
The solution to this problem, can be found HERE.
Esaj2 said:
The solution to this problem, can be found HERE.
Click to expand...
Click to collapse
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.
viscious said:
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.
Click to expand...
Click to collapse
Like I said, it works for some of us. I haven't had any rebooting issues, after I turned of the automatic network selection. Some Norwegians fixed this issue, by turning of the 3G. You could try removing the sim-card and leaving the phone at sleep mode for few hours, in order to see, if your phone is still suffering from the random reboots. If so, the problem is somewhere else and I can't help you with it, because I haven't had such issues.
I resloved the issue by sending the phone back to HTC and having the mainboard replaced. Now the phone is working exactly as it should.
Sent from my HTC HD2 using XDA Premium App
I am trying to flash MIUI coming from CM 7.1.0 but everytime i reboot into recovery it will stay on recovery for a second or two then just reboot the phone back to CM. can someone tell me what the problem is here?
Have you tried to reflash the recovery yet?
Sent from my HTC Glacier using XDA App
no how do i do that?
nevermind i know how
EDIT: the reason it is doing that is because the trackpad is "stuck" and before i can scroll down to do what i want it clicks reboot phone
does anyone know how to COMPLETELY disable the trackpad? because mine is stuck so it will select things at random and makes the phone very hard to use. i have tried different roms so this has to be a hardware issue. i would rather just disable it if it is possible rather then go through with trying to get a replacement.
thanks
NickDoughty said:
does anyone know how to COMPLETELY disable the trackpad? because mine is stuck so it will select things at random and makes the phone very hard to use. i have tried different roms so this has to be a hardware issue. i would rather just disable it if it is possible rather then go through with trying to get a replacement.
thanks
Click to expand...
Click to collapse
The problem is that any software solution to disabling the trackpad would be wiped out when you started the flash of a new ROM.
So you might end up disabling it to start the flash of a new ROM, then whatever you did to disable it would get undone during the flash, and you COULD (probably unlikely, but COULD) end up with the stuck button causing a worse problem during the final stages of the ROM flashing.
I can't imagine what problem it would cause. I'd just be nervous about going through the flashing process with a button on the phone sending signals to the processor constantly.
I have first mentioned the problem here
Discussion - Stuck at Sammy Logo Issue on Official Jellybean ROMs
Mates, the problem is there, we should admit that, had it on Galactus rom twice ( reflashed the rom again after full wipes to make sure ), and had it also on the stock LSZ with its stock kernel, and also on Cassie's rom.
Nothing solves the problem apart from wiping data.
Is it the preload ? the kernel ? defective JB from Samsung ? I really don't know.
The only thing I would really like to mention is that on Stock and Cassie's rom, had the issue surprisingly occuring on odd restarts not the even ones ! the first restart gets stuck, the other goes on !
Tried all the tricks in the book (restart to recovery, reinstalling bootloader, overinstalling the same rom, wiping everything keeping data, nothing worked.
Unless data gets wiped, the problem persists.
BTW, I had the same problem on all the previous leaked versions before the official ones.
Click to expand...
Click to collapse
The method was first described here and here by RbbCHan
Then suggested to me by kopitalk
Hi mate, finally I resolved this issue by following http://forum.xda-developers.com/show...postcount=2344 and http://forum.xda-developers.com/show...postcount=2347.
Now no matter I hard reset or reboot from recovery, I got no boot stuck anymore! Cheers mate!!!
Click to expand...
Click to collapse
So here is what I have done " a step by step guide"
1-on a safe kernel, do all wipes+formats 9system,data, and preload".
2-reboot into DOWNLOAD mode.
3-connect your N7000 to PC (I use PC Odin V. 3.04).
4-start PC ODIN, untic "Automatic Reboot"
5-flash stock official LSZ rom
6-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).
7-reflash again.
8-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).
8-reflash again (3rd time)
9-restart you phone.
10-let the rom settle down, do your settings.
11-do a couple of restarts (legitimate ones, not by holding power for 7secs).
12-root your rom with the latest PhilZ LSZ kernel
13-restart into recovery, format data only "under mount and storage", then restart your phone.
Installed eybee's rom with mods, restarted automatically after mod3, and right now I am with a JB rom that does not stuck at sammy logo even when I force restart pressing the power button for 7 sec.
If you feel it takes a longer time on Sammy N7000 Logo, just repress power button again for 7 secs and it will boot up.
Hope this helps anyone who suffered bootloops as I did.
Have you taken out the battery while Note was on? That's what causing bootloops, just rebooting not necessarily.
Will try and report...:fingers-crossed::fingers-crossed:
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
on 13rd steep should I wipe data/factory reset or format data under mount and storage?
zai89 said:
Will try and report...:fingers-crossed::fingers-crossed:
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
on 13rd steep should I wipe data/factory reset or format data under mount and storage?
Click to expand...
Click to collapse
mount and storage mate..
the JB bootloader will help and are they missing in ur step?
arinsms said:
the JB bootloader will help and are they missing in ur step?
Click to expand...
Click to collapse
its in step 5 - the official rom has the JB bootloader sbi.bin
though I'm crossing fingers that this will work for everyone, but i doubt....this is completely weird from any logical point of view (especially these 3 flashes in a row...what will be flashed on 2nd or 3rd attempt that wasn't flashed before??)...but hey...if it works, ok
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
AW: N7000 Official JB Bootloop - "3x Bombardment Odin Flash" simply works!!
If I would have the bootloop problem (actually I never faced any) I would definitely give this a try. Superstition or not, doesn't matter if it solces the problem, right?
Sent from my GT-N7000 using xda premium
ThaiDai said:
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
Click to expand...
Click to collapse
This is really silly of you. We are all trying to figure out a solution even if a temporary one which might help hundreds if not thousands who are trying to use their phones promptly and who regret buying this n7000 with the famous ics brick bug and now the unstable jb roms which are OFFICIAL SAMSUMG RELEASES.
To all, there really should be a 'counter' somewhere, which explains the 'every other restart' that succeeds and does not cause the n7000 to get stuck.
Sent from my GT-N7000 using Tapatalk 2
essentially we are just ensuring the new image sticks
coz there may not be a way to verify which bootloader we actually have even after first flash
ThaiDai said:
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
Click to expand...
Click to collapse
Shame on you... We may not know what's behind doing it but it works. I hope you will get this broplem so that you will swallow your saliva back.
I'm not ashamed and I do not feel silly because of my statement.
It's only my point of view and so I still think this is ridiculous.
If any member is positive about the results my comments never will change it.
But that won't stop me from commenting when rationality moves to the far side of the moon.
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Why does anyone take there battery out while the phone is on!? Can one magically change the batteries without switching off the phone?
dio62000 said:
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Click to expand...
Click to collapse
Ues, I have just done that replacing my stock battery with my 5000mAh, and it has worked just fine.
Sent from my GT-N7000 using Tapatalk 2
Sometimes you need to take your battery out, e.g. when you have a crash and nothing responds to buttons or touch anymore. I won´t happen too often, but once is enough to get really annoyed, because this always happens when you least expect it.
dio62000 said:
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Click to expand...
Click to collapse
Yes, I have just done that replacing my stock battery with my 5000mAh and it has worked just fine.
Sent from my GT-N7000 using Tapatalk 2
Ok, so you didn´t first shut off the phone, you took out the battery while it was still on? Now that may be interesting...
dio62000 said:
Sometimes you need to take your battery out, e.g. when you have a crash and nothing responds to buttons or touch anymore. I won´t happen too often, but once is enough to get really annoyed, because this always happens when you least expect it.
Click to expand...
Click to collapse
If a system freeze occurs, you don't have to pull the battery. You can long-press the power button and voila, reboob™ takes place!
How do you guys call this... soft reboot, soft reset...?
Hello. So, I was using the default ROM for my Galaxy Y, everything in factory settings, and then it started rebooting a few weeks ago. So I tried and installed a custom ROM (BeautySense), but it didn't solve the problem.
The strangest thing is: when I put on the battery, the cell phone turns on all by itself, I don't need to press the power button for it to turn on, and when the cell phone is on, when I press the power button to lock the screen, nothing happens.
Anyone has any idea what might the problem be?
Thanks.
don't worry
vitorassuena said:
Hello. So, I was using the default ROM for my Galaxy Y, everything in factory settings, and then it started rebooting a few weeks ago. So I tried and installed a custom ROM (BeautySense), but it didn't solve the problem.
The strangest thing is: when I put on the battery, the cell phone turns on all by itself, I don't need to press the power button for it to turn on, and when the cell phone is on, when I press the power button to lock the screen, nothing happens.
Anyone has any idea what might the problem be?
Thanks.
Click to expand...
Click to collapse
it has nothing to do with the software its a hardware problem it can be one of thees two:
1.the power button is stack and that will explain why you can't lock the screen and the reboot because you are making him power off and then power on
2.the battery keeps moving form inside the case causing it to shutdown and then start by it self which happens with a lot of phone like my note 2 and y duos
report to me after you chick step 1 and step 2
press thx if i helped :fingers-crossed:
Hello. It did help, but I don't think the problem is the battery moving. As for the power button being stuck, I'd already thought of it, but I don't know how to fix it. Apparently it is not stuck, but maybe it is stuck on the inside. In that case, how can I be sure?
Thanks.
It's a 90% hardware problem scenario.... But why don't you try changing to another kernel? (any stable kernels like hells fusion, jarvis, savie etc)
If it still reboots then u will be damn sure it's the power button problem.
vitorassuena said:
Hello. It did help, but I don't think the problem is the battery moving. As for the power button being stuck, I'd already thought of it, but I don't know how to fix it. Apparently it is not stuck, but maybe it is stuck on the inside. In that case, how can I be sure?
Thanks.
Click to expand...
Click to collapse
you can try flashing a kernel because when my phone fell in the bathroom i opened it my self and i lost my volume Button so i prefer that you keep the opening of phone as the last Solution :fingers-crossed:
Try to flashing with new kernel if it didn't work i think it's hardware problem
Solution
Many replies stated just to flash kernel.
Actually, you have to flash a kernel and then flash ROM.
If you do the reverse, you will stuck in bootloop.
The instability of the kernel is the cause.
Also do not install too many tweaks, which also causes some stability issues.
Over Clocking in some kernels also cause this restarting problem.
Solution: Flash Kernel and then flash the ROM
If it doesn't work, it is surely the hardware problem.
Press thanks button if I have helped you!
the_pirate_predator said:
Many replies stated just to flash kernel.
Actually, you have to flash a kernel and then flash ROM.
If you do the reverse, you will stuck in bootloop.
The instability of the kernel is the cause.
Also do not install too many tweaks, which also causes some stability issues.
Over Clocking in some kernels also cause this restarting problem.
Solution: Flash Kernel and then flash the ROM
If it doesn't work, it is surely the hardware problem.
Press thanks button if I have helped you!
Click to expand...
Click to collapse
this is not true
for stock based roms flash rom then flash kernel - this is because kernel has things like wifi driver that needs to be flashed after the rom however it doesnt matter if you do it the other way round - you can always flash the wifi driver seperately
for cm based roms you need to flash kernel first in order to format your system to ext4 in order to install the rom if not already on ex4 system partition
Thanks
marcussmith2626 said:
this is not true
for stock based roms flash rom then flash kernel - this is because kernel has things like wifi driver that needs to be flashed after the rom however it doesnt matter if you do it the other way round - you can always flash the wifi driver seperately
for cm based roms you need to flash kernel first in order to format your system to ext4 in order to install the rom if not already on ex4 system partition
Click to expand...
Click to collapse
Thanks for correcting my mistakes and guiding me!!
Anyone solved this problem? I am experiencing it right now, what to do .?
Sent from my GT-S5360 using Tapatalk 2