Related
Typical stuff, I take no responsibility for anything that happens to your device. That being said much love to Roach2010 and KTWombley for their work which led to my insignificant contribution.
Long story short this update is for the US version of Asus Transformer TF101. This upgrade applies to those who are running stock firmware that is rooted.
If you removed any stock applications or did anything to your stock installation this will fail.
I tested this update on my own tablet and my daughters who happens to have the keyboard dock and all was good. US only but if anyone wants to forward me other packages I would be happy to add them.
Try at your own risk.
chuy08 said:
If you removed any stock applications or did anything to your stock installation this will fail.
Click to expand...
Click to collapse
sad to hear. any workaround on that?
oifi said:
sad to hear. any workaround on that?
Click to expand...
Click to collapse
Flash the full ROM again. Then flash this update
chuy08 said:
Typical stuff, I take no responsibility for anything that happens to your device. That being said much love to Roach2010 and KTWombley for their work which led to my insignificant contribution.
Long story short this update is for the US version of Asus Transformer TF101. This upgrade applies to those who are running stock firmware that is rooted.
If you removed any stock applications or did anything to your stock installation this will fail.
I tested this update on my own tablet and my daughters who happens to have the keyboard dock and all was good. US only but if anyone wants to forward me other packages I would be happy to add them.
Try at your own risk.
Click to expand...
Click to collapse
I guess i need CWM to flash this?
Sent from my Transformer TF101 using Tapatalk
Can someone please post a step by step for running this update? been a while since I rooted and want ICS
thanks in advance... I rooted but left things unmodified
do I just flash the update like any other rom?
Yeah you can flash over.
I installed OTA Rootkeeper and made a backup of my root, then I flashed the zip like anything else. After I the update was finished, I went back into OTA Rootkeeper and noticed that I no longer had root so I used the app to restore my root and voila, all updated and rooted.
I flashed this via CWM and it all went well.
How do I remove the message in my notifications? Also, OTA (even with root keeper) doesn't seem to work with CWM installed.
Is there a ww version of this update?
Hi,
kookooktchoo, thanks for the info about OTA root-keeper!!! Unfortunately I didn't read the rest of your post, I too flashed this update and lost root. lucky I had installed and backed up my root using it.
thanks a lot !!!
John
---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------
Renarudo said:
I flashed this via CWM and it all went well.
How do I remove the message in my notifications? Also, OTA (even with root keeper) doesn't seem to work with CWM installed.
Click to expand...
Click to collapse
Go into your apps in settings, find DMClient, then clear the data and cache, then you will get no more notifications about updates.
CrazyPeter said:
Is there a ww version of this update?
Click to expand...
Click to collapse
+1
can we flash it over the 9.2.1.11 WW? will it keep the ROOT?
superdioz said:
+1
can we flash it over the 9.2.1.11 WW? will it keep the ROOT?
Click to expand...
Click to collapse
I think it will appear later this week.
You can still use ViperMod primetime option 1 to root after the flashing the update. Just did it myself .
kookooktchoo said:
Yeah you can flash over.
I installed OTA Rootkeeper and made a backup of my root, then I flashed the zip like anything else. After I the update was finished, I went back into OTA Rootkeeper and noticed that I no longer had root so I used the app to restore my root and voila, all updated and rooted.
Click to expand...
Click to collapse
It uprooted me too and that app works great thanks kookooktchoo
Sent from eee pad Transformer running ICS
Works perfect.. I did not lose root either..
Anyone know a way to get this to not check a current app? I only changed the SystemUI and cant find my backup of the original. It hangs on that. I tried the rooted+stock full version of the first ICS release but it apparently didnt blow away my ASOP SystemUI because its still failing.
No reboots or hangs so far. Good stuff.
Update the new firmware using the normal route. Still rooted after the update. No problem at all.
Worked great for me. Thanks!
The OTA kept failing on me so I tried this and it worked great.
For an 8MB update it took a little longer than I expected to flash (+5 mins).
Apparently this doesn't fix USB mounting of internal and removable storage on PC though. I was hoping it would. Guess I'll search out the separate fix. I know I saw it around here some where.
Update failed
Doesn't work for me, update says:
assert failed: apply_patch check("system/framework/framework.jar", "019f4fa7de941375127daceb8342fca208512e9f", ....etc
E:Error in /sdcard/update_9.2.1.17-tf102.zip
(Status 7)
Installation aborted
Coming from http://forum.xda-developers.com/showthread.php?t=1514658
with OptionB, fullwipe
Ok so one day my phone is all nice and dandy, rooted as a tree, and then I go to Advence Freeze an app, and Rom Toolbox Pro tells me I no longer have root access. So I go into Titanium backup and it says the same thing. For total verification, I go to Terminal Emulator, and the "su" command gives me a "not granted" response. So while I had root yesterday, for some reason I don't have it today. The thing I'm worried about most is that I did absolutely nothing in the meantime. The phone hadn't restarted in 3 days so that wasn't it. And all I did before it unrooted itself iis use the Inkpad Notepad app, and the Boat Browser app. I didn't touch a single thing that could possibly mess something up. Root hasn't always been very "observable" on my phone. After about a week after rooting it, Superuser stopped asking me if I wanted to allow or deny new apps. But all my root apps still worked. I run no special rom, just stock 4.1.2. I have SafeStrap Bootloader installed for backups as well. I downloaded Motochopper to try to reroot my phone just a few minutes ago and the exploit ran flawlessly. No errors whatsoever. When it booted up, still no root access. To be more specific, Voodoo OTA Root Keeper tells me the device is rooted, but without root access. I also have a root backup made with that program. Can someone please tell me how to fix this because the thought of a "normal" phone is making me depressed :crying:.
Try updating your SU and see if that does anything.
RikRong said:
Try updating your SU and see if that does anything.
Click to expand...
Click to collapse
The only way I could think of doing that is from the superuser app (if you mean update the binaries) and I already tried. It fails at "gettingroot access".
miapuffia said:
The only way I could think of doing that is from the superuser app (if you mean update the binaries) and I already tried. It fails at "gettingroot access".
Click to expand...
Click to collapse
Yeah, that's what I meant. Hmmm...
RikRong said:
Yeah, that's what I meant. Hmmm...
Click to expand...
Click to collapse
Perhaps I could backup my data using SafeStrap TWRP, download stock rooted 4.3 (which I wanted since it came out), install it to rom slot 2 using SafeStrap, and then restore my data! Where's my nobel prize? lol Would that work?
miapuffia said:
Perhaps I could backup my data using SafeStrap TWRP, download stock rooted 4.3 (which I wanted since it came out), install it to rom slot 2 using SafeStrap, and then restore my data! Where's my nobel prize? lol Would that work?
Click to expand...
Click to collapse
There is no stock 4.3 ROM for us. The highest stock version would be 4.1.2. You can get CM10.2 that is vanilla AOSP, but I don't know if it would boot on SS.
RikRong said:
There is no stock 4.3 ROM for us. The highest stock version would be 4.1.2. You can get CM10.2 that is vanilla AOSP, but I don't know if it would boot on SS.
Click to expand...
Click to collapse
I see. That's why my rooted 4.3 search came up.blank. I don't mind trying CM. I tried to SS install it previously but it failed (kinda). But now that I think about it I definitely installed the wrong version. As long as I can restore my data to CM I don't mind trying it. Can I get 4.1.2, root it, and then restore data? But wait, I know my bro has 4.3 rooted he used temp unroot -> update -> restore root. Can I do that? In case you didn't notice I'm new to this :/
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?
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?