[Q] Discussion about LG G3 android system topic

Hi to all of you. I recently did buy a LG G3 with KitKat 4.4.2. Phone is awesome, battery lasts a lot for this screen over a day and a half (medium usage), without lagginess, maybe after restart it takes about 1 second to find everything but generally i am very happy with my purchcase. I have some questions though. Recently i got a OTA update about sth vcalled 20e. Its an update ~555mb and after some search i found out that this is the Lollipop official firmware. After plugging my phone into the LG PC Suite, i found out that even a newer version is available the 20f firmware ~over 1gb. Here starts my questions. Is it worth to go from kitkat to jellybean? Or is it better to stick with kitkat until they fix all the bugs i found out on forums. (So far i saw battery doesnt last so long, wireless charging has problems, lte doesnt work on most devices, others said about lagginess, most apps do not work with the new ART system). So what are your thoughts about this? Also i want to remove some google apps like google drive, and i want to remove this McAfee. Is there any possible way to do that easily without ruining my phone?

By: dd On 06:08

Continue Reading

[Discussion] Xposed Framework topic

We will use this thread for discussion regarding Xposed

Quote:

Originally Posted by superstone (Post 54613886) Steps to Install Xposed 1.) Install newest Java JDK on the computer and link the installation path with the Win system / user variables. (see http://forum.xda-developers.com/show....php?t=2374008 Post#9) 2.) Install Android SDK. Be sure that the correct repositories for your Android Versions are also installed. If not install (e.g. for my Android 4.2.2. Version i needed all API 17 resources...) 3.) Use a specially modified Tool Chain with adjusted smali/baksmali for the MTK MT6592 / Alyiun OS called "Ureal-Deodexer". See https://code.google.com/p/smali/issues/detail?id=199 (use DL-Link in Post#16) 4.) after deodexing apks and framework put it onto the phone via Android.SDK. (see e.g. http://forum.xda-developers.com/show....php?t=2374008 Post#1 how to do this) 5.) after that modify /system/build.prop by adding a line with Code: dalvik.vm.execution-mode=int:fast . 6.) reboot the phone (now deodexed rom needs quite a while for the first startup....) 7.) be sure that all .jex files and .odex files are removed from /system/app and /system/framework. (i did it with a file explorer with root access for /system directly on the phone) Reebot again in case you have to delete. 8.) now u can install Xposed Framework and all your favorite Xposed modules. Try on your own risk.....

By: dd On 03:11

Continue Reading

lollipop root on G900A discussion topic

On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?

So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.

If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?

I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.

By: dd On 21:36

Continue Reading

[Discussion] Nexus 6 Underclocking topic

I know that on all my phones I underclock them to be able to conserve as much battery life as I can. I was wanting to know how many other people underclock this device and what are the setups they are using? I, for example, am using LiquidSmooth v4 Nightly 12/23 and Sensei Kernel R26.1 underclocked at a max frequency of 1.1GHz. I have CPU hotplugging enabled and only use 2 cores.

By: dd On 20:05

Continue Reading

Surface Pro 3 WIMBoot ROM + guide + discussion topic

TEST BUILDS:

December build [please search in surfaceforums, as I couldn't post links here]
(for next uploads, which one do you recommend: Box sync, Google Drive, MEGA, or OneDrive?)


Features:
1. Only 1.2 GB footprint on C: drive (54 GB free out of 55.2 GB C: drive on the 64 GB model. Free space increases accordingly on larger models) excluding hibernation and pagefile
2. August, September, October, November, and December update rollups slipstreamed
3. Surface Pro 3 specific updates included (KB2978002, KB2969817)
4. Bloat free with about 3 GB saving: (Microsoft devices are shipped bloat-free? Think again)
- Only 6 metro apps included (Camera, IE, OneDrive, PC Settings, Photos, Store). The rest can be downloaded from Store
- Trial Office removed
- Speech data removed (who uses that anyway?)
5. Pen Pairing OOBE appears and working
6. Languages included: Dutch, English, German, French. Since it is Windows 8 Pro, you can download any other language later.
7. WinRE from vanilla Windows, 200 MB saving (working so far, please report if something wrong happened)


I have been using this build for 2 days, as well as the previous, similar build for a week. No issues experienced from my side.


This *might* also work on the Surface Pro 2 since they have similar components. Not tested.






How to install:
0. Get a keyboard and USB hub (Type Cover might also work, but I don't have one to test)
1. Download and extract the package with WinRAR
2. Set up the ISO image on a CD or USB stick.
- If you use Rufus, set it on "MBR for UEFI computer" (only for the USB stick, the Surface will be set up as GPT)
3. Boot it on the Surface
4. Enter cd /d D:\scripts
5. Enter diskpart /s part43.txt (part43.txt means the recovery partition is 4300MB. I tried 4200MB, it didn't work)
6. Enter applywim D:\Images\install.wim D:\Images\winre.wim
7. You can repeat the step #6 just to be sure
8. Reboot, unplug the USB stick.





____________GUIDE____________

First of all, I would like to thank murphy78 from mydigitallife.info forum for creating the noob-friendly guide for creating WIMBoot image (friendlier than Microsoft's version, at least).

Here I tried doing it using Surface Pro 3's recovery image instead of clean Windows which is used on his/her guide. I recommend this especially for 64 GB model users, or if you want to deploy 64 GB Surface Pro 3s. 128 GB users can benefit too.

I don't really recommend this for 256 or 512 GB SP3s, since the additional free space is not worth the effort IMO (of course, youre free to do it, its YOUR SP3, after all).

(I copied most of the steps from murphy78's, unless changes are necessary)


(use elevated cmd when necessary)
Preparing the Windows PE files (only for applying the image, NOT installed on the SP3)

1. Run the ADK commandline shortcut from start menu


2. Run the following command: copype amd64 c:\WINPE_AMD64


3. Mount the boot.wim from c:\WinPE_AMD64\media\sources\ and add the update msu packages


4. Extract the 7z from the link in this post to the c:\winpe_amd64\media\Scripts folder (create folder if you need to)

Preparing the WIM image to be applied
(Surface Pro 3 has Windows 8.1 Update 1 included. If youre doing this on the Surface Pro or Pro 2, you might need to update it.)

1. Download SurfacePro3_BMR_20_3.4.1.zip recovery image from the official site


2. Copy install.swm, install2.swm, and install3.swm from SurfacePro3_BMR_20_3.4.1\sources\ to \Deployment Tools\amd64\DISM\ where imagex.exe resides (inside ADK)


3. Open cmd in that directory and run the following command:
   imagex /ref install*.swm /check /export install.swm * install.wim "SurfacePro3"


4. Mount the WIM image using the following command, change the directory if necessary
   Dism /Mount-Image /ImageFile:"C:\SurfacePro3_BMR_20_3.4.1\sources\ins tall.wim" /Index:1 /MountDir:C:\mount\


5. Move the winre.wim from the windows\system32\recovery\ folder to c:\winpe_amd64\media\Images\ (might need to turn on see system files)


6. Remove the system file attribute by running: attrib –s -h c:\winpe_amd64\media\images\winre.wim


7. Optimize the image for WIMboot using the following command:
   Dism /Optimize-Image /Image:C:\mount\ /WIMBoot


8. Capture the optimized image using the following command: DISM /Capture-Image /WIMBoot /ImageFile:" C:\WINPE_AMD64\media\Images\install.wim" /CaptureDir:C:\mount\ /Name:"SurfacePro3_WIMBoot"
   (create folder if needed)

Creating the WIMBoot ISO

1. Move the captured install.wim to c:\winpe_amd64\media\Images


2. Edit the partition size in D:\scripts\CreatePartitions-WIMBoot.txt. It is the combination of install.wim and winre.wim + 50 MB (no idea why, it refuses to copy the Windows RE image if I didn't give 50 MB additional space)
   The row to be edited is “shrink minimum=xxxx”


3. Create your wimboot iso by running the following oscdimg command in a directory with oscdimg (I use e:\waik5\amd64\)
   E:\waik5\amd64\oscdimg.exe -u1 -be:\waik5\amd64\efisys.bin -pEF -bootdata:2#p0,e,be:\waik5\amd64\etfsboot.com#pEF,e ,be:\waik5\amd64\efisys.bin c:\winpe_amd64\media\ c:\temp\WinPE_5.1_AMD64.iso

Now, move to the SP3

1. Boot from the iso
   (I do recommend to this on a VM first before messing with your SP3. Make sure your VM supports virtual SSD and EFI firmware)


2. Navigate to the disk's scripts folder in the winpe command prompt. For me it was cd /d D:\scripts\


3. (If you click on the command prompt at any time and it seems to pause, just press enter and it will come back to life - learned hard way on vm)


4. Run from the scripts folder: diskpart /s CreatePartitions-WIMBoot.txt


5. After the diskpart script is done run: ApplyWimBootImage d:\Images\install.wim d:\Images\winre.wim


6. And then just reboot and let the system finish setup. You can powerdown at the user creation screen if you are setting this up for a customer. (At least it says it's safe in the chm file)

By: dd On 09:41

Continue Reading

[Discussion] Moto G XT1032 - GPE Converted Lollipop topic

So yeah, I've successfully converted my XT1032 to GPE and updated it to Lollipop. In fact I didn't have to spend a lot of time in Fastboot as a lot of those guides out there would have you do. Just flashed the 4.4.4 GPE and then once it loaded it asked if I wanted to upgrade. So I don't know about other XT1032 users but I thought it was fairly painless.




One thing of note if your planning to root, this is the method I did it. http://autoroot.chainfire.eu/. Now just so you know that list doesn't have the new Lollipop versions I used Google and to find the post with them. Just make sure you turn off, "Mount namespace separation". I found it was giving me some trouble. I also ended up installing SuperUser into /system and after that my root issue disappeared.

During the whole thing I had my SIM out (I have to pay for data, I'm with Koodo Mobile). Once it was done installing the updates (software and everything) I put it back in and the phone asked to reboot. Everything seems to be working and I turned data off so I wouldn't use it.

Anyone else with a XT1032, having any difficulties with this?

By: dd On 22:46

Continue Reading

Seems a for place a brick discussion? topic

Have you got this phone in brick status and can't get a fix? ME TOO! I hope everyone with a brick of any type will come here and tell us how youbfixed it. Or ask how to fix. This is mostly for the optics l90 so please respect the tone! Hope this works.

By: dd On 18:12

Continue Reading

Discussion : XT1033 Brazil Firmware [ 5.0 ] Lollipop topic

Let's discuss about Brazil firmware here.

Some of the things i noticed.
1. Moto has sticked to it's own launcher with black background on app drawer.
2. Nothing much changed other than the launcher.
3. No you can't downgrade to Kitkat.
4. There is no Xposed Framework dedicated for Lollipop as of now
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
To install Brazil Lollipop Firmware,
1. Link 1 ,Link 2 or Link 3. I used Link 1 it's pretty clear and Noob friendly

Read this before proceeding

If you face any issues follow this

Thanks to respective OPs :)

By: dd On 22:38

Continue Reading