Related
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.
Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.
bvsbutthd101 said:
Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.
Click to expand...
Click to collapse
what are the steps you're using in odin? put the battery back in to flash stuff (if you don't already have it in) if it keeps failing... also what are you trying to flash and where are you trying to end up rom/kernel wise?
I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.
bvsbutthd101 said:
I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.
Click to expand...
Click to collapse
Yeah if an odin flash fails and you unplug it and boot it up it will start the last rom you were running. You can still get it into download mode for odin right? Strange that its not flashing right... Try using a different USB port on your pc (as well as plug in your pc for good measure), disable any antivirus software you may have or run Odin as administrator, then put the battery back in for odin as always only use PDA and/or PIT sections
tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.
bvsbutthd101 said:
tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.
Click to expand...
Click to collapse
I probably would've tried a little more to fix it, its extremely hard to brick this phone or make it so you can't recover or get back to stock... anyways thats good, hope its easier to odin with the new one
yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.
bvsbutthd101 said:
yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.
Click to expand...
Click to collapse
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too
anoninja118 said:
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too
Click to expand...
Click to collapse
Exactly, pretty important part if I do say so myself. I'm happy though. They didn't give any problem. I didn't even ask to get a new phone. They just told me that we'll just send one out to you.
Okay, I am not a total noob but I'm not a developer either so I only ~kind~ of know what I'm doing.
I bought a rooted gingerbread droid charge. I tried to un-root it so that I may activate it on my verizon line - to do this I used Odin to put a rooted ED1 rom on the phone. I then used an OTA update which was "supposed" to unroot it but it did not. I only updated it once, not twice, so it was only running froyo.
I then brought the phone to Verizon hoping that they would be able to activate the phone. The first thing that they did was switch the 4G Sim card with a new one and tried to activate it. After multiple failed attempts, they did a hard reset on the phone and tried to activate it again. The verizon guy said that the phone was able to use voice commands to search the internet, but that was all. He said that technically the phone was "all-set-up" and that the problem was was that the phone was not able to activate because it had a hacked kernel. He then told me that in order to fix this problem I would have to find a stock kernel and install it onto my phone.
I then went home and used tried to use Odin with several roms. The last one I tried was this one:
chargeforums.com/forum/droid-charge-development/1575-odin-rom-ep4d-factory-full-factory-restore-2-3-6-radio-unrooted-12-7-11-a.html
However, regardless of the rom I try to use, Odin fails at this line:
ID:0/006 Complete (write) operation failed
If I try to put my phone into recovery mode now, I get a picture of a phone with an arrow pointing to a computer.
Please help me!!!
af.austin.french said:
Okay, I am not a total noob but I'm not a developer either so I only ~kind~ of know what I'm doing.
I bought a rooted gingerbread droid charge. I tried to un-root it so that I may activate it on my verizon line - to do this I used Odin to put a rooted ED1 rom on the phone. I then used an OTA update which was "supposed" to unroot it but it did not. I only updated it once, not twice, so it was only running froyo.
I then brought the phone to Verizon hoping that they would be able to activate the phone. The first thing that they did was switch the 4G Sim card with a new one and tried to activate it. After multiple failed attempts, they did a hard reset on the phone and tried to activate it again. The verizon guy said that the phone was able to use voice commands to search the internet, but that was all. He said that technically the phone was "all-set-up" and that the problem was was that the phone was not able to activate because it had a hacked kernel. He then told me that in order to fix this problem I would have to find a stock kernel and install it onto my phone.
I then went home and used tried to use Odin with several roms. The last one I tried was this one:
chargeforums.com/forum/droid-charge-development/1575-odin-rom-ep4d-factory-full-factory-restore-2-3-6-radio-unrooted-12-7-11-a.html
However, regardless of the rom I try to use, Odin fails at this line:
ID:0/006 Complete (write) operation failed
If I try to put my phone into recovery mode now, I get a picture of a phone with an arrow pointing to a computer.
Please help me!!!
Click to expand...
Click to collapse
Did you odin the pit file along with froyo rom?
Sent from my SCH-I510 using xda premium
No, and I don't know how I would do that either...
Go to the Development forum and follow the "How to fix your phone" guide that is stickied. I would recommend using the EP4D Odin package to get to the latest software. The PIT file used is the same for all builds, and when flashing with Odin, leave the battery in the phone.
Thanks! I ~think~ that it worked. One question though, I wasn't able to find out if my my phone is now rooted or not (after using the EP4D Package)...
af.austin.french said:
Thanks! I ~think~ that it worked. One question though, I wasn't able to find out if my my phone is now rooted or not (after using the EP4D Package)...
Click to expand...
Click to collapse
if your rooted try and app that needs root
depending on which rom you installed or if you ended up ota to gingerbread..
Ota - odin cwr, flash new kernel using cwr
Rooted rom - do you have superuser app, if yes open it up.. If no dl it from market. See if you have root.
Sent from my SCH-I510 using xda premium
Every time I brick my droid going from rom to rom. I use the all_in_one_ep4d odin package. Even if your reverting completely back to stock your gonna have to upgrade your stock recovery anyway (thanks imnuts). I suggest you that use package if you didn't already.
As my post suggest I want to know if there is a way to install a custom rom on my Tmobile HTC ONE S without moving it to SD. I messed up and ended up deleting the current rom I had on it. I have unlocked the bootloader, and I previously had Zydroid v3.5. Currently I am able to use CWM on it but there is no data on the SD that I can use. Thanks you.
mgkamiolo said:
As my post suggest I want to know if there is a way to install a custom rom on my Tmobile HTC ONE S without moving it to SD. I messed up and ended up deleting the current rom I had on it. I have unlocked the bootloader, and I previously had Zydroid v3.5. Currently I am able to use CWM on it but there is no data on the SD that I can use. Thanks you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1667929
Yea, that's my way of doing it. It pushes it from your computer to your SD Card so you can flash it in CWM from there.
If you have no /data/ on your SD Card, that's ok. I did the same thing. Once you get a ROM installed and working, you'll be fine.
brwetz said:
Yea, that's my way of doing it. It pushes it from your computer to your SD Card so you can flash it in CWM from there.
If you have no /data/ on your SD Card, that's ok. I did the same thing. Once you get a ROM installed and working, you'll be fine.
Click to expand...
Click to collapse
I have spent the last 7 hours just trying to look through all threads to try to address this issue. Right now I am unable to send any zip file to my device through ADB. However by using the recovery tool in the ALL in One kit utility I can send a touch recovery .img file to my HTC One S. At first it shows error: could not find device but then the next line pushes that file with no issues.
mgkamiolo said:
I have spent the last 7 hours just trying to look through all threads to try to address this issue. Right now I am unable to send any zip file to my device through ADB. However by using the recovery tool in the ALL in One kit utility I can send a touch recovery .img file to my HTC One S. At first it shows error: could not find device but then the next line pushes that file with no issues.
Click to expand...
Click to collapse
Does ADB see your device?
what happen when you type in
Code:
adb devices
If this stuff is too complicated for u and u have messed up ya phone just run the ruu specific to ur phone and ull be back to normal but u will have to unlock flash and root again
Sent from my HTC One S using xda premium
Thanks for the replys. I acutally got ADB to work by using the mount feature in TWRP recovery tool. However now any custom rom I run will only crash and get stuck in continous boot cycle if I try to activate wifi. This whole issue started when my stock phone got an update two days ago, and it completely messed up my wifi. I should of waited and taken it to the T-mobile store but now its too late. I have unlocked, rooted and put a custom rom on it. I tried using the RUU file to go to 1.53 but i keep getting 155 unknown exception error. For now I will just have to use my phone without wifi till I have more time to look into this wifi issue.
U get the error cuz ur not using the right ruu for ur phone of ur Europe I can send u the ruu for ur phone
Sent from my HTC One S using xda premium
I am currently using RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
I have a Tmobile HTC ONE S phone, and when i had stock it was on 1.84 or so. I think I can't use 1.5 without modding some other files.
Tried using the 1.84 RUU?
Sent from my HTC One S using xda premium
Conflicting RUUs...try the 1.84 and (if you want) root it again afterwards. Glad you got adb working.
brwetz said:
Conflicting RUUs...try the 1.84 and (if you want) root it again afterwards. Glad you got adb working.
Click to expand...
Click to collapse
Unable to locate 1.84 RUU, but I heard that a user named "football" has it but requires a donation. The next best step I think is to try a rooted Nanorid of 1.84 that I found in
http://forum.xda-developers.com/showthread.php?t=1698861&page=4. Ill try this when I have more time. Right now using Zydroid 3.5 rom which works fine except for my wifi. Loading my wifi will crash my phone and put me in a crazy boot cycle.
Alright so I have use a 1.84 rooted backup and successfuly installed it on to my phone. However I still have my wifi issue, also my blue tooth does not work. I also loaded the boot.img file from the backup through fastboot but still having the same error.
I flashed different radios, tried nanoroid backup of 1.84, but wifi does not work. Wifi stopped working while I was still on stock rom. In the end I paid 20 bucks for tmobile to ship me a new phone, hopefully I wont have issues and I will stay on stock rom.
mgkamiolo said:
I flashed different radios, tried nanoroid backup of 1.84, but wifi does not work. Wifi stopped working while I was still on stock rom. In the end I paid 20 bucks for tmobile to ship me a new phone, hopefully I wont have issues and I will stay on stock rom.
Click to expand...
Click to collapse
When you sent it back you went back to RUU and locked bootloader, etc?
I haven't sent it back yet, I will be getting my new HTC ONE S in the mail in two days, and then I can ship my old phone back. Right now my phone is on a nanoroid back up of 1.84 stock rom with root. I tried going back to 1.53 but we dont have S-off so unable to do it. If i try to do that i get 155 unknown error in the RUU launcher. The t-mobile techs didnt know that my phone is rooted cause it basically is the stock rom. I have relocked the phone and I hope that the real techs dont notice that I unlocked the bootloader and it that its still rooted.
Im cancelling my order, some how my wifi works now. Yesterday I did a wifi radio install from europe, but it didnt seem to work. I also relocked the system and rebooted couple of times, this may have helped solve the issue as well.
So, before you think "Oh this guy just doesnt know how to enter fastboot mode" let me explain. So I had a Nexus S for att, all of the sudden *poof* the motherboard stopped working. So I bought a broken Spring Nexus S 4G. So I swapped the motherboards and all was good. Well, I wanted to use it for att. So I also swapped the Sprint communication board with the att one. Well it didn't boot after the switch. So I thought about putting a crespo rom on the crespo4g. It didnt like that, it wouldnt let me restore it. So I thought about flashing the bootloader from crespo. Fastboot accepted it, but then it rebooted fastboot could no longer find a device. Sadly, I hadn't rooted it or installed a custom recovery. If anyone has an idea to restore the crespo4g bootloader that would be amazing. Or a way to root without fastboot, then I could flash the recovery from userland.
Thanks,
Littlejd97
Littlejd97 said:
So, before you think "Oh this guy just doesnt know how to enter fastboot mode" let me explain. So I had a Nexus S for att, all of the sudden *poof* the motherboard stopped working. So I bought a broken Spring Nexus S 4G. So I swapped the motherboards and all was good. Well, I wanted to use it for att. So I also swapped the Sprint communication board with the att one. Well it didn't boot after the switch. So I thought about putting a crespo rom on the crespo4g. It didnt like that, it wouldnt let me restore it. So I thought about flashing the bootloader from crespo. Fastboot accepted it, but then it rebooted fastboot could no longer find a device. Sadly, I hadn't rooted it or installed a custom recovery. If anyone has an idea to restore the crespo4g bootloader that would be amazing. Or a way to root without fastboot, then I could flash the recovery from userland.
Thanks,
Littlejd97
Click to expand...
Click to collapse
Hi, try to go trough the Nexus Root Tool kit.