Related
Discontinuation Notice + Source Opened!
This project is now discontinued, as I have moved on to Android 4.X (ICS) which has perfect built-in RTL support.
I will still provide basic support as much as I can, but if your device has it, I recommend you move on to ICS as well.
If you wish to continue working on this project and improving, you have my blessing (as long as you credit me, of course).
Source code is available here, but be-ware: it's an undocumented, unorganized mess.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Android RTL Auto-Patcher
Version 1.5
The Problem
It's a well known fact that while Android has Hebrew and Arabic fonts, it has a problem with Right-To-Left alignment. The problem: It doesn't exist.
Sure, MOST programs display text correctly, but mix text and numbers in the same line and you'll get reverse numbers (123 appears as 321), and in SOME Google apps (like Gmail and Maps) the words themselves are reverse (so 'apple' appears as 'elppa').
The Old Solution
There is a solution for this, however you have to create a separate patch for every build, because the patch changes files in the build's framework. It's a relatively easy process, but for people who change builds constantly, it can get tiresome.
This Program
This program detects if a build is compatible with the patch, and if so - creates it almost automatically and install it back to the phone. A process that took about 10 minutes to complete before and required some knowhow, now takes only seconds and requires almost no prior experience!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ProTools
The ProTools are a collection of tools that will allow you to patch ROMs manually either directly to ZIP files, to the phone, or to framework files. It will also allow you to push, pull, extract and manipulate files to and from ROMs of all kinds, with great flexibility and ease!
Compatibility
This program is intended for use with custom DEODEXED roms of Android versions 2.1 and above. The program will inform you if your build is not deodexed.
The program will allow you to either push the fix directly to the device or flash via recovery.
WARNING: Some 'squashedFS' builds have been reported not to be compatible, and the program can not - at the moment - detect those!
Warnings
This program is in Beta stage!
Many features have not been thoroughly tested and error handling is far from perfect.
It may give some errors, crash or stall - at which point I ask that you please send me your log.txt (to find it, click 'About' and then 'Locate Log') or as an upload in this thread.
I do request - however - that you try to be as specific as possible regarding your build, your computer, and what caused the problem.
Also, if you include the log here, please enclose it in 'code' tags.
Requirements
You MUST have Microsoft .Net Framework 4 installed for this to work.
You will also need the latest Java Runtime Environment
You must also have the ADB drivers already installed:
In Windows Vista/7, just connect the phone and let Windows Update do it's thing.
In Windows XP, you need to manually install the drivers available here.
ADB itself comes with the program, so you don't need that.
How to use
If available, boot into recovery (recommended for non-rooted devices!)
Connect your phone to USB and make sure the computer recognizes it
Run the program, and select 'Test Connection'
After connection has been made, if the build is compatible - select the correct Sense version. The program WILL attempt to auto-detect, but it's not 100% reliable, so please confirm that the program detected correctly
Select distribution method:
Push to Device (Recommended) - does simply that, the program will attempt to automatically patch the phone for you.
Create ZIP - creates a ZIP file that's flashable through Recovery (Clockwork Recovery Mod). Will also offer you to save the ZIP on the SD card (doesn't even require mounting USB).
Show File - will just show you the patched 'framework.jar' so you can do whatever you want with it.
Select any additional options you might be interested in (Gingerbread keyboard, for example - is a fixed Gingerbread keyboard with fixed Hebrew RTL that is compatible with the patch the program installs. It should work on 2.2 devices as well, and replaces the stock Android keyboard).
GO GO GO!
Reporting bugs
Please be sure to provide the name and type of your build when giving feedback or reporting bugs. For better bug-squashing, please also provide your log.txt file, which you will find in the application's directory.
Also, even if you experienced no bugs, your logs will be appreciated.
Finally, if you put the the log content in your post, PLEASE encode it with 'code' tags.
If you have any additional non-bug-related questions, feel free to ask them in this thread. I will do my best to improve this program as time goes by.
Thank you, and good luck!
Download
Always available here:
Changelog, Known Issues and Planned Features
Changelog
1.5 - 14/08/2011
Advanced build numbers to 1.5 due to massive advances in the program.
Added global error handling - might not solve ALL problems, but will hopefully help avoid unlogged crashes.
When "Install Gingerbread Keyboard" and "Create Zip" are both selected, it will now also install the keyboard on the Zip.
The program will now also try to mount sd-ext in addition to system before patching (as will the flashable Zip).
When patching fails, the program will offer you to save the patched file to your computer for use with ProTools.
In the 'About' window, added the option to find the log file on your computer (for easier error reports).
Other minor undocumented improvements.
Completely overhauled the ProTools:
Offline Patching: Allows patching ROM Zips or 'framework.jar' files directly.
Manual Operations: Pretty much what ProTools was before, except with an easier straight-forward interface and with the option to operate on a ROM Zip file, from your phone, or directly from a 'framework.jar' file.
Added the option to manually push or pull anything to or from anywhere (with specific buttons for 'framework.jar', 'framework-res.apk' (for theming) and 'build.prop'.
Added the option to manually patch the Keyboard to the phone or the a ROM Zip.
1.1.2 - 20/07/2011 - minor update
Improved Sense 3.0 Detection
Updated build detection strings
1.1.0 - 14/06/2011
Fixed critical interface bug that caused the operation compelte / restart prompt not to appear if 'Push' was selected.
1.1.0 - 14/06/2011
Removed support for SD/SDRAM based builds
Instead, created three distribution methods: Push file, Create flashable zip or just Display file
Flashable zip will be flashable via recovery, and will attempt to push itself to the device's SD card.
Version 1.0.0 Beta
Build Detection:
Improved build properties detection
Vastly improved Sense detection mechanism
Sense versions now distinct by Sense version
Added Sense 2.1 (Gingerbread) support
'Pro Tools' (Beta) - Every single function of the patcher can now be called on seperately and manually.
Changed versioning scheme. Version 1.0.0 to be assigned.
Updated core framework files (fixed a lot of stability issues in Sense2.0 builds)
Planned Features
I plan to seriously improve the RTL fix itself in the near future, but since I lack the knowledge to do so myself, I'm waiting for some new methods currently under development by the excellent devs at iAndroid.co.il to be released.
I do plan to release to program's source code eventually, it's just such a mess at this point that I'm more ashamed of it than anything else.
I also plan to include a logcat monitor. Because the patch causes the phone to rebuild dalvik cache, first boot after patching often takes a VERY LONG time, and some users wrongfully assume their phone is frozen. I plan to include a logcat monitor that will hopefully know to differentiate between bootloops, errors, and dalvik rebuilding, so users can tell if their phone is actually frozen or just working. If this works, I might release this as an actual separate program.
Known Issues
Build 1.1.0 - If 'Push' is selected, when patching process finishes, no message is displayed and the program doesn't prompt to restart. - fixed in 1.1.1
There is hardly any error handling in the ProTools section. If they are called with no device available, it MAY freeze/crash the program. Will be fixed in upcoming release.
Fixes for Squashed filesystem roms do not work! Mostly.
Error handling is STILL utter ****e, may give unexpected errors (or not at all and just fail altogether).
If HTC Sync is installed and active, stuff may go nuts all around (as of 0.0.5 this is detected by the program and warns user).
Credits
Program and Graphics created by Elad Avron using Visual Studio 2010 Express.
ZIP Functions created by Elad Avron using free libraries from the IC#Code group, available at http://www.icsharpcode.net/opensource/sharpziplib/
Special thanks:
From HTCAddicts.com: Ronenpg, Ohect.
From XDA-Developers.com: TheAgent1982, silverbluem, mdeejay and the entire HD2 dev crew
From iAndroid.co.il: Classicaldude (Original fix, the hero of RTL!), Dudyk (Original fix), rasmux (Modified fix), Liavk1 (partial SenseHD fix), Avicohh (Gingerbread Keyboard), N1Man (RTL fix for Gingerbread Keyboard).
Keyboard fix by Avicohh and N1Man (from iAndoird.co.il)
If it will work man i'll give you a real big THANKS!
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
congratulation
Congratz of your new Project!
I will give it a shot as soon as i can
my teset here ..
this is my test in the log file attached
thx
I appreciate your efforts
reverse numbers problem still exits
big thanks
Voffchik said:
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Sup3r said:
I appreciate your efforts
reverse numbers problem still exits
big thanks
Click to expand...
Click to collapse
Can I get build type and log file please?
Thank you
jaguaralani said:
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Click to expand...
Click to collapse
The log indicates that you did everything right and experienced no errors, so there are two things I'd like you to try:
In the 'Toolbox' dir in the app dir, the leftover files from the creation process are left. Try pushing framework.jar manually to the device.
If that doesn't work, try putting 'classes_new.dex' in 'framework.jar', renaming it to 'classes.dex' (thus replacing the old one), and repeat step 1.
If that doesn't work something went wrong in the patching process itself, i.e. my source files aren't good for your build (they should be), the compression failed, or any step in between. Let me know if the leftover framework.jar and classes_new.dex solve the problem, and we'll try to isolate the problem from there.
Thank you all for helping
Thank you
Thank you very much for your great work.
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
NSider said:
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
Click to expand...
Click to collapse
Yes, I understand it's a problem with a lot of software, not only Android.
I will try to implement patching of Arabic characters in the future, once the program has a more solid base.
this is my log
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Ambious said:
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Click to expand...
Click to collapse
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Voffchik said:
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Right, sorry, my bad
I worked around your reported error in v.0.0.2, it was a little oversight I had in interface design.
Thank you for the report
Sent from my Android HTC HD2 using XDA App
Sup3r said:
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Click to expand...
Click to collapse
Thank you for the log.
From the log it seems like there were no errors and that everything went as planned. I'm using the same build as you, so I know it's compatible.
What I'd like you to try, if it's not too much hassle, is this:
In the 'toolbox' dir in the app dir, there are leftover files from the process. Push 'frameowkr.jar' to your device's "/system/framework/" using:
Code:
adb push framework.jar /system/framework/
and reboot.
If that solves it, the issue was with the push command (I currently have no method to actually detect if it was successful or not, I hope to fix that in future version).
If even that doesn't solve it, open 'framework.jar' using any zip/rar program, delete 'classes.dex' from it, insert 'classes_new.dex' (from the toolbox dir) into the 'framework.jar' file, and rename to 'classes.dex'. Push to the device, restart, and try again.
If you don't mind doing those things, it would help me greatly to detect where the patching process failed.
Thank you so much, and I promise to include Arabic fix as soon as the program structure is solid enough!
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
jaguaralani said:
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
Click to expand...
Click to collapse
Yeah, well, v002 changes nothing in the process, only the interface.
I'd like you to try, if not too much hassle - to push the framework file manually and reboot.
If that doesn't work, try to put 'classes_new.dex' into 'framework.jar' and rename it to 'classes.dex' and push framework.jar again.
If any of that works then I can narrow down the issue.
On another note, I got reports from other people using DesireZ that the process worked for them, so I know it's compatible, it's just a localized issue.
This doesn't specifically belong to NAND development.
Moved.
(Regardless of that, it's a wonderful project).
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]LG G3
AT&T D850[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How do I ask a question, so I'm not called a noob?[/SIZE]While you may see many questions asked in the Development section, PLEASE be aware this is not the place for questions.
Remember to use the search found at the top of the forum. There is also a search within each section. Example click on Q&A HERE. In the upper right you will now see two search's. At the top it says Search All Forums and a little further down you will see Search This Forum. Enter your search criteria in the Search This Forum to get info from this section. The search at the top will look through the entire forum.
Please read as much as you can prior to doing anything with your device.
Make sure your question has not been answered in the OP (Opening Post) of each section of Development
Search Q&A for threads that may have been started for a particular rom
[SIZE=+1]Q2: How do I update my stock firmware?[/SIZE]1) Turn on WiFi or data
2) Go to Menu > Settings > About Phone.
3) Select firmware update
[SIZE=+1]Q3: What is a ROM?[/SIZE]A rom is like a custom firmware image that is made by a Developer either entirely from scratch, or based off of the official firmware package. Some ROMs contain simple changes like changing icons and adding extra options to things, other more complicated ROMs can change the entire Android experience. Which one you will want to flash, will be entirely up to you. Read carefully, and make sure you understand what you are getting into before you flash.
[SIZE=+1]Q4: What is a Kernel?[/SIZE]A kernel is the heart of the device's OS. In simplest terms it’s a connection between your apps and your device’s hardware; i.e. the processor, RAM, etc. A custom kernel can dramatically change the way your device’s hardware performs… for the better and/or the worse]
[SIZE=+1]Q5: What is a Bootloader?[/SIZE]The bootloader is a program code that is executed before the device OS starts up, and that instructs that device to boot “normally”. The bootloader can come locked or unlocked from the manufacture. A unlocked bootloader will allow you to install custom ROMs & Kernels (as well as some other neat things) on your device.
[SIZE=+1]Q6: What does Root/Rooting mean?[/SIZE]Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc.
[SIZE=+1]Q7: What is the purpose of rooting my device?[/SIZE]Please bear in mind, rooting can be dangerous and if done wrong "brick" your phone.
Rooting the phone is a decision made by individuals looking to improve upon the Android OS. There are many benefits, however it is done to customize the phone to it's full potential
[SIZE=+1]Q8: How do I root my LG G3? [/SIZE]Use one of the following methods, for KitKat or Lollipop.
Android version 4.x.x (KitKat)
[ROOT][IOroot] LG G3 4.4.2 Jailbreak
PurpleDrake-Lite!
[Root] Stump Root for LG Devices
Android version 5.x.x (Lollipop)
One click script
[ROM][STOCK][BUMP'd] LG D850 20F Lollipop 5.0.1 (+ extras)
[SIZE=+1]Q9: How do I remove root and return to factory stock. Why would I uninstall root?[/SIZE]The complete "Unroot" method, can be found here"
Removing root is normally a process used for a couple main reasons:
1) You've done something to the device and now it doesn't seem to be working.
2) You need to return the device or send it in for service.
[SIZE=+1]Q10: What is ADB (Android Debug Bridge) and what is it for?[/SIZE]Please read [GUIDE] ADB Workshop and Guide for everyone. There is much to learn, please view everything in the threads OP
[SIZE=+1]Q11: How to I enter Download Mode and Recovery?[/SIZE]1) You must switch off the device to start the process.
2) Press and hold the “Volume Up” and connect the USB cable from phone to PC.
3) Use the original USB cable. Other device USB cables may not be detected by the Computer. It is strongly recomended to use the original cable that came with the device.
4) Wait for the driver installation on PC.
5) You will now see the download mode screen on your phone.
6) Done
You can now do any process, such as, install stock ROM through your computer or laptop.
You can return to the normal mode by pressing and holding power button.
DO NOT UNPLUG THE DEVICE while the update process is running. This can damage your device!
[SIZE=+1]Q12: What is a "logcat" and how do I create one?[/SIZE]For setting up ADB see What is ADB (above) logcat allows us to log what the OS is doing, and possibly offer information if things are not working. its quite simple to create but may be difficult for most to understand. This is a tool a Developer may ask for in detecting issues your device may be encountering.
To use logcat
Code:
adb shell
logcat
To logcat to a certain file do
Code:
adb shell
logcat -d > /sdcard/whatevertexfileyoulike.txt
For a full explanation follow the link in What is ADB
[SIZE=+1]Q13: Is there an app that will help me create a logcat directly from my phone?[/SIZE]Yes, Apps for logcat can be found in Google play LINK Any one of these apps will work. It is recomended to use one with a good rating. YouTube also has step by step directions on how to use many logcat apps
[SIZE=+1]Q14: What does odexed and de-odexed mean and what is the difference between the two?[/SIZE]Please read HERE
[SIZE=+1]Q15: What is a Nandroid backup?[/SIZE]A Nandroid backup is a complete backup of your entire current operating system. It backs up the NAND flash, (this is the hard drive of your device). A Nandroid backup can mean the difference when you install a custom rom or when you play with the roots of your device, and something goes wrong.
[SIZE=+1]Q16: How do I make a Nandroid Backup?[/SIZE]In order to make a Nandroid backup, you must have a custom recovery installed.
From your phone, enter recovery mode and look for the ‘backup and restore’ click on backup and wait a few minutes until the process is done. It is best to save your Nandroid backups on the external SD card or on the PC to avoid erasing it by mistake. Performing a back up will NOT back up your external sd card and unless you choose to format your external sdcard, this will remain a safe place for this back up
[SIZE=+1]Q17: How do I restore a Nandroid Backup?[/SIZE]Enter recovery mode again and look for the ‘backup and restore’. Select restore and everything should go back to normal in a few minutes.
If you choose the ‘Advanced Restore’ option, you can select which component of the backup to restore – like the boot, system, data or cache.
Reboot system. Your system is now restored and is exactly same as the time when the backup was made.
[SIZE=+1]Q18: What is CWM Recovery (ClockWorkMod Recovery) and TWRP (TeamWin Recovery Project)?[/SIZE]They are recovery program's that allows you to backup / restore a full or partial system backup of your device. They also allow you to install flashable .zip files; which is one of the primary installation methods for custom ROMs. They also provides other features such as cache and delvik wiping, battery reset, and other processes. If you are thinking about flashing custom ROMs or just want a really good backup program, it's strongly advised that you to install one of these.
[SIZE=+1]Q19: Why does my battery drain so quick?[/SIZE]Please see HERE for possible steps that can help
[SIZE=+1]Q20: What is "Bloatware" (Bloated Software)?[/SIZE]Bloatware is all of the extra software applications that come pre-installed on your device (in addition to vanilla Android)–it can include any kind of application but some of the most notable examples are carrier apps and/or trial apps that you have to pay for after a certain time to keep using it. At best these apps can simply be taking up space on your phone, or at worst it can be running in the background without your knowledge and drain your battery
[SIZE=+1]Q21: How do I remove "Bloatware"?[/SIZE]Important: You will require root for the following process
Start by making a backup of all apps in your recovery.
Next read this tutorial, How to remove bloatware on AT&T LG G3
[SIZE=+1]Q22: How do I block "OTA" (Over The Air updates)?[/SIZE]Please follow these simple steps found here
[SIZE=+1]Q23: What is the best rom for my phone?[/SIZE]While you can ask this as many times as you wish, the only answer is: the one that works best for you! A rule of thumb is to visit a several rom thread's and view what is happening within these rom's. Eventually viewing a few roms will cause the urge to try one that looks good to you.
[SIZE=+1]Q24 What is the MD5, and what does it do?[/SIZE]It ensures that file's are downloaded correct and complete, in order to avoid issues when installing/using it.
[SIZE=+1]Q25 What does the term "Bump" mean?[/SIZE]
thecubed said:
A new and easy way to sign boot images for most modern LG phones so they'll boot on any locked phone.
Bump an image once, and flash it to however many phones you please.
Click to expand...
Click to collapse
For a detailed explanation head over to here
Please feel free to offer additional questions w/ answers, you feel may be helpful to others.
** *** **
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A special thanks to everyone who contributed to the production of this FAQ
Coming from the nexus 5, these were some questions I had right away:
What does "Bumped" mean?
Can we root lollipop and if so, is it the same process? Do we still have to go back to kk to root?
Does anyone have the random dead spots in the digitizer where your touches aren't registered in certain spots for a while?
Great thread man
Sent from my LG-D850 using Tapatalk
DigitalUnderground said:
Coming from the nexus 5, these were some questions I had right away:
What does "Bumped" mean?
Can we root lollipop and if so, is it the same process? Do we still have to go back to kk to root?
Does anyone have the random dead spots in the digitizer where your touches aren't registered in certain spots for a while?
Great thread man
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
All done, except for "spots". I'm not aware of this issue on sock LG G3. If you have further info regarding this, I will gladly post what you find.
I just have a quick question Tony, after flashing a custom rom I plug the usb into my computer from the phone, and my computer doesn't recognize the phone anymore. I just want to drag and drop some music files, but how can I make the computer read the phone again ?
So far I've checked that Im on MTP
Thank you
koc88518 said:
I just have a quick question Tony, after flashing a custom rom I plug the usb into my computer from the phone, and my computer doesn't recognize the phone anymore. I just want to drag and drop some music files, but how can I make the computer read the phone again ?
So far I've checked that Im on MTP
Thank you
Click to expand...
Click to collapse
You should find this tutorial helpful~ [How to fix] Windows 8/8.1 is not detecting my LG G3 device
Unified development section
are we going to get a unified development section? there are just as many and most likely more roms that run on the d850 that are posted elsewhere because they run on multiple versions of the g3. i think it would be a great adition this forum and bring a bunch of new roms in.
is there a d850 stock rom that has hotspot enabaled
What is the procedure for roofing my lg g3 please
---------- Post added at 03:44 AM ---------- Previous post was at 03:40 AM ----------
I am a noob
hi
how can install twrp un order to install custom ROM on LG g3 d855 kitkat 10n rooted with this method https://forum.xda-developers.com/lg...t-lg-firmwares-kitkat-lollipop-t3056951/page5
DISCLAIMER: I do not own/build this ROM, This is not my work. I am posting this thread to help other Lenovo A760 users.
How to Install CM13 (Cyanogenmod 13) UNOFFICIAL 6.0.1 Marshmallow on Lenovo A760
***** Android Rooting/Modifying Disclaimer *****
You are making these modifications to your device. I am not responsible for whatever happens to your phone, shall this process fail. You understand that I cannot be held responsible if you do not follow directions and brick your device. You are the only person responsible if you brick your device, as you are the one choosing to modify your device. You are voiding your warranty by rooting, making modifications, and install custom roms. I encourage you to READ CAREFULLY before following along and continuing to void your warranty. A fair knowledge of ADB and ROM flashing might be needed . You have been warned! Not following directions CAN result in a soft or hard brick. Thank you for if you read all of this!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Known Bugs:
- No FM Radio
- Screen Recorder app causing phone to reboot (please do not use the app)
(All the links for download will be available at the end of these steps)
Step 1
Download cm-13.0-20160502-UNOFFICIAL-audi.zip and A-GAPPS 6.0.1.zip and save it under root directory in your phone's SD Card.
WARNING!! Step 4 to Step 9 will erase your Internal Storage. PLEASE BACKUP of all your files in Internal Storage (NOT SD Card) before proceed further!!
Step 2
Download the Qualcomm QPST zip, and install it on your Computer. (You may restart the computer after finished installation to make sure the driver is in effect)
Step 3
Power off your phone, take the battery out. Connect it with USB cable to the computer.
Step 4
Press & Hold (Vol +), (Vol -) & (Power Button) while its connected to your computer until you feel its vibrate 2x times. (check at the computer taskbar and see if device called Qualcomm CDMA Technologies MSM connected) DO NOT press FORMAT/ERASE drive if your computer prompt it. Just click cancel if the message appear.
Step 5
Download the HDD Raw Copy Tool and double click it to execute the application. You can now see 'Qualcomm MMC Storage' shown in the software.
Step 6
Download Lenovo_A760.imgc. Under the 'Qualcomm MMC Storage' line, there is another 'FILE' line, double click the line and select your downloaded Lenovo_A760.imgc
Step 7
Once your Lenovo_A760.imgc selected, it will display 'Please select TARGET' message. Click the 'Qualcomm MMC Storage' line and click the Continue>> button
Step 8
Click START and confirm to continue the process. This will take up to 20minutes.
Step 9
Once it shows 100% complete, you may remove the phone from USB cable, and insert back the battery. DO NOT power it on yet.
Step 10
Press & Hold (Vol +), (Vol -) & (Power Button) to go to Recovery Mode. Once you are in TWRP recovery, press ‘Wipe’, and swipe to proceed wipe/factory reset.
Step 11
Press 'Install' and select your cm-13.0-20160502-UNOFFICIAL-audi.zip.
Swipe to Install your zip. Press ‘Reboot system’ at the bottom.
Voila! you will be greeted with Cyanogenmod Boot Animation. Please proceed with the necessary steps to setup your phone for first time.
Step 13
Once booted up, go to Settings, scroll down until ‘About phone’. Tap on ‘Build Number’ for few times until a message appear: ‘You have enabled development settings!’.
Step 14
Go back once, and tap on ‘Developer options’. Turn on ‘Advanced reboot’ in Developer options, and scroll down a bit to set ‘Root access’ to ‘Apps and ADB’.
The following steps are only for those of you who want to install Google Apps:
Step 15
Press & Hold the Power button, select Reboot, and then select ‘Recovery’
Step 16
In the Recovery, press 'Install' and select your A-GAPPS 6.0.1.zip. Swipe to Install your zip. Once finished, just Press the ‘Wipe dalvik/cache’ button at bottom. After that, press ‘Reboot system’ again.
If your google Contacts does not sync, download the 'Google Contact Sync 6.0.1' apk and install & replace the current version in your phone.
Click to expand...
Click to collapse
If you are facing the ‘Unfortunately Setup Wizard Has Stopped’ or ‘Unfortunately Google Play Services Has Stopped’ errors, you may follow this steps:
For Setup Wizard, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Setup Wizard’ > (Press i in the circle) > ‘Permissions’ > Turn on the options for ‘Contacts’ & “Phone’
For Google Play services, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Google Play services’ > (Press i in the circle) > ‘Permissions’ > Turn on all the options
Download links
Qualcomm QPST: http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051
HDD Raw Copy Tool: http://viid.me/q0YITi
Lenovo_A760.imgc: http://viid.me/q0YH1w
Download CM13 Unofficial: http://viid.me/q0I8UI
Google Apps for Android 6.0: http://viid.me/q0I6nC
Google Contact Sync 6.0.1: http://viid.me/q0HCDh
--------- PLEASE SUBSCRIBE TO MY YOUTUBE ---------
Please Subscribe: https://goo.gl/Mr3YMF
Visit my website: http://tekmastah.blogspot.com
Credits
• Vlad Den from Youtube for HDD RAW Copy flash guide: https://goo.gl/i6bK9k
• Weritos from 4pda.ru forum for Cyanogenmod 13 UNOFFICIAL Rom: https://goo.gl/NdYfuS
• A-TEAM from XDA developers forum for Gapps: https://goo.gl/7A6kyX
• ZENELKA MILKO from Lenovo A706 Indonesia FB Group: https://goo.gl/wFKOsZ
• APKMirror for Google Contact Sync: https://goo.gl/mRJH8y
Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack
jachol said:
Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack
Click to expand...
Click to collapse
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!
mellomade said:
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!
Click to expand...
Click to collapse
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack
jachol said:
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack
Click to expand...
Click to collapse
Great! Actually, Starting from lollipop, rom installs require larger internal space. Since we barely have sufficient space for system on our A760, the internal storage needs to be repartition (done by HDD Raw copy tool). Luckily the provided image 'Lenovo_A760.imgc' will automatically install the updated recovery TWRP 2.8.7 (compatible for the rom install) so we dont have to.
I do think others from the old thread already shifted to other phones
The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks
astudent said:
The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks
Click to expand...
Click to collapse
I have updated with new download link (now its working). Sorry for the ads. You can click the 'Skip the ad' button after waiting for 5 seconds, or you can Google Qualcomm QPST if you prefer not to click it.
GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.
jachol said:
GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.
Click to expand...
Click to collapse
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:
mellomade said:
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:
Click to expand...
Click to collapse
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:
jachol said:
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:
Click to expand...
Click to collapse
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob
mellomade said:
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob
Click to expand...
Click to collapse
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.
jachol said:
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.
Click to expand...
Click to collapse
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.
mellomade said:
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.
Click to expand...
Click to collapse
Ah yes !, gotcha now ... total misunderstanding this end, and yes I've installed greenify, it helps a lot. Thanks again. ... J.
Can you please give a device tree of this rom.I really need it.
Multiple submition by mistake - please go here
THIS IS YOUR FIRST WARNING (WILL BE REITERATED PLENTY OF TIMES!) IN BIG RED BOLD LETTERS - THESE FILES ARE FROM/FOR THE USA ("XAR") REGION, SM-P610 WIFI MODEL ONLY!
(with the exception of the Odin utility, as well as possibly the modified boot splash screen, which may work on other variants, though untested and done solely at your own risk - read all the notes!!)
I already went through the work, so I figured I would share these files for those who also own the same exact tablet. Again, it's for the USA/XAR region Samsung Galaxy Tab S6 Lite WiFi Model ONLY - "SM-P610" / "gta4xlwifi". LTE model is a different variant; do NOT flash the stock firmware files to that device! Also, sorry, I will not support or answer questions for other variants (other than what I will mention in this OP). Downloading firmwares for other variants will be a huge PITA, and I don't have / pay for any "premium" accounts which would allow me to quickly download the huge firmware files. I'm only sharing these I'm posting because I already took the time to acquire and archive them for personal usage, and might as well share them for those who own the same device / variant.
Use these files at your own risk, and only flash if you know what you're doing!! I'm not responsible for any problems user may incur from usage of these files, the usual warnings apply, etc. This device is just a backup / playaround device for me, and so it doesn't get daily usage out of me, nor will I likely be very active on this subforum (sorry! just being honest). Also, I immediately installed LOS on my device anyway, so I don't run stock ROM myself and therefore won't be sharing pre-patched Magisk boot images either. Sorry to those who are used to that from me =)
So anyway... what's in this post?
Odin3 v3.14.4 (version I've been using on this device, and working perfectly fine as of this initial posting)
Stock firmware zips for USA/"XAR" Region SM-P610, WiFi Only
Modified BL file (Odin-flashable), to remove the warning boot text
Odin3 v3.14.4:
I posted this in another thread, but figured I would also link to it here so it's easy to find in one place. This worked perfectly fine for me to root / install TWRP / flash BL files, etc.
Download Link: https://www.androidfilehost.com/?fid=10763459528675582443
Stock Firmware Files:
USA/XAR WIFI ONLY! October 2020 Update - Firmware Version P610XXU2BTJ5
Download Link: https://www.androidfilehost.com/?fid=10763459528675592742
USA/XAR WIFI ONLY! September 2020 Update - Firmware Version P610XXU2BTI3
Download Link: https://www.androidfilehost.com/?fid=10763459528675592159
Firmware files for other variants, see this post. Follow the links, use the resources, consider the context for other variants: https://forum.xda-developers.com/showpost.php?p=83083249&postcount=2
Modified [BL-slot] Odin-Flashable File To Remove Warning Splash Screen Text:
My Thoughts On This...After unlocking the bootloader and flashing non-stock images, we all know we end up with that annoying, ugly splash screen screaming that the device is modified. Most of us modifying our devices understand the security implications involved, and ironically choose to modify our devices to increase security in other ways. Yet, these warning splash screens, in the unfortunate event of possible theft, may very well end up being the reason a more tech-savvy thief is able to break into the device, or find someone who can. So, thanks to users' posts Awesomeslayerg's hint and blascogm's guide, I quickly came up with an Odin-flashable file to change the splash screen, as seen below:
(if the pic doesn't show, probably the imgur link I used is dead, but I also attached it to this post)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know some people may be thinking "why not just remove the PRESS POWER KEY TO CONTINUE line completely and have it stay at the normal boot screen seamlessly the whole time", and the reason I decided not to do this is because it generally wouldn't make the average person suspect the device is modified, and it's still good for us to know that it's at the boot stage where we can hit the power key to skip the ~10 second timeout. It's exactly the same image, so it's still very seamless and stock-like. I even took the time to center the power key text exactly, by the pixel, from left to right and from top bottom relative to the knox and android logos.. ; )
And if it really bothers you that much, follow the guide I linked above and do it yourself. =)
I should also mention that, for our devices, the .bin.lz4 file that needs to be decrypted is actually "up_param.bin.lz4" and not "param.bin.lz4" as suggested in the guide, as it's for a different device. You will need the lz4 utility (check Awesomeslayerg's thread, or google lz4 github) to decrypt the lz4 file to a regular bin file, and then you can extract and/or replace the .jpg files using an archiver program (I recommend 7-zip for this).
The hash checksums for every single file/jpg in each up_param.bin were identical between the September and October firmwares. Therefore, at least as of this posting, the same modified Odin-flashable file will work on either firmware version, and likely future versions until they make any significant changes. I did test this myself too btw. Also, if you look at the structure and contents of the up_param.bin file for yourself, you'll see that they are simply .jpg files containing the screens, backgrounds, and text you're all familiar with when going into bootloader / download mode. Assuming they follow the same file naming structure, I suspect you can probably flash this to other variants, although it will change the text language to English (assuming they localize the bootloader / download mode text per every region; I have no idea about this as I only own US variants). To see what I'm talking about, here's a quick screenshot (better resolution pic, and just in case imgur link dies, also attached to this post):
Now that I (hopefully) tricked you into reading this entire section so that you now have some basic understanding of how it works before proceeding to flashing the warning text removal mod, here are the instructions / link for install:
- Download the .tar file provided below.
- Boot device into Download mode.
- Place .tar file into bootloader [BL] slot in Odin and flash.
Download Link: https://www.androidfilehost.com/?fid=10763459528675592179
To revert back to stock splash screen with warning text, for whatever reason:
Pull the stock up_param.bin.lz4 from the stock firmware file (from the BL****.md5 file within the firmware zip).
- Convert it to up_param.bin uzing lz4 utility.
- Add up_param.bin to an archive as .tar file, uncompressed (recommend using 7-zip).
- Flash the .tar file, which should contain only the stock decrypted up_param.bin file, in Download mode using Odin in the BL slot.
I uploaded my custom jpg's, as well as the stock untouched jpg's, for those that are curious or want to edit them further. Feel free to snag them here: https://www.androidfilehost.com/?w=files&flid=320350
* As we can see, we're only modifying the .jpg files provided by up_param.bin, so it's a relatively harmless process (unlike modifying aboot files in the old days of HTC devices, which if done improperly could literally result in an unrecoverable brick). But even so, please only flash if you know what you're doing and can recover from any potential mistakes or errors.
Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609
And another
Hi,
Thanks for these resources. I'm actually not at these steps yet. I'm having trouble gaining access to the OEM Bootloader Unlock option in developer options. Here are things I've tried already based on what I researched before my attempt.
Android 10 is the current OS installed after unboxing.
1. Disable Automatic Date and time
2. Select a date more than 7 days prior to current date of attempt.
3. Under Settings > About Phone > Software Information. Select/Tap Build Number 7-8 times to unlock Developer Option.
4. Disable Auto Update System (Apply Updates When Device Restarts) - *This was somehow already disabled the first time I entered Developer options*
5. Under Software Updates > Disable Automatic Updates -*This was also already disabled on unboxing and it says Automatically download updates over Wifi. It does not say Automatic Updates*
6. Reboot device and return to Developer Options after booting to OS.
7. The OEM Bootloader Unlock option should appear greyed out at this point. Toggle it to unlock bootloader with consideration that it will wipe the device data.
These are the steps I've found and tried with no success in gaining access to the Bootloader unlock option. I am also certain that my device is the international model SM-P610 with Exynos chipset and Mali-G72 GPU. Something else to note, I did uncheck many default options tied to improving privacy on the device before attempting the steps to gain access to the bootloader unlock option. I do not know if that would make a difference. If you recognize anything wrong with the steps I've tried already, please let me know where I'm going wrong or where I can find the correct way to unlock the bootloader. I've been posting in other threads, but nobody seems to be replying to me. Any help will be appreciated.
Hi
I've flashed your modded file on my PHN (Netherlands), no problems at all working ootb!
Hi. I used blascogm's guide for my P615 with latest firmware for SEC UI 3.1and all are OK! Thanks for all.
Add. I add link . Flash via Odin(BL).
https://androidfilehost.com/?fid=14943124697586347282
i5lee8bit said:
Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609
Click to expand...
Click to collapse
I flashed ths when I'm running lineageos 18.1 annd this is the only mod that worked for me
Thanks for posting your images and linking to the guide, worked perfectly and the images just fit to the pixel <3
Confirmed working as of March 2022. Device is running base P610XXU2DUL9. Thanks for the hard work.
can you make one for SM-P613 model plz?