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.
Related
This is for those of you that may need warranty work, exchanges whatever. It may or may not be an issue but im sure many of you have noticed that clockwork will pop up whenever the phone is powered off with a usb connection present. Which in most cases would be an immediate red flag for those of you needing work done. This will completely restore your phone and remove the clockwork recovery flash.
Update: I no long have an Aria to try this with but if you guys are running into issues try this as well.
winsettr said:
I'd like to suggest that you update the first post to include a link with the last 2.1 RUU, seeing as the 2.2 RUU breaks the ability of future rooting (for now). I have uploaded what I believe is the updated RUU 09142010 to MegaUpload, linked below. Just thought this might help
http://www.megaupload.com/?d=XXYBORR6
Click to expand...
Click to collapse
1.) Download ATT Original Shipped ROM file from here:
http://www.htc.com/us/support/aria-att/downloads/
2.) Disconnect USB connection to phone.
3.) Power down phone
4.) Boot into Fastboot Menu (hold trackpad on start)
5.) Insert USB
6.) confirm that the phone shows "FASTBOOT USB"
7.) Run downloaded exe file
8.) Process will take a few min at the end you should have a 100% restored and unrooted phone.
It may seem self explanatory now but I was running into issues getting the HTC tool to communicate with the phone and it would fail whenever trying to send the phone into the bootloader. Thought I would just save you guys the headache.
thanks for your solution. was thinking about unrooting my phone and exchanging my aria for a samsung captative...
thanks man. doubt i'll do this, but i might need this just incase ATT and HTC actually come through with a stable update to froyo 2.2 within the next couple months.
I think it will be safe to assume that said 2.2 ROM will begin floating around in a rooted form not before too long, and will be flashable via recovery.
this is great info to have. great work.
???
has anyone actually tried this? because my pc dosent recognize phone when i try
bred904= said:
has anyone actually tried this? because my pc dosent recognize phone when i try
Click to expand...
Click to collapse
install Android SDK USB drivers first
??
i think i did... i installed something from google called android-sdk. and when i connect my phone in bootloader i can see fastboot change to fastboot usb and my pc says driver successfully installed. but when i run the .exe file it never sees my phone. also htc sync wont connect and neither will droid explorer. thanks
i agree with bred, can't seem to restore the original rom. it doesn't recognize it during the process
I have tried this method on 2 computers and the exe can NEVER find my phone.
I have installed the SDK USB drivers, my computer sees the Android 1.0 device and sees it as the HTC booloader. And I see FASTBOOT and FASTBOOT USB when unplugged/plugged.
----UPDATE 2010-07-23----
After further research I was able to determine that even with the device NOT in FASTBOOT mode, that adb couldn't see it, so I thought it might be a driver issue.
I've gotten my computer to recognize the device when it's booted normally. But when put the device in FASTBOOT or the BOOTLOADER, adb can't recognize it and I can't get the recover exe to recognize the device, regardless of mode.
I have the latest clockwork recovery installed and I would like to get everything back to factory to exchange for a captivate.
theres no way to do a nandroid backup or anything like that? curious because i was going to take mine back tomorrow to exchange for the captivate as well. i bought mine from radioshack so i might try my luck and just return it rooted . i did the trade in program with them with my iphone and it was jailbroken and they still accepted it. i dont think i would try that with at&t though... worse comes to worse just return it and say it was like that when you got it! maybe an at&t employee messed around with it before you bought it. they cant prove it was you.
Can anyone confirm this works? Just in case. This might be something I will need to do quick fast and in a hurry in the morning. And I'm hoping that if it comes down to this I won't have any issues.
Sent from my HTC Liberty using XDA App
I have been thoroughly unsuccessful in getting this method to work.
I have tried it on 3 different computers and I can never get the HTC OriginalShipRom.exe to find my phone.
I have tried following the instructions to the letter, I have also tried plugging in while booting the phone into various menus (HBOOT, FASTBOOT, and regular booting), which was advice given to me in the IRC room.
I'm plugging the phone in right after I click "Next" on the "Plug your phone into the usb port" right as it shows the "Verifying data on your PDA" window. I have tried with the phone in HBOOT, FASTBOOT, and while booting the phone, none of these seem to work.
I've also tried it with just plugging the phone in and running the exe. Nothing seems to work. People in the IRC channel are claiming successful factory restores, but I can't seem to get it to work.
So can someone please update the first post with more thorough instructions? Because those instructions don't seem to work.
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
OutsiderWV said:
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
Click to expand...
Click to collapse
My problem is with step 3. The second I plug my powered down Aria into the computer via USB, it powers on and goes directly into Clockwork.
If I boot the device into FASTBOOT, then plug it in, and then run the exe, it says it can't locate the device.
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
farquep said:
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hi farquep, can you give me instruction on how to use linux what's the command line?? thanx
If you do it under linux, just download the file and run it like any other program in any other operating system. Although you will have to let the file run as an executable under permissions. I don't know if you need to install WINE which will emulate windows programs. There should be no need for terminal scripts.
Sent from my HTC Liberty using XDA App
Doesnt recognize my device at all. If I'm returning to insurance company, should I even bother taking off clockwork? I already have the replacement.
EDIT:
Update:
Just worked for me. I had to install aria_shipped_rooted_signed.zip first then HTCAriaOriginalShipROM.exe recognized the phone.
SysAdmNj wrote:
> I had to install aria_shipped_rooted_signed.zip first
perhaps that can be added to the original instructions.
the archive can be downloaded from here
I bought a Nexus S from craigslist last night and it was out of juice. The seller was like oh bring it back if it doesnt work and I fell for it! I have the box/manuals/charger and everything so the phone was not stolen. When I put it on charge and turned it on this morning all that comes on the screen is google and a unlocked padlock on it. I thought that I can restore it. Went to the recovery mode by pressing volume up an power switch and tried reboot/recover and power off and they all lead to the same screen. volume down and power leads to nothing. So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Now I am wondering if there is a way to restore the phone as I think that the seller messed up trying to mod the phone and there is no OS on the phone. Does anyone know how to fix this problem? I tried installing various recoveries and nothing seems to work since I cannot get super user to load nor can I boot up the phone to the OS. Please help a noob!
What is that "same screen" you are talking about? If it's the Droid with a "!" then you have to press vol up + power again to activate stock recovery.
Since you can access fastboot you should be able to flash a new recovery with adb.
Download the cwm recovery image, put it in /tools folder, run adb in cmd prompt, command is "fastboot flash recovery <recoveryimagename>.img", after that you can mount the internal storage via cwm recovery, copy any rom you like onto it, then "install from zip". I'd also format all parts of the phone once (mount and storage) and wipe dalvik cache (wipe) before you flash the new rom.
If it all doesn't help put the phone into download mode (vol up + vol down and then plug in usb cable while holding those two buttons), samfirmware.com has files (Odin) for the i9020 and i9023 (not NS4G yet).
In case your pc/laptop misses USB drivers you can find a guide on how to install adb and the drivers on unlockr.com.
even easier then that, just download the one click root (the gsm version for gsm or the ns4g one for cdma). turn the phone off then boot it back up by holding volume up and power. this will get you into fastboot, from there run the one clicks until it starts to do stuff to your phone, you may need to boot into fastboot mode again at some point. but it will get you a custom recovery loaded up from there you can download a custom rom and flash it in recovery and have a fully working phone
sounds liek the guy tried to root it and messed up something so he sold it privatly seeing as he couldnt figure it out. his loss is now your gain
the phone as you describe it is fully recoverable (dont use odin as its rather risky if you dont know what to do with it, not when you have things like fastboot or recovery mode)
mitrals said:
So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Click to expand...
Click to collapse
If you were interested in getting in touch with the seller, try calling that number from another phone. You have been Google Voice blocked.
However, your issue is easily fixed I think and this shouldn't be needed.
rentaric: It keeps going back to the screen that says Google and has a unlocked padlock at the bottom center. I tried doing the recovery by the following link: http://forum.xda-developers.com/showthread.php?t=1007782 (The phone is unlocked as it states in Lock State-Unlocked). I was able to finish part 3 as well. In part 4 I get stuck at step #8, where pressing recovery gets me back to Google and unlocked padlock screen. I repeated the procedure multiple times and always get stuck at part 4 step 8. I am trying to get samfirmware going after I try one click root. Will post results.
shabbypenguin: I will download one click root and see where that takes me. I also think there might be some water damage to the phone as the strip on the phone is red and at times buttons dont work.
t1n0m3n: I called the seller from 5 different numbers (US and Canada numbers) and it says the line is disconnected for all numbers. I think he disconnected his phone.
Other notes: Phone looks in great condition so if I can get it running it would be awesome. I paid $250 for it thinking its a great price if the phone worked. Attached is the picture of what the phone does on start up.
are you sure you were able to flash the recovery correctly? does the md5 match? maybe try re-downloading the file?
fastboot flash recovery recovery.img
make sure you are using the recovery specific to your device (NS, NS4G)
Where do I find the MD5?
Here is what the phone says on the bootloader mode:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 16
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKD1
CARRIER INFO - ATT
SERIAL NUMBER - 31310A98550B00EC
LOCK STATE - UNLOCKED
And the rest..
Please let me know if anyone can help! Thank you
Are you rebooting the phone after installing the custom recovery (part 3, step 5)?
If yes, skip the rebooting part and go directly into recovery from bootloader screen. In case it works you can continue to mount the usb storage, copy a ROM on your sdcard, unmount, then go back to "Install from zip" after doing all 3 wipes available in "wipe" menu.
If no, then I have no further ideas then using Odin.
Same issue for me, maybe this phone got the NAND Flash problem. Warm it up then try to turn on your Nexus, it worked for me but I sent my Nexus last week to Samsung for repair.
There is a thread in Google Mobile Help Forum (google.com) in Help forum > Google Mobile > Android Devices > Android Applications (not listed above)
Sorry but i can't post the link.
Regards.
I am having the same exact problem with my phone. The only difference is that my Nexus is a sprint phone. Were you able to get your phone working and how did you do it?
---------- Post added at 05:27 PM ---------- Previous post was at 05:15 PM ----------
Im having the same problem with my phone. I have a nexus s and I think I need to flash [RECOVERY] clockwork because it says "fastboot mode - No boot or recovery img." Im using a mac but I cant seem to get it working. Can someone help me. I cant seem to figure out what to do and where to start.
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
filmgeekben said:
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
Click to expand...
Click to collapse
i made this suggestion in another thread just a bit ago. I would try to slip a knife or something else thin under the tab in the phones usb port and push it up just a bit. My device was not being recognized or anything on my pc but would charge just fine. I did the afore mentioned and it works like a charm now.
other than that can't you push a recovery img through a terminal emulator on your phone?
I was able to connect to USB only a few minutes before this whole problem started, I even copied my backup folder from the device on to my computer. After the update, the drive disappeared.
On Windows it will appear as "Android 1.0" but says that drivers aren't installed, and the drivers installed from either Samsung or the Android SDK do not work for the device. I also tried using Odin as well as Unbrickable, which showed that it was connected, but failed when I tried pushing an image that way and said "Device not found".
I can get the device into Download mode in addition to fastboot, but neither can be recognized.
My phone did exactly the same connect very rarely and then only briefly, adb , fastboot and usb ( even sdcard on CWM) not working. I tried almost everything, even format all .....and then broke all....works only bootloader and CWM ...but what did not work anything ( adb, fastboot, usb) - I decided to go for repair because it was in warranty. Three weeks have passed since it is repaired....but they said that I will get back shortly. If you see that you can not do anything .... Think it take to repair....
When you start to have problems with usb will not take long and the phone will become unusable ! Get it repaired as quickly as you can , even if it's unlocked bootloader , if it have warranty will fix it....Good luck !
Surdu, I think you're right. I have arranged to have Samsung check it out, if they do wind up charging me for the repair hopefully it won't be too much.
filmgeekben said:
After checking lots of other recent posts, nothing has come close to the problems I'm having.
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6 successfully (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't get to recovery (get "dead droidbug" image). Device doesn't show up when connected with USB on Mac, Windows or Linux. Ran ADB on computer and it says the device is not connected. Tried using Unbrickable, didn't detect the device. HOWEVER, when connected to Windows it shows up as "Android 1.0" in device manager, but says that there are no drivers isntalled for it, and none of the drivers from Android SDK work.
Device can still charge from USB, and I can get to fastboot on the device itself. If I can some how get the device to show up on USB I know I'd be set. Any thoughts?
Click to expand...
Click to collapse
that dead droidbug image is stock recovery. update your drivers(pdanet is an easy way how), fastboot a recovery, access the usb option in your newly flashed custom recovery, load a rom unto your sd storage, WIPE, then flash the rom. i think your problem was that you didnt wipe before flashing the ics rom. it was a big step between gingerbread and ics, you usually want to wipe when roms are that different.
simms22 said:
that dead droidbug image is stock recovery. update your drivers(pdanet is an easy way how), fastboot a recovery, access the usb option in your newly flashed custom recovery, load a rom unto your sd storage, WIPE, then flash the rom. i think your problem was that you didnt wipe before flashing the ics rom. it was a big step between gingerbread and ics, you usually want to wipe when roms are that different.
Click to expand...
Click to collapse
He can not update the drivers because when the phone connects to the computer nothing happens !!! And if you try to install PdaNetA300.exe or x64.exe you can not because you must have phone connected to it!
---------- Post added at 07:51 PM ---------- Previous post was at 07:46 PM ----------
If your computer detects the phone you can enter in the device manager and click rigt on the android drivers and update with : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------
filmgeekben said:
Surdu, I think you're right. I have arranged to have Samsung check it out, if they do wind up charging me for the repair hopefully it won't be too much.
Click to expand...
Click to collapse
Hey I'm very happy now!!!
Today I received the phone back after being in service....very curious : they left bootloader unlocked ....mention that so I sent and with CWM 5.0.2.0 installed ....
On receipt of repair writes that changed the screws and update the software ...with 2.3.6 but still it was installed before breaks!
And all that free because the phone was in warranty!
My phone did not want to boot this morning after swapping SIM-cards twice. Tried many things, including a hard reset, but nothing worked; the phone kept getting stuck in the second boot menu (with the fancy coloured X). When I tried to leave it it took a few minutes but the phone finally booted.
But I lost all settings (not files luckily) and came into an unknown screen. Had to setup a Google account but could not do that before accessing for internet. All these things work again, but when I reboot the phone it seems to reset again and I have to start from this unknown screen again.
Does this sound familiar and what can I do about it?
By the way, the phone currently runs Android 2.3.6 so there are no official updates (right?).
I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.
Liquid_Metal said:
I've been messing around a bit and the "unknown screen" seems to be the new initial Android screen, in which you can setup the phone (Google account etc.). Strangely enough the phone keeps resetting and I cannot change anything. Even formatting, either through Windows or the boot/root menu doesn't help: all files that are on the phone right now are kept. I cannot add new files either.
Click to expand...
Click to collapse
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.
mabry said:
First of all, do you have a Nexus S, or Nexus S 4G? Is your bootloader unlocked? If not then I suggest you follow the guides in the development section. I can't put links due to still being 'new' on here. Find a recovery, flash via fastboot, boot into recovery and flash a rom to your liking. Or you can find some system images and flash via fastboot. I hope this helps. If not, then you can pm me and then I will show you how.
Click to expand...
Click to collapse
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).
Liquid_Metal said:
Thanks for your reply. I did not unlock the bootloader. I've seen many difficult topics and don't really know where to start.
I just found out that the phone not necessarily resets to a previous state (this morning) but seems unable to write anymore. I just hooked it on to my PC, removed a file, disconnected, and upon reconnection the file was there again (whereas Windows really removed it).
Click to expand...
Click to collapse
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.
mabry said:
I am uploading some files to Dropbox now. Its gonna take a bit. Then I will guide you through, step by step. Sorry for the wait. I know you want to get your phone back up and running. In the meantime, I recommend doing some reasearch here on xda. Don't be afraid of Google, either. Google can be your best friend.
---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------
Read this. This should help you out.
http://forum.xda-developers.com/showthread.php?t=935819
Read it first. It might come across tricky or hard, but its not... Once you do that to unlock bootloader and root, I would advise you to download either a stock rom, or any others you may feel comfortable with. Look around. There are plenty here on xda.
Click to expand...
Click to collapse
Thanks again . A friend of mine was trying to help with bootloading and stuff, but it's somewhat obscure. He said that chances that it's software or hardware are just 50:50.
Got me kinda frustrated yesterday evening but I still have warranty on the phone (have it for half a year now). Problem is that it might be a hassle, because of a conflict between the shop and the provider. But that should work out.
In the meantime it would be nice to try and get it running again.
Strangely enough, the phone drained itself this night. I made a basic install yesterday and left it in standby. This morning, when I checked the phone, it didn't do anything so I thought it finally passed away. Now that it's hooked to my computer it's charging, and it seems to start from 0 (starting with 0 bars of the battery).
Via your link I came to the following guide, which worked partially (cannot link it here).
age tee tee pee ://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I got up to step 13, where it seems that I cannot find the .zip-file because the phone doesn't store new files...
You can wait for warranty, or you can follow this guide:
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Odin will flash it back to stock without the need to put files on your sd card. Just download the odin files, open up odin, put phone in download mode, and happy flashing. You have to be careful with odin, though. Follow the guide. If you need help, then let me know. I can probably do it remotely for you.
Thanks, I'll try that tomorrow (topic doesn't seem so clear at first glance).
According to this guide, I have to start in Download Mode. I can access this by holding Volume Up + Volume Down and then plugging in the USB cable. It works, but the phone will not be updated and I'm stuck with the "Downloading..." message. Also, Windows Device Manager sees a Gadget Serial, which I cannot update. Google didn't allow for a clear answer (Samsung PC Studio 7 didn't work).
I also think I have an i9023, because it's the European version (which SHOULD be with an LCD screen).
By the way, I just tried formatting through Windows (FAT32) and if still connected the phone indeed seems to be empty. But as soon as I disconnect USB storage all files (on the phone) are back. Nothing special because the problem is very consistent.
Update
Alright, I finally got the drivers properly installed (also to work in Download Mode) and found proper Bootloader/PDA/CSC files (i9023EUR) for Odin and managed to do the flash update (however Odin I used is called I9003_Odin3 v1.82, don't know if that is a problem).
Then I should do a factory wipe, which works (Bootloader -> Recovery -> Wipe), but if I explore the phone I can see that all data is still present (all images, music, etc). So the hard drive still seems fixed.
Please help me out, guys...
Suggestions? Or unfixable and should I send it to be repaired?
I found out that I did not post my last update. I managed to flash with Odin, and I can get into the Bootloader menu to wipe the phone's data. I can, in Recovery Mode, also see the hard drive and it seems to be empty. That is, the phone fails to see it.
When I reboot out of Recovery Mode the phone gets stuck at the Google logo and that's it..
Ok, I will send the phone to be repaired. The phone is now unrooted and does not go further than the Google load screen.
Do you have fastboot? If not then download below.
http://dl.dropbox.com/u/64632729/platform-tools.zip
Extract contents to desktop. Open up a command prompt:
cd Desktop/platform-tools
Put phone in bootloader mode. In command prompt type:
fastboot oem unlock (only if your bootloader is still locked). If its unlocked then download this
http://dl.dropbox.com/u/64632729/recovery-clockwork-5.0.2.0-crespo.img
Put in the platform-tools folder you extracted earlier. Then type in command prompt:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Sometimes the flash might say 'fail' if that is the case then just boot the recovery image by typing:
fastboot boot recovery-clockwork-5.0.2.0-crespo.img
Now boot into recovery and flash either a stock rom, stock rooted rom, or whatever your desire is.
This should work. If not, then there has to be a hardware issue with phone and go ahead and send it in for warranty. Let me know if this helps.
Flashing Clockwork did work, but if I understand correctly I have to copy the stock rom to the phone and load it in Recovery Mode? When I connect the phone to my PC it is recognized as an Android Phone (and even as a Nexus S) but the drive it shows up as seems to be recognized as empty ("Please insert a disk into Removable Disk (E.").
So what do I do?
What is sort of promising is that it indeed was capable to flash Clockwork. So the memory is not completely stuck. However, when I do a format, still nothing happens (phone isn't formatted).
Update: I am able to mount the phone to USB and I can access the phone via Windows. However, I can still not format the SD Card (which is of course internal) or put files (stock rom) on it. Are there other tricks to flash a stock rom? If not, it does indeed seem to be that I cannot flash a custom/stock rom because the drive of the Nexus is frozen/broken/whatever.
First of all I apologize if this has been covered, I have been trying to find a solution for 3 days straight. I have a Rogers Wireless HTC One X I managed to unlock bootloader and root as well as having access to TWRP 2.1.8. recovery.
My problem is when I tried to apply the 3 dot removal mod my phone suddenly would not boot past the first screen, and a message would appear for developers use do not distribute but just stay on that screen. I have tried numerous things to no avail. I can boot in recovery and mount sd card from there (but have not found a successful way to restore from within recovery mode) otherwise in fastboot etc. the computer does mount the phone at all. it will not mount as a device properly so I cannot run the RUU and flash to stock.
So I am left with a unmountable and unbootable phone (brick) and have no other ideas on how to fix it if possible. BTW the device does show in device mgr and the computer gives the connect and disconnect alert, but it will not mount. Also, I have read the bootloader has to be relocked to flash back to stock if I relock the phone I cannot access recovery therefore an endless nightmare. Also, within TWRP recovery I try to reboot and it gives an error saying no Android OS found, install a rom or restore from backup (which I have neither) so I have to hold the power and dwn volume button to reboot each time to switch from recovery to fastboot. I think its toast.
Thank you in advance for any responses, I have been up almost 36 hours straight trying to figure this out and the phone is not even a week old. :crying:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
gunnyman said:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Click to expand...
Click to collapse
Thank you very much I will look into that today. Fingers crossed!
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
stnguyen09 said:
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
Click to expand...
Click to collapse
Yes, thank you I have HTC Sync installed and it does not recognize the phone when it is connected either. I will keep searching. Thanks.
ethantarheels123 said:
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
Click to expand...
Click to collapse
Yes, I have tried relocking bootloader, it did not help with the phone being recognized by the computer also when I oem lock I cannot access recovery and such. I will have some more time to poke around with it, I have downloaded the RUU utility although it sends back error with device not found. Thanks for your reply, I will keep at it I know the phone can not be bricked, well I am hoping not!