I have A mytouch Slide that I wnet through the process to root and after I rooted never installed a custom rom or eng. Since than it got updated to 2.1 update 1 newest Tmobile version.
I am having issues with it and need to send it back but It has the superuser porogram installed but I cannot figure out how to remove it before I send it back for warranty exchange.
asmodyus said:
I have A mytouch Slide that I wnet through the process to root and after I rooted never installed a custom rom or eng. Since than it got updated to 2.1 update 1 newest Tmobile version.
I am having issues with it and need to send it back but It has the superuser porogram installed but I cannot figure out how to remove it before I send it back for warranty exchange.
Click to expand...
Click to collapse
If the superuser app is installed and you can use superuser apps, then you are rooted, in which case flash this, which will break root, making it look as if you were a regular user, never rooted, etc.
Yeah I just checked and I do not have root access anymore, but I still have the SuperUser program installed. I tried mutli file remover but nothing will remove it.
That's because (most likely) it was installed to system/app. In order to delete anything from that area you'll need to re-root. Then find the stock nandroid backup listed somewhere in the dev section for our phone (using search would be handy for this one). Flash that nandroid just like any other and BAM, back to a stock, unrooted, no su, 1st time booted phone.
Okay great I figure that I might have to root it to get rid of it.
Thanks for the help.
I having issue trying to find the newest stock rom, can anybody point me in the right direction.
asmodyus said:
I having issue trying to find the newest stock rom, can anybody point me in the right direction.
Click to expand...
Click to collapse
Already posted the link
MusicMan374 said:
If the superuser app is installed and you can use superuser apps, then you are rooted, in which case flash this, which will break root, making it look as if you were a regular user, never rooted, etc.
Click to expand...
Click to collapse
I rooted my phone using the wiki guide for Cyanogenmod, but now tried to return to stock and seem to be having problems.
Using ROM Manager, I reverted back to my backup, however I can't seem to get any updates. No notifications of an available update, and manually checking for one says my phone is up to date.
Before rooting I had downgraded so I know I'm not at the latest version.
I tried unrooting my phone by following a video saying to remove these files with a file manager :
system/bin/su
/system/binx/su
/system/app/superuser.apk (something like that)
There was no su file in /system/binx
Is there an easy way to just revert to factory settings, no root, and working updates?
Thanks in advance.
you can try flashing the proper ruu via hboot. why not just flash a new rom alltogether? I mean you rooted your phone, are you not after superuser function? a better os? there are custom roms very similar to stock to pick from and also many that are far superior, either way...
Sent from my HTC Vision using xda premium
Flashed new rom
Hi
I was indeed looking for superuser access, but was now giving the phone away to a family member who didn't have interest in anything special.
I also had trouble rooting it again after I deleted the files, but got it working after simply pushing the files back on, so I flashed the MIUI Rom which looks great and user friendly.
Okay, I was on ICS 4.0.4 Yakju build. I flashed it using Gnex tool kit and then rooted the phone as well. Also left the bootloaded unlocked.
Today I received the OTA 4.1.1 Jelly Bean update. I began with the procedure and it downloaded well and good but then the installation was interrupted and the phone booted into my old 4.0.4 version. As it turns out, you should not accept the OTA update if you're rooted (lucky, I got away with it). I dont exactly know what caused my installation to fail, the root or the unlocked bootloader or both. Anyway, I used Gnex Tool Kit and 'Flashed the Google Factory Stock Rom' (exactly the same way how I got the yakju 4.0.4 build in the first place) , that left my phone with just as new Stock 4.0.4, UNROOTED with locked bootloader! Just like out of the box. Then I went on with my OTA update and it went through like a charm.
Anyway, now I'm on 4.1.1 Jelly Bean. I want to root the phone because I use too many apps that requires root access. So the latest version of Gnex Tool Kit (7.4) supports Jelly Bean root. But I dont wanna Root my phone this time unless I know how to UnRoot it. Don't wanna go against OTAs. (might start using CM rom when the next android version comes out) but till then I only want OTA updates.
So, can anyone tell me how to UNROOT the 4.1.1 Jelly Bean? (without wipe or deleting all the data) It'll be awesome if it can be done by Gnext Tool Kit. If not, then I dont mind doing it the hard way.
I wanted to post this question in 'Gnext toolkit' forum but I dont have enough privileges. So please help me out
As you can see I'm a noob. So please excuse my ignorance :/
Thanks a lot
Nobody? Please anyone help
Well root and your bootloader status (unlocked or not) really shouldn't affect your ability to receive an OTA IIRC. It should still work successfully although you may lose root.
Anywho, to unroot all you have to do is delete the 'superuser' application whether it be Superuser or SuperSu and then delete 'su' in /system/bin. That should work though IMO the cleanest way to unroot is to just restore the stock images.
Unlawful said:
Anywho, to unroot all you have to do is delete the 'superuser' application whether it be Superuser or SuperSu and then delete 'su' in /system/bin. That should work though IMO the cleanest way to unroot is to just restore the stock images.
Click to expand...
Click to collapse
Well, I guess you cant uninstall SuperUser. I tried that before updating but it acts like a system app and you cant delete it, unless you have 'System app remover' software, but then again it needs Root access to work so the whole thing is pointless I guess
And restore stock image HOW? I mean can you elaborate a lil please!
Using Gnex Tool Kit, which option? (my guess, 'Flash Google Factory Stock Rom' cuz for me it works but it wipes all your data.. backup solution?)
Super su has an unroot option
Here's a screenshot attached
Hit Thanks if i helped
Niallfitzy1 said:
Super su has an unroot option
Click to expand...
Click to collapse
Hey thanks
But does it work on Jelly Bean?? Also, when you Root Gnex using ToolKit then you have SuperUser and not SuperSU :| Whats the way around it?
tojonegi said:
Hey thanks
But does it work on Jelly Bean?? Also, when you Root Gnex using ToolKit then you have SuperUser and not SuperSU :| Whats the way around it?
Click to expand...
Click to collapse
Installing supersu and giving it root access to update such binary removes original superuser apps control you can switch just by downloading super su so it should work, cannot test myself though
Hit thanks if I helped
Niallfitzy1 said:
Installing supersu and giving it root access to update such binary removes original superuser apps control you can switch just by downloading super su so it should work, cannot test myself though
Hit thanks if I helped
Click to expand...
Click to collapse
Okay thanks, I'm gonna try this ^^
Hope it works well in the future while receiving OTA updates
P.S. I'd already hit Thanks
The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?
Lanthanide said:
The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?
Click to expand...
Click to collapse
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).
bruce7373 said:
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).
Click to expand...
Click to collapse
It doesn't matter in general. But it matters in case that you used S-Off to uninstall system APPs Thus an OTA wouldn't succeed.
That's what I wanted to say in my post above
Sent from my HTC One_M8 using XDA Free mobile app
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.
Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
Click to expand...
Click to collapse
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.
HTCNerdYoda said:
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.
Click to expand...
Click to collapse
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
is the s-off really worth it?
Yuskow said:
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
Click to expand...
Click to collapse
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Yuskow said:
is the s-off really worth it?
Click to expand...
Click to collapse
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).
Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.
Click to expand...
Click to collapse
I had the Vivid as well and ended up with a 4.4.2 ROM which seemed to be the most current that was available at the time, but can't remember the name or the dev.
As for the M8, I've been on ARHD almost exclusively and think it's one of the best ROMs out there. I've tried Viper, MaximusHD, Renovate also, but always come back to ARHD.
http://forum.xda-developers.com/showthread.php?t=2694917
---------- Post added at 07:40 AM ---------- Previous post was at 07:33 AM ----------
HTCNerdYoda said:
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).
Click to expand...
Click to collapse
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?
bruce7373 said:
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?
Click to expand...
Click to collapse
That's a really good question. Regarding ViperOne I could tell that running 1.8.0 (which was on 1.54.xx base) with 2.22.xxx FW worked flawlessly. So I would guess this should work just fine.
At least it's worth a try. Maybe better ask in the ROM thread.
Used arhd on my vivid for a bit. Must say it was an ok rom but lots of issues in general with all new roms on the vivid. Hardware too outdated. Maybe I'll give it a shot. Really leaning to a de-senced one.
HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
Ok, that's encouraging.
My CID is HTC__621 although I don't think I need that for just flashing back to stock recovery. My version is 1.54.709.12, so I downloaded the matching recovery from here http://forum.xda-developers.com/showthread.php?t=2701376 and flashed it. I confirmed that the stock recovery was installed by booting to it and getting the red triangle etc.
Then I downloaded the OTA upgrade and told it to install. I didn't watch the installation progress, but eventually it went to the red triangle screen and finally rebooted. But I'm still on 1.54.709.12, so I take that to mean the OTA failed. When I go to system update, it checks and finds one available and offers to download it again, which I haven't done.
I'm wondering if 'disabling' the weibo program could have caused the update to fail? Or possibly I *did* actually uninstall a stock program or two that I mentioned at #6 and that's what's preventing the update?
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?
Lanthanide said:
Ok, that's encouraging.
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?
Click to expand...
Click to collapse
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.
HTCNerdYoda said:
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.
Click to expand...
Click to collapse
Ok, so I put on a stock nadroid backup for HTC__621, changed to stock recovery, but the OTA update is still failing at around the 30% mark.
Actually I've just noticed that the stock ROM I put on doesn't have the calc or flashlight apps, but when I originally bought the phone they were on there. I had subsequently installed them using the apps on this thread here: http://forum.xda-developers.com/showthread.php?t=2699906
But maybe that is what is preventing me from doing the OTA now?
Edit: Right, so doing some more reading, it seems that HTC included these 'stock' apps in the /data directory instead of /system, so when doing the HTCDev install, they get wiped. But there was a note in that thread saying that for the One M7, they would actually do a hash of those apps too and if they weren't there the update would fail.
Someone linked to this thread http://forum.xda-developers.com/showthread.php?t=2703759 which says the APKs in the first one were from the M7, and these are from M8, and it also included another one called Seven Digital (yet another bloatware app I don't care about, hence why I didn't notice it was gone). Anyway I installed those 3 apps, but the OTA update still fails at around the 30% mark. I notice that the thread says preload APKs for 1.54.401.5, but my phone is running 1.54.709.12, so if they really are doing hashing for all of these apps, the update might be expectly a slightly different version and therefore fail the hash check?
Resolved!
Right, posting as new post because I solved it!
I searched through the collection thread and luckily found someone else who has HTC__621 who wanted to do the 4.4.3 upgrade as well. ckpv5 stepped in to lend a hand with this post: http://forum.xda-developers.com/showpost.php?p=54598052&postcount=1514
The TWRP stock ROM he posted there includes the flashlight and calculator app, as well as another one that looks like it was missing - WeChat. So now the OTA update has applied as expected. :highfive
I'll suggest Mr Hofs remove the existing nandroid backup for HTC__621 that he has there because it isn't complete.
Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Edit: More findings. In installing Xposed Framework on my phone, it can't do the 'classical' install because of S-on, instead it flashes it through recovery. So I suspect this could have been preventing the OTA update as well.
Lanthanide said:
Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Click to expand...
Click to collapse
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.
ckpv5 said:
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.
Click to expand...
Click to collapse
Ok, at least there's an explanation for what happened, but I didn't at any point explicitly lock the bootloader. All I did was:
1. Flash TWRP recovery
2. Flash the ROM you provided
3. Boot the phone, going through the setup stuff to configure wifi etc
4. Booted to fastboot and flashed to stock recovery
5. Rebooted phone, downloaded and installed OTA update
6. Booted to fastboot and re-flashed TWRP, ran nandroid backup and then installed superSU when offered
At what point would the locking of the bootloader have occurred?
Lanthanide said:
At what point would the locking of the bootloader have occurred?
Click to expand...
Click to collapse
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA
ckpv5 said:
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA
Click to expand...
Click to collapse
Ok, well like I said, I didn't explicitly choose the lock the bootloader at any point, and the nandroid backup that you created *did* have the extra apps in there (I confirmed their presence at step 3 in my sequence).
Note that I'm not trying to be argumentative, just explaining my experience in case this might help others in the future.
Hello,
My tmobile HTC One M8 was rooted (Supersu), unlocked bootloader, with TWRP. For the purposes of upgrading to Marshmallow, I restored stock recovery, re-locked bootloader, but was not successful in uninstalling SuperSu using Full unroot. The process hangs on 'Uninstalling'. I tried factory resetting from stock recovery, but after restarting the device SuperSU is still installed and rooted. Trying Full unroot again failed. Root checker confirmed that the phone was still rooted.
I tried loading the nandroid backup here , and installing from TWRP, but it fails to load.
EDIT - user error in loading the nandroid backup. After copying the unzipped folder and contents to TWRP folder, wiping the device then restoring, root was successfully uninstalled. Note that supersu did not uninstall with any other method. Marshmallow is now up and running.
murdoch07 said:
For the purposes of upgrading to Marshmallow, I restored stock recovery, re-locked bootloader, but was not successful in uninstalling SuperSu using Full unroot.
Note that supersu did not uninstall with any other method.
Click to expand...
Click to collapse
FYI, what you ended up doing, is mandatory (in order to OTA). You can't unroot and OTA, you need a stock (never rooted) ROM.
redpoint73 said:
FYI, what you ended up doing, is mandatory (in order to OTA). You can't unroot and OTA, you need a stock (never rooted) ROM.
Click to expand...
Click to collapse
That Is False, I Had A Rooted ROM (Slim6 HTC One M8 Android 6.0 STABLE Build) It's SuperUser/SuperSu Control Was In Dev. Options And I Still Managed To Run The OTA/RUU
---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------
murdoch07 said:
Hello,
My tmobile HTC One M8 was rooted (Supersu), unlocked bootloader, with TWRP. For the purposes of upgrading to Marshmallow, I restored stock recovery, re-locked bootloader, but was not successful in uninstalling SuperSu using Full unroot. The process hangs on 'Uninstalling'. I tried factory resetting from stock recovery, but after restarting the device SuperSU is still installed and rooted. Trying Full unroot again failed. Root checker confirmed that the phone was still rooted.
I tried loading the nandroid backup here , and installing from TWRP, but it fails to load.
EDIT - user error in loading the nandroid backup. After copying the unzipped folder and contents to TWRP folder, wiping the device then restoring, root was successfully uninstalled. Note that supersu did not uninstall with any other method. Marshmallow is now up and running.
Click to expand...
Click to collapse
Follow This Link, I Made A Thread That Will Show You How To Get Back To Stock, Doesn't Matter If You're Rooted Or Not
http://forum.xda-developers.com/tmobile-htc-one-m8/general/htc-m8-t-mobile-recovery-to-stock-t3493877
PM Me On Instagram @kailehkookie
Or Email Me [email protected]
If U Need Further Help
TheKookieGuy said:
That Is False, I Had A Rooted ROM (Slim6 HTC One M8 Android 6.0 STABLE Build) It's SuperUser/SuperSu Control Was In Dev. Options And I Still Managed To Run The OTA/RUU
Click to expand...
Click to collapse
OTA or RUU? They aren't remotely the same thing. They are very different, and have very different requirements. The fact you lumped them together, to me suggest you don't know the difference.
RUU doesn't care what mods are on the phone (root, custom ROM, etc.) as long as the bootloader is locked (not needed if s-off) and you are running the proper version RUU.
OTA is a completely different animal.
Or if you ran an RUU, before OTA, the RUU would already have returned you to a full stock (never rooted) image. Which is why the OTA would then work.
redpoint73 said:
OTA or RUU? They aren't remotely the same thing. They are very different, and have very different requirements. The fact you lumped them together, to me suggest you don't know the difference.
RUU doesn't care what mods are on the phone (root, custom ROM, etc.) as long as the bootloader is locked (not needed if s-off) and you are running the proper version RUU.
OTA is a completely different animal.
Or if you ran an RUU, before OTA, the RUU would already have returned you to a full stock (never rooted) image. Which is why the OTA would then work.
Click to expand...
Click to collapse
I'm sorry I misread what u said I understand where I was wrong. Thx for telling me