Database Info

Is there a safe root on stock 5.1.1 that doesn't wipe data?

I desperately need more storage on this phone.. :crying: The only way I have found to gain extra storage is to have root and use StickMount. I have a lot of info and game saves that I don't want to lose to a data wipe though. Is there a safe root method on stock 5.1.1 that doesn't wipe data?

The reason rooting with ChainFire's root tool wipes your data is becuase it boots to a custom one-time-use recovery (different from flashing twrp or cwm) to install the SU binaries. However, to do this an unlocked bootloader is needed. When the "oem unlock" command (what unlocks the bootloader) is run, it wipes all user data (the /data partition) as a security precaution, because one could flash something like twrp and then use adb commands to pull your personal files or remove the password on your lockscreen.
I cant verify if his works right now, i just got CyanogenMod 12.1 (pre-rooted) up and running, but you could try this: ROOTMaster
I used that to root my KFHD and my old LG Optimus G, both on older versions of android though. Let me know if it works for you

https://play.google.com/store/apps/details?id=com.rerware.android.MyBackup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
Try these 2 apps to backup your stuff, you should be able to backup your stuff without root, and then when you have root you could restore it. Just make sure to move the data from the phone because i believe oem unlock deletes everything from it.

My issue with those backup apps is this "* Users with root access can backup APKs AND DATA!". I have tried using backup apps in the past without root and the apps were backed up but I lost my game saves. Which, is really all I am worried about because I know how to back everything else up without root. I have lost games saves a few times switching from phone to phone without root and it sux. Also, with no data wipe I can avoid the hefty amount of time installing and setting up my phone environment. I do very much so understand the importance of a clean wipe and fresh environment though. With no data wipe and root I could back up app data and then do a fresh install.

It all depend on if you have already unlocked bootloader or not. If yes, just install custom recovery (TWRP) and install SuperSU. If not, there is no way to backup data without wiping your data, beside adb backup command.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351

So how do people transfer their game stuff to a new device? Does the adb backup command allow you to back up a device and transfer it onto another device? or will their be complications like file placement since it is a different device?

FlashFire with HTC One A9?

Anyone used ChainFire's FlashFire with the One A9?
I've used it for backups successfully but have yet to restore anything with it (a little squeamish to do so :silly.
And I'll just add, if anyone has used it and could offer any tips or procedures that would be great.

FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app
Click to expand...
Click to collapse
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?

theNdroid said:
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?
Click to expand...
Click to collapse
Of course. Root is required to use FlashFire. I use Xposed as well, and I've had no problems updating via FlashFire.

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Click to expand...
Click to collapse
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?

eelpout said:
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?
Click to expand...
Click to collapse
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***

CSnowRules said:
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***
Click to expand...
Click to collapse
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.

eelpout said:
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.
Click to expand...
Click to collapse
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.

CSnowRules said:
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.
Click to expand...
Click to collapse
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.

eelpout said:
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.
Click to expand...
Click to collapse
Ok, this post will go a bit off topic. That being said, I can offer two courses of action. I take no responsibility for anything in this post.
Safest--almost no risk (my personal preference)
1. Backup your data partition, including internal SD via TWRP to ext SD or USB OTG drive. Flash the latest RUU from HTC. Boot stock and apply OTAs until there are no more updates available. Fastboot flash the latest TWRP, and finally restore your data and flash the latest SuperSU via TWRP. Reboot your fully updated, rooted A9 with all your data still intact.
A little risky and untested to my knowledge--could result in a hard brick if something partially fails. FLASHING BOOTLOADERS IN FLASHFIRE IS STILL ALPHA FOR HTC DEVICES!!! This may work with s-on...but may require s-off.
Your system partition must have never been mounted r/w for this to work.
2. Download the OTA zips for your phone from the first update available to the latest and the latest SuperSU and TWRP. Use FlashFire to do everything in one shot. Select allow flashing bootloaders in FlashFire settings, select your OTAs for installation from oldest to newest (don't select restore boot and recovery), select TWRP and SuperSU for installation, disable everroot and preserve recovery. Cross your fingers and timidly press flash... If all is successful, you should have the same end result as option 1.
I STRONGLY recommend the first method, but if you're feeling lucky and decide to try the second method, please share how it goes, since this post is FlashFire related and this would be the ultimate test of FlashFire for our devices.

For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.

NuShrike said:
For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.
Click to expand...
Click to collapse
The solution for problem 1 can be handled in TWRP. The files can be deleted via TWRP's file manager or the built in terminal, which may be easier for some people.
Also, the solution for the corrupted data and internal SD is to create an image of the data partition (just like the system image backup option). This can be done via dd in TWRP or adb. It requires a large amount of storage and it takes longer, but I've had to do it, since I use VIP Access by Symantec for work. A normal file based backup in TWRP breaks that app. This also keeps the pin/fingerprint data intact.
If we could have that implemented in a user friendly manner, that would be great, but I'm sure CaptainThrowback and Chainfire both have bigger issues to deal with. I could probably figure out a solution, but the work wouldn't be worth it for my own benefit, since I'm fluent with the Linux command line.

Pre Rooted fw for the Z5

I am looking for a pre Rooted firmware, downloaded a custom Fw from XperiFirm and thought it'd be Rooted but it wasn't.
So I created a Pre Rooted FW using PRF Creator.
Done that, flashed the rom, using flash tool.
And somehow it didn't work.
So I was just wondering is there any pre Rooted firmwares out there I could download and flash from flash tool.
Also without losing any apps/app data if possible.
Thank you, please not my phone has not got a recovery.

You cannot flash a pre-rooted firmware without recovery so you need to unlock the bootloader and root
Sent from my E6653 using Tapatalk

No worries thank you.
I have tried unlocking the boatloads but keep getting errors.
My BL is unlockable

bjmag94 said:
No worries thank you.
I have tried unlocking the boatloads but keep getting errors.
My BL is unlockable
Click to expand...
Click to collapse
Hi
Did you try this ? ([GUIDE] StockROM -> # GUIDE -> UNLOCK BOOTLOADER)
What errors are you getting ?

I followed the guide off the Sony website to unlock the bootloader.
And I'm not sure what the errors are, I will have have to post them here soon when I get back on the computer
Emilen942702 said:
Hi
Did you try this ? ([GUIDE] StockROM -> # GUIDE -> UNLOCK BOOTLOADER)
What errors are you getting ?
Click to expand...
Click to collapse

bjmag94 said:
And I'm not sure what the errors are
Click to expand...
Click to collapse
Settings> Developer Options> Enable OEM unlock
set that and then try unlocking the bootloader

Awesome thanks worked for me, now my bootloader is unlocked can I flash a recovery then the PRF I created without losing any data?
SnowManWales said:
Settings> Developer Options> Enable OEM unlock
set that and then try unlocking the bootloader
Click to expand...
Click to collapse

bjmag94 said:
Awesome thanks worked for me, now my bootloader is unlocked can I flash a recovery then the PRF I created without losing any data?
Click to expand...
Click to collapse
I just looked at my phone after unlocking the Bootloader and it has deleted all my photo's off the phone, and some that I can not get back of my son, is there any way that I can get these back, I used FlashTool to unlock the Bootloader

bjmag94 said:
I just looked at my phone after unlocking the Bootloader and it has deleted all my photo's off the phone, and some that I can not get back of my son, is there any way that I can get these back, I used FlashTool to unlock the Bootloader
Click to expand...
Click to collapse
do you guys even try to think about a data backup before messing around and doing things that are able do delete your stuff?
Photos were stored on internal or SD card?
SD will be easy (if you haven't writen a lot of data on it).
Internal could be difficult...

They were on my internal.
Yes I did think about it, but only backed it up yesterday and didn't realise that there were more photo's taken since, because my partner also uses it to take photo's because of the camera quality..
So I only lost about 20 photo's but still beside the point..
I didn't think that unlocking your bootloader would delete anything?
So now I am about to look into flashing recovery onto the phone so I can flash the firmware that I created..
Would you suggest backing up my data again prior to flashing the recovery, and then the new firmware?
And will I lose all my app data or is there a way of backing that up as well?
Also how would I flash the recovery?
Thank you!
MKRashka said:
do you guys even try to think about a data backup before messing around and doing things that are able do delete your stuff?
Photos were stored on internal or SD card?
SD will be easy (if you haven't writen a lot of data on it).
Internal could be difficult...
Click to expand...
Click to collapse

I know your problem, I#ve also all photos of my children on my mobile, but exclusivly on the SD card and backup them with Foldersync once a day (to a 256 GB Flashdrive on my fritzbox)
Your Problem now is, that with each file operation on you internal storage (Android operations also count), the bytes of your pictures vanish.
If you're rooted (I think so), you should try easus Android Data Recovery, it's the only tool I know, that can handle internal storage from Windows:
http://www.easeus.com/android-data-recovery/android-phone-internal-storage-recovery.html
I use a lot of easus tools and I always get it back up and running, so give it a shot and good luck!
Unlocking the Bootloader just deletes your TA Partition and with that you DRM Keys. So without a TA Backup or a DRM Fix, your camera quality will descent drastically.

Thank you, I am not rooted as of yet..
But I will still give that a shot and see what I can recover..
Hopefully I haven't lost it completely, oh well that will teach me for next time, so how will I flash the recovery onto my phone?
So then I can flash the pre-rooted firmware to get root access.
Is there any simple guides to follow? Or simple methods, like a code to run through fastboot cmd?
Thank you once again in advanced..
MKRashka said:
I know your problem, I#ve also all photos of my children on my mobile, but exclusivly on the SD card and backup them with Foldersync once a day (to a 256 GB Flashdrive on my fritzbox)
Your Problem now is, that with each file operation on you internal storage (Android operations also count), the bytes of your pictures vanish.
If you're rooted (I think so), you should try easus Android Data Recovery, it's the only tool I know, that can handle internal storage from Windows:
http://www.easeus.com/android-data-recovery/android-phone-internal-storage-recovery.html
I use a lot of easus tools and I always get it back up and running, so give it a shot and good luck!
Unlocking the Bootloader just deletes your TA Partition and with that you DRM Keys. So without a TA Backup or a DRM Fix, your camera quality will descent drastically.
Click to expand...
Click to collapse

1. Flash Recovery "twrp-3.0.2-0-E6653-20160504.img" (extract the zip before) via fastboot
2. Flash a rootable Customkernel (boot.img) (extract Z5_AndroPlusKernel_Permissive_v36.zip) via fastboot.
3. Flash "SuperSU-v2.76.zip" (copy the zip to SD or internal) via TWRP
Download the files here: https://www.dropbox.com/sh/6424n9sop6kqmj7/AADtEiR3EeZXxedR7_g9lA-ma?dl=0
I've rooted my brand new Z5 a week ago with these files.
4. Do a DRM fix to get the camera quality back you're used to, without you will have really bad pictures in low light condition:
http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
If you want to do a fresh systemflash before rooting your device, use Flashtools xperifirm to get the latest Marshmallow 6.0.1 Stock Rom
Do not check any point on "wipe" for flashing, unless you want to setup the whole phone new. It's possible that you have to if you update from 5.1.1
KR
Rashka

Thank you I am already running marshmallow 6.0.1.
I am using the Custom AU one.
I can't manually root it via SuperSU or anything though, not sure if it is a rootable firmwatte or not..
But how do I flash the recovery?
Sorry I new to all this, I done my Z2 about two years ago, followed a guide off here, but it was more simple for the Z2 than the Z5 I think..
And only had to flash a custom rom and it was already rooted and then had to install busybox to get recovery and done it that way..
But now I would not have a clue what the heck I am doing haha..
I will not lose any data while flashing a recovery will I?
MKRashka said:
1. Flash Recovery "twrp-3.0.2-0-E6653-20160504.img" (extract the zip before) via fastboot
2. Flash a rootable Customkernel (boot.img) (extract Z5_AndroPlusKernel_Permissive_v36.zip) via fastboot.
3. Flash "SuperSU-v2.76.zip" (copy the zip to SD or internal) via TWRP
Download the files here: https://www.dropbox.com/sh/6424n9sop6kqmj7/AADtEiR3EeZXxedR7_g9lA-ma?dl=0
I've rooted my brand new Z5 a week ago with these files.
4. Do a DRM fix to get the camera quality back you're used to, without you will have really bad pictures in low light condition:
http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
If you want to do a fresh systemflash before rooting your device, use Flashtools xperifirm to get the latest Marshmallow 6.0.1 Stock Rom
Do not check any point on "wipe" for flashing, unless you want to setup the whole phone new. It's possible that you have to if you update from 5.1.1
KR
Rashka
Click to expand...
Click to collapse

Why dont your take a backup of the phone via Xperia Companion?
Alternatively, use Titanium Backup (free on Google Play) after you are rooted - before flashing your own ROM
Did you read the WHOLE guide @Emilen942702 linked you to? Especially sections [GUIDE] GENERAL and [GUIDE] StockROM / # GUIDE
If you use AndroPlus kernel v.36 then no need to do the DRM fix as it is already included in the kernel.

MKRashka said:
do you guys even try to think about a data backup before messing around and doing things that are able do delete your stuff?
Photos were stored on internal or SD card?
SD will be easy (if you haven't writen a lot of data on it).
Internal could be difficult...
Click to expand...
Click to collapse
yes, that why i back everything i want to sd card and cloud storage, all automated
sent from my Xperia Z5

I flashed the Kernel and Recovery and installed SuperSU.
And the done the DRM, and now I can not use google play, keep getting an error saying that it can not connect to google play or some crap..
Any easy fixes without having to completely wipe and install a fresh rom?

bjmag94 said:
I flashed the Kernel and Recovery and installed SuperSU.
And the done the DRM, and now I can not use google play, keep getting an error saying that it can not connect to google play or some crap..
Any easy fixes without having to completely wipe and install a fresh rom?
Click to expand...
Click to collapse
Try to clear data/cache/force stop from :
-Google Services Framework (type the three dots in the upper right corner, and tick "display system apps")
-Google Play Store
-Google Play Services
If it doesn't work
Try to delete hosts file from /etc/hosts (with a root explorer) and reboot
And btw, do you have Freedom installed ?

I will give this a try, and yeah I do, about to uninstall it as it keeps changing on me
Emilen942702 said:
Try to clear data/cache/force stop from :
-Google Services Framework (type the three dots in the upper right corner, and tick "display system apps")
-Google Play Store
-Google Play Services
If it doesn't work
Try to delete hosts file from /etc/hosts (with a root explorer) and reboot
And btw, do you have Freedom installed ?
Click to expand...
Click to collapse

bjmag94 said:
I will give this a try, and yeah I do, about to uninstall it as it keeps changing on me
Click to expand...
Click to collapse
That's the reason, try to stop it Belfort uninstall, if you can't then just delete host file
Envoyé de mon E6653 en utilisant Tapatalk

How To Backup *Everything*

Okay, I'm not a techie and I want to know how to backup everything on my phone before I attempt to root my OnePlus One using KingRoot.
At first I naively thought that copying all files and folders from my phone to my laptop would work, but 3 things seem to suggest it's not as easy as that:
I get an error message every time I try copying the files in the ColorNote folder
I saw a mention somehwere that to backup something called EFS you need to run a special app
I'm guessing that my contacts and SMS messages will not be backed up just by copying files and folders from my phone.
So my question is how do I backup *everything* (not just those things I have specifically refered to here) just in case something goes wrong when running KingRoot?
I would prefer not to have to upload my data to the cloud to back it up if at all possible.
Thanks fine people!

Reece Pondwell said:
Okay, I'm not a techie and I want to know how to backup everything on my phone before I attempt to root my OnePlus One using KingRoot.
At first I naively thought that copying all files and folders from my phone to my laptop would work, but 3 things seem to suggest it's not as easy as that:
I get an error message every time I try copying the files in the ColorNote folder
I saw a mention somehwere that to backup something called EFS you need to run a special app
I'm guessing that my contacts and SMS messages will not be backed up just by copying files and folders from my phone.
So my question is how do I backup *everything* (not just those things I have specifically refered to here) just in case something goes wrong when running KingRoot?
I would prefer not to have to upload my data to the cloud to back it up if at all possible.
Thanks fine people!
Click to expand...
Click to collapse
Do you plan to unlock bootloader and flash custom recovery? If not and you just want root,you can safely skip all of this backup part as kingroot/kingoroot won't do any harm to your device.
Also if you don't like kinguser as default granting roots app,you can change it into SuperSu too.
Here's a great guide by @Nishidh
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965

Mr.Ak said:
Do you plan to unlock bootloader and flash custom recovery? If not and you just want root,you can safely skip all of this backup part as kingroot/kingoroot won't do any harm to your device.
Also if you don't like kinguser as default granting roots app,you can change it into SuperSu too.
Here's a great guide by @Nishidh
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Click to expand...
Click to collapse
Hi and thanks for your reply.
I don't plan to unlock the bootloader. I also wasn't planning on flashing a custom recovery (tbh I don't even know what "flashing" means), however I was thinking of using the KingRoot desktop version and their website states that "the desktop KingRoot version can only be flashed using recovery custom tools". I'm guessing that means that when I run KingRoot it will automatically flash a custom recovery.
BUT if doing that means that my data is wiped then I will stick to the android version even though at the moment I am trying to write an absolute minimum of data to my phone. (My reason for wanting to root is to have one last attempt to recover a load of data that I lost off my phone using a file recovery program that requires root access).
I know that if I run KingRoot just to root it is not supposed to delete any data, but I thought that it was generally thought to be good practice to backup your data before the process anyway just in case something untoward happens (in fact I *think* I read a reccommendation to do that on the official KingRoot website).
Thanks for the video link & tip and, of course, your advice!

Reece Pondwell said:
Hi and thanks for your reply.
I don't plan to unlock the bootloader. I also wasn't planning on flashing a custom recovery (tbh I don't even know what "flashing" means), however I was thinking of using the KingRoot desktop version and their website states that "the desktop KingRoot version can only be flashed using recovery custom tools". I'm guessing that means that when I run KingRoot it will automatically flash a custom recovery.
BUT if doing that means that my data is wiped then I will stick to the android version even though at the moment I am trying to write an absolute minimum of data to my phone. (My reason for wanting to root is to have one last attempt to recover a load of data that I lost off my phone using a file recovery program that requires root access).
I know that if I run KingRoot just to root it is not supposed to delete any data, but I thought that it was generally thought to be good practice to backup your data before the process anyway just in case something untoward happens (in fact I *think* I read a reccommendation to do that on the official KingRoot website).
Thanks for the video link & tip and, of course, your advice!
Click to expand...
Click to collapse
No don't use the desktop version.Use the mobile version and make sure you've fast net connection.Kingroot doesn't install recovery.It just roots,though,ofc not as good as rooting from recovery but still enough for daily tasks.

Mr.Ak said:
No don't use the desktop version.Use the mobile version and make sure you've fast net connection.Kingroot doesn't install recovery.It just roots,though,ofc not as good as rooting from recovery but still enough for daily tasks.
Click to expand...
Click to collapse
Thanks for that. I've tried running KingRoot app, but having some problems as reported here: https://forum.xda-developers.com/oneplus-one/help/kingroot-app-t3573101

Reece Pondwell said:
Thanks for that. I've tried running KingRoot app, but having some problems as reported here: https://forum.xda-developers.com/oneplus-one/help/kingroot-app-t3573101
Click to expand...
Click to collapse
Yes,its totally safe to quit the app.
You can try Kingoroot too.

Mr.Ak said:
Yes,its totally safe to quit the app.
You can try Kingoroot too.
Click to expand...
Click to collapse
Thanks Mr Ak!

Backup and Restore - a Hybrid Method (Android 9)

I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup Boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img (extract from ap section of downloaded firmware for stock) or install UPie
2. Restore Boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files to /system/system
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.

If anyone can think of another system directory which I can backup and restore please let me know.

physwizz said:
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img
2. Restore boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
Click to expand...
Click to collapse
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.

Jeremy_J7 said:
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWinRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Click to expand...
Click to collapse
I think the system settings are stored in /data
I'll add it to the list.

physwizz said:
I think the system settings are stored in /data
I'll add it to the list.
Click to expand...
Click to collapse
Test it before you add to the list, can't be giving these people false information bro ?

Jeremy_J7 said:
Test it before you add to the list, can't be giving these people false information bro
Click to expand...
Click to collapse
True

I debloated from here
https://forum.xda-developers.com/galaxy-a20/development/debloat-samsung-a20-variants-t4070957
Then I added the updated camera from Ultimate Pie.
My app folders are here
https://mega.nz/file/dtkkES5L#YfHwWC3rlswwYUeA_cdUESCMQo8rvq8k8n20N-oc-8w

Alright will take a look, is this bootloader specific?

Jeremy_J7 said:
Alright will take a look, is this bootloader specific?
Click to expand...
Click to collapse
Not sure.
If it doesn't work it might reboot into recovery and then you need to copy and paste your own /app and /priv-app folders back in place.

@jajk
Try this

@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?

jajk said:
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
Click to expand...
Click to collapse
If you're talking about the red text that talks about 'official binaries' when booting after you flash TWRP (FRP LOCK) then there's a very easy fix.

@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....

jajk said:
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
Click to expand...
Click to collapse
I got that because i was using old data
solved by doing a clean install
The data was then good in future

@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different

jajk said:
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
Click to expand...
Click to collapse
You didn't restore old data?
Clean install?

@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....

jajk said:
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
Click to expand...
Click to collapse
What does red writing say?

@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....

jajk said:
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
Click to expand...
Click to collapse
I've had that twice
1. When I forced reboot before UPie was finished installing
2 when I didn't wipe caches , data and system before installing UPie
Could also be Samsung Conspiracy Theorist Detection Program (SCTDP) lol