Related
I ran into a few problems getting back to stock until I remembered a minor detail from my HTC Hero days.
You need to download and install HTC Sync get it here install it.
Reboot your computer
make sure the phone is NOT in USB debug mode and is in charge only mode.
the proper drivers will install. you'll know it's done right if you see ADB pop up as one of the drivers installed. You'll see a warning that HTC sync isn't detecting your phone and that's ok.
Then run the RUU exe all should work fine.
Get the RUU exe from this thread http://forum.xda-developers.com/showthread.php?t=952224 This is FROYO
http://forum.xda-developers.com/showthread.php?t=1191959 This one is Gingerbread
Didn't realize debugging had to be disabled.
Sent from my Inspire 4G or Desire HD or whatever this thing is called via XDA app.
gunnyman said:
I ran into a few problems getting back to stock until I remembered a minor detail from my HTC Hero days.
You need to download and install HTC Sync get it here install it.
Reboot your computer
make sure the phone is NOT in USB debug mode and is in charge only mode.
the proper drivers will install. you'll know it's done right if you see ADB pop up as one of the drivers installed. You'll see a warning that HTC sync isn't detecting your phone and that's ok.
Then run the RUU exe all should work fine.
Click to expand...
Click to collapse
RUU? Where do I find that?
http://forum.xda-developers.com/showthread.php?t=952224
So even if I've tried going through the rooting process and it didn't work, this will basically put the phone back the way it was before I started that process?
Yes
Sent from my Desire HD using XDA App
Good sir I can not thank you enough for helping me get my phone back. i don't even mind all the bloatware now. Too bad I can't use the thanks button more than once. I really appreciate it.
Happy to be of service. I can't dev my way out of a paper bag, well I've never tried, but I can share what I do know.
I tried to run the RUU but it failed twice. Both times it would get about 70% finished and it would stop with an Error 110 which says that a file is either open or corrupted. Then it tells you to download the RUU again and run it again, which I did but got the same results. I downloaded it with the anti virus and firewall turned off. Is there another site to download the file from?
capman231
capman231 said:
I tried to run the RUU but it failed twice. Both times it would get about 70% finished and it would stop with an Error 110 which says that a file is either open or corrupted. Then it tells you to download the RUU again and run it again, which I did but got the same results. I downloaded it with the anti virus and firewall turned off. Is there another site to download the file from?
capman231
Click to expand...
Click to collapse
have no idea. Sorry
Need to put my htc inspire to out of box state
I tried rooting my phone today and everything seemed fine but i didnt like it. so i went back to stock menu. and everything is okay but the sound isnt working can anyone please tell me how to fix this?
mohaamadq said:
I tried rooting my phone today and everything seemed fine but i didnt like it. so i went back to stock menu. and everything is okay but the sound isnt working can anyone please tell me how to fix this?
Click to expand...
Click to collapse
Either flash a different rom via Clockwork Mod or run the RUU. If you choose the RUU, be sure HTC Sync is installed, USB Debugging is checked and Fastboot is unchecked.
Thank you! It works!
Just used this thread to get my Inspire back to stock before taking it back for a refund and cancelling service. Decided to go with the HTC Evo3d from Sprint. This method worked returning the phone back to the latest (Gingerbread) and unrooted it from Cyanogen (CM7) ROM. Thanks a ton for sharing your wisdom!
Baffling Issues.
Hey, I have a question. When running this RUU update (downgrade) it gives me this: Error 140: Bootloader version error. Its agravating. I'd love to go back to froyo... I really can't use GB because it blocks tethering. Any help is appreciated. Thanks.
corvettezo7sp said:
Hey, I have a question. When running this RUU update (downgrade) it gives me this: Error 140: Bootloader version error. Its agravating. I'd love to go back to froyo... I really can't use GB because it blocks tethering. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
I take it you're not S-OFF? HTC (and probably others) decided they didn't want users reverting to older versions. You'll have to root, get S-OFF, before you can revert, but if you're rooted, you might as well just use the new andTether from google code:
http://code.google.com/p/android-wifi-tether/
http://forum.xda-developers.com/showthread.php?t=1233141
Just found out at Best Buy that my phone is crap. The memory is out and I have no apps installed, my HD card is empty except for the standard stuff, and I get error that I need to free up memory or something like that. Guy told me to UNroot my phone and call AT&T.
So, this thread is all I need to do that???? Can it really be this easy????
thanks so much,
Patti
Gene Poole said:
I take it you're not S-OFF? HTC (and probably others) decided they didn't want users reverting to older versions. You'll have to root, get S-OFF, before you can revert, but if you're rooted, you might as well just use the new andTether from google code:
http://code.google.com/p/android-wifi-tether/
http://forum.xda-developers.com/showthread.php?t=1233141
Click to expand...
Click to collapse
Ok, thanks for the info! And this phone has no root, its my Moms phone and she needs the tethering. Eh, maybe we can exchange the phone. Other than that I don't know what to do. I'll browse a few more forums. Actually, one more question: is it possible to root with the latest update from HTC? As you can tell I'm really not that up to date on things around here. Haha.
Sent from my HTC Inspire 4G using XDA Premium App (MIUI FTW!)
corvettezo7sp said:
Ok, thanks for the info! And this phone has no root, its my Moms phone and she needs the tethering. Eh, maybe we can exchange the phone. Other than that I don't know what to do. I'll browse a few more forums. Actually, one more question: is it possible to root with the latest update from HTC? As you can tell I'm really not that up to date on things around here. Haha.
Sent from my HTC Inspire 4G using XDA Premium App (MIUI FTW!)
Click to expand...
Click to collapse
Yes. Ace Hack Kit v12:
http://forum.xda-developers.com/showthread.php?t=952352
corvettezo7sp said:
Ok, thanks for the info! And this phone has no root, its my Moms phone and she needs the tethering. Eh, maybe we can exchange the phone. Other than that I don't know what to do. I'll browse a few more forums. Actually, one more question: is it possible to root with the latest update from HTC? As you can tell I'm really not that up to date on things around here. Haha.
Sent from my HTC Inspire 4G using XDA Premium App (MIUI FTW!)
Click to expand...
Click to collapse
You could try this:
http://forum.xda-developers.com/showthread.php?t=1208507
gunnyman said:
have no idea. Sorry
Click to expand...
Click to collapse
Nice to see you around again gunny
I think I put myself in a bad situation here...
I spent all day trying to figure out how to root my 5 week old Nexus as it's tethering ability is my only access to the web.
So - step one, I did the one-click method, as the instructions I was finding for "the long way" were written by people who know what they're doing FOR people who know what they're doing.
Once that was accomplished, I downloaded Rom Manager. Unfortunately Rom Manager didn't seem to want to work with One-Click's style of rooting, locking me on the boot screen every time I tried using it.
So, I finally worked out how to root my phone the "normal" way and Rom Manager was working.
Here's where my mistake came in... I was one part frustrated from how long it took me to figure it all out, one part elated that I finally DID figure it out, so I immediately put Cyanogenmod on my phone... without backing it up. I played with it a bit, but realized my mistake, so downloaded the 2.3.3 Stock Rom.
That totally futzed things up for me... First, my USB connection isn't working anymore. The USB cable still powers my phone, and the USB ports on my PC still work, but I can't get a phone to pc connection through USB anymore.
Second, my cell radio isn't working anymore, I can only get anything over wifi. The OTA 2.3.4 update was pushed and installed to me that way (The current version my phone is on now...)
Third, apparently my phone was no longer rooted, so Rom Manager wouldn't work anymore for me. When I go to the bootloader menu and try to Recover, it brings me to an android with a triangle and exclamation point symbol.
Once there, some trial and error brought up a menu that I'd hoped would have let me reroot or reinstall a working Rom, but every one I try gives me a Signature Verification error and aborts the install...
So, I'm stuck... Without my USB connection working, I can reroot my phone, and without rerooting, I can't get a working ROM back in place. If ANYBODY can help me with this, it will be greatly appreciated. If any additional information is needed, I'll do my best to give it. Thank you...
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Can you see the phone in fast boot by usb also have you course factory reset and then try to flash
Sent from my Nexus S 4G using Tapatalk
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
TBoarder said:
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
Click to expand...
Click to collapse
Can you answer my question about fastboot? I want to help you.
matt2053 said:
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Click to expand...
Click to collapse
I did that and nothing came up.
TBoarder said:
I did that and nothing came up.
Click to expand...
Click to collapse
ok can you please install PDAnet on your computer?
http://junefabrics.com/android/download.php
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
matt2053 said:
ok can you please install PDAnet on your computer?
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
Click to expand...
Click to collapse
It was already installed, but I reinstalled it. I got to the end of the process where it asked me to go into USB Debugging mode and won't finish the install because it's not reading the USB connection.
(Sorry for any delays here... Being a newbie, I have a 5 minute delay between when I can post)
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here: http://forum.xda-developers.com/showthread.php?t=947950
matt2053 said:
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here:
Click to expand...
Click to collapse
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
TBoarder said:
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
Click to expand...
Click to collapse
Can you post a link to the stock image you installed?
Was there ever a 2.3.3 for the nexus s 4g? Seems like it shipped with 2.3.4
Sent from my SPH-P100 using XDA App
matt2053 said:
Can you post a link to the stock image you installed?
Click to expand...
Click to collapse
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
My suggestion is to try and use Odin to flash it back to stock, I don't think Odin needs any drivers to see the phone...
Sent from my Nexus S 4G using XDA Premium App
TBoarder said:
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
Click to expand...
Click to collapse
Yeah see the thing is there is no 2.3.3 for NS4G. If you flashed 2.3.3 that means you flashed a GSM Rom on your CDMA phone. Oops! not the first time it has happened I'm sure.
Sent from my Nexus S using XDA App
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
How did you find astock 233 rom in rom manager, I only see cyanogen nighties oxygen, peter alphonso, extras etc everything is for the nexus a 4g
Sent from my Nexus S 4G using Tapatalk
TBoarder said:
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
Click to expand...
Click to collapse
Yeah. I have the T-Mobile version. When I download through Rom Manager I get a popup that says "select your phone model" or something similar and then two choices: "Nexus S" or "Nexus S 4G". It would be really easy to mess that up.
The good news is that I believe your phone can still be recovered, you're definitely not the first person with this exact issue, and at worst, it sounds like you have a Sprint rep who is willing to work with you. I think Odin is your only chance for a software solution. I can't walk you through Odin though, because I've never used it myself.
Let me know what happens.
Sent from my Nexus S using XDA App
matt2053 said:
Let me know what happens.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just got my warranty replacement phone due to an abnormally long backorder. Thank you very much for your help (And well, I would've more appreciated it if you hadn't shown me that the problem was all my fault... ). Being my only phone and being poor, I won't be trying to root again, no matter what I learned from this problem. Anyway, thanks again, the help was, in all seriousness, greatly appreciated.
Tried to post this confirmation over on the developer "How to Root" thread, but evidently I haven't posted enough yet
I used the instructions here and they worked great. It was fast and easy, and most importantly for me, did not require the unlock from Motorola. With a brand new phone, I just wasn't up for voiding my warranty just to be able to use Titanium Backup and Wifi Tether!
yep, Motofail2Go! drjbliss is a master exploit writer!
Damn, I did the motorola unlock code which voids the warranty.
First time with a motorola phone and wasn't aware of existing methods
Is there any way to install CWM or another recovery using this method, without unlocking the bootloader?
Nope, Safestrap would be the way to go, but from what I know it is not compatible with the Photon Q....never tried it tough. The Droid 4 works great with Safestrap.
Hey guys, I used this thread to root without bootloader. Worked great after installing the ADB files to my PC and working in debug mode.
Question: I rooted in order to install an ap called reverse tether (PC internet connection powers phone internet). Now the app won't work cuz my phone is shutting down my tethering option everytime because I guess its not on my current Sprint plan. Any pointers or is there something I am missing? Total noob here. TIA
EDIT: Fixed Charge Only mode error... apparently there is some convoluted BS regarding debug mode that will disable the mass storage aspect during debug mode and then keep that setting even after a restart and leaving debug mode. I had to go back in debug mode, 1. Toggle USB Debugging to On (Settings > Developer Options [Under System]) 2. Power the phone off. 3. Power the phone on. 4. Toggle USB Debugging to Off..... still dont know about the VSNCP thing but looks like I can get a handle on it soon as well.
ORIGINAL: Hey guys after my post last night now I am running into some issues... First of all, when I plugged in my phone at work this morning, it refuses to connect as Mass Storage or Media Device MTP or Camera PTP. It lets me select it, but it doesnt save the setting. It automatically reverts back to charging mode whenever I leave the screen. It refuses to save the selection like the options are disabled. Note line 1 of the notifications "charge only"
Secondly, when I decided to restart the phone to fix this connection problem, I got this notification in line 2 of the screen shot, note: "VSNCP Registration Response Error VSNCP Error 8:Admin Prohibited" This message pops up each time the phone boots up. You can't click on it and it doesnt do anything. You can only dismiss it. Any idea what this is?
One thing I noticed this morning is that the Motorola drivers I installed yesterday came with a little PC ap that monitors the phone for updates or whatever, a little Moto logo in the task tray in the corner... now today its gone? I was thinking maybe there is some sort of scheme by Moto to sync the phones to a certain PC with that program so unless that program is running the phone only charges on PCs and doesnt recognize the storage device... but today that program is nowhere to be found on my PC.
Does the root of these problems come from working in debug mode and switching some settings maybe?
Can anyone help me out? I am a total noob that came from a CM 10.1 Epic which is looking pretty nice right about now.
Keep in mind I am a total noob. I did this root method, now I don't know how to unlock the bootloader. I am surprised that the information and how-tos are so hard to find for this phone after being out for 5 months!
TIA
For your VSNCP Error Check this thread over at Sprint
Here is the link I used to unlock mine. As far as I know the only way is to do it through the official motorola website.
http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Sent from my PC36100 using xda app-developers app
Will this still work with 2.3.5?
If I'm not mistaken your on the wrong forum. This is for the photon q not the photon 4g.
Sent from my XT897 using Tapatalk 2
FWIW I have bricked my device twice with this method and of course had no custom recovery to flash and magically fix everything. Quite a hassle but that is the price you pay for being CARELESS. Use at our own risk. One benefit is that I kept warranty. It is great for aps like tether, reverse tether, backup, etc. that require root. Dont know if I will do it again because trying to hack the phone back to operation is not fun. At least my back up phone is an Epic with CM 10.1 and wimax is all over my area unlike LTE.
dwaynet89 said:
If I'm not mistaken your on the wrong forum. This is for the photon q not the photon 4g.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Thats what I have.
Just to confirm, I did this on my Photon Q LTE running Android 4.04 with absolutely no issues since I did it over a month ago.
Just did it and it worked the first time with no problems on my photon q and with 2.3.5
This doesn't work as of the latest firmware update.
Vivicus said:
This doesn't work as of the latest firmware update.
Click to expand...
Click to collapse
If you want root without bootloader unlock on the latest build (ASA-15) you must use this root method BEFORE updating to asa-15. Then install something like OTA root keeper and backup root and temp unroot before installing the update. Otherwise as Vivicus notes, it will not work.
Sent from my XT897 using xda app-developers app
Vivicus said:
This doesn't work as of the latest firmware update.
Click to expand...
Click to collapse
I confirm it
After flash to last firmware I can't get root too
iamchocho said:
If you want root without bootloader unlock on the latest build (ASA-15) you must use this root method BEFORE updating to asa-15. Then install something like OTA root keeper and backup root and temp unroot before installing the update. Otherwise as Vivicus notes, it will not work.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
I'm on ASA-14 and I can't get rooted. Every time I run this, it says exploit failed. I did a cache/data wipe from the stock recovery and even before entering my google account info and going through the startup of the phone, I still ended up with the exploit failed. Any ideas on getting the root wihtout unlocking the bootloader in ASA-14?
Currently no way to do it without unlock. Unless you were already rooted before the update your unfortunately out of luck until someone comes up with a new exploit.
Sent from my XT897 using xda app-developers app
i recently tried to install jellybean but the rom did not work on nexus s, i stupidly removed the only working rom from my 'sd' card and now my phone only boots into a black screen, i have tried to put a known working rom on my phone but every pc i try to connect my phone to says the device has malfunctioned and windows cannot install software. i have tried to use adb but that also cannot find my device. am i looking at getting another nexus with a broken screen and using my working screen to gain a decent phone back or am i missing a vital programme that will fix my utter cockup? thanks in advance
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i am only famililar with adb to the point of rooting, i have tried to download the drivers but only can see .dll files in the driver folders no option to install said drivers. i can get into power and vol up if that is fastboot?? the problem been is i installed a rom which was meant for the nexus s and i didnt read all comments and later found out it does not work with the nexus. i now cannot access the sd storage to put a working rom onto it . when i open cmd and type adb shell it says device not found. brains ready to explode right now. any help on adb is greatly appriciated
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i do not know how to flash factory images, im am very much a noob to rooted phones and playing with software.
i can get into fastboot and at the bottom it says
usb control init
usb control init end
top says fastboot mode
product name herring
hw version rev 11
bootloader version i9020xxka3
baseband version i9020xxkd1
carier info eur
ser 33304eb5103500ec
lock state unlocked
my laptop does not recognise the phone so i dont know how to flash a factory image. this is the cmd sequence i get
adb shell
error device not found
tried mounting sd card and data but no joy
also tried mounting usb storage.
all i get is device has malfunctioned and will not run
tried downloading google usb drivers and samsung drivers all to no avail.
fingers crossed you can tell me something i dont know as i really cant afford to buy a new phone
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
much appriciated and i hope you can too. thank you thank you thanks you
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
FirePoncho86 said:
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
Click to expand...
Click to collapse
still adb cannot find device.......... any links for known drivers for nexus s on win 7 64 bit?
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
reinsalled sdk tools, still phone not recognised by laptop. gonna try get a cheaper android and flog this one on ebay as someone else might know how to repair it. thank you for your time and help but it appears its all in vain......... damn stupid phone!
[deleted]
Rodya234 said:
the phone is probably fine if you can get into fast boot.
Click to expand...
Click to collapse
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i wish someone could just see this, pdanet asks me to connect my phone to finnish installing the drivers, problem is the phone is NOT RECOGNISED i know exactly what you are all saying to do but my phone will not connect at all. more than happy to post it to one of you guys on here to fix but like i said ive tried everything and have pulled nearly all my hair out in the process
Samsung repair? I know what you're talking about, it happened to me, I was completely bricked, all I could so was send it to Samsung repair..
Sent from my Nexus S using xda app-developers app
Damn, if only you could get it recognized you'd probably be able to flash custom recovery through fastboot and I guess you'd be able to install from sd without data loss.
Sent from my Nexus S
I have been looking for a way to root an old Galaxy S3 sch-1535 that used to be on VZW network.
I had cracked the screen a long time and replaced it. But VZW never asked for it back, so my wife just uses it now on wifi since she doesnt have a smart phone. But an app that she would like to start using on it does not support 4.0.4. So... I thought rooting it might be the way to go.
Although it seems as if the info to root this phone is becoming harder to find, I am assuming because it is "older".
I was hoping you guys could help point me in the right direction. Something easy to use to root the phone and a good ROM to use once it is rooted.
I did tried cyanogenmod to root it a few weeks ago, but apparently they dont support it anymore.
jekmandco said:
I have been looking for a way to root an old Galaxy S3 sch-1535 that used to be on VZW network.
I had cracked the screen a long time and replaced it. But VZW never asked for it back, so my wife just uses it now on wifi since she doesnt have a smart phone. But an app that she would like to start using on it does not support 4.0.4. So... I thought rooting it might be the way to go.
Although it seems as if the info to root this phone is becoming harder to find, I am assuming because it is "older".
I was hoping you guys could help point me in the right direction. Something easy to use to root the phone and a good ROM to use once it is rooted.
I did tried cyanogenmod to root it a few weeks ago, but apparently they dont support it anymore.
Click to expand...
Click to collapse
Have you tried the casual root and unlock method? Link below
http://forum.xda-developers.com/showthread.php?t=2332825
FYI you do need a pc to use this tool
Sent from my N5
ShapesBlue said:
Have you tried the casual root and unlock method? Link below
http://forum.xda-developers.com/showthread.php?t=2332825
FYI you do need a pc to use this tool
Sent from my N5
Click to expand...
Click to collapse
That won't work on ICS, only jellybean.
Fortunately this guide still exists.
http://forum.xda-developers.com/showthread.php?t=1762709
Good luck finding rootdebugfs though, if you can find a legitimate copy it will most likely work. However, I'd be extremely careful with it. I'm not exactly sure if it depends on server files to loophole your phone, and you'll be injecting a 3 year old copy of supersu (which is hardly recommended).
If you want my advice, you're better off using Odin and putting 4.1 on your phone, then using casual like ShapesBlue suggested.
BadUsername said:
That won't work on ICS, only jellybean.
Fortunately this guide still exists.
http://forum.xda-developers.com/showthread.php?t=1762709
Good luck finding rootdebugfs though, if you can find a legitimate copy it will most likely work. However, I'd be extremely careful with it. I'm not exactly sure if it depends on server files to loophole your phone, and you'll be injecting a 3 year old copy of supersu (which is hardly recommended).
If you want my advice, you're better off using Odin and putting 4.1 on your phone, then using casual like ShapesBlue suggested.
Click to expand...
Click to collapse
Damn man mine came with 4.1.2 when I got it back in 2013. I didn't even know the S3 was even on ICS but apparently I was wrong. Thanks for the heads up though
Sent from my N5
ShapesBlue said:
Damn man mine came with 4.1.2 when I got it back in 2013. I didn't even know the S3 was even on ICS but apparently I was wrong. Thanks for the heads up though
Sent from my N5
Click to expand...
Click to collapse
Not a problem, that's ancient information, back in my lurking days.
BadUsername said:
That won't work on ICS, only jellybean.
Fortunately this guide still exists.
http://forum.xda-developers.com/showthread.php?t=1762709
Good luck finding rootdebugfs though, if you can find a legitimate copy it will most likely work. However, I'd be extremely careful with it. I'm not exactly sure if it depends on server files to loophole your phone, and you'll be injecting a 3 year old copy of supersu (which is hardly recommended).
If you want my advice, you're better off using Odin and putting 4.1 on your phone, then using casual like ShapesBlue suggested.
Click to expand...
Click to collapse
Thanks for the reply. Im reading through the information now.
First question is, what exactly is the rootdebugfs that you referred to above?
Also, another question I have from reading so far is this, in the guide you provided the link to. The author says that once you are rooted to go to the superuser app and check that the bianaries are updated. If the bianaries are not updated, will I have issues updating them because of not having any OTA access, only wifi access??
I may have more questions as I read more, but wanted to ask this question before I forgot.
And just an FYI for the possibility of my stupid questions. I have done a fair amount of reading about rooting over the years, but have never actually done it
,
jekmandco said:
Thanks for the reply. Im reading through the information now.
First question is, what exactly is the rootdebugfs that you referred to above?
Also, another question I have from reading so far is this, in the guide you provided the link to. The author says that once you are rooted to go to the superuser app and check that the bianaries are updated. If the bianaries are not updated, will I have issues updating them because of not having any OTA access, only wifi access??
I may have more questions as I read more, but wanted to ask this question before I forgot.
And just an FYI for the possibility of my stupid questions. I have done a fair amount of reading about rooting over the years, but have never actually done it
Click to expand...
Click to collapse
Rootdebugfs is a script that injects supersu into the system. Just not sure where it's pulling supersu from.
Binaries are from the app, it'll make you update it from the playstore. Wifi access is fine for this.