Database Info

[Q] Help Desperately Needed - Need to reroot and USB doesn't work

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.

[Q] Nexus S Help!

I just purchased a Nexus S locally last night and it worked fine for a bit and now my sim card is not recognized. I have tried master resetting and that doesn't work. I have an unlocked bootloader and I think I may need to send it in for repairs and I can't lock the bootloader for some reason even after reading the directions. I need some help here please! Do I need to have some drivers for my phone so it can be recognized via cdm prompt? let me know either via PM or on the thread thanks.

Yes you need the Samsung drivers and adb. In the development thread there is a sticky with everything you will need. Read the root methods and they will tell you all the drivers you need and the process.
Sent from my Nexus S 4G using xda premium

pdanet
try to install pdanet and then it work

PDAnet is for tethering purposes I believe.

phoneman09 said:
PDAnet is for tethering purposes I believe.
Click to expand...
Click to collapse
It is used for tethering, but when you install the application it usually fixes the driver issue. After the driver issue has been resolved, feel free to remove the program.
You will also need the android sdk for fastboot to relock your phone, look through one of the stickied guides for root/unroot to get familiar with setting this up and how it is used

phoneman09 said:
PDAnet is for tethering purposes I believe.
Click to expand...
Click to collapse
PDA net installs the necessary drivers you will need to root and unlock the bootloader. Next time listen
Sent from my Nexus S 4G using xda premium

I was listening...I was just saying that's all. I got it all taken care of locally locked the bootloader and unrooted my NS.

Mine has been working since i got and actually loved the phone ... over the last week it has been dropping calls and cant send text messages ( only receives them) no internet, I talked to the techy guy and he said you should always turn off your WIFI because the phone gets confused whether to go on wifi or the carriers internet.... which i think is total bs because i was able to do anything before...
has anyone experienced the same issues here ? how did you fix it?
ps: i did a factory reset 3 times in hopes that it wil be fixed ... but it actually got worse, rooting didnt work for me but im not sure if thats gonna help either
please help
thanks

Having trouble unlocking with 1.85, not sure where I'm going wrong

Just picked up a 1 week old used AT&T One X. Previous owner had rooted, and the phone indeed shows "Tampered" and "Locked" when you boot into bootloader. I confirmed root by using Titanium Backup, and in there it showed "root access: OK (BusyBox 1.18-4-Titanium from app)", so I assume I'm all good there.
So I moved onto the unlock tutorial. The one found here: http://forum.xda-developers.com/showthread.php?t=1672284 I did the following:
1. Downloaded the Spoof-CID file. Unzipped and did not find the file referenced in the tutorial, which is "unlock-bootloader.bat", but assumed that must reference an older zip, and assumed the new file to use is "Spoof-CID.bat"
2. Updated the HTC drivers for the phone so it shows as "My HTC" under Android USB Devices in the device manager when plugged in and in USB debugging mode
3. Ensured USB debugging mode and Charge Only mode on phone are enabled
4. I opened task manager and shut down ADB and HTC manager if I found them running
4. Ran "Spoof-CID.bat" as admin (Win 7 pro x64) and got the red CMD prompt screen open and accepted the first two warnings.
5. This is where it failed - it gave me the following message
"Restarting ADB
Pulling Files
Checking Files
Couldn't pull files from device. Your device was not altered.
Press any key to continue..."
I've tried this on my laptop as well (also running Win 7 pro x64), and still no joy - exactly the same problem.
I did a factory reset, reinstalled superuser and SuperSU, and tried this again from scratch, and still it gave me the same error. I found one other thread that mentioned this same problem after searching, but there was no resolution given.
I'm kind of at my wits end here. I find the stock rom slow, buggy, incredibly bloated, and locked down after recently switching from a Galaxy Nexus with custom Jelly Bean rom on it. If I can't somehow unlock this thing and start putting custom roms on it, I think I might have to put it up for sale.
Any suggestions?

Did you turn fast boot off in power options?

_MetalHead_ said:
Did you turn fast boot off in power options?
Click to expand...
Click to collapse
Ah, yes, forgot to mention that too. Yes, I had it turned off. Still nothing

Taking a shot in the dark here because it's been forever since I unlocked, but try updating the SU binary in the SuperSu app.
edit: You only need SuperSU, delete SuperUser. Not sure but that could cause issues. Not necessarily with this but with other things.

Another suggestion would be to try the manual method so you can see step by step what's going on.
http://forum.xda-developers.com/showthread.php?t=1671396
Sent from my HTC One XL using Forum Runner

If your trying to do it with spoof partitions you can use the manual method also.
http://forum.xda-developers.com/showthread.php?t=1732980&page=1
Sent from my SPH-L710 using xda premium

_MetalHead_ said:
Taking a shot in the dark here because it's been forever since I unlocked, but try updating the SU binary in the SuperSu app.
edit: You only need SuperSU, delete SuperUser. Not sure but that could cause issues. Not necessarily with this but with other things.
Click to expand...
Click to collapse
I read that I should do that in another thread, but I couldn't figure out how to do it. Is that in the settings screen?
E.Cadro said:
Another suggestion would be to try the manual method so you can see step by step what's going on.
http://forum.xda-developers.com/showthread.php?t=1671396
Sent from my HTC One XL using Forum Runner
Click to expand...
Click to collapse
Thanks to all you guys for the tips. Maybe if I really can't find the solution I'll give one of these manual methods a try, though they look a little daunting and I'd be concerned about getting stuck with an unusable phone.
Is there a good reason to go with one over the other? I don't know what spoofing the partition is.

I followed your advice and tried the manual method. Turns out the problem was that the CID has already been changed to 11111111 or whatever. Makes me wonder if the previous owner did this or could it have possibly come that way from AT&T?
Either way, successfully got through the rest of the steps on HTCDev, and I'm good to go! Thanks again for the help!

Lol well that explains it. Glad it all worked out for you
Sent from my HTC One XL using Forum Runner

Really screwed up this time...

Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.

Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
Click to expand...
Click to collapse
Should probably be in the Q&A section -
But try this..
see if you can mount ADB and flash a custom recovery. You will need to google search or thread search for CWM ro TWRP for the xt926 (vanquish) and see if you can flash it through ADB.
that might get you recovery back and if you have a ROM or something on your SD try that.

Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
Click to expand...
Click to collapse
So go into ap fastboot and flash via rsd lite?
Sent from my XT926 using Tapatalk 2

Franzie3 said:
Should probably be in the Q&A section -
But try this..
see if you can mount ADB and flash a custom recovery. You will need to google search or thread search for CWM ro TWRP for the xt926 (vanquish) and see if you can flash it through ADB.
that might get you recovery back and if you have a ROM or something on your SD try that.
Click to expand...
Click to collapse
dark_mirage said:
So go into ap fastboot and flash via rsd lite?
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
ADB Keeps sending me messages saying "Command Restricted" and Remote Failure. RSD Lite gives me error messages. Very confusing.

Try DROID_RAZR_HD_Utility 1.1
See if this tool will recognize your XT926 & use the menu to go back to 4.0.4 (as last resort)..

itzik_man said:
See if this tool will recognize your XT926 & use the menu to go back to 4.0.4 (as last resort)..
Click to expand...
Click to collapse
Tried it. Same thing: FAILED (Remote Failure). Any ideas??

Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
Click to expand...
Click to collapse
Why are you trying to use voodoo to keep root and then downgrade/fastboot to stock? If you are downgrading and already had root on 4.1.1 you could downgrade without root, and even on 4.1.2 rooted and unlocked you just downgrade. You don't have to worry about root. Once the phone is back to stock upgrade to the latest 4.1.2 and then use the root and unlock bootloader if needed.
Is your bootloader already unlocked?
Even if your bootloader is locked you should have no problem rooting even on 4.1.2 with motochopper. And then unlock the bootloader with motopocalypse to be able to downgrade from 4.1.2.otherwose there is no downgrading. Motochopper must be used first if you don't have root or lost root on 4.1.2 in order to use motopocalypse .
Sent from my XT926 using Tapatalk 2

an21281 said:
Why are you trying to use voodoo to keep root and then downgrade/fastboot to stock? If you are downgrading and already had root on 4.1.1 you could downgrade without root, and even on 4.1.2 rooted and unlocked you just downgrade. You don't have to worry about root. Once the phone is back to stock upgrade to the latest 4.1.2 and then use the root and unlock bootloader if needed.
Is your bootloader already unlocked?
Even if your bootloader is locked you should have no problem rooting even on 4.1.2 with motochopper. And then unlock the bootloader with motopocalypse to be able to downgrade from 4.1.2.otherwose there is no downgrading. Motochopper must be used first if you don't have root or lost root on 4.1.2 in order to use motopocalypse .
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I'm not having issues with that stuff anymore. What I am having issues with, Is that my phone is unlocked, no rom, no recovery, etc. All I get is a warning for the unlocked bootloader and AP Fastboot. Everything else in the boot menu doesn't work. I really need to get something figured out. Nothing seems to be working. Look at the above posts for more info on the situation.

Action123 said:
ADB Keeps sending me messages saying "Command Restricted" and Remote Failure. RSD Lite gives me error messages. Very confusing.
Click to expand...
Click to collapse
Are your drivers updated on your computer?
sent from my xt926 RAZR maxx hd

I understand your situation and I have read the posts. What I am trying to say is that you did something wrong, and that there is no need to try to preserve root when fastbooting or downgrading with any utility because you will loose root. Your first post is confusing. You say you were on 4.1. 2 then 4.1.1 and downgraded. Was your bootloader unlocked prior to all this? Once your bootloader is unlocked, you can root on any firmware and sbf to factory settings which should remove root also. You need to re root, and to with motochopper it's the easiest. If I were you I would just sbf using matts until 1.20, upgrade all the way to 4.1.2 then root with utility. I don't see how it's not working.
Or sbf 4.1.2 and just root like stated above...
In order to get into fb mode do a hard reset(hold over and vol - for 10secs then immediately hold power and vol+
Sent from my XT926 using Tapatalk 2

If you can get into fastboot and are status 3 unlocked just flash a custom recovery manually and be on your way. It's not hard...
Sent from my XT926 using Tapatalk 2
---------- Post added at 12:23 AM ---------- Previous post was at 12:20 AM ----------
Start at step 3...
http://www.droidrzr.com/index.php/topic/15583-twrp-installation-on-unlocked-bl-razr-hdmaxx/
Sent from my XT926 using Tapatalk 2

koftheworld said:
Are your drivers updated on your computer?
sent from my xt926 RAZR maxx hd
Click to expand...
Click to collapse
Everything is updated. I'm on OS X dual booting windows. Tried it from both OS's and still getting same problems.

an21281 said:
I understand your situation and I have read the posts. What I am trying to say is that you did something wrong, and that there is no need to try to preserve root when fastbooting or downgrading with any utility because you will loose root. Your first post is confusing. You say you were on 4.1. 2 then 4.1.1 and downgraded. Was your bootloader unlocked prior to all this? Once your bootloader is unlocked, you can root on any firmware and sbf to factory settings which should remove root also. You need to re root, and to with motochopper it's the easiest. If I were you I would just sbf using matts until 1.20, upgrade all the way to 4.1.2 then root with utility. I don't see how it's not working.
Or sbf 4.1.2 and just root like stated above...
In order to get into fb mode do a hard reset(hold over and vol - for 10secs then immediately hold power and vol+
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I rooted a while back. Before the 4.1.2 update came out. I was on the latest update (4.1.1) but the only way to root an HDMaxx at that time with 4.1.1 was to go back to the original 4.0.4, root, keep root using voodoo, then upgrade back to 4.1.1 again. This worked fine on 4.1.1. Then, I upgraded to 4.1.2 and I lost root (even using voodoo correctly). I tried to unlock, then wipe the phone and try to do the process over again, but now I am without rom and recovery. Plus, for whatever reason, my phone isn't responding to adb or fastboot commands. It's probably an amateur user error, but it would help if someone could point me in the right direction. My apologies for a bad initial explanation. Again, thank you in advance.

arcanexvi said:
If you can get into fastboot and are status 3 unlocked just flash a custom recovery manually and be on your way. It's not hard...
Sent from my XT926 using Tapatalk 2
---------- Post added at 12:23 AM ---------- Previous post was at 12:20 AM ----------
Start at step 3...
http://www.droidrzr.com/index.php/topic/15583-twrp-installation-on-unlocked-bl-razr-hdmaxx/
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Tried and this is what I got back. Battery was charging all freakin night. So I doubt it's actually low.
Kim-Jong-Il:~ Cooper$ fastboot flash recovery /usr/bin/twrp-2.5.0.0-recovery-vanquish.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7428 KB)...
OKAY [ 0.629s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.750s

Just in case you overlooked the obvious, have you tried another USB port? My Mac only has one USB 2.0 when I boot it into Windows.
Another problem I have on occasion is that the USB cable just doesn't take for whatever reason. I have to unplug it and plug it back in and try again before anything can be flashed. The phone says its plugged but nothing transfers.
To repeat what's already been said, make sure you've gotten the updated Motorola drivers for Windows.
Make sure the Android SDK is installed and fastboot and adb are added to your PATH in Windows.
If still you have nothing, I only quickly read but I didn't notice that you'de attempted to flash a stock ROM for your carrier or not. It will wipe your data and internal SD, however it seems that whatever the problem is, that if you can get into recovery then something should work.
I'm really sorry that all I can offer is redundant and basic information but sometimes we overlook what's obvious or right in front of us, and good luck with it.
Edit: Sorry, I didn't see the battery low thing. Have you tried a simulated battery pull? Hold volume up and the power button for a bit. You're wanting to feel 10 quick vibrations.

PantsDownJedi said:
Just in case you overlooked the obvious, have you tried another USB port? My Mac only has one USB 2.0 when I boot it into Windows.
Another problem I have on occasion is that the USB cable just doesn't take for whatever reason. I have to unplug it and plug it back in and try again before anything can be flashed. The phone says its plugged but nothing transfers.
To repeat what's already been said, make sure you've gotten the updated Motorola drivers for Windows.
Make sure the Android SDK is installed and fastboot and adb are added to your PATH in Windows.
If still you have nothing, I only quickly read but I didn't notice that you'de attempted to flash a stock ROM for your carrier or not. It will wipe your data and internal SD, however it seems that whatever the problem is, that if you can get into recovery then something should work.
I'm really sorry that all I can offer is redundant and basic information but sometimes we overlook what's obvious or right in front of us, and good luck with it.
Edit: Sorry, I didn't see the battery low thing. Have you tried a simulated battery pull? Hold volume up and the power button for a bit. You're wanting to feel 10 quick vibrations.
Click to expand...
Click to collapse
I think I figured out the sad truth. I take back my previous statement about charging. Since my bootloader and recovery image are not functional, in addition to not having a rom, my device is therefore unable to "accept" the charge. I'm sitting down to solder together a factory cable (which forces the device to accept the charge, by going directly into the battery). I found it here: http://droidrazrroot.com/droid-razr-hacks/how-to-make-motorola-factory-cable/

Action123 said:
I think I figured out the sad truth. I take back my previous statement about charging. Since my bootloader and recovery image are not functional, in addition to not having a rom, my device is therefore unable to "accept" the charge. I'm sitting down to solder together a factory cable (which forces the device to accept the charge, by going directly into the battery). I found it here: http://droidrazrroot.com/droid-razr-hacks/how-to-make-motorola-factory-cable/
Click to expand...
Click to collapse
Just buy a factory cable from team Black hat everyone else does.
sent from my xt926 RAZR maxx hd

koftheworld said:
Just buy a factory cable from team Black hat everyone else does.
sent from my xt926 RAZR maxx hd
Click to expand...
Click to collapse
Soldered one together in about 10 mins. Worked as expected. I guess that was just the problem. I think I'll order a cable adapter from them. Thanks for the help

Action123 said:
Soldered one together in about 10 mins. Worked as expected. I guess that was just the problem. I think I'll order a cable adapter from them. Thanks for the help
Click to expand...
Click to collapse
Most people are not so adept nor have the tools readily available to do as you did and make their own factory cable.
That's why we went to the trouble of producing the factory cable adapters so average users could have a safe and inexpensive solution to this problem and never have to worry about it.
It's the best $10 investment you can make for your Motorola device.
Congrats on being resourceful and fixing your phone yourself!

cellzealot said:
Most people are not so adept nor have the tools readily available to do as you did and make their own factory cable.
That's why we went to the trouble of producing the factory cable adapters so average users could have a safe and inexpensive solution to this problem and never have to worry about it.
It's the best $10 investment you can make for your Motorola device.
Congrats on being resourceful and fixing your phone yourself!
Click to expand...
Click to collapse
Ordered my adapter from you guys this AM

Updated to 4.3 without realizing on rooted S3 now bricked

I have a Verizon S3 and saw a new symbol in my notification bar and stupidly clicked on it without really thinking and my phone tried to update to 4.3. Well after the update I get a screen that says I'm not using official verizon software or something like that and that I need to take my phone to a verizon store to fix it. I can get to the Odin downloading screen I just don't know how to fix it from there. Please help I really don't have the money to buy a new phone right now. Any advice would be welcome

It depends on what is happening to your phone. Is it working or not? Can you tell us what android version is loaded currently?

vax1170 said:
It depends on what is happening to your phone. Is it working or not? Can you tell us what android version is loaded currently?
Click to expand...
Click to collapse
It starts up and after the samsung logo. I get the message System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and to the nearest Verizon Wireless store for help. At the top in red it also says secure fail: kernal. I believe I'm running Android 4.1.2 but I can't remember. If I hold down volume, home, and power I can get into the odin downloading screen but those are the only 2 screens I can access.

deftjangle said:
It starts up and after the samsung logo. I get the message System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and to the nearest Verizon Wireless store for help. At the top in red it also says secure fail: kernal. I believe I'm running Android 4.1.2 but I can't remember. If I hold down volume, home, and power I can get into the odin downloading screen but those are the only 2 screens I can access.
Click to expand...
Click to collapse
As long as you can get to the download screen, you can flash the official 4.3 with Odin. Dont try to go back to 4.1.2 or any custom rom as that will result in a hard brick.
Sent from my SCH-I535 using xda app-developers app

5ft24 said:
As long as you can get to the download screen, you can flash the official 4.3 with Odin. Dont try to go back to 4.1.2 or any custom rom as that will result in a hard brick.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Could you tell me how to go about flashing the official 4.3 rom with Odin. I haven't messed around with my phone in years.

deftjangle said:
Could you tell me how to go about flashing the official 4.3 rom with Odin. I haven't messed around with my phone in years.
Click to expand...
Click to collapse
First go into download mode and see if the boot chain flashed. If it didn't you should flash 4.1 not 4.3.
Once you're in download mode, post all the information it says in the top left corner.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
First go into download mode and see if the boot chain flashed. If it didn't you should flash 4.1 not 4.3.
Once you're in download mode, post all the information it says in the top left corner.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ok this is what is in the top left corner.
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (1 COUNT)
CUSTOM BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOT: ENABLE

deftjangle said:
ok this is what is in the top left corner.
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (1 COUNT)
CUSTOM BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOT: ENABLE
Click to expand...
Click to collapse
You're on mf1 still.
Flash this in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using this guide, section 5:
http://forum.xda-developers.com/showthread.php?t=1762709
Then use this to root your phone again:
http://forum.xda-developers.com/showthread.php?t=2332825
After this, I'd unlock the bootloader with ez-unlock version 1.2 to make sure it's unlocked.
When you reboot, find sdm1.0.apk and fwupdater.apk and rename them to sdm1.0.apk.bak and fwupdater.apk.bak. Or use titanium backup and freeze both of them. Then you don't have to worry about an update being pushed to your phone.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
You're on mf1 still.
Flash this in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using this guide, section 5:
http://forum.xda-developers.com/showthread.php?t=1762709
Then use this to root your phone again:
http://forum.xda-developers.com/showthread.php?t=2332825
After this, I'd unlock the bootloader with ez-unlock version 1.2 to make sure it's unlocked.
When you reboot, find sdm1.0.apk and fwupdater.apk and rename them to sdm1.0.apk.bak and fwupdater.apk.bak. Or use titanium backup and freeze both of them. Then you don't have to worry about an update being pushed to your phone.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This is perfect thankyou! I will let you know how it turns out

I unlock bootloader using CASUAL i read the newest version of EZ umlock can brick ur fone or give off issues

twistedillutions said:
I unlock bootloader using CASUAL i read the newest version of EZ umlock can brick ur fone or give off issues
Click to expand...
Click to collapse
Ez-unlock will brick your phone if you're on the 4.3 base. In this case it will work just fine, he's on the 4.1.2 base.
Sent from my SCH-I535 using Tapatalk 2

locked bootloader on rooted verizon galaxy s3
my phone was rooted and i mistakenly upgraded to 4.3.
i didn't have any problems rerooting my phone.
however though the phone is rooted, from what i've read i'm going to assume my bootloader is locked.
so i've decided to seek answers from the professionals.
i have root checker, rom manager, goomanager, titanium back up, root broswer, rom installer, root explorer, android root tool,superuser, super su, quickboot, terminal emulator and the hackers keyboard.
all to no avail...everytime i try to install a custom rom a message pops up on the screen saying i have unauthorized software on my phone and that i need to take it to verizon. yes from recovery mode...as a matter of fact the recovery mode won't load it just takes me to the " take my phone to verizon screen "...
just to be clear i have a galaxy s3 on verizon running 4.3
phone is rooted and super su, or superuser has been granted to the necessary apps,
still everything i've tried hasn't worked.
sorry for the length but i was attempting to provide as much info as possible...
any and all help regarding this matter will be greatly appreciated...

wesyde said:
my phone was rooted and i mistakenly upgraded to 4.3.
i didn't have any problems rerooting my phone.
however though the phone is rooted, from what i've read i'm going to assume my bootloader is locked.
so i've decided to seek answers from the professionals.
i have root checker, rom manager, goomanager, titanium back up, root broswer, rom installer, root explorer, android root tool,superuser, super su, quickboot, terminal emulator and the hackers keyboard.
all to no avail...everytime i try to install a custom rom a message pops up on the screen saying i have unauthorized software on my phone and that i need to take it to verizon. yes from recovery mode...as a matter of fact the recovery mode won't load it just takes me to the " take my phone to verizon screen "...
just to be clear i have a galaxy s3 on verizon running 4.3
phone is rooted and super su, or superuser has been granted to the necessary apps,
still everything i've tried hasn't worked.
sorry for the length but i was attempting to provide as much info as possible...
any and all help regarding this matter will be greatly appreciated...
Click to expand...
Click to collapse
Sounds like you're on 4.3, if that's the case then you can't install any custom roms without a special recovery.
Just to be sure, boot into download mode and type out what the text says in the top left corner. Your symptoms sound like it could be either, the install of will usually fail if you're rooted, unless everything you had was completely stock.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Sounds like you're on 4.3, if that's the case then you can't install any custom roms without a special recovery.
Just to be sure, boot into download mode and type out what the text says in the top left corner. Your symptoms sound like it could be either, the install of will usually fail if you're rooted, unless everything you had was completely stock.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
i'd like to thank you for taking the time to respond, however i must admit i'm even more confused..my phone is in download mode as i type this,yet i'm at a loss as to what it is i'm supposed to type, plus in download mode i don't have access to any keyboard.
IF ANYONE OUT THERE KNOWS WHERE I CAN FIND A LINK TO A PROPER VID I'D BE MOST GRATEFUL IF YOU'D SEND ME THAT LINK...I HAVE SPENT THE LAST 2 DAYS FOR OVER 10 HRS ATTEMPTING TO FIND THE INFO OR VID I MAY NEED TO BE SUCCESSFUL...
once again thank you for the help...

wesyde said:
i'd like to thank you for taking the time to respond, however i must admit i'm even more confused..my phone is in download mode as i type this,yet i'm at a loss as to what it is i'm supposed to type, plus in download mode i don't have access to any keyboard.
IF ANYONE OUT THERE KNOWS WHERE I CAN FIND A LINK TO A PROPER VID I'D BE MOST GRATEFUL IF YOU'D SEND ME THAT LINK...I HAVE SPENT THE LAST 2 DAYS FOR OVER 10 HRS ATTEMPTING TO FIND THE INFO OR VID I MAY NEED TO BE SUCCESSFUL...
once again thank you for the help...
Click to expand...
Click to collapse
You're on 4.3 with a locked bootloader, meaning you can't install custom recovery, rom, kernel. The only thing available for 4.3 is root. Don't try to install custom recovery or you will brick your phone. At this time you may have a soft brick, go here to fix it http://forum.xda-developers.com/showthread.php?t=2586319

wesyde said:
i'd like to thank you for taking the time to respond, however i must admit i'm even more confused..my phone is in download mode as i type this,yet i'm at a loss as to what it is i'm supposed to type, plus in download mode i don't have access to any keyboard.
IF ANYONE OUT THERE KNOWS WHERE I CAN FIND A LINK TO A PROPER VID I'D BE MOST GRATEFUL IF YOU'D SEND ME THAT LINK...I HAVE SPENT THE LAST 2 DAYS FOR OVER 10 HRS ATTEMPTING TO FIND THE INFO OR VID I MAY NEED TO BE SUCCESSFUL...
once again thank you for the help...
Click to expand...
Click to collapse
Physically type down in a reply to @BadUsername, exactly what is written when you are fully booted into download mode. Everything in the upper left of the screen where it starts with "Odin Mode" in red all caps. Someone is helping you and they can't continue to help you, unless you help them first with that info.

BadUsername said:
You're on mf1 still.
Flash this in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using this guide, section 5:
http://forum.xda-developers.com/showthread.php?t=1762709
Then use this to root your phone again:
http://forum.xda-developers.com/showthread.php?t=2332825
After this, I'd unlock the bootloader with ez-unlock version 1.2 to make sure it's unlocked.
When you reboot, find sdm1.0.apk and fwupdater.apk and rename them to sdm1.0.apk.bak and fwupdater.apk.bak. Or use titanium backup and freeze both of them. Then you don't have to worry about an update being pushed to your phone.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Would those be appropriate to block if on rooted 4.1 currently and wanting to block the 4.3 update? Anything else to block/freeze?

andydumi said:
Would those be appropriate to block if on rooted 4.1 currently and wanting to block the 4.3 update? Anything else to block/freeze?
Click to expand...
Click to collapse
Here is my list:
If the OTA already downloaded, delete it here /cache/fota
To disable the OTA:
Rename or freeze the apps with Titanium backup:
otacerts.zip located in /etc/security - rename to otacerts.zip.bak
Rename fwupdate.odex, fwupdate.apk located in /system/app
and freeze SDM1.0 located in /system/app

Awesome thank you. And without TiBu? My wife uses the GS3, and I don't think she has a license for TiBu.
I guess just rename the first two with a file manager, delete the update and disable sdm1 in the app settings?

andydumi said:
Awesome thank you. And without TiBu? My wife uses the GS3, and I don't think she has a license for TiBu.
I guess just rename the first two with a file manager, delete the update and disable sdm1 in the app settings?
Click to expand...
Click to collapse
That would also work.
Sent from my SCH-I535 using Tapatalk 2