Database Info

[701] /System RW JB Boot image-Full Root UPDATED

For A701 users only running Jelly Bean Only.
Boot image used: AV051_A701_1.021.00_WW_GEN1. Should work fine on other JB builds.
New Version 3 uploaded 23/10/2012
Should fix ADB commands for /System Remount Thanks Vorbeth
2 Parts. Part 2 is full /system RW.... also know as ROOT for the A701 on JB who took the OTA
Part 1 is For people using the previous "andlommy" image flash..... For JB OTA see part 2...
Part 1
This is meant to replace your boot.img after performing the Root image flash from this thread by andlommy;
http://forum.xda-developers.com/showthread.php?t=1911437
Ok people, as some may realize, the current "root" procedure of fastbooting images doesn't allow full /system remount. This can be seen if you try to update your superuser binary. Superuser can't remount /system. Yes, you can probably delete some files via file manager, however, if you use a root app that calls for a /system remount, well, it's not going to happen. Not like it should be.
Also, the 701 doesn't have a reliable CWM, so we do things the old fashioned (and safer) way.
This method has been around in the 500 forums for some time now. Recently, I gave info to the 210 users to get the /system remount working on their tabs. I currently use the same. Why nobody tried it here, well.....
Basically it involves modifying the zimage to change security, and allow remounts. It does not involve the kernel itself, as it remains stock.
Replaces Stock A701 Boot.img
1. Allows for full /System RW
2. Increased IO over stock.
And yes, I do use the modified boot image, 2nd revision.
As always, you have to thank people who helped you in the past and present:And I owe a lot to these guys. (which is why I hit the Donate button for them)
Vorbeth
Civato
EZTerry
Skrilax_CZ
LinuxSociety
NOTE" You must have unlocked bootloader"
Also, you do this at your own risk.Most of you know this already.
Installation:
For previous somewhat Rooted JB installations.
Download the following package and unzip to your system.
FIX-JB-ROOT
1. Connect your tablet
2. USB Debugging is on
3. Open a command window where you unzipped the Fix-JB-Root
4. Type: adb reboot bootloader
after tab reboots to bootloader download, Type;
5. fastboot flash boot JB_701V3_boot.img
6. After success, reboot tablet.
7. Start Superuser and update binaries.
Part 2
AS A ROOT PROCESS. 701 only After OTA to JB.
Note that this is an alternative to the image flash method. You need only to OTA to JB, then follow the instructions.....
Needs Testing on a Stock JB 701 Make sure you've unlocked your bootloader
1. Follow the above procedures in part 1
2. After restart, with tab connected, open a CMD Window where you unzipped the package.
3. Type the following commands;
a. adb devices (and hit Enter. You should see your device listed)
b. adb remount /system (and hit Enter. You should see remount successful)
c. adb push su /system/xbin
d. adb shell chmod 6755 /system/xbin/su
e. Get Superuser and Busybox from the Playstore. Start Superuser, check for updating binaries. Install Busybox.
Hopefully this roots and grants /system RW. I don't have a stock 701JB, so would appreciate feedback if this works or not.
MD

Works perfect Thank you. Now we only nee CM10 for our 701

Thanks MD! Going to give the 4.1.1 another go this weekend, using this boot. Will let you know how it goes )

MD are you able to delete apk from "/system/vendor/app"?

IronFly said:
MD are you able to delete apk from "/system/vendor/app"?
Click to expand...
Click to collapse
Absolutely. Just moved Solitaire.apk into /Data/app
Use your root explorer and check for RW.
Remember, this just fixes a shortcoming in the original "pre-rooted image flashing" from 4.0.4 to 4.1.1 where you can't get system remounts from some root apps.
As stated near the end of the post, I haven't tried it on a "stock non-rooted" JB build.
MD

Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
fishwood said:
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
Click to expand...
Click to collapse

fishwood said:
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
Click to expand...
Click to collapse
I answered in your original thread.
MD

Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway

misteral1970 said:
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
Click to expand...
Click to collapse
Yeah, I meant to tell you yesterday it won't help your situation. Your issue, is you're stuck on the ICS bootloader and it won't update to the JB one. Not to mention now, you have that "Hybrid Mix". Maybe one day can come up with a solution for it. Trying to get my hands on a 701 Service Rom.
Acer won't fess up the SBK (Secure Bootloader Key), so it sort of makes NVFlash non-usable unless we have it.
The service rom uses NVFlash, which in theory will change bootloaders (it's what we used in the 500 forums).
But until then, we're sort of stuck. I still have one trick up my sleeve, but's it's a long shot, and not even sure it'll work. Might perma-brick your tab. Will look at my old files.
MD

MD got your method working thanks for sharing this MOD!

RiceDie said:
MD got your method working thanks for sharing this MOD!
Click to expand...
Click to collapse
Which method? Experimental Root? Or just the full System RW?
Also, which build Rom are you running Mate?
MD

MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?

bschrib said:
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
Click to expand...
Click to collapse
The root method should work the same as with ICS and JB.
Basically need an 700 ICS and JB boot.img. to do the mod. Takes about 10 minutes. Fastboot the boot image, download SU and BB. Should be good to go.
MD

I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD

Vorbeth said:
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Click to expand...
Click to collapse
Should have a modded boot image in a day or so. Seems the boot images are the same for all builds for 700 JB.
It's the weekend, so some family time is on order.
Thanks for the GB full update rom.
MD

Hi,
I was one of the first people who updated their A701 with the unrooted JB ROM which was posted on XDA forums. The update was flawless and smooth using the external SD card and normal recovery method. Last night I tried to unlock my device and root it using step by step instructions given on OP. Device has unlocked but it is still not rooted. I checked using Root Checker app. Have I missed any steps in performing the root operation? Please help.
Additionally after doing all the steps in the OP I reinstalled the original JB update ROM using external SD card and recovery method. Bootloader is still unlocked and device is still not rooted. Device is working fine as far as I can tell.
Awaiting expert advice and help!
Best regards,

So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?

farazjk said:
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
Click to expand...
Click to collapse
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD

Moscow Desire said:
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Click to expand...
Click to collapse
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz

farazjk said:
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
Click to expand...
Click to collapse
The unlocked bootloader will have no effect on normal day to day operations.
I'll try and get a 700 or 701 stock user to run a couple of things to get the SU issue sorted out. Shouldn't take that long. Probably a matter of using adb to push it through.
The 700 already has a JB Full rom update package, so hopefully the 701 will get one soon as soon as somebody locates it
Think it's time to bother Acer, and see about a SBK......
MD

Downgrade to lower version to use revolution

Im trying to get my desire s downgraded, rooted and be able to install a custom rom on it. I have searched and tried all guides on here but none of them seem to work anymore there are always files missing, web sites down or just things out of date I already have a gold card on my memory card.
I cant use revolution as my version is too high and needs to be downgraded can someone help me plz with the files or destination of them thanks.

Re. Downgrade....
Hallo...I am attaching zip with the files i`ve downloaded someday long ago,
,there is also file without extension which you can open wirh any text editor-
- it is description i`ve got from the original thread about the downgrading procedure..
I hope this is all you need to proceed to tthe fruitful end...
Good luck
And one more thing, those files were ment for versions lower than ics
so if you are running ics, they might be useless...No harm in trying though
Edit. I do not have the ruu but there is a beautifull thread in development section:
INDEX of ROMS/RECOVERY/ROOT/GUIDES/HBOOT/RADIOS/TWEAKS etc
you can find many answers there ...

This is one of the few sites that you can still get the RUUs http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
Intel Inside: The world's most widely used warning label. - Jim Hooper.

jugg1es said:
This is one of the few sites that you can still get the RUUs http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
Intel Inside: The world's most widely used warning label. - Jim Hooper.
Click to expand...
Click to collapse
My phone is branded to o2 but unlocked do i have to get a o2 ruu it will be used on tmobile when done but i don't want any branding on it. Sorry used to my sgs3 this is so different
Sent from my HTC Desire S using xda app-developers app

--> please notice: if you have a branded device, use a branded RUU to downgrade!
I strongly encourage you to read full tutorial first
Our desire s -> development-> Index, roms, recoveries...
Click to expand...
Click to collapse

got an issue already the first line adb push zergRush /data/local/tmp adb is saying cannot stat zergrush no such file or directory I have cd to the folder its in. ?????
got past that line now stuck at adb shell chmod 777 /data/local/tmp/misc_version
now

Re: downgrade...
torres76 said:
got an issue already the first line adb push zergRush /data/local/tmp adb is saying cannot stat zergrush no such file or directory I have cd to the folder its in. ?????
got past that line now stuck at adb shell chmod 777 /data/local/tmp/misc_version
now
Click to expand...
Click to collapse
are you rooted- if so then after adb shell you shall press enter
,and if you see a $ sign, type su
then in your device superuser app will ask you for superuser rights for the shell-
you grant it there
then in the terminal the sign should change to #
then you are ready for chmod 777[space]/data/local/....
Edit:
after you`l have succeded this procedure to the very end and have rebooted the device succesfuly!!
to flash ruu you need to relock your bootloader( you know this)
fastboot oem lock
I you are stuck along the way then write again- better be safe than sorry

asgardr said:
are you rooted- if so then after adb shell you shall press enter
,and if you see a $ sign, type su
then in your device superuser app will ask you for superuser rights for the shell-
you grant it there
then in the terminal the sign should change to #
then you are ready for chmod 777[space]/data/local/....
Edit:
after you`l have succeded this procedure to the very end and have rebooted the device succesfuly!!
to flash ruu you need to relock your bootloader( you know this)
fastboot oem lock
I you are stuck along the way then write again- better be safe than sorry
Click to expand...
Click to collapse
no im not rooted need to downgrade first don't I, seriously doing this is so hard so many different things to try it is confusing.

but you are unlocked aren`t you- by htc dev?
if this is so now it is time to get the recovery for saga,
flash it from fastboot fastboot flash recovery recovery.img...
then you ought to get superuser zip for saga and flash it from your newly installed recovery
and then your live with downgrading will be much easier
Edit: in the attachment yoou have
1. recovery.img flash from fastboot,,, fastboot flash recovery recovery.img
2. superuser.zip flash from recovery
any doubts? write...

torres76 said:
no im not rooted need to downgrade first don't I, seriously doing this is so hard so many different things to try it is confusing.
Click to expand...
Click to collapse
im not unlocked from htcdev registered but got no email so cant use the site 8-(

Re. Downgrade....
hoooo... pull the horses... when i read my post, it looks bit chaotic,
let us organise it ....
first:
you said before that you are unlocked- if that is true then either by htc dev or your device is natively
opened by manufacturer..either way you can flash recovery and root your phone.
Second:
if the first line in your bootloader(phone off then symultanously pressing power and volume down)
states >> locked<< then your phone is in an untouched state- stock
Third:
if your device is stock, and unrooted, without custom recovery
then the files from the downgrade zip are needed,
- zerg rush which is an exploit that lets us get temporary root for the shell,
and it is gone after you reboot the phone.
- misc_version that lets us change-or fool the phone about the software version that we have on board
Now, there is much more to it but.... see first what you can do with what you know already

asgardr said:
hoooo... pull the horses... when i read my post, it looks bit chaotic,
let us organise it ....
first:
you said before that you are unlocked- if that is true then either by htc dev or your device is natively
opened by manufacturer..either way you can flash recovery and root your phone.
Second:
if the first line in your bootloader(phone off then symultanously pressing power and volume down)
states >> locked<< then your phone is in an untouched state- stock
Third:
if your device is stock, and unrooted, without custom recovery
then the files from the downgrade zip are needed,
- zerg rush which is an exploit that lets us get temporary root for the shell,
and it is gone after you reboot the phone.
- misc_version that lets us change-or fool the phone about the software version that we have on board
Now, there is much more to it but.... see first what you can do with what you know already
Click to expand...
Click to collapse
Thanks mate I am now unlocked through htcdev had to reregister now everything is completed, so next step root ???? correct

Re: downgrade...
torres76 said:
im not unlocked from htcdev registered but got no email so cant use the site 8-(
Click to expand...
Click to collapse
I am not in your skin so it is realy difficult for me to advise you
either way but:
you can try again htc dev (or wait for email from them-check if you`ve followed their procedure to the letter)
procedure that is easier for all of us with less expearience
you can try to downgrade and s-off with another procedure- which is more difficult but works for many people,
have to decide yourself
I am s-on again- with an unlocked bootloader, because i am comfortable with it- not need s-off for now really,
but can speak only for myself

asgardr said:
I am not in your skin so it is realy bifficult for me to advise youeither way but:
you can try again htc dev (or wait for email from them-check if you`ve followed their procedure to the letter)
procedure that is easier for all of us with less expearience
you can try to downgrade and s-off with another procedure- which is more difficult but works for many people,
have to decide yourself
Click to expand...
Click to collapse
you didn't read my last message I am now unlocked via htcdev, but still have problems when trying to run the adb shell chmod 777 /data/local/tmp/misc_versionnow command it says permission denied is it because im not rooted ???

torres76 said:
Thanks mate I am now unlocked through htcdev had to reregister now everything is completed, so next step root ???? correct
Click to expand...
Click to collapse
Recovery first from fastboot
then root from recovery
congrats

asgardr said:
Recovery first from fastboot
then root from recovery
congrats
Click to expand...
Click to collapse
I rooted with oneclickroot what now
adb shell is showing # not $ now so all good now how too downgrade

Re. Downgrade....
torres76 said:
I rooted with oneclickroot what now
adb shell is showing # not $ now so all good now how too downgrade
Click to expand...
Click to collapse
1. if i were you I`d flash recovery from fastboot-just in case- you`l need it anyway
2. make backup of your curent rom -from recovery-just in case something goes wrong
3. try if the root remains after reboot- if not- then flash su (you`ll find in the second attachment) from recovery
4.push misc_version and do the rest of downgrade procedure to the letter
5.make sure you have the right ruu after you have lowered your software version number- run it and wait till it finishes
6. keep the unlock token from htc in a safe place- just in case
7. go to the revolutionary site, download the needed program and follow their procedure to remove
s-on
8. should also flash eng. hboot(should br extremely carefull with that-get as much info as you can) but it may be later
9. choose custom or stock ROOTED rom you want to flash- and flash it
10. enjoy your free saga
Steps: 1,2,3,4,5,6,7,9,10- important
8- best get some info and confidance first before you do it
Seems to much- i know- but it isn`t... remember: rush is the bad advisor
Edit:
almost forgotten: between step 4 and 5
to flash ruu you must relock bootloader- this is important
command fastboot oem lock
check this http://forum.xda-developers.com/showthread.php?t=1318919

torres76 said:
im not unlocked from htcdev registered but got no email so cant use the site 8-(
Click to expand...
Click to collapse
u search in the spam folder? i had the same problem

zgabi28 said:
u search in the spam folder? i had the same problem
Click to expand...
Click to collapse
yeah I did mate cheers it wasn't there I reregistered. cant wait to get my sgs3 back

asgardr said:
1. if i were you I`d flash recovery from fastboot-just in case- you`l need it anyway
2. make backup of your curent rom -from recovery-just in case something goes wrong
3. try if the root remains after reboot- if not- then flash su (you`ll find in the second attachment) from recovery
4.push misc_version and do the rest of downgrade procedure to the letter
5.make sure you have the right ruu after you have lowered your software version number- run it and wait till it finishes
6. keep the unlock token from htc in a safe place- just in case
7. go to the revolutionary site, download the needed program and follow their procedure to remove
s-on
8. should also flash eng. hboot(should br extremely carefull with that-get as much info as you can) but it may be later
9. choose custom or stock ROOTED rom you want to flash- and flash it
10. enjoy your free saga
Steps: 1,2,3,4,5,6,7,9,10- important
8- best get some info and confidance first before you do it
Seems to much- i know- but it isn`t... remember: rush is the bad advisor
Edit:
almost forgotten: between step 4 and 5
to flash ruu you must relock bootloader- this is important
command fastboot oem lock
check this http://forum.xda-developers.com/showthread.php?t=1318919
Click to expand...
Click to collapse
hey mate good so far just need to install the engineers hboot do you have it

HTC One SV Revert to Stock Help (for update)

Hi All,
Of course the first thing I did after getting my new HTC One SV is root it and install LBE privacy protection to stop data leakage. However recently ive been getting a notification of an update to jelly bean through my phone provider (Vodafone Australia). However this will not install due to custom recovery image so the pre-install check fails. I cannot find stock recovery images anywhere and even if I did, due to presence of clockwork mod cant push images via Android SDK (skips straight past hboot to clockworkmod so isn't detected as an available device).
Can anyone help me get my phone back in a state where I can install the new update and the re-root?
Am not 100% noob, am familiar with custom roms and basics required to root and use SDK, this is my 3rd android device ive played with so hopefully this question is not tooooo SIGH.
Seems like HTC one SV is too new to have its on page in XDA support?

Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV

Not helpful
marceli-szpak said:
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Hi there,
Unfortunately I don't have permission to post messages in that thread, nor does it seem the appropriate place to ask my question as it is an area for resources not help.

You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV

RE HTC One SV Revert to Stock Help (for update)
marceli-szpak said:
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000

snorglamp said:
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
Click to expand...
Click to collapse
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.

old.splatterhand said:
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
Click to expand...
Click to collapse
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.

snorglamp said:
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
Click to expand...
Click to collapse
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.

?????????????*

ismailnayir said:
?????????????*
Click to expand...
Click to collapse
If's there anything you don't understand, ASK!
So nobody knows, what you want, sorry.

old.splatterhand said:
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
Click to expand...
Click to collapse
Yes I thought that might be the case but was not having any luck with search results to find out what to do. Thank the internet gods for you! Going to your thread now XD!

I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!

madpausa said:
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
Click to expand...
Click to collapse
DUDE! THATS TOTALLY WHAT I WANNA HEAR, however, ive been having enormous trouble getting fastbood/ADB to recognise the phone is attached, I have tried the universal clockwork mod ADB driver which didnt work, and I havent had any luck folloing the instructions on Splatterhand's other threads in getting it recognised. The command fastboot devices just leaves a flashing cursor FOREVER! Other commands leave the message "waiting for device". According to splatterhand ADB/Fastboot wont recognise the phone as attached because of clockworkmod and therefore I cant push any commands or files...how did you solve this?

OMG
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!

snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhead for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help

madpausa said:
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
Click to expand...
Click to collapse
So I took your advice and pulled a recovery image from the ICS Cricket (using the link in splatterhand's thread to stock resources) image. Downloaded the OTA and went to apply it, got past boot/recovery screen checks and all was looking good until i got to a screen with what looked to be an SD card icon and a loading bar under a larger phone icon with a green recycle type circle over it. That loading bar stopped about half way with a red triangle and exclamation mark (i.e. during the update process). Fortunately not bricked. It may be that I need the original Vodafone AU recovery image, or that there was something about the ICS OTA image that I used that made it fail. Not sure. Will try to find another stock recovery image.

Applied recovery from EU RUU stock and while that went fine and can boot into htboot no problem, when applying the OTA update it skips the fastboot and gets stuck on HTC One screen like normal loading except stuck.
I think I will try old.splatterhand's recommendation now that I am able to push things to the phone through adb/fastboot, so thanks for your commandline tip but now I must try flashing the JB recovery etc as outlined in his post.
The problem may be that the OTA is expecting a vodafone australia stock recovery as i seem to be getting different outcomes depending on which stock recovery image I apply...
I have sent Old.Splatterhand the Vodafone Australia JB OTA file for the main thread collection in case anyone wants it or the images therein, but at the moment it is of little use to me hehe.

SUCCESS! How to update to Jelly Bean from modded/rooted HTC One SV ICS
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!

Good to see you got your problem sorted out!:highfive:
And the download of OTA was succesful, thanks!:good:

snorglamp said:
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Click to expand...
Click to collapse
This is the exact problem I had. I started trying to root my HTC One SV (Boost Mobile) a couple of months ago. I got past the HTC unlock bootloader, but I got confused by the rest of the rooting guide, so eventually I gave up on finishing the rooting process. Ever since then, it has said ***TAMPERED*** in hboot when I go in there. Well, just like you, I started getting the JB update notification in the OTA. I tried to install it like 15 times, but it always just rebooted into the existing image I had, which was the stock image.
So today I decided to try and finish the root and then find a JB ROM to install. old.splatterhand helped me out with getting it rooted, and it was a success. But when I asked him about JB ROMs, he said I had to have S-off. When we spoke a little more about it, he pointed me here, telling me that he helped you get the root back after you got through the OTA update.
So now, I guess I need to try and follow your instructions on getting the OTA update, and then go back to the thread where he helped you get the root back.
I'm a complete n00b to rooting android devices, but I'm pretty confident that I can do this with the proper guidance. I have rooted 2 Samsung SCH-i500s and today I finally got this HTC One SV rooted. I'm starting to see how it all works.
If you don't mind, let me know of any details of issues you faced that may not be in the guides you followed. That would be a great help.
Congrats on getting yours all done.
Thanks.
---------- Post added at 07:32 PM ---------- Previous post was at 07:15 PM ----------
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Do you type "adb reboot bootloader" in the command line? I wanna be clear on this before I make any moves.

HTC One SV Boost.. Trying to UPDATE too 4.2.2 Not working

I have a Rooted and s off HTC one Sv from Boost mobile. I can download the OTA for Sense 5 and 4.2.2 but when I try to install it it cancels and says something like cant get ro.products.build = k2cl.. and something else ...
Im new to all of this, but Im really good with following a step by step guide if there is something I can read to fix this issue.
Im just trying to get the latest software available for this phone. And also if there is a way to edit the build.prop on this phone to make it run faster and increase the network speed too. that would be amazing. I have yet to find anything for this phon

Well, for boost mobile you can use a Ruu which they released for the latest available Software.
http://dl3.htc.com/application/RUU_...V_NV_Boost_2.20_150_release_389346_signed.exe
This will delete all of your data and your bootloader must be locked, if you are S-on (only as an info, in case you have unlocked at htcdev.com to gain root access).

Hi. Thanks.
So I need to turn the bootloader off and switch S off back to S on?
I dont remember what software I used to root it, it was on my other computer that got stolen.
How would I go about locking the bootloader? And turning the S back on? And once successful in getting the update will I be able to root it again?
Is there any other better roms I can flash on it now that is better? I would love to have KitKat on here if possible.. But as of now I know that cyanogen mod isnt supporting this device and all I know to do is update it to 4.2.2 with sense 5, if I could just figure out how.
Sorry for all the questions.
Last question is... I seen build.prop editing possiblities to be able to speed up 4g, 3g, and 2g networks speeds and even to bypass network caps, but no guides for htc one sv for boost. Are there any that I can be directed to to edit the build.prop to achieve this?

Don't know about boost specific tweaks.
Also there are no custom roms available for boost.
You are S-off, you didn't mention. But thats good! Don't go S-on, and no need to relock bootloader in this case, as far as i remember.
Backup everything you need, connect your device to your pc and run the Ruu. It will bring you to the latest software for your phone.

Ive been trying over and over to get the Ruu to work and I followed the instructions properly. And even deleted it and downloaded it again.
It keeps saying : Error 170 USB Connection Error. And wants me to check the USB sync cable or my connection to the PC.
But Both my cables work fine and my computer is new and nothing wrong with it. I am able to use my USB to Tether app just fine and im able to copy and paste to and from my phone and able to use HTC Sync manager too. SO Idk what the deal is.
Maybe some specifics about my setup may help.
My computer is an HP Envy Sleekbook with 8g of ram and i5 processor running windows 8.1 64bit.
My phone is the Boost mobiles version HTC One SV C525c with these details:
Android Version: 4.1.2
Sense: 4
Software number: 2.06.653.6 710RD
HTC SDK API: 4.65
HTC Extension Version: HTC Extension_Sense45_12
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: 2.06.653.6 CL209682 release-keys
I dont know if that helps with my situation but just in case I added it.
Thank you and I appreciate the help

Do a research on google with "htc ruu error 170".
You will get many results, like this:
http://forum.xda-developers.com/showthread.php?t=2553296

No matter what I do nothing seems to be helping
I have been googling for days. And been at it for hours today trying to figure this out.
I really just need a step by step guide. I dont understand this stuff.
So far, I downloaded and unistalled and reinstalled drivers for windows 8.1. I downloaded adb drivers and fastboot.
I tried to use RUU by going into Fastboot usb. I even tried to download the OTA update and then manipulate the update-script by deleting all the assert checks to stop getting the getprop errors. But still didnt work.
IDK what to do all I want to do is have my phone back to normal again and to be able to update it to the newest software version. Its annoying to see the update available notification in my tray and I cant do anything about it.
The closest I got so far was switching to the windows 7 computer and turning off the developer options menu. But then RUU starts to work but then stops at HTC fastboot.exe has stopped working. Im stuck.
Some more information about my phone just in case its helpful. :
Moonshine S-OFF
K2_CL PVT SHIP S-OFF RL
CID-SPCS_003
HBOOT-2.00.4444
RADIO-1.12.50.0516
OpenDSP-v9.2.0268.1214
eMMC-boot
I also got rid of CWM and put TWRP v2.8.4.0
I just went to the bootloader screen and tried to install the OTA file from there and also the OTA file that I deleted the assert build prop stuff from and I get the same error E: Error executing updater binary in zip
SO idk what to do but im determined to fix this.
Thank you much for helping me

Now my phone wont work at all.
Its stuck on the HTC screen and I cant figure out how to get it back. I know there is a way. This really sucks.

guitarjae said:
Now my phone wont work at all.
Its stuck on the HTC screen and I cant figure out how to get it back. I know there is a way. This really sucks.
Click to expand...
Click to collapse
Theres is not much what i can do, because i don't know much about boost, and i don't have any files for it.
Maybe @Modding.MyMind can help you here, he has much more knowledge in this kind of stuff, than me.

Ok. I managed to get my phone unbricked by using windows 7 and using fastboot to flash the same operating system I was already using. Now I don't have twrp or cwm. Its just a red triangle now if I try to log into recovery.
It is also switched from moonshine s off to locked.
So I'm assuming I'm S on now and bootloader locked.
I went back to the RUU program you told me to install and it started to work but then stop and gave an error 158 image error. I googled it but I don't understand how to fix it.
Is there any way I can just get sense 5 and 4.2.2. I'm starting to think its not possible. But would be nice if I could.

I don't know, whats wrong here. What have you flashed on your phone to get it running?
A RUU? This would explain, that you loose twrp, because it flashes everything to stock. But it don't set S-off to S-on! That step has to be done manually by yourself.
---------- Post added at 09:57 ---------- Previous post was at 09:13 ----------
Please check this website for more information and download of the RUU you need:
www.htc.com/us/support/htc-one-sv-boost/news/

guitarjae said:
Ok. I managed to get my phone unbricked by using windows 7 and using fastboot to flash the same operating system I was already using. Now I don't have twrp or cwm. Its just a red triangle now if I try to log into recovery.
It is also switched from moonshine s off to locked.
So I'm assuming I'm S on now and bootloader locked.
I went back to the RUU program you told me to install and it started to work but then stop and gave an error 158 image error. I googled it but I don't understand how to fix it.
Is there any way I can just get sense 5 and 4.2.2. I'm starting to think its not possible. But would be nice if I could.
Click to expand...
Click to collapse
https://www.dropbox.com/s/tacg3jdz84c6wlh/Pure_Jelly_Bean_4.1.2_TWRP_Backup.zip?dl=0
Download this pure 4.1.2 JellyBean backup made specifically for TWRP and extract the zip on to your desktop. Flash the TWRP recovery to your recovery partition using fastboot.
Code:
fastboot flash recovery twrprecovery.img
Reboot in to TWRP, make sure your device is plugged in to your computer.
Now before we move on further I need you to make a quick TWRP backup. You do not need to make a full backup. Just one will do since I am merely aiming to have the required TWRP backup directory be created on your device.
Did you make a quick backup? Good. Lets move forward.
Select the option to mount your usb (You should still be in TWRP). A window will pop up on your computer showing either your internal or external storage. Find the TWRP folder and look through it until you find the backup folder. Go inside the backup folder and you will see the files created to make your backup. Delete them all.
Copy my backup that you downloaded earlier over to that same directory. When done, unmount device from computer, then unmount device from phone. Select to restore your device using that TWRP backup. After completition, reboot your device, let the phone start up. Welcome back to 4.1.2.
Go to settings to manualkly update your device to 4.2.2 but before you accept the update you must make sure you flash back your stock recovery using the same instructions given at the beginning. DO not attempt to accept the OTA with TWRP installed, it will fail.

Hey thanks
Im on 4.1.2 now
Last night I went to this forum http://androidforums.com/threads/htc-one-sv-boost-stuck-on-splash-screen.826881. When I was there I followed the instructions that the guy gave the other guy for his problem, since I was bricked and stuck on the splash screen. I downloaded this https://www.dropbox.com/s/wqq04edwc844ufw/decrypted_k2_cl_2.06.653.6_rom.zip. And that got me back to 4.1.2 with sense 4.
Now since I did that it deleted the twrp I had on it and where it used to say moonshine S Off it now says LOCKED? So, I dont know what that means if Im s off or not anymore.
I went to download the update to 4.2.2 and it started to install but then just rebooted and it still asks me to update and im still on 4.1.2. I also tried the RUU again in fastboot mode and it will start to install and stops at error 158 image error. ? ... I also took the OTA update file that downloaded from the downloads folder and put it on my computer and tried to flash it with fastboot and it still stops after some kind of check. I even edited the update-script to delete the assert at the top and it started and stopped at a different error. So idk..
Right now my phone is back on and I can use it. I just want to get the update somehow. So maybe if you still think I should try again and do what you just mentioned, Ill do it tonight once i get to my desktop with win 7 since win 8.1 is stupid with this.

guitarjae said:
Hey thanks
Im on 4.1.2 now
Last night I went to this forum http://androidforums.com/threads/htc-one-sv-boost-stuck-on-splash-screen.826881. When I was there I followed the instructions that the guy gave the other guy for his problem, since I was bricked and stuck on the splash screen. I downloaded this https://www.dropbox.com/s/wqq04edwc844ufw/decrypted_k2_cl_2.06.653.6_rom.zip. And that got me back to 4.1.2 with sense 4.
Now since I did that it deleted the twrp I had on it and where it used to say moonshine S Off it now says LOCKED? So, I dont know what that means if Im s off or not anymore.
I went to download the update to 4.2.2 and it started to install but then just rebooted and it still asks me to update and im still on 4.1.2. I also tried the RUU again in fastboot mode and it will start to install and stops at error 158 image error. ? ... I also took the OTA update file that downloaded from the downloads folder and put it on my computer and tried to flash it with fastboot and it still stops after some kind of check. I even edited the update-script to delete the assert at the top and it started and stopped at a different error. So idk..
Right now my phone is back on and I can use it. I just want to get the update somehow. So maybe if you still think I should try again and do what you just mentioned, Ill do it tonight once i get to my desktop with win 7 since win 8.1 is stupid with this.
Click to expand...
Click to collapse
You should still be S-Off. If you boot up to your bootloader it will either say S-On or S-Off. You used a decrypted RUU so it is a good chance your bootloader is in fact locked. You lost TWRP because the "RUU" restored your device back with the original images as if your device came right out of the box. Which is the whole purpose of an RUU. As for the issue you are having with the OTA update, that seems a bit off, so just follow my instructions and you should be fine. Check to see if you are S-On or S-Off. Also insure that your bootloader is unlocked. If you are S-On then take the boot.emmc.win file from my backup and rename it to boot.img. Use fastboot to flash the boot.img to the boot partition.
Code:
fastboot flash boot boot.img
recovery.emmc.win is the stock recovery. Again, if you are S-On, then rename it to recovery.img and flash it using fastboot.
Code:
fastboot flash recovery recovery.img
This is required because being S-On will prevent you from writing to those partitions using DD. Requires you to be S-Off otherwise. If you are S-On, then that is fine. First focus on getting yourself up to 4.2.2. Once that has been accomplished then use rumrunner universal for HTC to gain S-Off again.

Modding.MyMind said:
You should still be S-Off. If you boot up to your bootloader it will either say S-On or S-Off. You used a decrypted RUU so it is a good chance your bootloader is in fact locked. You lost TWRP because the "RUU" restored your device back with the original images as if your device came right out of the box. Which is the whole purpose of an RUU. As for the issue you are having with the OTA update, that seems a bit off, so just follow my instructions and you should be fine. Check to see if you are S-On or S-Off. Also insure that your bootloader is unlocked. If you are S-On then take the boot.emmc.win file from my backup and rename it to boot.img. Use fastboot to flash the boot.img to the boot partition.
Code:
fastboot flash boot boot.img
recovery.emmc.win is the stock recovery. Again, if you are S-On, then rename it to recovery.img and flash it using fastboot.
Code:
fastboot flash recovery recovery.img
This is required because being S-On will prevent you from writing to those partitions using DD. Requires you to be S-Off otherwise. If you are S-On, then that is fine. First focus on getting yourself up to 4.2.2. Once that has been accomplished then use rumrunner universal for HTC to gain S-Off again.
Click to expand...
Click to collapse
Hello
Sorry I havent been online lately to give an update.
Thank you for your help. I am successfully now on 4.2.2 with sense 5 by following your instructions.
So now all I have to do is Root again. Can you tell me an quick and easy way to Root again?? I did it last over a year ago on this phone and I think the way it was rooted was the reason I was having such issues. But idk.... Im open for better options on rooting the phone. Towelroot doesnt work for this phone, not that I every used towelroot, i just seen that lots of others are saying it worked and it was fast and easy.
After I root it, I want to be able to increase my phone storage too and be able to move apps to sd card instead of it using all my phone storage. It is already saying cant download bc of insufficient storage.
And other than that, do you know of a good build.prop script for this phone that can increase network speed and maybe bypass the data cap?
Also, I still dont know how I can tell if Im S off or S on? When I hold the vol down and power button, it pops up like it used too but instead of saying its S off it just says LOCKED?

Can somebody please help me with something?

I have my M8 with S-OFF (Paid for Sunshine) and it is temporarily rooted with KingRoot. I'm just confused on what I need to do next to get fully rooted so I can start flashing some ROMS! I tried to install TWRP with the app but it doesn't seem to work and it just boots into the standard recovery mode and NOT TWRP.
So, where do I go after having S-OFF and temp root?
I would greatly appreciate anybodies help here, I've rooted several devices before but nothing has been harder or more confusing then rooting the m8 on 5.0.1!
Thanks in advance!

MTN927 said:
I have my M8 with S-OFF (Paid for Sunshine) and it is temporarily rooted with KingRoot. I'm just confused on what I need to do next to get fully rooted so I can start flashing some ROMS! I tried to install TWRP with the app but it doesn't seem to work and it just boots into the standard recovery mode and NOT TWRP.
So, where do I go after having S-OFF and temp root?
I would greatly appreciate anybodies help here, I've rooted several devices before but nothing has been harder or more confusing then rooting the m8 on 5.0.1!
Thanks in advance!
Click to expand...
Click to collapse
Flash twrp with fastboot and push/flash SuperSU in twrp.
--beaups
Sent from my XT1254 using Tapatalk

I'm having trouble finding some good directions on that stuff...

I'm trying to run the WinDroid program to flash twrp, it reboots the phone into fastboot but then WinDroid just says rebooting device and doesn't seem to get passed that. Should I just wait?

MTN927 said:
I'm trying to run the WinDroid program to flash twrp, it reboots the phone into fastboot but then WinDroid just says rebooting device and doesn't seem to get passed that. Should I just wait?
Click to expand...
Click to collapse
Shouldn't use apps like that. Just flash it with fastboot manually.
Sent from my XT1254 using Tapatalk

beaups said:
Shouldn't use apps like that. Just flash it with fastboot manually.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
This is where I'm not finding any good directions for these steps, as far as how to do the command prompts.

OK finally got TWRP installed, can I flash SU from the SU app?

You flash SuperSU from within twrp.
Sent from my XT1254 using Tapatalk

MTN, I know this can be frustrating for a newbie. There are plenty of walkthroughs, and I'm sure everyone else will tell you to google, but for the sake of being concise, here's the scoop:
1. Make sure you have ADB installed.
2. Go to your ADB prompt and make sure your device is showing up (need the HTC drivers installed) by doing:
adb devices
3. Reboot into fastboot:
adb reboot bootloader
4. Flash TWRP:
fastboot flash recovery twrp####.zip
5. Once you've got TWRP installed, you reboot INTO TWRP (full recovery) and let it patch your system because if you don't it will be overwritten. As follows:
- Reboot with VolDwn held.
- From bootloader, pick "recovery".
- Wait for TWRP to come up.
6. Once TWRP is in, drop supersu package ZIP (get the latest one, careful here!) into a directory, boot into TWRP, and install it.
Boom, your device is completely rooted.
But I think that the thing that you need to understand is that "rooted" only applies to the current ROM. Rooting isn't a magic thing - it simply means that you have root privilege on the current OS. It is separate from firmware, bootloader, etc. which all also have to be flashed/loaded/updated depending on what you are doing. There probably ought to be a newbie page somewhere that explains to people what each thing is. The ROM is essentially the same as whatever version of windows/linux/etc. you have on your home computer. It has nothing to do with the hardware, the firmware, or the bootloader.
On my phone, I followed the above procedure, but then proceeded to download and install a clean ROM that was pre-rooted. Then later I put back the stock Verizon ROM and had to reapply root. I then later removed root to return the phone to verizon for service. But I didn't uninstall Root, I simply flashed on a non-rooted ROM.
Does that make sense?