Develop Bugs

Help installing theme

This is the theme I would like to apply. Ive only installed ones in zip form, and i tried to adb push this but i dont have the correct commands or its not the right way to install? Please help me get this to work
http://forum.xda-developers.com/showthread.php?t=716727

To copy a framework-res.apk to your phone:
Edit: MAKE A NANDROID BACKUP BEFORE ATTEMPTING THIS
1. Boot into clockwork recovery (hold volume down and power while phone is off then choose recovery)
2. Plug the phone into the usb port on your computer.
3. In clockworkmod, scroll down to partitions and select it.
4. Select "mount /system"
5. Now copy the framework-res.apk file that you want to put on your phone into the sdk tools folder from wherever you downloaded it.
6. While you have the tools folder open on your desktop, hold shift and right click somewhere inside the folder. Choose "open command window..."
7. Type the following command:
adb push framework-res.apk /system/framework/
8. When it finishes copying, go back to your phone and choose "unmount /system"
9. Now go into the command window and type:
adb reboot
Once your phone reboots, you should have the replaced framework-res images.

[GUIDE] Mini guide to root Gnex manually

1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.

it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )

cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.

Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.

You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium

smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.

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

PUSH ZIP FILES To SDCARD While in RECOVERY

SEND FILES THROUGH ADB When IN RECOVERY MODE
1. Connect phone in recovery mode to pc….
2. In TWRP mount menu select sdcard to mount
3. Copy the Rom.Zip(I want to push the Zip file which name is Rom.Zip) file to platform tools folder which can be found in sdk folder .
4. Now open command prompt and change the directory path to sdk\platform-tools.(mine platformtools path is C:\adt-bundle-windows-x86-20140702\sdk\platform-tools so check yours and change it to that path)
5. Now check wheather device is connected or not. type adb devices and press enter(if device not connected then goto www.adbdriver.com and download adb driver installer,its about 9 mb,then install it and run the program while your phone is connected in recovery mode and it will automatically detect your phone and click on istall adb driver(in this process your phone should stay connected as in recovery mode and internet is required) then move to next step
6. If device found connected type adb remount and press enter(it will give message remount succed)
7. Here you type the push command to push the file
adb push Rom.zip /sdcard press enter and it will send file to your phone.now you can flash the Rom.zip through recovery….
Hope it will help you…press thanx button if it helps you

Replacing Boot Animation Without Rooting

Can someone check if this method works to replace stock bootanimation without rooting the device?
Disclaimer: I am not responsible for bricking device or bootloop. Also, note that modifying /system will break OTA update. So, please try it at your own risk.
1. Download any bootanimation and make sure to change the name to bootanimation only. You can get it from here. Link: https://forum.xda-developers.com/android/themes/alienware-t3721978 (Credit goes to @mauam)
2. Go to device settings/Developers option and turn on USB debugging
3. Make sure you have ADB tool installed properly in your computer.
4. Connect your device to the computer using the USB cable.
5. Now open ADB tool folder and paste the bootanimation zip file here.
6. On the same ADB folder, press shift+right click and open command box.
7. Type: adb shell mount /system
8. Now type: adb push bootanimation.zip /system/media
9. Type: adb shell umount /system
10. Type: adb shell reboot
I am not sure if it will work for Mi A1 (I can't test as I no longer have an Mi A1), but it works perfectly on my Nokia 7plus.

Rowdyy Ronnie said:
Can someone check if this method works to replace stock bootanimation without rooting the device?
Disclaimer: I am not responsible for bricking device or bootloop. Also, note that modifying /system will break OTA update. So, please try it at your own risk.
1. Download any bootanimation and make sure to change the name to bootanimation only. You can get it from here. Link: https://forum.xda-developers.com/android/themes/alienware-t3721978 (Credit goes to @mauam)
2. Go to device settings/Developers option and turn on USB debugging
3. Make sure you have ADB tool installed properly in your computer.
4. Connect your device to the computer using the USB cable.
5. Now open ADB tool folder and paste the bootanimation zip file here.
6. On the same ADB folder, press shift+right click and open command box.
7. Type: adb shell mount /system
8. Now type: adb push bootanimation.zip /system/media
9. Type: adb shell umount /system
10. Type: adb shell reboot
I am not sure if it will work for Mi A1 (I can't test as I no longer have an Mi A1), but it works perfectly on my Nokia 7plus.
Click to expand...
Click to collapse
Yes, I habe tried it now and it works, the bootanimation is in the system/media folder, why wouldn't ot work? Lol

Haxomen said:
Yes, I habe tried it now and it works, the bootanimation is in the system/media folder, why wouldn't ot work? Lol
Click to expand...
Click to collapse
Because you can't modify system files without root

jigs4wkiller said:
Because you can't modify system files without root
Click to expand...
Click to collapse
I am not rooted and it worked, how?

jigs4wkiller said:
Because you can't modify system files without root
Click to expand...
Click to collapse
That's why we are mounting the system partition to push the bootanimation.zip into /system/media

Haxomen said:
I am not rooted and it worked, how?
Click to expand...
Click to collapse
have you unlocked bootloader?

I haven't tried it and I will not try it.
But if you can push it into the system and It doesn't work, try setting correct permissions for the files after pushing it.

Rowdyy Ronnie said:
That's why we are mounting the system partition to push the bootanimation.zip into /system/media
Click to expand...
Click to collapse
Yes I know but when you try to override other files it will not work that's why I'm a bit confused.