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.
Related
tried to install custom rom, didn't work out. tried to do a restore the phone gets to a point where it stops and says "lost+found" and won't go any further. any suggestions?
Thanks
Also when i try to reboot in recovery i get this "E:can't open/cache/recovery/log" and stops right there. Any ideas??
Odin is your friend look it up!!
Sent from my SPH-D700 using XDA App
Have odin and still can't get past the places on my previous post. Every time i try to reboot i get the "clockworkMod Recovery v2.5.1.0"
"E:can't open /cache/recovery/log"
just like that half way down the screen. won't go any further. need some serious help.
you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back
Skrewup5 said:
you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back
Click to expand...
Click to collapse
At this point the only way i can power it down is to remove the battery and even when i hold 1 and power back up it goes into clockwork recovery mode instead of download mode.
thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom
Skrewup5 said:
thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom
Click to expand...
Click to collapse
A friend at work, who has an EVO wanted to work on my phone while I was out of the office on business. He was able to finally get it to enter download mode, flashed odin and froyo DK28 and got me back up. Just a temporary glich that took several tries for some reason. Anyway I'm back on 2.2.1 and looking forward to rooting again but probably going to download a different rom. Thanks for help and advise. also good to have phone savy friends at work. Thanks Ashley.
Dana
Im glad it was all resolved haha. try the new bonsai4all 2.0. its very easy to install
Last night I installed Gingerbread 2.3.1 on my HTC HD2.. Followed the directions exactly and was able to boot Android and customize and had no problems. Tonight, suddenly my buttons at the bottom (home button, start menu, back, etc) started flashing -- side note: if anyone knows why this happens and how that can be stopped please let me know!! --, I figured I would just restart my phone. Well, when I restarted, suddenly I had no service when I booted Android.
I have rebooted my phone in the different methods (reboot, recovery, and bootloader), tried powering it off and then turning it back on, tried putting it on airplane mode (dunno why) and then back off, took out the battery and sim and waited for 20 min and then put it back in... Nothing has had any luck.
When I boot Windows Mobile, I have a phone signal, but for some reason when I'm booting Android, it isn't there.
Anyone else have a similar problem or can suggest how to fix this? I really want to be able to continue using Android but that's not going to happen if it continues to have this problem...
Flash official windows again, then try NAND Gingerbread 2.3.4 Its great ROM and all works.
sultans said:
Last night I installed Gingerbread 2.3.1 on my HTC HD2.. Followed the directions exactly and was able to boot Android and customize and had no problems. Tonight, suddenly my buttons at the bottom (home button, start menu, back, etc) started flashing -- side note: if anyone knows why this happens and how that can be stopped please let me know!! --, I figured I would just restart my phone. Well, when I restarted, suddenly I had no service when I booted Android.
I have rebooted my phone in the different methods (reboot, recovery, and bootloader), tried powering it off and then turning it back on, tried putting it on airplane mode (dunno why) and then back off, took out the battery and sim and waited for 20 min and then put it back in... Nothing has had any luck.
When I boot Windows Mobile, I have a phone signal, but for some reason when I'm booting Android, it isn't there.
Anyone else have a similar problem or can suggest how to fix this? I really want to be able to continue using Android but that's not going to happen if it continues to have this problem...
Click to expand...
Click to collapse
try a different rom, the flashing buttons was common on early builds of gingerbread
i take it you are using an sd version rather than nand ?
Try switching to 2G only and see if your signal is back.
Richy99 said:
try a different rom, the flashing buttons was common on early builds of gingerbread
i take it you are using an sd version rather than nand ?
Click to expand...
Click to collapse
Yes, I'm using SD version... To be honest, I didn't really know the difference, but from what I was told NAND basically erases Windows, right? If that's correct, I was afraid of the installation not going right and being stuck without a working phone.
michie said:
Try switching to 2G only and see if your signal is back.
Click to expand...
Click to collapse
I tried going to my settings to switch to 2G, but at first it was greyed out, so I couldn't even select it. Then I clicked Access Point Networks and went back and suddenly it was available to be clicked. I clicked it and went to another screen and for some reason decided to go back to check it and it had been unclicked and greyed out again....
Seems it's a problem related to your rom and not a hardware problem because it works on wm.
Im not familiar with SD roms, maybe you should try a different SD rom or a NAND rom and see if the problem is solved.
Hope u get it sorted !
Since it seems I just need to try a different rom, can anyone suggest a link? I think I want to try SD again just because if I'm having these problems I don't want to completely wipe Windows and not have something to resort back to if I run into something again..
bluur said:
Flash official windows again, then try NAND Gingerbread 2.3.4 Its great ROM and all works.
Click to expand...
Click to collapse
Honestly I don't want to NAND it because I don't want to completely wipe Windows in case I have a problem again... (this is all assuming I understand NAND correctly)... Right now I have a problem so I was able to go back to Windows Mobile. Do you have any suggestions for another SD rom?
Not quite true. You can always go back to Winmo from Android Nand if you are unhappy with it. I used to think the same way but since taking the plunge I've always found it easy to reinstall Winmo in order to use my tomtom navigator
ROM wise there are various fantastic offerings with Android Nand. Some are even spotting the new sense 3. You can try either CoreDroid or LeoRC Mix.
For now head over to the Nand section and read the stickies at the top. There are ample and easy guides on how to prepare your HD2 for a Nand Rom and how you can return to Winmo if you don't like it. If you follow the instructions properly, trust me nothing will go wrong.
Sent from my Desire using XDA App
I'll give it a try, thanks!
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
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...
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