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.
Related
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!!
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.
Hi. My wife has managed to kill the screen on her phone. The phone is running TWRP 2.6.0.0, CM10.1.2, etc.
The phone turns on, gets messages, makes sound. It just doesn't display anything.
The phone is locked with a PIN. I know the pin, but I can't enter it.
I would like to get some ideas on how I could grab the stuff off of the internal SD card.
I do have a windows box that has all of the appropriate drivers loaded.
Any ideas?
Much less important is that I would like to flash it back to stock. I am sending it back to verizon in a few days...
Thanks in advance!
t1n0m3n said:
Hi. My wife has managed to kill the screen on her phone. The phone is running TWRP 2.6.0.0, CM10.1.2, etc.
The phone turns on, gets messages, makes sound. It just doesn't display anything.
The phone is locked with a PIN. I know the pin, but I can't enter it.
I would like to get some ideas on how I could grab the stuff off of the internal SD card.
I do have a windows box that has all of the appropriate drivers loaded.
Any ideas?
Much less important is that I would like to flash it back to stock. I am sending it back to verizon in a few days...
Thanks in advance!
Click to expand...
Click to collapse
You can pull the stuff off of your phone just by hooking it up to your pc, just mount it as a disk drive.
As far as returning to stock, just reboot the phone into download mode and use odin. Odin won't recognize your phone unless it's in download mode, and you really don't need to see anything on the screen as long as odin passes.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You can pull the stuff off of your phone just by hooking it up to your pc, just mount it as a disk drive.
Click to expand...
Click to collapse
I have a pin set, so unfortunately it is not that easy (you must enter the pin to be able to copy files.)
I was able to get most of the stuff off of the phone by utilizing the boot up time (time NOT protected by a pin) to copy the files off. Seems like a glaring security hole to me... However, I don't want to look a gift horse in the mouth... hehe
It took several tries to get the data off and erased.
BadUsername said:
As far as returning to stock, just reboot the phone into download mode and use odin. Odin won't recognize your phone unless it's in download mode, and you really don't need to see anything on the screen as long as odin passes.
Click to expand...
Click to collapse
I have tried and tried to get the phone into download mode. Given what I am running, what are the exact steps with timings?
Pull battery, hold down vol-down, hold down home, press power for 2 seconds. Release power and then home/vol-down. Then after a few seconds press the up arrow?
If I hold down the power until it vibrates, have I gone too far?
I have tried to follow some youtube videos, but I can't seem to get it into d/l mode. I have odin open to tell me when I get it there. The PC that I am using is the same one that I used to root it, so it has the download mode drivers and such already loaded.
I may have to boot the phone up fully and see if I can play around with fastboot/adb.
Hahaha! Right after writing the previous post, I followed my own instructions, waited for the vibrate, released the keys as described, waited about 5 seconds, pressed the up arrow, it vibrated again and voila! Download mode in odin.
Thanks! I am all set now.
hi every body!
I have an original shield tablet, also it effected by kill switch.
I try to delete the TegraOTA.apk by following the instruction of @Bogdacutu http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489 then it's ok for a month.
But the trouble is when I change the IMEI (successfull) then update OTA3.1.1 via recovery. At this time, any thing also ok, but I did't delete TegraOTA.apk again, then turn on wifi for try to get OTA4.0 directly. unfortunately the tablet was shutting down after one minutes, then automatically boot to recovery before change to black screen . I understood that skill switch is activated!!! Although IMEI different !
Now when connect to PC, it become a APX device, in details http://forum.xda-developers.com/wiki/Nvflash
I try for some of solution but all of them not work. Also solution of @carlompms
good evening,
I received my recall tablet yesterday, before connecting the new one, I installed a new rom, for now I have 2 tables to work.
in the process I do not know what I did my tablet brick in apx mode.
for exit apx mode I connected to the PC, press power button until you hear the disconnect sound on pc(tablet turn off)
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
It may work for you too
Click to expand...
Click to collapse
Then if @Thepiewarrior, if you can read this post, please instruct for me that, how can you clear your trouble before: http://forum.xda-developers.com/shield-tablet/help/unlocked-bootloader-rooting-shield-t2995472 tks.
So, after my trouble, every one should remember that, must be deleted the TegraOTA.apk before go to online, then maybe all of solution try to change IMEI may be should't work.
Now, I waiting for some of solution from the expert (such as nvflash...), maybe there're some of member like me...
I've tried flashing patched boot.img file from the December update with the january rom, because patched boot.img file from january update wasn't working. The phone rebooted twice, displayed a message that the phone failed to boot and gave me options to either restart and try again or factory reset. I chose restart and the phone is since then bricked. Black screen, occasionally if i hold some buttons it flashes faintly but thats all. If i connect it to a pc, it is able to connect after holding some buttons for 2-3 seconds as a COM device, but then it disconnects again.
Also apparently i forgot that p7p was different and did the whole thing with boot.img instead of init_boot.img.
iplux said:
I've tried flashing patched boot.img file from the December update with the january rom, because patched boot.img file from january update wasn't working. The phone rebooted twice, displayed a message that the phone failed to boot and gave me options to either restart and try again or factory reset. I chose restart and the phone is since then bricked. Black screen, occasionally if i hold some buttons it flashes faintly but thats all. If i connect it to a pc, it is able to connect after holding some buttons for 2-3 seconds as a COM device, but then it disconnects again.
Also apparently i forgot that p7p was different and did the whole thing with boot.img instead of init_boot.img.
Click to expand...
Click to collapse
Is it out of battery?
mackdacre said:
Is it out of battery?
Click to expand...
Click to collapse
sadly no, around 60-80% maybe
hello have you tried pixel flasher?
jejemc said:
hello have you tried pixel flasher?
Click to expand...
Click to collapse
i will try now, but i dont think it'll work since the pc doesn't recognize the phone. i can make the phone somehow connect to the pc for 2 secs, but it connects as COM device and instantly disconnects after that.
Edit: it did not work
and holding the power button and volume up or down for a while does nothing?
jejemc said:
and holding the power button and volume up or down for a while does nothing?
Click to expand...
Click to collapse
correct. power + vol up, power + vol down, all 3 buttons pressed at the same time - nothing, all nothing. I'm able to make the screen for a brief second if i connect the phone to charge and press all 3 buttons or volume down + power, but that's all.
iplux said:
correct. power + vol up, power + vol down, all 3 buttons pressed at the same time - nothing, all nothing. I'm able to make the screen for a brief second if i connect the phone to charge and press all 3 buttons or volume down + power, but that's all.
Click to expand...
Click to collapse
alas it means sending it sav I don't see what else to do.
jejemc said:
alas it means sending it sav I don't see what else to do.
Click to expand...
Click to collapse
small update, i just noticed that the phone is slightly warm, so its definitely on and doing something in the background with the screen completely off. I will give it a night to completely discharge and see if i can get it to show literally anything on the screen. If not, i gotta think of a way to ship it to the UK so it can get fixed, because i'm in a non supported region sadly.
Have you tried holding down the power button for 15 seconds?
febo17 said:
Have you tried holding down the power button for 15 seconds?
Click to expand...
Click to collapse
yup, sometimes that makes the screen flash for a split second and then nothing. tried pretty much any combination for up to 30 secs. sometimes its a single screen flash, sometimes it flashes twice. It's barely visible.
iplux said:
yup, sometimes that makes the screen flash for a split second and then nothing. tried pretty much any combination for up to 30 secs. sometimes its a single screen flash, sometimes it flashes twice. It's barely visible.
Click to expand...
Click to collapse
Just to see if I understand better, so the phone is on but the screen doesn't work as it should?
Try it even longer than 30 seconds (up to maybe 60 seconds) , I also had some problem with my P7P stuck and needed to push it really long
febo17 said:
Just to see if I understand better, so the phone is on but the screen doesn't work as it should?
Click to expand...
Click to collapse
i was on december android update with magisk installed. i tried today to install january update today - i patched the boot.img file (yes, i know it should've been init_boot.img), replaced the original boot file with the patched one on my pc and flashed the new january rom with "-w" parameter removed. That however didn't work (obvious reasons), i had no root. I then decided that the new boot.img file from the january update might have some issues , and decided to flash the january update with replaced boot.img patched from december update (again with -w parameter removed). The phone took it all, then the google logo popped up... after a few seconds it restarted and the google logo popped up again... it once again didnt boot, and restarted, but after the 3rd restart i was greeted with a message from the bootloader (i assume) that the system failed to load twice, and i was presented with 2 options - "restart and try again" or "factory reset the system". I chose restart, and the screen went black and that was all. (it was only after all of this happened when i realized that everything happened because i was patching the boot.img instead of init_boot.img).
Now the screen is black, no matter which button combination i am trying. Sometimes the screen flashes once or twice when i hold some buttons, but that aside- nothing. I assume the phone is still doing something in the background, because if i leave it on my bed sheets and touch it after awhile, the back is a bit warm, so obviously something is working, but im certain its not the OS.
iplux said:
i was on december android update with magisk installed. i tried today to install january update today - i patched the boot.img file (yes, i know it should've been init_boot.img), replaced the original boot file with the patched one on my pc and flashed the new january rom with "-w" parameter removed. That however didn't work (obvious reasons), i had no root. I then decided that the new boot.img file from the january update might have some issues , and decided to flash the january update with replaced boot.img patched from december update (again with -w parameter removed). The phone took it all, then the google logo popped up... after a few seconds it restarted and the google logo popped up again... it once again didnt boot, and restarted, but after the 3rd restart i was greeted with a message from the bootloader (i assume) that the system failed to load twice, and i was presented with 2 options - "restart and try again" or "factory reset the system". I chose restart, and the screen went black and that was all. (it was only after all of this happened when i realized that everything happened because i was patching the boot.img instead of init_boot.img).
Now the screen is black, no matter which button combination i am trying. Sometimes the screen flashes once or twice when i hold some buttons, but that aside- nothing. I assume the phone is still doing something in the background, because if i leave it on my bed sheets and touch it after awhile, the back is a bit warm, so obviously something is working, but im certain its not the OS.
Click to expand...
Click to collapse
I hope you solve it, good luck and stay tuned
Since this is a very new device, I suggest contacting Google for warranty repair, because that will be much easier than trying to diagnose what works and what doesn't, as well as trying to recover the device. You have a warranty; use it.
oko17 said:
Try it even longer than 30 seconds (up to maybe 60 seconds) , I also had some problem with my P7P stuck and needed to push it really long
Click to expand...
Click to collapse
just tried:
pwr
pwr + vol up
pwr + vol down
pwr + vol up + vol down
each for more than a minute, no response.
V0latyle said:
Since this is a very new device, I suggest contacting Google for warranty repair, because that will be much easier than trying to diagnose what works and what doesn't, as well as trying to recover the device. You have a warranty; use it.
Click to expand...
Click to collapse
I most likely will, i just don't want to because im in Bulgaria (a country where they dont sell the phone) which means i have to find a way to send the phone to the UK, and they will probably refuse to ship it back.
iplux said:
I most likely will, i just don't want to because im in Bulgaria (a country where they dont sell the phone) which means i have to find a way to send the phone to the UK, and they will probably refuse to ship it back.
Click to expand...
Click to collapse
Ah. Well...without the screen working, there isn't much you can do, beyond seek repair in your own country. If the screen isn't working, it's usually due to either of 2 reasons, both of which require specialty repair:
The screen and/or display controller are defective and must be replaced
The bootloader is corrupted and the mainboard must be replaced
The tools required to rescue a device with a corrupted bootloader are not publicly available, unfortunately.
This is kinda crazy....
this is probably the first time/instance I've seen where tripping up the init_boot partition (with the boot.img used instead) caused this bad of a problem! Since the Pixel 7's changed things to init_boot, there have been very many people that have gotten tripped up flashing the boot.img to it, but it usually just results as a bootloop and a simple reflashing of the stock init_boot properly fixes things!
Are you sure you tried completely draining the battery? A hard reset can sometimes do wonders...
If Google doesn't "play ball", I'm sure you could find some 3rd party repair company/shop that would -- of course this will also cost money though...
Hopefully it works out for you OP!