Related
So I hope its in the correct thread... I was helping my friend bring his phone back to life cause he decided to root his phone and flash a rom and it wouldn't work for him... so i tried flashing it back to stock rom and for some reason or other it went into a black screen and it stayed stuck there so I pulled the battery out and tried turning it back on but nothing it just vibrates 3-4 times and it stays on black screen... so Im pretty sure that means its bricked. I wanted to see if anybody had encountered this problem before and if you were able to get a fix or fixed it yourself... I would greatly appreciate it.
does it boot into HBOOT?
hold vol dwn + power
Would also help to know how for into the root process it got.
Sent from my Inspire 4G using XDA App
Flashed this kernel :[Kernel]Skyrocket[2.6.35.14](v0.0.8)OC~1.73GHz/GPU OC/OTG/UV/SLQB/BLN[Jan-08]
Its a great kernel and thanks so much to whoever delvelpoed it but i am having a problem when trying to shutoff the phone. When i press the Power button and slect to Power off. The phone goes black, vibrates, and then restarts. Is there a fix for this? Anything would help because this is a great kernel. Thanks.
I m guessing this is faux123's kernel and if it is what version are you running.
jaison92 said:
Flashed this kernel :[Kernel]Skyrocket[2.6.35.14](v0.0.8)OC~1.73GHz/GPU OC/OTG/UV/SLQB/BLN[Jan-08]
Its a great kernel and thanks so much to whoever delvelpoed it but i am having a problem when trying to shutoff the phone. When i press the Power button and slect to Power off. The phone goes black, vibrates, and then restarts. Is there a fix for this? Anything would help because this is a great kernel. Thanks.
Click to expand...
Click to collapse
Running kernel version: 2.6.35.14 on Android : 2.3.5
I'm really only looking for a kernel that let's me use bln control on the skyrocket, is there a better kernel that you know of?
Yes use romracer's kernel its good stock with bln and boothanimation.
jaison92 said:
Running kernel version: 2.6.35.14 on Android : 2.3.5
I'm really only looking for a kernel that let's me use bln control on the skyrocket, is there a better kernel that you know of?
Click to expand...
Click to collapse
I just flashed romracer's kernel, and it seems to be very stable but i am still having the reboot problem. When i press the power button and hit power off the phone looks as if its shutting down, goes black, vibrates and restarts. Any ideas? Thanks in advance.
What rom r u using?
jaison92 said:
I just flashed romracer's kernel, and it seems to be very stable but i am still having the reboot problem. When i press the power button and hit power off the phone looks as if its shutting down, goes black, vibrates and restarts. Any ideas? Thanks in advance.
Click to expand...
Click to collapse
jaison92 said:
Flashed this kernel :[Kernel]Skyrocket[2.6.35.14](v0.0.8)OC~1.73GHz/GPU OC/OTG/UV/SLQB/BLN[Jan-08]
Its a great kernel and thanks so much to whoever delvelpoed it but i am having a problem when trying to shutoff the phone. When i press the Power button and slect to Power off. The phone goes black, vibrates, and then restarts. Is there a fix for this? Anything would help because this is a great kernel. Thanks.
Click to expand...
Click to collapse
You need to unplug the power cord before selecting "power off", is a work around fix for the CM7 w/Da_G's kernel, and I bet it works for your trouble as well.
To add my experience:
My SGS2 runs Android 2.3.4, kernel 2.6.35.7, GINGERBREAD XWKI4). I've had it for just under a year and it has always run the stock Samsung ROM. My phone's not rooted. I've never had any trouble of the kind I'm about to discuss so far.
Today my phone has begun to restart when I power if off. Googled around, saw some people had such problems because of SD card problems. I unmounted the card, removed it, put the battery back in (yes the phone boot up on its own when I inserted the battery). Same problem with no SD in.
I then saw a thread that some people had the phone on the charger when trying to power off (or the phone showed being on the charger when it wasn't - thunder on battery level); my phone shows no thunder and it's not on the charger.
My 8-year old son has taken the phone for a spin today (which means he fires off about a dozen apps aftes he tires of taking pictures and Cutting the Rope).
Any thoughts about how I might go about diagnosing this? Besides rooting my phone, taking a Titaium backup and hard resetting?
Thanks
Nikolas
In the future Nickolas please refrain from resurrecting an old thread and post a new one. Also u are in the wrong section, u want the original Samsung Galaxy S2, not the skyrocket (this forum), or the T-Mobile T989, but the i9100
Yes, I realize I posted in the wrong place; I'll post it on the i9100 forum. Thanks for the heads up.
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
far8s said:
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
Click to expand...
Click to collapse
any luck on this??? i jacked mine up trying to flash a new firmware and am stuck in the same boat with my sensation being completely unresponsive.
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Overlord-in-training said:
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Click to expand...
Click to collapse
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
No charging LED isn't a good sign.
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
newr said:
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
Click to expand...
Click to collapse
What rom were you running when this happened?
GROGG88 said:
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
Click to expand...
Click to collapse
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
shawn0223 said:
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
Click to expand...
Click to collapse
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
yahhboy said:
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
tjamaican said:
What rom were you running when this happened?
Click to expand...
Click to collapse
I installed 6.6.2 Revolution. It booted fine after I installed the ROM...so unlike some others, the installation seems to worked fine. I was able to run Titanium and restalled all the programs....but then when I talked on the phone....it became unresponsive and shutdown and never turned on again
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
dreaddie101 said:
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
Click to expand...
Click to collapse
WEll..if your phone lights up or have some response.maybe you can still do something by connecting to computer. Mine was completely unresponsive...and can't be detected on computer!
Maybe it's an overclock issue? I've read on different threads that there may be a motherboard issue. The sensation is known for overheating. Maybe it's frying the motherboard.
What frequency were you guys running and was your phones randomly shutting down before it became unresponsive?
i think we guyz got the same problem :S its just turned off with a constant beep
http://forum.xda-developers.com/showthread.php?t=1624293
shawn0223 said:
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
Click to expand...
Click to collapse
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
yahhboy said:
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
Awesome, I just got my new sensation yesterday. Worked like a charm.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
shawn0223 said:
Awesome, I just got my new sensation yesterday. Worked like a charm.
Click to expand...
Click to collapse
Oh and thanks lol
Hi, I am new at this forum and i would like to ask you the following question.
recently i bought a samsung galaxy ace 2 phone and today i decided to try a custom ROM with, being a Linux geek for years...
So i chose Kyrillos Rom for my phone and after several failures i got to understand that before i try to load the custom ROM i had to upgrade my firmware and kernel as described here :http://forum.xda-developers.com/showthread.php?t=1955679
So i used Odin tool , and tried to flash the new firmware as described here :http://forum.xda-developers.com/showthread.php?t=2118119,before proceeding to kernel flash.
Everything went smooth , Odin showed 'pass' indication and my phone after the procedure tried to reboot...and never woke up...
From then i cannot boot my phone at all, i mean neither in usual mode by pressing the power button nor in recovery or download mode. It does not respond to any of those, the screen and the buttons are completely black no matter how many seconds i press them
When i started the procedure my battery level was at 70% and just to be sure i connected it to USB port so as not to empty the battery during the procedure..Now that i connected it to its' charger it does not show the charging indicator
Any ideas as to what happened and how i can fix my problem?
Thank you in advance and keep up the good job!!!
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Blackwolf10 said:
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Click to expand...
Click to collapse
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
VisagenNoir said:
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
Click to expand...
Click to collapse
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Blackwolf10 said:
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Click to expand...
Click to collapse
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. then what exactly do i have to do..
VisagenNoir said:
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. them what exactly to i have to do..
Click to expand...
Click to collapse
i don't think they will know since the phone won't boot up at all they know by going to download so give it a try and take it to a service and if ur in europe rooting does not affect ur warranty hope this helps
Hello all,
So I'm getting desperate.
I've tried everything I can think of but I'm positive my Infuse is dying. I've reset it to factory, rooted it to remove junk apps, flashed a custom rom and kernel, etc, etc. The problem is every few hours or days it will simply stop responding. I can hear the beep when I go to unlock it or turn an alarm off but the screen stays blank and the only way I've found to fix it is to remove the battery and reboot (especially annoyng if I'm using it as an alarm clock and have to remove my case, take the back off and remove the battery to stop the alarm.
Anyone have any ideas?
phazer11 said:
Hello all,
So I'm getting desperate.
I've tried everything I can think of but I'm positive my Infuse is dying. I've reset it to factory, rooted it to remove junk apps, flashed a custom rom and kernel, etc, etc. The problem is every few hours or days it will simply stop responding. I can hear the beep when I go to unlock it or turn an alarm off but the screen stays blank and the only way I've found to fix it is to remove the battery and reboot (especially annoyng if I'm using it as an alarm clock and have to remove my case, take the back off and remove the battery to stop the alarm.
Anyone have any ideas?
Click to expand...
Click to collapse
not enough info.
if you post questions..include the rom, the history, the build, the modem etc
you may be getting the infamous SOD (screen of death) - some app or kernel conflict. Touch response will stop. If you hold the power putton for 20-30 sec, the device will reboot without battery pull.
possible solution: find conflicting app or kernel
use different rom + kernel
use stock gb
use stock froyo
Oh I thought I mentioned. It's a stock rom ( that I rooted with one of the one click tools or Goomanager I'd have to check which) I have CWM recovery 2.5.1.3 Voodoo lagfix installed but everything else is stock but for the root
Either way the only way to get out of these freezes is to take the battery out. Holding the power button down does squat (believe me I've tried all the usual tricks)
Modem wise I can't remember and will have to see if I can find it tommorrow usingthe one click tool it's a USA phone on AT&T if that helps,
phazer11 said:
Oh I thought I mentioned. It's a stock rom ( that I rooted with one of the one click tools or Goomanager I'd have to check which) I have CWM recovery 2.5.1.3 Voodoo lagfix installed but everything else is stock but for the root
Either way the only way to get out of these freezes is to take the battery out. Holding the power button down does squat (believe me I've tried all the usual tricks)
Modem wise I can't remember and will have to see if I can find it tommorrow usingthe one click tool it's a USA phone on AT&T if that helps,
Click to expand...
Click to collapse
Running stock with voodoo. .. if you get sod, it could be from voodoo mismatch.
You can try:
Back up your info
Find voodoo folder in sdcard..delete
Under settings/privacy.. factory reset.
Go to download mode
Odin or heimdall back to stock with repartition
Run as stock unrooted for a few days to see if anything happens
Restore nothing...
If you still see it... it may be hardware
If you don't see it, it's something you installed or restore or file mismatch
You didn't mention but I'll add that you shouldn't add any tweaks. . They can destabilize the os