So my otherwise trusty I9100 decided that it wanted to sleep the eternal black sleep. Yesterday it locked up and I had to remove the battery. When powered on, it asked for the password for the encrypted storage (I do not have encrypted storage that I know of). I could only power off or reboot at that point. I chose shutdown and let the phone rest for a couple of minutes. Then I started it again and then it went into eternal boot loop. I powered off by holding the power button and when that seemed to fail, I removed the battery. I tried to enter the normal boot menu (running standard firmware 4.1.2). This failed. I tried to use the volume down+home+power button and that to my relief showed the warning about installing a custom os. I proceeded and Odin started on the phone. Great I thought. I can at least flash the phone and have a phone again. I downloaded the firmware and Odin 3.0.7 and proceeded to flash. Odin 3.0.7 could detect the phone and started sending the cache image preparing instructions to the phone. This took a long time and then it timed out. The phone still showed the Odin downloading screen. I tried to restart the software on the pc, but that failed right away. I tried to restart Odin on the phone, but the phone was now completely dead. Black screen forever.
For reference, I have flashed with Odin before (long time ago) and it worked as intended. Besides, I was following the troubleshooting guide presented here on this site for the S2 and right now, I can get zero signs of life from this phone.
Seeing as my friends S2 died after 2-3 years with black screen of death and my sisters S2 died with black screen of death, also after approx 2 years and now my phone after close to 3 years, I can only suspect that Samsung has made the phone to die this fast. I only know of 2 more persons that have such a phone and their phones are not so old yet. But I guess theirs will die after 2-3 years as well. :-/
So, it was interesting having a smartphone and I liked it, but now I am back on my trusty old Nokia i6110 (has run 11 years without issues and with original battery, still lasting 3-4 days per charge).
But I'd like a new smartphone, just not a Samsung. They have burned me enough.
I just learned that the phone might be salvageable using the JTAG interface. So, any JTAG'ers around the Århus, Denmark area?
galmok said:
I just learned that the phone might be salvageable using the JTAG interface. So, any JTAG'ers around the Århus, Denmark area?
Click to expand...
Click to collapse
There's a thread called jTAG centre near you or something like that, look it up, maybe you can stike luck.
My device is like 3 years now, but it's gonna live forever, I'ma see it thru
If you have any linux (get a live cd for free everywhere) at hand post 'lsusb' into an terminal when the phone is connected. if it shows up any sign of an active usb device it might still be alive, else it truly is a jtag case
Related
TL;DR: Any way to fix/flash a Nexus 7 that reports it's in APX mode to Windows yet, that won't do anything else?
Backstory: I've had a 2012 Nexus 7 32gb since the day it came out (Oct 2012 or so?). Worked great for a year, loved it! Had AOKP on it, unlocked/rooted, used tons of apps, never a single problem. And then one day while I was using it to play music while charging it, out of the blue, it hard shut off while it was running, rebooted and shut off during boot and... never turned on again. Wouldn't indicate a charge, wouldn't turn on, couldn't get it to respond to any power or volume key presses, nothing.
I called Asus, and they agreed it needed to be repaired. I sent it to them, they sent me back the same unit, repaired, and said they swapped the mainboard out in the repair notes. Worked great, except the device was completely wiped, relocked, unrooted, and they removed my nice Stenheil screen protector.
I was without it long enough that I got used to not having it. Since it was completly back to stock, I decided instead that I would sell it when I found a good buyer (friend, etc), and buy the new 2013 Nexus 7 instead. I found a friend who wanted it a few days ago.
Today's Issue: I charged it over night last night so it was on a full charge this AM. I saw that I was still running 4.3 on it (hadn't really used it since I got it back in November), so I did the factory/official "OTA" update to 4.4.2 this AM. Went flawless, no issues, booted up fine. I updated all the apps on it, also worked fine.
I then decided to do a Factory Reset on it, (Thru Backup/Reset IN android, NOT Recovery). I went thru the confirmations/warnings, and then it said "Shutting Down..." and, it shut down. I let it sit for a few minutes, expecting it to boot back up (it never did). I tried to turn it on, nothing. I tried ALL combinations of power + volume, + charging cable in/out, etc. Everything possible, trust me, I scoured the web for new combinations and timing ,etc. No matter what, I never got ANYTHING on the display, no charging indicator, no recovery or bootloader, nothing. It's like the display is dead. The battery was fully charged this AM after being charged overnight so I know the battery wasn't even close to low. It's like it's completely dead no matter what I do.
I then tried to hook it up to my PC, which is setup for ADB etc, couldn't see it in ADB. In Device Manager though, it's showing as being in APX mode? So I tried holding power down for 10 seconds with it connected, and it DOES disconnect from windows, and a few seconds later, it shows up again, again in APX mode. Nothing ever appears on the display. Holding VOL down or all three buttons while plugging into PC never changes anything, no matter what, it ALWAYS shows in APX mode.
From what I'm reading online, this is a sign that the bootloader is missing or corrupt, and, that there isn't a fix for that unless you first backed up your crypto "blob" using Flatline (which I didn't even know about till today). I'm hoping that maybe what I've read is out of date? Is there perhaps a way to fix or flash this yet?
The whole thing makes little sense. All I did is update it, then reset it, all officially supported/normal things, on a bone stock tablet. It seems more like they didn't ACTUALLY fix it the first time it went back to them....
Help? AFAIK the tablet is now out of warranty. I just want to sell it and get the 2013 model! The tablet is in perfect shape, it's been used with a screen protector and case since day 1 - not a single scratch on the screen or case. :crying:
i'll take the silence to mean I'm screwed, right? :crying:
I don't know how, but it seems your bootloader is gone. (corrupted sector on the nand,maybe)
You can't do much without the proper blobs.
If I were you, would try to send it back to Asus. They are the only ones who can repair it.
Wow I can't believe it's been two months, but, I still have this tablet, still not working, Asus won't fix it for a reasonable price... anything changed on this in the last two months?
It seems like it should be possible to do something... maybe I'm just optimistic.
I want a 2013 Nexus 7 but it's hard to pull the trigger knowing my very lightly used gen1 model failed twice now.
There is no way to produce an universal blob and device specific blob creation is working so there is little to no reasons for further development.
You could fit a new motherboard 32gb ones are expensive but the 16gb are a lot cheaper
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
They're readily available on eBay - $35 for a used 16GB motherboard, and $50 for a 32GB board. That's how I fixed my APX bricked N7...
Whoever stumbles across my late entry, if the N7 won't boot after empty battery, no button combinations work and PC shows only APX mode - take off the back housing (it's pretty easy to do) and disconnect and reconnect the battery cable, this let me boot it up immediately...
(my N7 however was plugged over night to charge before I attempted this unplug but actually didn't show up the charging indicator and wasn't bootable, surprisingly it was charged already half when I finally could boot it up)
Sent from my OnePlus5T using XDA Labs
Apparently it is possible without having done the backup first, at least for some people.
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-blob-bin-t4083879
- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?
mufc786 said:
- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?
Click to expand...
Click to collapse
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...
abaaaabbbb63 said:
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...
Click to expand...
Click to collapse
I bought it 2nd hand from Cex (second hand retailer in UK). Luckily I still had 2 months of warranty left so they've taken it in for repairs. I don't know if they'll find out it's hard bricked (if it is), or not.
Unfortunately happened to me, too, yesterday, while rebooted my Nexus 4. It doesn't boot. The LED blink once, red, and nothing. The worst thing is it's the Service page from LG Romania website "is not available". Now I'm digging the web to find a solution
okay guys screw CeX (second hand UK retailer with 1 year warranty on ALL electronics). I took my supposed dead nexus 4 to them and the guy took it in for repairs (I'm 2 months from the end of my warranty). So they take it in and I go in 2 weeks later as they haven't updated me on the progress.
Get into the store and the guy pulls my phone out. He says because it has a crack on the back they can't book it in for repairs. I ask him why did they take it in if it wasn't going to be booked in, his reply, well its obvious no one would fix a phone with a crack in it! This guy was the goddamn manager.
So since about 2/3 weeks my phone's been dead I haven't touched it. I'll try again tomorrow but hopefully it will start working. Wish me luck.
And is it possible to hardbrick a phone because its battery dies out AND the ROM/Bootloader can't allow the device to charge?
I had an alarm app give me an alarm last night but I was busy in another app and dismissed the alarm in a way that the sound was still going. The only thing I thought to do was to do a reboot of the phone. I gave it a few minutes and when I pulled it from my pocket I noticed that it had not rebooted. So I held the power button for a few seconds and waited for that vibrate then the "Custom" screen.
Nothing.
Held the power button for about 30 seconds.
Nothing.
Good battery, at least 75% before this happened. No sweat. I have a spare battery that I know is 100%. When I put that one in, the phone immediately did a vibrate and gave me the "Custom" screen. Then dead. Power button did nothing.
Pulled the battery and upon insertion, I got that vibrate again. But this time I held Volume+ and I get that tiny blue bootloader message at the top of the screen for a half a second. Then dead. Tried it again and this time did Volume-, this time I got download mode for half a second. Then dead.
Tried all this with power plugged in and get even less. Nothing.
Connected it to a PC (OEM cord straight into the motherboard) and got nothing. No charging LED, no sound from the PC upon plugging. Nothing new showed up in Device Manager.
Did I just do the "Low Effort Brick" method just by rebooting? I have had this thing for a few years, running CWM then TWRP. Several ROMs in the past, xposed, done it all and never once even had a boot loop. Now I have a brick because I rebooted a phone that had been VERY stable for weeks (on Dan's GPE ROM)?
I am not so concerned about the device, I actually ordered a LG G4 already. What I REALLY want is the autobackup of Tasker that is in the internal storage. I know I have a TiBu of everything on the microSD and a TWRP is on there too. But both are a few days old and I have made many changes to Tasker in the past few days. Tasker updates a backup every time you leave the app, so I know I have a very recent file in there. But how do I get it?
It's not bricked. The power button on some S4's are janky. Mine did the same thing for a while. You can try smacking the power button on the corner of a desk or something but otherwise either just keep pulling the battery and trying, try opening it and cleaning the switch, or try replacing the switch.
It's hardware issue with power button. I've got the same issue with my S4. The only solution is to replace the button.
Good advice. Found a few YouTube videos that are pretty close the issue that I have. I shall do some work on this this weekend. Thanks for taking the time to respond!
Hell yeah. Effin HELL YEA. Found a few YouTube walk through videos and got down to the switch. Using my ever-awesome Simpson 260, I was able to determine that the power switch was bad. I exercised it a few dozen times and then it went open. Roughed everything back together (without screws) and got a boot.
Immediately made a TiBu of everything. I will also make a TWRP as soon as that is done. Now I have to source a power switch. I should have no problem replacing the switch. I have a fantastic solder station at work and a 20X magnifier. This shall be my crutch until the LG G4 arrives.
Thanks again for the advice. Proof again that this is a real community.
Side note: I went to AT&T to get my old Vivid back into action to replace my S4. When I mentioned that the device was rooted, they replied with some statement that my "jailbreaking" the device is what caused the failure. I asked if she knew what rooting was, and she said "yeah...jailbreaking". I asked her if she knew what an "unlocked bootloader" was and she just glazed over, mouth open. When I told her that the device has been rooted for years with no problem, she insisted that the problem happened when I "jailbroke" it.
Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.
Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.
If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.
Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.
Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
This is an out-of-the-box Verizon S7. Never tried to root it or do anything with it. Out of seemingly nowhere, it just stopped turning on today. I know it sounds weird that I haven't touched the phone and it mysteriously "just stopped working," but I swear. It was working fine about 3 weeks ago. I left it uncharged (dead) on my desk for about 2 - 3 weeks without touching it. Now it won't boot. I contacted Samsung and my phone is out of warranty by 5 months.
I downloaded Odin 3.12.7. I booted the phone into Download Mode and flashed an Android 7.0 file from this website. After flashing the phone, it started to turn on properly, but then abruptly got thrown back into a boot loop before getting to the lock screen.
What can I do? I really just need my pictures and stuff off this phone, but it would be great if there's a way to make it work like it did 3 weeks ago.
edit: nvm. battery is shot, won't hold a charge and won't boot up for some reason.
Lithium Ion batteries don't like being stored with no charge at all! It's very likely that you've killed your battery and it can no longer generate or keep the voltage at the right levels. See this article about storing Li-Ion batteries for a better understanding.
EDIT: nvm. didn't see the edit.
if you flash twrp you can mount and take files off, i believe
Fridder said:
This is an out-of-the-box Verizon S7. Never tried to root it or do anything with it. Out of seemingly nowhere, it just stopped turning on today. I know it sounds weird that I haven't touched the phone and it mysteriously "just stopped working," but I swear. It was working fine about 3 weeks ago. I left it uncharged (dead) on my desk for about 2 - 3 weeks without touching it. Now it won't boot. I contacted Samsung and my phone is out of warranty by 5 months.
I downloaded Odin 3.12.7. I booted the phone into Download Mode and flashed an Android 7.0 file from. After flashing the phone, it started to turn on properly, but then abruptly got thrown back into a boot loop before getting to the lock screen.
What can I do? I really just need my pictures and stuff off this phone, but it would be great if there's a way to make it work like it did 3 weeks ago.
edit: nvm. battery is shot, won't hold a charge and won't boot up for some reason.
Click to expand...
Click to collapse
Have you tried factory reset and wipe cache from stock recovery?