Develop Bugs

[CWMR ZIP] ICS Keyboard backlight fix

First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE

Awesome!

does not work for me...

Worked perfect here, that fixes my only serious issue with the ICS rom.

I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.

does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing

The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.

Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.

Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was

Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium

Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!

Can anyone help me with this via step by step?

I could use a little help as well
Sent from my SGH-I927 using xda app-developers app

Yea, i could use some help too, after re-writing over the existing file didn't work

OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.

Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch

ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man

LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?

Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister

Hummm is their gonna b a flashable zip for this ?

[GUIDE]Swap Internal Memory to External & Vice Versa

The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
Step 1: Setting up stuff
Find and download a suitable file explorer that allows you to modify and browse system files. I recommend Root Explorer. (Optional)
Download and install Terminal Explorer from the Google Play Store.
Download and install Script Manager from the Google Play Store. (Optional)
Step 2: Walking the path
Open Terminal Emulator and type in
Code:
su
Your root manager should request you for permission. Grant the app superuser permission.
Type in
Code:
vold
Press enter
Type in
Code:
mount -t vfat -o umask:0000,uid=1000,gid=1023 /dev/block/vold/179:33 /storage/sdcard0
Press enter.
Type in
Code:
mount -o bind /data/media /storage/sdcard1
Press enter.
Click to expand...
Click to collapse
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
 @darz
 @raw235
 @mattiadj
 @Ace King 34

not work in FW XM Dual
how to swap internal and external in FW XMD ?

@gadgetroid , will it work in Xperia M Dual 4.2 ?

It Worked!!!
gadgetroid said:
The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
@darz
@raw235
@mattiadj
@Ace King 34
Click to expand...
Click to collapse
Worked for me
13 GB internal storage

aerialus said:
not work in FW XM Dual
how to swap internal and external in FW XMD ?
Click to expand...
Click to collapse
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Code:
mount > mount
Then, on the computer, open a command prompt window (or terminal on Linux) and type in
Code:
adb pull /partitions
Code:
adb pull /mount
Put these two files in the zip along with the vold folder and post them here. I will look into it and provide you the guide.
jereMarfil24 said:
@gadgetroid , will it work in Xperia M Dual 4.2 ?
Click to expand...
Click to collapse
Since it runs 4.2, I can't be very sure, as Sony may have changed device names. Once the above user submits the files, I will look into it and post the guide.

gadgetroid said:
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Click to expand...
Click to collapse
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?

Did u written su above?
Sent from my C1904 using Tapatalk 4

aerialus said:
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.

gadgetroid said:
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.
Click to expand...
Click to collapse
my device is already rooted and have Busybox installed,,
please look at my attachment

aerialus said:
my device is already rooted and have Busybox installed,,
please look at my attachment
Click to expand...
Click to collapse
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.

aerialus said:
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.

gadgetroid said:
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.
Click to expand...
Click to collapse
in XM Dual no need use rootfixer anymore,,
just root with tools and success full root,,
magicw said:
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.
Click to expand...
Click to collapse
ok i will try :fingers-crossed:

Yes. That is exactly what it does. It works if you put in sdcard

Script
I have created a script for this. If OP gives me permission i can publish it.

pull partitions and mounts success,,
but when i try to pull folder "/dev/block/vold"
the result is " 0 files pulled, 0 files skipped"
see my attachment

icoolguy1995 said:
I have created a script for this. If OP gives me permission i can publish it.
Click to expand...
Click to collapse
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.

gadgetroid said:
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.
Click to expand...
Click to collapse
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped

icoolguy1995 said:
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped
Click to expand...
Click to collapse
I'll add it to the op soon. BTW, if you place the script in /data folder and set it to rw-r--r--, it will be easier. That way, the script won't be in the wrong drive after it's been switched.

No it will not work unless all the options are ticked on permission setting.

icoolguy1995 said:
No it will not work unless all the options are ticked on permission setting.
Click to expand...
Click to collapse
It works for me with rw-r--r--
This message was brought to you by my Sony Xperia M (C1905), using the XDA app.

[SS/DS] Deodex 4.3 Firmware on LOCKED BOOTLOADER (NOOB FRIENDLY)

Hey guys this is a noob-friendly tutorial on how to deodex stock 4.3 Firmware on a locked bootloader. This tutorial is for windows only, im sorry, that's what i have.
Requirements:
1. A fully rooted xperia M.
2. Busybox installed
3. Winrar
4. A brain
5. Time and patience.
BEFORE WE START, MAKE SURE YOU HAVE INSTALLED BUSYBOX:
1. Go to playstore.
2. Search busybox
3. Download the one by stericsson, not busybox x, not anyother busybox. If you are using busybox x or something else. This app will replace the one you downloaded so do it anyway.
4. Open the app
5. Click normal install
6. After installation, reboot.
PART 1:
Here i will show you how to setup adb as a variable. This is NOT optional.
1. Go to this website: http://developer.android.com/sdk/index.html
2. Scroll down
3. Click download for other platforms.
4. Go to the sdk tools only list and download the zip for windows 32&64 bit. NOT THE EXE, THE ZIP.
5. After downloading is finished, right click on the file and click "extract files..."
6. Click the "C:\" directory and the extract.
6.1. Download this file: http://www.mediafire.com/?d5wj9bslikmf53d
6.2. Extract it into the root of the android-sdk-windows folder, in the "C:\" directory.
7. After thats done, Right click on "Computer" ("my computer" for windows xp)
8. Click "properties"
9. Click on the advanced tab
10. Click environment variables
11. double click on the text entry named "Path" in the lower list box
12. At the end of it, add: ";C:\android-sdk-windows\platform-tools" (without quotation marks)
13. Click on OK to exit out of the dialog
14. then OK again to get out of My computer's properties
15. Reboot computer.
PART 2:
Here i will show you how to deodex your firmware.
16. For both single sim download this: http://d-h.st/VWr
For C2004 download this: https://www.dropbox.com/s/90qbypc36kde8y9/deodex_c2004_dual.zip
For c2005 download this: https://www.dropbox.com/s/mkzfnt05vhwjcta/deodex_c2005__Latest.zip
17. Extract to anywhere, the file for you from the above links.
18. In the extracted folder open system
19. Take both app and framework folders and paste them onto your desktop.
20. Rename the app folder to done_app
21. Rename the framework folder to done_framework.
22. Connect your phone to computer via usb
23. Copy the done_app and done_framework folders to the root of your external sd card. So these files can be found at /ext_card/done_app and /ext_card/done_framework.
24. disconnect phone
25. On phone, go to settings
26. Click developer options
27. Enable usb debugging
28. Click revoke usb debugging authorisation, then ok
29. Connect phone to pc again
30. On pc, Click start
31. Click run
32. Type cmd in the box, then ok
33. A command prompt window should open up.
34. Type adb shell, and hit enter. If it says that your phone is unauthorised, then check your phone, grant the computer permissions to use adb.
35. Type adb shell and hit enter again if you got the unauthorised error. This should start daemon. If you didn't get the unauthorised error, dont type it again.
36. Now type these commands line by line, hitting enter as you type each line, NOT all of them at the one go. Copy and paste would be better than typing them.
su
stop
mount -o rw,remount /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /ext_card/done_app/* /system/app/
cp /ext_card/done_framework/* /system/framework/
mount -o ro,remount /system
reboot
39. When you're phone reboots itself, you will have a fully deodexed
Stock firmware.
TROUBLESHOOTING (MUST READ THIS!!!!) :
1. If you got an error like system is busy when typing in the second last command, wait a minute then retype it. If it happens again after you retype it then run the STOP command again and retry.
2. If settings app force closes after you deodex, download this on your phone: http://www.mediafire.com/?ygyuln0heu25qb9. Extract it using a file manager. In the extracted folder, open system then app then move all three files there to /system/app overwriting the old settings app. Set all three files' permissions to rw-r-r. Reboot. It should now work fine.
3. If any other of your apps give a force close, then uninstall and reinstall them. This is very unlikely though, none of your apps should give a force close error.
CREDITS: @paper13579 for creating this thread and editing the code a little bit. A big thanks to @gamer649 who showed me the method to deodex. @arshh19 for providing deodexed files for single sim. @stalin.sk2 for providing deodexed files for C2004 and C2005. @ansebovi for creating the moddified settings.apk
Sent from my C2004 using xda app-developers app

thks bro but one Mistake = brick So until ı hava à Lots öf money., i cant RİSK that.
...... Bull**** this SwiftKey Keyboard ı cant close auto Fix.
Sent from my C1905 using XDA Premium 4 mobile app

abuzer3 said:
thks bro but one Mistake = brick So until ı hava à Lots öf money., i cant RİSK that.
...... Bull**** this SwiftKey Keyboard ı cant close auto Fix.
Sent from my C1905 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Bro, i gave you this guide step by step, you don't need to figure anything out yourself. It's all done for you. It works, trust me, i used that exact procedure on my permanently locked bootloader and ut worked. Same for other people
Sent from my C2004 using xda app-developers app

Thanks for this thread it's very helpfull but It's not so noob friendly. ADB won't work with your setup guide because adb.exe is placed in different location. In my case proper location is: C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools but it's sdk version/os type related.

iks8 said:
Thanks for this thread it's very helpfull but It's not so noob friendly. ADB won't work with your setup guide because adb.exe is placed in different location. In my case proper location is: C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools but it's sdk version/os type related.
Click to expand...
Click to collapse
You downloaded the wrong package
Is you read it properly, you would have realised that this is what i wanted you to download it from here http://developer.android.com/sdk/index.html#download. Scroll down. Click download for other platforms. Scroll down to sdk tools only. Click the first windows zip package. It says all of that in the guide
Sent from my C2004 using xda app-developers app

paper13579 said:
You downloaded the wrong package
Is you read it properly, you would have realised that this is what i wanted you to download it from here http://developer.android.com/sdk/index.html#download. Scroll down. Click download for other platforms. Scroll down to sdk tools only. Click the first windows zip package. It says all of that in the guide
Sent from my C2004 using xda app-developers app
Click to expand...
Click to collapse
Yes, you're right. Sorry xD

iks8 said:
Yes, you're right. Sorry xD
Click to expand...
Click to collapse
No problem bro.
Sent from my C2004 using xda app-developers app

When i download the zip you said to download, there is no adb in folder \tools, just a txt file saying that adb has been moved to an other directory. Do you have a direct link where i could download the right zip ?
PS : Sorry for my bad english

krarche said:
When i download the zip you said to download, there is no adb in folder \tools, just a txt file saying that adb has been moved to an other directory. Do you have a direct link where i could download the right zip ?
PS : Sorry for my bad english
Click to expand...
Click to collapse
This is the .zip what you are told to download. I've just had a look in my SDK folder and it is the same, have you got a platform-tools folder?

No, no platform-tools folder

krarche said:
No, no platform-tools folder
Click to expand...
Click to collapse
Download the .zip I'm attaching to this post and then extract it in the root of the SDK folder. So you can choose between going to platform-tools and tools. Once you have done that edit the path so instead of it finishing with /tools it will finish with /platform-tools.

That worked ! Thanks for your help

krarche said:
That worked ! Thanks for your help
Click to expand...
Click to collapse
Not a problem, I have the entire ADT and SDK so I have every file Remember to hit the thanks button for me and paper13579.

Sorry, i just saw your comments. did i miss something in my guide that i should add?
Sent from my C2004 using xda app-developers app

paper13579 said:
Sorry, i just saw your comments. did i miss something in my guide that i should add?
Sent from my C2004 using xda app-developers app
Click to expand...
Click to collapse
In the zip you're saying to download in your guide, adb is missing in the folder \tools

Hi bro can make tutorial for unlocked bootloader to.thx

YsfIsma said:
Hi bro can make tutorial for unlocked bootloader to.thx
Click to expand...
Click to collapse
Bro there is already a tutorial for unlocking bootloader, here it is(for dual Sim) http://forum.xda-developers.com/showthread.php?t=2484622
For single sim- http://forum.xda-developers.com/showthread.php?t=2650510
Sent from my C2004 using Tapatalk

paper13579 said:
Hey guys this is a noob-friendly tutorial on how to deodex stock 4.3 Firmware on a locked bootloader. This tutorial is for windows only, im sorry, that's what i have.
Requirements:
1. A fully rooted xperia M.
2. Winrar
3. A brain
4. Time and patience.
PART 1:
Here i will show you how to setup adb as a variable. This is NOT optional.
1. Go to this website: http://developer.android.com/sdk/index.html
2. Scroll down
3. Click download for other platforms.
4. Go to the sdk tools only list and download the zip for windows 32&64 bit. NOT THE EXE, THE ZIP.
5. After downloading is finished, right click on the file and click "extract files..."
6. Click the "C:\" directory and the extract.
6.1. Download this file: http://www.mediafire.com/?d5wj9bslikmf53d
6.2. Extract it into the root of the android-sdk-windows folder, in the "C:\" directory.
7. After thats done, Right click on "Computer" ("my computer" for windows xp)
8. Click "properties"
9. Click on the advanced tab
10. Click environment variables
11. double click on the text entry named "Path" in the lower list box
12. At the end of it, add: ";C:\android-sdk-windows\platform-tools" (without quotation marks)
13. Click on OK to exit out of the dialog
14. then OK again to get out of My computer's properties
15. Reboot computer.
PART 2:
Here i will show you how to deodex your firmware.
16. For both single sim download this: http://d-h.st/VWr
For C2004 download this: https://www.dropbox.com/s/90qbypc36kde8y9/deodex_c2004_dual.zip
For c2005 download this: https://www.dropbox.com/s/mkzfnt05vhwjcta/deodex_c2005__Latest.zip
17. Extract to anywhere, the file for you from the above links.
18. In the extracted folder open system
19. Take both app and framework folders and paste them onto your desktop.
20. Rename the app folder to done_app
21. Rename the framework folder to done_framework.
22. Connect your phone to computer via usb
23. Copy the done_app and done_framework folders to the root of your external sd card. So these files can be found at /ext_card/done_app and /ext_card/done_framework.
24. disconnect phone
25. On phone, go to settings
26. Click developer options
27. Enable usb debugging
28. Click revoke usb debugging authorisation, then ok
29. Connect phone to pc again
30. On pc, Click start
31. Click run
32. Type cmd in the box, then ok
33. A command prompt window should open up.
34. Type adb shell, and hit enter. If it says that your phone is unauthorised, then check your phone, grant the computer permissions to use adb.
35. Type adb shell and hit enter again if you got the unauthorised error. This should start daemon. If you didn't get the unauthorised error, dont type it again.
36. Now type these commands line by line, hitting enter as you type each line, NOT all of them at the one go. Copy and paste would be better than typing them.
Su
Stop
mount -o rw,remount /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /ext_card/done_app/* /system/app/
cp /ext_card/done_framework/* /system/framework/
mount -o ro,remount /system
Reboot
39. When you're phone reboots itself, you will have a fully deodexed
Stock firmware.
TROUBLESHOOTING (MUST READ THIS!!!!) :
1. If you got an error like system is busy when typing in the second last command, wait a minute then retype it. If it happens again after you retype it then run the STOP command again and retry.
2. If settings app force closes after you deodex, download this on your phone: http://www.mediafire.com/?ygyuln0heu25qb9. Extract it using a file manager. In the extracted folder, open system then app then move all three files there to /system/app overwriting the old settings app. Set all three files' permissions to rw-r-r. Reboot. It should now work fine.
3. If any other of your apps give a force close, then uninstall and reinstall them. This is very unlikely though, none of your apps should give a force close error.
CREDITS: @paper13579 for creating this thread and editing the code a little bit. A big thanks to @gamer649 who showed me the method to deodex. @arshh19 for providing deodexed files for single sim. @stalin.sk2 for providing deodexed files for C2004 and C2005. @ansebovi for creating the moddified settings.apk
Sent from my C2004 using xda app-developers app
Click to expand...
Click to collapse
I did as indicated but I'm not getting through the Su command!

pedroj666 said:
I did everything you say but I'm not getting through the point 30!
I downloaded the SDK Tools Only for other platforms and platform-tools. Unzipped the sdk and moved the "android-sdk-windows" folder to the root of pc c: \.
After that unzipped platform-tools folder and moved into android-sdk-windows.
After that I went to "environment variables" and added the "Path" in the lower box the list you have indicated (C: \ android-sdk-windows \ platform-tools).
did the remaining steps in sony M but when I get to step 30 nothing appears on the pc!
Click to expand...
Click to collapse
Ok, first of all, don't quote the full thread from he OP. Second, step 30 is telling you to press start. What do you mean y don't know his to get past this step. It's as basic as it can get
Sent from my E15i using xda app-developers app

paper13579 said:
Ok, first of all, don't quote the full thread from he OP. Second, step 30 is telling you to press start. What do you mean y don't know his to get past this step. It's as basic as it can get
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
Ya sorry xD!
I have noticed this but now my probelema is not this! I can not run the command Su. Give me the error "not found".

What a way to delete the core programs

Hello every one
First of all. I have a problem I can not delete the basic device software note I have root authority
II. Was installed busyBox but I can not install it and when the installation device works Risterat What problem

read about write system protection.
tutos are available on this forum (wp_mod.ko file to push in system/lib/modules, and run a command on the phone with a terminal app)
#su
insmod system/lib/modules/wp_mod.ko
if im speaking chinese, dont try
but as you tried to change partitions before having write protection removed, you wont be able to do it without a restart until you reflash your rom (clean install)

fabulous69 said:
read about write system protection.
tutos are available on this forum (wp_mod.ko file to push in system/lib/modules, and run a command on the phone with a terminal app)
#su
insmod system/lib/modules/wp_mod.ko
if im speaking chinese, dont try
but as you tried to change partitions before having write protection removed, you wont be able to do it without a restart until you reflash your rom (clean install)
Click to expand...
Click to collapse
Excuse me, I hope if they do not understand you, and my heartfelt thanks for the quick feedback if possible, a simple explanation for the action steps

i think you shouldn't try to do it...
a bad understanding of a Tutorial, and you could make your phone bug.

Follow These Steps....
muhamadalani said:
Excuse me, I hope if they do not understand you, and my heartfelt thanks for the quick feedback if possible, a simple explanation for the action steps
Click to expand...
Click to collapse
Quoted from Step 2 Here,
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470 ,
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/show....php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into a root explorer app and mount /system as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!

jayblaze406 said:
Quoted from Step 2 Here,
http://forum.xda-developers.com/desire-816/general/guide-vm-htc-desire-816-root-how-to-t2862470 ,
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/show....php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into a root explorer app and mount /system as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!
Click to expand...
Click to collapse
Thank you
Unfortunately, I could not do a thing did not work the way and I do not know why:crying::crying::crying:

[How-To][No Recovery/No Flashfire] Install "Xposed Framework" on Lenovo Vibe K4 Note

Finally i found a method to install Xposed framework on K4 note (I am on S152 ROW version) :victory::cyclops: ​Requisites:-
1. Rooted Phone
2. Busybox
3. Terminal Emulator
4. Xposed zip and installer apk files
5. SuperSu and not Kinguser
Here are the steps:-
1. Download the Zip file from here: [url]https://drive.google.com/file/d/0B7DMgItCtbjhY2hwQlM0dWdVVlE/view?usp=sharing[/URL]
2. Extract it into your phone's internal storage using any of the file manager (Though i prefer ES)
3. Install busybox from the folder and open it. Click on install and let it install the lib files.
4. Now copy the installer.bin file and xposed-sdk22-arm64.zip to root of your internal storage.
5. Now install terminal emulator and open it.
Type su and enter and allow SuperSu permission and then it will show '#' instead of '$'.
6. Now type sh /sdcard/installer.bin and press enter. (Note:- If it fails to install, rename the xposed.zip file in the root folder with xposed-vsdk.zip and installation should go through. Thanks @Ondipuli for this suggestion.)
7. It will ask whether to install Xposed or not. Press 1
Wait for the process to finish and then it will say install is successful.
8. Reboot the Phone. It might seem it is stuck at boot but give it some time(5 mins). Then it will start optimizing the apps and let it finish with that.
Now open xposed app and Voila! Xposed is installed​Enjoy Xposing!!​Credit goes to Razor Beam from youtube...
Hit Thanks if i helped:fingers-crossed::fingers-crossed:..​

Dear Bro, I Installed several times but never ever this installer.bin file ever used. And every time I got succeded. Via Flashfire 0.24

ramisumi said:
Dear Bro, I Installed several times but never ever this installer.bin file ever used. And every time I got succeded. Via Flashfire 0.24
Click to expand...
Click to collapse
Bro, this method is for those who don't want to install flashfire to flash xposed or for those who simply cant get xposed working through Flashfire(I myself was unable to install it through flashfire).
Though flashfire is recommended, sometimes it fails to flash the zip on some devices and that is a known issue. Chainfire is working on the solution.

It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app

Ondipuli said:
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes its true. I also tried but renaming is useful or I have xposed zip already i flashed with flashfire. That also worked with this installer.bin. But as it is provided zip is not installing without renaming or the otherr copy.

Ondipuli said:
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ramisumi said:
Yes its true. I also tried but renaming is useful or I have xposed zip already i flashed with flashfire. That also worked with this installer.bin. But as it is provided zip is not installing without renaming or the otherr copy.
Click to expand...
Click to collapse
Actually, for me it installed without the need of renaming. But still if you guys say so, I will edit the post and mention the need to rename the zip if it's not working by default.
Thanks..

Worked for me after renaming. Thanks.

Virus0044 said:
Worked for me after renaming. Thanks.
Click to expand...
Click to collapse
I am glad it did!

Krishnas096 said:
Finally i found a method to install Xposed framework on K4 note (I am on S152 ROW version) :victory::cyclops: ​Requisites:-
1. Rooted Phone
2. Busybox
3. Terminal Emulator
4. Xposed zip and installer apk files
5. SuperSu and not Kinguser
Here are the steps:-
1. Download the Zip file from here: https://drive.google.com/file/d/0B7DMgItCtbjhY2hwQlM0dWdVVlE/view?usp=sharing
2. Extract it into your phone's internal storage (Though i prefer ES)
3. Install busybox from the folder and open it. Click on install and let it install the lib files.
4. Now copy the installer.bin file and xposed-sdk22-arm64.zip to root of your internal storage.
5. Now install terminal emulator and open it.
Type su and enter and allow SuperSu permission and then it will show '#' instead of '$'.
6. Now type sh /sdcard/installer.bin and press enter. (Note:- If it fails to install, rename the xposed.zip file in the root folder with xposed-vsdk.zip and installation should go through. Thanks @Ondipuli for this suggestion.)
7. It will ask whether to install Xposed or not. Press 1
Wait for the process to finish and then it will say install is successful.
8. Reboot the Phone. It might seem it is stuck at boot but give it some time(5 mins). Then it will start optimizing the apps and let it finish with that.
Now open xda installer app and Voila! Xposed is installed​Enjoy Xposing!!​Credit goes to Razor Beam from youtube...
Hit Thanks if i helped:fingers-crossed::fingers-crossed:..​
Click to expand...
Click to collapse
[email protected]:/ $ su
[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # '$'.
k_shell/10161:17229: $.: not found
127|[email protected]:/ #
Plz help how to install

Help
executed installer.bin then pressed 1 but after that it shows cant create folder

PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?

shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Are you trying this method on Lollipop or Marshmallow. If so then on what version(Build no).
Sorry for the late reply. I am a student and i am not able to come online on xda regularly.

Permission ?
Hi,
I try this method, follow every steps, but it tell me this:
mount: Operation not permitted
/sdcard/installer.bin[25]: can't create /test.txt: read-only file system
Error: Busybox is not installed
I'm rooted under SuperSu, Xposed installer is installed, same as Busybox (by install the lib file too)
Can i get some help please.

Thnx BUT...
OK the first time I tried it did not work so I renamed the xposed package to xposed-vsdk.zip but it did not install the zip so xposed did not recognize or find it. So I when online and downloaded the latest sdk22 (sdk22=lollipop). I renamed it and it worked so I think you should update the master zip with the latest xposed zip.
BTW This also this works on Kindle Fire HD 8 cuz FlashFire doesn't support it.

shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Your command is missing " "(space)
The correction command is
sh /sdcard/installer.bin
Enjoy

chitranjn_k said:
[email protected]:/ $ su
[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # '$'.
k_shell/10161:17229: $.: not found
127|[email protected]:/ #
Plz help how to install
Click to expand...
Click to collapse
may be the installer.bin is in sdcard, not sdcard1

can i install on any device using this method actually I have mobile which has android 5.1.1 and arm 32bit system can i install frame work using this technique

Rename the file txt at the place of bin.then try

shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Ans:-Give space after sh. (sh /sdcard/installer.bin)

atif ahmad said:
can i install on any device using this method actually I have mobile which has android 5.1.1 and arm 32bit system can i install frame work using this technique
Click to expand...
Click to collapse
No. You cannot. The script and the xposed apk inside the zip file are for arm64 so it wont be possible. Don't try it and brick your device.