Hey,
Yesterday I rebooted my i9023 and it won't start anymore. I pulled the battery because I forgot to start in bootloader mode, and I think I might've done that while the bootloader was starting up. I assume the bootloader is corrupted, or something. Buttons don't react anymore, nothing is displayed on-screen when charging, can't get into bootloader or download mode. I've tried all the things I could find, including this, but no dice.
I'm gonna make myself a USB JIG tomorrow and try to get it into download mode, but before that,is there something else I could try?
You can't even boot into fastboot mode? Even if its a black screen did you check if the computer detected it?
You can try the typical method of getting into download mode: hold vol+ and - and plug in the usb, not sure if it works that way with the Nexus. I see i9023 odin images available at sammobile.
Sent from my SGH-T959
eksasol said:
You can't even boot into fastboot mode? Even if its a black screen did you check if the computer detected it?
You can try the typical method of getting into download mode: hold vol+ and - and plug in the usb, not sure if it works that way with the Nexus. I see i9023 odin images available at sammobile.
Sent from my SGH-T959
Click to expand...
Click to collapse
Nope, can't boot it into anything and the pc doesn't detect it.
Sadly another confirmation that pulling battery to save seconds is a bad idea, happened some people before. Hope you can save your phone.
Well, I hope the JIT works. Otherwise, it's off to warranty, and hopefully they can fix it....It'd be sad to have to get a new phone...really really like this one.
Don't you worry. Just send it on warranty and they will replace your motherboard. I did exactly the same thing, pulled my battery to save some seconds. I sent my phone to repair, they took care of it in 10 days
Sent from my Nexus S using xda premium
nexususer1 said:
Don't you worry. Just send it on warranty and they will replace your motherboard. I did exactly the same thing, pulled my battery to save some seconds. I sent my phone to repair, they took care of it in 10 days
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Is there a chance to recover the data? I don't have much on it, but I have photos I haven't pulled.
That was my biggest concern. I'm afraid you'll loose all data, just as I have lost mine. Some (or all) of your photos might have been autosent to your gmail account. I managed to restore only some of those photos. Not all of them have been sent to my google account.
Sent from my Nexus S using xda premium
this happened to me twice before ,i fix it by ,using adb cmd and rebuilding recovery image ,it works
james300 said:
this happened to me twice before ,i fix it by ,using adb cmd and rebuilding recovery image ,it works
Click to expand...
Click to collapse
Yes, but your computer was able to detect it, if you could do that. Mine is literally a brick right now. Computer doesn't see it and it doesn't start at all. I'll try the JIG later, and if not, I'll send it to warranty and hope for the best
JIG didn't work. Didn't react at all....I'm sending it to warranty...
Related
Hey I'm in need of some serious help. My power button no longer works. It's as thought the phone thinks its constantly being held down. (Put battery in phone boots up by itself). I'm pretty comfortable with flashing roms etc and I need to get the bootloader locked for my warranty. I've tried multiple ways (I've done it in the past for friends). The 'fastboot oem lock' in fastboot via cmd doesnt work. It appears to be due to the power button being held down. It wont progress any further. It is not physically jammed (trust me ive tried fidgeting with it lemme tell you). I'm at a loss. Any ideas?
Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
Have you tried taking the phone apart to see what could be holding the power sours down?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all
Same thing happened to me and I sent it in for warranty with the bootloader unlocked. Samsung fixed it and no charge.
garu12 said:
I thought about it but it appears perfect. Looks and feels like it normally does. That's why at first I thought it was software related. Nope alas it was not. I tried pulling it with tweasers and there is no response at all
Click to expand...
Click to collapse
Dang. I hope u can fix it.
Sent from my Xoom using xda premium
Thanks for the replies. It's impossible to relock in this state! I did manage to unroot and install a stock rom so at least it's gonna look somewhat legit when I bring it in. Going to the Samsung repair center tomorrow (there is one not far from me so I dont need to send it). I'll let you know how it goes. Wish me luck!!
So I went in today to the Samsung repair center and 2 hours later my Nexus is good as new . Pretty classy of them. That's really good service. They didnt even question the unlocked bootloader and it was covered by the warranty. This makes me want to stick with Samsung. When my Nexus One power button died it took like 4 weeks to get it back
Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App
I have an entirely different issue but it involves me sending in my phone to samsung with an unlocked bootloader. My phone won't boot past the google screen and I can't relock the boot loader via adb. I've already sent the phone but didn't mention anything about it being rooted when I called customer service. Think there's a good chance they'll fix it no questions asked?
bradmikd said:
Does anyone know how to force my Nexus s into recovery? Its stuck in boot screen
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)
garu12 said:
In CMD if you have adb installed type "adb reboot bootloader"
It will get you to fastboot and then select recovery. Or you can just hold the volume up and power on the phone (I'm assuming that doesnt work)
Click to expand...
Click to collapse
or just adb reboot recovery
Hi All
Hoping someone can tell me if I've completely killed my phone. It was working absolutely fine with no problems whatsoever until earlier today when it froze. Without looking around at what to do I just held down Vol + & Vol - & power. This restarted the phone and it went through the T-Mobile logo and then just sat there. I then took out the battery, put it back in and held vol - and hit power, got into the clockworkmod menu and used the recovery option to wipe then restore an earlier backup, this all seemed to go fine and I used the power off option to restart the phone.
Nowwww though it just vibrates 7 times and stops, if I then pull the battery and replace it and hit power it vibrates 7 times again and then nothing unless I pull the battery again.
Am I screwed?
The phone is S-Off and had clockworkmod installed. Has the clockworkmod boot loader thingy some how been damaged? Anything I can do?
Appreciate any advice. Thanks
can you get into recovery? if so try wiping everything and then doing a fresh install of something
Sent from my Desire HD using XDA App
dont keep pulling the battery if you dont already have emmc failure you will soon if you continue to pull the battery!
Yea I didn't realise pulling the battery was that bad. I haven't done it since reading this forum. But no I can't get in to recovery any more since that time I wiped everything and restored a backup. Since then it just vibrates 7 times when I push the power button and that's all.
can it connext to adb? if so, id try flashing an ruu via fastboot. that will set everything back to stock. then you can reroot and flash a rom, and id get rid of that backup
Sent from my Desire HD using XDA App
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
rlzzzz said:
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
Click to expand...
Click to collapse
theres tons of guides but if you give me a few minutes ill upload a auto installer for you, so then you just have to add the path in
Sent from my Desire HD using XDA App
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
rlzzzz said:
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
Click to expand...
Click to collapse
it could of, and its worth a shot, it might be recognized. just get adb working, and install the drivers. plug the phone into your computer, and wait a minute or 2 and the screen should turn on but be black. then just boot into the bootloader and flash the ruu via fastboot
Sent from my Desire HD using XDA App
So I installed Java JDK, then Android SDK, then downloaded the HTC adb drivers but it says to install the drivers plug in your phone and wait for Windows to detect it... which is as far as I can go because Windows doesn't detect the phone.
I don't even seem to be able to reset the phone by holding Vol + & Vol - & power at the same time. It's not looking good.
In fact you say about the phone going to a black screen, it did do this after I initially restored the image. But it was just after that that I pulled the battery and now it doesn't do that anymore.
I assume basically what has happened then is first some thing froze and corrupted my normal install, so to fix this I tried the restore and the restore image somehow overwrote clockworkmod but at this point the phone was still recoverable via adb? but then I pulled the battery and now it's definately dead?
Seems like an unfortunate string of events but at least I know now to avoid pulling the battery next time! Thanks for all your help stumpyz9 and djisgod, I don't suppose you know why pulling the battery can so easily kill the phone?
Btw if anyone would like to jump in and make my day by saying nooo everything is fine here is a quick fix please feel free
my only guess of why pulling the battery killed it is when you where restoring it and then pulled the battery, it was restoring something very essential to even turning the phone on. i dont know why windows wouldnt detect your phone, it has derected my DHD even in the worst scenarios. and were you saying the drivers wanted you to hook the phone to the computer? if so dont and try to continue installation, because if you can get it hooked up to your computer and have adb recognize it, then tyere is a very good chance you can recover it. if not, then im sorry to say you have yourself a very pretty paper weight. if it is a paper weight, id say maybe check to see if a dev could use it or basically part it out on ebay and sell the lcd, digitizer, housing, camera and you can probably make some of your money back.
Sent from my Desire HD using XDA App
The ADB HTC drivers I downloaded are not an installer file, you need to plug in the phone so Windows will recognise a new device and ask you to select the location of the drivers but I can't because it doesn't detect the phone being plugged in at all.
I've also been reading around a bit more and found a thread about a fried eMMC chip. I was actually getting the same errors they mention in that thread when I did the restore from clockworkmod.
"E:Can't open /cache/recovery/log" etc etc
dont use that, install htc sync, then plug the phone in and tell me if that works
Sent from my Desire HD using XDA App
Yea I just gave that a go after reading someones adb guide and even with HTC sync installed when I run "adb devices" it lists nothing.
It's strange I thought once I had clockworkmod installed nothing could go wrong because I would always be able to restore from an old backup. I always assumed that clockworkmod would be sat on the boot partition and never touched even when restoring a backup. I can't understand how it went so wrong lol.
Although right now the phone seems so far gone maybe I could get away with a warranty repair as they won't be able to tell it was S-OFF.
yah if all of the chip has been fried and it wont power on, i think that would be your best bet, seeing as they probably wouldnt be able to tell.
Sent from my Desire HD using XDA App
Ok well thanks for your patience I appreciate your help.
rlzzzz said:
Ok well thanks for your patience I appreciate your help.
Click to expand...
Click to collapse
no prob, alwsys like to help out when i can
Sent from my Desire HD using XDA App
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?
Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)
It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.
If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!
With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk
I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)
I flashed a Jellybean touchwiz rom for Verizon GS3, and went to reboot and now nothing, zero zip nada. No charging led light, no way to get into recovery and no response.
Anything I can do?
what happens when you do vol up + home+power button?
Absolutely nothing. I tried to get back into the recovery to see if I could restore my backup and nope.
did you try leave it pluged in for 30mins ?
does it vibrate once when you try to turn it on?
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
NickTheMajin said:
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
Click to expand...
Click to collapse
leave it plugged in for a while to make sure its not drained battery
do you have a usb jig?
I don't have a USB jig but this is possibly good news. I removed the battery and SD card and plugged it into my computer and it tried to install drivers (failed but tried) and the led light comes on red.
if your gettin led now you more then likely need to let it charge
It doesn't give me the led with the battery in
Plug it into a wall charger for at least 30 or even better if you can get a battery from someone.
Sent from my sexy white Eclipsed galaxy S3
I think its gone still nothing.
red led means qualcomm download mode. sounds dead to me
Yeah, haha. I saw it and mentally prepared myself for it. Literally just got the phone today so Verizon had no qualms with just sending me a new phone. Guess I'm reactivating my Rezound in the meantime. Thanks for the help guys.
you know
I am surprised. That also happened to me the first time i flashed that very same rom (touchwiz) with twrp . I have done this so many times , i literarily can flash a rom on the way to work .
I was in shock , i still dont know how the heck can i flash a rom and brick .
I plugged mine into windows and i got the device manager driver error from hell . and my phone never came back up again
I stayed away form twrp and touchwiz and i still cant possibly comprehend how a simple rom flash can brick my phone .
Which ROM did you flash?
Sent from my SCH-I535 using xda premium
you could probably send it to get Jtag'ed for around $60 if your warranty is invalid (ie used device)
You just hard bricked it. I did the same thing. Check here - post 5 shows the same symptoms :http://forum.xda-developers.com/showthread.php?t=1770341
And here: http://forum.xda-developers.com/showthread.php?t=1791721
I was pushing a copy of root66 that I hadn't md5'd. Took a JTAG to bring me back (twice) .
Sent from my SCH-I535 using xda app-developers app
So, in the future, md5 checksum absolutely everything since I'm assuming now that that is why this happened? (Since I made doubly sure I was flashing a rom for my phone).
If you still have the file you downloaded, you can check it. That would answer that question. If it checks out fine, then we have to look elsewhere for the problem.
BTW, MobileTechVideos.com can bring you back - based on my experience with them, I highly recommend.
Sent from my SCH-I535 using xda app-developers app
Please share exactly what you did so others can benefit from your unfortunate experience.
What ROM did you flash?
Did you use ODIN or a recovery?
If recovery, which one - CWM or TWRP?
Was there any unusual condition you can think of ... low battery, USB connected to computer or to charger, etc?
Ok so, I just did a trade on Craigslist recently and got an S3 from Verizon, clean ESN and all, it just had a cracked screen. Well the guy had already bought a replacement he just didn't know how to do it. Did the trade, got home and completed the screen repair. Works great, but here are my problems....
1. Phone is PIN locked and I don't know it and he can't get a hold of the guy he got it from.
2. It will not boot into anything but normal, no Download mode, no Recovery, nothing.
3. Windows doesn't recognize it. At one point in my 100+ times of connecting and disconnecting it, it did recognize it and was going to install the drivers for it and then it said device unplugged, which it hadn't been.
So now I come to the great world of XDA and see if we can't solve this issue together. Anyone have any ideas? I have tried 4 different USB cables as well. All of which work with my current S3.
Thanks
So no one knows anything eh?
Sent from my SGH-T959 using xda app-developers app
You should be able to pull battery, replace, and force into download mode. I haven't heard of a phone that wouldn't go into download mode that would boot up. Anyway, after flashing with Odin, the pin should disappear.
HHF2 said:
You should be able to pull battery, replace, and force into download mode. I haven't heard of a phone that wouldn't go into download mode that would boot up. Anyway, after flashing with Odin, the pin should disappear.
Click to expand...
Click to collapse
Yea man I have tried all that. I have tried every kind of way to get into download mode, to no avail. Pretty frustrating really! I even reformatted my computer to see if it might be that, but nope.
Still hoping...
Ok so it is sitting in DOWNLOAD mode right now but Windows still doesn't recognize it, meaning ODIN doesn't see it either!! Any help would be greatly appreciated!! I don't know what I did, I just unscrewed everything, moved stuff around and screwed it back together.......
EDIT: Ok so I got into recovery finally, did a factory reset. Windows still won't recognize it but at least it works now.
If you can get into recovery. Wipe data. so and PIN should be gone
Now boot phone and hit that USB debugging.
Odin should see it now.
Sent from my SCH-I535 using xda app-developers app
barrackOBAMA said:
If you can get into recovery. Wipe data. so and PIN should be gone
Now boot phone and hit that USB debugging.
Odin should see it now.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea I did a factory reset, but can't get past activation of SIM since it isnt unlocked or anything. So it just give me turn off phone or emergency call. Windows still doesn't recognize it though.