First of, I have a problem getting into the bootloader as I've said in my post: forum . xda-developers . com / showthread.php?t=759279
I've been using Kostas244's ROM -> www . forum . xda-developers . com / showthread.php?t=554071 for a few months now, no problems until now.
What happened: The touchscreen began to not respond to my input, slowly and gradually for a few days. I clicked on a few things, something else was triggered. So I figured I only had to reboot the phone. Now I can't get even use my phone.
My phone activies: Calls, SMS, Alarm, Play Solitaire, Taking Photos. That's about it. Nothing else.
Now I can't seem to enter the bootloader (Camera Hold + Power) during startup, can't get into the system cause the slider reacts just once and then it hungs up. Freezes for a while, then after I shut down the screen and turn it on again it simply does not respond at all.
First time I could enter my security code, but then I couldn't enter my PIN code so I took out my SIM CARD - then I couldn't enter my security code and nothing seems to be working.
Right now my phone ask me to enter a code due to "several bad atempts to get into the phone" and I could only press q (whatever I would input, it simply gave me a q and then nothing) and that doesn't do me any good.
Just a few minutes ago I tried forum . xda-developers . com / showthread.php?t=636170&highlight=bricked+my+cruise&page=2 on the thread ( forum xda-developers com / showthread.php?t=636170&highlight=bricked+my+cruise&page=2 ) who seemed to have a similiar problem as mine - the touchscreen isn't working.
But I don't have Windows XP (if that's the case it's not working) and the guides seems to point that it has to be in RGB mode (bootloader) and that is not working either.
Does anyone have any ideas or solutions I could try? This just happened out of the blue, I hadn't done anything with the phone for a whole day and it just began acting like this. No damage to the phone has been made or anything out of the ordinary. So it sounds like a software problem, but I can't seem to get past it.
I use Linux 64 and Windows 7 64 if there's solution to connect to the device on either Operating Systems.
Thanks anyway.
To enter the bootloader screen press the camera button an the reset button at the bottom of your phone 'the little hole next to the usb'.
You could try hard reset press and hold both bottom buttons and reset 'you will lose your contacts sms ect' so back up using pimbackup.
If your digitizer is not working 'doesn't respond to touch' try sync your phone and install mymobiler/,then you can browse you phone and backup to sd card before hard reset.
Already tried that, as I included in my previous post about getting access to the bootloader. I can't get into the bootloader with Camera Hold + Reset. Nothing happens, it's as if the buttons don't respond correctly.
Hold down both "bottom buttons"? You mean GPS and IE buttons? Tried that too. Tried a few others. And I'm certain this worked before. Like I said in my post, nothing has happened to the phone recently - it just started acting this way. So I'm guessing it's more a software problem than a hardware problem. Since I have HARD SPL and a homecooked OS the chances of it being that is a probability.
I have nothing that needs to be backed up, so I don't need to do anything about that.
Hi
I have same problem. Screen doesn't react (only if press hard), and i can't enter bootloader and make HR.
Also, I had same problem 2 month ago. But I managed to revive it - made a lot of try of HR and one of them was successful. but now it is dead again and I don't know what to do...
Hello XDA friends. This is my first official posting on the XDA site and I'm in need of serious help.
I've noticed that intense research and development has been put into this phone. With so many rom selections available for the MT4GS I decided to try out several different roms kind of playing around. Many of the roms available were very well put together.
I decided to try out the Doubleshot MIUI v0.3 as I have used on other devices in the past and liked its customization. After installing the rom I made some adjustments in the settings to personalize my phone. Everything was working fine until I rebooted my phone and now it is hard-bricked. My device is S-Off with bootloader unlocked, and prior to installing MIUI I formatted all data, Dalvik, and system. I don't know what I did to brick my device and I can't find similar issues among others.
Issue Details:
When I have the phone powered off then hit the power button my backlight will slightly light up (very dim with no splash or image), and it will vibrate (Like on a normal boot). What else is crazy is every 37 seconds it will vibrate, and this is ongoing if I let the phone sit in that state.
If I have the phone off and plug it in a power source I get no love.
I'm unable to access HBOOT or Recovery mode, and the phone is not detected when connected to PC.
Please help me.......
that looks like a screen/digitizer problem. I don't think you're even bricked seeing as you didn't mess with any partitions according to what you did above. Also if the phone vibrates and the backlight turns on then it's still alive.
Thanks for the response. I'm sure the screen is fine. I performed the reboot when the issue first happened. This phone is driving me crazy.
wait u said you phone isn't connecting to adb right?
Did you try Fastboot?
I'm not able to bring up the HBOOT menu to enter fastboot mode.
have you tried a battery pull?
Thanks for the reply. I have tried pulling/replacing the battery and didn't have any luck. I also have two spares and the issue continues........
I can't figure it out, or figure what I did exactly to cause this.
Any other ideas?
does adb recognize it when it is plugged in?
I wanted to solve this problem on my own but after almost 6 hours I just can't figure it out. Its either totally bricked or I'm just missing something simple. I've seen many people complain about this problem but none of them seem to have had the same problem I do. Thing is I was just really starting to love the way I had the phone set up. DAMN!
I used this thread to root: (CF)
http://forum.xda-developers.com/sprint-galaxy-s5/help/q-root-galaxy-s5-sport-sm-860p-t2859473
SPRINT GALAXY S5 SPORT SM-G860P
Android 4.4
I had CW recovery installed
(wish I had more info about the software)
Here's whats happening:
START
(vibrate)
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
(Also on Screen are the logos)
Samsung Galaxy S5 Sport
Powered by Android
This stays on for about 10 seconds.
Then blank screen (2 seconds)
(vibrate)
Screen still blank (2 seconds)
REPEAT (Auto reboot and goes back to start)
Other notes:
Trying to boot into recovery (home+vol up+power) Nothing Happens
Try to power off and nothing happens.
Pulled battery, did the 30 sec and restarted no change.
I have all updated usb drivers.
Odin will not see the device because its not on long enough. (Kies didn't see it either.)
Plug into PC via usb - Nothing Happens, device doesn't even show up because its not on long enough (win 8.1 and 7)
Pull battery to get it to stop, once battery goes back in, it auto starts again.
I TRIED AS MANY SD CARD / BATTERY/USB CABLE/POWER CABLE/BATTERY PULL/BUTTON COMBINATIONS AS I COULD FIND ONLINE AND THEN SOME. No Luck with anything.
I know this isn't a "help desk" I just wanted to give as much info as possible hoping to help you help me!
Please point me in the right direction.
Thanks!
Try to hard-reset your phone. There is a button combination for that., search it over the internet.
Thanks for the reply.
Unfortunately the hard reset combo does nothing. I've tried every button combination that I have been able to find with no luck. Factory reset, hard reset, etc. etc. no luck. I've also searched for a possible "hidden" button underneath the back cover or something of the like...nothing.
hmmmm
At least, it is not hard-bricked. So there is hope.
Have you checked if it is entering the download mode? If not, then try it. You can use this mode to flash file via the PC.
Check this link
It worked! Obviously I didn't search or try as many things as I thought I did. : / I can't thank you enough! wow. Amazing!
Thread closed.
Guys,
I have a OPO 64gb which is in Dead State (Hard-bricked) currently.
It doesn't switch on. Nothing comes up on the screen after pressing Power button. Can't even go to Recovery Screen or Download Screen. No display, no logo, no vibration. I even tried it after keeping it for charging overnight.
This happened after my cousin tried to flash something (I have no idea what he was doing).
I have gone through many thread on this and various other forums which gives solution of Unbricking the phone. However none of them helped, because my case is a little different.
In all those Recovery procedures, it is mentioned to connect the phone to PC and press Vol Up + Power button. When I connect the OPO to PC, it is not detected at all. Even it doesn't show up in the Device Manager (no QHSUSB_BULK, as many mentioned). There is absolutely nothing which indicates that the phone is connected to PC. This is were I get stuck because I don't know what needs to be done from here.
Has anyone ever faced such an issue? How to I bring back the OPO back to life from this state? Is there a solution to this?
Please help!
What did you end up doing???
What did you end up doing???
I have the exact same situation though I wasn't trying to update anything, it just crashed and all the same symptoms appeared...
@SuzAnDroid
Dont worry,
If you are still facing the problem,
Then You can follow this Superb Link
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Also having same issue
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Strongo said:
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Click to expand...
Click to collapse
No, unfortunately my phone is still stuck on that exception red text (not a single green one like the one i found online).
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
The only solution I could find that could help me in the future is that 1. Phone is dead, eMMC and motherboard cannot start. 2. Since the phone could be (difficultly) tore down, the best bet is that you find a data recovery center (not Samsung since as I found out they don't do data recovery, but they simply change everything giving you a new phone basically or they change the motherboard, so deleting everything) or a data recovery specialist so that you could disassemble the phone, remove the memory, and read the content on a chip reader.
In this case maybe there's a chance to recover the simple data you have (photo, video, music, documents and something else that has a recognizable header) but probably everything else is lost.
I would be more than happy to be proven wrong since I'm not an expert but it's been 2 weeks and I received no answers.
Iztooi said:
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Click to expand...
Click to collapse
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes. Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
cooltt said:
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
Click to expand...
Click to collapse
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes.
Click to expand...
Click to collapse
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
Click to expand...
Click to collapse
The fact is that it doesn't power off and on multiple times, but just one time.
Iztooi said:
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
The fact is that it doesn't power off and on multiple times, but just one time.
Click to expand...
Click to collapse
I'm this case you'll need to use ADB and side load to flash a new bootloader.
cooltt said:
I'm this case you'll need to use ADB and side load to flash a new bootloader.
Click to expand...
Click to collapse
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Iztooi said:
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Click to expand...
Click to collapse
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
cooltt said:
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
Click to expand...
Click to collapse
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Iztooi said:
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Click to expand...
Click to collapse
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
cooltt said:
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
Click to expand...
Click to collapse
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Iztooi said:
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Click to expand...
Click to collapse
I assume youre in upload mode. Press only power button for 20 seconds
kpwnApps said:
I assume youre in upload mode. Press only power button for 20 seconds
Click to expand...
Click to collapse
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Iztooi said:
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Click to expand...
Click to collapse
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Iztooi said:
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
Click to expand...
Click to collapse
kpwnApps said:
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Click to expand...
Click to collapse
I already did that, but sadly it didn't work.
Iztooi said:
I already did that, but sadly it didn't work.
Click to expand...
Click to collapse
Then it might be an UFS hardware fault
kpwnApps said:
Then it might be an UFS hardware fault
Click to expand...
Click to collapse
I have the exact same problem. This is the closest thing I could find on the internet I could find regarding diagnosing it. Had to make an account just to reply. I was thinking it was a OS problem for the longest time, but I suspect that it may be a hardware problem after all. My s7 did this to me the morning of Jan 9. Set it down and came back to it, reboot with bootloader error, red text only, no combinations of buttons work etc. I see that two others in the thread had theirs fail around the same time as well.
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
draco18 said:
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
Click to expand...
Click to collapse
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Iztooi said:
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Click to expand...
Click to collapse
I was wondering if you installed any apps recently and how full your internal memory was. I believe my phone was around 90% full of the 32GB, had no warning symbol about how full my memory was though. Friend was saying I should of got a warning if my memory was getting near capacity. I installed F-droid recently and used it to download Adaway app. Deleted F-droid and deleted Adaway since I couldn't get Adaway to work. Never rooted my phone. I was curious if you also did anything similar to what my phone did since we're in the same boat. Otherwise the only things we share in common is we set it down and it reboot with this bootloader error.