Related
Hey guys,
I upgraded my G1/Dream from an older cyanogen version, to the newer one 4.2.15.1
and now for some reason my phone keeps restarting Any reason why ?
Can you please tell me how to fix it?
I've taken battery out & Also 'green+home+red' . Same keeps happening.
It restarts when it wants, can be 2 minutes, 10, 30.. but lately ever 1 minute or so..
What can I do?
Bump
bump
Anyone?? please
I'd recommend a full wipe and reinstall of your desired rom from scratch. Sounds like kernel panics to me.
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Tone-E said:
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Click to expand...
Click to collapse
Why would you completely unroot and reroot? That's just too much work.
Wipe, and reflash. Also, a few apps have a problem with custom ROMs, try disabling apps that run in the background one by one until you find that your phone no longer reboots.
However, if you didn't wipe, I highly recommend that as the person before me said.
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
Probably other people will say it, but wrong forum.
Also, what ROMs have you flashed after the nightly froyo? Nightly froyos are cautioned, which I'm sure you knew.
yep, I used a couple of FroYo SP French Connection nightlies and then switched to CM V6.0.0-RC1.
(sorry if it's the wrong forum, @admins, please feel free to move it to wherever make sense)
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
This may not be your problem, but I found personaly that as soon as I enabled swap, my phone became a bit unstable. It was not rebooting itself when I had compcache on. Then I turned that off and switched to swap and now my phone rebooted itself sometimes. For me compcache was noticeably faster but swap multitasks better. So I've kept swap in spite of reboots. I have also found that switching between them either way my phone becomes unstable and rebooted itself multiple times before becoming stable on compcache or at least not rebooting as much on swap.
Sent from my HTC Magic using XDA App
well i had the same issue. nothing helped, i reinstalled the spl, radio, rom, recovery, everything.
the only thing that helped is :
REROOTING YOUR PHONE
there´s no other way.
have a good day.
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
<snip>
Click to expand...
Click to collapse
I would expect a Donut based ROM to be fine. Which ROMs have you tried since the freezing/rebooting problem started?
The next time it reboots you should take a copy of /proc/last_kmsg and post it here. You can do so with:
Code:
adb shell cat /proc/last_kmsg > last_kmsg.log
Reboot cycle
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
benjaminb007 said:
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
Click to expand...
Click to collapse
Eclair ROMs are just as stable as donut ROMs and as fast as donut. Just don't use Froyo till it's stable. Use CM5.0.8 or any CM variant and you should be fine.
I'm having the same problem after flashing the new radio the phone will boot and as soon as its done loading the home screen it will reboot then load the home scree and turn off
Flashed French Connection ROM few days back and have had same problems as above ever sense.. Flash other ROM's and they constantly Reboot. cy 6.0 Working for me now, But only my Nandroid back up of it. Re flashed it fresh and it reboots...
why dont you reroot ur phones like i told you?
This freezing and rebooting problem is weird - it doesn't make sense a lot of the time.
I've developed a ROM based on AOSP 2.2 for the G1 and it also seemingly randomly freezes or reboots.
When it reboots it's usually the result of an ARM9 crash and so far I have tracked it down to a call to a proprietary library function which doesn't return to the correct return address. It seemingly returns to a random address and the consequences of doing so is random. Sometimes it causes a freeze or a reboot and other times it doesn't.
I'm starting to suspect something in the JNI code is causing the problem but it's difficult to track it down.
FroYo SP French Connection is overclocked to 614 by default. My Mytouch (32B) reboots and freezes constantly if i don't turn it down to 576. Try turning the overclock down in set cpu to 528 first then if its stable you can try turning it up a little.
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
alutastisch said:
why dont you reroot ur phones like i told you?
Click to expand...
Click to collapse
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
akivlin said:
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
Click to expand...
Click to collapse
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
hudl said:
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
Click to expand...
Click to collapse
I totally agree. I know waiting for the official Froyo for the Magic may take years before it's finally released, but I'm tired of flashing and testing new roms every day without getting the results I want. As a result of this frustration, I will go back to Donut 1.6 for now and wait for the official update. Hopefully 5.1 won't be out before we finally get the update
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
Yes, I will find out the maximum Donut clock speed and test at that speed.
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
I modified the kernel to allow only the following frequencies:
09-12 01:41:12.579 D/setcpu ( 281): Autodetecting Frequencies
09-12 01:41:12.599 D/setcpu ( 281): Frequencies autodetected: 122880 128000 245760
Click to expand...
Click to collapse
Unfortunately the phone still rebooted due to an ARM9 crash.
I've attached a small CM6 RC1 update as a test fix for the ARM9 crashing.
Anyone experiencing random freezing or reboots should give it a try by copying it to your SD card and boot to recovery to flash it.
If you install the test fix but still experience random reboots I'd appreciate if you could upload a copy of /proc/last_kmsg to http://android.pastebin.com and post the link to it in here. A logcat up to the point of the reboot would be very helpful too.
hey there fellas
(i'm sorry to post my problem here in the development section but i guess it might be related to the lag fix)
My SGS is acting weird lately , dunno if its related to the lag fix ( [UTIL] One Click Lag Fix 1.0 - 2.0 ) ever since i got the phone with normal use iv never seen anything funny like this. it all started with lag fix version 1 , the phone was fast and with that fix even faster , the phone was all good started with the root as step 1, then it was the market fix, after that i was tempted to try the lag fix which was amazingly effective, went from version 1 to version 2 of it and then it started.
the phone took long to respond 'sometimes' when the screen was off and after a day the phone simply didnt want to get out of standby ( black screen ) so used the boot mode and formatted the phone , once the phone started i formatted the internal sd and rebooted and applied the Root-market fix-lag fix ver 1.0 in that sequence, now the phone seems a little weird . by weird i mean strange things r happening like when i goto the apps menu the icons move by them selves in a random way after a reboot. I set it up to show apps in the first couple pages followed by games , now its all messed up and i didn't mind it at all.
with my internet provider i really have to keep an eye on my 3g usage, and have been using 3g watchdog to keep track. now i notice everytime i restart or switch off / on the phone, the counter goes back to 0 which really gets on my nerves.
now to track the problem would someone point me in the right direction ?
could it be the lag fix ? could it be the program itself ? should i switch to another ? would i need a fresh flash ? my phone is working on eclair 2.1 version I9000JXJF1 , using kies since day 1 there has been no firmware update for the U.A.E and i dont want to risk updating to anything unless its official from samsung.
any help is much appreciatted ^_^
it's interestingly weird case.
i'll start by suggesting to wipe the cache data, and data in recovery mode or
*2767*3855#
WARNING! FACTORY RESTORE, DATA WIPE AND RESET TO FACTORY STATE, as soon as you enter the last # use it only if you want to clean wipe your phone
i started with the first and then was like WTH and went with the second only to find out its the same procedure hehehe..... anyways phone is fresh now , started with rooting then off with lag fix 2.0 ( hope it dont get that same problem again ) . Now i notice there's no bootup logo when starting the SGS ( the swirling S ) but the sound still plays , is this normal ?
mazroui said:
the phone took long to respond 'sometimes' when the screen was off and after a day the phone simply didnt want to get out of standby ( black screen )
Click to expand...
Click to collapse
I had this exact same issue when I was using SetCPU. Uninstalled it and the problem was gone. Also some of the custom kernels are having wake-up lag.
mazroui said:
when i goto the apps menu the icons move by them selves in a random way after a reboot
Click to expand...
Click to collapse
Are you using LauncherPro? If so, this is common behavior and might also be so with other launchers. After booting up it will sequentially load your apps and that's why they will seem to popup in a random order bouncing about in the menu. After it's finished loading everything it will all be back to normal.
mazroui said:
the counter goes back to 0 which really gets on my nerves
Click to expand...
Click to collapse
Seems to me that you had a problem with applying your lagfix and that the phone doesn't store your app-data properly.
My recommendation is to update to the JM5 firmware. It's the version that's been most tested with the lag fixes. I'm running JM5 with RyanZA's Lag Fix 2.0 and SamSet 1.9e (except kernel). It works like a charm and have done so for the past week. No wake-up lag, crashes or other weird behavior.
Hope this helps, and good luck
mazroui said:
i started with the first and then was like WTH and went with the second only to find out its the same procedure hehehe..... anyways phone is fresh now , started with rooting then off with lag fix 2.0 ( hope it dont get that same problem again ) . Now i notice there's no bootup logo when starting the SGS ( the swirling S ) but the sound still plays , is this normal ?
Click to expand...
Click to collapse
First boot will always take longer time and might also affect the sync between the sound and animation. It's normal!
mekwall
thank you very much for your informative reply
let me start replying to what u just told me
#1
I had this exact same issue when I was using SetCPU. Uninstalled it and the problem was gone. Also some of the custom kernels are having wake-up lag.
i dont have SetCPU installed as i have tried it for a few days and found it useless , since i dont have the 1.2 ghz tune i dont see why i should even keep the app, yes i saw how the app messes with the phone so i removed it.
#2
Are you using LauncherPro? If so, this is common behavior and might also be so with other launchers. After booting up it will sequentially load your apps and that's why they will seem to popup in a random order bouncing about in the menu. After it's finished loading everything it will all be back to normal.
no im not using Launcher Pro and i could see how it would affect the arrangment of the programs but it wasn't that. My guess is it might probably be 1 of 2 , either titanium backup or Mybackup pro after restoring the data and not the apps.
#3
Seems to me that you had a problem with applying your lagfix and that the phone doesn't store your app-data properly.
im guessing a maybe here since i dont know how it would affect my 3g watchdog's app or make it reset the counter, i switched to Network monitor ( not as good as 3g watchdog but it does the same job ^_^ )
#4
My recommendation is to update to the JM5 firmware. It's the version that's been most tested with the lag fixes. I'm running JM5 with RyanZA's Lag Fix 2.0 and SamSet 1.9e (except kernel). It works like a charm and have done so for the past week. No wake-up lag, crashes or other weird behavior.
just like i said id love to go that way but can wait a month or 2 till froyo joins the fun.
#5
First boot will always take longer time and might also affect the sync between the sound and animation. It's normal!
i hope its just a sync problem , but the phone gave up on the animation , after a couple of tries yea the logo simply isn't there anymore just the sound but i did notice a little faster boot up time this way with only a small vibration to indicate the phone has started.
i'll redo everything again 1 step at a time 1 app at a time , i'll delete my backups as i could do it just this time to get a good fix after a clean boot , and i guess i'll just stick with version 1 as i didnt see anything wrong with it so no need to jump to version 2 of the lag fix
could anyone tell me what app will back up all my sms/mms/call log without any trouble ? does titanium do that coz i looked everywhere and couldn't find anything regarding that
Thanx to everyone for your help ^_^
now to find a fix for that gangster game after redoing everything
ok new discovery
using mybackup pro to backup all the sms's and mms's restarted after the restore and boom
what i see now is the old background from before the *2767*3855# method and the apps linked to homescreen from before , could it be the trouble maker ?
ok now im not gonna use it and test the whole procedure all over again
ok i guess thats it... even after a factory reset the logo wont show up again T_T
any tutorials on how to flash the original FW safely ? where could i find my original FW ? thing is i need arabic lang and doubt the JW5 has it built in anyways im off for now....... ~ spends the night googling~
mazroui said:
ok i guess thats it... even after a factory reset the logo wont show up again T_T
any tutorials on how to flash the original FW safely ? where could i find my original FW ? thing is i need arabic lang and doubt the JW5 has it built in anyways im off for now....... ~ spends the night googling~
Click to expand...
Click to collapse
JPJG8 off samsung-firmwares is very good, and has arabic support.
ok ^_^ thanx for the fast reply
downloading it as im typing right this instance
will post on how things go with my SGS
having trouble right now with restoring my apps using titanium T_T whenever i restore it freezez on the first app it shows guess i have to install them 1 by 1
i guess a fresh start is a must
Again thanx you fellas for the informative/fast replies
Much appreciatted ^_^
last but not least
everything downloaded and ready for the flash
using a youtube video looking at a detailed guide to flash my sgs
i notice the big FW file has 3 files starting with CODE , CSC and another CSC
my file JPJG8 has got OJP_JG9 and the files in it are
zImage
param.lfs
modem.bin
factoryfs.rfs
dbdata.rfs
cache.rfs
where do i go from here ?
B U M P . . . . . . .
Anyone knows whats the deal with those files
Hi!!
Something happens with my Nexus One over the night.. I wake up every day with my N1 asking for the Pin unlock code.
Doesn't matter the ROM, RADIO or KERNEL (it just happens with Android 2.3)
My solution was to remove the ask for pin code option...
How can I debug this issue?
anyone please?
Sounds like it's rebooting over night.
Lately when I wake up, I cathe it rebooting.. but its not a normal reboot...
It show the boot animation for linke 3sec and then ask for pin code.. so its rebooting
How can I debug this problem?
I've managed to extract the K_lastmsg: http://pastebin.com/hjaqQVAR
And the logcat: http://pastebin.com/8wKmAE2W
Can anyone help find the problem?
Thank you!
Please?
Sent from my Nexus One using XDA App
Sounds and looks like a kernel panic. I don't see an obvious reason for the crash in last_kmesg. It complains a bit about bad sectors on the internal memory but it should be able to handle those without crashing. What version of CM are you running?
same thing happened to my g1. but nothing similar has happened to my N1. Have you tried lowering the clock speed? I've noticed that if my clock speed is above 900 it'll reboot. Or you could just try wiping your cache and stuff then reflashing it.
I'm using nightly#41.. but no matter what Rom I use. Its always during the morning (usualy before I wake up) no matter the kernel or radio...
I've wiped like 100times 3times each lol but with no lucky... on froyo i never had this problem...
I've no setCPU installed (for debugging purposes)
I'll try the latest nightly though... tomorrow I'll post again
Sent from my Nexus One using XDA App
there you go..
Yesterday I've flashed latest nightly #57.
But this mornig it happen again!
I've pulled out theese logs right after the reboot.
Logcat: http://pastebin.com/7LHGi1n5
k_lastmsg: http://pastebin.com/q7wDDRia
btw.. how can I repair thoose bad blocks?
any help please!
Thank you!
Can't repair bad blocks.
Kernel is not failing according to the logs. Logcat is too old to diagnose anything I'm afraid.
I suggest it's an app or hardware.
Move to a stable ROM
Only install basic apps
Try again
Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
bytecodeboy said:
Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
Click to expand...
Click to collapse
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Mod issue or battery or hardware fault
Cheshire-Cat said:
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Click to expand...
Click to collapse
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
bytecodeboy said:
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
Click to expand...
Click to collapse
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
stamatis16 said:
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
bytecodeboy said:
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
Click to expand...
Click to collapse
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
stamatis16 said:
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
Click to expand...
Click to collapse
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
bytecodeboy said:
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
Click to expand...
Click to collapse
yea, i guess your battery almost dead.....and i dont think its a good idea to by new battery, you better buy new phone,as the batteries are quite expensive if you think that the worth of the x8 right now would be 50 euros....
Try ebay bro
Sent from my E15i using Tapatalk 2
Flash rom with xrecovery not cwm
Sent from my X8 using xda premium