Related
OK so my problem is as stated above. My exhibit boots to the Samsung logo for about 3 seconds then reboots in a continuing sequence. I have tried entering recovery mode with no luck as the phone does not stay on long enough. I am able to boot into download mode however, when i tried restoring the stock firmware nothing happened. Its says that everything went well but the phone keeps rebooting in the same pattern. Though this is no longer my primary phone I would like to get it fixed. Any help is deeply appreciated.
akeem127 said:
OK so my problem is as stated above. My exhibit boots to the Samsung logo for about 3 seconds then reboots in a continuing sequence. I have tried entering recovery mode with no luck as the phone does not stay on long enough. I am able to boot into download mode however, when i tried restoring the stock firmware nothing happened. Its says that everything went well but the phone keeps rebooting in the same pattern. Though this is no longer my primary phone I would like to get it fixed. Any help is deeply appreciated.
Click to expand...
Click to collapse
When you get to recovery try hitting the menu button several times with a pause in between. If you can get in, wipe data and you will be good to go.
Sent from my Nexus 7 using xda app-developers app
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
Click to expand...
Click to collapse
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
kuboa said:
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
Click to expand...
Click to collapse
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
hold it under a bright light and try again
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
if you can get still have adb access use Hasoon's AIO Toolkit to reboot to bootloader/recovery and go from there. otherwise hold power and volume down button with the screen facing a very bright light.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
kuboa said:
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
Click to expand...
Click to collapse
just reflash superuser, i think it was left out by mistake
Aldo101t said:
just reflash superuser, i think it was left out by mistake
Click to expand...
Click to collapse
I tried that but didn't work. Anyways, that's a far less scary problem than a bricked phone, I'll figure it out. Thanks again.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
hi there.. im having the same problems. i cant access recovery and my computer wont let me access the files on my phone neither. when i boot on the phone it goes right into the bootloader and won't go anywhere else. please help! many many thanks
Bricked after attempted TrickDroid update
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Deano1889 said:
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
Click to expand...
Click to collapse
go to fastboot, use HTC all in one kit by hasoon to flash TWRP, go in twrp, Wipe everything including data, system, cache, dalvik cache, again go on HTC kit and put command of adb sideload, go on TWRP advanced menu and sideload roam. once sideload gets transferred, it will start installing and try different rom like ARHD 10.1
I can't belive it, but the bright light thing actually worked for me!
Thanks!
I was in the same situation with an HTC logo and flashing back and home keys. When I tried volume down + power under a bright light, it came back to life in bootloader. Not sure what the bright light has to do with it but glad it worked.
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
ayan15 said:
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The bright light trick is not a bug, and it has nothing to do with TWRP. It happens because HTC built in a "pocket protection" so that the phone will not reboot on its own in your pocket. The proximity sensor needs light shining on it for a hard reboot to work. (Sometime they're not sensitive enough and it takes a brighter light than you would expect)
Sent from my HTC One using XDA Premium 4 mobile app
I have seen a lot of threads on similar problems, but none of them seem to have a fix for me. So, here I am!
A few weeks back, I flashed a custom CM11 ROM to my phone, and it went through without a hitch. The phone did have a few problems, but the dev had mentioned that the ROM had a few bugs, so I didnt think much of it. The phone screen would turn off at random, and if i plugged in the phone while it was not turned on, it would get stuck at the loading screen that precede the battery animation. Like I said, I didn't make much of these.
The dev released the newest update yesterday, so I downloaded it, and when I tried to boot my phone into recovery, the s3 mini splash screen came up for a few seconds, then the phone turned off. This happened several times, even when I tried to turn it on in download mode.
I decided to use Terminal Emulator to turn on recovery, but when I tried to turn my phone on normally, the same thing happened (s3 mini splash screen, then turned off).
I saw other threads on the same matter, but they were mostly due to a pressed-in power button, or were solved with steps that didnt work out for me. Please advise!!!
polski691 said:
I have seen a lot of threads on similar problems, but none of them seem to have a fix for me. So, here I am!
A few weeks back, I flashed a custom CM11 ROM to my phone, and it went through without a hitch. The phone did have a few problems, but the dev had mentioned that the ROM had a few bugs, so I didnt think much of it. The phone screen would turn off at random, and if i plugged in the phone while it was not turned on, it would get stuck at the loading screen that precede the battery animation. Like I said, I didn't make much of these.
The dev released the newest update yesterday, so I downloaded it, and when I tried to boot my phone into recovery, the s3 mini splash screen came up for a few seconds, then the phone turned off. This happened several times, even when I tried to turn it on in download mode.
I decided to use Terminal Emulator to turn on recovery, but when I tried to turn my phone on normally, the same thing happened (s3 mini splash screen, then turned off).
I saw other threads on the same matter, but they were mostly due to a pressed-in power button, or were solved with steps that didnt work out for me. Please advise!!!
Click to expand...
Click to collapse
is it turnoff and keep restart or turnoff and never turn on ?
Ahmed.ragab said:
is it turnoff and keep restart or turnoff and never turn on ?
Click to expand...
Click to collapse
I have the same problem, since two weeks the phone was stuck on the pre-charging logo loading.
This morning the phone showed the same problem of polski, but i can boot in recovery and in download mode.
Every time i try to change something, the phone's situation worsens.
First the phone reboots 5 seconds after the system completely boots.
After a nandroid restore the phone was stuck in S3 mini logo
After that i tried another nandroid restore and it failed.
The phone keep restart, anyway.
Sorry for double-posting, anyway i tried a way to resolve and it had been successful.
I downloaded original firmware from samsung site (obiouvsly the correct one) and i flashed it with odin.
After that i re-flashed Maclaw's CM11 by odin and now the phone work well
HylianHero said:
I have the same problem, since two weeks the phone was stuck on the pre-charging logo loading.
This morning the phone showed the same problem of polski, but i can boot in recovery and in download mode.
Every time i try to change something, the phone's situation worsens.
First the phone reboots 5 seconds after the system completely boots.
After a nandroid restore the phone was stuck in S3 mini logo
After that i tried another nandroid restore and it failed.
The phone keep restart, anyway.
Click to expand...
Click to collapse
HylianHero said:
Sorry for double-posting, anyway i tried a way to resolve and it had been successful.
I downloaded original firmware from samsung site (obiouvsly the correct one) and i flashed it with odin.
After that i re-flashed Maclaw's CM11 by odin and now the phone work well
Click to expand...
Click to collapse
As u can go.to download.mode.. flashing full stock.firmware via odin will solve it
As i said
There's another problem now... the phone works well but there's no more the Samsung Splash screen but a crashed image (like static of TVs)
HylianHero said:
As i said
There's another problem now... the phone works well but there's no more the Samsung Splash screen but a crashed image (like static of TVs)
Click to expand...
Click to collapse
Flash param and image will be alright again.
tys0n said:
Flash param and image will be alright again.
Click to expand...
Click to collapse
The problem started with the GT-i8190N_param.tar flash
Ahmed.ragab said:
is it turnoff and keep restart or turnoff and never turn on ?
Click to expand...
Click to collapse
It turns off and never turns on. :\
I bought a new battery today to see if it fixes the problem, but it didnt. :\
polski691 said:
It turns off and never turns on. :\
I bought a new battery today to see if it fixes the problem, but it didnt. :\
Click to expand...
Click to collapse
if it didn't respond at all so it is a hard brick for sorry
Ahmed.ragab said:
if it didn't respond at all so it is a hard brick for sorry
Click to expand...
Click to collapse
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
polski691 said:
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
(can u access download mode if yes so try complete stock firmware via odin
polski691 said:
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
First of all do you have a Custom Recovery installed??
If you don't this won't work.
(This happened to me on my S3.
I was using pimp my ROM and upon reboot, turned of after splash screen)
My way to fix this was:
•Download another ROM (for your device) (using a PC or another Android Phone) move downloaded ROM to External SD Card
•Insert External SD card back into Galaxy S3 Android Phone (or you can move ROM file to Internal SD Card if your using a PC)
•Boot into recovery mode.
Turn phone off
Press & hold Power Button, Volume Up & Home Button.
•Factory Reset
•Flash ROM from External or Internal depending on way used.
•Reboot
•Profit
Sent from S3 Mini
Using XDA App
polski691 said:
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
Discharge battery using download mode and return to seller for refund or replacement!
My wife's phone is completely stock, I have never rooted it or anything.
A couple of days ago, she started getting a strange notification with the android icon and something called Smith with the message that it is disabled. Her phone would reboot itself a couple of times a day and now it is stuck in a boot loop. The phone has been stuck in the loop for a couple of hours now, stopping on the white android screen for a second and shutting down, rinse and repeat.
I can get into recovery by ONLY holding down the volume key, which is kind of strange. I also cant select anything in recovery.
Any help would be appreciated, she is about to kill me and switch to an iPhone.
allstarfung said:
My wife's phone is completely stock, I have never rooted it or anything.
A couple of days ago, she started getting a strange notification with the android icon and something called Smith with the message that it is disabled. Her phone would reboot itself a couple of times a day and now it is stuck in a boot loop. The phone has been stuck in the loop for a couple of hours now, stopping on the white android screen for a second and shutting down, rinse and repeat.
I can get into recovery by ONLY holding down the volume key, which is kind of strange. I also cant select anything in recovery.
Any help would be appreciated, she is about to kill me and switch to an iPhone.
Click to expand...
Click to collapse
Follow this guide - it should fix you up.
StormyNight said:
Follow this guide - it should fix you up.
Click to expand...
Click to collapse
unfortunately this doesn't apply to my situation because the phone has never been rooted
allstarfung said:
unfortunately this doesn't apply to my situation because the phone has never been rooted
Click to expand...
Click to collapse
Follow the instructions here then. Be warned though, this will wipe everything, including internal storage.
The Smith file is some file that HTC put into the ROM that expired in mid-August. Ever since then, the app shows as expired when you reboot. Nothing you can really do about it if you are not rooted, but HTC is supposedly working on a fix that they will push via OTA.
However, it shouldn't be causing the bootloops as far as I know. If a factory reset doesn't work, then running the RUU is most likely the way to go.
So ever since I updated my phone to 5.1.1 the phone doesn't work without power connected to it. When I try turn it on it just shuts back off when the google logo comes up. It only stays on if it's connected to a charger.
Today I manually flashed 6.0 and the problem is still there.
5.0 and 5.0.1 was completely fine, then 5.1 came out with this issue.
I've tried recovery mode then holding down the power button on bootloader logs and that doesn't work. It also happens in safe mode, just turns off without a power source connected to it.
Any ideas on how to fix this issue?
ShaunW50 said:
So ever since I updated my phone to 5.1.1 the phone doesn't work without power connected to it. When I try turn it on it just shuts back off when the google logo comes up. It only stays on if it's connected to a charger.
Today I manually flashed 6.0 and the problem is still there.
5.0 and 5.0.1 was completely fine, then 5.1 came out with this issue.
I've tried recovery mode then holding down the power button on bootloader logs and that doesn't work. It also happens in safe mode, just turns off without a power source connected to it.
Any ideas on how to fix this issue?
Click to expand...
Click to collapse
sounds like your battery is dead or close to it.
simms22 said:
sounds like your battery is dead or close to it.
Click to expand...
Click to collapse
I thought that as well, but it only started when 5.1 came out. 5.0 and 5.0.1 didn't have this issue. Surely it's a software issue?
ShaunW50 said:
I thought that as well, but it only started when 5.1 came out. 5.0 and 5.0.1 didn't have this issue. Surely it's a software issue?
Click to expand...
Click to collapse
most things happen at weird times, its just . my nexus 5 died 3 weeks ago. i flashed m, wanted to clean flash it again. so i wiped, and reflashed. as soon as i pressed , it went black, never to boot again. did the reflash kill it? no. it was just a coincidence.