[SS/DS] Deodex 4.3 Firmware on LOCKED BOOTLOADER (NOOB FRIENDLY) - Sony Xperia M

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".

Related

Java JDK,Android SDK and resigning APK's

WINDOWS 7
Thought i would make a noob friendly guide on setting all these up..should make it easier foor noobs to have some fun
To make it more noob friendly i will include pictures
Download Java JDK HERE
Android SDK HERE
And Testsign.zip View attachment testsign.zip
Install Java JDK by double clicking the JDK file you downloaded
Now goto My Computer > Local Disk (C:\) and create a folder called Android and open it.....Create another folder called androidSDK (NO SPACES!)
Extract the Android SDK you downloaded into the AndroidSDK folder there should now be 5 folders in there....)FIG(A)add-ons,docs,platform,usb_driver and tools...
Go into tools and keep it open...the top bar will say something like C:\Android\androidSDK click this top bar and copy it ALL!FIG(A)
Now you need to add the tools folder to your path....
Right click my computer > Properties > Advanced system settings > Enviroment variables
In the system variables box (the lower one) find the path it should be the 5th one down (under OS) highlight path and click edit....
Now go to the end of that line and put a ; there..Then paste the line you copied earlier..
Your path should now look like FIG(B)
now make a Tea/Coffee/Grab a beer or whatever
Back to your tools folder now...Remember that Testsign.zip? Well extract it into your tools folder please.
Next click start (win7 logo in your taskbar) and type CMD it should say command prompt.exe double click it!
Now is the test! Type autosign and hit enter (not hard obviously) If it says XDA in huge letters you are laughing! If not drag and drop Autosign.bat from your tools folder into the CMD window and press enter.
type 1 > enter > yes
2 > enter > yes
3 > enter > yes (enter means press enter not type it.just in case your such a noob you dont know your own keyboard)
You should now be able to resign .apk files by right clicking, if that doesnt work you can type autosign in a cmd window and do option (4) to manually sign.
To install drivers for your android device.......
Check adb debugging is enabled on your phone and plug the bad boy in,go to device manager (right click my computer) find ADB (it will probably have a warning sign) right click that and direct the install to your USB_DRIVER folder
Open up Command prompt (CMD.EXE) type adb devices should say something like HT01GL902119 device
Now i think you are all done!! Please dont hesitate to ask if you have problems i have subscribed to this thread so can answer pretty quickly
Linux.....Coming soon
Saved for linux method
Saved for winxp if i reinstall my laptop
Saved for creating update.zip tutorial
Thank you very much!
If I use this method to sign a modified apk file on my Windows 7 PC,
will installing the apk via File Manager on my phone, cause infinite boot loop?
Stericsson is mentioning here that this could happen.
I dont really know i have always installed apk's (/system/app) via update.zip and have never edited 3rd party apk's(/data/app) to need to sign.
What apk's are you installing?
It's OK! I slightly edited ADW Launcher (just the highlight element in fact)
to match the Xperia (Rachael UI) interface.
It worked just fine, no problems at all!
Thank you again!
Nice guide!
brilliant guide, although i am stuck at the last hurdle. Where can i find device manager? its not in the menu when i right click on computer.
Right click My Computer
then properties>device manager
if that doesnt work it will be in control panel > Add Hardware i believe.
will you do the update.zip tutorial ? because I think that I will need it soon thanks
It is something I have been hunting for a long time. Thx for great work.
steps 2 and 3 are giving me error
Thank you very much. Precise and easy to follow.
Cheers
I'm attempting to install JDK now and don't seem to be doing something right. I'm pretty sure it's changed a bit since this thread began. Any chance someone can assist me? I'm looking to go through the Headfirst Java textbook.

[GUIDE] enable trackball/pad wake on the latest MIUI builds again

I think I found an easier way to enable trackball/pad wake again!
1. connect your phone to your pc and open a cmd window
2. execute the following commands:
adb shell
stop
cd /data/data/com.android.providers.settings/databases/
cp settings.db settings.bak
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',1);"
start
3. thats it, if you want to disable it again do the same again but instead of
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',1);"
use
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',0);"
I have found a way to enable trackpad wake on MIUI Roms again! It's a little tricky but it works perfectly.
Things you need:
SQLite Database Browser -> http://sourceforge.net/projects/sqlitebrowser/
Follow these steps exactly:
1. connect your phone to your computer and open a cmd prompt
2. type in the terminal:
Code:
cd %USERPROFILE%\desktop
adb shell stop
adb pull /data/data/com.android.providers.settings/databases/settings.db
3. extract SQLite Database Browser somewhere and start it
4. open your settings.db with SQLite Database Browser (you'll find it on your desktop)
5. Change to "Browse Data" and select the system table
6. add a "New Record"
7. doubleclick the name filed of the new record and write
Code:
trackball_wake_screen
inside. Click Apply Changes!
8. doubleclick the value field of trackball_wake_screen and write
Code:
1
inside. Click Apply Changes!
9. Save the file (maybe you want to make a backup of the original file before this point )
10. last step is to copy the file back to your phone:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell start
Now trackpad wake should work again.
Woukd this only work on miui?
There are quite a few people waiting for this feature on xboarders stock gingerbread rom.
Sent from my Nokia 3210 using XDA Premium App
Can someone try this out on the test ver? I badly need track wake
Sent from my T-Mobile G2 using XDA App
xile6 said:
Can someone try this out on the test ver? I badly need track wake
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I just tried this on my Droid Incredible, and it does work! Thanks!
Worked on my N1, Thankyou
Just wanted to say that I tried this again with the latest MIUI build...and again it works! Thanks!
Sweet worked for my HTC Incredible running MIUI 1.6.24 with Incredikernel 06192011
without adb
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
slim_thumb said:
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
Click to expand...
Click to collapse
I guess not since android has to be stoped to make this change. (stop command is to shut down android)
But why don't you just enable trackball wake in the settings menu? The Nexus One had always the option for it. The settings app checked the device name and if it wasn't passion (N1) or bravo (Desire) the trackball wake option didn't show up.
So Desire Z (vision) lost trackpad wake. Thats why I was looking for a way to enable it again. But since a few releases this isn't needed anyways.
Sent from my HTC Desire Z using Tapatalk
g4rb4g3 said:
But why don't you just enable trackball wake in the settings menu? The Nexus One had always the option for it.
Click to expand...
Click to collapse
Sorry I looked at the settings menu (under "hardware key setting"), there is no such option.
slim_thumb said:
Sorry I looked at the settings menu (under "hardware key setting"), there is no such option.
Click to expand...
Click to collapse
Goto Settings - System - Button Settings - Trackball wake
I can't belive that this doesn't exist on the Nexus One.
Sent from my HTC Desire Z using Tapatalk
Found it, my bad!
slim_thumb said:
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
Click to expand...
Click to collapse
Works with root explorer... Just copy database to sdcard then edit while connected to pc.. Copy back, change permissions, reboot and your set..
You can also just use an sqlite editor app..
Any chance someone could post step by step instructions on how to do this with sqlite editor on the phone?
EDIT:
Scratch that. Figured it out.
Thanks a million! This saved the day. Cant believe its not integrated with miui. Nexus One MIUI
Hi..
when I open cmd and I type adb shell... i get this..
'adb' is not recognized as an internal or external command,
operable program or batch file.
magdiel1975 said:
Hi..
when I open cmd and I type adb shell... i get this..
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
You need to navigate to your sdk / adb folder.
Sent from my Sensation using xda premium
trackpad wake works on latest miui.. I am currently running it? :S
I wonder why people don't use the trackball/pad wake option in the settings menu too....
This was an issue half a year ago but the MIUI team fixed it a few weeks later and since then it works without this.
works for me
g4rb4g3 said:
I have found a way to enable trackpad wake on MIUI Roms again! It's a little tricky but it works perfectly.
Things you need:
SQLite Database Browser -> http://sourceforge.net/projects/sqlitebrowser/
Follow these steps exactly:
1. connect your phone to your computer and open a cmd prompt
2. type in the terminal:
Code:
cd %USERPROFILE%\desktop
adb shell stop
adb pull /data/data/com.android.providers.settings/databases/settings.db
3. extract SQLite Database Browser somewhere and start it
4. open your settings.db with SQLite Database Browser (you'll find it on your desktop)
5. Change to "Browse Data" and select the system table
6. add a "New Record"
7. doubleclick the name filed of the new record and write
Code:
trackball_wake_screen
inside. Click Apply Changes!
8. doubleclick the value field of trackball_wake_screen and write
Code:
1
inside. Click Apply Changes!
9. Save the file (maybe you want to make a backup of the original file before this point )
10. last step is to copy the file back to your phone:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell start
Now trackpad wake should work again.
Click to expand...
Click to collapse
This method worked for me on my HTC Droid Incredible running MIUI 2.11.9. I actually used File Explorer in Android:
1. copied settings.db
2. uploaded it to my PC
3. used SQLite to edit it
4. copied it back to phone
5. backed up settings.db
6. pasted the new file in
Restarted phone and trackball wakes it up now.
Thanks!

Adb Problems? Read this.

--This thread is recommended to be viewed on a Pc/Linux (I included you guys too ), OR on your ANDROID-POWERED phone (with XDA or in browser now ).--
--This is for PC and LINUX problems.--
Hallo!
You may have adb errors such as: cannot connect to daemon. This is a common problem beginners commonly forget. Also MAKE SURE you have installed android sdk
If you get adb error like :
adb server is out of date * killing***
daemon still not running
error:cannot connect to daemon
Click to expand...
Click to collapse
That means your device can't be found in adb.
Simply:
1) Make sure USB debugging is on
Found in Settings>Applications>Development
Click to expand...
Click to collapse
2) Make sure you have YOUR PHONES DRIVERS INSTALLED.
They can be installed via HTC Sync.
Click to expand...
Click to collapse
3) Still not working? Instead of using the USB option Charge Only/Disk Drive.
Use HTC Sync USB option.
Click to expand...
Click to collapse
________________________
RUU Problem [May encounter in the future](Thanks miguelca)
--Not for RUU Setup exe.
Out of date daemon error
Click to expand...
Click to collapse
Step 1) Browser to your android sdk folder
Its probably in: C:\android-sdk-windows OR C:\Program Files (x86)\Android\android-sdk (In 64bit edition of windows) OR C:\Program Files\Android\android-sdk
Click to expand...
Click to collapse
Step 2) Enter the platform-tools folder
Its simple just press Platform-tools
Click to expand...
Click to collapse
Step 3) Copy all of the files except: Source.propties, NOTICE.txt, lib, renderscript folder.
Hold Ctrl-A then press the files, then when done right click and press copy.
Click to expand...
Click to collapse
Step 4) Browse to your RUU Folder, and paste the files there.
Enter the RUU folder, right click anywhere press paste (If asks to overwrite press yes.)
Click to expand...
Click to collapse
Step 5) Should be done now!
________________________
[Linux ADB Problems (Thanks Tectas)]
Hallo, now this part of the thread is about linux ADB Problems .
permission denied ?????????
Click to expand...
Click to collapse
If you use Linux and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
[B][I][U][COLOR="DarkOrange"][FONT="Lucida Sans Unicode"]adb kill-server
(be sure the path to the adb directory is inside the .Bashrc file or CD to the right directory)
adb start-server[/FONT][/COLOR][/U][/I][/B]
Afterwards you can exit to normal shell and use it like ever.
[End of thread. Please scroll up or down to read reply's, or to read on ]
One addidonal thing,
if you are an linux user and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
adb kill-server
(be sure the path to the adb directory is inside the .bashrc file or cd to the right directory)
adb start-server
to start the adbd in su context, afterwards you can exit to normal shell and use it like ever.
It's not as trivial as you say. I had the out of date daemon error while trying to update my phone with the 2.3.5 European RUU by football. The solution was to uncompress the RUU and replace the ADB executable and dll's with updated ones from the Android SDK I had installed. It had nothing to do with USB connections or settings. Probably the RUU wasn't prepared for Windows 7 x64 SP1... I guess.
Sent from my HTC Wildfire S A510e using XDA App
Thanks!
Updated the thread.
XDA_h3n said:
Updated the thread.
Click to expand...
Click to collapse
You're welcome!
Thank you for the nice thread, for updating it quickly and for crediting me too.
It's great when several experiences are compiled in a way that might help many other users.
That's what a community is all about.
My trick is Download Vroot on your Pc and it will install everything you need. (Might replace your current Root Manager if you don't cancel the process of it rooting.) Once you connect your phone to your pc with Vroot it's ask you to install a apk just click okay. Once you see the apk installed wait for it to get a green backrground with wire connected image. Then there you go. Sorry for my Bad English. Hope it Helps.

Help in installing apktool on ubuntu 11

Noob here
I want to install apktool on ubuntu but i am not able to get root permission on usr/local/bin folder.....
Plzz help.......
Can anyone is able to help me posting any video.
I have seen the 1st video of apktool tutorial on youtube. In that video the person opens the bin folder by open as administrator but it didn't show that option on my ubuntu....
Sent from my HTC Wildfire using xda premium
nishantsikri13 said:
Noob here
I want to install apktool on ubuntu but i am not able to get root permission on usr/local/bin folder.....
Plzz help.......
Can anyone is able to help me posting any video.
I have seen the 1st video of apktool tutorial on youtube. In that video the person opens the bin folder by open as administrator but it didn't show that option on my ubuntu....
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I think you need to install nautilus-gksu first before installing apk for you open folders as root/administrator.
1. Open up a terminal.
2. sudo apt-get install nautilus-gksu
3. sudo cp /usr/lib/nautilus/extensions-2.0/libnautilus-gksu.so /usr/lib/nautilus/extensions-3.0/
4. You can now try it on 'usr' folder by right-clicking on it and choose "open as administrator".
5. Once open, you can now extract apktool files and move it to this folder.
I have successfully install apktool with this method.
okay thanx
sudo cp /usr/lib/nautilus/extensions-2.0/libnautilus-gksu.so /usr/lib/nautilus/extensions-3.0/
cp: cannot create regular file `/usr/lib/nautilus/extensions-3.0/': Is a directory
stuck there please help!!
this should work
bambam1978 said:
sudo cp /usr/lib/nautilus/extensions-2.0/libnautilus-gksu.so /usr/lib/nautilus/extensions-3.0/
cp: cannot create regular file `/usr/lib/nautilus/extensions-3.0/': Is a directory
stuck there please help!!
Click to expand...
Click to collapse
Just open nautilus as root user directly by typing "sudo nautilus" and then enter password and after that go into usr and then extract apktool in there .................... hopefully it will work!
cheers

[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 ?

Categories

Resources