Related
I'm rooted with rock my moto, stock recovery is reflashed, & I have write protection permanently off. Uninstalling safestrap is a no-brainer. I'm guessing the OTA will kill root and write protection? I presume slap my moto will work once I'm in Kit Kat, but is there anything I can do while on 4.2.2 to prepare for a rootable update into KitKat?
fat-fingered and Maxx-ed out.
I second this, want to be fully prepared and make no mistakes
I fxz'd back to stock a few days ago. I was under the impression that our root method altered the system partition and would cause updates to fail
Root method only removes stock recovery (used for write protection off). Flash recovery back on in ADB, good as new. My stress is permanent write protection off causing a problem after pre-KK FXZ, or OTA in restoring root (if SuperSU Survival Mode can't maintain root).
Edit: WP will survive FXZ, but not likely OTA. Soooo...FXZ, OTA, Slap, WPoff (again) looks like.
fat-fingered and Maxx-ed out.
From what I can tell you need to fxz back to stock and run slapmymoto frist, since slapmymoto work like rockmymoto except installs a "backdoor" instead of root. Keep in mind by taking the 4.4 update you are risking preminate loss of root, because slapmymoto works on the idea that you can roll back to 4.2.2 after KitKat and moto has had a month since the moto x's update rolled to prevent this on the droids. Also I know that anyone has used the motowpnomo mod have has issues getting root back. There is a fix out but I haven't used it and am not sure how it will effect the moto slapping process
Please let us know if anyone gets a successful or unsuccessful method. Then we can verify what does/doesn't work. I have a backup running and the update downloading at the moment. I will post back if I get some time to give it a try.
l337h4cker said:
Please let us know if anyone gets a successful or unsuccessful method. Then we can verify what does/doesn't work. I have a backup running and the update downloading at the moment. I will post back if I get some time to give it a try.
Click to expand...
Click to collapse
Plz pull the update from /cashe with root explorer (or w/r you use) and post a link I'm happy to try but it hasn't been pushed to me yet.
Can anyone pull the install-recovery.sh from system/img for the 4.2.2? I need it for my update.
I just used House of Moto in "Keep Data" mode. Stock recovery is back, along with the annoying bootup sound. Still waiting for the update to push to my phone.
http://forum.xda-developers.com/showthread.php?t=2450702&highlight=houseofmoto
rlmesq said:
I just used House of Moto in "Keep Data" mode. Stock recovery is back, along with the annoying bootup sound. Still waiting for the update to push to my phone.
http://forum.xda-developers.com/showthread.php?t=2450702&highlight=houseofmoto
Click to expand...
Click to collapse
Recommended you look over SlapMyMoto 1.0 before taking the OTA! If you still have root, you could run the MotoWPoff exploit now, if you want.
fat-fingered and Maxx-ed out.
Einsteindks said:
Recommended you look over SlapMyMoto 1.0 before taking the OTA! If you still have root, you could run the MotoWPoff exploit now, if you want.
Click to expand...
Click to collapse
Will MotoWPoff survive the OTA? The thread says
This exploit is permanent in the sense it will survive factory resets, reflashing the device, etc. However, like with any exploit, you should not expect it to survive OTA's or other updates.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2551113
rlmesq said:
Will MotoWPoff survive the OTA? The thread says
http://forum.xda-developers.com/showthread.php?t=2551113
Click to expand...
Click to collapse
Either it did, or KK allows WP toggle for rooted users. Not quite smart to know why. I can tell you what I did, but I can't tell you what happened or why it works.
fat-fingered and Maxx-ed out.
I have an unlocked bootloader. I haven't gotten update yet. Losing patience. I got the email last night saying it would push this morning. Still waiting
Sent from my XT1080 Developer Edition using Tapatalk
Einsteindks said:
I'm rooted with rock my moto, stock recovery is reflashed, & I have write protection permanently off. Uninstalling safestrap is a no-brainer. I'm guessing the OTA will kill root and write protection? I presume slap my moto will work once I'm in Kit Kat, but is there anything I can do while on 4.2.2 to prepare for a rootable update into KitKat?
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
I am in the same situation, very curious on where to go from here to achieve root on 4.4. I have yet to get the update, but would like to be prepared.
Thank you.
Sent from my XT1080 using Tapatalk
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
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
esjames said:
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
Click to expand...
Click to collapse
Literally one thing: http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3-4.30.14.pdf
Well, then. Thats a worthy update lol
esjames said:
Well, then. Thats a worthy update lol
Click to expand...
Click to collapse
by all means, if you're traveling to Canada then update away haha
Lmao wow. That's the most pitiful update ever. Seriously, couldn't they have waited until there was something more substantial and then included Canadian roaming in THAT update. As always though, Verizon is dumber than a bag of hammers...
Sent from my iPhone using Tapatalk
Might be worthwhile to extract the modem package and see if the SMS bug is rectified.
wow
i was so sure this was a KK upgrade. been looking around for how to retain root if you take it. thanks for the info!
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
EddieK23 said:
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
Click to expand...
Click to collapse
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
landshark68 said:
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
Click to expand...
Click to collapse
Ah, I see, next time I'm around her I'll re-root it and backup all her stuff with titanium backup, flash the VRUCML1 and factory reset, then restore everything and see if it works.
Strangely enough, when the same update for my Verizon Note 2 came out, I was able to update while rooted even though I unsinatalled theexact same system apps I did on her phone. How strange.
Nonetheless, thank you so much.
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Joe R said:
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Click to expand...
Click to collapse
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Ok thanks. I will try to find an ML1 download.
Sent from my Samsung Galaxy S III using Tapatalk
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
pnuker said:
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Maintained root
twistedillutions said:
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I was able to maintain root on the OTA update by having OTA Survival Mode checked on SuperSU.
SlimSnoopOS said:
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
smalco44 said:
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
Click to expand...
Click to collapse
Apparently I need a refresher on how to properly copy and paste Here's the link again: http://forum.xda-developers.com/showthread.php?p=52515244#post52515244
I have not yet updated to this new patch yet, am I still able to install saferoot as directed on the thread for it or do I need to do something special first?
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
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?