Fix error 255 on TWRP backup/restore - OnePlus 5 Questions & Answers

Im using the newest blu_spark TWRP with my OP5 OEM unlocked rooted with magisk running the 5.01 OOS.
BACKUP
Before running a backup do the following in TWRP/Advanced/Terminal
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
You will successfully be able to backup!!
RESTORE:
 @simo6 Gave me the solution. You need to go into the TWRP terminal before doing a restore and delete:
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
then restore your backup!

krumbman0wnz said:
Im using the newest blu_spark with my phone OEM unlocked rooted with magisk running the 5.01 OOS.
Click backup have 'createTarFork() process ended with ERROR=255'. copied log and found :
data/system/999
data/system_ce/999
data/misc/999
data/misc_ce/999
data/user/999
data/user_ce/999
Were unable to be backed up. so after deleting these folders through TWRP terminal i can backup without error.
However i cannot restore, as i keep getting the 'extractTarFork() process ended with ERROR=255' error on restoring. why cant our recovery just work? Ever since oreo launched on OP its been nothing but headaches. Every update triggers my encryption and forces me to totally wipe the phone and start from fresh install. (no matter how many of these xda update guides i follow). Ive been rooting and "modding" phones since the G1 and ive never had so many issues.
Click to expand...
Click to collapse
Even before restoring u need to delete those folders. Worked for me.

How can you delete these folders when restoring? there is nothing on the phone besides the backup file folder. literally nothing.

krumbman0wnz said:
How can you delete these folders when restoring? there is nothing on the phone besides the backup file folder. literally nothing.
Click to expand...
Click to collapse
Once u are in twrp u open file manager and delete manually the 999 folders since the system recreates them at every reboot

simo6 said:
Once u are in twrp u open file manager and delete manually the 999 folders since the system recreates them at every reboot
Click to expand...
Click to collapse
Thanks for the heads up. I'm sure this will help tons of people!!!
Props!

didn't someone make a twrp zip for this?

We need to type this in terminal

krumbman0wnz said:
Im using the newest blu_spark TWRP with my OP5 OEM unlocked rooted with magisk running the 5.01 OOS.
BACKUP
Before running a backup do the following in TWRP/Advanced/Terminal
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
You will successfully be able to backup!!
Click to expand...
Click to collapse
I'm using latest by_ibe twrp and it's not working. No 999 folders found. Backup fails at system partition with error 255.
Will try bluspark twrp.

Hey guys,
after some struggle I was able to restore my backup. When I selected reboot system, my phone was stuck on the oneplus scree...so I powered it off, started recovery and dirty flashed rom to be able to boot. It booted normaly with restored settings, layout and stuff. But then I recognized that some data was missing. I have 2 apps with important (personally important for me) statistical data, but the data is lost.
Is there a possibility to restore this data somehow?
When I've created the mentioned backup, I've checked every point, so everything should have been stored.
Thanks in advance.

Sorry but the only permanent solution for these errors while backup or restore is to factory reset your device and never touch the parallel app in setting....so far that's what solve my problem and now i can make backup and restore without any problem!

cam someone explain why i cant cd to /data/system/?

I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.

hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.

hello i have the Oneplus6T with OxygenOs and i having the same problem, i cant do a nandroido backup from twrp having the same problem 255, i have deleted the parallel app and the account but there is no luck at the moment.
any other advice ?

I deleted all folders mentioned above, deleted all parallel apps... It's not working for me.. I am getting same error when trying to make a backup.. :/
Edit : I successfully fixed error. This working for me : https://forum.xda-developers.com/showpost.php?p=76760812&postcount=1

krumbman0wnz said:
Im using the newest blu_spark TWRP with my OP5 OEM unlocked rooted with magisk running the 5.01 OOS.
BACKUP
Before running a backup do the following in TWRP/Advanced/Terminal
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
You will successfully be able to backup!!
RESTORE:
@simo6 Gave me the solution. You need to go into the TWRP terminal before doing a restore and delete:
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
then restore your backup!
Click to expand...
Click to collapse
did not work with op5t oos 9!!

I just ran into this too. I'm looking here after the fact and the way I fixed it and don't see what I did so this is it:
- for me, it was the presence of multi-user directories in numerous places. I don't use multi-users on pie so not sure why they're there, but it hurts nothing to delete them.
- if I only deleted 999, that'd not have worked for me
- First: I read the recovery.log file after rebooting after the failed backup. It's a big file, so I transferred it to a laptop and used notepad+ --
- Look in there for the error (tarfork) and then look for the file/directory that began the chain of errors. Mine happened to be /data/vendor_ce/10
- Go to your /data/ folder in root explorer (or equiv):
- Do an ls */10 to find out all the places the 10 user occurs or you'll then get the error on the next 10 file. For me it was 5 other dirs.
- All you should have for user number directories in those places is 0 (unless you use multiple users and then I don't know).
- delete each one. I did it all from adb on a booted op5. so like this: "rm -r /data/{folder}/xx" where {folder} is where you found the 10 11 whatever, and xx is user-numbers other than 0
- when you've got them all gone, reboot directly into recovery so you have no chance of the system recreating them (so for me: adb reboot recovery)
- Backup. Mine worked no errors and was actually faster too because the errors take time to timeout.
- reboot system
Careful when using 'rm -r' that you only delete what you want to or you can mess up your phone. - cheers.
Edit: Twrp Version: Probably should mention SW versions: Twrp, latest 991 blu_spark twrp, OS: 9.0.3 Pie, Other: xXx noLimits Rom/Module
-

simo6 said:
Even before restoring u need to delete those folders. Worked for me.
Click to expand...
Click to collapse
Do you mean even before backing up?

How to fix error 255 twrp oneplus 5
hachamacha said:
I just ran into this too. I'm looking here after the fact and the way I fixed it and don't see what I did so this is it:
- for me, it was the presence of multi-user directories in numerous places. I don't use multi-users on pie so not sure why they're there, but it hurts nothing to delete them.
- if I only deleted 999, that'd not have worked for me
- First: I read the recovery.log file after rebooting after the failed backup. It's a big file, so I transferred it to a laptop and used notepad+ --
- Look in there for the error (tarfork) and then look for the file/directory that began the chain of errors. Mine happened to be /data/vendor_ce/10
- Go to your /data/ folder in root explorer (or equiv):
- Do an ls */10 to find out all the places the 10 user occurs or you'll then get the error on the next 10 file. For me it was 5 other dirs.
- All you should have for user number directories in those places is 0 (unless you use multiple users and then I don't know).
- delete each one. I did it all from adb on a booted op5. so like this: "rm -r /data/{folder}/xx" where {folder} is where you found the 10 11 whatever, and xx is user-numbers other than 0
- when you've got them all gone, reboot directly into recovery so you have no chance of the system recreating them (so for me: adb reboot recovery)
- Backup. Mine worked no errors and was actually faster too because the errors take time to timeout.
- reboot system
Careful when using 'rm -r' that you only delete what you want to or you can mess up your phone. - cheers.
Edit: Twrp Version: Probably should mention SW versions: Twrp, latest 991 blu_spark twrp, OS: 9.0.3 Pie, Other: xXx noLimits Rom/Module
-
Click to expand...
Click to collapse
Please pin this as the answer. This is the right answer.

ERROR 255 FACT AND FIX:
The error 255 is caused due insufficient space on the phone
I've discovered that while trying to restore backup on my S6. System part was around 3gb, data aroud 9gb, efs and modem few hundred mb. While trying to restore every thing at once, i would get error 255 (While data was recovering). So while phone being in TWRP, I've deleted everything from backup and phone that i can copy afterwards, except data part of backup and tried to restore only data and it worked! After data restore, i haven't rebooted but have deleted data backup and copied system, efs and modem part of backup from my pc to phone and restored them and everything went fine
Then I've rebooted and phone works like charm!
So, to fix error 255 you have to free space, especially if your backup files are huge

Related

Helppp removing .apks with sdk method

i try this on the comment prompt while phone running.
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
and it'll say:
rm failed for -f, read only file system
it wont let me write on the system im guessing.
Now i tried doing the same thing but phone mode is on recovery.
I have the nand protection unlocked so when i get to recovery mode
i have already the custom recovery setup showing, i don't run the recovery-windows.bat.
now when i type this on the comment prompt
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
after i hit enter it shows me
#
so im assuming the apk. has been removed
after i exit the comment prompt and i wipe the dalvik-cache
i reboot the phone and all the apps i removed are still there and running still.
help please

Any way to write a batch script to remove apps in Clockwork?

This is a list of the apps I remove while in clockwork, with /system mounted etc... My question is, is there a way to have it do these commands automatically? I hate having to copy from notepad the commands as i have them saved, then right click in my cmd, paste, enter each and every single one
rm -r amazonmp3_1.6+24_signed_zipaligned.apk
rm -r AppPack2.0.apk
rm -r YouTube.apk
rm -r IM.apk
rm -r Mail.apk
rm -r vvm-signed.apk
rm -r Faves.apk
rm -r mytouchmusic-signed.apk
rm -r HtcTwitter.apk
rm -r com.htc.TwitterWidget.apk
rm -r FavesWidget.apk
rm -r htcmailwidgets.apk
rm -r HTCSetupWizard.apk
rm -r SelfHelp.apk
rm -r Hoops.apk
rm -r NatureTheme.apk
rm -r Palazzo.apk
rm -r Surf.apk
rm -r Wildflower.apk
rm -r com.htc.FriendStreamWidget.apk
rm -r com.htc.NewsReaderWidget.apk
rm -r com.htc.StockWidget.apk
rm -r com.htc.WeatherWidget.apk
You could create a batch script and put adb shell before each line, then when you have mounted /system just type in the name of the script IE remove.bat
sent from my *ROOTED* myTouch 3G Slide
adb does have an "uninstall" option. I'm not sure it would work in this situation. You could try a batch file that has "adb uninstall AppPack2.0.apk" for example and see if it works.
^ Will that work on the Slide?
<--- ADB newb
I tried removing apps using root explorer but when I mount the system again the phone reboots and the app is still there. Im just trying to find a way to remove some of the pointless apps.
You have to be in recovery mode because the /system NAND is protected otherwise.
Here's what I do:
1. Reboot the phone in recovery.
2. Run Clockworkmod (by applying update.zip in recovery).
3. Mount /system in Clockworkmod.
4. Now using adb shell, you can remove the apps in /system/app.
Thankyou very much

please someone help to restore info

ahhh... so I had done method 1 of lagfix and I was looking to do CFLagfix instead...
method 1:
db shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
undo method 1..
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
BUT.. here's where I messed up... I accidentally looked at the wrong line of the undo and I'm pretty sure I did the undo method (restore to point of application)
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot
So now when I reboot all I get are a bunch of force closes...
I can't even get into recovery by holding down the volume keys and power
i have a nandroid backup but I can't get into recovery to restore it.. i'm not sure if there is a way to get into clockwork using adb commands?
BUT.. when I try a SU command it fails bc I get a force close on the phone. I'm just lost so if anyone can help me restore this thing.. or at worst.. to just restore to factory settings..I'd appreciate it.
adb reboot recovery should get you into recovery.
recovery doesn't work. says not permitted.
decided to flash the stock rom using ms_gurus method in http://forum.xda-developers.com/showthread.php?t=728698
hopefully i'll have a working phone so i can go about restoring

sl4a shell script help

Hi all,
I'm trying to run a shell script in sl4a but I'm running into problems. Here's what I want to do: change ADW configuration files in one click (since the app doesn't yet do it natively). There are two files that need to be changed for this to happen:
Code:
/data/data/org.adwfreak.launcher/databases/launcher.db
/data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
I'm trying to delete those files and copy in new files from a stored location on the SD card but I can't get the sl4a script to run the following rm commands:
Code:
rm -rR /data/data/org.adwfreak.launcher/databases/launcher.db
rm -rR /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
I use
Code:
su -c
before the rm commands to run them as root, but the error then is that the /data partition is not mounted (which I find strange since it should be rw anyway...). I've tried using
Code:
mount -o remount,rw /dev/block/userdata /data
and it looks like it runs but then it doesn't work and I can't rm the files anyway.
Am I running into a limitation of sl4a or shell scripts in sl4a? I can rm the files from the terminal, so I'm not sure what the issue is. I'm very new to this (obviously) so any tips would be helpful. Thanks!
Here is my full script currently:
Code:
#!
kill android.process.acore
kill org.adwfreak.launcher
busybox rm -R /data/data/org.adwfreak.launcher/databases/*
busybox rm -R /data/data/org.adwfreak.launcher/files/*
busybox rm -R /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw_ex_launcher.db /sdcard/ADW/Honeycomb/adw_ex_launcher.db
cp /sdcard/adw_ex_settings.xml /sdcard/ADW/Honeycomb/adw_ex_settings.xml
cp /sdcard/ADW/Portrait/adw_ex_launcher.db /sdcard/adw_ex_launcher.db
cp /sdcard/ADW/Portrait/adw_ex_launcher.db /data/data/org.adwfreak.launcher/databases/launcher.db
chmod 664 /data/data/org.adwfreak.launcher/databases/launcher.db
cp /sdcard/ADW/Portrait/adw_ex_settings.xml /sdcard/adw_ex_settings.xml
cp /sdcard/ADW/Portrait/adw_ex_settings.xml /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
chmod 664 /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
exit
When I test the rm commands in the sl4a shell, they don't remove the files even when the /data partition is mounted. I've tried all that I know. Help please!
Sent from my DROIDX
I don't know what you are trying in your second post, but from your first post I would say:
Code:
su
busybox rm -r /data/data/org.adwfreak.launcher/databases/*
busybox rm -r /data/data/org.adwfreak.launcher/files/*
busybox rm -r /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw/prefs.xml /data/data/org.adwfreak.launcher/shared_prefs/
..
kill org.adwfreak.launcher
If you do "chmod 664" on the files, you also have to do "chown & chgrp" or the launcher won't be able to write into the settings xml's/db's.
And /data ist mounted rw, everything else would be senseless.
Thanks for the response.
I'm trying to change ADW configuration with one click. I'm going to use Tasker to create a widget that, when clicked, runs a script. That script will:
1. delete the current ADW configuration files (launcher.db and adw_ex_preferences.xml)
2. copy the target configuration files to the proper places (and set permissions, owner, group)
3. restart ADW so that the configuration is loaded
OR
3. open the ADW settings page so that I can click "restore desktop" and "restore preferences" and have the configuration loaded in an almost-one-click solution.
The script in the 2nd post is my best effort at that. I have tried the busybox part of the script, but I don't believe it makes a difference. I will try again, though, and report back.
As far as chown and chgrp goes, I'll add in what I think that should be and post that back later, too.
Fr4gg0r said:
I don't know what you are trying in your second post, but from your first post I would say:
Code:
su
busybox rm -r /data/data/org.adwfreak.launcher/databases/*
busybox rm -r /data/data/org.adwfreak.launcher/files/*
busybox rm -r /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw/prefs.xml /data/data/org.adwfreak.launcher/shared_prefs/
..
kill org.adwfreak.launcher
If you do "chmod 664" on the files, you also have to do "chown & chgrp" or the launcher won't be able to write into the settings xml's/db's.
And /data ist mounted rw, everything else would be senseless.
Click to expand...
Click to collapse
Progress update: Success! More or less.
I realized I wouldn't need to remove the files since the ones I was copying in would just overwrite them anyway, so that cleared up that issue.
I did add chown and chgrp (a piece of information I'm sure I'll find useful in the future) so I'm sure that helped. Making sure to get the group and owner right PER YOUR OWN SETUP was key. When I changed ROMs I had to redo it... so check properties with Root Explorer or whatever.
I revised my script a little to add the background wall paper, too.
The true key, however, was using Lua in SL4A and using the 'sush' script in this post here:
http://code.google.com/p/android-scripting/issues/detail?id=184 (comment #9). That allowed me to run my script in the 'sush' format and do what I wanted.
I also had to add a line to kill the launcher process (android.process.acore) so it would restart itself.
I now have a one-click solution to changing between two ADW desktop configurations/settings!
I've attached my script if anyone would like it. Just get SL4A, the Lua interpreter, and put the pieces together! (Use a custom shortcut on the desktop and not a widget and the desktop setup will be preserved; widgets aren't supported in any method...)

[ROOT][LB] Xperia Z (C6602) running Android 5.0.2 (10.6.A.0.454)

Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again leave this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
I have used King's Root to root my phone. My issue is random reboot whenever an app tires to get root access. And titanium backup is not able to backup (it keeps on saying insufficient storage on 20GB free storage area) or delete any app. Plus, I also get random reboot whenever an app having root access is updated over Play Store. And from random reboot it reboots some times and sometimes it doesn't reboot.
So, if anyone having same issue kindly ping back.
(I will post update after reflashing the ftf)
Replace KingUser app with SuperSU
DrXperience said:
I have used King's Root to root my phone. My issue is random reboot whenever an app tires to get root access. And titanium backup is not able to backup (it keeps on saying insufficient storage on 20GB free storage area) or delete any app. Plus, I also get random reboot whenever an app having root access is updated over Play Store. And from random reboot it reboots some times and sometimes it doesn't reboot.
So, if anyone having same issue kindly ping back.
(I will post update after reflashing the ftf)
Click to expand...
Click to collapse
To deal with random reboot issue, I would suggest you to replace KingUser app with SuperSU as described above.
For TitaniumBackup issue, try this:
Open TitaniumBackup, Go to MENU -- Preferences -- Backup folder location.
You will see Storage provider: (Click to change) and you will see multiple option of storage providers. Select second option DocumentProvider Storage and then click on SD Card option and at the bottom of screen you will see select "SD Card". Click on this option. It is important that you do not select any folder inside SD Card, you only have to select the SD Card option. Now select <<Create a new folder>> and then select USE THE CURRENT FOLDER.
To make it more clear, I have attached the snapshots, please go through snapshots one by one and you will be able to fix insufficient free storage error in TB.
SurenderK said:
To deal with random reboot issue, I would suggest you to replace KingUser app with SuperSU as described above.
For TitaniumBackup issue, try this:
Open TitaniumBackup, Go to MENU -- Preferences -- Backup folder location.
You will see Storage provider: (Click to change) and you will see multiple option of storage providers. Select second option DocumentProvider Storage and then click on SD Card option and at the bottom of screen you will see select "SD Card". Click on this option. It is important that you do not select any folder inside SD Card, you only have to select the SD Card option. Now select <<Create a new folder>> and then select USE THE CURRENT FOLDER.
To make it more clear, I have attached the snapshots, please go through snapshots one by one and you will be able to fix insufficient free storage error in TB.
Click to expand...
Click to collapse
Okay I will give it a shot :highfive:
And you have not provided download link. Provide that in your first post.
Download link sent
DrXperience said:
And you have not provided download link. Provide that in your first post.
Click to expand...
Click to collapse
Hey DrXperience,
Check your PM, I have sent the download link through PM....
Try both links, one should be working
can i have download link plz?
SmunksRiley said:
can i have download link plz?
Click to expand...
Click to collapse
Hey SmunksRiley,
Please check your PM. I have sent the link.
Sent from my C6602 using xda Forums PRO
hi sir
sir can i have a link to i need to replace kings app to avoid random reboot
bagsey said:
sir can i have a link to i need to replace kings app to avoid random reboot
Click to expand...
Click to collapse
Hey, please check your PM. I have sent the download link
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again leave this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
Click to expand...
Click to collapse
The following lines in script gives error
busybox chattr -ia /system/xbin/ku.sud
chattr: stat /system/xbin/ku.sud: No such file or directory
busybox chattr -ia /system/bin/.usr/.ku
chattr: stat /system/bin/.usr/.ku: No such file or directory
busybox chattr -ia /system/usr/iku/isu
chattr: stat /system/bin/usr/iku/isu: No such file or directory
DrXperience said:
The following lines in script gives error
busybox chattr -ia /system/xbin/ku.sud
chattr: stat /system/xbin/ku.sud: No such file or directory
busybox chattr -ia /system/bin/.usr/.ku
chattr: stat /system/bin/.usr/.ku: No such file or directory
busybox chattr -ia /system/usr/iku/isu
chattr: stat /system/bin/usr/iku/isu: No such file or directory
Click to expand...
Click to collapse
Hi,
Ignore the error if it says No such file or directory. Proceed to next commands and once completed reboot your device. You will get SuperSU working and KingUser replaced.
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again leave this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
Click to expand...
Click to collapse
Sadly my phone reboots as soon as I get to the point where I mount /system ("mount -o remount,rw /system" ). Probably caused by RIC, any suggestions on how to avoid this?
cruzersteve said:
Sadly my phone reboots as soon as I get to the point where I mount /system ("mount -o remount,rw /system" ). Probably caused by RIC, any suggestions on how to avoid this?
Click to expand...
Click to collapse
Hi,
Please check this xda thread. Might help you out.
http://forum.xda-developers.com/xpe...b-definitive-root-remount-reboot-fix-t2317432
Sent from my C6602 using xda Forums PRO
Anyone tryed on c6603?
hey surrenderk, i did the mistake of following this tutorial and literally copy pasted everything despite not having a sony, but an infinix hot note, just because i wanted to remove kinguser and kingroot and have superuser as the dedfault application for handling root access. any way to reverse everything we just did, coz i cant update via ota?? shell commands to undo everything perhaps that affected the "system" folder or that affected normal working of device??thanks!!
Jokichu said:
hey surrenderk, i did the mistake of following this tutorial and literally copy pasted everything despite not having a sony, but an infinix hot note, just because i wanted to remove kinguser and kingroot and have superuser as the dedfault application for handling root access. any way to reverse everything we just did, coz i cant update via ota?? shell commands to undo everything perhaps that affected the "system" folder or that affected normal working of device??thanks!!
Click to expand...
Click to collapse
Which device and software are you using??
Are you observing any strange behaviour in your device after making changes?
Sent from my C6602 using xda Forums PRO
Hey surrenderk yep, the problem is that somehow, I can't see any Ota update. It's says it's up to date, while I know there's an upgrade. In the steps we did, did we in any way change anything related to that??
I was already rooted, and had kinguser, and used kingroot. Whenever an Ota update came I could just unroot, perform the update then root again, easy.
However since I followed your tutorial steps with the adb shell, I received an Ota update, and did the unroot as usual, but the system found several files failing the root integrity tests, thus failing to update. My questions are
1.all these rm commands we used, did we remove/delete any core essential android file from the system folder? Bin folder? (debuggered /real/64) kroot_*, iku, kr-stock-conf, icusuflag.conf,
2.what do the rt.sh and install-recovery.sh scripts do?
My phone had become unstable, and could not play videos well nor audio files, it kept stuttering like it's buffering from an online Stream. Anyways, I am now unrooted and did a factory reset which fixed the video/audio glitch but still cannot "see" any new update although it's there. I just want want that update.
Sent from my Infinix-X551 using XDA Free mobile app
Question:
Why is the link not available in the OP?
Why is the link only shared thru PM?
Isn't this XDA - a sharing community?
This thread is just a little too weird.

Categories

Resources