Develop Bugs

[HOWTO] Backup your EFS partition

As with newer Samsung Android phones it is practically essential that if you go to the modding scene and start uploading custom roms you should have a backup of your efs
For simple backup of efs partition
by sishgupta
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
and for a full image of your brand new phone
as various users have stated there are other more correct ways of backing up your new efs partition,
the one i liked the most is this one by because it backs up all your partitions
by c0ns0le
Code:
IF YOU HAVE BUSY BOX INSTALLED
adb shell
su -
for i in $(ls /dev/block/platform/omap/omap_hsmmc.0/by-name/ | grep -v user)
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
NO BUSYBOX:
adb shell
su -
for i in boot cache dgs efs metadata misc param radio recovery sbl system xloader
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
deprecated just staying here because this started all the correct backup commands for your efs
In order to do this for your galaxy nexus you should have adb working on your machine and also debugging enabled in your phone
this is practically easy, your phone must be rooted, or at least booted with the boot.img of this thread How to Root GALAXY NEXUS
Code:
adb root
adb remount
adb pull /factory
and now backup that file to at least 2 places lol
I always get paranoid with this
have fun installing custom roms

i don't think that works for GN
Samsung changed their EFS recently on the new released phones
it's no longer how it was with the Galaxy S line of phones

No one know if we really can backup and restore /factory (EFS)?

this should put an .img file in /sdcard. It's the same method as the one in the sgs2 section but with different paths.
Code:
adb shell
su
cat /dev/block/platform/omap/omap_hsmmc.0/by-name/efs > /sdcard/efs.img
edit: you'll need to be root, obviously
edit again:
this is technically better but does the same thing:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img

Out of curiosity, what is efs?
I am pretty familiar with flashing my HTC Desire, but there is not an efs partition (AFAIK)?
Cheers!

It backs up your imei information in case it gets corrupted by flashing custom roms and mods
Sent from my GT-I9000 using xda premium

420SYN said:
It backs up your imei information in case it gets corrupted by flashing custom roms and mods
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Cool thanks!
Stew

Is this something specific to Samsung phones? I have been rooting and flashing since the nexus one and have never needed this.
Doesn't clockwork mod back this up? If not, why not?
Sent from my LG-P999

dave_t321 said:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
Click to expand...
Click to collapse
Would it be if=/dev/block/platform/omap/omap_hsmmc.0/by-name/factory since this partition is named "factory" now?

If the efs is really in the /factory folder and its not hardlinked files sitting somewhere else is there a better way to save the files and keeping the permissions?
Using tar or gzip on them before?

So which method to follow in order to backup my efs folder?All information is under /factory

use
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
this is the right command as if you run ls on the by-name folder you can see that it is still efs not factory
factory must be a link to this

omg, i have a 0049... IMEI after flashing ICL53F via fastboot!
how could i restore my old IMEI?
edit: jippie, i got my IMEI back after flashing the ITL41F odin version from this post!
i suggest everyone to backup the efs before flashing other firmwares!

Could someone provide the correct commands to restore the efs folder please Ive backed it up just need to know how to restore it if something bad happens

There is a guide for it on these forums. Google 'efs restore android' and you should find it.
There is also an efs restore application that will use img files (like how we made in this guide) instead of just the nv_data.bin
Sent from my Galaxy Nexus using XDA App

does it actually work with this phone?

fun w/ shellfoo
Code:
IF YOU HAVE BUSY BOX INSTALLED
adb shell
su -
for i in $(ls /dev/block/platform/omap/omap_hsmmc.0/by-name/ | grep -v user)
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
NO BUSYBOX:
adb shell
su -
for i in boot cache dgs efs metadata misc param radio recovery sbl system xloader
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done

---------- Post added at 03:43 PM ---------- Previous post was at 03:15 PM ----------
[/COLOR]
dave_t321 said:
this should put an .img file in /sdcard. It's the same method as the one in the sgs2 section but with different paths.
Code:
adb shell
su
cat /dev/block/platform/omap/omap_hsmmc.0/by-name/efs > /sdcard/efs.img
edit: you'll need to be root, obviously
edit again:
this is technically better but does the same thing:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
Click to expand...
Click to collapse
i've foud this one..wich is better?
adb shell
su
busybox dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/data/media/my_efs_backup.img

They are the same with different output locations. The one that leads with busy box is for a configuration where the commands are not aliased for a busy box setup.
Sent from my Galaxy Nexus using XDA App

Similar thing happened to me. I got a 2nd nexus, decided to restore a nandroid from my 1st nexus onto the 2nd one. Restore went fine, it was like a clone of the 1st phone except the IMEI was corrupt with a generic 0049... one. I flashed the phone back to a google factory ITL41D and the IMEI was restored. Needless to say I won't be doing that again!
paratox said:
omg, i have a 0049... IMEI after flashing ICL53F via fastboot!
how could i restore my old IMEI?
edit: jippie, i got my IMEI back after flashing the ITL41F odin version from this post!
i suggest everyone to backup the efs before flashing other firmwares!
Click to expand...
Click to collapse

[ADDON][One X] Generic startup/init.d scripts support for Stock ROM/Kernel

[ info ]
i am attaching a easy to run package which contains the files required for full functionality of executing startup scripts (init.d scripts)...
basically this will allow the user to execute custom shell scripts, placed in /system/etc/init.d/ folder and they will be executed on each boot!
Please note that some custom ROMs/Kernels already have this feature... This addon is ment to be used on STOCK ROM...
[ requirements ]
stock rooted ROM
windows PC with adb drivers installed
[ how to install ]
download the provided zip package
save it on c:\
extract the contents of the package
connect phone with usb debugging active to PC via ADB
execute "runme.bat"
follow onscreen instructions & enjoy!
incase some issue is there post the output/log of script
[ additional info ]
i have added the following things in the package:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.19.3 binary)
correct /system/etc/install-recovery.sh file (this file gets executed by default on stock kernel too!)
test/example script /system/etc/init.d/99test
to check if this is working the test script (99test) will create a temporary file /data/local/tmp/init.d_log_test.txt on each boot
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ download link ]
generic-init.d-support-v01.zip (mirror)
MD5HASH: 4cd2606280524aa96af9d486ce90ea7e
OR
generic-init.d-support-v01.zip
MD5HASH: 2eda273af4b91c34f868807820cceaee
let me know how it goes!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ENJOY!

ok so Paul has posted a working recovery... i will test it out and soon post a package which can be flashed via recovery...

This will be included by default on most custom ROM's wont it?

wilkyyyy said:
This will be included by default on most custom ROM's wont it?
Click to expand...
Click to collapse
i suppose so... thats why i marked the title of this thread as "....support for STOCK ROM..."

DooMLoRD said:
i suppose so... thats why i marked the title of this thread as "....support for STOCK ROM..."
Click to expand...
Click to collapse
Yep i saw, was just checking
Good work btw!
How you finding the one x?

wilkyyyy said:
Yep i saw, was just checking
Good work btw!
How you finding the one x?
Click to expand...
Click to collapse
its great!!!

Thanks DL. Waiting for your DoomKernel

But all we have S-ON with unlock bootloader and we can't change kernel and radio ? Or I'm wrong ?

witek_77 said:
But all we have S-ON with unlock bootloader and we can't change kernel and radio ? Or I'm wrong ?
Click to expand...
Click to collapse
u can flash kernels... i already flashed a bunch of test kernels on my One X
not sure about the radio though...

I don't need anything but change the rom and kernel. Unlocked boot is enough. So why do we need s-off ? We are waiting for final results of your work. I hope that it will be with oc because 4x1,3gHz is not enough You are amazing

Radio's/Baseband's should only be flashed with S-OFF!

Doomlord, glad to know you chose one X over the xperia s.
Not ready to unlock yet btw, will wait first for root exploit w/o unlocking device.
But probably later I'll still unlock it lol.
Sent from my Sony Arc w/ ICS

Is this compatible with Paul's recovery? Because I got error while i flashed it.
Code:
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- remounting system
--- checking
sh: grep: not found
--- pushing files
push: files\system/bin/sysinit -> /data/local/tmp/./bin/sysinit
push: files\system/etc/init.d/99test -> /data/local/tmp/./etc/init.d/99test
push: files\system/etc/install-recovery.sh -> /data/local/tmp/./etc/install-reco
very.sh
push: files\system/xbin/run-parts -> /data/local/tmp/./xbin/run-parts
4 files pushed. 0 files skipped.
1546 KB/s (1116656 bytes in 0.705s)
--- copying to system
sh: cp: not found
mkdir: can't create directory '/system/etc/init.d/': File exists
sh: cp: not found
sh: cp: not found
sh: cp: not found
--- correcting permissions
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/bin/sysinit: No such file or directory
Unable to chmod /system/bin/sysinit: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Unable to chmod /system/etc/init.d/*: No such file or directory
--- checking
/system/etc/install-recovery.sh: No such file or directory
/system/bin/sysinit: No such file or directory
lrwxrwxrwx root root 2012-04-12 08:51 run-parts -> /system/xbin
/busybox
drwxrwxrwx root root 2012-04-12 08:51
ALL DONE!!!

ShyamSasi said:
Is this compatible with Paul's recovery? Because I got error while i flashed it.
Code:
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- remounting system
--- checking
sh: grep: not found
--- pushing files
push: files\system/bin/sysinit -> /data/local/tmp/./bin/sysinit
push: files\system/etc/init.d/99test -> /data/local/tmp/./etc/init.d/99test
push: files\system/etc/install-recovery.sh -> /data/local/tmp/./etc/install-reco
very.sh
push: files\system/xbin/run-parts -> /data/local/tmp/./xbin/run-parts
4 files pushed. 0 files skipped.
1546 KB/s (1116656 bytes in 0.705s)
--- copying to system
sh: cp: not found
mkdir: can't create directory '/system/etc/init.d/': File exists
sh: cp: not found
sh: cp: not found
sh: cp: not found
--- correcting permissions
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/bin/sysinit: No such file or directory
Unable to chmod /system/bin/sysinit: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Unable to chmod /system/etc/init.d/*: No such file or directory
--- checking
/system/etc/install-recovery.sh: No such file or directory
/system/bin/sysinit: No such file or directory
lrwxrwxrwx root root 2012-04-12 08:51 run-parts -> /system/xbin
/busybox
drwxrwxrwx root root 2012-04-12 08:51
ALL DONE!!!
Click to expand...
Click to collapse
its got nothing to do with recovery... ur busybox installation is not correct...
Code:
sh: cp: not found
mkdir: can't create directory '/system/etc/init.d/': File exists
sh: cp: not found
sh: cp: not found
sh: cp: not found
i will create a recovery flashable update.zip later

I tried to flash your Kernel but it failed to acquire root so I had to flash Paul's Recovery. So the Busy Box didn't install under xbin. I used Busybox installer from Play store.

ShyamSasi said:
I tried to flash your Kernel but it failed to acquire root so I had to flash Paul's Recovery. So the Busy Box didn't install under xbin. I used Busybox installer from Play store.
Click to expand...
Click to collapse
try SuperSU (CWM zip)

I tried to Advance Stock Kernel that doesn't have a recovery does it?
OK got it to work, I think your script created xbin so installed BusyBox under xbin then when I ran the batch file it ran successfully. I think you can make the script compatible with both xbin and bin.

ShyamSasi said:
I tried to Advance Stock Kernel that doesn't have a recovery does it?
OK got it to work, I think your script created xbin so installed BusyBox under xbin then when I ran the batch file it ran successfully. I think you can make the script compatible with both xbin and bin.
Click to expand...
Click to collapse
this device is different... unlike our Xperia phones, HTC devices have a dedicated partition for recovery so we dont need to include Recovery in main kernel...

hi sir
general question
please would you develop a mod kernel for call recorder feature as in sony xperia s
hopefully you will help us
thanks in advanced

Busybox Uninstaller v1.0 - Remove busybox & its +600 symlink files [26 Aug 2012]

Busybox Uninstaller v1.0 - Removes busybox and its +600 symlink files
It will backup all files before they are deleted + activity log written to sdcard
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is for Samsung phones only. Other phones need changes in sdcard mount position
Always do a nandroid backup before flashing anything.
Use at your own risk.​
How to use - Flash from recovery method:
Download attached zip file from this post
Copy the file you downloaded to external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the Busy_Box_Uninstaller_v1.0-signed.zip file downloaded above
If you use CWM Recovery, you can put the zip file in internal or external SD
Busybox will be completely removed with its +600 symlink files
Click to expand...
Click to collapse
How to use: run script in terminal:
This part does not apply for the beginners. If you don't understand this shell, use the recovery version attached
You can try the below shell script to run from terminal with root rights.
It just misses one line to remove the busybox main package at end of script. The attached zip will delete the package in updater-script rather than in the script. Either remove the busybox package manually when done or add the rm line at the end of script
Actual features:
This small script will remove busybox from /system/xbin and from /system/bin.
It will search and remove all symlinks installed in the above 2 folders. Those are over 600 files !
It will make a backup for each file before deleting it. Backups are located on the external sdcard.
If backup file fails (sdcard full), it will abort and last file that failed the backup will not be removed. You can just resume the process later when you fixed the free space issue for backup.
Backup in tar.gz format with path in filename for easier restore if needed.
Will not overwrite any files during backup.
Log file written in sdcard backup directory.
Number of files deleted displayed when done.
Click to expand...
Click to collapse
To come: Depending on demand and my time, I think at:
Search for busybox in all phone and sets path to look for symlinks to delete. However, not sure if it is welcome!
Date/Time stamped backup folder. No need to delete a previous backup to proceed with script.
Code cleaning (was a bit hard as android and busybox shell are very restrictive).
Click to expand...
Click to collapse
Below is the shell code base used for those who want to know or give ideas to enhance it. Keep in mind it is busybox shell, very limited compared to Bash...
Code included is to run in terminal and will put backup files to internal sdcard (recovery version will put the backup on external sd)
I could include another shell, but would make the zip file bigger in size
Also, did not rely on android built in shell (/bin/sh) to avoid variations depending on shell version with devices / kernels
Code:
#!/bin/sh
bkdir="/sdcard/bb-uninstall" ;
if [ -d "$bkdir" ] ;
then
busybox echo "Backup folder $bkdir already exists. Please remove it to proceed...">>$bkdir/__Error_Backup_Folder_Already_Exists__.txt ;
busybox echo "Backup folder \"$bkdir\" already exists. Please remove it to proceed..." ;
exit 1 ;
else
busybox mkdir $bkdir ;
if [ ! -d "$bkdir" ] ;
then
busybox echo "Backup folder \"$bkdir\" could not be created" ;
busybox echo "Check if sdcard is present, mounted, has free space or you have permissions!!" ;
exit 1 ;
fi ;
fi ;
bbdir="/system/xbin /system/bin" ;
ndeletes=0 ;
for bbpath in $bbdir ;
do
for f in $(busybox find $bbpath -type l) ;
do
gnr=$(busybox readlink $f) ;
if echo "$gnr" |busybox grep -q busybox ;
then
busybox echo -e "$f \t is linked to \t $gnr ---> backup up in sdcard then deleted">>$bkdir/bb-uninstall.log ;
bkfile=`busybox echo "$f" | busybox tr '/' '.'` ;
bkfile=bak$bkfile ;
busybox tar zcf $bkdir/$bkfile.tar.gz -C / ${f:1} ;
if [ ! -f "$bkdir/$bkfile.tar.gz" ] ;
then
busybox echo "Error while creating backup file \"$bkdir/$bkfile.tar.gz\"" ;
busybox echo "File \"$f\" was not deleted" ;
busybox echo "Check free space on \"$bkdir\" or if you have needed permissions" ;
busybox echo "Uninstall will stop. Launch it again after fixing write issue to \"$bkdir\"" ;
exit 1 ;
fi ;
busybox echo "$f linking to $gnr backed-up. Now deleting" ;
busybox rm $f ;
ndeletes=`busybox expr $ndeletes + 1` ;
else busybox echo "$f is not linked to busybox, but to $gnr ---> file not deleted">>$bkdir/bb-uninstall.log ;
fi ;
done
done
echo >>$bkdir/bb-uninstall.log ;
echo "=========================================">>$bkdir/bb-uninstall.log ;
echo " Busybox Uninstaller v1.0 Completed !! ">>$bkdir/bb-uninstall.log ;
echo "=========================================">>$bkdir/bb-uninstall.log ;
echo " - Details - ">>$bkdir/bb-uninstall.log ;
echo "Number of deleted files: $ndeletes">>$bkdir/bb-uninstall.log ;
echo "Busybox cleaned folders: \"$bbdir\"">>$bkdir/bb-uninstall.log ;
echo "Backup folder: \"$bkdir\"">>$bkdir/bb-uninstall.log ;
echo "Log file: \"$bkdir/bb-uninstall.log\"">>$bkdir/bb-uninstall.log ;
echo >>$bkdir/bb-uninstall.log ;
echo "=========================================">>$bkdir/bb-uninstall.log ;
echo "Brought to you by [email protected]">>$bkdir/bb-uninstall.log ;
echo "=========================================">>$bkdir/bb-uninstall.log ;
echo ;
echo "=========================================" ;
echo " Busybox Uninstaller v1.0 Completed !! " ;
echo "=========================================" ;
echo " - Details - " ;
echo "Number of deleted files: $ndeletes" ;
echo "Busybox cleaned folders: \"$bbdir\"" ;
echo "Backup folder: \"$bkdir\"" ;
echo "Log file: \"$bkdir/bb-uninstall.log\"" ;
echo ;
echo "=========================================" ;
echo "Brought to you by [email protected]" ;
echo "=========================================" ;

FAQ / Updates
To be completed

Done
Any feedback and ideas about the code is welcome

Thank you so much for ur work! Sorry I'm out of thnx today! will surely thank u 2morrow!
Been looking for this a long time!:victory:

The-Droidster said:
Thank you so much for ur work! Sorry I'm out of thnx today! will surely thank u 2morrow!
Been looking for this a long time!:victory:
Click to expand...
Click to collapse
Please give feedback here after you try it

Updated instructions for the beginners

Tried, everything ok. Thanks
Sent from my GT-I9100

But why ?
I m sorry to question you on this, but why would one want to remove busybox ? given that there are 600+ symlinks .. but what is the benefit / effects of removing it or NOT removing it ?
Knowing this would educate people as to why people people should do this... its a solid noob question which should be added to the OP FAQ/ description if you ask me ... no offense

nayak.aj said:
I m sorry to question you on this, but why would one want to remove busybox ? given that there are 600+ symlinks .. but what is the benefit / effects of removing it or NOT removing it ?
Knowing this would educate people as to why people people should do this... its a solid noob question which should be added to the OP FAQ/ description if you ask me ... no offense
Click to expand...
Click to collapse
When you install busybox in a folder, it creates about 328 symlinks in install folder (xbin often). Most cwm roms add to this a symlink for all commands to the bin folder.
Now, each busybox version comes with its active applets. You can end up with shortcuts installed by a previous version but that are not supported by the actual version.
At worst, some apps can have unpredictable behaviour. If link is removed, app will just end with a not found (also causing impredictable behaviour) . Actually, i never had any of these supposed issues, but why keep non working shortcuts in your system path?
This script is for people that tested so many web installers and busybox versions mainly. Flashing a full ROM in odin will clean it too.
Personally, when I change busybox version, i would use it to clean previous install. Why uninstall a program and leave hundreds of files?
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
When you install busybox in a folder, it creates about 328 symlinks in install folder (xbin often). Most cwm roms add to this a symlink for all commands to the bin folder.
Now, each busybox version comes with its active applets. You can end up with shortcuts installed by a previous version but that are not supported by the actual version.
At worst, some apps can have unpredictable behaviour. If link is removed, app will just end with a not found (also causing impredictable behaviour) . Actually, i never had any of these supposed issues, but why keep non working shortcuts in your system path?
This script is for people that tested so many web installers and busybox versions mainly. Flashing a full ROM in odin will clean it too.
Personally, when I change busybox version, i would use it to clean previous install. Why uninstall a program and leave hundreds of files?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
So to resume, this script exists just because it can be done and because someone, somewhere, somehow may someday need it.

perfect example you install a Rom it comes with all applets installed you check the busybox version and its old so you wish to remove all applets then install new busybox.
Sent from my GT-I9100 using Tapatalk 2

When I uninstall an app, I hate when it leaves folders and files around
And busybox around installers can leave up to +600 of such files in just 2 folders, and you can install elsewhere too
Now, a clean approach is to install busybox in a custom folder and add it to path. No trash over the system. However, some apps look for it selectively in system folders and not in path

nayak.aj said:
I m sorry to question you on this, but why would one want to remove busybox ? given that there are 600+ symlinks .. but what is the benefit / effects of removing it or NOT removing it ?
Knowing this would educate people as to why people people should do this... its a solid noob question which should be added to the OP FAQ/ description if you ask me ... no offense
Click to expand...
Click to collapse
Why would anyone want to leave 600 files on their phone if they dont need them?
karendar said:
So to resume, this script exists just because it can be done and because someone, somewhere, somehow may someday need it.
Click to expand...
Click to collapse
Plenty of people in plenty of places with issues arising from installing busybox from market many a day will need it
Sent from my GT-N7000 using xda app-developers app

This will come handy in the future. Thanks for this!

Hey congrats on your work.I have a problem if you can provide help:i flashed the uninstaller via stock recovery but after phone reboot wifi couldn't obtain ip adress.
Any help?

Invalid_GR said:
Hey congrats on your work.I have a problem if you can provide help:i flashed the uninstaller via stock recovery but after phone reboot wifi couldn't obtain ip adress.
Any help?
Click to expand...
Click to collapse
Can you attach the file here
Code:
/sdcard/bb-uninstall/bb-uninstall.log
Also, under that folder you have a backup of each deleted file, so keep it so you can restore if needed
Sounds like some files in system/bin were removed wrongly, but I doubt my script would do it as I tested it fully and I even include the specific temporary busybox needed for the script
Post the log file so I can see

Phil3759 said:
Can you attach the file here
Code:
/sdcard/bb-uninstall/bb-uninstall.log
Also, under that folder you have a backup of each deleted file, so keep it so you can restore if needed
Sounds like some files in system/bin were removed wrongly, but I doubt my script would do it as I tested it fully and I even include the specific temporary busybox needed for the script
Post the log file so I can see
Click to expand...
Click to collapse
First of all thanx for the quick responce.Here is the file you asked :
https://dl.dropbox.com/u/98804712/bb-uninstall.log
(sorry xda didn't allow me to upload a log file so dropbox it is)

Invalid_GR said:
First of all thanx for the quick responce.Here is the file you asked :
https://dl.dropbox.com/u/98804712/bb-uninstall.log
(sorry xda didn't allow me to upload a log file so dropbox it is)
Click to expand...
Click to collapse
Problem seems in your system toolbox symlinks hijacked by a bad busybox installer
Code:
/system/bin/cat is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/chmod is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/chown is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/date is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/dd is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/df is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/dmesg is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/hd is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/id is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/ifconfig is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/insmod is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/ionice is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/kill is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/ln is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/ls is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/lsmod is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/mkdir is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/mount is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/mv is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/netstat is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/printenv is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/ps is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/renice is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/rm is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/rmdir is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/rmmod is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/route is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/sleep is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/sync is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/top is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/touch is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/umount is linked to /system/bin/busybox ---> backup up in sdcard then deleted
/system/bin/uptime is linked to /system/bin/busybox ---> backup up in sdcard then deleted
All these entries should have been kept linked to toolbox instead of busybox. But, probbaly some third party busybox installer (market installers, a ROM you installed...) linked them to busybox without resetting toolbox links
So, as they are linked to busybox, they got deleted and you end up with a corrupted toolbox installation
Try this below script:
Code:
#!/system/bin/sh
toolbox ln -s /system/bin/toolbox /system/bin/cat
toolbox ln -s /system/bin/toolbox /system/bin/chmod
toolbox ln -s /system/bin/toolbox /system/bin/chown
toolbox ln -s /system/bin/toolbox /system/bin/date
toolbox ln -s /system/bin/toolbox /system/bin/dd
toolbox ln -s /system/bin/toolbox /system/bin/df
toolbox ln -s /system/bin/toolbox /system/bin/dmesg
toolbox ln -s /system/bin/toolbox /system/bin/hd
toolbox ln -s /system/bin/toolbox /system/bin/id
toolbox ln -s /system/bin/toolbox /system/bin/ifconfig
toolbox ln -s /system/bin/toolbox /system/bin/insmod
toolbox ln -s /system/bin/toolbox /system/bin/ionice
toolbox ln -s /system/bin/toolbox /system/bin/kill
toolbox ln -s /system/bin/toolbox /system/bin/ln
toolbox ln -s /system/bin/toolbox /system/bin/ls
toolbox ln -s /system/bin/toolbox /system/bin/lsmod
toolbox ln -s /system/bin/toolbox /system/bin/mkdir
toolbox ln -s /system/bin/toolbox /system/bin/mount
toolbox ln -s /system/bin/toolbox /system/bin/mv
toolbox ln -s /system/bin/toolbox /system/bin/netstat
toolbox ln -s /system/bin/toolbox /system/bin/printenv
toolbox ln -s /system/bin/toolbox /system/bin/ps
toolbox ln -s /system/bin/toolbox /system/bin/renice
toolbox ln -s /system/bin/toolbox /system/bin/rm
toolbox ln -s /system/bin/toolbox /system/bin/rmdir
toolbox ln -s /system/bin/toolbox /system/bin/rmmod
toolbox ln -s /system/bin/toolbox /system/bin/route
toolbox ln -s /system/bin/toolbox /system/bin/sleep
toolbox ln -s /system/bin/toolbox /system/bin/sync
toolbox ln -s /system/bin/toolbox /system/bin/top
toolbox ln -s /system/bin/toolbox /system/bin/touch
toolbox ln -s /system/bin/toolbox /system/bin/umount
toolbox ln -s /system/bin/toolbox /system/bin/uptime
Copy paste it in a sh file using notepad++ with EOL Conversion set to unix format and run it in a su terminal
If complicated for you, use attached file:
- download toolbox_fix.txt
- rename it to toolbox_fix.sh (do not open it or edit it in windows notepad or it will be corrupted)
- put it in /system/bin in your phone using a program like root explorer (you have to mount /system as rw in root explorer)
- in root explorer, long press the file name and select to change permissions, check all boxes there
- save settings
- open terminal and type:
Code:
su
sh /system/bin/toolbox_fix.sh
Now, reboot and all should be fine
If not, in terminal type:
Code:
su
ls -l /system/bin >/sdcard/ls_log.txt
And attach here the ls_log file you will find in root of your sdcard
Please report back if this fixed your issue. If it is the case (which I am quiet sure), I will edit my uninstaller script to automatically make these symlinks for people in situations like you

Once again thanx for your help.Yeah i used a market bustbox installer..Before i try anything could you please make clear what exactly i must do in the last step when you say "open terminal" sorry if it's noob level question..

Invalid_GR said:
Once again thanx for your help.Yeah i used a market bustbox installer..Before i try anything could you please make clear what exactly i must do in the last step when you say "open terminal" sorry if it's noob level question..
Click to expand...
Click to collapse
Download this application from market and install it:
https://play.google.com/store/apps/details?id=jackpal.androidterm
Then, open it (it is the terminal)
Then, you type the 2 commands line in code I told you
Do not forget to mount /system as rw in root explorer and set file permissions like described above

[Root] How to root z1s and get it to stick on reboot.

Z1s Root+Reovery+Deodex Android 4.3 Updated 6/18/14​
This was put together by @ayuready1989 and @Tactic13
This Not A Rom "Do NOT WIPE ANYTHING JUST FLASH AS IS"
This is a Patch to keep root on reboot as well as deodex your current rom.[
NO LONGER USED
Please use Root 4.4.4 on z1s
Once you have recovery you can flash this instead of using the script it does not require you to make the script.
First of all we would like to thank @jcase for getting the initial root, @[NUT] for the recovery @xsacha for the ta backup and @RyokoN for some of the tools, if we forgot someone just send us a message.
Okay now for the fun part.​
Make sure that you have usb debugging enabled.
Root with jcase method.
Install SuperSU from market reboot.
Run adb shell su -c "/system/xbin/kill_ric.sh"
Then adb shell su -c "mount -o remount,rw /system"
Install Recovery But use the one for the z1 Locked boatloader.
Finaly Flash Deodex + Root Devhost Minor
Optional
Backup Ta image. Ta Backup
We will keep working on this as well as start working on a rom just wanted to get this out to you guys.
You assume all the stand disclaimers when you flash this that not is to say that we wont help you.

Mine Just in case i need it.

Tactic13 said:
Mine Just in case i need it.
Click to expand...
Click to collapse
+1

This is what i get when trying to install recovery. Supersu working fine. I just used it for TB. Should I try SuperUser instead?
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices =
= =
==============================================
[ 1. Installation on ROM rooted with SuperSU ]
[ 2. Installation on ROM rooted with SuperUser ]
[ 3. Installation on unrooted ROM ]
[ 4. Exit ]
Please choose install action. [1,2,3,4]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found
=============================================
Step2 : Sending the recovery files.
=============================================
9 KB/s (29 bytes in 0.003s)
3847 KB/s (15759 bytes in 0.004s)
244 KB/s (501 bytes in 0.002s)
2880 KB/s (11798 bytes in 0.004s)
5030 KB/s (56662 bytes in 0.011s)
1504 KB/s (3082 bytes in 0.002s)
187 KB/s (385 bytes in 0.002s)
5489 KB/s (657704 bytes in 0.117s)
5318 KB/s (2875482 bytes in 0.528s)
5240 KB/s (2581087 bytes in 0.481s)
5347 KB/s (1845510 bytes in 0.337s)
384 KB/s (8658 bytes in 0.022s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Apr 30 05:38 /data/local/tmp/recovery/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.7.123 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
mount: permission denied (are you root?)
blockdev: applet not found
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Copy mr wrapper script to system.
cp: can't create '/system/bin/mr': File exists
chmod: /system/bin/mr: Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': File exists
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: Read-only file system
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries
=============================================
Press any key to continue . . .

Re run the root as well as the second set of commands and on your phone it should ask you to grant root access to adb. But i installed SuperSu and used option 1.

same here, supersu and option 1,but make sure /sbin/xbin/kill_ric.sh is ran before u install recovery a couple times(2-3) just to make sure.
this is the specific one i used, for winblows V4
http://forum.xda-developers.com/showthread.php?t=2426739

So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.

themacman1000 said:
So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.
Click to expand...
Click to collapse
cool. if asked to fix root after cwm flash it seems safe to always chose to fix it

ayuready1989 said:
strange, the zip doesnt touch /system/xbin/su .. try the su fix that cwm asks for when trying to reboot after flashing a zip . ive selected yes and no, still the same result. still had root.. but flash via cwm and apply the fix root fix it asks, dont disable flash recovery though
Click to expand...
Click to collapse
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself

themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed?
Click to expand...
Click to collapse
alrighty, nice to know it works, thanks for actually giving feedback @themacman1000 now time for the modules and tweaks

themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself
Click to expand...
Click to collapse
I installed this apk.
http://dl-count.xposed.info/modules/de.robv.android.xposed.installer_v32_de4f0d.apk
Sent from my iPad using Tapatalk

I'm curious if Z1 roms would work for the Z1s... Considering they're basically the same phone... I did a full backup on mine, now considering trying that out...

I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.

It's good to see T-Mobile roms,when you're overseas you can use WiFi Calling to call back to the US free.:thumbup::thumbup:
Sent from my HTC One_M8 using Tapatalk 2

Well you have the start right here it deodex the rom and root sticks

Tactic13 said:
I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.
Click to expand...
Click to collapse
I was actually thinking 4.3 roms... I figured 4.4 wouldn't work, but 4.3 maybe?

adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help

jahjah440 said:
adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help
Click to expand...
Click to collapse
There's supposed to be a space between chmod and 755.

Elysian893 said:
There's supposed to be a space between chmod and 755.
Click to expand...
Click to collapse
Thank you I actually got it working before I had forgotten to give elevated permission to write to /data
I have achieved root!

what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
LaosPerson said:
what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
Click to expand...
Click to collapse
nevermind, i just had to read the z2 link thing

[Root] [Script] OTA Killer for LG K7 m1 and other devices

Disclaimer: I nor XDA nor anyone else is responsible for your lack of reading or comprehension skills, ignorance on your part or anyone else's nor just plain stupidity on your part or anyone else's, so if you don't know what you're doing and or don't know how to fix any bad things that could happen then just don't do it.
Root and Busybox required.
This is a more permanent solution to stop OTA updates from downloading on your rooted device that is designed to survive when you wipe /cache. I'm including the script which will work on any device that downloads it's OTA updates as update.zip to /cache without modification and a flashable zip, the flashable zip is for the LG K7 m1 Metro PCS variant rooted with Magisk ONLY (unless modified) and was fully tested, you're free to edit the script and or the updater-script in the flashable zip for your device (be sure you get the /system partition for your device right, the init process right if not rooted with Magisk and the proper location and file name for your OTA updates) and you may release it for others to use if you like but please give appropriate credit. The script can simply be dropped in your appropriate init folder (/data/adb/service.d/ for Magisk) and set chmod 0700 before rebooting your device.
Alternately you can use MacroDroid to run the script at boot.
Trigger > Device Events > Device Boot
Action > Applications > Shell Script (Paste script on line)
The rest should be self-explanatory.
Thanks to QuickNET Tech for coming up with this method. You can and should read about it HERE and follow up with part 3 from their post so you don't get the annoying notifications. Instructions for reversing this modification are also in that thread, in addition to those instructions you'll also need to delete the 22otakiller script from your init directory (default is /data/adb/service.d/).
QuickNET Tech said:
-Part 3. [Optional]
The annoying update notifications are actually Google Play Services fault. All you have to do is go to "Settings > Apps" and find Google play services and disable the apps ability to show you notifications.
Click to expand...
Click to collapse
What this script does:
The script (see bottom of this post) when ran either automatically on boot or manually will check for update.zip in /cache, if it exist but wasn't created by the script or using the same method with the appropriate attribute applied then it will delete it (regardless of size including an authentic update.zip file) and create the appropriate 0 byte update.zip file with the appropriate attribute and permissions, if it doesn't exist it will create the appropriate file with the appropriate attribute and permissions. It creates a 0 byte update.zip that can not be modified or deleted by anyone including the super user without removing the file attribute which can only be removed by the super user. The flashable zip for the LG K7 rooted with Magisk ONLY (unless edited for your device and or root method) will install the script to /data/adb/service.d/ and set it's permissions to 0700.
Please let me know and post your device information if the updater-script in the flashable zip works as-is with your device.
Enjoy!
Script (22otakiller):
Code:
#!/system/bin/sh
uzip="/cache/update.zip"
if [ -f "$uzip" ] && lsattr "$uzip" | cut -c 6 | fgrep -q 'i'
then
exit
elif [ -f "$uzip" ]
then
rm -f $uzip
touch $uzip
chmod 7400 $uzip
chattr +i $uzip
exit
else
touch $uzip
chmod 7400 $uzip
chattr +i $uzip
exit
fi

Been a long time since I've been on this site seeing as most every device after the K7 hasn't had any development. Glad to see people are still messing with this device. Good work man!