Okay here are my problems:
I'm running a Nexus S - Rogers version (i9020AUCKE1)
My goal is to get to 2.3.6.
I can't connect via the USB anymore, whenever I try Windows says that it doesn't recognize the USB device. Mac doesn't say anything at all. I have tried turning USB debugging on (though I didn't before and it worked previously) - and I've tried multiple cables.
I can't install / update anything I've found so far through the recovery - everything I've tried fails signature validation.
I'm currently running this version:
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
My phone is unlocked and was previously rooted; though through a series of unfortunate events, I no longer have superuser access directly on the phone (though there is a superuser.zip on my sdcard) and I'm on stock recovery instead of clockwork.
What I'm hopeful to do, at this point, is to get super user access again, get Clockwork back on it and skip the signature validation so I can get it updated. But I haven't figured out a way to do it yet.
I tried z4root but when I tried to root it, the app started but closed itself after about 2 minutes and didn't seem to actually do anything.
Anyone have any ideas of what I can try?
update - I've tried Gingerbreak and it's just hanging on me - doesn't seem to work for either.
Also - I can't find the USB Settings anywhere. I'm wondering if that's my problem with the ROM - it doesn't have the proper USB settings.
Hi,
I got a similiar problem a few weeks ago and found a solution in the internet, that worked for me: Just shut down the phone, put the battery out for approx. a minute. Put it back in and boot, and try again.
I could not believe it, because I don't see the technical explaniation how this could solve this problem - but it did worked, and that is what counts.
Good luck
If your phone is unlocked download rom manager and flash cwm from the app. Do this just after a fresh boot of the phone. If cwm isn't there when you boot into recovery reboot the phone and again flash cwm from rom manager as soon as the phone boots. This time it should stick. From cwm flash superuser.zip and you are rooted again. Then just flash the rooted version of the update.
Normally I recommend flashing recovery from fastboot, but in your case rom manager is the only way to go.
Sent from my Nexus S 4G using xda premium
Related
Hey everyone, I'm quite the lurker on these forums and don't post very often at all. I just want to first and foremost say that everyone here has been amazing and the work that has gone on for this phone is truly astonishing.
Now, with that being said... I'm bricked.
I was running CM7 today and decided (don't ask why) to try that ICS for the i9003. Dumb move. Hopefully someone is getting a laugh out of this as well.
I expected the results to be bad, but not disastrous. In the process of trying to do this I bricked the phone. When I had the ICS ROM on it, it got stuck on the AT&T screen. No worries, I made a back up this morning... I figured just pop back into recovery and restore myself back to normal and everything's fine.
Well, here's where it gets bad. I cannot get into recovery. After multiple attempts of trying to get into recovery. ADB nor Odin even see my phone in download mode. I do have a USB JTAG jig, which has saved me quite a few times.
I started downloading stock ROM's like crazy today. The only one that I could get to install was stock 2.3.5 with Boog's kernel with CWM. I booted into the OS and all seemed well at the time... except there's no modem! I have no internet, service, or anything. This is the only time ADB can see my phone, is when it's booted up. As soon as it's in download mode, ADB can no longer see my phone. The same with ODIN.
ODIN sees my phone when it's booted up, but doesn't actually make the handshake for an install of another version. I've tried to root it, in hopes of being able to push ROM Manager, Super User, and restore my back up in CWM. This didn't work either. During the rooting, using a one-click, it hangs up trying to run the psneuter exploit.
If I'm booted into this 2.3.5 stock of android with no modem, I tried to reboot into recovery using ADB running reboot recovery. This just boots the phone back into Android as if there's no recovery on the device at all.
Soon as I'm back in download mode I cannot push any files with ODIN or ADB. Neither one of them see my device at this point. Even using the JTAG jig.
This is where I'm now at. I'm not sure what else to try at this point. Is there a reason that my device is no longer being recognized in ADB when in download mode?
Any insight would be greatly appreciated. I've been trying to scour forums and search engines with no luck so far. This is my only phone, so it's a little depressing to be without any means of communication on the go, but that's the chance you take...right?
p.s. I do have all the Samsung USB drivers as I normally push files with ADB and have just done so earlier this week. Had the same luck on my computer at work today. So, I know it's not a PC related issue.
Thank you to everyone in advance.
I've also tried to push a modem to the phone with no luck.
I installed 2.3.5 with the Executable JAR of Heimdall AndroidOS 2.3.5 to push the files and that JAR version is the only device that will install to my phone and makes the handshake. Just no modem
You may want to give Heimdall a try - it installs its own USB drivers, so it's possible it might be able to see your phone that way. Nevermind - just saw your post. Which Heimdall did you grab?
Also try switching USB ports - sometimes a different port makes a difference.
There's a one-click in my signature if you need it.
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
edit: Just to be sure I did try the one in your sig. It installs no problem, but ROM manager crashes and the screen distorts right before home screen loads. Once it's loaded it seems OK. Might be a boot loader issue.. but not sure. Once in download moad Odin3 doesn't recognize the device. The one click app does, but not Odin3 v. 1.3 to flash rooted kernel. It just doesn't recognize the device for some reason, but java installer still recognizes it.
I cannot get into CWM as it just crashes. Doesn't reinstall correctly, gets stuck on running privileged commands. Cannot boot into it since it's a privileged command as well. Only version of odin that recognizes my phone is the one in your link and it's a JAR Exe lol. This is the strange part.. no modem. Just got the wifi to work to at least make it to the market place. Still no modem, broadband is 'unknown'.
When I go back into download mode to flash a kernel in Odin v1.3 it doesn't recognize my device. ADB does not recognize my device. The java installer for the stock rom I just used in your sig still recognizes the device. Only the java installer recognizes it. Tried using Heimdall 1.1 for the kernel flash and it also does not recognize my phone.
I do have an HP TouchPad running CM7 alpha 2.1 as well. Not sure if this will help, unless someone can think of something clever by having an extra Android device. Just throwing it out there.
sunfirex said:
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
Click to expand...
Click to collapse
As far as I know, that should have CWM installed in the file. Depending on which bootloaders you have, either holding V+ and Power from a powered-off state, or V+/V-/Power should put you straight into CWM.
If that isn't working for you, but you're at least on a Gingerbread rom, try this. It appears Heimdall is ok with your phone, and this kernel I'm certain has CWM baked in. You might bootloop, but you should definitely get to CWM from this.
That's exactly what it was. That version of Heimdall in the link you provided solved my issue.
Thank you so much!
Glad to hear it.
Ok guys, here I am - finally.
This forum is my last chance as I am going mental trying to find a solution to this issue searching the internet.
My Defy won't charge!!!
It won't charge from a socket, not form the PC via USB.
And It's not the hardware failure, 100% sure.
Now,
Imagine you have a rooted defy with original stock rom.
Everything is fine and you never experienced any real problems with the phone apart from freezing maybe but this is nothing (just uninstall all the unnecessary crap and you'll be fine).
Anyway you decided to play with custom roms, and as this is you first time you do two very important things: back up you current rom and back up all you apps using Titanium Backup.
You also have clockworkmod recovery.
Now,
Here where the problem started - I download new ROM using Rom Manager but when I tried to install it I was given a message: The phone will be turned off and instalation will continue in recovery mode. And when I pressed yes nothing happened.
Next I did the most stupidest thing ever - I installed 2ndinit recovery and THAT'S IT - after reboot - no sign of life whatsoever. I am still asking myself why on Earth I did that.
Oh no, I can get to bootloader but it is saying that battery low cannot program.
I can also get to android recovery mode but this is not clockworkmod recovery and there is no option for restore. I only can wipe cache and restore to factory state but it does not help.
I was trying to get into RSD solution but PHONE IS DEAD, CAN'T DO THAT!
ANY SUGGESTION, I do not want to believe that this is the end for the great handset.
Anything anybody......???????????????????????
Can you see the device when it's connected to a computer? Then you should be able to flash clockwork recovery again using adb. Follow the 'Installing bootmenu & the ClockworkMod Recovery' instructions on the Cyanogenmod wiki / Defy full update guide.
Then you can restore your backed up ROM.
Actually It's not detected by PC just because battery is dead.
So when I get it charged somehow I certainly will try that. Thanks
It won't charge even when the phone is powered off? Have you tried a different USB cable? Maybe you know someone else with a Defy that you can swap batteries with. Or get one of those external battery chargers. It's starting to sound more like a hardware problem, then a software problem with your ROM.
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!
Hi I have stock Nexus S GT-9020T UK running ICS 4.0.3 (which I installed after the stock update failed - by placing the file on SD/Card in recovery mode and installing) . However I'm having problems with battery, radio (Wireless & 3G) and it won't re-boot after it's turned off. (I get round this by heating it up with a hairdryer then it will re-boot eek!).
So to try and resolve some of these issues I have tried to unlock the phone with fastboot. Fastboot runs ok 'fastboot devises' shows serial number but I get a failed message rather than an unlock. Phone just goes back to recovery screen as if nothing happened.
I was hoping to unlock, root and then try a different OS.
So next I have tried to re-install 4.0.3 but when in recovery mode I can't access the SD/Card to run the file. I get a failed to access E:/drive message.
Can anyone give me any pointers to help either unlock and root phone or re-install 4.0.3?
I have been following the relevant guides on these forums but am now stuck for ideas!
Thanks Dinger
I read somewhere about having to heat it up for it to boot. Ended up the nand chip was dying/dead. Exchange if you can else it looks like a hardware failure.
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks. bit disappointing, Samsung customer services suggested I tried Samsung Kies but my Nexus S was not recognised by that either. As it boots into recovery mode I was hoping it was a software problem rather than hardware.
Friend gave me this old phone saying he bought it from "some guy." It appears to have the pre-alpha Eaglesblood Jellybean ROM installed.
What it will do:
-Boot to launcher
What it won't
- Connect to Wifi. Wifi powers on, authenticates, and when it tries to grab an IP address, it soft-crashes & reboots.
- Connect to mobile network. Just doesn't see it at all
- See SD installed SD card (which is known to work.)
- Boot to recover or S/W update mode. I've tried every combo of VOL+/VOL- + PWR, both VOL buttons w/ battery removed then plugging in the USB cable, telling ROM Manager to reboot into recovery... I can't even tell if it had clockwork installed or not.
As a Nexus guy, this device is really frustrating! Searched for many hours. "Oh just do a,b,c" but nothing's working.
If I could get into recovery (which I have to assume is CWM since a custom ROMs on there now) and it could see the SD card, I could flash a working ROM. As it stands, this thing is useless.
Are there any tricks with this specific model to get into recovery that I'm not seeing?
Thanks in advance.
Have you tried reinstalling/flashing cwm again via nvflash? There's a link in one of the stickies with nvflash. Try reinstalling it. I once had a problem where I couldn't boot into recovery for some reason....so I reflashed cwm and it got it working again.
Sent from my LG-P999 using xda premium