Related
So, I just deodexed my Defy MB525 and wanted to share this info.
It works on Defy+ too!
************************************************************
DEODEXING ONLY MAKES SENSE IF YOU ARE USING A STOCK ROM.
MOST OF CUSTOM ROMs ARE ALREADY DEODEXED
************************************************************
WHAT IS DEODEXING?
Read here for a complete guide on odexed vs deodexed ROMs. In a few words a deodexed ROM allows users and developers to make easier modifications and theming.
ATTENTION:
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!
If you don't follow the steps correctly you might brick your tablet and/or lose your personal data!
REQUIREMENTS:
xUltimate (download here)
Rooted Motorola Defy/Defy+
ADB set up and basic knowledge of using it
Windows PC
a brain that is able to think (not too much )
Process:
1. Unzip xUltimate to a folder, and launch "Main.exe"
2. Plug in your Defy/Defy+ (USB debugging enabled)
3. If everything is OK, xUltimate should recognize the phone and make a connection. You now should see a list of options.
4. Run option 5. This is going to take a while. Don't panic.
5. When it's finished, exit xUltimate and put the phone in USB mass storage mode.
6. Go back into the xUltimate folder, copy "done_frame", and "done_app" and move them to the root of the sdcard.
7. Turn off the USB mass storage.
8. Open command promt, navigate to your ADB directory, and type in the following:
Code:
adb shell
su
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
reboot
8. Now, let your phone reboot, it is now deodexed!
Thanks for sharing. Although I might have some problem with that last requirement
I'll use the thanks button on this one definitely
thanks. some people think a odexed rom run faster than deodexed rom.if you dont modify your rom , i think a odexed rom works better.
Sent from my MB525 using xda premium
hsrars-d said:
So, I just deodexed my Defy MB525 and wanted to share this info.
It works on Defy+ too!
************************************************************
DEODEXING ONLY MAKES SENSE IF YOU ARE USING A STOCK ROM.
MOST OF CUSTOM ROMs ARE ALREADY DEODEXED
************************************************************
WHAT IS DEODEXING?
Read here for a complete guide on odexed vs deodexed ROMs. In a few words a deodexed ROM allows users and developers to make easier modifications and theming.
ATTENTION:
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!
If you don't follow the steps correctly you might brick your tablet and/or lose your personal data!
REQUIREMENTS:
xUltimate (download here)
Rooted Motorola Defy/Defy+
ADB set up and basic knowledge of using it
Windows PC
a brain that is able to think (not too much )
Process:
1. Unzip xUltimate to a folder, and launch "Main.exe"
2. Plug in your Defy/Defy+ (USB debugging enabled)
3. If everything is OK, xUltimate should recognize the phone and make a connection. You now should see a list of options.
4. Run option 5. This is going to take a while. Don't panic.
5. When it's finished, exit xUltimate and put the phone in USB mass storage mode.
6. Go back into the xUltimate folder, copy "done_frame", and "done_app" and move them to the root of the sdcard.
7. Turn off the USB mass storage.
8. Open command promt, navigate to your ADB directory, and type in the following:
Code:
adb shell
su
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
reboot
8. Now, let your phone reboot, it is now deodexed!
Click to expand...
Click to collapse
Are you know the procedure how extract the stock Rom of Defy by md5 file?.
I would like use to modifiy system, kernel etc
Thanks
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 ?
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Well, it seems Google is really retarded regarding SD Card access, changing API every other version:
http://stackoverflow.com/questions/32129716/how-does-storage-access-change-on-android-6
Radek Hulán said:
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Click to expand...
Click to collapse
i used the old Kitkat fix for my brief period on 6.0, but i rolled back to 5.1 for the time being, battery drain was too much.. here
Well, not going to root my device to gain basic features such as being able to delete photos Camera app put on SD card.
This is insane.
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Thanks Radek for this!!!
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
interesting. i see on some lines there are twrp. so this method can only be used with G4 variants that has twrp? CMIIW
i'd really like to try this on my H818P but there's no TWRP for the variant yet...
Good work mate
Requires root ?
It does not require root, but you must have unlocked bootloader.
Odesláno z mého LG-H815 pomocí Tapatalk
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Continue working this metod?
Sorry for me bad english xD
[email protected] said:
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Click to expand...
Click to collapse
Download TWRP for LG G4, run it:
https://twrp.me/devices/lgg4h815.html
In TWRP, select Mount > System, from menu, and continue according to these instructions.
ADB is part of Android SDK tools:
http://developer.android.com/sdk/index.html#Other
I don't know if it is the same problem but I believe it is, so my problem is that I can transfer files from SD to internal but it doesn't work the other way around, I don't want to unlock my bootloader so is there anything else I can do? Thanks
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Nazdar Radku,
the solution is known feature of MM (adopt external storage), but biggest dissadvantage of this, is that you cannot use SD card in other devices anymore - not only in PC using some reader, but not even in other LG-ie your lg g4 broke....no way to get your data back. For some reason LG didnt include this functionality of MM yet. 2nd disadvantage is slowing down your device, as acces, R/W ops are quite slower. And I agree with googles approach to SD card - they want to "protect" users is foolish - you cannot protect stupid people, they should make it as default but keep option for advanced users to access storage as before KK for advanced user as it could be done with KK & LP using that media_rw grp hack.
coolmaster121 said:
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Click to expand...
Click to collapse
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
rick09 said:
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
Click to expand...
Click to collapse
I resolved the issue by basically booting back in to TWIRP, flashing the stock image again. (didnt loose any files as I didnt do a wipe)
Then ran through the commands from the previous post. But the "set" did not work for me. I then downloaded the build.prop file to the desktop using the "get" command and edited it with wordpad, saved and then sent over the edited file, followed the rest of the permissions and it worked fine then.
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
rick09 said:
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
Click to expand...
Click to collapse
Just tried, it, does not seem to work. it changes the value, says I need to restart, but after restart it goes back to false
Lg G4 SD card as internal storage
Can someone tell me a little more detail on this im new to this and trying to figure it out for myself what software do I need and how to do this to my 2 lg G4's
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.
Disclaimer: I am not responsible for bricking your 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/and...nware-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 unmount /system
10. Type: adb shell reboot
hi,
Link: https://forum.xda-developers.com/and...nware-t3721978 is not working. Can you please restore it?
sylarm said:
hi,
Link: https://forum.xda-developers.com/and...nware-t3721978 is not working. Can you please restore it?
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/android/themes/alienware-t3721978