Right now my Nexus appears to be pretty much soft bricked and I do not know how to get back to normal. A little background on what happened that led up to this. Was running slimbean 4.3 don't know what slim version but about a month or 2 old(had it when 4.3 was still new) Installed the google hom launcher(launcher, search framework) All went well, Decided to factory reset because phone was running slow(was before installing kit kat launcher) Did so through recovery(latest CWM) when I rebooted I was stuck on the activation screen. Iut can scroll through the various languages, but can not click on any of them to procede. Can open the notification bar and the control panel. Can turn off and on wifi, bluetooth etc. Setting does me no good. When I enter fastboot, I can only reboot booloader, I can not select any of the other options using volume down. I can not use fastboot as it detects nothing(no error, no device on/offline) Device manager gives me generic drivers which aren't installed such as ethernet and pci. No Nexus S driver. Tried installing drivers nothing. I should also note that when I am on the activation screen I can enter usb mode to copy and paste files. ADB and fastboot are working with galaxy nexus. I really want to sell this phone to my cousin but obviously I can not. I really don't think any hardware is currupt but I don't know for sure.
md1008 said:
Right now my Nexus appears to be pretty much soft bricked and I do not know how to get back to normal. A little background on what happened that led up to this. Was running slimbean 4.3 don't know what slim version but about a month or 2 old(had it when 4.3 was still new) Installed the google hom launcher(launcher, search framework) All went well, Decided to factory reset because phone was running slow(was before installing kit kat launcher) Did so through recovery(latest CWM) when I rebooted I was stuck on the activation screen. Iut can scroll through the various languages, but can not click on any of them to procede. Can open the notification bar and the control panel. Can turn off and on wifi, bluetooth etc. Setting does me no good. When I enter fastboot, I can only reboot booloader, I can not select any of the other options using volume down. I can not use fastboot as it detects nothing(no error, no device on/offline) Device manager gives me generic drivers which aren't installed such as ethernet and pci. No Nexus S driver. Tried installing drivers nothing. I should also note that when I am on the activation screen I can enter usb mode to copy and paste files. ADB and fastboot are working with galaxy nexus. I really want to sell this phone to my cousin but obviously I can not. I really don't think any hardware is currupt but I don't know for sure.
Click to expand...
Click to collapse
Don't know how I did it, but somehow I was able to go through recovery via bootloader, still curious as to why I wasn't able to before and why installing drivers to enter fastboot mode failed, I am just glad all is running
Related
First off, I know I'm a new member, and I did watch the video, I've been searching the forum for days now trying to find someone with the exact some problem as me but I've come to the conclusion I must be special as I haven't seen this problem else where. Lucky me...
Let me start off with some information about the phone.
Carrier: Vodafone AU (says XSE on the recovery screen)
Baseband Version: I9020XXKI1
Bootloader Version: I9020XXKL1
HW Version: Rev 52
Model: Nexus S i9023
Lock State: Unlocked
Primary computer: iMac
Fairly certain I have USB debugging turned off :\
I rooted and unlocked the phone and was running the latest CyberGR mod ROM and the latest AirKernel kernel. The phone was running brilliantly, not a problem in the world, very smooth, very fast, excellent battery life, I loved it. Only thing I didn't like was how the keyboard became unresponsive at times. For that reason, I think I'll be switching to the Bugless Beast ROM and thalmus kernel when (if) I get this phone fixed.
So a few days ago, the power button on my Nexus S stuffed up and wouldn't work anymore. Completely unresponsive. I couldn't lock/unlock my phone using the power button. I had to either connect/disconnect it from the USB or turn it on/off by taking the battery out to be able to use it. Needless to say, this got very tedious very quickly and I decided to unroot it and send it back to Samsung.
I looked into how to unroot and came across the Odin app and decided that I'd use that to unroot. (noob error on my behalf, I realise now) Regardless of what I'd read, Odin doesn't work on a Nexus S apparently and although I didn't flash to stock, my phone became significantly less useable, half the time it wouldn't respond to anything I did on it. I tried to boot into CWM and although I was able to do so, it was useless as my power button wasn't working.
At this stage, I took out the battery, put it back in and the phone booted up again. I didn't press the power button, it just booted up straight away. I took it out again and held the volume up button on the side and this time, I didn't get put into the CWM menu, but the normal Android recovery menu. I went to press the volume up and down buttons but nothing worked. Power button is still unresponsive.
When I don't boot into recovery, it goes past the Google screen with the unlocked lock on the bottom of it, and goes to a screen where it says "Android" in a metallic style (I disable the boot animation logo in CyberGR mod so I was used to this screen) and it just hung on there, it never booted up past that screen.
Every time I tried to use fastboot -w to wipe the phone, or oem lock or anything, I would just get < waiting for device >
I plugged it into my Windows 7 laptop, tried the one_click_stock app and got the message that my phone has no boot.img. I then googled problems regarding the boot.img and no one really had any solutions that helped me out.
The SDK won't recognise my phone is there, but the sound pops up on Windows saying a device has been connected and disconnected but it never shows up.
Is it bricked or unfixable? Clearly warranty is void, not sure if I should just take it into Vodafone and ask for a new phone (as its still within warranty period, hence why I wanted to lock it and flash a stock ROM).
Very sorry for the lengthy post, I know I was meant to be brief but I thought the more information I could give, the better chance there would be for anyone to help me out. Thanks.
Make the root of your phone with any application in the market and install the recovery ClockworkMod touch with Rom manager premium or Rom toolbox Pro. Restart recovery using Rom manager or Rom toolbox and do a full cleaning on the phone. Wipe only data and cache.
Now, select from mount and storage mount USB storage and copy over to your i9020 storage any rom ( try using the cm9 ). If the installation is successful restart, if not try some other roms. More than that I do not know how to help.
P.s.: In theory it should go smoothly, otherwise I do not assume any liability for further damage to the phone ... Good luck!
Did you know you can operate cwm using the capacitive search button instead of the power button?
Alfaneo said:
Make the root of your phone with any application in the market and install the recovery ClockworkMod touch with Rom manager premium or Rom toolbox Pro. Restart recovery using Rom manager or Rom toolbox and do a full cleaning on the phone. Wipe only data and cache.
Now, select from mount and storage mount USB storage and copy over to your i9020 storage any rom ( try using the cm9 ). If the installation is successful restart, if not try some other roms. More than that I do not know how to help.
P.s.: In theory it should go smoothly, otherwise I do not assume any liability for further damage to the phone ... Good luck!
Click to expand...
Click to collapse
Thanks for the reply, I can't actually boot into the phone or get to any market place or any screen that could make the phone useable at all, it just sits on the CyberGR android screen for when you disable the boot animation.
bedalus said:
Did you know you can operate cwm using the capacitive search button instead of the power button?
Click to expand...
Click to collapse
I was pressing the search button (the volume buttons were working when I could boot into CWM) and the text just disappeared off the screen and just showed the logo. I can no longer boot into CWM.
I've installed Ubuntu and I'm going to try running the unrbickable java app that a user on here created, hopefully that may work.
Device:
Droid Razr MAXX HD - Stock Factory Phone - Unrooted, nothing been touched. - VERIZON
What happened:
Updated to JB last week. Was a little too glitchy for my liking so I was going to factory data reset and clear the cache.
Problem 1: Failed Reset
Hit Factory Data Reset, phone starts up green android on screen with twirling blue stuff. Progress bar at bottom. Sits there for hours and nothing ever happens. Pulled SD card to see if that helped and tried again. Nothing.
Problem 2: Can't get into Recovery
I power the phone on and hold vol + & vol -, select recovery then get red moto logo then the same screen from problem 1. I hit Vol - then Vol + to try to get into recovery and it doesn't work. It just says ge 0/0 Formatting /data... Again, nothing.
Problem 3: It's reset, but if you shut the phone off you get problem 1 again.
Power on with vol + & - and I select any other option the phone will boot up and will activate for the first time. Sometimes it will find the network, sometimes the network and battery symbol will have question marks. The problem is, when the phone shuts off or restarts you get problem 1 again. Then if I select any of the options with vol+ & - it resets the whole phone.
Any ideas on how I could fix this other than throwing it on the pavement? All this from a factory data reset on a stock unmolested phone.
Glad to see it's not just me then man. Same problem with my Razr HD. Mine was rooted, but stock apart from that. I had been worried that perhaps it was because I'd been too dumb to remove (or better yet, actually protect) bits and pieces like SuperUser and they were annoying it or something.
Get exactly the same problems as you, haven't yet been able to figure out what's wrong. Called Motorola, erm, no, I'm not able to send my phone in, I kinda need it!
Just a note though with the first part of your problem...
Problem 1: Failed Reset
Hit Factory Data Reset, phone starts up green android on screen with twirling blue stuff. Progress bar at bottom. Sits there for hours and nothing ever happens. Pulled SD card to see if that helped and tried again. Nothing.
I'll bet you that if you watch really closely, just before the screen goes blank, you'll see the android laying down with the red exclamation above him. At least I do.
Have also experimented with all the boot options, and also tried redoing the reset from the settings menu. No dice.
I'm guessing that because you've got a Maxx, you'll have a totally different service provider too.
planeray said:
Glad to see it's not just me then man. Same problem with my Razr HD. Mine was rooted, but stock apart from that. I had been worried that perhaps it was because I'd been too dumb to remove (or better yet, actually protect) bits and pieces like SuperUser and they were annoying it or something.
Get exactly the same problems as you, haven't yet been able to figure out what's wrong. Called Motorola, erm, no, I'm not able to send my phone in, I kinda need it!
Just a note though with the first part of your problem...
Problem 1: Failed Reset
Hit Factory Data Reset, phone starts up green android on screen with twirling blue stuff. Progress bar at bottom. Sits there for hours and nothing ever happens. Pulled SD card to see if that helped and tried again. Nothing.
I'll bet you that if you watch really closely, just before the screen goes blank, you'll see the android laying down with the red exclamation above him. At least I do.
Have also experimented with all the boot options, and also tried redoing the reset from the settings menu. No dice.
I'm guessing that because you've got a Maxx, you'll have a totally different service provider too.
Click to expand...
Click to collapse
Thanks for the advice but unfortunately I don't have the android with the !. If I did, I would probably be able to get into recovery. Good luck!
Have you tried to fastboot the phone?
You might lose your data, but you've already tried a factory reset. Here's what to do:
1) Download the Motorola USB drivers from here - https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
2) Download RSDLite 6.0 from here - https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
3) I take it you're on VZW, so download the Jelly Bean fastboot file from here - http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip
4) Boot the phone up in fastboot mode - Turn phone off completely, on power on hold VOL+ and VOL- and press power, that should load a menu. Select "AP Fastboot"
5) Plug the phone into the PC and it should detect in RSD Lite, load the file you downloaded and flash the phone
This shouldn't ruin your warranty status, but nothing is official. I've never done this with the newer Motorola HD phones (since I don't have one yet...) but I have done this many times on many different Motorola Devices like RAZR (OG) and Droid 4, and Droid 3, etc. I'm pretty sure it'll work fine for you.
If you have anymore troubles let me know.
Good luck!
This info should be in a sticky, or a FAQ or something, very useful.
danifunker said:
Have you tried to fastboot the phone?
You might lose your data, but you've already tried a factory reset. Here's what to do:
1) Download the Motorola USB drivers from here - https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
2) Download RSDLite 6.0 from here - https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
3) I take it you're on VZW, so download the Jelly Bean fastboot file from here - http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml.zip
4) Boot the phone up in fastboot mode - Turn phone off completely, on power on hold VOL+ and VOL- and press power, that should load a menu. Select "AP Fastboot"
5) Plug the phone into the PC and it should detect in RSD Lite, load the file you downloaded and flash the phone
This shouldn't ruin your warranty status, but nothing is official. I've never done this with the newer Motorola HD phones (since I don't have one yet...) but I have done this many times on many different Motorola Devices like RAZR (OG) and Droid 4, and Droid 3, etc. I'm pretty sure it'll work fine for you.
If you have anymore troubles let me know.
Good luck!
Click to expand...
Click to collapse
Thank you for this info but unfortunately this doesn't work on my phone either. Computer will not recognize the phone. I did everything as suggested. I got to load the file and it fails almost instantly.
bdbaity said:
Thank you for this info but unfortunately this doesn't work on my phone either. Computer will not recognize the phone. I did everything as suggested. I got to load the file and it fails almost instantly.
Click to expand...
Click to collapse
That means we need the right drivers. Try downloading the other USB drivers from the Motorola site. Also what OS are you using?
Sent from my XT894 running ICS
danifunker said:
That means we need the right drivers. Try downloading the other USB drivers from the Motorola site. Also what OS are you using?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Windows 8
bdbaity said:
Windows 8
Click to expand...
Click to collapse
Yes... I'm really not surprised. I have had major driver issues with Android devices on Windows 8.
When you plug in the phone through fastboot mode, can you take a screenshot of your device manager? Try to double click on the device and locate the Motorola fastboot device.
Sent from my asus_laptop using Tapatalk 2
danifunker said:
Yes... I'm really not surprised. I have had major driver issues with Android devices on Windows 8.
When you plug in the phone through fastboot mode, can you take a screenshot of your device manager? Try to double click on the device and locate the Motorola fastboot device.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
Smart man.... That was the first thing I did was look in device manager and it was a mess while the phone is in fastboot. Computer recognizes the phone fine while it's powered booted up and on. I can get RDLite to find it and try to start and force the file to the phone but the moment it goes into fastboot it fails every time. I got Verizon sending me another phone today.... I appreciate your help on this... I'd buy you a beer if I could! :highfive:
bdbaity said:
Smart man.... That was the first thing I did was look in device manager and it was a mess while the phone is in fastboot. Computer recognizes the phone fine while it's powered booted up and on. I can get RDLite to find it and try to start and force the file to the phone but the moment it goes into fastboot it fails every time. I got Verizon sending me another phone today.... I appreciate your help on this... I'd buy you a beer if I could! :highfive:
Click to expand...
Click to collapse
No problem. I'm going to look for ways to fix this Windows 8 driver issue. I've had problems with nexus 7, Galaxy S, Motorola phones, etc...
Sent from my XT894 running ICS
So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?
n3tm0nk said:
So, my new/used mobo boots,but is password protected. it was not set back to factory. Tried getting into rck, and I get a dead android. No other menu options except to wipe and Android. Anyone point me in the right direction?
Click to expand...
Click to collapse
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.
transformer pad tf300t
graphdarnell said:
Sounds like you're in official 4.2 bootloader, which apparently has no USB icon. When you hit RCK on official loader, if you don't have an official rom loaded somewhere, you'd end up with an android on its belly. Out of caution you should verify with an "elder", or elderly for that matter, if there's a way to ascertain, from where you are, what bootloader you presently have.
On my part, I'd say if you hold down volume - and power, and the tab gets into fastboot mode automatically, this indicates official bootloader 4.2. Then you can use ADB to push or flash TWRP recovery, I think. When in Windows with ADB drivers installed, check when you connect your tab to your PC to ensure it shows up as "fastboot device." And you need to flash the correct version (4.2.1). Read this thread first. Good luck.
Click to expand...
Click to collapse
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.
n3tm0nk said:
Thank you for your reply.
Forgot to include the fact that the tab has not been unlocked or rooted.
The tab doesn't go into fastboot. My windows laptop recognizes it as a media mtp device and wants to synch with it every time I plug it in, but neither fastboot or adb see it.
Click to expand...
Click to collapse
What happens when you follow the directions here by Tobdaryl (reverting back to official 104220 where 4.2 is encrypted)? Short of returning the MB, ain't much you can do hanging on to it, right? I've done this with my tab on official 4.2, and it went back to official 104220 without problems. Must warn you though, it took quite a few minutes and at times, looked as if it's frozen. Just leave it on till it says it's done. Patience counts.
Ok so here is the issue. My Nexus S i9020a has a power button that is no longer working. Whenever I put the battery in, it automatically boots up, to reboot I take the battery out and slide back in. I want to bring it back for warranty since my bro got the warranty until 2014 or so. I had previously had a couple of custom ROMs on it. I wanted to flash stock ROM and lock the bootloader.
When I boot into recovery (hold up while I put the battery in), I can't do anything. Even the volume up/down doesn't do anything, and of course pressing the power button doesn't select anything. So I got ROM Manager and found a copy of the stock rom. ROM Manager was supposed to install the rom from the .zip file, which it sort of did. It wiped everything and installed. I left it on while I went to do something. When I came back, the phone is stuck in the bootup animation.
If I was able to do anything in recovery I would just reflash a different ROM and go again.
I have watched some videos, and tried the Oneclick Unbrick, but doesn't work. I've read some other threads here that talked about getting Linux on a USB, or other mod. But I am trying not to go that route, as it seems pretty complicated.
When the phone is in the bootup animation and I connect it to the computer, I hear the sound that Win7 detects new hardware. If I am in the bootloader Win7 does not play any of that sounds.
I remember using adb and I still have the files on my computer from when I unlocked and rooted.
Not sure what should I do now?
also, all of my soft button lights are on during the boot animation. read in one of the threads that different lights on mean different modes. so not sure if this means anything.
hi, I am afraid the bad functioning of power button is responsible of all of these problems,
probably you can send it for warranty as is now
---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------
have you tried already the linux app UnBrickable Resurrector ?
maybe you would be able to install the stock rom via fastboot
Possible fix: Remove all drivers and reinstall via Nexus root toolkit. Go to adb and flash TWRP, or CWM Touch Recovery (make sure it's touch-enabled), then flash a new rom.
Permanent fix: As far as I can remember (I also had this issue about 6 months ago) samsung will still recognize the warranty even when your bootloader is unlocked, at least in my place. The issue you're returning with is a hardware issue, not a software issue. So tell them to just replace the power button and you'll do the rest. As long as the samsung warranty sticker on top of the screw is in-tact, you're good to go. Again, this is my experience in a samsung service center near my place. I don't know how they deal with things elsewhere.
if this can help, I read in forums that also in Italy samsung support fixes nexus s in warranty even with unlocked bootloader, this is not a direct experience though
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
eugene188 said:
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
Click to expand...
Click to collapse
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
ej8989 said:
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
Click to expand...
Click to collapse
I just tried the PDAnet, I choose the Samsung drivers, then once it pops up with the screen to ask me to connect the phone then I'm stuck. Whether I put the battery in and let it bootloop or hold vol+ and put the battery in, it doesn't get past the screen. Only thing I could do was "skip USB" which still installed PDAnet but possibly without USB support and just bluetooth support.
I even tried it on my brother's laptop which is still in a relatively clean OEM state but the got stuck at the same place.
Ok SO I've installed the Google Drivers and uninstalled and reinstalled them. I've done the same with Samsung Drivers.
I've tried the Bacon Toolkit and the OPO specific toolkit.
Here's the issue:
No matter what I do my OPO is recognized fine in ADB and can be seen by Windows Explorer but it shows up as an unknown device in Fastboot Mode.
I am running Windows 7 x86 and just did a factory reset on my OPO to see if that would help with this process.
GOAL: Unlock the bootloader and Root the phone.
Reason: I'm not a super handy guy with Tech. The reason this began is my OPO was RANDOMLY restarting after the last CM update and I do mean random. Different apps. Different processes. Sometimes not even in use and I feel it vibrate only to see the start-up screen. I'm starting to think I have a virus, if that's even possible. My phone was almost unusable. I'm happy to report that the factory reset DID seem to help. It hasn't restarted without prompting yet.
I still would like to Root it.
PLEASE HELP!
I'm having the same problem. My one plus one was rooted and unlocked bootloader .and I installed Hydrogen Os. It installed perfectly with no issues. But my root access is no more. I cannot go to recovery mode using hardware buttons or any other,neither it shows up on Odin. Please Help.
Sent from my A0001 using XDA Free mobile app
MacCumhailTX said:
Ok SO I've installed the Google Drivers and uninstalled and reinstalled them. I've done the same with Samsung Drivers.
I've tried the Bacon Toolkit and the OPO specific toolkit.
Here's the issue:
No matter what I do my OPO is recognized fine in ADB and can be seen by Windows Explorer but it shows up as an unknown device in Fastboot Mode.
I am running Windows 7 x86 and just did a factory reset on my OPO to see if that would help with this process.
GOAL: Unlock the bootloader and Root the phone.
Reason: I'm not a super handy guy with Tech. The reason this began is my OPO was RANDOMLY restarting after the last CM update and I do mean random. Different apps. Different processes. Sometimes not even in use and I feel it vibrate only to see the start-up screen. I'm starting to think I have a virus, if that's even possible. My phone was almost unusable. I'm happy to report that the factory reset DID seem to help. It hasn't restarted without prompting yet.
I still would like to Root it.
PLEASE HELP!
Click to expand...
Click to collapse
oneplusonehattu said:
I'm having the same problem. My one plus one was rooted and unlocked bootloader .and I installed Hydrogen Os. It installed perfectly with no issues. But my root access is no more. I cannot go to recovery mode using hardware buttons or any other,neither it shows up on Odin. Please Help.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
First off, do not use toolkits. You don't learn much from them and it makes troubleshooting very hard.
Firstly, power off your device.
Secondly, press volume up + power button boots your device into fastboot mode
Thirdly, head to TWRP and download 2.8.6.0: https://dl.twrp.me/bacon/
In your fastboot folder, press shift + right click mouse and select open command window.
In command prompt, type "fastboot flash recovery recovery.img (can be directory of TWRP OR drag your TWRP recovery into cmd) and press enter"
After that type "fastboot boot recovery recovery.img (can be directory of TWRP OR drag your TWRP recovery into cmd) and press enter"
And now you're in recovery mode, you can do all sort of stuff. Remember to make a nandroid beforehand if anything goes wrong