Related
(Tittle changed from *Phone won't boot with sdcard inserted*)
I woke up this morning and my phone was just dead over night. I thought well the battery just drained but no. First it wouldn't charge, no red led lighting up on the power button. After 15 min. in the wall charger and no sign of charging i hooked it up on my netbook. About five min. went on and then the red led shined and i thought yes and tried booting but just a vibrate once and a black screen.
I was running latest 4.0.A.2.368, rooted, unlocked bl, doomlord's kernel and @thomassafca's samsung theme when this happened.
Tested fastboot mode and flash mode all good there, blue and green light.
Then i re-flashed doomlords kernel and it rebooted to the point of *sony ericsson* on the screeen and went black and then the charging icon and orange led.
Took out the battery and inserted it again and booted up. Again only vibrate once and then black screen.
Then flashed kernel.sin with flashtool, still the vibrate once and black screen.
So i was a bit lost and took out sim and sdcard and flashed 4.0A.2.368 ftf file posted by @thomassafca and it booted fine. Then i turned it off and inserted the sim and booted up. It booted just fine. Then inserted the sdcard and again vibrate once and black screen.
Then formated the sdcard extFat still no boot, tried Fat32 no boot, tried a card from my old nokia wich should be formatted correct since it also run on a linux base (maemo) no boot.
I'm a bit lost on what to do to make my phone boot with sdcard again.
Have been working with no issues at all since i flashed the new firmware/unlocked bl/flashed kernel/rooted.
Any help will or if someone could explain what happened will be great
Regards Dousan...
e: Ok a slight change in this. The phone when turned of won't boot again unless i take out battery and insert again. When booted into the phone i inserted the sdcard and mounted it and now it boots with the sdcard, but still the same issue of having to take out the battery to boot when turned off?
e2: Tried adb reboot and it seems to go in a bootloop. It connects to the pc and disconnects (windows sound plinging connected disconnected) and i can adb devices and a connected device number appears after the first pling and after the second pling there's no device to be found with adb and then it just goes on and on till i disconnect and pull the battery and boot? All this is with a black screen not even *sony ericsson* appears.
e3: Reflashed it with the latest fw and without pulling battery it booted right up and i thought, yes, problem solved. Went through setup and then turned it off and booted the phone and still vibrate once and a black screen. Pulled out battery and botted again and still vibrate and black screen? So pulled it out again and sdcard and it booted up fine. Inserted the sdcard when on and mounted it and it works, but still the boot problem?
After the reflash the vibrate felt different, stronger, and after i pulled the battery it's weaker.
e4:Flashed doomlords kernel again and rooted, still same issue?
e5: Solved problem by flashing doomlords kernel v2 for fw 4.0.A.2.368. After flashing it booted with the kernels new boot txt and then it turned off and the charging icon showed. Then booted into cwm and wiped dalvick cache and battery stats. Then rebooted from cwm and it booted up. To make sure problem was resolved I tried 2 times in a row to reboot with quick boot and it booted without me having to pull the battery Thanks all for your suggestions
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
AndroHero said:
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Cheers mate for the surgestion, but that was a no go, didn't help
Back on 4.0.A2.368/unlocked/doomlord kernel/rooted... With a reboot problem
Regards Dousan...
Could be related to the doomlord kernel?
Sent from my R800
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Deoxlar said:
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Click to expand...
Click to collapse
Not likely as i only OC'ed to 1400 the first feew days i had the kernel and then 1200 and when it happened stock clock.
My incident is isolated and your point is?
@captain67, yes it might be related to the kernel, could be?
Regards Dousan...
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Dousan said:
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Click to expand...
Click to collapse
And it turned out that there was a point to it, problem solved
First post edited (e5
Regards Dousan...
Had the same problem
It was solved by magic though
Sent from my Xperia PLAY R800i using XDA App
And then the problem reappeared and this time i couldn't fix it myself and has just gotten my play back from service today (one and a half week they had it). It turned out to be some hardware problem and i've got a new screen, top cover and some other stuf.
Flashed the latest FW and locked the bootloader before handing it in and just told them what happened. Woke up and turned the device on and it froze and then it turned off with the backlight on. Tried rebooting but just a single vibrate and then a black screen.
They fixed my issue but created another. The volume button is now broken and i have to go back tommorow for a second time. Just booted the phone this evening and wanted to hear some music, but couldn't turn up the volume without pressing a pionty thing on the rocker. Down works fine. Bit annoying that a broken volume button can leave the service place, that should've been seen by the service person in the shop before it was ok'ed.
The screen is nice and crisp and the old one had a backlight issue i just lived with... untill now
Regards Dousan...
So a little update on this:
As i said they broke my volume button while repairing it for the stuff i wrote about above (didn't want to turn on).
It took me a week to go back with my play and in the meentime i descovered that it would randomly turn off during the night and wouldn't turn on unless i pulled the battery and charge it untill the charging symbol showed on the screen. It would then boot and first i thought it was the battery that was drained, but when on the lockscreen it showed that there was plenty of juice on. One time it was 35% and another it was 62% and no way it could've charged that much in 1-2 min.
Another thing i descovered was that when turned off it wouldn't turn on again unless i pulled the battery.
Anyway i went to pick it up yesterday and here i saw that they've broken my R-trigger Those idiotic service people even ticked of a box on the service papers that they've checked that all buttons where working (i don't think so, slackers). They did this on both occations
My play had no juice on it so i wasn't able to see if they had fixed my problem about not being able to reboot without pulling the battey and the random switch off's. Further more the service papers that came back with the phone didn't mention it at all? They did fix my volume button or atlest it seems they did as i couldn't turn it on and check if it did actually work.
So once again i'm without my play, but this time they're processing it express
Regards Dousan...
As long as you can use your phone,its all good
Cat_On_Droid said:
As long as you can use your phone,its all good
Click to expand...
Click to collapse
Yeah i know, I'd rather have them fixing it though, than having a fualty device. In the end it might go to SE and let them see if they can fix the issue. Hope not, don't want to be without my play once again Got the iches for gaming and now EA got free games, bummer
Regards Dousan...
Well just need to vent a little.
Starting rant:
So I got my phone back today for the third time. They did fix the R-trigger they recked the last time it was in for service, but they didn't fix my issue with the random rebooting/turning on without pulling the battery.
They claim it worked fine before shipping it, but when i unpacked it and let it charge enough to power on guess what it didn't turn on i had to pull the battery to get it to turn on lol They shipped it without checking if they fixed it. Hell i don't even think they tried at all cuz then they would've cought it straight away. They're full of BS and when googling them and reading their trustpilot it's also full of dissatisfied customors with the same type of problem as me, no fixing or pour fixing or even more breaking of the device or simply lieng it was water damaged
Hey that sound's familiar to me, not fixed and more broken, those C*NTS.
I'm pissed and nothing i can do but a claim with the place i made the purchase.
Rant ended
Regards Dousan...
End of story...
Well the last update on this.
I made a claim with cdon.com where i bought it and sent it of to their service center for repair and once again it was returned non repaired. Still wouldn't turn on without pulling the battery. Then they sent it of to SE and they couldn't fix it either and sent a new device to cdon.com, but i chose to get my money back instead of a new device.
The cons of this device ended up being more than the pros. Relly liked this device though and what it was supposed to've been. I was just not the big gamer i used to be and mostly played RB6 online and found the lag of analog touchpads support in fpse annoying and psxperia converter tool didn't work with the games i liked to play.
Anyway it was a fun ride while it lasted and mostly a friendly helpfull crowd I encountered here in the play sub forum. Must say that it has been the best forum I've been submitted to so far
Thanks to all of you and I might see you around
Regards Dousan...
What are you going to buy in the end?
Logseman said:
What are you going to buy in the end?
Click to expand...
Click to collapse
I ended up with the Lumia 800. The N9 seemed nice and have good specs and a familiar OS, but tried it out a few times in a shop and didn't get that wow feeling. Further more read a few things on TMO (talk.maemo.org) in the N9 sub forum that convienced me not to pick up the N9. Even read some danish users experience with the device and it wasn't good all in all. Though the N9 has it's openess and a lot of modding potential i didn't want to go for a 'half finished OS' as i see it from reviews from users. On TMO hardcore N900 users that shifted to the N9 was dissapointed in the N9 as it's gone more mainstream and comercial in how Nokia build the OS.
As of now the Lmia suites my needs much better and I do like the WP7 feel and looks.
It was hard to choose between the two devices as they both have good things going for them.
Regards Dousan...
My epic randomly went into boot loop on sunday. I odin'ed it monday and it was working better then before i woke up today and it was boot looping again i just tried odin 3 times now and it boot loops... is my epic bricked?
No, bricked means no lights, no power, no nothing. You are sponged. Try a different cable and a different tar.
Sent from my SPH-D700 using XDA App
any idea why this would keep happening out of the blue? Also i am using another my other cable that i always use. used it to root and odin multiple times.
What are you Odining and are you restoring data? My guess is your data is bad. Downlod your apps fresh from the market. Don't restore any data.
Sent from my SPH-D700 using XDA App
IDK
Not restoring anything i also removed the sd card. I tried to odin ec05 stock and eb13 stock. right after it says successful and closes threads i unplug my phone. Then put my batter back in and it say samsung after about 45 seconds it turn's black and samsung comes back up and loops. Also when i charge it shows the battery icon and the spinning circle in it freezes and the screen will not turn off. Seem like its just done for. I took extremely good care of it too very frustrating. If you have any other idea's I would appreciate them.
Edit: also each time it did this i couldn't get into CWM. Thats why i used odin. Just thought i should mention it.
lgevo said:
Not restoring anything i also removed the sd card. I tried to odin ec05 stock and eb13 stock. right after it says successful and closes threads i unplug my phone. Then put my batter back in and it say samsung after about 45 seconds it turn's black and samsung comes back up and loops. Also when i charge it shows the battery icon and the spinning circle in it freezes and the screen will not turn off. Seem like its just done for. I took extremely good care of it too very frustrating. If you have any other idea's I would appreciate them.
Edit: also each time it did this i couldn't get into CWM. Thats why i used odin. Just thought i should mention it.
Click to expand...
Click to collapse
Have you tried using the "official" Samsung EB13 app? I've used it as a last resort for a clean flash.
http://www.multiupload.com/JCW8LY9KE0
poit said:
Have you tried using the "official" Samsung EB13 app? I've used it as a last resort for a clean flash.
http://www.multiupload.com/JCW8LY9KE0
Click to expand...
Click to collapse
I will give it a try
lgevo said:
I will give it a try
Click to expand...
Click to collapse
Good call it seems to be working.. i guess i will see for how long. Really strange it was totally bricked for a few mins no power or lights.. then i unplugged it and plugged it back in and boom started actually charging like normal (the the circle started spinning in the middle of that battery icon) so i turned it on and I was shocked to see the sprint boot screen. I bet its a temp fix till it full breaks but at least i dont have to use this damn blackberry.
Very strange
thanks
The Samsung update tool repartitions your device. It may have been a bad partition table. My next suggestion was to use the PIT file and check repartition in Odin but I see you are up and running...great!
kennyglass123 said:
The Samsung update tool repartitions your device. It may have been a bad partition table. My next suggestion was to use the PIT file and check repartition in Odin but I see you are up and running...great!
Click to expand...
Click to collapse
Oh maybe that was it. Hopefully this battery issues works its self out i kept saying full but really it wasnt charged. now i let it die with the phone on and its showing its low. But anyway thanks.
lgevo said:
Oh maybe that was it. Hopefully this battery issues works its self out i kept saying full but really it wasnt charged. now i let it die with the phone on and its showing its low. But anyway thanks.
Click to expand...
Click to collapse
You should fully charge your battery and clear battery stats in CWM.
allright, i will charge it up then root it again.
lgevo said:
allright, i will charge it up then root it again.
Click to expand...
Click to collapse
No, just go into CWM and hit Clear Battery Stats.
Sent from my SPH-D700 using XDA App
I couldn't without rooting it and installing CWM. So i got it charged, rooted the installed CWM then did what u said. Anyway I hope this doesn't screw up again. thanks for the help guys.
OH, so when you Odin'd you did not root after...Ah, I see. There is also an app to clear the stats and calibrate the battery but I believe it requires root as well.
Everything in the ROM works as advertised, except the battery level will not update until a reboot. Third party apps and the system read the same. Flashed the correct boot image, gapps, ROM etc. Charged up to full (Overnight, reboot, read 100%), then went into recovery and wiped battery stats, nothing happened. About to try draining to 0%, recharge to 100%, and wipe stats.
Kind of doubtful as to whether this will work, but if anyone has had similar experiences on other ROMs or this ROM in particular, any advice would be greatly appreciated :laugh:
bump and update...
Tried above method, didn't work (Almost bricked phone when I rebooted on low battery LOL)
Flashed jmz's updated cm10 app correctly, everything worked as advertised, but battery still wouldn't update.
Starting to think something's wrong with my phone, going to see if Best Buy will take it back.
Asteradragon said:
bump and update...
Tried above method, didn't work (Almost bricked phone when I rebooted on low battery LOL)
Flashed jmz's updated cm10 app correctly, everything worked as advertised, but battery still wouldn't update.
Starting to think something's wrong with my phone, going to see if Best Buy will take it back.
Click to expand...
Click to collapse
Really not sure. you are the only person to report that. flash my stock rom and see if it works.
Alright will do. Thanks for the reply. How do I do a COMPLETE wipe of everything that I can possibly wipe asides from sdcard data (photos, vids)? I think there's something that's being left behind from each ROM i flash, because I restored back to stock, and I couldn't activate phone, restored to your cm9, chrome/browser sporadically and randomly close.
Feels like each time I flash/restore to a different ROM, something new goes wrong.
Asteradragon said:
Alright will do. Thanks for the reply. How do I do a COMPLETE wipe of everything that I can possibly wipe asides from sdcard data (photos, vids)? I think there's something that's being left behind from each ROM i flash, because I restored back to stock, and I couldn't activate phone, restored to your cm9, chrome/browser sporadically and randomly close.
Feels like each time I flash/restore to a different ROM, something new goes wrong.
Click to expand...
Click to collapse
Choose factory reset in recovery. That's all that is ever needed. Some people swear by using every option to individually wipe each item. Its unnecessary. Puts extra wear on the nand.
Sent from my One V using xda premium
Asteradragon said:
Everything in the ROM works as advertised, except the battery level will not update until a reboot. Third party apps and the system read the same. Flashed the correct boot image, gapps, ROM etc. Charged up to full (Overnight, reboot, read 100%), then went into recovery and wiped battery stats, nothing happened. About to try draining to 0%, recharge to 100%, and wipe stats.
Kind of doubtful as to whether this will work, but if anyone has had similar experiences on other ROMs or this ROM in particular, any advice would be greatly appreciated :laugh:
Click to expand...
Click to collapse
Happened to me to. All I did was reboot back to normal.
Sent from my One V using Tapatalk 2
jmztaylor said:
Choose factory reset in recovery. That's all that is ever needed. Some people swear by using every option to individually wipe each item. Its unnecessary. Puts extra wear on the nand.
Sent from my One V using xda premium
Click to expand...
Click to collapse
I do that, but the problem persists. About to try your stock ROM, will update.
Edit: Tried the ROM, similar issues (worse, if anything). Am now suspicious of phone defect. Is there an established way of unrooting/demodding in general the one V? Thanks for all the help so far.
My battery is goofy too running CM9 Primoc.
The first night it charges just fine.. .shows 100%.
The next night it will only charge to 92-93% or so.
The next night it will only charge to 85% or so.
It's like each night I recharge it I lose 7-8% off my final charge.
I'm pretty sure the charge is there it's just displaying the wrong percentage for some reason because if I simply reboot the phone and do nothing else the charge percentage jumps back up. If I reboot it after charging all night then it shows 100%.
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
Hi everyone,
My S3 would all of a sudden just turn off and I wouldn't be able to turn it back on. I've tried taking the battery out and putting it back in. The phone would turn on by itself, but once it flashes the S3 logo, it would go black and the power button would become unresponsive. Sometimes it would keep vibrating. The only way I was able to keep it on long enough to re-flash/do a hard reset was if I took the battery out and left it overnight. But when I managed to re-flash/hard reset, the problem would come up again after a few hours. I was wondering what might be the cause of this. The first time it happened I was just streaming music, the second time it was just charging. I just got it back from warranty because of a loose power button and this problem was never there before. I was wondering what might be the cause of the problem and how I can go about remedying it. Thanks!
Sounds like the battery is failing. To be sure though, you said you can get it up and running for a few hours, right? That should be enough, but first make a nandroid backup. Then recharge, then do a full wipe and odin flash the stock firmware. (Only do this if you are certain it won't die during the flash.)
Are you on a stock rom now? If so and you're not sure enough to use odin, factory reset, including internal sd, and see if it continues.
If it does go to a Tmobile store and see if they'll let you test with a known good battery.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Sounds like the battery is failing. To be sure though, you said you can get it up and running for a few hours, right? That should be enough, but first make a nandroid backup. Then recharge, then do a full wipe and odin flash the stock firmware. (Only do this if you are certain it won't die during the flash.)
Are you on a stock rom now? If so and you're not sure enough to use odin, factory reset, including internal sd, and see if it continues.
If it does go to a Tmobile store and see if they'll let you test with a known good battery.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
I did a full wipe and odin flashed it with stock firmware after the first time it happened. I thought I was in the clear, but it happened again couple hours later. I've tried it with my spare battery but it does the same thing, it would turn on by itself, flash the S3 logo, then the screen would go black.
I'd take it to T-Mobile, let them see it happen do their thing, and ask them to note it on your account if they tell you to call support.
Sent from my SGH-T999L using xda premium