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
Related
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.
Hello,
I have tried searching but haven't been able to find a similar issue for any android devices (amazing right?). My nexus 7 will not respond to any soft reboot. From power menus to terminal to factory reset (yes including from ROM recovery and the like). It will reboot from the 10second press, but as we know that is pretty ineffective considering the nexus 7 has that bug where you can't access recovery from boot loader. I have tried connecting to a PC to force recovery, Nada.
So now I am out of idea. Also, for the next 2 weeks I don't have a PC, only a gnex and nexus 7...
Any help appreciated.
update your bootloader and recovery, that bug has been fixed. what rom are you running, every single reboot/power off option works here.
I can't update it without being able to reboot. And I know its not a common issue.. hense why I ask for help... I am not reporting a issue, I am asking for ideas... thanks for the tremendous comprehension though
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
MatAuc12 said:
I can't update it without being able to reboot.
Click to expand...
Click to collapse
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
MatAuc12 said:
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
Click to expand...
Click to collapse
let the battery die and power itself off, then charge it. flash another kernel for sure.
simms22 said:
let the battery die and power itself off, then charge it. flash another kernel for sure.
Click to expand...
Click to collapse
I did let it die for cold boot and again, understanding my problem means since I can't initiate a reboot or get into recovery I cannot flash anything
BillGoss said:
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
Click to expand...
Click to collapse
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
MatAuc12 said:
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
Click to expand...
Click to collapse
boot pressing volume down while pressing the power button into the bootloader, flash a different kernel via fastboot. you can flash franco kernel in fastboot, since it is in boot.img form, or extract the stock boot.img from a stock rom and fastboot flash that. ive had similar behaviors with test kernels, faux forgot something in the kernel. then download and flash the newest bootloadee to fix your recovery from bootloader bug.
Try simms22 approach first.But if you can't get into fastboot and you can boot into the ROM- then you could try rewriting the boot.img. Get the boot.img/kernel you want and use the dd command to write it.
Warning: you can do serious damage with the dd command.
If you need some help with this, let me know. But I accept no responsibility if things go terribly wrong.
Sent from my Nexus 7
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...?
So. I've finally done it - gone way beyond my comprehension. I'm not exactly new to flashing roms/kernels, but I'm certainly still at the noob level.
Here's what I did: I have Pac Man rom (22.2.0-rc1). I've tried different kernels but have a very poor signal at home and it's very hard to connect to wifi at home even though other devices connect flawlessly. Even the latest Franco (both stable and nightly) have a lot of problems with the wifi. So, I just made a nandroid in TWRP, flashed cwm-radio-m9615a-cefwmazm-2.0.1700.54.zip, then flashed Faux123+Shaky156V0.4.zip, then wiped cache/delvik then rebooted system. (I did all of this by copying the files into the ready-to-flash/root files and simply flashed them via TWRP.
Here's the problem: I'm stuck on PACs boot screen. The little pac man game-type animation runs, then it goes to the PAC is loading screen and stays there. And I can't get back to TWRP. If I hold the power/volume up& down keys, it simply reboots right to the rom and goes back to the bootloop.
I've tried searching XDA for a solution but can't find one. Any advice? Thanks!
david251 said:
So. I've finally done it - gone way beyond my comprehension. I'm not exactly new to flashing roms/kernels, but I'm certainly still at the noob level.
Here's what I did: I have Pac Man rom (22.2.0-rc1). I've tried different kernels but have a very poor signal at home and it's very hard to connect to wifi at home even though other devices connect flawlessly. Even the latest Franco (both stable and nightly) have a lot of problems with the wifi. So, I just made a nandroid in TWRP, flashed cwm-radio-m9615a-cefwmazm-2.0.1700.54.zip, then flashed Faux123+Shaky156V0.4.zip, then wiped cache/delvik then rebooted system. (I did all of this by copying the files into the ready-to-flash/root files and simply flashed them via TWRP.
Here's the problem: I'm stuck on PACs boot screen. The little pac man game-type animation runs, then it goes to the PAC is loading screen and stays there. And I can't get back to TWRP. If I hold the power/volume up& down keys, it simply reboots right to the rom and goes back to the bootloop.
I've tried searching XDA for a solution but can't find one. Any advice? Thanks!
Click to expand...
Click to collapse
Its volume down + power button... not power + vol up/down. Do that then use the volume up/down buttons to go to RECOVERY and then boot into recovery.
I don't see why flashing those two would cause it to bootloop.... maybe bad MD5 hash?
zephiK said:
Its volume down + power button... not power + vol up/down.
Click to expand...
Click to collapse
Thanks - got it. I definitely appreciate your time and help.
david251 said:
Thanks - got it. I definitely appreciate your time and help.
Click to expand...
Click to collapse
Welcome, hit the thanks button .... just reflash the ROM without wiping and then reboot. See if it loads up, it should boot up without having it boot loop.
zephiK said:
Its volume down + power button... not power + vol up/down. Do that then use the volume up/down buttons to go to RECOVERY and then boot into recovery.
I don't see why flashing those two would cause it to bootloop.... maybe bad MD5 hash?
Click to expand...
Click to collapse
By the way, your question of possibly a bad MD5 hash.... lol... I have no idea. I tend to think it's more due to me doing things to my phone that I really have no business doing since I have only the vaguest clue of what I'm doing at any given time.
david251 said:
By the way, your question of possibly a bad MD5 hash.... lol... I have no idea. I tend to think it's more due to me doing things to my phone that I really have no business doing since I have only the vaguest clue of what I'm doing at any given time.
Click to expand...
Click to collapse
Basically, if you're going to be flashing things. Especially when it comes to a flashing a bootloader or radio (baseband) you should verify its MD5 hash.
MD5 hash just verifies that your download was indeed a good download and nothing screwed up. Flashing a bootloader/baseband with the wrong MD5 hash will lead to problems and ultimately possibly to a brick (not to scare you or anything).
Nah what you did was fine, I don't know why would boot loop. But stuff happens, at least you didn't say "omg i bricked my phone??!" like some other people hehe.
For example, http://forum.xda-developers.com/showthread.php?t=2087227 If we look at 0.54 baseband on the website,
MD5 Sum: 0d556693de6c6af086d8d9a74a5dc164
It has that.... you would then use a program such as http://www.softpedia.com/get/System/File-Management/HashTab.shtml
Which when you download the file, right click -> properties -> file hashes -> you can copy paste the md5 hash and it'll have a check (same md5 hash as the one you copy pasted) or X which is NOT the same md5 hash. If its a green check mark... go ahead and flash away, else... redownload it until you get the right md5 hash (use another browser to download if it fails the second time again).
Better safe than sorry, right? especially when flashing bootloader/basebands. Both are very fragile components of the phone. As far as kernels, roms, etc... doesn't mean as much.
In case it helps anyone, I'll say that it has something to do with the kernel I used. Here's why I say that:
After getting back into TWRP, I restored the nandroid I'd made and everything booted very well, back to just the way it was. Since I'm not one to give up so easily, I went back to TWRP and flashed the radio .54, wiped cache/delvik and rebooted the system - the idea here was to try one at a time and see what happened. Phone rebooted normally and everything as before (meaning it showed (in About Phone) the baseband version 54 but still wouldn't connect to wifi without trouble. So - everything was normal. (Just for the record, the only ROM/Kernel I've found that had no problems at all (in terms of my own Nexus 4) was Paranoid Android v.3.56 from 22MAY2013. This one connected pretty well consistently. But then an update to that rom came out and after flashing, it booted fine but I kept getting an error of "Android Process Acore has stopped" and I couldn't do anything at all - which is what led me to the PAC rom.)
Anyway, so after flashing the radio .54 the phone booted and worked normally. Then I went back into TWRP and flashed the Faux123+Shaky kernel, wiped cache/delvik and rebooted system. Now it went back into the same bootloop and stayed there. So... maybe it's just that this kernel isn't compatible with my PAC rom??
So now I've again restored the nandroid. It's a bummer because I love the PAC rom but I have to be able to connect to wifi. And from what I've read, I'm surprised the Franco kernel doesn't help that. It will eventually connect but often takes 30 to 60 minutes to connect and will then often disconnect after the phone sleeps for 10 minutes or so.
From what I have experienced , faux kernel can not be directly flashed over Franco kernel due to something wrong I didn't know with Franco kernel, I did it and went into boot loop then searched and found that you have to flash reset kernel from faux first over Franco then flash faux kernel,
Official notice from faux kernel thread
NOTICE: If you come from Franco Kernel, YOU MUST FLASH RESET KERNEL FIRST otherwise it will result in a boot loop due to NON-STOCK ramdisk used in Franco Kernel!
Hope that helps
Sent from my Nexus 4 using Tapatalk 2
The reset kernel has helped me a couple of times when had bootloops. The 2 I've had wouldn't ever get to the boot animation though, just the Google logo with padlock, then reboot and same again.
This is the reset kernel I've used. I don't know where I got it or who to give credit to, but it works well
back.to.stock_kernel_and_components.zip here http://www.multiupload.nl/BHFJSGU3QD
MD5: f801fc7702e29d85447e9b6fdc880549
SHA-1: a6e60cf80ba29da4eff4c2048934e8627fb682ac
Pretty sure that Franco changed the ramdisk back to the stock ramdisk A LONG time ago and Faux forgot to change the OP post.
Wouldn't hurt to try the 'reset kernel' though but I don't think that is the case.
Source:
r85:
* Add a bunch of patches from CAF to test if the msm_hsic wakelock can get lower.
* Fix the boot.img packing derp that could bootloop the device after flashing another custom kernel on top of franco.Kernel.
* Make the thermal driver poll twice as fast when the device hits the hot threshold as by showp1984 suggestion.
* Disable sched_autogroup because of one Google's engineer answer to my question: https://android-review.googlesource.com/#/c/51323/
* Add a sampling_timer option for the hotplug driver: /sys/module/auto_hotplug/parameters/sampling_timer - it controls how often the hotplug decision is called. The value is in jiffies. For reference 1 second is 100.
* Merge a patch from Linux Kernel that adds a new hashtable (http://en.wikipedia.org/wiki/Hash_table) implementation to be used in the block layer (block layer is the layer that controls the IO on the several block nodes).
Source: http://minooch.com/franciscofranco/Nexus4/4.2.2/appfiles/nightly-changelog
Click to expand...
Click to collapse
(in bold)
zephiK said:
Pretty sure that Franco changed the ramdisk back to the stock ramdisk A LONG time ago and Faux forgot to change the OP post.
Wouldn't hurt to try the 'reset kernel' though but I don't think that is the case.
Source:
(in bold)
Click to expand...
Click to collapse
Wrong Franco still uses a modified ramdisk. What he's talking about is a drep in the packaging of the boot.IMG that caused bootloops
Sent from my Nexus 4
spaceman860 said:
Wrong Franco still uses a modified ramdisk. What he's talking about is a drep in the packaging of the boot.IMG that caused bootloops
Sent from my Nexus 4
Click to expand...
Click to collapse
K no need to be rude about it with saying "wrong" this is XDA a place to learn from each other. Sorry I don't follow every single word that is being said in the Franco thread or any other related kernel thread.
You need to work on your articulation to make yourself not come off as an aggressive person for absolutely no reason.
zephiK said:
K no need to be rude about it with saying "wrong" this is XDA a place to learn from each other. Sorry I don't follow every single word that is being said in the Franco thread or any other related kernel thread.
You need to work on your articulation to make yourself not come off as an aggressive person for absolutely no reason.
Click to expand...
Click to collapse
I wasn't being rude :beer::thumbup:
Sent from my Nexus 4
I appreciate all the input from everyone. As a final update to this thread, what I finally did is flashed the Xenon HD rom and GAPPS with photosphere (as recommended by the developer). Wifi and signal issues are completely resolved and it seems to be an awesome rom for me. I'm stoked and think I'll wait at least a few days before I go in and screw up anything else.
david251 said:
I appreciate all the input from everyone. As a final update to this thread, what I finally did is flashed the Xenon HD rom and GAPPS with photosphere (as recommended by the developer). Wifi and signal issues are completely resolved and it seems to be an awesome rom for me. I'm stoked and think I'll wait at least a few days before I go in and screw up anything else.
Click to expand...
Click to collapse
PSST, if you're scared you might screw up, make a NANDROID when your phone is still fine. If you get into a bootloop, just restore the NANDROID. It does take quite a lot of space though, so keep that in mind.
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...