Using this
I let it run twice, and now it works great... weird.
running 2.3.4/4.5.621?
sd_shadow said:
running 2.3.4/4.5.621?
Click to expand...
Click to collapse
Seriously need root back on my phone. Is this build 4.5.621 on android 2.3.4?????
I had to get warranty replacement, and replacement is upgraded!!!!!!
Please let me know.
Sent from my DROID2 using Tapatalk 2
I tried the same thing you said you did and got nothing. which build version are you on? im on this god forsaken .622 on the r2d2 and nothing will work for root. if anyone has heard any news about accomplishing it please let me know
I Tried it a bunch of times on .621 and could not obtain root.
Data:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
$ su
su: permission denied
$ /system/xbin/su
/system/xbin/su: not found
$ mount -o remount,rw /dev/block/mtdblock3 /system
if [ -e /data/local/12m.bak ];
mount: Operation not permitted
$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
exit
$ exit
(success)
> mv /data/local/12m /data/local/12m.bak
(success)
> ln -s /data /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
> exit
> exit
$ su
mount -o remount,rw /dev/block/mtdblock3 /system
su: permission denied
$ /system/xbin/su
/system/xbin/su: not found
$ mount -o remount,rw /dev/block/mtdblock3 /system
if [ -e /data/local/12m ];
mount: Operation not permitted
$ if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
exit
$ exit
(success)
> mv /data/local/12m.bak /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
> exit
> exit
su
/system/xbin/su
$ su
su: permission denied
$ /system/xbin/su
/system/xbin/su: not found
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
$ exit
(success)
> mv /data/local.prop /data/local.prop.bak
> echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
> echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
$ mv /data/local.prop /data/local.prop.bak
failed on '/data/local.prop' - Permission denied
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
$ echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ exit
(success)
Yeh that's about all anyone is going to get until a dev figures out the sbf now that it has finally been leaked
*alarmed sputter* from R2D2
I really don't know how it happened. Like, at all. But... it works now '
Sent from my DROID2 using xda premium
i doubt it
i doubt you got root on .621/.622
I had it working until the data wipe I did today. Will report back with this attempt here.
No updates available, managed to get wifi tether for root users and ultimate backup to work properly. Trust me, I had it.
It looks like something about having it already rooted originally may help me here. Weird...
Here, have some video proof:
http://www.youtube.com/watch?v=5iwcwoa6Vx0
possible
Before i mistakenly downgraded i did have root on the update. But if you wipe completly then you will lose root forever (untill root is found)
When I first got the update, I had my SU and such icons, but it wasn't actually rooted. Ran the script, it's rooted now... weirdness, man.
I hope someone figures this out soon this phone sucks as totally stock.
That's what mine was!
Also, I did a /data wipe, no problems.
Sent from my DROID2 using xda premium
mewshi said:
That's what mine was!
Also, I did a /data wipe, no problems.
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Were you on .629?? Cause i need help with .629
seb559e said:
Were you on .629?? Cause i need help with .629
Click to expand...
Click to collapse
Would you mind paying a modicum of attention? Good lord, this isn't even the D2G forum.
Related
I lost root from 2.3.3 to 2.3.4 after automatic OTA download . I downloaded update 4.7.3.eb.US
PreUpdate Info : 4.6.8.XT610.Verizon.en.US
Baseband : N_01.81.00R'
I rooted using Super One Click 2.3.3 , i tried rooting using Motorola 1-click root,Droid 3 easy root script and PetesMotorola Root Tool but failed .
Here is the log from Motorola root tool/
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
su
/system/xbin/su
mount -o remount,rw /dev/block/mtdblock3 /system
if [ -e /data/local/12m.bak ];
$ su
then
rm /data/local/12m.bak
fi
exit
exit
exit
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local/12m /data/local/12m.bak
(success)
> ln -s /data /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
> exit
> exit
$ su
if [ -e /data/local/12m ];
then
rm /data/local/12m
fi
exit
$ /system/xbin/su
exit
exit
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local/12m ];
> then
> rm /data/local/12m
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local/12m.bak /data/local/12m
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
> exit
> exit
su
/system/xbin/su
mount -o remount,rw /dev/block/mtdblock3 /system
$ su
if [ -e /data/local.prop.bak ];
then
rm /data/local.prop.bak
fi
exit
$ /system/xbin/su
exit
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /data/local.prop.bak ];
> then
> rm /data/local.prop.bak
> fi
$ exit
$ exit
$ exit
(success)
> mv /data/local.prop /data/local.prop.bak
> echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
> echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
> echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
> echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
$ mv /data/local.prop /data/local.prop.bak
failed on '/data/local.prop' - Permission denied
$ echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
cannot create /data/local.prop: permission denied
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /system/bin/su ];
> then
> rm /system/bin/su
> fi
> exit
> exit
su
/system/xbin/su
mount -o remount,rw /dev/block/mtdblock3 /system
if [ -e /system/bin/su ];
$ su
then
rm /system/bin/su
fi
exit
exit
$ /system/xbin/su
exit
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /system/bin/su ];
> then
> rm /system/bin/su
> fi
$ exit
$ exit
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /system/sbin/su ];
> then
> rm /system/sbin/su
> fi
> exit
> exit
$ su
if [ -e /system/sbin/su ];
then
rm /system/sbin/su
fi
exit
$ /system/xbin/su
exit
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ if [ -e /system/sbin/su ];
> then
> rm /system/sbin/su
> fi
$ exit
$ exit
$ exit
(success)
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> exit
> exit
su
/system/xbin/su
mount -o remount,rw /dev/block/mtdblock3 /system
$ su
exit
exit
$ /system/xbin/su
$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
$ exit
$ exit
$ exit
(success)
same problem here...
...have you found any workarounds?
So now that there's 3 premium super user apps I figured I'd ask what's the proper way to uninstall and install a new one if I wanted to I also figured this would help noobs. The way I would do it is go into file explorer mount my system to R/O and delete the system in system app . then I would flash a new super user through recovery or adb. Now in not sure if anything would be lingering around that would come in conflict with a new SU so hopefully someone can help answer this. Thanks
Sent from my Nexus 4 using Tapatalk 2
Surely the new ZIP package removes/replaces the old one with the new package (assuming they are the same name, of course)?
EddyOS said:
Surely the new ZIP package removes/replaces the old one with the new package (assuming they are the same name, of course)?
Click to expand...
Click to collapse
Well I guess what I mean is going from SuperSu to clockworkmod su
Sent from my Nexus 4 using Tapatalk 2
The ZIP package remove any old versions before flashing the new one so you just flash the package in CWM/TWRP and you should be good to go...
Code:
#!/sbin/sh
# arg 1 is recovery api version, generally 3.
# arg 2 is the pipe fd, to the recovery binary.
# communicate with it using the recovery api.
# arg 3 is the zip file
echo -n -e 'ui_print Installing Superuser...\n' > /proc/self/fd/$2
echo -n -e 'ui_print\n' > /proc/self/fd/$2
cd /tmp
mkdir superuser
cd superuser
unzip -o $3
X86=$(uname -a | grep x86)
if [ ! -z "$X86" ]
then
PLATFORM=x86
else
PLATFORM=armeabi
fi
echo -n -e 'ui_print Installing '$PLATFORM' binaries...\n' > /proc/self/fd/$2
echo -n -e 'ui_print\n' > /proc/self/fd/$2
mount /system
rm -f /system/bin/su
rm -f /system/xbin/su
rm -f /system/app/Superuser.apk
cp $PLATFORM/su /system/bin/su
chown 0:0 /system/bin/su
chmod 6755 /system/bin/su
ln -sf ../bin/su /system/xbin/su
cp Superuser.apk /system/app
umount /system
hi,
By mistake I flash a i9500 recovery on a 9505 and it installed (see picture) and erased my EFS.
I flash a stock with spit, then replaced the EFS (which I had saved on the PC), but each reboot EFS disappears! and the image returns.
Each solution??? I do not know what to do
Alan-B said:
hi,
By mistake I flash a i9500 recovery on a 9505 and it installed (see picture) and erased my EFS.
I flash a stock with spit, then replaced the EFS (which I had saved on the PC), but each reboot EFS disappears! and the image returns.
Each solution??? I do not know what to do
Click to expand...
Click to collapse
you must be rooted, type the following commands in terminal emulator:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
samersh72 said:
you must be rooted, type the following commands in terminal emulator:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
Click to expand...
Click to collapse
Hi,
Thanks
I'll test
But t'is Flash had to add items to the root? but what to delete?
Alan-B said:
Hi,
Thanks
I'll test
But t'is Flash had to add items to the root? but what to delete?
Click to expand...
Click to collapse
rm >> will remove old "keystr" file (if existed, responsible of power menu and lockscreen) and old "factorymode" (responsible of this yellow window)
echo >> will make new two mentioned files with a "on" in it
chown >> will change file owner and group information of these two files to the right one.
chmod 744 >> will set the right permission for the two files rwxr--r--
reboot :good:
you can also use "adb shell" to execute those commands.
samersh72 said:
rm >> will remove old "keystr" file (if existed, responsible of power menu and lockscreen) and old "factorymode" (responsible of this yellow window)
echo >> will make new two mentioned files with a "on" in it
chown >> will change file owner and group information of these two files to the right one.
chmod 744 >> will set the right permission for the two files rwxr--r--
reboot :good:
you can also use "adb shell" to execute those commands.
Click to expand...
Click to collapse
Sorry but the command does not pass error file read-only '
How to use ADB Shell? never used!
NB:
I do not understand why if I replace the EFS it fades to reboot?
And delete any file to remove this yellow page (which directory and file?)
Sorry but this is not easy!
Alan-B said:
Sorry but the command does not pass error file read-only '
How to use ADB Shell? never used!
NB:
I do not understand why if I replace the EFS it fades to reboot?
And delete any file to remove this yellow page (which directory and file?)
Sorry but this is not easy!
Click to expand...
Click to collapse
be sure you have busybox installed
hmmm you need to mount efs folder as write
with root explorer (enable mount in its setting) long press on efs folder and choose permission and tell me what is the permission and if you can set it to: owner: rwx group: rwx others: r-x
samersh72 said:
be sure you have busybox installed
hmmm you need to mount efs folder as write
with root explorer (enable mount in its setting) long press on efs folder and choose permission and tell me what is the permission and if you can set it to: owner: rwx group: rwx others: r-x
Click to expand...
Click to collapse
Ok is solved...
Re Hi,
My EFS is a copy pasted on the PC, is there a solution for the flash via a zip? in a command line?
Or create a tar. To restore
please help me
please help me[/QUOTE]
i have the same , yellow screen , and NO power menu
what too do ?
su
rm /efs/FactoryApp/keystr (NOT FOUND)
rm /efs/FactoryApp/factorymode (NOT FOUND)
echo -n ON >> /efs/FactoryApp/keystr (No Such File Or Directory)
echo -n ON >> /efs/FactoryApp/factorymode (No Such File Or Directory)
chown 1000.1000 /efs/FactoryApp/keystr (NOT FOUND)
chown 1000.1000 /efs/FactoryApp/factorymode (NOT FOUND)
chmod 0744 /efs/FactoryApp/keystr (NOT FOUND)
chmod 0744 /efs/FactoryApp/factorymode (No Such File Or Directory)
reboot
Please Help me ??
-=Ghostface=- said:
please help me
i have the same , yellow screen , and NO power menu
what too do ?
su
rm /efs/FactoryApp/keystr (NOT FOUND)
rm /efs/FactoryApp/factorymode (NOT FOUND)
echo -n ON >> /efs/FactoryApp/keystr (No Such File Or Directory)
echo -n ON >> /efs/FactoryApp/factorymode (No Such File Or Directory)
chown 1000.1000 /efs/FactoryApp/keystr (NOT FOUND)
chown 1000.1000 /efs/FactoryApp/factorymode (NOT FOUND)
chmod 744 /efs/FactoryApp/keystr (NOT FOUND)
chmod 744 /efs/FactoryApp/factorymode (No Such File Or Directory)
reboot
Please Help me ??
Click to expand...
Click to collapse
if you have the I9505 variant, do this with terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
for I9500:
Code:
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
then do the previous posted line commands
What about s3 code?
samersh72 said:
if you have the I9505 variant, do this with terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
for I9500:
Code:
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
then do the previous posted line commands
Click to expand...
Click to collapse
same problem i am having,, what is code for s3 I9300 ?
Please help me..
m.htc said:
same problem i am having,, what is code for s3 I9300 ?
Please help me..
Click to expand...
Click to collapse
for S3 I9300 efs is in block 3 (like I9500)
Can't open error
samersh72 said:
for S3 I9300 efs is in block 3 (like I9500)
Click to expand...
Click to collapse
can't open '/dev/block/mmcb1k0p3' : no such file or directory error..
What to do ?
m.htc said:
can't open '/dev/block/mmcb1k0p3' : no such file or directory error..
What to do ?
Click to expand...
Click to collapse
It is not b1k but blk (l like lemon)
Sent from my Galaxy Nexus using xda premium
ya did same later
samersh72 said:
It is not b1k but blk (l like lemon)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
still error,, see attached image...
m.htc said:
still error,, see attached image...
Click to expand...
Click to collapse
see here, it may help http://forum.gsmhosting.com/vbb/f777/how-fix-samsung-gt-i9300-yellow-text-overlay-factory-mode-1660813/
How to fix this factory mode problem.
please see the attached image & help me.
Mobile model - Samsung Galaxy S4 I9505
sumonfd said:
How to fix this factory mode problem.
please see the attached image & help me.
Mobile model - Samsung Galaxy S4 I9505
Click to expand...
Click to collapse
in terminal emulator, tyoe
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
with search button you could find the answer...
samersh72 said:
in terminal emulator, tyoe
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
with search button you could find the answer...
Click to expand...
Click to collapse
I tried with that but not working. Please help me.
sumonfd said:
I tried with that but not working. Please help me.
Click to expand...
Click to collapse
what it gave you? i think you need to mount the partition before:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
samersh72 said:
what it gave you? i think you need to mount the partition before:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
Click to expand...
Click to collapse
Showing mke2fs not found after giving the below command
mke2fs /dev/block/mmcblk0p10
sumonfd said:
Showing mke2fs not found after giving the below command
mke2fs /dev/block/mmcblk0p10
Click to expand...
Click to collapse
P.S. you must be rooted
samersh72 said:
P.S. you must be rooted
Click to expand...
Click to collapse
my phone is already rooted & also installed root browser MORE OVER IT'S IMEI CORRUPTED & DON'T HAVE WARRANTY.
i Have z3x box & NS pro. please guide me.
Open "Root Explorer" App
efs/FactoryApp/
Open "factorymode" file with text editor
Change OFF to ON
Reboot
Mr.W0lf said:
Open "Root Explorer" App
efs/FactoryApp/
Open "factorymode" file with text editor
Change OFF to ON
Reboot
Click to expand...
Click to collapse
already tried this but not working.
sumonfd said:
already tried this but not working.
Click to expand...
Click to collapse
Tried to do the same for "keystr" file?
Mr.W0lf said:
Tried to do the same for "keystr" file?
Click to expand...
Click to collapse
both file are edited to "ON" but was not working then delete these file & restart after that edited then reboot, now working.
But IMEI problem, please advise me how to fix that.
Hello I found this flashable tweak from franco dev team, 2013 , but they are working good just sharing then. Credits to the awesome franco and his dev team.
Just flash it in recovery, to remove them just dirty flash your current ROM, enjoy.
875mntsettings
Code:
#!/system/bin/sh
# chmod -R 755 /system/etc/init.d
# 12-May-2013 by Franco's Dev Team
# malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres
# sysfs+sdcard tweaks
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /proc;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /sys;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /sys/kernel/debug;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /mnt/shell/emulated;
for i in /storage/emulated/*; do
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto $i;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto $i/Android/obb;
done;
# partition tweaks
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,barrier=0,noauto_da_alloc,discard -t auto /data;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,barrier=0,noauto_da_alloc,discard -t auto /cache;
busybox mount -o remount,nodev,noatime,nodiratime,barrier=0,noauto_da_alloc,discard -t auto /system;
925vmsettings
Code:
#!/system/bin/sh
# chmod -R 755 /system/etc/init.d
# 26-Jun-2013 by Franco's Dev Team
# malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres
# disable sysctl.conf to prevent ROM interference
if [ -e /system/etc/sysctl.conf ]; then
mount -o remount,rw /system;
mv /system/etc/sysctl.conf /system/etc/sysctl.conf.fkbak;
mount -o remount,ro /system;
fi;
# vm tweaks
echo 5 > /proc/sys/vm/dirty_background_ratio;
echo 200 > /proc/sys/vm/dirty_expire_centisecs;
echo 20 > /proc/sys/vm/dirty_ratio;
echo 500 > /proc/sys/vm/dirty_writeback_centisecs;
echo 2884 > /proc/sys/vm/min_free_kbytes;
echo 4 > /proc/sys/vm/min_free_order_shift;
echo 3 > /proc/sys/vm/page-cluster;
echo 0 > /proc/sys/vm/swappiness;
echo 100 > /proc/sys/vm/vfs_cache_pressure;
# lmk tweaks
minfree=6144,8192,12288,16384,24576,40960;
lmk=/sys/module/lowmemorykiller/parameters/minfree;
minboot=`cat $lmk`;
while sleep 1; do
if [ `cat $lmk` != $minboot ]; then
[ `cat $lmk` != $minfree ] && echo $minfree > $lmk || exit;
fi;
done&
# fs tweaks
echo 10 > /proc/sys/fs/lease-break-time;
# entropy tweaks
echo 128 > /proc/sys/kernel/random/read_wakeup_threshold;
echo 256 > /proc/sys/kernel/random/write_wakeup_threshold;
# tcp tweaks
echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control;
950iosettings
Code:
#!/system/bin/sh
# chmod -R 755 /system/etc/init.d
# 11-Jun-2013 by Franco's Dev Team
# malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres
# disable sysctl.conf to prevent ROM interference
if [ -e /system/etc/sysctl.conf ]; then
mount -o remount,rw /system;
mv /system/etc/sysctl.conf /system/etc/sysctl.conf.fkbak;
mount -o remount,ro /system;
fi;
# general queue tweaks
for i in /sys/block/*/queue; do
echo 512 > $i/nr_requests;
echo 512 > $i/read_ahead_kb;
echo 2 > $i/rq_affinity;
echo 0 > $i/nomerges;
echo 0 > $i/add_random;
echo 0 > $i/rotational;
done;
# override scheduler defaults with tweaked values
scheduler=reset;
while sleep 1; do
current=`cut -d\[ -f2 /sys/block/mmcblk0/queue/scheduler | cut -d\] -f1`;
if [ $scheduler != $current ]; then
scheduler=$current;
if [ $scheduler == "deadline" ]; then
# deadline tweaks
echo 250 > /sys/block/mmcblk0/queue/iosched/read_expire;
echo 2500 > /sys/block/mmcblk0/queue/iosched/write_expire;
echo 1 > /sys/block/mmcblk0/queue/iosched/writes_starved;
echo 1 > /sys/block/mmcblk0/queue/iosched/front_merges;
echo 8 > /sys/block/mmcblk0/queue/iosched/fifo_batch;
elif [ $scheduler == "row" ]; then
# row tweaks
echo 100 > /sys/block/mmcblk0/queue/iosched/hp_read_quantum;
echo 75 > /sys/block/mmcblk0/queue/iosched/rp_read_quantum;
echo 5 > /sys/block/mmcblk0/queue/iosched/hp_swrite_quantum;
echo 4 > /sys/block/mmcblk0/queue/iosched/rp_swrite_quantum;
echo 4 > /sys/block/mmcblk0/queue/iosched/rp_write_quantum;
echo 3 > /sys/block/mmcblk0/queue/iosched/lp_read_quantum;
echo 12 > /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum;
echo 10 > /sys/block/mmcblk0/queue/iosched/read_idle;
echo 25 > /sys/block/mmcblk0/queue/iosched/read_idle_freq;
## N4 and N10 row adds lsl and rsl, which were hardcoded previously
echo 10000 > /sys/block/mmcblk0/queue/iosched/low_starv_limit;
echo 5000 > /sys/block/mmcblk0/queue/iosched/reg_starv_limit;
## N4 and N10 have a new version of row with corrected entry for lsq and renamed ri and rif
[ `cat /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum` != "2" ] && echo 2 > /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum;
echo 10 > /sys/block/mmcblk0/queue/iosched/rd_idle_data;
echo 25 > /sys/block/mmcblk0/queue/iosched/rd_idle_data_freq;
elif [ $scheduler == "cfq" ]; then
# cfq tweaks
echo 4 > /sys/block/mmcblk0/queue/iosched/quantum;
echo 80 > /sys/block/mmcblk0/queue/iosched/fifo_expire_sync;
echo 330 > /sys/block/mmcblk0/queue/iosched/fifo_expire_async;
echo 12582912 > /sys/block/mmcblk0/queue/iosched/back_seek_max;
echo 1 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty;
echo 60 > /sys/block/mmcblk0/queue/iosched/slice_sync;
echo 50 > /sys/block/mmcblk0/queue/iosched/slice_async;
echo 2 > /sys/block/mmcblk0/queue/iosched/slice_async_rq;
echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle;
echo 0 > /sys/block/mmcblk0/queue/iosched/group_idle;
echo 1 > /sys/block/mmcblk0/queue/iosched/low_latency;
## N4 and N10 cfq adds tl, which was hardcoded previously
echo 300 > /sys/block/mmcblk0/queue/iosched/target_latency;
fi;
fi;
# loop forever independently
done&
Flash an unidentified 3-year-old zip? Thank you, but I'll pass...
fedef12evo said:
Hello I found this flashable tweak from franco dev team, 2013 , but they are working good just sharing then. Credits to the awesome franco and his dev team.
Just flash it in recovery, to remove them just dirty flash your current ROM, enjoy.
Click to expand...
Click to collapse
Why should anyone flash this?
Can you also post a Ice Cream Sandwich rom to go with it
fedef12evo said:
Hello I found this flashable tweak from franco dev team, 2013 , but they are working good just sharing then. Credits to the awesome franco and his dev team.
Just flash it in recovery, to remove them just dirty flash your current ROM, enjoy.
Click to expand...
Click to collapse
Don't you think you should at least explain exactly what these tweaks do?!
download the zip with pc, then open it and read every of 3 tweak what do, im gonna post it for you
first off, what do these "tweaks" do do you know? as nd Franco isnt a dev team, its an individual person.
simms22 said:
first off, what do these "tweaks" do do you know? as nd Franco isnt a dev team, its an individual person.
Click to expand...
Click to collapse
Read them tweak, back in thr day franco had a team
fedef12evo said:
Read them tweak, back in thr day franco had a team
Click to expand...
Click to collapse
no, he doesnt. he has people test out his kernels, but he IS alone. i know, im friends with him. i dont need to read the tweaks, you posted them here and you have to post what they do. if not, your thread will kust get closed down.
Thread closed. No-one with any sense would try this considering absolutely no info on resultant effects has been given, and the sheer age of the "tweaks".
Anyone wishing to try does so bearing the above caveat in mind.