Related
I would be so greatful if someone could help me, I think I have really messed up.
Coles Notes: I flashed the 4.0.4 image to my System partition which I am pretty sure should have gone to the boot partition now... Holy **** I'm dumb.
Anyways now my phone is just stuck saying Google. Anyone who can point me in the right direction of even a System image I can flash over top I would be so greatful.
Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?
Moleculor said:
Ok. I'm a dumb newbie, but what happens if you pull the battery, put it back in, then hold down the Up/Down buttons and turn the phone on?
Click to expand...
Click to collapse
Not a dumb newbie, checking if bootloader still works is a good idea
@OP: If you can get in the bootloader, your best bet would be unlocking, installing CWM and then flash a ROM through it.
You can also flash the stock ROM via the GNex toolkit.
Just read the guides and information here in the forums, it seems confusing at first but is really simple once you get used to it.
Good luck!
Thank-you for your quick response. I have CWM installed and can get into the bootloader. the problem now seems to be I cant get the device to show up in windows I always get <waiting for device> when going to flash it. Any ideas? I have been searching the forums trying to find an answer but nothing so far seems to have worked.
Another dumb newbie thing, but when you plug the phone in to the USB port on your computer, does your computer show the phone as having connected (ala the ADB driver in your Device Manager in Windows)?
If not, double check to make sure your ADB drivers are installed. I doubt they aren't, seeing as how you were flashing stuff earlier (from your computer, right?), but it's a wild guess anyway.
Thanks to everyone for the advise. Yes I could see the drivers and they were working perfectly according to device manager. However I guess it was stuck outside of debug mode?
Anyways from the boot menu the program was able to detect it, flash 4.0.4 to the phone, and then I was able to install the canadian radio without issue (hence the reason why I did this in the first place, we are stuck on yakjuux with 4.0.1).
Thanks again to everyone, great learning experience.
Sure thing!
Glad it worked
As a future reference, the "Boot Menu" is actually where you need to be for flashing via PC. The commands won't come through if you're in recovery.
Make sure to make an Android right now!
You enter CWM Recovery, go to backup and restore and then hit backup.
In case your phone ever messes up while you're not close to a computer, you can just boot into CWM and hit "restore", it's as easy as that.
I always have 2 recoveries on my phone just in case.
I saw a couple people had the same issue that im now having but none of there solutions solved my problem
i wiped my GS3 for ATT tried to go back to a stock with root rom and when it rebooted it now just hangs at the samsung logo at boot tried re-flashing via odin with no luck also tried flashing a CWM.tar since i cant get into stock or CWM recovery to flash from there is there something im missing i know its late and maybe my brain isnt working like it should
Solved the problem myself.....and rather then just say i figured it out ill share how i did this since i watched countless videos and read endless amounts of threads and since none of them helped mem
First also try t put your phone into stock recovery mode and wipe your phone then flash this should take care of things if it doesnt try what i tried below
and i hope this can help someone else out there who has the same problem that i had all you have to do is the following i did this with obviously an AT&T model should work with others but as always try at your own risk.....
First make sure your battery has a charge even if its stuck on the boot screen its still charging....
then download KIES from samsung update it and make sure you have the latest version.
Next plug in your phone if your stuck at the samsung screen your computer will recognize your phone still at least it did with mine.
Once your done with the above open up KIES goto the top and then TOOLS and Firmware upgrade click on that enter your phone model (ATT SGH-I747) i dont get this part but next it will ask you for your SN and for some reason it doesnt recognize the SN use your IMEI
Now it should ask you a couple questions tell you its wiping your device and you will lose everything etc.....but then it will download the latest FW and begin to install everything and in about 20-25 mins everything will be back to stock
Nvm.. misread.
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
dbdynsty25 said:
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
Click to expand...
Click to collapse
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
yearziro said:
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
Click to expand...
Click to collapse
Yes, all drivers are installed because that's how I ODIN flashed it in the first place! Just stuck on the damn Samsung screen and I can't get Kies to connect to the phone. Not in Download Mode or when it's just stuck on that screen.
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
whit3gh0szt said:
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
Click to expand...
Click to collapse
Worked, thanks! I appreciate it.
it doesnt work on mine
dbdynsty25 said:
Worked, thanks! I appreciate it.
Click to expand...
Click to collapse
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
me neither
mkstf said:
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
Click to expand...
Click to collapse
Yeah I can't get into recovery either, and its getting really annoying.
indieslap said:
Yeah I can't get into recovery either, and its getting really annoying.
Click to expand...
Click to collapse
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
xBeerdroiDx said:
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
Click to expand...
Click to collapse
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
cabato said:
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
Click to expand...
Click to collapse
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
xBeerdroiDx said:
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
Click to expand...
Click to collapse
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
cabato said:
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
Click to expand...
Click to collapse
Sounds like you need to clear your cache partition and clear your dalvik cache. There are several guides on this site to help you. Choose the one that is most appropriate to what you are trying to do and follow it EXACTLY. There is one to start. Follow it from the beginning.
http://forum.xda-developers.com/showthread.php?t=2042775
When nothing else works start over from search. You cab use download mode? First make sure you got right drivers as that can mess up Odin. Use one in my Sig if you want. Then flag stock recovery with root someone nice will part a link to it I'm on my phone can't do it. Well fix your phone
Sent from my SGH-I747 using xda premium
allow rldcess
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Bump
Sorry, I really need help for this. I can't install the MTP drivers even through using some of the tips on this site. That seems to be the problem with me accessing the phones storage from my computer. Does anyone have an ideas for what else I could do? Should I just take it to the store and hope they can fix it?
cabato said:
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Click to expand...
Click to collapse
go to your device manager on your computer, locate samsung drivers for your device, uninstall them
restart your computer
then plug in the phone and lets it reinstall by itself
Use my drivers in my signature
They are last good damaging drivers. Don't update them but install them and plug phone in with no internet. after install plug internet in. There good stable drivers
Sent from my SAMSUNG-SGH-I747 using xda premium
Hi
Really need some advice here. After (successfully) flashing ROMs on my HTC Desire and a couple of LG / Samsung units, I decided I was fed up with the stock ICS ROM on my Arc S so found one I liked called Jelly Sandwich v6.2.
So, I rooted, no probs, unlocked the bootloader, no probs. Installed CWM and did a nandroid backup to my SD card. So far, so good.
I then used CWM to install the JS ROM and the phone is now stuck on the SONY screen, presumably the boot is looping and I have to pull the battery to shut it back down.
I can't get it into recovery, tried every combination of buttons I can think of. I can get it into fastboot by holding the menu button and inserting the USB cable and if I do a CMD line fastboot.exe -i 0x0fce getvar version I get the expected response, but if I try adb shell I get 'device not found'.
I am rubbish at best with command line stuff but I think this is my only way forward.
Have tried flashtool and I get the phone into Flashmode but it finishes with an error.... 04/048/2012 00:48:51 - INFO - Ending flash session
04/048/2012 00:48:51 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed".
Have also tried SuS and that fails with an error along the lines of "The phone has got modified software that cannot be upgraded" or similar.
Anyone tell me specifically what to try? and exactly what I need to be doing with commands etc.
Would appreciate any help no matter how small
Use the Flashtool instead of SEUS.
XperienceD said:
Use the Flashtool instead of SEUS.
Click to expand...
Click to collapse
he's saying he used flashtool but nothings working..
Sent from my AT100 using xda app-developers app
SORTED!!!
ok I sorted this eventually.
Tried everything I could think of and more besides (went through 100s of threads on here and elsewhere).
Eventually I went to wontanserver.com after seeing it recommended on a thread but it didn't work (forget the error but basically it wouldn't flash).
Then the battery died, left it on charge overnight but it was still dead so really thought that it was a hard brick.
Anyway, this morning, still very blearey eyed, I booted it into fastboot with usb connected and then the wotan tool didn't even recognise the phone, so used Flashtool to connect and the only command that would work was "Rebbot into fastboot mode (via Fastboot)"
Did that and the wotan flash tool started working, unpacking and flashing merrily along and a few minutes later the phone is back from the brink of almost certain death.
Don't know if my blurb will help anyone else, but it at least shows you should never give up :victory:
yorkiepudd said:
ok I sorted this eventually.
Tried everything I could think of and more besides (went through 100s of threads on here and elsewhere).
Eventually I went to wontanserver.com after seeing it recommended on a thread but it didn't work (forget the error but basically it wouldn't flash).
Then the battery died, left it on charge overnight but it was still dead so really thought that it was a hard brick.
Anyway, this morning, still very blearey eyed, I booted it into fastboot with usb connected and then the wotan tool didn't even recognise the phone, so used Flashtool to connect and the only command that would work was "Rebbot into fastboot mode (via Fastboot)"
Did that and the wotan flash tool started working, unpacking and flashing merrily along and a few minutes later the phone is back from the brink of almost certain death.
Don't know if my blurb will help anyone else, but it at least shows you should never give up :victory:
Click to expand...
Click to collapse
I have the exact same problem but I don't know how to solve this. Please help me.
lance26 said:
I have the exact same problem but I don't know how to solve this. Please help me.
Click to expand...
Click to collapse
Try reading the post you've quoted.
Sent from myushi
have you tried to flash a specif kernel for this rom or just redownloaded the rom? maybe there was a problem with the download
Since these problems I have installed both CynogenMod 10 and UltimateHD without any problems what so ever.
When I boot up my tablet, I get nonstop error messages telling me things have stopped working. I tried getting help from someone else on a different site, and this is what they told me to say: I flashed the GROUPER lollipop ROM onto a FLO. Someone please help me!!! It's a totally clean tablet. no files on it except android.
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions: https://developers.google.com/android/nexus/images
Only thing I don't know is whether or not you'll have to repartition the internal flash.
I'm a dummy.
nhizzat said:
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions:
Only thing I don't know is whether or not you'll have to repartition the internal flash.
Click to expand...
Click to collapse
i don't understand how to do all that though I'm not good with command prompts... and nexus root tool kit has done me no good. Could you dumb down the instructions for me?
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
It is almost impossible to hard brick this device, even if you flash the wrong ROM on this device..
Download this utility and it will bring your Nexus back to life....
http://www.wugfresh.com/nrt/
Giving up
nhizzat said:
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
Click to expand...
Click to collapse
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
So that means you will sell it to me for $20?
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
I tried NRTK
madbat99 said:
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
Click to expand...
Click to collapse
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Make sure fastboots working first. Put the tablet in bootloader mode by shutting it off then holding power and volume down (or up I forget, you want the screen that says start at the top and has device info at the bottom left.)
Connect to computer then go into the platform-tools folder in the SDK folder, hold shift and right click over the window>open command prompt here.
Type fastboot devices and hit enter. Does it show a serial number or does it show nothing? (waiting for device or something like that) If nothing you should uninstall all drivers for the tablet in device manager and install the google usb driver from the sdk manager in the sdk you installed.
Once you see the serial number you're almost done. If your bootloader is locked type fastboot oem unlock
Now from the factory image copy the image-razor.zip, bootloader.img and flash-all.bat to the platform-tools folder.
Double click flash-all.bat
That's it.
I think that it will be beneficial for you to look into using virtual machines (VM's). It allows you to run different operating systems directly from your computer.
The second half to this equation is learning to use Linux (Ubuntu is my choice). Since Android is built from Linux, you don't need special drivers to recognize your devices.
Another option to run Ubuntu is to create a Virtual Hard Drive on your PC, and install Ubuntu onto it (YouTube it, and follow the directions carefully).
Lastly, you can always get a flash drive that is 8gb or greater (16gb or 32gb is recommended), and install Ubuntu onto it was well. It will move little slower than your PC, but your issues will be solved and manageable.
Why am I advocating for Ubuntu? Because it works. PM me if your are interested in learning more, but don't expect me to do all of the work. You need to educate yourself a bit to actually follow my instructions.
____________________________
Please remember to:
Check Q & A forums before asking!
Search forum for similar post before creating!
Hit "thanks" to everyone who may have helped you (it costs nothing)!
Read the OP!!!!
Boucherwayne78 said:
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Click to expand...
Click to collapse
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
^Yeah like my last post, those are perfectly fine instructions. If that don't work, stuck at "erasing user data" or something you're ****ed. Most likely.Try a different cord/usb 2.0/computer
Tried a few things. Got any other ideas?
Zaphodspeaks said:
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
Click to expand...
Click to collapse
Thank you for your reply. Do you have any suggestions though for my situation? My bootloader was unlocked. I did try locking it then unlocking it several times though. I've tried two seperate stock ROMs, different usb cables, different usb ports, and it now tells me that fastboot is not working. even a link is greatly appreciated. I think it is a driver problem. My tablet does boot into the OS though. I can use the ui for about 10 seconds, then a notification pops up mid-screen: "unfortunately, the process android.process.acore has stopped." Please, even a link is greatly appreciated. I've tried just about everything to get these drivers working, and to get this tablet working. I will continue to research as well. Wish me luck!
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
azsgolf said:
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
Click to expand...
Click to collapse
Got any ideas on Fastboot.exe stopping working when the flash process begins? it fails sending bootloader and then fastboot.exe fails. It says on the screen when i close the error message it's booting into bootloader, but the tablet never restarts. it stays on bootloader(where i had it in the first place.) It should turn off the screen and go back into bootloader. Please, any feedback is appreciated.
Have you tried selecting the option of hardbrick on the tool?
Hello everyone!
I opened this thread because my current situation seems different from ones I found on this forum, but if you think otherwise please direct me to links that I might need. Before I start with explaining please have in mind that I am quite newbie to anything regarding Android platform and consequently my actions might not have been the smartest ones there. So let me start: I think i hard bricked my Xperia S. I had my Xperia running ROM 1252-0023_6.2.B.1.96_GENERIC-user that i found on this forum. It was a temporary solution, I wanted to put a stock ROM and was about to flash another stock ROM before that. While flashing with flashtool an error occurred (unfortunately I didn't save log file) that had to do something with system.sin . Anyways, my phone is atm unable to turn on, I do not have recovery and I can't even connect it to flashtool (flashtool does not recognize my phone, pressing volume down and connecting to PC doesn't do anything). Only response that I get from my phone is from holding volume up and power button at the same time (it vibrates once, then 3 times).
LONG STORY SHORT: does anyone have any suggestion what can I do with phone that probably has no recovery, can't be turned on and flashtool seems not to recognize it? Thx in advance, I will provide more info on my phone if needed.
blade415 said:
Hello everyone!
I opened this thread because my current situation seems different from ones I found on this forum, but if you think otherwise please direct me to links that I might need. Before I start with explaining please have in mind that I am quite newbie to anything regarding Android platform and consequently my actions might not have been the smartest ones there. So let me start: I think i hard bricked my Xperia S. I had my Xperia running ROM 1252-0023_6.2.B.1.96_GENERIC-user that i found on this forum. It was a temporary solution, I wanted to put a stock ROM and was about to flash another stock ROM before that. While flashing with flashtool an error occurred (unfortunately I didn't save log file) that had to do something with system.sin . Anyways, my phone is atm unable to turn on, I do not have recovery and I can't even connect it to flashtool (flashtool does not recognize my phone, pressing volume down and connecting to PC doesn't do anything). Only response that I get from my phone is from holding volume up and power button at the same time (it vibrates once, then 3 times).
LONG STORY SHORT: does anyone have any suggestion what can I do with phone that probably has no recovery, can't be turned on and flashtool seems not to recognize it? Thx in advance, I will provide more info on my phone if needed.
Click to expand...
Click to collapse
Try the rubber band trick from here.
Ur xperia s is working noww?
Sent from my Xperia S using XDA Free mobile app