ok so i really need some help with this, here's the problem:
My nexus s won't charge or either be recognized by the computer so i've had to charge it with the core cables of the charger connecting the red to the + and the black to the - anyways i need to return my phone to wind but my phone is rooted and they won't accept it so i really need help to relock the bootloader without using my computer because it won't recognize it any suggestions please?
You're out of luck... Unless you used gingerbreak, which I'm not sure if it works either, you need to use computer to unroot your phone... Have you tried another cable maybe?
Sent from my Nexus S using XDA App
yes i try 4 different ones none of them worked
You can unroot it no problem. What you can't do is relock the bootloader.
ye figured that out (after runing again the update to ICS) i guess ill stay with my phone like this now.. Now quick qestion is it possiible to root it again? haha rom manager is not flashing the Clockworkmod :S
You would need a computer to root now. Should have flashed su after you flashed the update.
guess im completly f*cked now, all i want is to restore to where i had my apps.. is that possible?
I had the same charging problem, but realised that it was charging it just doesn't say it anywhere.
The only place it tells you that it's charging is under setting > battery.
I thought my phone was gone too, but just try plugging it in and going into the settings and it might say charging
You can still root, assuming you have a non-stock recovery. Otherwise you may be out of luck.
im trying to find out how to have recovery or restore my phone on different way (not using a pc) rom manager keeps giving an error that it doesnt have permission so i cant flash recovery from ROM Manager
You can't.
so theres no way to make ROM manager work either?
You need to be rooted to flash a recovery with rom manager. Which you are not. You are stuck there .
yeh well after trying everything cant do Sh*t about it im stuck with this phone can't do much now just the basics
Related
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
ex-googler said:
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
Click to expand...
Click to collapse
have you tried manually flashing the stock signed by google rom through your stock recovery yet? it sounds like it got corrupted or has some corrupted data. id try to manually flash it.
aliiasgar said:
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
Click to expand...
Click to collapse
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
ex-googler said:
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
Click to expand...
Click to collapse
you need the nexus s drivers go to the pdanet website http://junefabrics.com/android/ and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
simms22 said:
you need the nexus s drivers go to the pdanet website and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
Click to expand...
Click to collapse
I've already installed that. It won't detect the phone properly because I can't enable the USB thing within the android OS since I'm blocked from fully loading up the phone.
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's interesting you say that because I do notice an error during recovery and selecting data wipe. I had a colleague in the android dept tell me it's most likely bad flash memory.
"E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata"
I'm gonna call Samsung tomorrow.
Hi all,
I've got a Nexus S 4G CDMA Sprint phone running Stock ICS 4.0.4 IMM76D.
My bootloader is unlocked from previous roots and whatnot.
My problem is that my phone is not being recognized by my computer at all. We're talking complete nonrecognition. No yellow triangle in device manager, no pop-ups, nothing. This phone will just not be read by my computer! I've tried different cords, different computers, re-installation of drivers after resetting my computer, installed PDA net, did a factory reset on the phone, I've literally been on Google for hours upon hours upon hours trying to figure this out and can't figure out why the computer is not recognizing the phone and why the phone is not allowing me to put it into usb mounting. It is however, charging via the computer and wall plug. I can get into stock 3e android recovery, fastboot using V-Up and Power and I can get it into download mode. It is NOT recognized in any modes by the computer nor other computers including my Linux box. The phone states that the usb control initializes but then ends a moment later. I am thinking this is a hardware issue but that leaves me with two issues:
If I was to go to Sprint to have it fixed they would realize my bootloader was unlocked thus voiding the warranty and I'd feel like quite an idiot at the store
If it is hardware related why is the charge working on the device.
I have also tried to bend up the usb plate to make it touch the pins better but that did not help at all. I am at my wits end and really need some help here, I've done everything I could find on Google and here plus more. I want to just return it but with the bootloader unlocked this is really not a possibility. I am looking for help to either become able to lock the bootloader without it having to be connected via the computer so I can then get it fixed if it is hardware related or if I can get the darn thing to be read by the computer once more. so yea, this is where I am at and I would appreciate it so much if someone could help me out, thanks guys!!!
Wireless adb in playstore should help.
Sent from my Nexus S 4G using XDA
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Ebicoustic said:
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Click to expand...
Click to collapse
You might be able to download your rom of choice and rename it update.zip. I'm not sure if it will flash though....someone else chime in if I'm wrong. You can use wireless file transfer if needed.
Sent from my Nexus S 4G using XDA
Yea I've tried that, everything gets shot down by the recovery with a E:Signature Verification Failed. Thank you for your help so far but I don't think this is something that is going to be helped. I've put in a ticket to Samsung for a repair under it's warranty. In the past I've sent in a rooted phone and they've fixed it so I think I'm going to give that a shot. Just don't want to be without a phone for 2+ weeks.
Well good luck...you are running stock unrooted so it shouldn't matter. It is a dev phone for damn sake. Sorry couldn't help.
Sent from my Nexus S 4G using XDA
Well if you want to download a custom rom... Since you are on this forum. Download any rom (preferably CM9 since its quite good from my experience). Flash the stable version and wait till everything is completed. Now when you flash make sure you download a recovery...eg ClockWorkMod Recovery from google market. You should now have a custom rom installed and download wireless adb as chappy said. See if that works
Im looking for help on fixing my SGS4G.
Here is the current list of problems:
1. Phone isnt recognized when i plug it into any computer (i download all the drivers, Kies and Odin both cant find it, and 1 out of every 10 tries my computer will recognize the microsd card and treat it like a normal sd card)
2. My Dialer and Messages will open for 3-4 seconds and close without a force close screen or anything. Obviously this is really annoying :|
3. Im rooted but trying to go back to stock to redo this whole process over is becoming a pain.
4. When trying to flash a custom rom from ROM manager i get the signature verification failed message.
Im about to try the heimdall one-click package to get back to stock and see if that works...idk if it will find my phone though.
My system info:
Firmware: 2.3.6
Baseband: T959VUVKJ6
Kernal: 2.6.35.7-T959VUVKJ6-CL694130
Build: GINGERBREAD.VUVKJ6
If i manage to get back to stock/unrooted where do you guys suggest i go from there? im kind of out of the loop as far as where we are with ICS or jellybean or any of that :|
Thanks a bunch in advance and sorry if this is nooby
Also:
adb devices shows nothing :\
USBDview shows nothing for my phone...i plug it in with debugging on and all it does is charge my phone
First problem. Do not use ROM manager. Download ROM zips and flash through CWM/TWRP.
Have you tried using a different cable when connecting to PC? Some cheaper cables do not work well, or at all. I have a blackberry cable that I only use for this.
Have you tried alternate USB ports. Sometimes that may be this issue as well. Also, some people have better luck with Odin, while others have better luck with heimdall. You may want to try the alternate and see if you have the same issue.
I would follow the guides on going back to stock. You may have old conflicting drivers so you may need to completely remove old ones first.
Sent from my SGH-T959V using xda app-developers app
I use the cable that came with it and the one that comes with my girlfriends phone which is a different phone with no problems. You might want to mess with the usb configuration on your computer
Sent from my SGH-T959V
As far as the dialer and messenger app backing out automatically that was an issue with all bml gingerbread roms. I think there was a fix but I'm not sure. Cm7 is mtd based gingerbread and it doesn't have that problem.
Sent from my SGH-T959V using xda app-developers app
Jiggly,
Ive tried every USB port on my desktop and my laptop. Both of them im reinstalled the drivers on. On my desktop the moment I plug it in it says the device malfunctioned.
Usbdview didn't show anything like the guides said it should. (HTC something...there was.nothing)
ROM manager is just on my phone ive never actually used it other than to boot to recovery
Sent from my SGH-T959V using xda app-developers app
The phone goes into download mode but heimdall still doesnt detect it, windows still tells me the device cant be recognized and im out of ideas.
i went into regedit and deleted all the samsung folders and reinstalled the drivers fresh but im still not getting anywhere...
flash the blastoff kernel, or some custom GB kernel.
Let it convert to ext4, it'll take 10 minutes,
flash a rom through CWM which you will now have.
Im missing something here...but i cant flash anything as everything is unsigned and i cant get out of 3e recovery. ODIN, heimdall etc still wont find my phone from my computer(s) and everything i attempt to flash is unsigned.
Can you boot into your ROM?
boot into my rom as in use my phone? yes the phone functions fine with the exception of not being able to plug it into my computer to tether it/use mass storage and these darn auto close problems with my dialer/messages
Well i was able to flash a new kernel with CWM then upgraded to cm9.
didnt realize contact sync didnt work so i lost all that info :\ computer still says the device malfunctioned but my messaging and dialer apps dont auto close now lol
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Morphie said:
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Click to expand...
Click to collapse
Something like this happened to me a week ago. I have Nexus S 4G. So, I ordered USB Jig from usbjig.com and now I have download mode. It worked! :laugh:
You can buy USB Jig from that site, or build it yourself, or borrow it from someone.
Hi guys,
I think I messed up my phone big time. I had problems with turning on wlan, so I tried Rebooting and Factory Reset but without success. Next I wanted to reinstall android via TWRP like I would do it with my PC. Now I have a Phone with an empty internal SD Card, locked bootloader and no idea how to fix it.
The PC Companion or any other program does not recognize my phone.
Is there any way to install Android again with a locked bootloader or can I unlock the bootloader without android?
Hopefully anyone knows a solution and I do not need to buy a new phone.
Thanks in advance!
Flash a FTF using flashtool
yeah but how do i get my phone in flashmode?
Draiman102 said:
yeah but how do i get my phone in flashmode?
Click to expand...
Click to collapse
http://bfy.tw/1ftE
thanks a lot but so far did i get myself before even posting here ...
i cannot enter flashmode via android obviously and via the volume button is not working, the led does not flash and flashtool is not recognizing the phone when i try it
Plug it into a wall charger for 24 hours and then try again.
Also, sone information from your device manager in your pc may help and what scaly you flashed in recovery to get into this situation. Its very difgicult to offer advice on such limited information.
Problem is fixed, i got a new mainboard ...