Related
Hi!
Im having trouble getting into CWM. I have been running MIUI on my Galaxy S i9000 for over a month now without any problems with CWM. Im running MIUI RC8vC right now and decided to update it to the latest release MGv2, but here comes the problem. I can't get into the Clockwork Mod Recovery mode.
What i have been trying is the standard 3-button-combination, where i end up on the splash screen for the Galaxy S i9000 and than nothing more happens (left it on for 10 minutes just to be sure). So i then tried rebooting into CWM using the ROM Manager from Market, ending up with the same result.
My question is, what is the most simple way of fixing this annoying problem?
Thanks!
how long are you holding the 3 button combo for ? you only need to do it until the GT-I9000 screen comes on, then let go.
anyway if you cant get it working its probably kernel related, did you flash they CM7 initial kernel before you came to MIUI,
do this again in ODIN and start the process again
Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?
RobertRoos_ said:
Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?
Click to expand...
Click to collapse
yes, that should work
weird problem and i have never heard of it before lol..
Thanks for the quick answer!
I did what you said and it worked fine, im now running the latest release of MIUI for Galaxy S.
But now i can't get into CWM again! This is really strange, and annoying, if i have to go back to the initial kernel all the time for upgrading MIUI, i do wonder what could be causing this problem. If it was the kernel that comes with the later releases av MIUI i suppose others would have similar problems, but i can't find anyone else having these kinds of problems.
Seems like im beeing followed by bad luck today.
so download mode IS working ??? Hmmm.... not a 3 button combo issue then..
How long have you been on MIUI, did you come from a gingerbread ROM ?
can i just ask how are you doing the 3 button combo..... (i feel stupid asking this, but this problem is so strange)
Yes, works like a charm- so as I said im on the MGv2 right now but with the same problem as before lol.
I've been on MIUI for about a month now, perhaps a little longer. No i came from Darkys v9.5, than did the standard update procedure going to a stock froyo rom and so on as described in the main MIUI thread.
Well im doing it the same way both when on the kernel for CM7 where i can get in, and when on the kernel for MGv2. Menu+Volume Up+POWER, Releasing Power directly when the "Galaxy S i9000 Samsung" splash screen turns up. So im 100% im doing the combination right. I can't get into CWM using the ROM Manager either that donät require the 3-button combination, so there must be something else.
Thanks for trying to help me with this!
no need for thanks we havent got it sorted yet lol
make a post in the MIUI thread in development, there is a lot of cleverer people in there and im hoping that they can shed some light on this bizzare situation
I wanted to do that in the first place, however i must reach 10 posts or so before i can post in there. You could not post my question in there for me you think? So i don't hace to just spam this forum with another 5 posts.
thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI
hey mate had a reply, dont know if you have been checking but here is what was said
I had a similar problem when first installing CM7, I believe it is a problem with having come from the original JVK. The solution was to flash an older Froyo version (JS3 in my case) and repartitioning with 512-pit, then installing MIUI again from scratch. Hope that helps.
Click to expand...
Click to collapse
hope this helps
Ill reply when more solutions come up
azzledazzle said:
thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI
Click to expand...
Click to collapse
azzledazzle said:
hey mate had a reply, dont know if you have been checking but here is what was said
hope this helps
Ill reply when more solutions come up
Click to expand...
Click to collapse
Thanks again azzledazzle!
Yes a did a complete wipe since I as well thought that might could solve the problem, however it did not.
Okay I will have a go at it tomorrow- I guess i need to find a ROM with a bootloader and all though when downgrading from 2.3.4?
yes, im not sure which firmware contains the bootloader or if you have to check 'update bootloader' in odin, i have never had to do this, so you will have to search.
but let me know how you get on and we can go from there.
Im off to bed now its late, if you get it fixed PM me, if not il be back to check on the thread tomo
Problem is now solved!
I was thinking that MIUI gets updates all the time, and switches between kernels quite often as well, so I decided to wait for the next update with a kernel-switch.
MGv4 was released today and had the kernel-switch I had been waiting for, so I just flashed over the initial kernel for CM7 again using ODIN. Than went into CWM and updated MIUI to MGv4.
Than with my fingers crossed i tried entering CWM again and it worked like a charm.
So I did not have to go back to FroYo and all that again, just had to wait for the next update.
Thanks for your help!
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
Hi, I have rooted 2.3.6 (I9000XXJVT). There is random problem with dialer. It's crashing when I start dialing number and just back to home screen without warning. Any help? PS. The same was with older version of android. THANKS!
i have this issue to
does anybody know the solution if not i think i might have to reflash via odin
Have you tested to see if the proximity or light sensors are faulty as i had similar crash problems force closes and just returning to the home screen and it is my proximity sensor not working and when you try to make the call and the phone dont do what the cpu is saying that's not right it just gives up
sent by looney on his galaxy gti9000 via xda app u no u gotta love the droid
sumsy2011 said:
does anybody know the solution if not i think i might have to reflash via odin
Click to expand...
Click to collapse
reflash giving nothing... Still the same...
Try this:http://www.mediafire.com/?h9n6e4qwagaln3f
Copy two files in system /app and then reboot.
your rom ust be rooted and deoxeded
First of all, @OP and followers:
I think that you have force close error on com.android.phone, right?
Second, for the helpful guy: the solution depends: there are two version of fix, for odexed and deodexed phone, both available After magic button: SEARCH use
no FC's just exits i tried wipe data thrum titanium backup but it works for a short time. it is really annoying and it happened to me since jvq i think and now i am on jw1
gigeaky said:
no FC's just exits i tried wipe data thrum titanium backup but it works for a short time. it is really annoying and it happened to me since jvq i think and now i am on jw1
Click to expand...
Click to collapse
same here...
and this stops you from trying the solution provided above? OK guys, so please wait. I hope that within 12 months someone will look for it specifically, as you do not want to replace phone.apk.
I've just installed I9000XXJVU|2.3.6|OXA| and problem seems to be solved: http://forum.xda-developers.com/showthread.php?t=1431596
i have same problem so looking for a different rom.
was on jvu 2.3.6
i had same problem with jetpack v9 flashed darky 10.4.2 running smooth also has a phone fix in darky ota app dialer working great no probs whatso ever
I need to flash a kernel for the stock froyo 2.2.2 on the LG Optimus 2x (LG-P990HN). I NEED to get rid of the annoying TOUCH BUG on the phone, and I heared that flashing an alternative kernel will fix the problem. For those of you who don't know what the touch bug is: when you tap on certain spots at random times the screen will become unresponsive and you have to tap harder. It's very annoying.
THANKS!
What about upgrading to 2.3.4?
Rutifruti said:
What about upgrading to 2.3.4?
Click to expand...
Click to collapse
Well.. I WISH I could. However the LG Update tool says I'm at the latest firmware. I'm in Canada with Fido so maybe they didn't realease the 2.3.4 update. That makes me mad because the rest of the world has 2.3.4 and is waiting for ICS. Not fair. So do you know what kernel I should flash?
Anyone know? The touchscreen is annoying the heck out of me. Any kernel I can flash, anything????
How about rooting your phone. I actually can't believe that some living person has the patients to use that awful froyo
Release. It's buggy and annoying. I lasted about 3-4 weeks before rooting my phone, I would have sold it or thrown it away if it wasn't for custom rom . And I don't believe you can change kernel without rooting it. Root saves your phone
My opinion by the way
Sent from my LG-P990 using Tapatalk
You can't flash anything without rooting.....
And if you root, it's weird to keep the old buggy crappy Froyo.
Root wit SuperoneClick,
then install Clockworkmod recovery, and the you can flash whatever you want.
xda<3 said:
Anyone know? The touchscreen is annoying the heck out of me. Any kernel I can flash, anything????
Click to expand...
Click to collapse
What is this 'touch bug'? Can you describe it pls.
---------- Post added at 03:22 PM ---------- Previous post was at 03:13 PM ----------
Have you checked out Spica's HorsePower 2x eXtreme 24BPP for stock MCR FROYO/GB?
http://forum.xda-developers.com/showthread.php?t=1295486
Recommend reading the above thread.
Guys I am rooted! But I am hesitant to go to CM7 or alpha CM9 because I'm scared that when I backup my stock rom on Clockworkmod it won't recover. Happened on my previous phone (HTC Hero) and I was unable to return to stock. The reason I need to be able to go back to stock is becuase I might return the phone if the touchscreen bug doesn't dissapear after flashing a custom ROM. And yes I used SuperOneClick 2.2 and I might unroot it. (depending on how the custom ROM works)
indyroid said:
What is this 'touch bug'? Can you describe it pls.
---------- Post added at 03:22 PM ---------- Previous post was at 03:13 PM ----------
Have you checked out Spica's HorsePower 2x eXtreme 24BPP for stock MCR FROYO/GB?
http://forum.xda-developers.com/showthread.php?t=1295486
Recommend reading the above thread.
Click to expand...
Click to collapse
It's a bug with the earlier versions of froyo. When you tap on certain areas at certain places it will be unresponsive. Most of the time it's ok but sometimes even up to 10 minutes the phone is unresponsive and you have to press everything harder.. not just a light tap. It's TRULY annoying. I want to upgrade to CM7 but I don't want to void my warranty. So I will backup the stock ROM. I just hope it recovers properly. Last time it didn't
One advice... If you're using CWM 5.0.2.0, don't rename the backup folder after you made a backup. Otherwise you'll get a MD5 mismatch and it won't recover. Learned that the hard way...
I'm not sure if this problem is also on the newer recoveries.
You can rename but without space in the name. Yes bug still present. I would recommend to use 'old' 5.0.2.7, Touch Version is too buggy.
You can backup Froyo, but even if you unroot you'll still have Recovery. The only solution would be nvflash.
Cm9 is good lol. With Ironkrnl, very fast.
Striatum_bdr said:
You can rename but without space in the name. Yes bug still present. I would recommend to use 'old' 5.0.2.7, Touch Version is too buggy.
You can backup Froyo, but even if you unroot you'll still have Recovery. The only solution would be nvflash.
Cm9 is good lol. With Ironkrnl, very fast.
Click to expand...
Click to collapse
I've flashed CM7! MUCH MUCH FASTER. But my phone doesn't vibrate anymore. It vibrates only for the bottom keys like home back search etc. But the vibration is weird.. its like really strong. Not the same as before. And I'm still having an issue with the touchscreen where sometimes it won't respond to my touch and I have to touch it another time . Is it because the screen has bleeds. Yellow hue at the top two right corners? Should I get it replaced? So i'll restore unroot and get rid of recovery.
EDIT: Nevermind it seems the vibrate issue is all sorted out now But now theres another problem. When I turn my phone off the Home back and search etc buttons light up and don't turn off......
EDIT: OHHH CRAPPP!!!! Can't restore the stock 2.2.2 I'm so screwed. It won't boot up. I hate my life. Any way of restoring to stock android 2.2.2? I need to return it!! DARN IT I shouldn't of ever trusted Clockworkmod! I knew it wouldn't work!
How do I get rid of Clockworkmod Recovery?
How would I got about this proccess?
xda<3 said:
How would I got about this proccess?
Click to expand...
Click to collapse
Dude.. there are stickies and threads all over to walk you thru.. why dont you search a bit rather than spamming the fora by opening new threads..
The guys here are too helpful but we dont believe in XDA being a noob feeding ground.
Thanks.
Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc
How did you upgrade?
bkgrc said:
Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc
Click to expand...
Click to collapse
Hi
i have been having the same problem have you found the solution if yes please share it,
i upgraded my galaxy note in February and i have my galaxy note is really slow many time and i have to restart it many times a day...And it gets really hot too.....
Note 1 hangs after upgrade
Hi baz77,
I did the upgrade via samsung kies, connect phone to my PC. few weeks ago.
Thx
system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..
Note 1 hangs after 4.1.2 upgrade
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
Rooting does void your warranty but the process is relatively simple. Follow 1a method in this guide.
the link rcheung28 has provided is the perfect way / safe way
bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
If ever you have to return your phone to the service center, simply flash an official wipe ROM through PC Odin (that will remove the root and restore the phone to its "original" state). That's what I did when I had to replace mine (I flashed a Gingerbread ROM, made sure the phone booted fine and I was good to go).
nokiamodeln91 said:
system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..
Click to expand...
Click to collapse
What if I just disable the app instead of root delete? Any idea which app can be disabled without affecting phone normal operation? Thanks
i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..
jaycm1130 said:
i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..
Click to expand...
Click to collapse
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
I haven't used a stock ROM for while, not because of battery drain (which is mostly app-related and can be checked with BBS), but because it was sluggish compared to CM.
As for the media scanner issue, you can try this app.
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..
jaycm1130 said:
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..
Click to expand...
Click to collapse
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.
devll said:
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.
Click to expand...
Click to collapse
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..
jaycm1130 said:
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..
Click to expand...
Click to collapse
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:
devll said:
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:
Click to expand...
Click to collapse
Philz kernel is stock based kernel not a stock one..
try this app: https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
One thing that I've noticed that I haven't heard people talk about (maybe because it's stupid and non-applicable) is to go into your DCIM folders, both on your SD and in the phone and delete the entire .thumbnails directory. Mine somehow managed to accumulate a good GB or so of thumbs and that appeared to be bogging down media searching.
Even after that, phone has been really laggy lately. Going into running apps, I noticed a "Software Update" process running, even though I know this phone will not OTA update. Killed that process and things were ok again. YMMV.