Okay guys, thank you soooo much for your time and patience, but finally after deleting and redownloading 23 different times, I finally got my phone rooted with s-off. You guys are all heroes in my book, thank you much!!
Thanks for keeping with it and congratulations
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
Put me in the list for people who successfully got my phone rooted!
Aside from my stupidy that added about seven hours to this (I thought my SD Card was internal memory for like three hours and used Unrevoked 3.32 at the beginning for almost two hours before I realized it), these instructions are pretty straight-forward for a noob such as myself and just wanted to say thanks again so...
Thank you! Also for the responses to my questions!
The Following 2 Users Say Thank You to Maverick812 For This Useful Post:
I used this thread to achieve root back in October. I was able to try various ROMs, from CM7 to MIUI to newer ICS alphas. I wanted to say thanks again.
For fear of messing with what I set up, I didn't get around to achieving S-Off until today. The instructions were, once again, easy to follow.
The downgrade was very easy. Just as noted as a possibility, the Unrevoked 3.32 did not, in the end get S-off. I had to flash the S-off tool in recovery, which was no problem.
Thanks!
The Following User Says Thank You to zerbrechen For This Useful Post:
Okay guys, thank you soooo much for your time and patience, but finally after deleting and redownloading 23 different times, I finally got my phone rooted with s-off. You guys are all heroes in my book, thank you much!!
way to go! do you have any idea what you may have done to finally get it working? you will be a hero to anyone with the same issue if your experiecnce can help figure it out!
Quote:
Originally Posted by Maverick812
Put me in the list for people who successfully got my phone rooted!
Aside from my stupidy that added about seven hours to this (I thought my SD Card was internal memory for like three hours and used Unrevoked 3.32 at the beginning for almost two hours before I realized it), these instructions are pretty straight-forward for a noob such as myself and just wanted to say thanks again so...
Thank you! Also for the responses to my questions!
Quote:
Originally Posted by zerbrechen
I used this thread to achieve root back in October. I was able to try various ROMs, from CM7 to MIUI to newer ICS alphas. I wanted to say thanks again.
For fear of messing with what I set up, I didn't get around to achieving S-Off until today. The instructions were, once again, easy to follow.
The downgrade was very easy. Just as noted as a possibility, the Unrevoked 3.32 did not, in the end get S-off. I had to flash the S-off tool in recovery, which was no problem.
Thanks!
awsome! 3 more incredibles saved from the gloom and doom of s-on
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
The Following User Says Thank You to scotty85 For This Useful Post:
I'm wondering why adb commands dont work for me anymore.
I even tired the simple "cd c:mini-adb_inc" in command prompt, and it tells me that the specified path isnt found. It's still there on my pc. It there a problem with my command prompt?
I want to try to push for apk files around and i don't have the slightest idea what i need to enter to be able to use those adb commands...
I'm wondering why adb commands dont work for me anymore.
I even tired the simple "cd c:mini-adb_inc" in command prompt, and it tells me that the specified path isnt found. It's still there on my pc. It there a problem with my command prompt?
I want to try to push for apk files around and i don't have the slightest idea what i need to enter to be able to use those adb commands...
You should be typing
Code:
cd C:\mini-adb_inc
If you are still getting it as an unknown path, first try navigating to that path using explorer, if it doesn't come up then the folder doesn't exist anymore.
If you are able to find the folder with explorer, look in the address bar, and double check the path with what you are typing into the command prompt. (it has to match exactly)
Sometimes you have to navigate the command prompt all the way back to the root of the C:\ first by typing
Code:
cd ..
until the prompt just says C:\
So basically, if you are getting the unknown path error, you are typing something wrong.
If you are still getting it as an unknown path, first try navigating to that path using explorer, if it doesn't come up then the folder doesn't exist anymore.
If you are able to find the folder with explorer, look in the address bar, and double check the path with what you are typing into the command prompt. (it has to match exactly)
Sometimes you have to navigate the command prompt all the way back to the root of the C:\ first by typing
Code:
cd ..
until the prompt just says C:\
So basically, if you are getting the unknown path error, you are typing something wrong.
wow, it's funny, cause I could have sworn that "cd c:mini-adb_inc" worked when i rooted my phone at the beginning of the year, but yeah, you're right. That forward-slash did it.
The Following User Says Thank You to soystat For This Useful Post:
When using the Windows command prompt (Win7), I had the same problem changing to the adb directory. I tried everything. Strangely, I simply renamed the folder to MINI and using the command:
cd C:\MINI
I was able to continue. Anyone know why I had to do that?
When using the Windows command prompt (Win7), I had the same problem changing to the adb directory. I tried everything. Strangely, I simply renamed the folder to MINI and using the command:
cd C:\MINI
I was able to continue. Anyone know why I had to do that?
Someone else had a similar problem, where they couldn't use the "dash (-)" and had to rename their folder also, I've personally never had the problem on windows 7, but it's not unheard of for Windows to get confused.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
Need some help! I followed everything just as it said and when it get's to hboot, it is saying PB31IMG.zip not found. I checked it with a file manager on the phone and it is saying .zip. At the hboot It's saying like 3 other things but it's to fast for me to read.
Edit: Got it working. Not sure what was going on but I ran through everything one more time and it worked! Thanks!
Last edited by Duke82ish; February 28th, 2012 at 07:52 PM.
Need some help! I followed everything just as it said and when it get's to hboot, it is saying PB31IMG.zip not found. I checked it with a file manager on the phone and it is saying .zip. At the hboot It's saying like 3 other things but it's to fast for me to read.
The file is on the ROOT of the SD card and the SD card is formatted to FAT32?
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
Need some help! I followed everything just as it said and when it get's to hboot, it is saying PB31IMG.zip not found. I checked it with a file manager on the phone and it is saying .zip. At the hboot It's saying like 3 other things but it's to fast for me to read.
Edit: Got it working. Not sure what was going on but I ran through everything one more time and it worked! Thanks!
A few things I encountered:
Case sensitive...pb31img.zip is not PB31IMG.zip is not PB31IMG.ZIP
If you downloaded your zip file on windows, the file could very well have been named PB31IMG.ZIP.ZIP. This is unlikely since you used file manager, so really this is for the benefit of others reading this thread.
Mountpoints in *nix are odd. Case in point, I can sometimes pull my SD card, do an LS in the terminal and it will list files as being mounted at /sdcard when the sdcard is not in the phone. Using your boot utility, unmount the sd card then remount the sd card, then the files should be visible.
Clear the caches (dalvik, adb) and user data.
Make sure you've fully formatted your SD card as FAT32 with 4KB sectors. A quick format won't do it.
After I got my phone rooted (yay), I tried to install cyanogenmod 7 nightly, and nothing worked right. I did stable, and everything worked wrong (didn't even have phone). Once I did a full format, cleared my caches, mounted my card and flashed the ruu, my phone worked like a champ. (took me another 10 minutes to figure out that I had to then flash the google apps.)
I love my new phone. I would have rooted it a long time ago if I knew it could be this good.
The Following 2 Users Say Thank You to acask For This Useful Post:
Hello, So I'm trying to root my droid 1. I couldn't get Unrevoked to work (even after factory reboot I still got "is your firmware too new" erro). So I'm trying the "downgrade with adb" method (from the beg. of this thread. I'm stuck at the $ prompt. The command su gets me "permission denied" and nothing pops up on my phone.
Any help?!
Thanks in advance
(btw -- 1st time posting here, so sorry if I'm breaking conventions I'm not familiar with)
Hello, So I'm trying to root my droid 1. I couldn't get Unrevoked to work (even after factory reboot I still got "is your firmware too new" erro). So I'm trying the "downgrade with adb" method (from the beg. of this thread. I'm stuck at the $ prompt. The command su gets me "permission denied" and nothing pops up on my phone.
Any help?!
Thanks in advance
(btw -- 1st time posting here, so sorry if I'm breaking conventions I'm not familiar with)
You can't downgrade until you root... you either have to run the version of unrevoked that is linked in the original post (3.22) or use the zergRush method which is in post 2. Do NOT use the version of unrevoked from their website.
Re read the first post very carefully and follow the directions EXACTLY and you'll be fine.
Thanks so much for the reply! So I'm into the ZergRush, I've just typed in "adb reboot bootloader" and now the phone is resting at the FastBoot/BootLoader screen and on my PC the Found New Hardware Wizard wants to help. Do I cancel the wizard, or help it navigate to... (where?), or is there something on my phone I should do?
Thanks again in advance (obviously I'm a newbie...)
Quick question! So I successfully rooted and gained s-off today!
...however, I was an idiot and used the stupid proprietary Verizon backup assistant for all of my contacts and therefore couldn't access them through CyanogenMod.
Long story short, I ran the backup made before downgrading, but as I booted the phone up into bootloader, I noticed I was still s-off!
...
Shouldn't I by all means be s-on and have to run all of the downgrading/unrevoked 3.32 stuff again?!? Or maybe I'm misunderstanding something...
I know this isn't really relevant to most issues on the thread, but I figured I'd ask since you guys seem to know your stuff...great job on the thread btw!
Quick question! So I successfully rooted and gained s-off today!
...however, I was an idiot and used the stupid proprietary Verizon backup assistant for all of my contacts and therefore couldn't access them through CyanogenMod.
Long story short, I ran the backup made before downgrading, but as I booted the phone up into bootloader, I noticed I was still s-off!
...
Shouldn't I by all means be s-on and have to run all of the downgrading/unrevoked 3.32 stuff again?!? Or maybe I'm misunderstanding something...
I know this isn't really relevant to most issues on the thread, but I figured I'd ask since you guys seem to know your stuff...great job on the thread btw!
Your phone will stay s-off until you purposely turn it s-on by flashing a specific file through recovery.
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
prolly best bet for your contacts is to follow verizons directions to create a file of your back up asst contacts,then import them into gmail. once youve gotten all your contacts as gmail contacts,make sure you always save them that way when you add new ones.
that way,whenever you get a new android device(or change your rom ) all your contacts will come back simply by signing into youre google account
The Following User Says Thank You to scotty85 For This Useful Post:
Thank you so much for this invaluable information. I am pretty much a novice and did this in a few hours! I have one question, after I restored from recovery mode and then from Titanium backup, I am receiving the following message:
Quote:
System updates
Android Software Update (4.08.605.2)
Downloaded and verified 87.7 MB
This Software Update includes additional improvements to your recent software upgrade for your DROID Incredible by HTC. You will be unable to use your device or make emergency calls for the duration of the install, which is expected to take 10 minutes but could take longer. For more information, please visit: www.verizonwireless.com/droidincrediblesupport.
<Restart & install>
Where "Restart & install" is my one and only option. I have been ignoring it and had that before root and s-off. After my back up restores I still have superuser permissions and s-off, so I'm wondering, should I let it update. I searched the thread before I sent this message and didn't find any answer to my question. Your help is greatly appreciated!
Thank you so much for this invaluable information. I am pretty much a novice and did this in a few hours! I have one question, after I restored from recovery mode and then from Titanium backup, I am receiving the following message:
Where "Restart & install" is my one and only option. I have been ignoring it and had that before root and s-off. After my back up restores I still have superuser permissions and s-off, so I'm wondering, should I let it update. I searched the thread before I sent this message and didn't find any answer to my question. Your help is greatly appreciated!
Yeah, see that, thank you! and does anybody know anything about "Wi-Fi Error" after root? I can't turn it on from settings, and (and I appreciate answers to all root questions) will I/should I even try to use HTC Sync since I rooted.