Boot loop after CM7 & Baseband 15 - XPERIA X8 Q&A, Help & Troubleshooting

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

Related

Keeps rebooting after Darky 8.1 update

Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Zink6 said:
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Click to expand...
Click to collapse
try a re flash of another ROM preferably a stock ROM then start all over again, similar thing happened to me earlier, i am quite new to all this but i dont know if its the kernel or lagfix i had what caused this...
i re flashed back to froyo and then installed darkys ROM then re installed my kernel last.. all is good (for now)
worked for me first time but when i went to sgs tools to upgrade your apps ie gallery, camera, it said no busybox installed but went ahead and done fine in v8.0 and i see that cwm changed from red to green too went to market for busybox to download it but when it goes to install phone just reboots all the time mmmm...
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
stepsch said:
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
Click to expand...
Click to collapse
YES !!! i agree, it is a pain.. but we love our phones and we would do anything for them its always best to flash back to standard FW if you ever get a problem...
I myself experienced this. Whenever I installed a new software, it would just boot. I got fed up because darky's forums are also down and there is no discussion. flashed doc's rom. Now everything is fine.
...mh... but it's not caused by Darkys ROM. This cycling boot feature may appear at all ROM, at all lag fix actions and so on. It depends how proper you interact with phone- and ROM-features while configuring. A lil disturbance during your session (by you or battery issue or whatelse) or a not so well prepared basic from where you start and your unlimited-feature-wishlist-and-paint-it-golden-one-click-action is enough to interrupt the whole thing and run into trouble.
It was and is all the same - since DOS or C64. And it will be the same, even when iPhone is on level 12.x or Android will be able to beam you elsewhere thru the barcode scanner.
It's a game. Nothing more. And game means lot of fun - and in the beginning a certain thrill when your phone stuck first time and you are thinking: "... f*ck... bricked..."
yup same for me
cycle boot thing
didnt enable download mode before that....
can get into debug screen thou but wiping it doesnt help
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
Just tell the warranty guy darky screwed it .
OR
http://forum.xda-developers.com/showthread.php?t=853950
jje
cant even boot the phone mate
so ehm i dont get it....how can odin help me ?
is there any way of getting it into download mode still when it doesnt boot up? i heard about that JIG thing they made themself...isnt that just like the microusb cable that comes with it to the pc? i dont get it sorry if im trippin but im maddd at myself for even trying this lockscreen thing
http://forum.xda-developers.com/showthread.php?t=819551
jje
Thanks guys for all the replies. Now I did try flashing a stock rom but with no results. Was still having the same thing happening to me. If you guys can give me the link to the files you used to solve this problem, that would be great. Also just for your information I have a Bell i9000m unlocked running on fido. And NO its not an sd card failure lol.
As for DarelSteilz85, I did make one of those JIG usb for myself. It easy, just get the micro usb and strip it bare to the point you can see the pins on the usb which usually are connected to the wires and get a resister to connect one pin to another. Now for which pins, I remember it was 4 and 5 that you had to connect through the resistor but double check as I am not sure. Also the resistor has to be a certain level which I forgot so double check that also. Good luck.
http://forum.xda-developers.com/showthread.php?t=853950
What i use for problems .
jje

[Q] Bricked Milestone, stuck at Motorola logo

Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result

[Q] Captivate power issue download mode unless charging.

Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.
anarchybob6 said:
Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.
Click to expand...
Click to collapse
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?
BWolf56 said:
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?
Click to expand...
Click to collapse
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?
anarchybob6 said:
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?
Click to expand...
Click to collapse
Start by flashing Odin KK4 from this post: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3 - That will clean your phone of w/e was on it before.
From there, you can flash Corn Kernel to get back to a JB ROM. Although, know that if you had the wrong bootloaders, your phone wouldn't boot and it would show color stripes.
Also, before flashing a ROM, you should wipe system and factory reset to make sure everything is clean (Backup your stuff first).
BWolf56 said:
...your volume down is probably stuck or dirty, making your phone go in download mode all the time...
Click to expand...
Click to collapse
I had a similar problem with my Sprint Galaxy S2 D710 (Epic 4G Touch) - my phone would randomly reboot every few days, and it kept getting more frequent. I thought it was the ROM, the overclock, etc. I flashed back to a stock ROM, and stock clock speeds. Eventually, I noticed that even brushing the power button would wake the screen, and about 10 seconds later the phone would reboot. I cleaned the button with some 95% isopropyl (rubbing) alcohol, and it worked better for a few weeks. It started acting up again, so I bought and installed a replacement power button.
Long story short, I got a new power switch, soldered it in place, and have had zero problems since!
The i897 Captivate uses the same switches for power and volume up/down. These switches are notorious for failing, so that's probably the issue with your phone. Try cleaning them, or you can buy a new switch for about ten bucks on ebay.
YouTube has numerous "teardown" or "disassemble" videos and several eBay sellers offer the switch you'll need.
(They don't include the skills needed to replace it. It's a tiny switch - about 4mm long, and you'll need a good soldering iron and a steady hand. Do you have a friend who's pretty good at soldering stuff?)

[Q] Galaxy S I9000 won't boot and turns off

Hello Community,
I'm new here and hope you can help me even if it is only a little bit
So I have a Samsung Galaxy S I9000 with stock rom 2.3.6, root rights and cwm flashed.
Before I did this I had some problems with my phone, e.g. if I hit (gently) the back side the phone turns off =/
My new at the moment real problem is that I cannot turn my phone on if I only use the battery. (onlly the Samsung logo appears for a short time)
I can only boot it if the phone is pluged into my computer. When it runs and the display turns off, the phone will go off also. (not instantly but atfter 2-5 minutes)
Does anyone knows something about such a problem?
Thanks for your help.
graphik_
p.s.: I am sorry for bad english =/
graphik_ said:
Hello Community,
I'm new here and hope you can help me even if it is only a little bit
So I have a Samsung Galaxy S I9000 with stock rom 2.3.6, root rights and cwm flashed.
Before I did this I had some problems with my phone, e.g. if I hit (gently) the back side the phone turns off =/
My new at the moment real problem is that I cannot turn my phone on if I only use the battery. (onlly the Samsung logo appears for a short time)
I can only boot it if the phone is pluged into my computer. When it runs and the display turns off, the phone will go off also. (not instantly but atfter 2-5 minutes)
Does anyone knows something about such a problem?
Thanks for your help.
graphik_
p.s.: I am sorry for bad english =/
Click to expand...
Click to collapse
Weird try a flashing a custom ROM while plugged into the computer maybe it will help.
Sent from my GT-I9000 using Tapatalk 2
Seems to me like a hardware problem.I guess battery is going to die soon.Try with another battery.
TheImpossibleEnemy said:
Seems to me like a hardware problem.I guess battery is going to die soon.Try with another battery.
Click to expand...
Click to collapse
I can exclude the battery. I have tested two of them and I can be sure that both are well because they work in another Galaxy S I9000 without problem.
To flash a custom rom with plugged phone into computer will be tested tomorrow.
graphik_ said:
I can exclude the battery. I have tested two of them and I can be sure that both are well because they work in another Galaxy S I9000 without problem.
To flash a custom rom with plugged phone into computer will be tested tomorrow.
Click to expand...
Click to collapse
Good luck:good:But I would suggest to flash stock gb rom first just to make sure its not a software problem.
I remember @xsenman has mentioned a solution for this problem about two months ago..... I am sure he will write you soon here.
I had the same problem with my phone, it would reboot if i tapped the back of it, i found out it was a dodgy app i installed so i uninstalled a couple of apps i recently installed and it solve the problem.
So know I have tryed to flash with connected phone. I do not know whether it works because the phone won't boot the system, only recovery and bootloader.
In cause of this I have reflashed with Odin again. Now I get at reboot this screen:
image: s29.postimg.org/bu61r7md3/PZv_PCPk_Txs5a_Xl_G_z1a22_Odgumodl7_HN6v_Ksy3_Q5_MNPm_s.jpg
sry but i cannot post direct links =/
I understand what there is written but I don't know why, the only sdcard is my internal there is no external connected.
So there is a new problem and I would be glad about new ideas =\
(I tryed: reboot, wipes and reboot, wipes and new flashing (same problem))
@tetakpatak if my system boots again I would search for his post thank you

[Q]Suddenly shutdowns on MI3 Need help

I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Maybe there's a problem on your phone's battery. Try to bring it on a service center.
error01671 said:
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Click to expand...
Click to collapse
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
paul c said:
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
Click to expand...
Click to collapse
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
error01671 said:
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
Click to expand...
Click to collapse
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
paul c said:
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
Click to expand...
Click to collapse
OK, I got some conclusions, and it might be a hardware problem.
First, I replaced the battery with same ROM, it still got SOD.
Then I flash Omni, PAC, Euphoria-OS, all got SOD like before.
So I return to MIUI, no SOD, but I got random reboots and sometimes Wi-Fi will disconnect itself even in its range.
Now I'm using Ivan's AOSP, still got random reboots and Wi-Fi problem.
And now I need this phone to work because I don't have a backup, waiting for new Nexus!!

Categories

Resources