Search results

Updated the guide to show steps to properly use Kingroot to root successfully.

I have read some conflicting posts about the Boost mobile model. Do you know if fastboot oem unlock works on the Boost mobile variant?

I will add a warning saying Kingroot is still really unstable. I have not tried it as I do not want to have to go theough the process as it would take at least a hour or two to fully test it and restore a backup of my current set up. Sent from my LG-H631 using Tapatalk

Well unless you or someone else can find a exploit that will achieve root. Then this is the best way. This is the same way you root nexus devices and since it is Android 6.p the is being rooted by the SuperSU.zip then it is a systemless root also. I have got to be honest here and I am not trying...

Oh so you flashed back to complete stock using t2hw kdz file. Since you did that you will have to start all over again. Which means you will have to fastboot oem unlock again as the kdz file relocked your bootloader. If you follow the steps in the guide you should be fine. Just make sure to have...

It almost sounds like you did the fastboot oem unlock command after you flashed the SuperSU.zip. But from the feed back I am getting I would think that was not possible as users have said they had to fastboot oem unlock to get recovery to boot. Anyway the fastboot oem unlock is what factory...

This would not work because you still would need root to push thesu binaries to system/bin. Now it might be worth trying that while you have TWRP installed as it has access to the system and has root. But if you need to use the TWRP to beable to push the su binaries why noy just flash the zip...

Hmmm looks like maybe fully unlocking the bootloader enables all fastboot commands. You can try downloading and installing Kingroot and root with it as the posts here comfirm it will root the update now. Or just u lock the bootloaderb but your device will be reset if you do.

Are you trying to use the fastboot boot recovery.img command?

My apologies as I made a typo in the guide. The correct command is "fastboot flash recovery recovery.img" to flash the recovery. I will fix this along with another rework about putting the SusperSU.zip only on your SD card. I do not know if you can use it or not as I do not have that device...

Resserved in case needed later.

This guide was made before Kingroot was able to root the official update. But thanks to oskar and TheDerekHarper on XDA and to josephwv on Android forums it is now comfirmed that Kingroot will root the official update. But first you must still follow steps #1 through #6 so Kingroot can root your...

Finally Official Android 6.0 It is finally here. The Official Android 6.0 update for the LG G Stylo for T-Mobile and Metro PCS. Android Police article here.

How so I know developers that have samsung devices and the make recoveryimage command works fine for them.

Use this command to just make recovery. Replace "devicename" with your device name. . build/envsetup.sh && lunch cm_devicename-userdebug && make recoveryimage if your are building with cm. . build/envsetup.sh && lunch omni_devicename-userdebug && make recoveryimage if you are building with omni.

No disrespect, bit did you compile this? I ask cause I am trying to compile the new TWRP for my device wich is a LG G Stylo and my touch input does not work. So I was wondering if you had this issue and if so how did you fix it?

Just to set the record straight here Hello all I am Tony Roach the mod of the G+ community that Totaltelecom is complaining about. The Unofficial XDA G+ community was started several years ago by Debadatta Bose who is a recognized contributor here on the XDA Forums. I can not remember his user...

I understand what you are saying. But all of us with knowledge of building Android, and building recovery is part of that, should be willing to help out where and when we can. That is what a community is about. And do we not all concider ourselfs part of the Android community. Plus that is also...

I hope they don't clean the posts. I mean have you ever tried googling for fixes to build errors? The more answers that are out there the better. T-Macgnolia on Tapatalk

Look in your devices vendor folder and see if you have libcamera_client.so. if not add it to you vendor and to the vendor-blobs.mk and your Android.mk in your vendor. T-Macgnolia on Tapatalk

Sounds like a vendor issue to me. T-Macgnolia on Tapatalk

Sorry but I still don't understand what you mean by, "I edited the BoardConfig.mk so it's unified with CDMA." Are you talking about the TARGET_OTA_ASSERT_DEVICE line in your BoardConfig.mk? I myself have never liked the idea of a unified device tree as it tends to create problems. Also where did...

No the files I was talking about are for APN's. What file are you talking about and where did you make your change. T-Macgnolia on Tapatalk

That may be it but I am not sure. But just for further knowledge the gsm.mk has been unified to work for CDMA and GSM devices. The cdma.mk is obsolete now that is why all devices call the gsm.mk files in their configuration. T-Macgnolia on Tapatalk

Amazing how your suggestion did not work like I already new it wouldn't. Also amazing how someone trys to help spread knowledge and then someone gets all butt hurt cause the feel like someone was teying to be little them when they were actually trying to help educate them. People like you have...

No you are that person. I havebeen doing ROM development for over 4 years now. I know exactly what I am talking about. Yes the updater script has. A check in the begining but it is to check against the device that the recovery was built for. Or in other words the ro.product.device that was...

LMAO I swear some people crack me up. T-Macgnolia on Tapatalk

Yeah I saw it was a unified build frome the screen shot. And I say the last device listed was klte. Your recovery doesn't like something in your META-IF folder. I would compare all the files in that folder with the ones from a ROM that flashed successfully. T-Macgnolia on Tapatalk

It is not the updater-script that does the checks. The checks are built into the recovery. The updater-script just prevides the info for the recovery to check against what device info was built into it. T-Macgnolia on Tapatalk

You need to edit your updater-script to only show klte as the message says your recovery is for klte. T-Macgnolia on Tapatalk

Remove the fstab from your common folder and then look in the BoardConfigCommon.mk of your common folder and see if you have TARGET_RECOVERY_FSTAB defined there. If so remove it and then define it in your device folder BoardConfig.mk T-Macgnolia on Tapatalk

Yes there is a CM 12.1 build for the device. But I am not sure of other builds are going to be possible as I have been working on building a different ROM for this device and also a android 6.0 build but nothing is booting so far. Real pain to be honest. T-Macgnolia on Tapatalk

Look at the error message. It gives you two file directories to look in and the line number in the file that is causing issue. The first time it gives . bootable/recovery/miniuitwrp/events.c line #19 And bionic/libc/include/fcntl.h line #43 The second time it gives you...

Compare the file in bionic with the same fike in CM and you should be able to fimd where you multiple definition is. I had a simmiliar error in bionic. T-Macgnolia on Tapatalk

Is it a ROM spacific mod? I use CM our XenonHD. T-Macgnolia on Tapatalk

Does anyone have a working link to download the D618 zip?

Your problem is uou do not have a AndroidProducts.mk file in your divce folder. You need to create one, just look in the Omnirom github at how they have it. It is a very simple file with only one line. Also do not worry about the no omni.dependencies file. That is just a file that roomservice...

I can get CM 13 to build using the current repos(screenshot provided as proof) but it does not even give a boot animation so I can not pull a log to try and go further. I am really thinking the issue is in the init scripts but that is the obvious starting point. I have been trying to use the...

What you did to add the led.sh works but the vendor/lge folder is really for pulling in the needed blobs(prorietary) files for the device. You should really add it in in your device tree. In device/lge/h631 you could make a folder named "etc" and then inside the etc folder make another folder...

Ok first off there is no need to be ugly and curse at someone. In fact it is against the XDA rules. I use to be a mod on here so I am very familiar with the rules So I would like a apology or I will be reporting your post. We can be civil just as I was very civil with you in my post...

I have not checked on this thread in a couple of days as I have been busy working on developing another kernel source for the Stylo based off of cm's msm8916 kernel which I will be trying to build now that I am at a point I can try to build with it. So I am going to respond to posts in the order...

I did notice in the dmesg this. qcom,mdss_dsi_lgd_incell_phase3_hd_video:1:none so I am not sure if it will still not have to be fixed in the kernel

I believe the camcorder issue may lay in one of these two things I found in the log. I am also goingto flash again and pull the last_ksmg,txt to look at it also. I/CAM_Config( 4163): no local config found for g4stylusn_tmo_us W/CyanogenAmbientUtil( 4163): Cyanogen Ambient is missing...

Well I saw that camera was listed as not working in the OP. Plus there is no camera app included in the ROM. ---------- Post added at 06:07 PM ---------- Previous post was at 05:56 PM ---------- I have no issue with it as this is not my build, I am just offering help with it. Also you do...

As far as I know it is.

I flashed your build on my device and within 30 minutes had the camera and GPS fixed. I know what your issue is because I pulled the blob files from your build to try and use with mine as I pulled all mine from a stock rom. The below is the output I hadwhen pulling the files which lead me to the...

Have you tried to plug your device up to your computer and then power it on to see if it will boot to download mode that way?

Can you link me to Riku's repositories that you are working with?

Looking for info Are you using the device repos posted on TeamRegular's github account or do you have your own device repos you are using? If you have your own device tree repos are they on github? I ask this because I am working on building XenonHD for the h631. I currently have it booting to...

Update on Kingroot I have not read through the whole thread to see if it has been mentioned. But seeing as it is not in the OP I wanted to post and say that KingRoot now works on the stock 5.1.1 ROM. I am running stock build LMY47V Software version h63110j as you can see from my attached...