Database Info

New software update

I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet

The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it

Is there a new update? post/after asa14?
Checked around but after seeing the old do this if you cant upgrade threads pop up I was curious.

Seen some traces of the 9.8.2Q JellyBean update for the Q, but don't know it's current status.

Interesting and good news, Just checked and mine stated not update available sadly..

Gxkon said:
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
Click to expand...
Click to collapse
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?

swintec said:
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
Click to expand...
Click to collapse
I dont know it dont look like a new os. One was around 60 mb then i had a small 7 mb update

arrrghhh said:
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Click to expand...
Click to collapse
Yeah, the motofail2go exploit to root works only if you haven't updated. After rooting, you can save root by Voodoo OTA rootkeeper, temp unroot, install any updates, then restore root with OTA rootkeeper. Works great, and you keep your warranty. But of course you can't flash any ROMs or anything, but you can still use Titanium backup, other programs that require root.
see this thread:
http://forum.xda-developers.com/showthread.php?t=2053444

4.4 (V2) root still work using Jcase method?

Hey guys,
I apologize for making a new thread about this but I think some others may have this question too. So I received the second 4.4 OTA today and I'm curious if the Root exploit SlapMyMoto from Jcase will work with this new OTA? I do not know if it it is the same update as all it says it "Kitkat ... update (19.5.3.en.us)" nothing about 4.4 or 4.4.2. Thanks in advance for any input

it should...the actual OS update is the same as what we got in December.

dano1282 said:
it should...the actual OS update is the same as what we got in December.
Click to expand...
Click to collapse
for the VZW non Developer Edition right? I'm reading up on MotoWpNoMo and it references an unlocked bootloader.
Also can I do this method if I did RockMyMoto before MotoWpNoMo to gain root?

Have you already installed 4.4? If so, you're out of luck. The Moto X can be downgraded back to 4.2.2 but the DROID line can not.
Don't attempt to FXZ 4.2.2 or you'll have issues.
Sent from my XT1080 using xda app-developers app

If you follow jcase's instructions for SlapMyMoto I can verify it works. Did it this morning on my Maxx, but as stated earlier, you can not root if you've already updated to 4.4, and you can not go back to 4.2.2. If I'm remembering correctly, the basic process was: from 4.2.2, root, permanently remove write protection, go back to stock 4.2.2 (after camera update), then SlapMyMoto.

osucowboy96 said:
If you follow jcase's instructions for SlapMyMoto I can verify it works. Did it this morning on my Maxx, but as stated earlier, you can not root if you've already updated to 4.4, and you can not go back to 4.2.2. If I'm remembering correctly, the basic process was: from 4.2.2, root, permanently remove write protection, go back to stock 4.2.2 (after camera update), then SlapMyMoto.
Click to expand...
Click to collapse
here's what i've done so far. rooted using RockMyMoto AFTER camera update. Still on 4.2.2 I do not know how to remove the Write protection because I tried using MotoWpNoMo and I keep getting a "1". Also, What do you mean by "go back to stock" after removing Wp?

Carrzy said:
here's what i've done so far. rooted using RockMyMoto AFTER camera update. Still on 4.2.2 I do not know how to remove the Write protection because I tried using MotoWpNoMo and I keep getting a "1". Also, What do you mean by "go back to stock" after removing Wp?
Click to expand...
Click to collapse
keep hammering it with MotoWpNoMo. You have to get that to work and must get write protection off (0). Took several tries on mine to get it to work. Make sure you are running it with admin priv and all your antivirus etc is off and are following directions exactly.
back to stock means after you have done the above, reflash 4.2.2 camera update (15.15) to REMOVE root and get it back to a stock build.
Then do the SlapMyMoto steps 1-3, then take 4.4 update, then finalize Slap steps.

jkhouw1 said:
keep hammering it with MotoWpNoMo. You have to get that to work and must get write protection off (0). Took several tries on mine to get it to work. Make sure you are running it with admin priv and all your antivirus etc is off and are following directions exactly.
back to stock means after you have done the above, reflash 4.2.2 camera update (15.15) to REMOVE root and get it back to a stock build.
Then do the SlapMyMoto steps 1-3, then take 4.4 update, then finalize Slap steps.
Click to expand...
Click to collapse
In addition, when I did MotoWpNoMo the first time, I noticed it was asking for root access on my phone and I had to unlock my phone and give it access. The first time failed, I believe, due to not immediately having root access (I got a line with like 4-5 "T"s followed by either a bunch of dashes or asterisks, then next line was "Press Enter to exit" or something similar). The second time I ran it, since it now had root access, it ran like a charm.
To get back to 12.15.15 after removing write protection, I used HouseOfMoto, keeping data. Some prefer a full wipe.
Good luck, and if you run into any other issues I'll help any way I can. No expert, but I'll offer what limited advice I can.

osucowboy96 said:
In addition, when I did MotoWpNoMo the first time, I noticed it was asking for root access on my phone and I had to unlock my phone and give it access. The first time failed, I believe, due to not immediately having root access (I got a line with like 4-5 "T"s followed by either a bunch of dashes or asterisks, then next line was "Press Enter to exit" or something similar). The second time I ran it, since it now had root access, it ran like a charm.
To get back to 12.15.15 after removing write protection, I used HouseOfMoto, keeping data. Some prefer a full wipe.
Good luck, and if you run into any other issues I'll help any way I can. No expert, but I'll offer what limited advice I can.
Click to expand...
Click to collapse
I gave it root access but I still get the T's and asterisks. I'll keep trying tho and I appreciate the help guys

Alright so I was able to disable Write protection successfully but now I don't know how to to create and FXZ file for House Of Moto (steps, 3,4 & 5)

[Q] rooted droid maxx boot loops after ota attempt

I have a droid maxx on 12.15.15 update and rooted it using the telnet and adb way. I kept cancelling the last ota update becasue I wanted to make sure root was available. Anyway this morning i aciddently hit install now ;( It didn't install but now its stuck in boot loop. It powers up fine, but after everything loads a bout a minute later it says Power off...Shutting down.. and restarts and keeps boot looping. I've rooted all my other fons, but this is getting tricky. How can I fix this?? I don't mind installing ota if there is root availalble, but I just need my fon fixed! I'm on vacation 1400mi from home, but fortunately I have my old fon along. Any help would be greatly appreciated!

droidrepair said:
I have a droid maxx on 12.15.15 update and rooted it using the telnet and adb way. I kept cancelling the last ota update becasue I wanted to make sure root was available. Anyway this morning i aciddently hit install now ;( It didn't install but now its stuck in boot loop. It powers up fine, but after everything loads a bout a minute later it says Power off...Shutting down.. and restarts and keeps boot looping. I've rooted all my other fons, but this is getting tricky. How can I fix this?? I don't mind installing ota if there is root availalble, but I just need my fon fixed! I'm on vacation 1400mi from home, but fortunately I have my old fon along. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You are bootlooping because the root method used on this phone removes the stock recovery, thus the phone keeps trying, and failing, to install the update. As far as I'm aware the only way you can get out of the bootloop is to boot into fastboot and re-flash stock 12.15.15 (luckily because the 4.4 update has not installed on your device you will be able to keep your lower firmware, and thus re-root). However I am not 100% sure this is the only solution, and this would wipe your phone as well. I recommend waiting for more responses or looking around for a possible other solution if you prefer to try to not wipe your phone....

Yachter99 said:
You are bootlooping because the root method used on this phone removes the stock recovery, thus the phone keeps trying, and failing, to install the update. As far as I'm aware the only way you can get out of the bootloop is to boot into fastboot and re-flash stock 12.15.15 (luckily because the 4.4 update has not installed on your device you will be able to keep your lower firmware, and thus re-root). However I am not 100% sure this is the only solution, and this would wipe your phone as well. I recommend waiting for more responses or looking around for a possible other solution if you prefer to try to not wipe your phone....
Click to expand...
Click to collapse
I haven't had time to look around and find the thread, but I was able to find a thread that allowed me to FXZ using fastboot to restore 12.15.15 and restore everything, leaving your data intact. Worked like a charm when I was stuck in the bootloop. So, it's doable.

@droidrepair do you have titanium back up installed and are you booting into the os even if momentarily?
Sent from my KitKat Ultra

Bump, this problem is an exact replica of what I am currently experiencing. You do get to boot into the OS for a little while, but after about (maybe) 1/2 a minute, it says powering off and reboots.

sangar66 said:
Bump, this problem is an exact replica of what I am currently experiencing. You do get to boot into the OS for a little while, but after about (maybe) 1/2 a minute, it says powering off and reboots.
Click to expand...
Click to collapse
OK. Do you have titanium back up?
Sent from my KitKat Ultra

Caseyk621 said:
OK. Do you have titanium back up?
Sent from my KitKat Ultra
Click to expand...
Click to collapse
Yes, but it was only to delete bloatware, there is no actual backup of what's on my phone. Additionally, I don't really care about recovering lost data, I just want to bring my phone to a working state.

sangar66 said:
Yes, but it was only to delete bloatware, there is no actual backup of what's on my phone. Additionally, I don't really care about recovering lost data, I just want to bring my phone to a working state.
Click to expand...
Click to collapse
That's ok. When you get to your os quickly go into titanium back find apk MotorolaOTA and freeze it. That should stop your bootloop. If it doesn't you may need to freeze an app called updater. Lemme know how it works out.
Sent from my KitKat Ultra

Caseyk621 said:
That's ok. When you get to your os quickly go into titanium back find apk MotorolaOTA and freeze it. That should stop your bootloop. If it doesn't you may need to freeze an app called updater. Lemme know how it works out.
Sent from my KitKat Ultra
Click to expand...
Click to collapse
I don't have the donate version of Titanium Backup, so I can't freeze things. Should I uninstall OTA?

sangar66 said:
I don't have the donate version of Titanium Backup, so I can't freeze things. Should I uninstall OTA?
Click to expand...
Click to collapse
Don't think that it would hurt your situation. Give it a try.
Sent from my KitKat Ultra

Caseyk621 said:
Don't think that it would hurt your situation. Give it a try.
Sent from my KitKat Ultra
Click to expand...
Click to collapse
I don't have time to uninstall, but I was able to get a telnet connection which I can use to find the process to kill (the update process), but I don't have permission to actually do so.

sangar66 said:
I don't have time to uninstall, but I was able to get a telnet connection which I can use to find the process to kill (the update process), but I don't have permission to actually do so.
Click to expand...
Click to collapse
Use House of Moto then to go back to stock. Use 12.15.15 fxz
Sent from my KitKat Ultra

no, i don't have ti backup. Fon is stock except for root.

Caseyk621 said:
Use House of Moto then to go back to stock. Use 12.15.15 fxz
^^^this^^^^
droidrepair said:
no, i don't have ti backup. Fon is stock except for root.
Click to expand...
Click to collapse
Sent from my KitKat Ultra
Click to expand...
Click to collapse

Ok i used houseofmoto 2 and fastboot and so far seems to be working fine! Thanks SamuraiHL and all!
Now i don't have root tho. I assume i'll be able to re root using telnet, etc? Or should i install ota and then root, or is that not possible yet?

droidrepair said:
Ok i used houseofmoto 2 and fastboot and so far seems to be working fine! Thanks SamuraiHL and all!
Now i don't have root tho. I assume i'll be able to re root using telnet, etc? Or should i install ota and then root, or is that not possible yet?
Click to expand...
Click to collapse
Don't take 4.4 OTA as there is no way to root it. You need to start the process on rooted 4.2.2 using the slapmymoto process nicely outlined here.
http://forum.xda-developers.com/showthread.php?t=2616104
[GUIDE V1.6][ROOT][4.2.2 TO 4.4] XT1080/M (Requires Rooted 4.2.2) 01/20/14
Sent from my KitKat Ultra

I rooted using https://docs.google.com/file/d/0B67RS0BDBp_iaVFhZDd2dmtaTFE/edit
do I need to use the method you show to do 4.4 ota?
Caseyk621 said:
Don't take 4.4 OTA as there is no way to root it. You need to start the process on rooted 4.2.2 using the slapmymoto process nicely outlined here.
http://forum.xda-developers.com/showthread.php?t=2616104
[GUIDE V1.6][ROOT][4.2.2 TO 4.4] XT1080/M (Requires Rooted 4.2.2) 01/20/14
Sent from my KitKat Ultra
Click to expand...
Click to collapse

droidrepair said:
I rooted using https://docs.google.com/file/d/0B67RS0BDBp_iaVFhZDd2dmtaTFE/edit
do I need to use the method you show to do 4.4 ota?
Click to expand...
Click to collapse
That's correct. You have 4.2.2 rooted now you can move on to start the rooting process for 4.4.
Sent from my KitKat Ultra

wow. It takes a lotta work to keep these things rooted and updated! oh well, educational i guess. Is there a stable 4.4 ota or is this just the one from dec that got pulled?

droidrepair said:
wow. It takes a lotta work to keep these things rooted and updated! oh well, educational i guess. Is there a stable 4.4 ota or is this just the one from dec that got pulled?
Click to expand...
Click to collapse
Yeah it does! They (vzw) re-released it in January. Its stable. Just follow instructions to a t and you'll be OK. Plenty of help around here as well.
Sent from my KitKat Ultra

Confused about if there's root for 4.4 etc

Ok so I got my XT1080 few days or whatever and it had the first 4.4 ota, you know the one with the transparent status bar but still that blue jelly bean hue on the status bar etc.... So not thinking of it I just decided to see if there was another ota and there was so I got it and now I want root.... Here's what I want to know please.. Without telling me to go read 30 pages on another post can someone just tell me
Is there root for me
If so do I have to have boot loader unlocked, I've had phones with locked boot loaders and still flashed Roms
Can I flash Roms on this device with a locked boot loader via twrp
I mainly read that you have to downgrade to a certain version use jcase method it something? I got lost in that bounty post..

Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.

bluebloomers said:
Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.
Click to expand...
Click to collapse
Wow I love you!

alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!

kdm212 said:
alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!
Click to expand...
Click to collapse
What build of 4.4 are you one? 19.5.3 or 19.6.3?

Topsnake said:
What build of 4.4 are you one? 19.5.3 or 19.6.3?
Click to expand...
Click to collapse
19.5.3 it should be made known i plan on using the phone with t-mobile and the outside hope that i can have a fully functional phone with lte...

Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?

Topsnake said:
Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?
Click to expand...
Click to collapse
Boot loader is not unlocked. However if I do the update I won't be able to get root. Correct?

Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off

Topsnake said:
Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off
Click to expand...
Click to collapse
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!

kdm212 said:
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!
Click to expand...
Click to collapse
Link to what specifically? You dont need to downgrade on your version

Topsnake said:
Link to what specifically? You dont need to downgrade on your version
Click to expand...
Click to collapse
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?

kdm212 said:
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?
Click to expand...
Click to collapse
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4

Topsnake said:
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4
Click to expand...
Click to collapse
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!

kdm212 said:
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!
Click to expand...
Click to collapse
No problem

any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?

kdm212 said:
any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?
Click to expand...
Click to collapse
Run motowpnomo to gain wp off then safe strap can install su to system

Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.

TheDroidURLookinFor said:
Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.
Click to expand...
Click to collapse
What version is it on?

Topsnake said:
What version is it on?
Click to expand...
Click to collapse
19.5.3

[Q] Unable to get back to stock

I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse

TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks

I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.

nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.

dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.

nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?

dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.

nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?

dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM

back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks

empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.

unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?

empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845

not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?

Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.

empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...

nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.

jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?