Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N
Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app
Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.
Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.
I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app
XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.
In case anybody comes back here, I'm just gonna drop this in.
Related
Hi guys,
I have a little problem where my phone's power button will not function in any way, long presses, short, almost embedding my thumb in it, all to no avail. This is doubly dissapointing as I have just installed the latest dexter plus patch to fix the problem. I still had the problem on the previous version and I thought a clean start may fix it. The only way I can get the screen on is to press the media play button! Which of course isn't doing anything on dexter.
Hunches:
I have been playing with a light sensor program and using a 3 second press to turn the phone off, I am only thinking this is related as when I re-installed then turned off the phone using a battery pull, that now the media gallery button will now not work at all, so that is a change.
Second, the power button is buggered. Seems unlikely as everthing feels normal, no big drops have occurred from heights, and the button is travelling in and out as usual.
I have also noticed that as soon as I re-insert a battery that the phone starts immediately, the M pops up as if it is already posting. So maybe it is stuck down?? Again, I don't think so, as the mechanism is working per usual.
If anyone can help it would be fantastic, you guys haven't let me down yet, and this thing is purring, but unfortunately I cannot use it lol. Just my luck.
Thanks in advance
another thing, still not solved
Another thing is happening, the phone screen turns on "after" pressing the power button, it may be once or a few times, and then pressing the gallery button.?!?!
Also, at random times it plays a podcast on my phone, the exact same podcast, and from the start, though the duration may be a few seconds then repeat, or it may go for ages, its quite a rude podcast too which has caused me to throw my phone under the car seat to shut it up when people have been trying to talk to me, as you can imagine its quite embarassing.
There are no services or apps running that I can find related to music, it may happen after pressing the camera button, or opening a website.
It is still going really fast though. And I have also reinstalled the light sensor program so I can turn it on and off without causing damage to the power button.
Thanks again everyone.
pisceanblue said:
Another thing is happening, the phone screen turns on "after" pressing the power button, it may be once or a few times, and then pressing the gallery button.?!?!
Click to expand...
Click to collapse
please clarify
sure, so the only way I can get the screen to turn back on, after turning off as per display power saving preferences, is by pressing the power button, maybe a couple of times, then following that up by pressing the gallery button next to the shutter button, pressing the gallery button doesn't seem to be working to turn the screen on now, but this combo is.
I hope that helped.
Cheers.
EDIT:::
The gallery button alone is working again. sorry guys.
You might just want to reflash it to stock to see if this resolves the problem.
Yeah I think I may have to.
Before I do., I was reading a post on a different forum where another person was having a similar issue. They seemed to solve the problem by using rom manager to boot to a manual restore menu where there was a button tester section, after using it the power button worked for them. I tried but after resetting it displayed a triangle graphic then rebooted.
Is there any way to do this with our open recovery program or any other utility to test the functionality or maybe reset the button or apply a patch etc.
Thanks again :-D
Sent from my XT720 using XDA App
Getting Frustrating
Alright so I followed your advice on your videos on how to reflash to stock, so of course my bootloader does not show up the same as yours on the video. I can get to the bootloader fine, using the button combo or by using quick boot > bootloader, both have the exact same result, the boot loader screens as follows:
Bootloader Fastboot mode
80.89
and that is it....
Also, my computer using rsdlite does not acknowledge the phone, not omap drivers loading etc. Followed your instructions exactly.
This is frustrating me to no end lol.
I am guessing that because I can get to the bootloader with combo no problem, that the buttons physical connections are working.. At least thats a positive.
Can I flash to stock with openrecovery? Or maybe to an earlier version of Dexters froyo? Other ideas?
Any help would be much appreciated guys, trying to use this phone at work with light sensors to turn off screen is not as easy as they say. OMG....
Thanks so much
pisceanblue said:
Bootloader Fastboot mode
80.89
Click to expand...
Click to collapse
The fastboot bootloader isn't the right one. So... if you hold volume up + camera shutter while powering on you end up in fastboot? That's really weird.
Maybe your keys have been remapped somehow? Does anyone know a chord to boot fastboot? Perhaps check to see if your USB port is clean?
Lmao
Just my luck to have a weird problem. I thought it may have been remapped so I have been trying the program buttonremap. It doesn't seem to let me do anything except stop the buttons I re assign doing anything :'(
Does anyone have a proper key mapping file that I can replace with my faulty one to hopefully fix it?
Or any other ideas?
Cheers everyone
Sent from my XT720 using XDA App
Just checked my system / user / keylayout folder. How many files are supposed to be inside, there are a few. I checked the contents of some and they seemed to be the same. Just an idea.... thanks again.
Sent from my XT720 using XDA App
Ok installed anyunlock it allows you to use any physical button to unlock the screen. It doesn't respond when the Power button is pressed, it responded fine to volume rockers, gallery and shutter though.
Anyone know if this would mean for sure its a physical problem before I crack it open and try and fix it.
Thanks guys.
Sent from my XT720 using XDA App
No one has any solutions for me? Come on guys.
Sent from my XT720 using XDA App
Breakthrough!
I am pretty sure I have fixed the problem, I tapped the phone fairly hard on its sides and back, and lo and behold after a battery pull and replacement it didn't turn itself on, I waited, nothing, so then I held the power button and it started up!!!!
But....I have another problem that happened before that, I am stuck in the boot animation that open recovery uses before going into its program (i.e. where you can load nandroid, wipe dalvik cache etc).
I was about to load a new rom, and was in open recovery, had installed it and about to do the reset and the phone turned itself off, and thats when I got the problem with the sticking boot animation.
So just to be clear, I am stuck in a boot loop, but not with the M logo, the restore logo.
I hope the power button solution can help someone else, as random as it is.
If anyone could help me get out of this boot loop without flashing stock that would be great. ( i can get to the real bootloader now btw)
Thanks again everyone.
Solved it all
Just took the sd card out and rebooted. And the power is getting better after banging it.
Thanks to all.
Sent from my XT720 using XDA App
pisceanblue said:
Solved it all
Just took the sd card out and rebooted. And the power is getting better after banging it.
Thanks to all.
Click to expand...
Click to collapse
So, is your conclusion is that the button was stuck and the banging freed it? It doesn't restick?
The Button is not perfect still. Sometimes over sensitive Occasionally it will not even work but it works most of the time. I am just wondering what cleaning solution I could use to free it some more.
It has certainly been a trying problem. Cheers for the help.
Now I need to figure out why I have this strange ghosting on the top of my screen.....
Sent from my XT720 using XDA App
Samsung Galaxy S2 Power Button Not Working
Hi Guys,
Any solution for the power button problem? Current latest Android 2.3.3 Samsung Galaxy S2 also having the same power button problem. Most of the time I can't use my power button to turn on/off the screen (wake/sleep) and there's no menu for long tap as well. Luckily it does wake when i press the only physical Samsung center button.
What i have already tried: Factory Reset, disable Power Saving Mode, Spare Part+ (apps), Screen Off and Lock (apps), and all won't help.
Is there any current updates or patches to allow the power button to work as usual?
Thank you.
take it to the samsung technical centre
Thats if you still have warranty
archer88 said:
take it to the samsung technical centre
Click to expand...
Click to collapse
won't help because this is the 3rd phone replacement from the shop with the same problem. 100% Android software problem.
OK first of all, if you can fix this you are a GENIUS!
Basically, my power button stopped working today. The phone DID work fine and the screen turned on via plugging in the charger etc as it 'jumps' it. Also, when I take my battery out and put it back in, the phone automatically turns on, which leads me to believe the power button is somehow stuck or pressed in, even though it clicks like normal when I push it... Backing this theory up in the fact that when I start in bootloader (i.e. just holding the volume UP button when I put my battery in) I can't use the volume up or down buttons to scroll through the options, which I believe is due to the power button being 'stuck'.
So in trying to fix this, I downloaded the new Cyanogenmod 10 to see if it was a software issue. I previously had 9 installed. Long story short, it didn't fix it and I decided to go back to Cyanogenmod 9.. so I went into ROM Manager and loaded the previous version of 9 that I had the zip of on my SD card. NOW when I turn my phone on it just stalls on the Cyanogenmod intro!! And I can't turn my phone on or scroll through the options in Bootloader to install another version..
ANYONE know how to fix this?
If your power button is really stuck I'd suggest taking your phone apart to an extent and taking a look at it.
Nexus S. (GSM i9020a)
Paranoid Epsilon 1.2 (1.992 - 4.1.1)
Air Kernel (JBN Stable 1 - Voodoo)
Smartassv2 (800/200)
Deep Idle (Off - Deadline)
BLX (98 - Inverted Apps)
Black Exodus (Undervolted)
309041291a said:
If your power button is really stuck I'd suggest taking your phone apart to an extent and taking a look at it.
Nexus S. (GSM i9020a)
Paranoid Epsilon 1.2 (1.992 - 4.1.1)
Air Kernel (JBN Stable 1 - Voodoo)
Smartassv2 (800/200)
Deep Idle (Off - Deadline)
BLX (98 - Inverted Apps)
Black Exodus (Undervolted)
Click to expand...
Click to collapse
The power button isn't literally stuck, that's why I put 'stuck' in quotation marks. The button still presses as per normal and the phone hasn't been damaged at all. It just seems like the button is stuck, because when I put the battery in the phone automatically switches on, whereas normally I would have to hold the power button in to do that. I did try to take the phone apart but I couldn't get the front off LOL
I have the same exact problem. Thought it was a ROM issue. But no.
I even tried to Odin but when I hold the volume buttons and plug and in USB. It just turns the phones on. Every time I plug in a cord. It will always turn on. Making it impossible to get into download mode.
So then I installed " widget rebooter " which should get me into download mode right from my home screen. But all it does is reboot. Leading me to think I can't get into download mode anymore without a jig.
IM STUMPED!!
Sent from my Nexus S using Tapatalk 2
Use fastboot from a computer. Fastboot boot recovery name of recovery.IMG will boot it up ( the image needs to be in the same directory as fastboot).
Hey, I actually have the same issue with the power button. I just ordered this off of ebay: http://www.ebay.com/itm/230794282928
It's a completely new housing so every button works. In the meantime, you can try fixing the power button by opening the phone up, removing the 6 screws, locating the power button and blowing really really hard on it, or hit it with some compressed air. If it doesn't work....the link above is a $30 fix to permanently fix this issue and you also get a new phone feel afterwards.
If the power button itself is broke that housing won't fix it.
I recently dropped my phone and my power button wouldn't work or sometimes it would work but it would act like it is stuck, so I took my phone apart and used 99% alcohol with a q-tip and cleaned the power button on the motherboard and the plastic button on the case as well as other all the other connections and let it air dry for 30 mins and reassembled and it works now.
Sent from my Nexus S
albundy2010: Can you please explain how to use fastboot? I have tried connecting my phone to Odin but it doesn't work because like BuLLeT_PrOOf_wAlleTz says, as soon as I put my battery in the phone turns on.. so I can't get into download mode even if I am pressing the two volume buttons.. And then when my phone turns on it just sticks on the Cyanogenmod 9 startup screen.
shadowx360: This looks great, but will it definintely fix the issue? I was told that I need a new 'ribbon' for the power button.. it's not the actual outer casing button itself that doesnt work.. it's the internal button that I think is connected to the motherboard..... so I'm guessing that just buying outer casing won't work?
Start the phone into the bootloader as you described in your original post. That is fastboot .
If you don't know how to issue the commands on the computer and set it up read a guide.
In a perfect world everyone with a unlocked nexus should know how to do it. But morons ( sorry its true, well not really sorry ) use one click , scripts etc.
Even of you used one of those open a command prompt in the folder ( directory) of the tool that has fastboot.exe in it and put the recovery. img ( should already be one in there) in there and issue the command.
albundy2010 said:
Start the phone into the bootloader as you described in your original post. That is fastboot .
If you don't know how to issue the commands on the computer and set it up read a guide.
In a perfect world everyone with a unlocked nexus should know how to do it. But morons ( sorry its true, well not really sorry ) use one click , scripts etc.
Even of you used one of those open a command prompt in the folder ( directory) of the tool that has fastboot.exe in it and put the recovery. img ( should already be one in there) in there and issue the command.
Click to expand...
Click to collapse
With mine I believe it's beyond the power button. I believe it's Not able to get into download mode at all. I have used commands and it just reboots.
Doesn't necessarily mean we're idiots.
Sent from my iPad using Tapatalk HD
I did not mention download mode.
albundy2010 said:
Start the phone into the bootloader as you described in your original post. That is fastboot .
If you don't know how to issue the commands on the computer and set it up read a guide.
In a perfect world everyone with a unlocked nexus should know how to do it. But morons ( sorry its true, well not really sorry ) use one click , scripts etc.
Even of you used one of those open a command prompt in the folder ( directory) of the tool that has fastboot.exe in it and put the recovery. img ( should already be one in there) in there and issue the command.
Click to expand...
Click to collapse
I have downloaded fastboot.exe and have connected my phone to the usb and have it in bootloader... how can I then use the PC to install another version of cyanogenmod so I can at least start up my phone?
FYI when i type 'fastboot devices', nothing comes up... and if, for example, i typoe 'fastboot reboot', it sais <waiting for device>, but no action or prompt appears on my phone.. it just stays in bootloader..
You don't have the drivers installed. Read a guide on how to set up fastboot / install the SDK
albundy2010 said:
You don't have the drivers installed. Read a guide on how to set up fastboot / install the SDK
Click to expand...
Click to collapse
It gets tiring repeating the same stuff over and over, doesn't it? There's at least 1 thread regarding a broken screen or power button each freaking week and yet nobody but the people helping seem to be able to use the search function.
polobunny said:
It gets tiring repeating the same stuff over and over, doesn't it? There's at least 1 thread regarding a broken screen or power button each freaking week and yet nobody but the people helping seem to be able to use the search function.
Click to expand...
Click to collapse
Thanks for the help polobunny, really appreciate it.
PS I have installed the drivers, as far as I can see. I have "Android Composite ADB Interface" in device manager, BUT it only shows up when I start my phone and connect, NOT when I start in fastboot mode. Anyone know a way around this.
FYI I am searcing for other threads on this one, but have had no luck so far.
I have reinstalled the driver from http://dottech.org/android/26188/us...rs-for-windows-for-all-android-phones/#google
bump. If anyone could help it would be much appreciated.
Notice how nobody replied after your stupid comment quoting polobunny?
There is a reason for that..... bump all you want. Good luck getting anybody to help
albundy2010 said:
Notice how nobody replied after your stupid comment quoting polobunny?
There is a reason for that..... bump all you want. Good luck getting anybody to help
Click to expand...
Click to collapse
Why was my comment stupid? Polobunny was the one mocking the person in need of help, assuming he hadn't tried searching google/forums first. There is no need for a reply like that.
you should be able to manually boot into recovery, bootloader and download modes. If your phone is powering on when the battery is inserted, it means there is a positive signal going through the power button to complete the circuit, in some way. With that said, let's assume you inserting the battery is the moment you would hypothetically be pressing the button if it worked. So in this individual case of the battery insertion acting as a power button depressing, it should be possible to get into any one of the modes desired by keeping any additional buttons depressed while inserting the battery.
In other words, to get into download mode press the vol up+down buttons at the exact same time the battery is inserted. it should work. My sister's evo4g had the exact same symptoms your phone does, and it worked for hers. I was easily able to boot into the bootloader, as well as recovery by following the steps I mentioned, and since it was a touch-based recovery, I was still able to flash/backup/restore, etc...I had full control over recovery, and everything worked just fine.
on second thought, download mode probably won't work with our device since you have to release the power button or it will fully boot....but fastboot and recovery should definitely work!!
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
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.
Good day, this would be a pretty lengthy post. I'd like to describe my experience clearly since I don't know what I possibly skipped over as I am very positive that my efforts have been correct basing on prior XDA forums. I even made this account solely for posting this to ask for help formally along with archiving this problem I'm having for those having a similar experience.
I've been working on my mom's phone this whole day and there are fruits of my current hard work. I am immensely stressed and despairing with my situation.
The Problems
Infinite boot looping
Can't access the recovery menu (power, volume+, even with home button)
Can access the ODIN / Download menu
Can't turn off either (holding down power button has no effect)
What I've done so far
I read XDA forums about similar experiences. Can't really access the recovery menu so I've factory reset.
We live in the Philippines and this phone is open line, so I went with those requirements while searching stock ROMs.
I downloaded the stock ROMs of the phone model via galaxyfirmware.com which was positively shared in the forums.
Did trial and error with it and eventually got the right one. I have formed a level of understanding with the filenames and eventually knew which is compatible.
Used Odin3 to Flash the BL, AP, CP, CSC, and even go Nand Erase and got the PIT file inside the CSC (Opened it using winrar)
The flashing is actually successful and quite fast to be honest.
The phone reboots itself and shows that it is still sadly boot looping.
Also, despite the several files used for the Flash, still can't access the Recovery Menu.
With that said, I have also tried using Frija which automatically downloaded the stock ROMs based on the model name and CSC type. Placed it in ODIN again and no changes, still boot looping.
I also can't put the TWRP I got here because of the FRP Lock, which can be undone via the settings of the phone. But since it's boot looping, I can't really do much about installing a custom ROM.
Currently, my dad is letting the phone drain its battery, since we can't really turn it off. The phone model doesn't have easily detachable battery as well, unlike the old days.
For some additional notes of what happened prior to this incident
My mom was just playing with her phone as her usual days went on. That day, she installed a new hotel-themed game she saw on Google Play. As I assume that it's from the app itself and not on some shady apk website, I saw no problem with it and didn't think it was the cause of all this. I went with the theory anyway and with the flashing, using CSC instead of HOME_CSC (which apparently saves the existing data on the phone from wiping), and even used the Nand Erase in the end. It's still stuck at boot looping.
I would appreciate anyone's reply to this discussion. I am truly desperate to fix this for my mom. If worse comes to it, I'll save money to buy her a brand-new phone.
You don't have a working android, so you won't remove the RFP. TWRP will not help you with this.
The symptoms you describe indicate a defective power button.
You manage to enter download mode because the power button is constantly on.
Because of the constantly on power button, you have no way to turn off the phone. Bootloop can also be the result of a constantly on power button.
To sum up, you should fix the power button.
1. The easiest way is to blow with compressed air and press the edge of the button with your fingernail, rapidly releasing the pressure. Perhaps the fuzz has blocked the button. Unfortunately, this rarely works.
2. Take the phone to a local service center.
Hi ze7zez! Me and my dad greatly appreciates your insight and we were definitely enlightened on this angle.
We didn't really think that the power button was stucked pressed on because you can clicking sounds when you press on it. The phone never had problems with the buttons along the 6 years it accompanied us, perhaps its age does start to show.
We're going to look into it tomorrow. Thank you very much! You gave us the idea that it may be shorted inside or some sort. Thank you again!
A bit of update.
I pried open only the back case of the phone so I can see and clean up the power button. I used tools specifically for it and made no damage on the phone during the process.
We couldn't really see anything busted from there. The buttons on the circuit still do the neat clicking sounds on it. Battery still looks the same.
Testing out the theory that the power button was stuck on:
We tried to only press and hold the volume down and power button. It didn't go to the download menu. We needed to press down all three together to access it. It is confusing since we believe it would be a power button issue too, as the phone instantly turns on by itself when plugged to a power source (it's completely drained by now and we still can't turn it off manually)
Perhaps it's an internal circuit problem with the power button? It's confusing with the fact we still have to press on it to access the ODIN menu if it was like "on" the entire time it's looping.
Thank you in advance for further insights.
Try restarting by pressing home, power and volume up all at once.
Hi Pranav2406,
I have tried that as well in order to access the Recovery menu to factory reset, but no luck.
We have given up on repairing the phone and went out yesterday to buy a new one in a rush.
We will still send this broken phone to a repairman.
If he fixes it, I'd ask what he did on it so I can post an update on this problem as well.
It's better to let the expert troubleshoot it.
I do suspect the problem in the phone's hardware. I'm pretty confident with all the stock ROM flashing I've done so it's not a software problem.
Thank again for everyone's insights.
Perhaps this case is too much for an amateur to fix.