Database Develop

How To: Get back to stock 2.1, stock recovery and S-ON for an RMA

The other day my phone's touchscreen developed a dead spot. Verizon was kind enough to send me a "Like-New" replacement and requested that I return the old phone. The only problem with that was I had hacked the hell out of it and didn't want them to see what I did and charge me.
I had rooted the phone, installed Clockwork Recovery, set S-OFF with Unrevoked Forever, updated to the latest radio and installed all kinds of different ROMs before finally settling on CM6. Now I had to find a way to install either stock 2.1 or stock 2.2 with the correct radio for either one, flash back the stock recovery, and finally set the phone back to S-ON. If you find yourself in a similar situation, you'll probably want to read this instead of spending 6 hours pulling your hair out, like I did. Here's what I finally came up with:
STEP 1: Get ADB Running.
Make sure you have ADB up and running. If you're rooted with a custom ROM and you don't have ADB running you have more problems than I can help you with. If you use a Mac, see Step 1A below to make things a little easier when using ADB.
Step 1A: (Mac Users Only) Make Your Life Easier.
Let's add the android SDK tools folder to your .bash_profile. What does this do, you ask? It makes it so that you can run any ADB commands without having to be in your SDK Tools directory. How do we do this?
Open a terminal window. Type
Code:
nano ~/.bash_profile
This will open a text editor in the terminal and create a new text file in your home directory called .bash_profile, which will be invisible in the Finder.
Enter the following:
Code:
PATH=$PATH:/Applications/Utilities/android-sdk-mac_86/tools
export PATH
!!IMPORTANT!! I have my "android-sdk-mac_86/tools" folder inside my "Utilities" folder, which is inside the "Applications" folder. If you have your android sdk folder somewhere else you will have to change the above text to reflect the proper path to your folder.
Hit ctrl-x. Not cmd-x, ctrl-x.
The editor will ask you if you want to save changes. Press "Y".
It will ask you what you want the file name to be. Just press enter, as we've already named it .bash_profile.
Quit and re-open terminal.
You can now use any command in the SDK tools folder from any directory.
STEP 2: Install Fastboot.
Make sure you have the HTC Fastboot tool installed. If you don't, you can get it here: http://developer.htc.com/adp.html
Download it for your particular operating system.
Another tip for Mac users: Once you download and unzip it, rename it from "fastboot-mac" to just "fastboot", then place it in your SDK Tools directory.
STEP 3: Downgrade To 2.1 With Old Radio.
We now need to downgrade our radio and get back to stock 2.1. The best way I found to do this was explained in this thread: http://forum.xda-developers.com/showthread.php?t=757927
Download the zip and follow the instructions.
Hat tip to Berzerker7 for the write-up, and aiccucs for putting together the zip file in that thread.
The next step will be a little bit of backtracking, but it's mostly painless, and it still seems to be the easiest way to do this.
STEP 4: Set NAND To S-ON.
We now need to set the NAND to S-ON. Problem is, in step 3 we flashed the stock recovery back onto the phone. Not a huge issue.
First, go to unrevoked.com and download unrevoked3. Run it. This will re-root the phone and install Clockwork recovery. Once this is done, go here: http://unrevoked.com/rootwiki/doku.php/public/forever and download the unrevoked-forever S-ON Tool.
Copy this file to your SD card and rename it "update.zip"
You can do that with adb like this:
Code:
adb push /path/to/unrevoked-forever-son.zip /sdcard/update.zip
Reboot into recovery and use Clockwork to apply the patch, which will set the NAND back to S-ON.
STEP 5: Get The Phone To Accept Stock Recovery With S-ON
This was the biggest problem that I ran into. The phone would regurgitate every zip I found which contained a stock recovery when the phone was set S-ON. I finally found a way around that.
First, download this PB31IMG.zip file: http://d01.megashares.com/index.php?d01=CHoQD3B
This IMG file was posted by Diego Mejia, on a youtube video he uploaded. Thanks to Diego, his work was very helpful in this process.
Here's the catch: in order to apply this PB31IMG.zip, we need to downgrade HBOOT or we'll get an error, due to the fact that we had set S-ON in the previous step.
Here is a link to a post on androidforums.com with an attached zip file called "revert.zip": http://androidforums.com/incredible-all-things-root/123816-how-revert-back-earlier-version-hboot.html
Credit is due to adrynalyne for coming up with this process and posting the files, I just tweaked his instructions a bit to make them work for me.
Once the "revert.zip" file has been downloaded, follow adrynalyne's instructions on what to do with the files. Reposted below:
Boot the phone into Clockwork Recovery.
Go to partitions, and mount data.
Type the following commands in a terminal window:
Code:
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Watch for your phone to reboot to a silver HTC logo.
Then type:
Code:
fastboot devices
Verify your device shows up/responds/etc.
Click to expand...
Click to collapse
If the "fastboot" command works you should see an "H" followed by a string of random numbers and letters. So far, so good.
STEP 6: Reapply Stock 2.1 With Stock Recovery.
Once you've run the "fastboot" command successfully, go ahead and pull the battery. Leave the phone off. Go back to the PB31IMG.zip you downloaded in step 5, and copy it to the root of your SD card. Put the SD card back in the phone and boot it into recovery. If you've done all this correctly, the phone should recognize the PB31IMG.zip as valid and ask if you want to apply it. Do so. This will reflash the stock 2.1 ROM with the stock recovery while the phone is set S-ON. You can now send your phone back to Verizon.
STEP 7: Profit.
--B

Hey Mods, any chance of a sticky?
--B

There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.

Berzerker7 said:
There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.
Click to expand...
Click to collapse
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B

xraystyle said:
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B
Click to expand...
Click to collapse
Not reading your topic. lol

I found it easier, to just since your rooted already, just put it to S-on, then run the stock RUU for 2.2. and your done in two steps. no need for all the codes.... I just did it, got my refurb yesterday,...

Thanks for the informative post! This will help a lot of people in the future.

[TUT] HTC Unlock/Recovery/Rooting *Noobs*

​
The Ultimate guide on how to do everything for noobs
Anyone taking these steps please be aware, you do this as your own choice/Risk....If you have anything important on your phone, back it up right now before you proceed....as everything will be wiped by the bootloader unlock!
Bootloader unlock.
Download this >http://www.mediafire.com/download.php?uma19r3pysr93dr
Unzip into a new folder on your c: called Android (C:/Android)
Plug your Phone into Computer/PC and select charge only.
Follow the guide precisely on HTC
1. Go to HTCDEV website: http://www.htcdev.com/bootloader/
2. Click on "Begin Unlock Bootloader" (create a user if you don't have one)
3. follow the instructions step 1 through step 10 on htcdev.com
4. In step 10, when posting your token, make sure you remove the blanks preceding each line
5. After you receive your Unlock_code.bin in email, follow step 11.
6. Now your rezound should reboot and you have your bootloader unlocked.
so you have updated the HBOOT and unlock bootloader....
Good now for the next bit.
If by chance you cannot unlock via HTC Dev please tell me as i maybe able to help you on that.
I require knowing which RUU you have installed, this u will find out by using HTC Dev.
Using HBOOT 1.0.7 and updating should be easy and fast.
Installing CWM 5 (Recovery Menu)
Please also read my orther thread on recoverys...it hold same details with extras >http://forum.xda-developers.com/showthread.php?t=1791707
This is a program installed into the phone itself.
This allows you to do pretty much anything you want.
Main things are Backup and restore of your device.
Flashing of custom Roms
Here is the recovery file >http://forum.xda-developers.com/attachment.php?attachmentid=852074&d=1326296914
Save the recovery.img and flash_image in the root of your adb folder.(this means C:/Android)
Now using DOS CMD window
goto C:/Android
*hint, copy the txt in these windows into your DOS window and press enter....it saves time and spelling errors*
DOS txt
Code:
adb reboot bootloader
it should now reboot and show Fastboot USB mode
DOS txt
Code:
fastboot flash recovery recovery.img
from the hboot menu, go to recovery.
now if above doesn't work and you cannot get into bootloader to flash the cwm. follow this
pull out battery
insert battery
hold volume down key and press power at same time
Hboot will appear
scroll down and select bootloader option, press power.
and your ready now in fastboot usb mode
Rooting
Please note, this method is old, current methods are simply just flash a new rom!
All roms come Pre Rooted with all apps required to run with root (Superuser)
For details in these check out the Android Development forum in our salsa section.
or go here>http://forum.xda-developers.com/forumdisplay.php?f=1043
Download this file >http://www.mediafire.com/download.php?pypn6v69o0vnvl9
(This is outdated somewhat and requires updating via Google Play)
place this file on the base of your sd card.
Now goto your new recovery menu.
use this cmd from DOS Windows
Code:
adb reboot recovery
it will reboot automatically
1-Select Install Zip from SDcard
2-Choose Zip from SDcard
3-Find Root.Zip on the SD card
4-Scroll upto Yes-Install Root.zip
it will now flash the root.zip
5-Go back
6-Reboot System Now
Now from here you will have done the following
Unlocked your bootloader
Flashed recovery system
Rooted your stock device.
if by any chance you make a mistake which is not very likely, but odd chance u do...redo the steps per section till you get it right.
WIKI
Root-2 meanings
System root giving superuser access pr SU
Root of SD - meaning base of sd no folders
ADB Android debug bridge - used with dos commands when phone is plugged into computer via USB cable
extra Utilities are Java SDK
>http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download and install accordingly to instructions given.
this gives access to more functions via ADB

thanks
thank you sir, you are a genius. i was stuck in 'adb'. and dont know what does it mean. got it cleared from geek.com . would like to suggest that please also add things like 'installing utilities from android sdk platform, root means the root directory of system(usually c:\ )for amateurs like me.
nevertheless it's really a useful post.... hats off to you and developers of this site!!!!!!

Save the recovery.img and flash_image in the root of your adb folder
MOD EDIT: No need to quote the whole post when asking a question
"Save the recovery.img and flash_image in the root of your adb folder"What does this mean root of adb folder???and from where will i get this file- flash_image??

raghavaggsss said:
"Save the recovery.img and flash_image in the root of your adb folder"What does this mean root of adb folder???and from where will i get this file- flash_image??
Click to expand...
Click to collapse
read the OP, the files are in the link provided!
>Here is the recovery file >http://forum.xda-developers.com/atta...4&d=1326296914<
can u also trim down the quotes too....being as the first post is big...

Files given by your link
Do we have to download these files from htcdev.com or can we just use your files posted here????
the files are:
adb.exe
AdbWinApi.dll
fastboot.exe

kashttl said:
Do we have to download these files from htcdev.com or can we just use your files posted here????
the files are:
adb.exe
AdbWinApi.dll
fastboot.exe
Click to expand...
Click to collapse
i've hosted the files here in my thread so u don't have to get them from HTCDEV.

Stuck at step 8.. please help!!!!
I am stuck at step 8
It's supposed to show some block of text
Which didn't come up.....
Instead I got a message saying--
<Waiting for the device>
Please help me out....

kashttl said:
I am stuck at step 8
It's supposed to show some block of text
Which didn't come up.....
Instead I got a message saying--
<Waiting for the device>
Please help me out....
Click to expand...
Click to collapse
settings>applications>Development>Debugging mode (Select this option)
Now retry the cmds.

already in debug mode
BigBearEvo said:
settings>applications>Development>Debugging mode (Select this option)
Now retry the cmds.
Click to expand...
Click to collapse
its already in debug mode...... Still not working

kashttl said:
its already in debug mode...... Still not working
Click to expand...
Click to collapse
only thing left is your hboot update!
do u have locked or unlocked in pink?

I dit it all
BigBearEvo said:
only thing left is your hboot update!
do u have locked or unlocked in pink?
Click to expand...
Click to collapse
What is
locked or unlocked in pink
Click to expand...
Click to collapse

kashttl said:
What is
Click to expand...
Click to collapse
in your hboot menu or bootloader menu, at the top of the screen it will show up locked or unlocked in a pink background, u can't miss it!
do u have this locked or unlocked?

Unlocked or locked....
It's locked..... It shows something like
LOCKED(OOW)
Click to expand...
Click to collapse
What could i do now.......!!!

kashttl said:
It's locked..... It shows something like
What could i do now.......!!!
Click to expand...
Click to collapse
unlock it...simple...without going to htcdev and following the steps which you didn't do, i cannot help

Another problem(the CWM recovery part)........ when i use the adb reboot bootloader cmd command.... it show device not found.........What can I do........!!!

kashttl said:
Another problem(the CWM recovery part)........ when i use the adb reboot bootloader cmd command.... it show device not found.........What can I do........!!!
Click to expand...
Click to collapse
select debugging mode in settings>application>Development
if this is unchecked, check it. then try cmds.
if this is already enabled and it still dont work on cmds then reboot into hboot yourself.
to do this, pull out battery, insert battery, hold volume key down while pressing power on button, hboot will appear, now wait...then select bootloader, and then fastboot usb will appear.
now follow cmds to install recovery
again all this is explained in main thread

SuperUser?
Hi BBE,
Followed your tutorial and was successful at every step. But one thing that is bothering me (or maybe I messed up at some step) is that I still do not have the Superuser (Su) rights. I used "Root Check Basic" and it says I have Root access. But when I try to run "Link2sd" or "Titanium Backup" it says I do not have Superuser rights. Is this method supposed to give us Superuser rights? If yes then what should I do now? If no then how can I get Superuser rights for my HTC Salsa?
Thanks.
Zaeem

Look in the apps list and you should see a pirate like app icon. If you do open app up and update it. This should rectify the su problem. If not.gimme a shout
BB is using Xparent Tapatalk ICS Blue

BigBearEvo said:
Look in the apps list and you should see a pirate like app icon. If you do open app up and update it. This should rectify the su problem. If not.gimme a shout
BB is using Xparent Tapatalk ICS Blue
Click to expand...
Click to collapse
Yea I did update it myself and now I have Su on my Salsa . However the binary is out dated and when I try to update it, it gives me 'failure' status. Downloaded the SuperUser binary installer fix from Market but still getting the error. Any help with that? (I think I am good even with the out dated binary though)

ZaeemRaza said:
Yea I did update it myself and now I have Su on my Salsa . However the binary is out dated and when I try to update it, it gives me 'failure' status. Downloaded the SuperUser binary installer fix from Market but still getting the error. Any help with that? (I think I am good even with the out dated binary though)
Click to expand...
Click to collapse
ok goto market, download, SuperSU looks like a large blue hashtag lol.
install that, update it etc, see if that runs, if you get successful updated binary, reboot the phone. u can run with both SU apps, but you would be better removing the old Su in favour of the new one...im gonna look around for a root.zip with new Super Su in there

[HOW-TO]Unlock, Root and install CWM step by step

This HOW-TO is meant for individuals who like to do things manually and see each process as they occur, versus using a toolkit. I prefer manually unlocking/rooting as I can confirm each step visually and I believe it makes for a more educational experience. Familiarity and confidence with fastboot/adb can be beneficial later on for restoring/troubleshooting/flashing etc down the road.
Unknown at this point if OTA updates will install after flashing CWM. There may be a check file in the OTA that could prevent installation if modified file structure is detected. I’ll edit when I confirm. At any rate, not really an issue as you can flash the OTA yourself as someone on XDA will most likely post it up, or you could re-flash the stock recovery using fastboot which you will now be comfortable with after using this guide! Additionally, if an OTA causes you to lose root you can revisit the appropriate steps to flash SuperSU again.
There are several ways to do these procedures, and I’ve certainly taken the long way on some of them. So by no means am I claiming this to the best or most efficient method, but my hopes are to make things a little more clear and simple based off some of the questions and challenges I’ve seen in a few threads.
This how-to was written for Windows and uses adb and fastboot for installation.
Please let me know of any corrections, additions or errors. Many thanks to the members and devs who made these files available.
1. Download all of the following files and place them in the same directory. I will note whether you need to extract them or not.
Download and extract platform-tools-v16.zip from here: (thanks to efrant)
http://forum.xda-developers.com/showthread.php?t=1626895
Download and extract [ADB/FB/APX Driver] Universal Naked Driver 0.72 from here:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Download SuperSU from here: (look for UPDATE-SuperSU-v1.25.zip or current version)
http://forum.xda-developers.com/showthread.php?t=1538053
Download ClockworkMod from here: (look for Galaxy Nexus 7, Download Recovery 6.0.3.1 or current version – Recommend non-Touch as of ver 6.0.10, some reported issues with the Touch version)
http://www.clockworkmod.com/rommanager/
2. Now we will install the drivers and verify they are working. If you cannot verify drivers are functioning in both normal boot and recovery you need to stop and figure out what you are doing wrong. Proceeding further would be pointless. If you are having trouble, visit the Naked Driver thread listed above or here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
a. Make sure you have USB debugging enabled on your Nexus: setttings ->develop options ->USB Debugging.
b. USB connect your Nexus to your Windows pc. If you get a notification for unknown/driver not found, look in Device Manager for the exclamation point, and right click for update driver software, then browse my computer, then point to where you saved and extracted the Universal Naked Driver folder. If you get a warning from Windows complaining the driver is not signed, hit ‘Install driver anyway’. After the driver installs, you should now have ‘Nexus 7’ listed under ‘Portable Devices’ with no exclamation point.
Now we will verify using adb. You will need to launch a command prompt from the directory you saved all the files from step 1 to. Easiest way is to navigate to the directory via file explorer, then hold down shift and the RIGHT mouse button, and select “Open command window from here”.
In the cmd prompt, type:
adb devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again. You should see something like:
List of devices attached
945d3339495 device
if instead you see:
List of devices attached
945d3339495 offline
then most likely you need to look on your nexus for a notice to allow the connected computer permissions to use usb debugging. If you don't see a notice, disable/enable usb debugging in "Settings -> Developer options" and then you should get the prompt. You should select 'remember this computer', if not you will have to do it again upon reboot.
c. Now we need to reboot into the bootloader and load the drivers again. So type:
adb reboot bootloader
and your Nexus should reboot into the bootloader. My laptop found the driver on its own, note that in Device Manager it is now listed as ‘Android Device’ instead of under ‘Portable Devices’. If your system does not find the driver, follow the same steps as above to update your driver after you located the exclamation point in Device Manager.
Now we will verify that the driver is installed correctly while in the bootloader. Again from a command prompt opened from the directory where you saved all the files from step 1, type:
fastboot devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again.
3. Perform device unlock. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! Please backup accordingly.
Your Nexus should still be in the bootloader. Type:
fastboot oem unlock
Your Nexus will prompt you to accept. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! After a short moment, the device should report unlocked under “lock state”. Reboot device by typing:
fastboot reboot
After rebooting, sign in, etc.
4. Copy over SuperSU . In windows explorer locate the UPDATE-SuperSU-v1.25.zip and copy it to your Nexus internal storage area. Don’t put it any of the folders, just dump it in there. Now reboot into the bootloader again by typing:
adb reboot bootloader
5. Flash CWM. Once in the bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
after you get ‘finished’ from the command window, reboot your Nexus into CWM recovery by navigating with the volume buttons to ‘recovery mode’, then press power button.
6. Root Nexus. Using the volume keys, navigate to ‘install zip from sdcard’ and hit the power button. Now select ‘choose zip from sdcard’ and hit the power button. Navigate down to UPDATE-SuperSU-v1.25.zip’ and hit the power button. Select ‘Yes’, hit power. Once done select ‘go back’, then ‘reboot system now’.
Congrats, you’ve unlocked and rooted your Nexus!
Now at this point CWM recovery may or may not still be present on your device. There have been mixed reports on whether it will ‘stick’ the first time you flash it. The stock ROM has a check file that will replace CWM with the stock recovery upon reboot. To determine if CWM is still present simply reboot into recovery and see if it is there. Type:
adb reboot recovery
Obviously if you see the droid with exclamation point CWM did not stick. If you have no need for CWM, and simply wanted root you could stop now. Wait a few minutes and your device will reboot on its own and you are all done.
However, if you desire CWM then proceed on.
7. Rename recovery-from-boot.p to prevent stock recovery re-installation. Your Nexus should be booted normally at this point.
a. Go to the Play store and install ES File Explorer File Manager. Under settings enable ‘up to root’, ‘root explorer’, and ’mount file system’.
b. Navigate to /system and rename:
recovery-from-boot.p
to
recovery-from-boot.bak
by long pressing and selecting ‘rename’. Note: Be careful while navigating your device with these options enabled, a typo or slip-up could cripple your device and require a restore. I suggest once this rename is competed to disable the above options to avoid any mistakes in future exploring.
8. Flash CWM again.
a. Reboot into bootloader by typing:
adb reboot bootloader
b. once in bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
c. reboot device by typing:
fastboot reboot
d. verify CWM stuck by rebooting into recovery:
adb reboot recovery
And that should be it!
Some additional notes: CWM does make notice on rebooting with a message ”ROM may flash stock recovery on reboot. Fix? This can not be undone”. I don’t know what CWM will do there, so I prefer to rename the recovery-from-boot file so that I could easily restore it if I wanted. But perhaps that is what CWM does, although the message persists even after I renamed the file. Maybe someone could clarify this.
Hope this helps some people out in enjoying this great device even more, thanks for reading.

4.1.2 and 4.2.1 updates...
Thought I would revisit the thread as we've had two updates since I wrote the above. I installed 4.1.2 OTA with no problems but as expected, I lost root and CWM.
Because I'm lazy, I didn't worry over it much and then 4.2.1 shows up and also installed perfectly. Finally got around to getting root back and here are the steps I used.
Notes:
* Need to make sure drivers are correctly installed. See first post.
* I never really used CWM so I elected not to permanently install it this time.
* This update is a brief synopsis of how I got root back. If the steps are not clear, review the first post as the procedure is very similar.
1.) Ensure USB debugging is still enabled. On 4.2.1 "Developers options" are hidden by default. To enable simply tap "Settings > About tablet > Build number" 7 times. Back out and "Developers options" should now be available. In my case USB debugging was still enabled.
2.) Download SuperSU v0.99 and CWM 6.0.1.9 from links in first post. I used non-touch version of CWM.
3.) Transfer SuperSU over to internal storage of your Nexus. Be sure you know where you dumped it.
4.) Reboot into bootloader: adb reboot bootloader
5.) Temporarily boot or permanently install CWM so we can install SuperSU zip.
for temp boot type: fastboot boot recovery-clockwork-6.0.1.9-grouper.img
for perm install type: fastboot flash recovery recovery-clockwork-6.0.1.9-grouper.img
6.) Once in CWM select:
a. install zip from sdcard
b. choose zip from sdcard
c. navigate to /0/ then wherever you put SuperSU
7.) Once finished back out and reboot system now. I selected "No" on allowing CWM to disable stock recovery. If you are only temp booting CWM then this likely won't matter either choice you make. If you perm flashed CWM then you may wish to choose 'Yes".
That should cover it. Thanks for reading, any questions or corrections be sure to let me know.

I have a question about this:
I rooted and installed CWM on my 4.2 N7, but now, then I try to install the 4.2.1 OTA update, I get this error:
Code:
assert failed: apply_patch_check("/system/lib/libweb rtc_audio_preprocessing.so", "bin_number", "big_number""),
E: error in /cache/jop40d-from-jop40c.zip
(Status 7)
It's wise to apply this if I already have a rooted+CWM N7?

Some root procedures, or third party apps like Titanium Pro can make changes to certain system files that will cause an official update to fail. In your case, it appears at least "rtc_audio_preprocessing.so" located in "/system/lib/libweb" has been altered.
The easiest solution is to flash the current factory image then root. You can find them here: https://developers.google.com/android/nexus/images#nakasi.
However, you will lose your data. So back up accordingly.
If that's not an option, you can try:
a.) figure out which app you have that caused the change, and see if it has a 'revert' option or if uninstalling will put the file(s) back to stock.
b.) find the unmodified contents of /system/app and /system/lib and replace yours. Needs to be from 4.2 in your case.
c.) find a modified manual update patch (either zip for CWM or .img for fastboot) that has been altered to ignore the integrity check.

Curious, just went looking for "rtc_audio_preprocessing.so" in a factory 4.2 system.img and can not locate it, or the lib/libweb directory. Perhaps a third party app made these additions and thus the integrity check is failing as the files are unknown/unaccounted for?
At any rate, I went ahead and sourced a 4.2 system.img and extracted the /app and /lib directories in case this helps you or anyone else searching along.
Extracted from: nakasi-jop40c-factory-6aabb391.tgz
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip.md5
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip.md5

so I factory-reseted my N7, but it didn't helped. I found the file /system/lib/libwebrtc_audio_preprocessing.so so I tried to replace it with the file you posted (thanks btw!), but while using a console (su, then cp file.so file.so.backup) I get the error saying it's a read-only system, so I can't replace that file
any other idea?
EDIT: So I was playing around with the N7 (although I can really remember, I think I formated /system ?):
So, yeah, I actually formated /system for some unknown reason and there is no OS to boot, so I'm downloading at 25 KBps (yes...I know) and I'll be installing the JOP40D version for the N7.

ah, so the file is actually:
/lib/libwebrtc_audio_preprocessing.so
not
/lib/libweb/rtc_audio_preprocessing.so
That makes a little more sense. On cp over the original file, as you discovered the /system partition needs to be remounted as writable before you would be able to make changes. You could easily accomplish this with one of the root file explorers from the market. I use "ES File Explorer" as its free. Then simply copy over your file.
Or if you prefer adb: mount -o remount rw /system
Regardless, you are starting over from scratch so no worries. One of the things I love about this device is the option to start fresh-from-factory with minimal fuss.

igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA

cub0ne said:
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
Click to expand...
Click to collapse
I am also on 4.2.1 unlocked and rooted with wugfresh toolkit. I downloaded CWM from the play store, the app can download the latest CWM recovery and flash it for you. That is what I did, All I have used CWM for is a nandroid backup, but have booted into recovery and wiped cache and fixed permission
Has anyone had issue is SuperSU and CWM running Fix Permissions in the CWM app? I get an error...

Thank you!
Thank you very much for the excellent guide, your explanations were very clear!
It was a lot of fun following it, and I am very happy for choosing this guide over the 'one-click' toolkits.

I'll give it a try
After trying a "all in one toolbox" to unlock and root I think I'll give this a shot. I got stuck at not being able to root and like your OP said, doing it manually would help with the learning curve.
Quick questions that has popped up is.
Do I lock my bootloader back to use your guide?
I've noticed drivers I have in device manager have different names. Does this mean there are dif drivers that do the same thing? Should i delete them and use the ones in the OP?

Late response, but I'll answer for future users following this thread...
Once your bootloader is unlocked by any means, no need to relock in order to follow this guide. We simply have to have it unlocked so we can gain root
Drivers are probably the most common issues people have in any instance of trying to interact with their device. While its not imperative that the names are the same, what is most important is that you can communicate with the device. There really isn't the right or wrong driver name, just that the driver works! Having said that, if you are wondering whether you have the correct drivers installed, simply follow the steps and attempt a "adb devices" or "fastboot devices" command depending on your device status as is outlined in the tutorial. If you do not have the appropriate response, then you need to stop and determine the issue.

Update after OTA 4.2.2
Lost root as expected, and followed procedure in post #2 to gain root back. Also updated OP file versions to current as of this post as they all worked successfully.
Only thing I would note: If you get a "offline" notice after trying 'adb devices', be sure to check your nexus for a notification to allow the connected computer access for USB debugging. If you don't see one, go to "Settings -> Developer options" and disable/enable USB debugging and it should pop up. I don't remember this behavior when I first wrote the tutorial, so it may be something new for 4.2.2. After reboot it will require approval again, so you may wish to select 'remember this computer'. I added this note in the OP as well in the appropriate step.

s-off

how to gain s-off on windows xp????

Download a Linux startup disk....
Sent from my Vivid 4G using Tapatalk

jerryj3000 said:
how to gain s-off on windows xp????
Click to expand...
Click to collapse
The process is not the easiest - but it can be with your patience and full attention. When I had my HTC Raider (Canadian version of the Vivid), I had collected all the info needed to get my phone rooted/bootloader/s-off/recovery from right out of the box. I will paste it all below. I think that when it mentions things like the RUU/Stock, you should use an appropriate one for your phone model. Not that the instructions below start with a ICS stock RUU!
I think the forums for this phone have quieted down a bit, so links may be dead now. That said, contact me if you need any of the files mentioned. I probably have them all archived.
As for S-Off procedure, I remember when following all of the threads that it was very important to read and follow every instruction exactly. I had missed a small step and I could not get it done. Eventually I caught my mistake, tried again, and got S-Off with no problems. I had done it on WinXP (or Win7 maybe).
If any of the instructions below contain errors, please let me know and I will update! I am not responsible for anything bad happening to the device... this is simply a collection of all of the great posts on this forum.
*** I understand that juopunutbear/unlimited.io team do not support the Windows versions of their tools any more (specifically I'm referring to ControlBear that I used to successfully S-OFF my phone.). They mention on their site to only use the latest tool (linux only), and have asked people to NOT bundle their old Windows-based software. Back then, the Windows version of ControlBear for ICS worked great for me (and I'm sure many others) in WindowsXP (or 7). I obviously won't attach or post links to it here, but I'm pretty sure I do have it archived, so contact me if you need it (and this obviously goes with the understanding that myself or them are not responsible for what you decide to do with it)
SECTION 1: STARTING FRESH WITH STOCK ICS RUU - note that RUU's will refuse to flash if you have already unlocked your bootloader. They will require you to re-lock your bootloader to flash.
To start, install the stock Bell ICS RUU (or even the Rogers ICS RUU is OK)
(RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed)
**You should use this opportunity to make sure you have the appropriate drivers installed on your computer so it can communicate with your phone via Fastboot, ADB, etc.!
Filename I used for drivers: HTCDriver3.0.0.007.exe
SECTION 2: UNLOCK THE BOOTLOADER
Next, unlock your bootloader.
-Sign up at htcdev.com
-Log in (make sure youre logged in!)
-Click Unlock bootloader
-Follow Instructions
Quick version of instructions:
1) Get phone into Fastboot mode
2) Run "fastboot oem get_identifier_token" in command line
3) Paste the token text into the htcdev page
4) you get emailed Unlock_code.bin from htcdev and link to next steps. Download that .bin file.
5) Run "fastboot flash unlocktoken Unlock_code.bin"
6) use volup/down on phone to choose yes and hit power to accept
7) Phone will data/cache wipe and start fresh
SECTION 3: S-OFF!
Now, do you want to S-OFF? It's painful but follow this word for word and it should work ok! It makes flashing roms and kernels a lot easier (no restrictions or workarounds needed). If you don't want to S-OFF, you can still do stuff like flash ROMS. You would just need to flash the kernel (that is appropriate for that rom) separately.
Note that S-OFF stays (i.e. if you install a stock RUU rom to your phone, it won't turn S-ON), so you only have to do this procedure once! But remember, if you have unlocked your bootloader, I beleive that RUU's will refuse to flash until you re-lock the bootloader.
1) Since your bootloader is unlocked, you are almost ready to S-OFF
2) Download the WCXJB ROOT PACK zip to your hard drive and UNZIP it (to, say, C:\temp\SOFF)
3) On your phone, make sure in your settings, USB Debugging is ENABLED in development
4) Turn off your phone, pull battery, put battery back.
5) Turn it back on by holding VOLUMEDOWN + POWER
6) Use the volume rocker and power button to select fastboot
7) Connect your phone to your PC
8) Open a command prompt window.
C:
cd \temp\SOFF
fastboot flash recovery wcxrecovery.img
9) Now you can reboot your phone
10) Download and put Vivid_CWM_Root_VER2 zip file on root of internal sdcard (aka NOT in any folders)
11) Boot into H-Boot like you did before (turn off phone, turn back on holding power + vol down), and use the volume rockers to go to "recovery" and press the power button to select it
12) Select "install zip from sdcard"
13) Select the VIVID_CWM_ROOT_VER2.zip to flash it. Then select "reboot"
14) You are now perma-rooted in preparation of the S-OFF procedure.
15) Turn off phone. Remove the SIM Card, the MicroSD card and the battery.
*-You will need a spare, formatted MicroSD card inserted. Do not use your regular MicroSD card because it will become corrupted/wiped during the S-OFF process!
*-Make sure your battery is fully charged!
*-You will also need a short length of insulated wire, so you can connect the 2 points during the S-OFF procedure.
*-Beside the MicroSD slot, is a small screw holding in a square panel.
The screw is covered by a VOID sticker. Removing this will void your warranty!
Put the screw and square panel somewhere safe.
Look at the JPG - it can be seen here: ( http://unlimited.io/images/wt_holiday.jpg )
The point indicated is what you need to ground (to the GND) point
You will of course do this with your short length of insulated wire!
Be sure the exposed part of the wire isnt so thick that it will touch other points!
The point is kind of small! The ground point is pretty big and easy to hit.
16) Put battery back in, and the SPARE MICROSD - not your usual MicroSD. Keep that safe.
17) Boot phone normally. Make sure (again) USB debugging is enabled in Developer options of the Settings!
18) *** I understand that juopunutbear/unlimited.io team do not support the Windows versions of their tools any more. They mention on their site to only use the latest tool (linux only), and have asked people to NOT bundle their old software. So for this step, all I can say is that back then, the Windows version of ControlBear for ICS worked great for me (and I'm sure many others) in WindowsXP (or 7). I obviously won't attach or post links to it here, but I'm pretty sure I do have it archived, so contact me if you need it (and this obviously goes with the understanding that myself or them are not responsible for what you decide to do with it)
19) Unzip the CONTROLBEAR zip to an easy to access path (like C:\temp\SOFF2)
20) Run controlbear as admin(windows) or root or using sudo on linux
Now get your insulated wire and get ready! Only connect the 2 points when instructed.
You will have to watch and wait for it to tell you.
Do not press any of the buttons on the phone during the process.
When you are instructed to do the wire trick, briefly connect
the point and the GND point using the wire, then wait approximately 1.75
seconds and then again connect the 2 contacts together.
Allow the program to continue.
Note: it may take several attempts of running the program in order to obtain the correct timing for the wire trick.
After doing the “wire-trick” your phone will reboot.
If you see the following message from ControlBear after doing the wire trick:
ErrorMsg: Still sober.
This means that you have been unsuccessful in implementing the wire-trick. Run ControlBear again.
The usual cause for this is that you failed to perform 2 clean contacts
or mis-timed the wire trick (or you didnt flash the perm root before
starting - but that was indicated above, so you must have done that.)
Your phone will reboot several times during the process, this is normal. ControlBear will tell you when it has finished whether successfully or not.
Once your phone is rebooted and back to normal, you can shut it off, pull the battery, put the square panel and screw back, and put your regular MicroSD back (as well as your SIM card).
SECTION 4: FLASHING CLOCKWORKMOD RECOVERY
(Optional but recommended! It's a great Recovery
Note that if you want to install WCX's rom, you will need to have WCX's recovery to flash it!
So don't use Clockworkmod at all if you plan on flashing WCX's roms.)
1) Put your phone into bootloader mode by turning it on with VOLDOWN+POWER.
(You will have to pull the battery to make sure the phone is fully off before doing this)
2) In the bootloader use the volume buttons to choose Fastboot
and hit POWER to select it.
3) Download Clockworkmod recovery (filename: CWM-beta2.img) and put it in an easy path
(like C:\temp\cwmrecovery)
4) Copy the adb and fastboot package to this same folder (c:\temp\cwmrecovery)
5) Go to command prompt and:
C:
cd\temp\cwmrecovery
fastboot flash recovery CWM-beta2.img
6) Clockworkmod recovery will be flashed. You can get to it by booting your phone into
bootloader mode, then choosing Recovery
SECTION 5: INSTALLING CUSTOM ROMS
If you S-OFF'd successfully, custom roms will install fully via CWM recovery (kernel and everything) so you will not have to flash the kernel separately.
If you don't want to S-OFF (or were unsuccessful with S-OFF and simply can't do it), it is important to understand that when you install a custom rom, the kernel for that rom (or whatever compatible kernel) needs to be flashed separately before or after the rom is flashed!! This will be addressed in the steps below.
1) Download the ROM you want (any ICS-based custom rom) and copy its .ZIP file to your MicroSD card
2) Get into Recovery mode (by booting phone into bootloader mode and choosing Recovery)
3) MAKE A NANDROID BACKUP OF YOUR CURRENT ROM - VERY IMPORTANT.
Just use the volume keys to go to Backup and choose it by hitting POWER.
This will help you get back to normal if the rom you install doesnt work
or if you just dont like the rom you have installed.
Make sure your MicroSD card has lots of space
The backup takes under 1 gig but you'll want more space for more backups/roms later.
Side note -- To restore your backup, go into recovery, do your 4 wipes (data/cache/dalvik/system) and
then choose backup/restore, choose restore and choose whichever backup you made from the
list. It will be date/timestamped.
***Note - if you did not S-OFF your phone, im not sure if Restore will flash your old/appropriate Kernel. You may have to flash that backups kernel (boot.img) after you do the restore (testing required - will this be necessary for S-ON phones?) If this is needed, general kernel flashing instructions are below starting at Step 10. Just make sure you are flashing your appropriate boot.img from your backup folder!
4) Now that the backup is done: In Clockworkmod recovery, go back to the main menu.
5) WIPES - Now we should do the 4 wipes. Choose Wipe Data, Wipe Cache, then go into Advanced, and choose Wipe Dalvik cache, then go into Mounts and Storage and choose Format /system.
6) Now from the main menu of clockworkmod, you can choose "install .zip from sdcard"
7) Choose the zip of the rom you wish to install (remember you copied it to your MicroSD card in step 1 so it should be listed.). When the install is finished, it may offer to reboot your phone. S-OFF users can go ahead. If you didn't S-OFF, you should probably pull the battery after choosing reboot.
8) IF YOU ARE S-OFF, YOU ARE DONE - IF YOU DIDNT S-OFF YOUR PHONE, YOU MUST CONTINUE SO YOU CAN FLASH THE APPROPRIATE KERNEL FOR THE ROM!
9) Get phone into bootloader mode by holding VOLDOWN+POWER. Choose FASTBOOT.
10) On your PC, open the ZIP that has the ROM you just installed. In the zip
will be a file called "boot.img".
***NOTE that some roms have multiple kernels to offer during the install process.
***Try to identify which boot.img is which kernel.
***If it doesn't matter to you, you should be able to pick any of them, as they were all packaged with the ROM because they are compatible with the ROM.
11) Copy the boot.img to an easy path (like C:\temp\whateverromkernel)
Copy your ADB/Fastboot package to that folder as well so you can run everything from there.
12) In command prompt:
C:
CD\temp\whateverromkernel
fastboot flash boot boot.img
13) The kernel will be flashed. Once it's done, you can restart the phone, and boot into the ROM!
**NOTE** if you're ever having trouble (whether s-on or s-off) flashing kernels (i.e. its saying its not allowed or something), your phone may have to experience the flashing of an 'insecure' kernel. kozmikkick's "stockish" kernel is an insecure boot.img that, once flashed, will allow you to flash whatever kernel's you want (you only have to flash the insecure boot.img once and then you'll be good)

From where can I download all the files required from this thread?
Thanks a lot!

desipan said:
From where can I download all the files required from this thread?
Thanks a lot!
Click to expand...
Click to collapse
Stock ICS RUU - should be easy enough to find one that is appropriate for your phone.
HTC Drivers - easy enough - search the forum or google
ADB and Fastboot exe's/files - also easy to find
wcxjb root - go to the superguide thread
Vivid_CWM_Root_ver2 - also in the superguide thread
Controlbear ICS zip for windows - discontinued - may be hard to find. google it and search a lot. If you cant find it, send me a PM, i may have it still
CWM-beta2.img - is here http://forum.xda-developers.com/showthread.php?t=1812452&highlight=cwm-beta2
Stockish kernel by kozmikkick - google him - its available on his dev-host page (youll want the "holiday" variant of the kernel)

LaZiODROID said:
Stock ICS RUU - should be easy enough to find one that is appropriate for your phone.
HTC Drivers - easy enough - search the forum or google
ADB and Fastboot exe's/files - also easy to find
wcxjb root - go to the superguide thread
Vivid_CWM_Root_ver2 - also in the superguide thread
Controlbear ICS zip for windows - discontinued - may be hard to find. google it and search a lot. If you cant find it, send me a PM, i may have it still
CWM-beta2.img - is here http://forum.xda-developers.com/showthread.php?t=1812452&highlight=cwm-beta2
Stockish kernel by kozmikkick - google him - its available on his dev-host page (youll want the "holiday" variant of the kernel)
Click to expand...
Click to collapse
Do you still have controlbear for vivid?

chindtown said:
Do you still have controlbear for vivid?
Click to expand...
Click to collapse
Yeah I found it. PM me your email or something and I will send.

same here, I have it for Win7 64-bit

[Guide] Get S-OFF hboot 1.55 after OTA or RumRunner failed (pouring 8)

Update 1: Before following this guide, you should try using the tool from http://firewater-soff.com to obtain S-OFF. If it does not work then proceed with the following guide.
I do NOT take any credit for this guide.
You can thank BD619 for walking me through all this and the updated command, Indirect for the original commands, benny3 for his awesome ROM, O.M.J for his 3.04.651.2 RUU and for his 3.05.651.6 Firmware, and RumRunner for their awesome S-Off tool!
Also, if anything goes wrong I can try to help you, but the only person responsible is yourself for not following the guide 100%. I have done this all myself and it worked like a charm.
After 3.04.651.2, attempting to achieve S-Off with rumrunner will fail every time after the pouring 8 stage. This guide will show you how to change your version number in order to install an older RUU. After installing the older RUU, then you can proceed to unlock the bootloader, download benny3's Stock ROM (Link Below), flash it after a full wipe, and finally run rumrunner again with success. From there you can optionally update your firmware (Link Below) and flash a ROM of your choice. Once official kitkat is released this guide will not work because the hboot will be different than the one found in the RUU
Changing the Mainver
Before doing all of this, you should backup all your applications and other data with Titanium Backup which can be found in the Play Store. Once your backup is complete, you must copy the titanium backup folder found on your internal storage to your computer because the RUU will wipe the entire storage. Copy any other things you may need including Photos, Music, and Downloads to your computer so you can restore them later. Also, make sure you are on hboot 1.55. I have not tested this with any other hboot but it is confirmed working on hboot 1.55.
1. Make sure the ADB drivers are set up properly in recovery. I used TWRP but other recoveries should be fine.
2. Boot into recovery and connect the phone to the computer.
3. Open the command prompt, and type in adb devices A string of letters and numbers should pop up. This is only to test the ADB drivers and make sure they are working properly.
4. Now type adb shell and press enter.
5. Now type this exactly as it is here echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160 with the quotes around the version number. After entering the command, it will say failed in the window but just ingnore that.
^^^I recommend you copy and paste to avoid typos.
6. Now enter adb reboot bootloader into the prompt. Your phone will now reboot bootloader and you should see your version number changed to 3.04.651.2.
7. As most of you may know, in order to install a RUU you must relock the bootloader, so click on fastboot on the phone and make sure it says fastboot usb. From here type in fastboot oem lock. Now the bootloader is locked.
Essentially, all we did up to this point is change the version number in order to trick the RUU into installing, and lock the bootloader also for the RUU to work.
Installing the RUU
8. Now you have to download the 3.04.651.2 RUU from http://forum.xda-developers.com/showthread.php?t=2508907. The zip or exe is fine. Do not use the decrypted version.
9. Once downloaded, put the phone into fastboot usb mode, and run the exe. If you downloaded the zip, follow the instruction in the link above to install it.
Flashing the custom ROM
10. Once the RUU is complete you will have to download benny3's ROM from http://forum.xda-developers.com/showpost.php?p=47048176&postcount=2. Either odexed or deodexed is fine. I personally chose odexed but it does not matter. Once downloaded make sure the ROM is not corrupt by matching the MD5 codes, or simply opening the zip.
11. We cannot install yet however because the RUU restored the stock recovery and the bootloader is locked.
12. Unlock the bootloader by following the instructions at http://www.htcdev.com/bootloader
13. Once the bootloader is unlocked we can now flash a custom recovery. Download TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/m7wls Once it finished put phone into fastboot usb, copy the TWRP img you just downloaded into the fastboot command prompt folder, open fastboot command prompt, and type in fastboot flash recovery recovery.img Replace recovery.img in the command with the actual name of the file.
14. Once the custom recovery is installed boot into Android and copy the downloaded ROM into the internal storage, boot into recovery and do a full wipe (Dalvik Cache, Cache, Data, System). Do NOT wipe the internal storage!
15. Go back and tap install. Select the ROM you placed in the internal storage in step 11. Once it is flashed clear the dalvik cache and reboot the system.
Running RumRunner
16. Before you run RumRunner, confirm all drivers are working correctly by testing adb and fastboot commands in recovery, fastboot, and the OS. Enable USB Debugging in developer options. Set auto sleep to the maximum of ten minutes. Go to personalize, and choose the no lockscreen setting. Go to settings, power, and make sure fastboot is NOT checked. Disable firewall and anti virus programs on your computer. Run the SuperSu app and make sure all SU Binaries are updated.
17. Once you've done everything above, you can download RumRunner 0.5 from http://rumrunner.us/downloads-2/ Make sure phone is connected to PC in ADB mode, and run soju.exe as administrator. Follow the onscreen instructions.
18. Once RumRunner is complete your phone will reboot to bootloader and report S-Off.
Updating Firmware
19. Now that you are S-Off, we can move on and update the firmware. Download the Full unmodified Firmware (fastboot flashable) from http://forum.xda-developers.com/showthread.php?t=2576995 Follow the instructions in the link for a guide on how to flash the firmware.
20. Once your firmware is updated if you reboot into the OS, your touchscreen may not respond. Do not worry about that it will be fixed soon.
Flashing A Custom ROM
21. Find a ROM of your choice in the android development section or the android original development section. The ROM you choose MUST be a Sprint ROM.
22. Copy the ROM to your internal storage, reboot to recovery. and do a full wipe (Dalvik Cache, Cache, Data, System). Again, do NOT wipe the internal storage!
23. Once the wipe is complete, flash the ROM you chose and clear the dalvik cache. Reboot system and you should be good to go. Remember, the first boot takes a bit longer than usual. Give it a good ten minutes before getting worried.
24. At this point you could copy your titanium backup folder back into the internal storage. Install titanium backup from the Play Store, open it, go to menu>preferences, scroll down to backup folder location, tap it and find the backup folder you just copied to your storage. Now you can restore all the apps and data you backed up. Also, you can copy all the other things you backed up to the computer.
I know this is a long guide, but the process above works 100%, and I tried to include as many details as possible. If you have any suggestions, please let me know. Also, if anyone runs into any problems, post it in the comments and maybe someone can help you.

Nicely done
This is the command you should copy and paste into your cmd window for step 5
Code:
echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
As stated below please use at your own risk this is a VERY dangerous command if you don't know what you are doing!!!

Thanks!
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life

jluca98 said:
I do NOT take any credit for this guide.
You can thank BD619 for walking me through all this and the updated command, Indirect for the original commands, benny3 for his awesome ROM, O.M.J for his 3.04.651.2 RUU and for his 3.05.651.6 Firmware, and RumRunner for their awesome S-Off tool!
Also, if anything goes wrong I can try to help you, but the only person responsible is yourself for not following the guide 100%. I have done this all myself and it worked like a charm.
After 3.04.651.2, attempting to achieve S-Off with rumrunner will fail every time after the pouring 8 stage. This guide will show you how to change your version number in order to install an older RUU. After installing the older RUU, then you can proceed to unlock the bootloader, download benny3's Stock ROM (Link Below), flash it after a full wipe, and finally run rumrunner again with success. From there you can optionally update your firmware (Link Below) and flash a ROM of your choice. Once official kitkat is released this guide will not work because the hboot will be different than the one found in the RUU
Changing the Mainver
Before doing all of this, you should backup all your applications and other data with Titanium Backup which can be found in the Play Store. Once your backup is complete, you must copy the titanium backup folder found on your internal storage to your computer because the RUU will wipe the entire storage. Copy any other things you may need including Photos, Music, and Downloads to your computer so you can restore them later.
1. Make sure you are on hboot 1.55. I have not tested this with any other hboot but it is confirmed working on hboot 1.55.
2. Make sure the ADB drivers are set up properly in recovery. I used TWRP but other recoveries should be fine.
3. Boot into recovery and connect the phone to the computer.
3. Open the command prompt, and type in <code>adb devices</code> A string of letters and numbers should pop up. This is only to test the ADB drivers and make sure they are working properly.
4. Now type <code>adb shell</code> and press enter.
5. Now type this exactly as it is here echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160 with the quotes around the version number. After entering the command, it will say failed in the window but just ingnore that.
^^^I recommend you copy and paste to avoid typos.
6. Now enter adb reboot bootloader into the prompt. Your phone will now reboot bootloader and you should see your version number changed to 3.04.651.2.
7. As most of you may know, in order to install a RUU you must relock the bootloader, so click on fastboot on the phone and make sure it says fastboot usb. From here type in fastboot oem lock. Now the bootloader is locked.
Essentially, all we did up to this point is change the version number in order to trick the RUU into installing, and lock the bootloader also for the RUU to work.
Installing the RUU
8. Now you have to download the 3.04.651.2 RUU from http://forum.xda-developers.com/showthread.php?t=2508907. The zip or exe is fine. Do not use the decrypted version.
9. Once downloaded, put the phone into fastboot usb mode, and run the exe. If you downloaded the zip, follow the instruction in the link above to install it.
Flashing the custom ROM
10. Once the RUU is complete you will have to download benny3's ROM from http://forum.xda-developers.com/showpost.php?p=47048176&postcount=2. Either odexed or deodexed is fine. I personally chose odexed but it does not matter. Once downloaded make sure the ROM is not corrupt by matching the MD5 codes, or simply opening the zip.
11. Boot up current ROM and copy the downloaded ROM into the internal storage. We cannot install yet however because the RUU restored the stock recovery and the bootloader is locked.
12. Unlock the bootloader by following the instructions at http://www.htcdev.com/bootloader
13. Once the bootloader is unlocked we can now flash a custom recovery. Download TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/m7wls Once it finished put phone into fastboot usb, copy the TWRP img you just downloaded into the fastboot command prompt folder, open fastboot command prompt, and type in fastboot flash recovery recovery.img Replace recovery.img in the command with the actual name of the file.
14. Once the custom recovery is installed boot into recovery and do a full wipe (Dalvik Cache, Cache, Data, System). Do NOT wipe the internal storage!
15. Go back and tap install. Select the ROM you placed in the internal storage in step 11. Once it is flashed clear the dalvik cache and reboot the system.
Running RumRunner
16. Before you run RumRunner, confirm all drivers are working correctly by testing adb and fastboot commands in recovery, fastboot, and the OS. Enable USB Debugging in developer options. Set auto sleep to the maximum of ten minutes. Go to personalize, and choose the no lockscreen setting. Go to settings, power, and make sure fastboot is NOT checked. Disable firewall and anti virus programs on your computer. Run the SuperSu app and make sure all SU Binaries are updated.
17. Once you've done everything above, you can download RumRunner 0.5 from http://rumrunner.us/downloads-2/ Make sure phone is connected to PC in ADB mode, and run soju.exe as administrator. Follow the onscreen instructions.
18. Once RumRunner is complete your phone will reboot to bootloader and report S-Off.
Updating Firmware
19. Now that you are S-Off, we can move on and update the firmware. Download the Full unmodified Firmware (fastboot flashable) from http://forum.xda-developers.com/showthread.php?t=2576995 Follow the instructions in the link for a guide on how to flash the firmware.
20. Once your firmware is updated if you reboot into the OS, your touchscreen may not respond. Do not worry about that it will be fixed soon.
Flashing A Custom ROM
21. Find a ROM of your choice in the android development section or the android original development section. The ROM you choose MUST be a Sprint ROM.
22. Copy the ROM to your internal storage, reboot to recovery. and do a full wipe (Dalvik Cache, Cache, Data, System). Again, do NOT wipe the internal storage!
23. Once the wipe is complete, flash the ROM you chose and clear the dalvik cache. Reboot system and you should be good to go. Remember, the first boot takes a bit longer than usual. Give it a good ten minutes before getting worried.
24. At this point you could copy your titanium backup folder back into the internal storage. Install titanium backup from the Play Store, open it, go to menu>preferences, scroll down to backup folder location, tap it and find the backup folder you just copied to your storage. Now you can restore all the apps and data you backed up. Also, you can copy all the other things you backed up to the computer.
I know this is a long guide, but the process above works 100%, and I tried to include as many details as possible. If you have any suggestions, please let me know. Also, if anyone runs into any problems, post it in the comments and maybe someone can help you.
Click to expand...
Click to collapse
Thank you and Big Daddy! Only thing I noted in instructions mentioned to copy downloaded ROM to internal storage and then to unlock bootloader. However this will erase everything and therefore ROM needs to be copied after doing unlock and twrp flash after unlock. I sincerely thank you for helping me achieve S-Off.
Doc

SOLID.
Great guide you guys. Very concise and easy to understand steps. :good:

Anyone who does not have S-OFF yet I highly suggest getting it before KitKat drops...HTC has a habit of making things harder with every OTA. Rumrunner may not work afterwards.

Docarut said:
Thank you and Big Daddy! Only thing I noted in instructions mentioned to copy downloaded ROM to internal storage and then to unlock bootloader. However this will erase everything and therefore ROM needs to be copied after doing unlock and twrp flash after unlock. I sincerely thank you for helping me achieve S-Off.
Doc
Click to expand...
Click to collapse
Ok guide was updated with proper instructions. Thanks for letting me know. I'm glad the guide worked for you!

What am I doing wrong?
D:\Users\Android\HTC One\HTC Unlock>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
FA37SSxxxxxx recovery
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
[try again]
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Windows 8.1 / TWRP / unlocked / fastboot works fine / etc

echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
you need to bold "echo" it took me a bit to figure I needed to copy that part of the string

That command is very, very dangerous if you screw up even a little -- could easily brick a device. OP, the guide is really useful for folks, but please put all the parts folks need to copy in quote blocks.
Most of the readers don't even know what the dd command is because they don't use any Unix type OS (e.g., Linux) and they are using it with full root level access.
[Edit: adding a little explanation]:
The 'dd' command is a 'direct dump' and it takes whatever you tell it from the 'if' parameter (input file) or if no 'if' flag is provided, from the standard input. The 'echo' command puts whatever you specify to the standard output (a.k.a., stdout in unix/linux terms). The vertical bar is a 'pipe' specifier and pipes the stdout of the last command to the input of the next -- in this case the 'dd' command.
So how can this all to really, really badly? Imagine, just by happenstance, the recovery shell you use sends error output to stdout (by a mistaken bug, instead of stderr which is the norm). Whatever the shell would print as the error message is going to go to the dd command as stdin and it will write that to your device where you tell it. In short, brick city.
Just by luck, imho, the user above who failed to add the "echo" was using a recovery that (very luckily) sent nothing to stdout, so dd didn't have anything to write. I'm telling you, folks, @BD619 and I both have stated on multiple occasions the raw danger here.
Be careful and DO NOT RUSH INTO THESE THINGS -- IF YOU ARE NOT SURE, EVEN IF ONLY 0.000000001% UNSURE ASK! WE WILL GET YOU SET.

jluca98 said:
I do NOT take any credit for this guide.
You can thank BD619 for walking me through all this and the updated command, Indirect for the original commands, benny3 for his awesome ROM, O.M.J for his 3.04.651.2 RUU and for his 3.05.651.6 Firmware, and RumRunner for their awesome S-Off tool!
Also, if anything goes wrong I can try to help you, but the only person responsible is yourself for not following the guide 100%. I have done this all myself and it worked like a charm.
After 3.04.651.2, attempting to achieve S-Off with rumrunner will fail every time after the pouring 8 stage. This guide will show you how to change your version number in order to install an older RUU. After installing the older RUU, then you can proceed to unlock the bootloader, download benny3's Stock ROM (Link Below), flash it after a full wipe, and finally run rumrunner again with success. From there you can optionally update your firmware (Link Below) and flash a ROM of your choice. Once official kitkat is released this guide will not work because the hboot will be different than the one found in the RUU
Changing the Mainver
Before doing all of this, you should backup all your applications and other data with Titanium Backup which can be found in the Play Store. Once your backup is complete, you must copy the titanium backup folder found on your internal storage to your computer because the RUU will wipe the entire storage. Copy any other things you may need including Photos, Music, and Downloads to your computer so you can restore them later. Also, make sure you are on hboot 1.55. I have not tested this with any other hboot but it is confirmed working on hboot 1.55.
1. Make sure the ADB drivers are set up properly in recovery. I used TWRP but other recoveries should be fine.
2. Boot into recovery and connect the phone to the computer.
3. Open the command prompt, and type in <code>adb devices</code> A string of letters and numbers should pop up. This is only to test the ADB drivers and make sure they are working properly.
4. Now type <code>adb shell</code> and press enter.
5. Now type this exactly as it is here echo "3.04.651.2" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160 with the quotes around the version number. After entering the command, it will say failed in the window but just ingnore that.
^^^I recommend you copy and paste to avoid typos.
6. Now enter adb reboot bootloader into the prompt. Your phone will now reboot bootloader and you should see your version number changed to 3.04.651.2.
7. As most of you may know, in order to install a RUU you must relock the bootloader, so click on fastboot on the phone and make sure it says fastboot usb. From here type in fastboot oem lock. Now the bootloader is locked.
Essentially, all we did up to this point is change the version number in order to trick the RUU into installing, and lock the bootloader also for the RUU to work.
Installing the RUU
8. Now you have to download the 3.04.651.2 RUU from http://forum.xda-developers.com/showthread.php?t=2508907. The zip or exe is fine. Do not use the decrypted version.
9. Once downloaded, put the phone into fastboot usb mode, and run the exe. If you downloaded the zip, follow the instruction in the link above to install it.
Flashing the custom ROM
10. Once the RUU is complete you will have to download benny3's ROM from http://forum.xda-developers.com/showpost.php?p=47048176&postcount=2. Either odexed or deodexed is fine. I personally chose odexed but it does not matter. Once downloaded make sure the ROM is not corrupt by matching the MD5 codes, or simply opening the zip.
11. We cannot install yet however because the RUU restored the stock recovery and the bootloader is locked.
12. Unlock the bootloader by following the instructions at http://www.htcdev.com/bootloader
13. Once the bootloader is unlocked we can now flash a custom recovery. Download TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/m7wls Once it finished put phone into fastboot usb, copy the TWRP img you just downloaded into the fastboot command prompt folder, open fastboot command prompt, and type in fastboot flash recovery recovery.img Replace recovery.img in the command with the actual name of the file.
14. Once the custom recovery is installed boot into Android and copy the downloaded ROM into the internal storage, boot into recovery and do a full wipe (Dalvik Cache, Cache, Data, System). Do NOT wipe the internal storage!
15. Go back and tap install. Select the ROM you placed in the internal storage in step 11. Once it is flashed clear the dalvik cache and reboot the system.
Running RumRunner
16. Before you run RumRunner, confirm all drivers are working correctly by testing adb and fastboot commands in recovery, fastboot, and the OS. Enable USB Debugging in developer options. Set auto sleep to the maximum of ten minutes. Go to personalize, and choose the no lockscreen setting. Go to settings, power, and make sure fastboot is NOT checked. Disable firewall and anti virus programs on your computer. Run the SuperSu app and make sure all SU Binaries are updated.
17. Once you've done everything above, you can download RumRunner 0.5 from http://rumrunner.us/downloads-2/ Make sure phone is connected to PC in ADB mode, and run soju.exe as administrator. Follow the onscreen instructions.
18. Once RumRunner is complete your phone will reboot to bootloader and report S-Off.
Updating Firmware
19. Now that you are S-Off, we can move on and update the firmware. Download the Full unmodified Firmware (fastboot flashable) from http://forum.xda-developers.com/showthread.php?t=2576995 Follow the instructions in the link for a guide on how to flash the firmware.
20. Once your firmware is updated if you reboot into the OS, your touchscreen may not respond. Do not worry about that it will be fixed soon.
Flashing A Custom ROM
21. Find a ROM of your choice in the android development section or the android original development section. The ROM you choose MUST be a Sprint ROM.
22. Copy the ROM to your internal storage, reboot to recovery. and do a full wipe (Dalvik Cache, Cache, Data, System). Again, do NOT wipe the internal storage!
23. Once the wipe is complete, flash the ROM you chose and clear the dalvik cache. Reboot system and you should be good to go. Remember, the first boot takes a bit longer than usual. Give it a good ten minutes before getting worried.
24. At this point you could copy your titanium backup folder back into the internal storage. Install titanium backup from the Play Store, open it, go to menu>preferences, scroll down to backup folder location, tap it and find the backup folder you just copied to your storage. Now you can restore all the apps and data you backed up. Also, you can copy all the other things you backed up to the computer.
I know this is a long guide, but the process above works 100%, and I tried to include as many details as possible. If you have any suggestions, please let me know. Also, if anyone runs into any problems, post it in the comments and maybe someone can help you.
Click to expand...
Click to collapse
OK command fixed in step 5.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life

pbassjunk said:
What am I doing wrong?
D:\Users\Android\HTC One\HTC Unlock>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
FA37SSxxxxxx recovery
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
[try again]
D:\Users\Android\HTC One\HTC Unlock>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Windows 8.1 / TWRP / unlocked / fastboot works fine / etc
Click to expand...
Click to collapse
I'm not sure, maybe try another PC with windows 7, USB 2.0, and drivers installed correctly.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life

jluca98 said:
I'm not sure, maybe try another PC with windows 7, USB 2.0, and drivers installed correctly.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life
Click to expand...
Click to collapse
After some more testing, this seems to be an 8.1 specific issue. Not sure if it's an HTC driver issue, an 8.1 USB 2/3 driver issue or something with ADB (up to date), but I tried it on an 8 laptop (USB 3 only) along with a 7 desktop (USB 2 only, older imac in bootcamp heh) and things worked as expected.
Not scientific but as close as I could get with the hardware I have. Pretty sure it's an 8.1 problem.

Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app

androidforeve said:
Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Its not really that hard. If you follow instructions properly and meet the prerequisites in the OP then you will be fine. I know of multiple people who followed this guide with no problems. Try it and if you run into any issues post a comment and we will try to help you.
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life

androidforeve said:
Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Thanks for the input but do I really need to be s-off? So far I can flash everything fine with no problem of course I have not tried flashing firmware or radios because I have latest ones I'm assuming that's the problem I will have but I thought I read somewhere that you can still flash firmware and radios even with s-on but I could be wrong
Sent from my HTCONE using xda app-developers app

You can read this guide to understand more about s-off. http://android-revolution-hd.blogspot.com/2013/06/do-we-really-need-s-off.html?m=1
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life

androidforeve said:
Looks a little complicated as much as I would love to go s-off not sure if could handle this
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Do a backup in recovery
Copy your entire internal sd to pc
Follow instructions as above
After s-off root like you did before
Move internal back to device
Restore in recovery
Good 30 minutes
I sugest you download everything first, that way your device isnt down while you wait
I only have 1 very anoying issue. Was 3.05.651.5 complete stock with root and .6 update released. I did s-off, did ota, then rooted. I'm 3.05.651.6 s-off, rooted and i still got the ota notice to update to 3.05.651.6 and it wont go away.

Maybe this can help you. http://forum.xda-developers.com/showthread.php?t=1856632
Light a fire for a man and you`ll warm him for a few hours...Light a man on fire and you`ll warm him for the rest of his life

saaaaweet