Here's my normal workflow when doing a clean flash. I've done this with my OnePlus One for years:
1) Install Rom with TWRP, root with SuperSU
2) Install TI Backup and restore all my apps
3) Fully unroot with SuperSU (restore stock boot, do not restore stock recovery)
I have to unroot because I use the Outlook App for work email. I've never figured out how to get around root to use Outlook. Anyway, I can't get this method to work with my new OnePlus 5T. I go through the steps and get everything reinstalled and set up the way I want, running the stock ROM. When I go to unroot, the phone gets stuck in boot with a blank screen and a greyish blue LED light. It just sits there that way for what seems like forever. I haven't left it that way for longer than about an hour, but I don't think it should take that long.
I've tried unrooting with SuperSU and it wont work. It gets stuck in boot with that LED light on. So, I started from scratch, reinstalled the ROM and everything, and rooted with Magisk. When I try to unroot with Magisk it does the same thing. It still gets stuck in boot with that light. I'm not ask familiar with Magisk and I chose the option "complete uninstall."
EDIT- I tried flashing the latest Magisk uninstaller from TWRP. The phone gets stuck in boot with the light on using this method as well.
What am I doing wrong here? How can I get rid of root after using it to install my apps with TI Backup?
In trwp go to wipe then advanced, wipe caches, system and data, do not do internal storage, then make a clean install of ur rom, make sure to always back up and I thought titanium required root anyway, so u may not be able to restore it
U may be able to just wipe caches and system and clean install ur rom and that should keep data and possible remove root, have u tired to use magisk and add app to magisk hide
Titanium does require root, but once I'm done restoring all my apps and data, I really don't use root at all anyway. I was hoping to avoid a clean install of the ROM. I'll try adding Outlook to magisk hide. Again, I'm not very familiar with Magisk, so that's a good suggestion. Thanks!
Edit- I added Outlook to the Magisk Hide list and rebooted. Outlook still says the phone is rooted and won't work. I've run into this issue in the past which is why my usual solution is to fully unroot.
I managed to get unrooted by flashing the magisk uninstaller, and rebooting to recovery all from within TWRP. Then I dirty flashed the stock ROM. Problem is, then I have to boot to download mode and reinstall TWRP from a computer using fastboot. I'm still looking for an easier way of unrooting.
Related
My fire is rooted and I have voodoo OTA rootkeeper installed, I temporary unrooted to download from amazon store, I did not restore root and now it seems that voodoo is unable to restore the root.
Is there any way to restore root without restoring and rerooting device.
No you will need to use kfu to reapply root I have had to do the same thing when a restored a backup that I had forgotten to change settings back on ota root keeper. You could also flash modaco right over your existing without wiping anything except dalvik and cache to reset your root permissions this will also give you an insecure boot.IMG that will allow for shell.
thanks for the info, but I am not sure how to do this and I forgot to mention I am using a mac.
ROM http://forum.xda-developers.com/showthread.php?t=1439916 methods for flashing http://forum.xda-developers.com/showthread.php?t=1923010 choose between the two ROM flashing methods there both with different results one is clean the other could be dirty I don't know the state of your device. Skip trying to reroot it just flash modaco.
thanks, got it working.
No problem which route did you go?
Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.
Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.
In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0
It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.
Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.
I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.
I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)
I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.
Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it
Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.
I finally got around to rooting my 5x this last weekend. I flashed the latest version of the SuperSU update zip. After flashing I used the SafetyNet Helper to check if my phone successfully jumps through all of Google's hoops. I failed the test, so I went back to recovery and restored my boot partition from my nandroid backup, which I created immediately after flashing and booting to TWRP. When I tried rebooting system I got a message my software was corrupt and phone got stuck on boot screen (Google logo with annoying padlock to indicate bootloader is unlocked). Went back to TWRP and tried restoring both boot and system but it was still getting stuck on the boot screen. So I downloaded the factory images, flashed everything but userdata, and phone was working again.
After some digging I found that I failed to read the fine print for the newer versions of SuperSU, stating that if you want the systemless install you have to write a couple of settings to a file in /data that the installer checks. Did this and root worked and passed the SafetyNet checks and I was happy. Then I installed AdAway and flashed systemless hosts and I'm even happier. But I'm still wondering why it was saying my software was corrupted, even after I restored my nandroid backup. Any ideas?
jgummeson said:
I finally got around to rooting my 5x this last weekend. I flashed the latest version of the SuperSU update zip. After flashing I used the SafetyNet Helper to check if my phone successfully jumps through all of Google's hoops. I failed the test, so I went back to recovery and restored my boot partition from my nandroid backup, which I created immediately after flashing and booting to TWRP. When I tried rebooting system I got a message my software was corrupt and phone got stuck on boot screen (Google logo with annoying padlock to indicate bootloader is unlocked). Went back to TWRP and tried restoring both boot and system but it was still getting stuck on the boot screen. So I downloaded the factory images, flashed everything but userdata, and phone was working again.
After some digging I found that I failed to read the fine print for the newer versions of SuperSU, stating that if you want the systemless install you have to write a couple of settings to a file in /data that the installer checks. Did this and root worked and passed the SafetyNet checks and I was happy. Then I installed AdAway and flashed systemless hosts and I'm even happier. But I'm still wondering why it was saying my software was corrupted, even after I restored my nandroid backup. Any ideas?
Click to expand...
Click to collapse
In general, phones get messed up after flashing backups or changing through multiple ROMs. The backups like nandroid backup are primarily meant for immediate resolution and a full fresh install is always recommended for any device (be it a desktop, laptop or any mobile device). Its always better to find the best suited ROM as per your needs and stick with it rather than messing up by flashing different zips through TWRP. Cheers :good:
ultraquantum said:
In general, phones get messed up after flashing backups or changing through multiple ROMs. The backups like nandroid backup are primarily meant for immediate resolution and a full fresh install is always recommended for any device (be it a desktop, laptop or any mobile device). Its always better to find the best suited ROM as per your needs and stick with it rather than messing up by flashing different zips through TWRP. Cheers :good:
Click to expand...
Click to collapse
Right. Nandroid can quickly get you out of the most common sticky situations by restoring the most commonly messed with partitions (system, boot, data). There are a bunch of other partitions that can mess things up. The only things flashed though were TWRP and SuperSU (non-systemless by mistake). I'm just trying to understand what might've gone wrong. Something outside of system/boot must have been modified and broke the boot, only after restoring the boot partition. Think I figured it out though - I looked at the update script for SuperSU and it looks like it could be messing with the vendor partition (at least for non-systemless installs). When I flashed back the stock boot image a change in the vendor partition must have tripped dm-verity, which the SuperSU installer had disabled when it updated the boot image.
I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help
stiarlitserenity said:
I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help
Click to expand...
Click to collapse
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.
Reflash rom, kernel and supersu. You shouldn't lose anything doing that.
sfhub said:
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.
Click to expand...
Click to collapse
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
stiarlitserenity said:
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
Lesson learned bud. Half of the reason for TWRP and CWM is to have a full recent/current backup. Its always been like this. All roms, tweaks, xposed, write-ups or threads all say "make a backup" A backup is needed when something goes wrong. Notice the word "when" its not a if something goes wrong. Playing with androids involves way to much stuff and things do go wrong. Everytime your gonna do something just make a backup and delete your previous backup. Keep the backup on a sd card and delete the previous one. You put yourself in a situation like street racing on the freeway in a thunderstorm on new years eve. Not being a **** but for years and years now there a thousands of tutorials on this stuff. How to use adb, fastboot, twrp, soft brick, hard brick, de-brick tool. I don't know where the link is but I have a xposed script to flash in recovery that disables xposed and all modules from recovery in case of a bad module. If that can be found still I suggest that using xposed
FYI. The two replies before this told you what to do. If your looking for a easy everything is 100% going to be ok and you won't lose your text messages its probably not going to happen.
stiarlitserenity said:
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
If you are on the stock rom, flash the stock boot.img and stock system.img either in TWRP or via fastboot will erase any mods in /system (including Xposed). This will return you to a stock setup. Your apps, sms, and data would be retained.
To do this, download the factory image that matches your rom base. The July OTA is MTC19Z by the way. June is MTC19V, you'll have to remember which one you were on. This can be found on Google's Nexus factory image website. Next, unzip the downloaded file then flash the boot.img and system.img in TWRP (transfer the files to your phone). Alternatively, you could learn to use fastboot. Follow section 10 of this amazing guide by Heisenberg, but flash only boot.img and system.img.
You *should* be able boot up and learn from your mistakes as others have said. If you still have issues, factory reset and charge this loss to the game.
Sent from my Nexus 5X using Tapatalk
So, one of the new features of TWRP is to install as read-only, which is pretty useful for making a "clean" backup of your ROM before messing with it, but it prevents you from giving it root access.
Thing is.... the option doesn't seem to appear again if you want to install TWRP with that access later. The prompt no longer appears when you boot into recovery, I see nothing under the Settings or Advanced menu to install it with full permissions, and re-installing the recovery image doesn't make it ask again either.
How would one go about giving it write access? And also..... is there any reason to? If I don't have it installed with full rights on system, then can selecting to do a factory wipe from the phone remove it? And would it survive a wipe if it was? Would it survive an OTA update too, or would that wipe the recovery no matter what? If you even can do an OTA update anymore after installing TWRP and SuperSU (but staying on the stock rom). And would installing TWRP with these full rights trip that encryption/loss of radio issue that SuperSU causes?