Hey all, thanks for taking your time to read and possibly help me out with my problem. Yesterday I've tried rooting my droid in order to put cyanogen mod on it later. The reason I was interested in doing that was because I felt as droid was not working to it full potential and constantly crashing apps on me (browser, games, weather, etc). A friend of mine suggested cyanogen as he himself owns it. Being that I've did plenty of CFW on PS2, psp, xbox and mp3s/ipods, I thought there shouldn't be a hassle with this.
I followed the procedures listed on cyanogen's wiki page in order to complete the rooting process. But on the step where it asked to instal .sbf file trough RSD lite and wait till it says "pass" I've ran into trouble.
During the unpacking of that file to the phone using RSD lite the phone was undergoing several reboots, and after finally finishing the reboots on my PC screen in the RSD Lite window it showed 100% complete "please reboot the phone manually". I had no idea how to do that manually as the phone just kept going on and off by itself. (also for some reason it kept saying "error" force close/wait/send notice. But I thought it was probably just the process. After trying to reboot the phone a couple of times nothing worked. I didn't receive any "pass" signs on the droid screen.
I've got a little worried about the whole process and decided to shut the phone off and during that close the RSD Lite on my computer. Doing that made no further improvements for me. The phone just kept going on and off like crazy while in USB and not turning on at all while not plugged into either USB or AC. I've decided to go to recovery mode and just reset everything to stock as I was running out of time and had to get some sleep before work next day. After reseting the cache/data files I rebooted the phone but the same things kept happening to it. Now it was asking me to reconnect with gmail account and all that intro stuff. But the phone would always end up locking up and shutting off somewhere in the process of reconnecting the account.
Fast forward to today I've read that its possible to complete reset everything to stock version trough .sbf file once again. But now the problem consists of the phone not having enough batter life. (I'm not sure what the screen is called where the process of dumping .sbf trough RSD lite starts) but that screen keeps saying battery is too low to do anything with it. And mind me it has been charge for a very long time now in the AC adapter.
Now it also appears as the problem has worsened. The phone does not start up at all in either USB or without connection. It only starts up in AC adapter but then it shuts off in 2 minutes and back on and off , on and off. Recovery mode can't be accessed in any way, at least any way known to me. The black .sbf screen can only be accessed while the phone is not connected to anything but still keeps saying the battery is too low. And I've noticed the phone getting extremely hot during AC charge. (another small detail that sometimes when the phone does turn on and goes to home screen opening up the landscape view does not increase the length of the top (pull down) bar in horizontal view.
I've tried taking out both battery and sdcard and putting them back but no luck. I'm really lost as to what I can do next in order to fix this problem.
If you need any further information please let me know and thank you again for trying to help me!
I don't really see how you managed to get a fc with rsdlite.
Did you reboot your phone (turn off) then boot into usb recovery (power on while holding up, for the droid)?
Sent from my Droid using XDA App
I am by no means an expert and could be just wasting your time but in the absence of expert opinions something is better than nothing right? It sounds to me like maybe you have a bad battery that as luck would have it failed during the update/rewrite. Have you tried getting into recovery with the battery pulled running straight off the ac adapter? Hopefully you made a clockwork/nandroid backup before you started?
sent from a random hobo's droid on xda's app
I'm not an expert either, but having just successfully rooted my droid and installed cyanogen I feel the need to ask: did you hold up on the d-pad while RSD rebooted the phone the first time? If not then you needed to immediately restart the process.
I think you need to use a separate battery charger (meaning that charging battery without a phone) to charge the battery.
Sometimes, battery won't hold a charge when your phone is a brick.
BTW, it appears that you are having the same issue with mine.
(I can't post a URL because I am new here, but you can take a look at my article in this section, called "[S.O.S] A rare MILESTONE brick situation". )
I had the same problem (battery won't charge and phone won't start-up), I had to purchase a separate battery charger, and then flashed another SBF, to make the phone charging normal. (Although my phone is still a brick, but not a problem with battery. )
Since I can't post in development section (under 10 posts) I will ask here!
I'am using Paranoid 0.2 and it is great, no SOD, no battery drain.... but I did notice something strange!
My Note died on the way home from work (got to get extra battery), and when I connected to charger system booted up. I tried several times to power off but every time I connect charger (original Samsung), my note boots up!
It's not really an issue but I'am curious is it just my device or is it a known/unknown software bug??
Did the search button but came up empty
Experienced the same thing the other day.
Generally, my phone battery never depletes to that extent so I'd never had this problem before.
What made it worse was that I was unable to fully boot the phone, it would die in the middle of the Paranoid Android boot animation.
Ended up having to boot into recovery and leave the phone to charge for 10min just to ensure I could successfully reboot.
In any case, not really an issue as I usually recharge the phone long before the battery is completely depleted.
I usually carry charger with me but I was caught off guard this time!
After a few tryes I decided that this ROM is so good that my note simply refuses to stay off
Now I'am really curious about this bug, hoping to hear from someone with more knowledge!!
ozyk100 said:
I usually carry charger with me but I was caught off guard this time!
After a few tryes I decided that this ROM is so good that my note simply refuses to stay off
Now I'am really curious about this bug, hoping to hear from someone with more knowledge!!
Click to expand...
Click to collapse
If I understood correctly:
Your phone doesn't have enough juice to support the boot animation? And you can't charge it because phone just turns on when you put charger on.
Solution would be to boot into recovery, then charge it.
its not a bug
ozyk100 said:
Since I can't post in development section (under 10 posts) I will ask here!
I'am using Paranoid 0.2 and it is great, no SOD, no battery drain.... but I did notice something strange!
My Note died on the way home from work (got to get extra battery), and when I connected to charger system booted up. I tried several times to power off but every time I connect charger (original Samsung), my note boots up!
It's not really an issue but I'am curious is it just my device or is it a known/unknown software bug??
Did the search button but came up empty
Click to expand...
Click to collapse
It's not a bug, its a feature, PA or rathor Android never goes into shutdown mode. It has been implemented that way...
This discussion was discussed on the official PA thread just a couple of days back, read 4-8 pages back and you will get all the required info...
I just used this rom for about one week, the front is small for me
Hello, I'm new to the forums, although I always keep an eye here to download a ROM or reading any tips, but the time has come that I really need help and can't find in any topic, even the ones that are similar to mine.
I own a note and I love it. I've been using the JellyBam ROM for a while now, never changed kernels etc.
that is... until yesterday, when I flashed the thor 0.28 kernel. Everything was nice but today I had to do some stuff outside home so I took my galaxy S player with me, but when I was driving it ran out of battery, so I put its SD card in my Note (N7000), but it didnt recognized my sd card, so i changed them back and drove without music and didnt touch my phone. this was 10AM, I guess.
when I stopped to get my hair cut I noticed my phone was rebooting. I had just left my house and the battery was already in 46%. this was about 10:30AM, so I took of the battery and replaced it. the phone started normally but when the main screen appeared it turned off. I thought it was only the display, so I pressed the on/off button but it didn't work, so I pressed a little longer and the phone started again. but then it turned off.
so I plugged it into the mobile car charger and it turned on normally. so I looked to the battery stats and it was showing 20% of battery left, but the moment I took the energy cable, the phone turned off.
long story short: until now my phone is only working when connected to its charger, although it's saying 100% charged :/
from 01PM, the time I arrived, 'til now I've wiped everything I could, changed kernels, changed ROMs but it refuses to work.
I notice something, though: while charging I can use it normally, except if I try to use the camera. When I click on the camera app it turns off, as like it was not connected to the charger.
I'm about to install the stock ICS ROM to see if the problem vanishes, but I doubt it. let's see...
hope anyone can help me :/
EDIT: I'm using the stock ICS without any problem for like 10 minutes now. But when I was configuring it for the first time it turned off once. this was 10 minutes ago. oh, and the camera is taking pictures and not turning the phone off... when connected to the charger. when I take pictures USING FLASH without charging at the same time, it turns the phone off. pictures without flash are taken normally. goddamn it D: what this could be?
I would just try another battery.
If the problem doesn't occure due to the system, it can only be a hardwareproblem.
So just ask a friend and put the battery of his/her phone into yours and check if the problem still exists.
reported for using a non gpl kernel.
Change it, if you wsnt to receive help at xda, or go ask in th*rs forums...
You are like high on weed going to cops(xda) to ask them about thc content (the kernel that shall not br named)... and then not expecting a scolding.
There a multiple cases where Z3 Compact suddenly off, and then cannot be boot at all (with any mean available). It randomly can be boot, in my case i charged it a long time (approximately one night), then i saw the LED lights lit hence the successful boot. But 5 minutes later, poof, it die again and cannot be boot. I plugged back to the charger, no LED light or respond whatsoever.
The second time i able to boot it, i reflash the stock rom using the PC Companion repair section. But the problem persist, which hint me that this is maybe a hardware problem. I found in the sony forum that the motherboard or the battery could be fail, OR the battery was too low to lit the LED light during charging (which seem illogical for my case which the phone dead with 100% battery).
In the end i sent it to the service center and the phone not currently held up in a ward for god know how long. The friendly assistant at the service center suggested the board or the battery were failed since the phone didn't respond with charging and reset charging.
Any comment from you guys about the possibility of board and battery failure will be appreciated
There a thread in the sony forum,
https:// talk.sonymobile.com/ t5 / Xperia-Z3-Compact/ Sudden-Death-of-Sony-xperia-Z3-Compact/ td-p/877345/page/5
and based on the thread there is a lot of case happen in Malaysia. So for future owner, watch out!
well, this is a similar case [i suppose] http://forum.xda-developers.com/z3-compact/help/bricked-z3c-help-t2952415
Well my Z3C used to be softbricked like you. Meaniez had post my thread about it right above.
The reason for this was the unrespond battery. In my case, I charged it for about 3->4hrs, started at 17%. Then it suddenly softbricked, plugged it to PC, the logo Xperia appeared, but it still remained the same. I took it to the store, their technicians found out that the battery wasn't gone at all, it was hibernate. So they charged it with high-voltage electric for hours, then it came back to life, just like we do the electric shock to save people.
I think my case will help you with a solution to safe your phone.
leonjun said:
Well my Z3C used to be softbricked like you. Meaniez had post my thread about it right above.
The reason for this was the unrespond battery. In my case, I charged it for about 3->4hrs, started at 17%. Then it suddenly softbricked, plugged it to PC, the logo Xperia appeared, but it still remained the same. I took it to the store, their technicians found out that the battery wasn't gone at all, it was hibernate. So they charged it with high-voltage electric for hours, then it came back to life, just like we do the electric shock to save people.
I think my case will help you with a solution to safe your phone.
Click to expand...
Click to collapse
Well, in your case, the phone responded when connected to PC. Mine didn't respond at all. Thanks though for your information.
You meant the logo Xperia didn't appear on the phone when you plugged it ?
fzl.abdulaziz said:
There a multiple cases where Z3 Compact suddenly off, and then cannot be boot at all (with any mean available). It randomly can be boot, in my case i charged it a long time (approximately one night), then i saw the LED lights lit hence the successful boot. But 5 minutes later, poof, it die again and cannot be boot. I plugged back to the charger, no LED light or respond whatsoever.
The second time i able to boot it, i reflash the stock rom using the PC Companion repair section. But the problem persist, which hint me that this is maybe a hardware problem. I found in the sony forum that the motherboard or the battery could be fail, OR the battery was too low to lit the LED light during charging (which seem illogical for my case which the phone dead with 100% battery).
In the end i sent it to the service center and the phone not currently held up in a ward for god know how long. The friendly assistant at the service center suggested the board or the battery were failed since the phone didn't respond with charging and reset charging.
Any comment from you guys about the possibility of board and battery failure will be appreciated
There a thread in the sony forum,
https:// talk.sonymobile.com/ t5 / Xperia-Z3-Compact/ Sudden-Death-of-Sony-xperia-Z3-Compact/ td-p/877345/page/5
and based on the thread there is a lot of case happen in Malaysia. So for future owner, watch out!
Click to expand...
Click to collapse
I am French, exact same thing happened to me last night (didnt boot, plugged it, pressed power/vol+, booted with red light blinking and when on lockscreen restarted automatically and did the same thing again in a loop, then stopped responding at all. Plugged it for the night, green light this morning. Unplugged, didnt boot. Waited, plugged it again, this time it booted up, and it's still working fine. Did a factory reset and erased my data in case I have to send it to repair. It's such a shame, I love this little phone.
I think I'm done. Sick with having to go to the centre, sick with their crappy excuses and most importantly sick with all the 'bad batch' problems - Glass cracked, Flap covers, and worst of all, sudden death? Gosh that's crazy. Btw I am from Malaysia and my phone last night have just officially been infected with the sudden death problem for no reason. I am pretty confident that even if they swap my phone with a new one, that would also be from the bad batch.
But again, this is just me. I hope yours would be much better because overall the phone is actually quite good given the size. Cheers
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
bilboa1 said:
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
Click to expand...
Click to collapse
I know I'm a bit late to the party, but a colleague of mine just contacted me about the same issue - phone rebooted and remains dead.
I have not yet had a chance to look into the phone itself, but according to him the internal storage would be full up to a few MB, which would explain the issue based on your investigation.
Will look into it further...
Dude,
I feel your pain, read what happened to me : http://forum.xda-developers.com/showthread.php?t=3037336
The phone went back in warranty, I just had to pay the postal service, nothing else.
They didn't told me what was the problem, but I think they replaced the motherboard.
Sent from my D5803 using XDA Free mobile app
FYI: Here's the report I received from them.
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
This just happened to me. For my exp, we have this problem when we charge with the magnetic cable. Correct me if I am wrong.
So happy to see this topic, hoping that there is the fix guide in this, however ...
can anybody helps me ?
laufersteppenwolf said:
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
Click to expand...
Click to collapse
Hi,
please do inform us when u find any solution cause i'm facing similar issue after using it for 6-7 months
shardul.phatak said:
Hi,
please do inform us when u find any solution cause i'm facing similar issue after using it for 6-7 months
Click to expand...
Click to collapse
Have you tried upgrading to 5.1.1 (23.4.A.0.546)? I had the same problem, where my z3c would only last an hour or so until the next sudden death and I'd have to wait a few days before being able to turn it on again (and will die after another hour).
Since I upgraded, it has only happened a couple times, and even then I could immediately turn it back on. While it's not a complete solution for me, at least my phone is usable now.
laufersteppenwolf said:
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
Click to expand...
Click to collapse
Well, This sudden death phenomenon happened to me as well this weekend, without any prior warning, since the phone is just 5 weeks old. I tried every possible fix suggested on the web, no response at all.
Now the phone has been shipped to a service centre in Athens, Greece, 350 km from where I live. Ought to have an update on phone;s status in approx. 10 days I was told. I keep my fingers crossed... From what I've read searching this matter during these past days, it seems more like a hardware issue (i.e. defective motherboard). If that's true, and since this phenomenon tends to grow steadily like an epidemic all around the globe (first SE Asia, now Europe) than it is a disgrace for SONY not to organize a recall...
Same issue here. Started few times and then hard brick. No flash mode, no fast boot, no charging... The girl from Sony support, after I've told her that i have an issue reported by many user on their support forums told me not to believe everything I see on the internet . I've been a Sony fan for many years but this denial of a manufacturing fault will make me reconsider...
This has been happening to me regularly now. The only way to get it to boot is to leave it on a charger for an hour or two. After an hour it will say it's charging again. Once it shows that it's charging, you can power it on. Pretty annoying, especially because when this happens to me, the battery will usually be over 90% full.
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
bilboa1 said:
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
Click to expand...
Click to collapse
My internal and external storage are both only half full and the sudden death bug continues to happen. Not sure it's related to storage. I've noticed that it only happens to me when the phone is sleeping with the screen off. I know sony did a lot of work to get the phone to use very little power when idle. Maybe it's related to the phone not being able to wake up? Does anyone know if this happens with non-stock ROMS as well?
penske said:
This has been happening to me regularly now. The only way to get it to boot is to leave it on a charger for an hour or two. After an hour it will say it's charging again. Once it shows that it's charging, you can power it on. Pretty annoying, especially because when this happens to me, the battery will usually be over 90% full.
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
My internal and external storage are both only half full and the sudden death bug continues to happen. Not sure it's related to storage. I've noticed that it only happens to me when the phone is sleeping with the screen off. I know sony did a lot of work to get the phone to use very little power when idle. Maybe it's related to the phone not being able to wake up? Does anyone know if this happens with non-stock ROMS as well?
Click to expand...
Click to collapse
Started happening to me a couple of weeks ago. Currently on SlimRom 4.4 and have been using this ROM for about a year now.
I was actually about to reflash a stock ROM until I saw this thread and now I don't know. Might have to call Sony.