Related
Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium
But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.
sometimes my screen goes blank and I have to pull the battery and everything comes back to normal
Hello everyone. I have a Samsung Galaxy Note II (N7100) phone which will not turn on. This occurred after I attempted to enter recovery mode by pressing UP+HOME+POWER. The screen said something about an SD card (the message appeared very briefly). I removed the SD card, and found that my phone will no longer power on. I have tried putting the phone into download mode, pulling the battery, putting the phone into recovery mode, accessing the phone via ADB, all of which failed. The phone is not appearing as a USB device on my PC, and rather alarmingly, while plugged in, the charging light doesn't come on. I would try putting the SD card back in, but, rather foolishly, I wiped the card.
Is there anything that can be done for this phone, or am I going to have to return it to Samsung? I'm concerned about returning it because I had just installed a new ROM before the phone bricked itself, and so didn't get the chance to reset the custom ROM counter. If the phone doesn't turn on at all, is there any way of Samsung knowing if the phone has been modified?
hi, does anyone know the answer to this ? my N7100 recently did the same thing as well. thanks !
as u say it bricks, i think samsung cant tell whats inside, unless the counter binary still works
May be Battery died. ..charge it for few hrs and try again
scribbled from my note 2 (N7100)
Same here
WeirdEars said:
Hello everyone. I have a Samsung Galaxy Note II (N7100) phone which will not turn on. This occurred after I attempted to enter recovery mode by pressing UP+HOME+POWER. The screen said something about an SD card (the message appeared very briefly). I removed the SD card, and found that my phone will no longer power on. I have tried putting the phone into download mode, pulling the battery, putting the phone into recovery mode, accessing the phone via ADB, all of which failed. The phone is not appearing as a USB device on my PC, and rather alarmingly, while plugged in, the charging light doesn't come on. I would try putting the SD card back in, but, rather foolishly, I wiped the card.
Is there anything that can be done for this phone, or am I going to have to return it to Samsung? I'm concerned about returning it because I had just installed a new ROM before the phone bricked itself, and so didn't get the chance to reset the custom ROM counter. If the phone doesn't turn on at all, is there any way of Samsung knowing if the phone has been modified?
Click to expand...
Click to collapse
Similar has happened to mine nothing is working so ive downloaded the stock firmware and a pit file and just waiting for a jig i bought to show up. I'm hoping the jig will put it to download mode so I can re partition and upload the stock firmware. if that works I swear ill never touch it again lol. But if anyone has already solved this in a reasonably easy way please enlighten us
teat007 said:
Similar has happened to mine nothing is working so ive downloaded the stock firmware and a pit file and just waiting for a jig i bought to show up. I'm hoping the jig will put it to download mode so I can re partition and upload the stock firmware. if that works I swear ill never touch it again lol. But if anyone has already solved this in a reasonably easy way please enlighten us
Click to expand...
Click to collapse
------------------------------------
same happened with me and I also tried the JIG but in vain.
Guys I feel sorry for your phones. As a friend mentioned up, usb jigs are not puting download mode. Sad to say but should send it to a Samsung service center.
In the end, I just sent the phone to Samsung. Even though I couldn't reset the flash counter (the phone died straight after flashing), I'm hoping Samsung don't notice. I'm pretty optimistic about them not noticing; after all, the phone is completely dead, so I don't think they'll be able to tell unless they have some kind of special gadget to read the flash counter.
if they have a special device to get to a point where they can read flash counter... that would probably fix it straight up
I had this on my note 1 and there was nothing i could do. I sent it off for someone to jtag it but still noting so sold it broken for £150.
Sent from my GT-N7100 using xda premium
Very weird what appeared about the sd card? Why would that even appeared? I mean did you do something before going to recovery mode?
Sent from my GT-N7100 using xda premium
looks like sudden death Syndrome to me
please details on your kernel version build number before having bricked!
Have you been running on old FW ?
or
HAve you updated to the latest Software?
So I wanted to install a new custom ROM and I all ready had one. It wasn't the first time. So, like usual I download the files needed and put them on my phone, boot into recovery and flash them ( but I didn't factory reset or anything because with the ROM I had I didn't need to for it to work I could just fix the not responding errors) Then i go to reboot and I wait. Nothing, nothing at all. Now I try to remove the battery and try again and now none of my buttons do ANYTHING the only sign of life there is, is when I remove the battery and plug my phone to a usb cable and attempt to charge it, all that happens is a red LED comes up. It's probably due to one of the things i installed on my phone that flashes a red LED when battery is low. Please help me with this. My last resort is to give my phone to rogers for them to fix it because I still have a warranty.
Specs: S3 i1747M Rogers
I had aokp jellybean 4.3 as my ROM
I do have a nandroid but its on my phone's sd card
Thank you for your time and I hope we get this to work.
Can you get into recovery mode or download mode?
FoxTrotz said:
Can you get into recovery mode or download mode?
Click to expand...
Click to collapse
No there's litteraly nothing I can do. pressing all the buttons does absolutely nothing. Just stays black and no signs of life
bump. I need help fast with this.
Not sure exactly what you did but I hate to say its sounds hard bricked. Mine was exactly the same, with only the red light coming on for about a minute when cord was plugged in with no battery. I screwed mine up with a file I grabbed without reading properly what it was for and in my haste I installed it. After I rebooted it never came back until I got it back from warranty with a replaced control board. Im guessing they didnt even check the internal memory or they would haven known what a dumbass i was since i voided the warranty doing stuff i had done before that mistake. Glad I had made a nandroid before i pooched it so i didnt lose anything after i got it back.
Yeah after some research I found out I hardbricked it but this isn't the first time and I had a warranty for both( different phones btw )times so I guess I'll just send it out. :c
could just be out of juice, leave it on the charger for around an hour then try and go into download mode.
I have a GT-N7105 that I was copying a large file to via a USB cable. It froze up during the copy, rebooted and then was quite dead. It wouldn't get past the usual bootloader screen and attempting to get into recovery would cause it to half load the recovery screen, then freeze.
Attempting to flash it with ODIN didn't work, it kept failing. I tried a few more times and ended up with messages about "No PIT found". So I attempted to flash a PIT to it. Now it's dead. Won't turn on at all, not recognised by the PC or anything. I've tried the SD Card bootloader trick but that doesn't work either, but to be honest I'm not 100% sure what I'm doing's right. I've written the n7105_boot2.img to a 32Gb SDCard (I don't have a 2Gb one) but it doesn't boot at all.
Does anyone know if these things are JTAGable? I've read a few posts that seem to imply it is, and a few posts that seem to imply it isn't. Something about the JTAG fuse being blown open so you can't.
Before I spend a lot of time trying to find someone with a RiffBox in New Zealand (if you know someone who does, please PM ME!), is it worthwhile? Can the phone be bought back to life using a RiffBox easily enough, or is it complex? Or does RiffBox not support GT-N7105?
I realise the EMMC is probably dead on this thing anyway, even though the EMMC in the phone wasn't affected by the SDS bug. But it's also possible the PC I was using to try and ODIN the phone back into life wasn't well setup, and has just sent bad info the phone.
If it's dead, oh well. I have a lovely Nexus 6 to replace it now. But it would make a great spare phone.
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.