Related
So let me start off with I've done research and not just posting up a new thread because I'm lazy. All of the threads that I have looked through all seem to be close but not the same as most people can boot into recovery.
Running Konis elite series III had it about a week with no issues Ive reboot plenty of times and havent had any problems once so ever. Now I think my problem happened yesterday when I needed to clear up some space and deleted the package I installed Konis rom from I figured since it was already installed the package wasnt needed anymore. I noticed later that day my number pad was no longer showing up didn't pay much mind to it figured i just needed a restart. Reboot the phone today at work and low and behold.
Phone gives me 3 vibrates no lights on regular power up.
Vol - power I get 5 vibrates green flashing led (gotta pull batt for it to turn off)
Vol + I get 3 vibrates no lights
The phone just stays black need to take out the battery in order to get the vibrate errors again.
All the threads I read regarding the 5 vibrates say its in diagnostic mode but everyone else is able to get into recovery. I think I am now the owner of an expensive paper weight. -_-
Would pulling the koni rom install file off the sd do this?
What does the vibrate error mean.. being in diagnostic mode is pretty broad how are you suppose to troubleshoot something like that :/
Are you able to get into the bootloader at all?
Are you absolutely 100% positive that you're holding volume down and power? That should take you to the bootloader. I saw someone with a similar problem, but they were just doing volume up instead.
What happens when you try to power the device normally?
And deleting the rom zip from your SD card shouldn't cause any problems. In fact, I can't think of a single way it could cause anything to go wrong. That is the only thing you deleted, right? You didn't delete anything from internal memory?
Sent from my PC36100 using Tapatalk
well i think that the 5 vibrates and green led's are indicative of safe mode. the other i'm not so sure about. if you're holding vol down and power and getting 5 vibrates then maybe there is a prob with your vol buttons. its acting as if your holding the vol up button without hitting it. maybe its stuck or something like that. just guessing though.
yo
Thanks for all the replys.
Nah doesn't let me do anything. I plug it in and it asks for broadcom drivers thats about it.
I made sure that the vol - is being pressed it gives me 5 vibrations and then the green led no recover menus/
A buddy of mine had the same problem after flashing the kingdom rom on his incredible. He sent it to the phone insurance company and they replaced the motherboard. So basically, your kind of screwed.
Well.....unless you can somehow fix it on the evo...... because I know we tried everything on his incredible, and it would just do the exact same thing every time, no matter what.
nvm same deal. it booted up intro recovery one time i erased cache and ran a saved backup on clockworks phone restarted after it finished and back to the same deal. yay.
unregimented said:
nvm same deal. it booted up intro recovery one time i erased cache and ran a saved backup on clockworks phone restarted after it finished and back to the same deal. yay.
Click to expand...
Click to collapse
What do you mean by back to the same deal?? Back to normal or back to the problem?
hardware related..
volume button keeps getting stuck some way some how and whenever the phone turns off its a pain to turn on. 30+ tries taking the batt in and out. When the phone would be turned on the volume would pop up randomly. Figured it was that so i bumped the phone on the desk with the buttons down and it cranked on did it again early today and it cranked up again after a few tries my phones toast. -_-
(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...
Ok, so this is not my phone that I'm trying to fix. Its a buddy of mine that has never rooted or messed with his phone. Apparently this just suddenly happened out of no where. He can get into a 3 button bootloader but it says "reboot" "reboot bootloader" and "power down". Again this isn't my phone and I'm not familiar with HTC at all. Please help lol
Sent from my SCH-I500 using xda premium
That's the fastboot screen, what happens when you press the reboot bootloader?
Sent from my PC36100 using Tapatalk
similiar problem
I'm having a similiar problem and have read many threads and apparently the problem i'm dealing with is a hardware issue...apparently... I just don' understand how a phone will only boot up to the home screen for a moment and then go through boot loops. When i go into hboot it will stay there and never crash and never bootloop, it will literally stay there until batt dies. It seems a software issue or something to me??? I've rooted it, tried divers roms, radios, etc. all to no avail, so, I then unrooted. I have charged it all the while off and while on. I have pulled the charger and plugged it back up without turning it on just to make it as fully charged as I can. I have let it bootloop until it shuts itself off. I have left it in hboot until the battery completely died and then turned it back on and repeated this until it would not start again. Nothing has worked, I've called HTC and Sprint but it's not under warranty and I am broke.
I am desperate for help....desperate. I have no money to replace it. I will take any suggestions and at this point try anything since it is not under warranty. If anyone is up for a challenge and project, PLEASE pm me. I've exhausted my knowledge, i've even prayed. Can anyone here offer any advice? I'm willing to pull this thing apart and examine the internals but I don't know what to look for, perhaps someone else does though.
From my experience you can do one of two things.
1. Hold volume down and power until the bootloader screen shows up. When in there use the volume buttons to go down 2 to where it was wipe data/factory reset. Hit the power button to select it and then volume up to confirm. Everything on the phone is lost, nothing on the memory card is touched. Then give it a couple minutes when it restarts and it should boot fine.
2. Take the phone apart, I have seen some that bootloop and its because the camera is loose. I know it sounds weird, but over time with phones being dropped or just the movement of being in a pocket can cause the camera to become knocked even a little loose. Simply push on the camera and you will feel it lock into place. Then put the back plate back on and turn it on and you're done.
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
I have read the other posts regarding the rebooting issues of the Sprint Galaxy S3 variant, but I seem to have a touch more difficult problem. My phone constantly resets and seems to be getting worse. It now will reset in the middle of recovery. I was able to wipe the cache and dalvik and then it started resetting even more frequently in recovery and made reloading the rom impossible. It even resets in the download screen. So it makes it impossible to use Odin and other applications. If anyone has any ideas let me know. I have a few possible options that I am pondering. The following is what led up to this if you need some background:
A week ago, I noticed that my battery suddenly was not charging when wifi was on. I turned it off thinking it was some glitch and reset the phone and plugged it in to charge. It said it was at 100 % some hours later. then I turned it back on again and within a couple minutes, it said it was at 22%. So I hard reset and then plugged it into the wall, but it was still not charging. I had go somewhere,so I plugged it into the car charger and enabled fast charge. I turned on my data and all the sudden it rebooted, lost my wifi password, but when it came back on, it was charging properly. So I thought it was just some odd glitch. Charged properly for days.
Then I noticed the phone starting to randomly reset maybe once very other day when texting. I was actually going to put on a new rom tomorrow thinking maybe my old one had become corrupt. Then it suddenly increased drastically tonight to where it was starting to reset constantly. I thought maybe the button was stuck, and pulled off my otter case to make sure it wasnt being pressed down oddly, but it continued. Then I went into recovery and was able to wipe the cache and dalvik before it got really bad and now it won't even let me stay in recovery for any length of time. I almost got a rom loaded when it reset and its been resetting faster than ever. Becoming unresponsive to button presses as well. Even when I could get into the recovery, it would keep showing "swipe screen to open," as the power button was apparently continuing to activate or the phone was trying to reset itself. And yes, I have tried a battery pull several times and then tried to get into recovery, only to be booted out right as I see the recovery screen if I get there.
So that is my problem. I can't flash odin or anything else as the phone just keeps resetting. Part of me thinks to get a new battery and try to see if that doesn't solve my issue, as maybe the battery is causing the phone to reset? But part me is also thinking maybe the power button has gone sticky suddenly? It won't charge it seems as the red light will not come on and it keeps resetting before the battery charging icon can even come up. Any help or advice would be appreciated. I am leaning towards the battery going bad suddenly and shorting out the phone. I now have the battery, which last I saw was at 48% (It was charging when this happened), out of the phone and am waiting till morning to hopefully pick up a new battery. But I would appreciate any insights into this issue.
Thank you very much
Same issue
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
mawamd said:
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
Click to expand...
Click to collapse
I just had my phone replaced for same reason ( Thank god for insurance) Download mode would last about 5 seconds, Recovery would do the same. I managed to get a stock restore with flash counter reset to boot as i was walking into the Sprint store for the techs to look at this lol.. Same exact thing happened on my S2. Power button is done. If you have INS call and get it replaced (Took me about a week for new phone)
I read some post on possibly using Samsung Kies to flash a new ROM, but that was for the international version. I would be curious if anyone has ever tried this or if its possible to replace the power button with a part replacement? I have ordered an S4 but this time I will make sure to use the home and left touch pad more often to unlock the phone and save wear on the power button. I wold still be interested f anyone has found a fix for this.
mawamd said:
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
Click to expand...
Click to collapse
So after looking around, I am pretty convinced this the power button,as people describe on this question. If you don't have insurance, I see there are selling replacements or you can pay someone to replace and fix the power button fairly affordably on ebay. I might go the second route, as I want it fine right and the man had a 100 percent rating positive, and I dont really know what I am doing lol. Thanks everyone for your answers.