Develop Bugs

Problem solved! Low battery warning on LG Mobile Tool

Problem solved! Low battery warning on LG Mobile Tool
1. Uninstall LG flash tool , LG Mobile Tool , lg drivers and msxml in your control panel or delete their folder
2. Install everything again ( tested on windows 8 and 8.1 i fixed my phone.. yey)
3. and follow these instructions http://forum.xda-developers.com/showthread.php?t=2420219 and tadaaa your phone is working
Hit Thanks if this helps ) Finally i fixed my phone 9:58am 2/28/14 Philippine Time

Mr.Gabo said:
Problem solved! Low battery warning on LG Mobile Tool
1. Uninstall LG flash tool , LG Mobile Tool , lg drivers and msxml in your control panel or delete their folder
2. Install everything again ( tested on windows 8 and 8.1 i fixed my phone.. yey)
3. and follow these instructions http://forum.xda-developers.com/showthread.php?t=2420219 and tadaaa your phone is working
Hit Thanks if this helps ) Finally i fixed my phone 9:58am 2/28/14 Philippine Time
Click to expand...
Click to collapse
thank you very much
I've tried, but still gives me error low battery, I have ls CM ROM, it may be that the problem?

amilio said:
thank you very much
I've tried, but still gives me error low battery, I have ls CM ROM, it may be that the problem?
Click to expand...
Click to collapse
try flashing using lg flashtool and download the tot file for your device. this might work to you. extract the dll in your latest kdz.

Mr.Gabo said:
try flashing using lg flashtool and download the tot file for your device. this might work to you. extract the dll in your latest kdz.
Click to expand...
Click to collapse
Hello, I could not install anything, you can only enter TWRP, and have nothing in memory, as can be done to install a rom Stock?

amilio said:
Hello, I could not install anything, you can only enter TWRP, and have nothing in memory, as can be done to install a rom Stock?
Click to expand...
Click to collapse
Flash using download mode

Mr.Gabo said:
try flashing using lg flashtool and download the tot file for your device. this might work to you. extract the dll in your latest kdz.
Click to expand...
Click to collapse
As far as I know .tot.files are only available for at&t models.
For other g-pro models, there are no freely available flashtools.
"lg support tool" (with the .kdz.loader "uptest.exe") seems only to be safe with a locked bootloader on the phone.
Would be nice to make sure g-pro owners get to know that, before they have costly experiences with their phones.

xifizurk said:
As far as I know tot. files are only available for at&t models.
For other g pro models, there are no freely available flashtools.
"lg support tool" (with the kdz.loader "uptest.exe") seems only to be safe with a locked bootloader on the phone.
Would be nice to make sure lg g pro owners get to know that, before they have costly experiences with their phones.
Click to expand...
Click to collapse
There are also f240's tot file and e988 i saw it on one of the thread i read.
Reading is always the key to success

xifizurk said:
As far as I know tot. files are only available for at&t models.
For other g pro models, there are no freely available flashtools.
"lg support tool" (with the kdz.loader "uptest.exe") seems only to be safe with a locked bootloader on the phone.
Would be nice to make sure lg g pro owners get to know that, before they have costly experiences with their phones.
Click to expand...
Click to collapse
my bootloader is not locked, as can relocket? thanks

amilio said:
my bootloader is not locked, as can relocket? thanks
Click to expand...
Click to collapse
you can relock it by flashing kdz or tot via lg mobile tool or lg flash tool. done it many times and still counting

Mr.Gabo said:
you can relock it by flashing kdz or tot via lg mobile tool or lg flash tool. done it many times and still counting
Click to expand...
Click to collapse
what is going on here?
amilio just told us he isn`t able to flash!
already starting this thread with the misleading information!
this really gets down here to pure spamming!
why are you doing this???
nevertheless trying to give an answer:
TWRP has traditionally among its advanced tab features some sort of "adb" support.
on my other older android phone i could easily push zip files from pc to the phone.
This might be a way to go to get something to the phone that boots up or is close enough to stock firmware to be flashable with lg-support-tool

hello
thank you all, but I could not solve the problem, low battery error, and only enters TWPR, and I tried installing the CM, and error, which can not do.
thanks

xifizurk said:
what is going on here?
amilio just told us he isn`t able to flash!
already starting this thread with the misleading information
this gets realy down here to pure spamming!
why are you doing this???
nevertheless trying to give an answer:
TWRP has traditionally among its advanced tab features some sort of "adb" support.
on my other older android phone i could easily push zip files from pc to the phone.
This might be a way to go to get something to the phone that boots up or is close enough to stock firmware to be flashable with lg-support-tool
Click to expand...
Click to collapse
pure spamming? do you even know what that means? im just sharing my experiece and what i do it works for me. i think the problem on his phone is not yet on my knowledge.

amilio said:
hello
thank you all, but I could not solve the problem, low battery error, and only enters TWPR, and I tried installing the CM, and error, which can not do.
thanks
Click to expand...
Click to collapse
cant you enter download mode? can you open your phone? maybe your file is broken. tried testing the archives using 7-zip it should not have any errors. if there is a single error , redownload it. that's what i when i flash g2 v5. i always get error status 1 but i fix it by redownloading and test if it has no errors in 7-zip. hope this helps

Before I created this thread here, I had already tried everything you have mentioned in your original post instructions. The instructions you provided are the first things I tried when I was troubleshooting and everyone should have already tried doing the obvious already. The problem most of us are facing, goes well beyond these instructions. I think it has something to do with missing boot files or permissions that were only exposed after the unlocking process using a specific released version of freegee.
I have managed to use LG Flash Tools now, even after being affected. I would not advise trying this though, as it was an accident for me. I had the back cover off while flashing a custom rom with CWM. After the rom file was installed, I rebooted my phone from CWM. As the phone was rebooting (was on the rom boot animation) the battery fell out. After I put the battery back in the phone would load to the rom boot animation, but it would freeze on this screen and then reboot and do the same thing over and over (bootloop to animation) - I then tried to factory reset and flash the rom again, with the same thing happening again) - I then went in to restore my phone using a backup through CWM. After the restoration, then phone would still hang at boot animation and then bootloop. I retried restoring and flashing multiple roms and re root the phone with a saved zip file on my phone. None of this was working. I decided to try to use LG Flast Tools again, only this time it actually passed the low battery warning. The funny thing is, I have tried thousands of times even at 100% battery level and lower (when there was nothing wrong with my phone at all) and it has never worked. This time it did (even though I had 66% battery) and still works now, as I just tried it again.

Thank you!!
Mr.Gabo said:
Problem solved! Low battery warning on LG Mobile Tool
1. Uninstall LG flash tool , LG Mobile Tool , lg drivers and msxml in your control panel or delete their folder
2. Install everything again ( tested on windows 8 and 8.1 i fixed my phone.. yey)
3. and follow these instructions http://forum.xda-developers.com/showthread.php?t=2420219 and tadaaa your phone is working
Hit Thanks if this helps ) Finally i fixed my phone 9:58am 2/28/14 Philippine Time
Click to expand...
Click to collapse
that worked for me...after 2 days of trying i realy was disperate...then i tried this ad worked first time. you saved my phone:good::good::good::good:

23dno said:
that worked for me...after 2 days of trying i realy was disperate...then i tried this ad worked first time. you saved my phone:good::good::good::good:
Click to expand...
Click to collapse
im glad that this help

Tell me there's hope for my LGOGP

Ok, so I rooted my Optimus G Pro the other day and everything seemed to be going smoothly. Just yesterday it decided it wanted to reboot (it didn't give me a choice) and it sent me to TWR mode. I tried everything I could think of in there to recover or reboot and I just kept getting sent back there. I eventually ended up in CWM recovery but nothing will run properly.
I was able to get into Download mode but I can't figure out how to get further than this.
I think mine was forced an update as I've seen others complaining about... I'm following this thread http://forum.xda-developers.com/showthread.php?t=2302660 so I hope I can get it running.

vaughnpereira said:
Ok, so I rooted my Optimus G Pro the other day and everything seemed to be going smoothly. Just yesterday it decided it wanted to reboot (it didn't give me a choice) and it sent me to TWR mode. I tried everything I could think of in there to recover or reboot and I just kept getting sent back there. I eventually ended up in CWM recovery but nothing will run properly.
I was able to get into Download mode but I can't figure out how to get further than this.
I think mine was forced an update as I've seen others complaining about... I'm following this thread http://forum.xda-developers.com/showthread.php?t=2302660 so I hope I can get it running.
Click to expand...
Click to collapse
Edit: I am in LG Flash Tool following this: http://alllatesthardwaresolution.blogspot.com/2013/05/lg-flash-tool-free-no-need-b2b-userpass.html but I can't get to the third screenshot (Device Manager) I don't have/see that option anywhere...

vaughnpereira said:
Edit: I am in LG Flash Tool following this: http://alllatesthardwaresolution.blogspot.com/2013/05/lg-flash-tool-free-no-need-b2b-userpass.html but I can't get to the third screenshot (Device Manager) I don't have/see that option anywhere...
Click to expand...
Click to collapse
What OS are you on?ie Windows XP...7...8...

TheMighyLoki said:
What OS are you on?ie Windows XP...7...8...
Click to expand...
Click to collapse
Nevermind. I got LG Flash to work and my phone is back to stock! Damn, this was stressful. lol but that last post helped me, in case anyone wanted to know.

Skull.
vaughnpereira said:
Nevermind. I got LG Flash to work and my phone is back to stock! Damn, this was stressful. lol but that last post helped me, in case anyone wanted to know.
Click to expand...
Click to collapse
Good to hear that you got it working.

Latest T-Mobile Update Slowed Down My Phone

Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?

cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.

reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r

cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.

Thank you.
It's sadly still doing it.

cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.

Factory Reset

Unlocked Bootloader Message

Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.

http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69

Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !

I also don´t like the screen... the opportunity to hide would be great.

here's the same, maybe someone can make a xposed module?

kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.

uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...

kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:

any luck on the nag screen yet? maybe gone in the july update? =D lol

I get this message Everytime, any ideas? Help would be great

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!

makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.

I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!

Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.

How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it

..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."

I am posting hoping some progress may or may not have been made on this. Its atrocious.

How I Rooted my S7 on Nougat. PlayStore ROM V3 *outdated but still working*

*I TAKE NO CREDIT FOR ANY OF THIS, IM JUST TELLING HOW I DID IT. I AM ALSO NOT GUARANTEING YOU WILL HAVE THE SAME OUTCOME*
*I recommend going to this new update guide by CVertigo1 in the ROM's section as this version of the PlayStore ROM is outdated.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695)
ROOTING
1)Flashed stock Nougat ROM
2)Flashed ENG-ROOT found here https://www.androidfilehost.com/?fid=457095661767141717
- Make sure to flash the correct kernel included in the zip file
3) Install SuperSU. Link: https://www.androidfilehost.com/?fid=529152257862710010
- I used the regular Root.bat not the one with tweaks
FIXING LAG
1)Install Flashfire from PlayStore
2)Download the PlayStore Rom from https://www.androidfilehost.com/?fid=457095661767144652
-Transfer the file to the S7
3)Open Flashfire and flash the zip choosing only Mount/ system read/write
4)Now AROMA Installer will pop up and go through all of the terms and conditions
-When asked what to wipe I choose to wipe everything
-Next when asked what bloat to remove I choose the PlayStore Rom which removes all bloat and replaces stock apps with google apps (To see full list of changes refer to the PlayStore thread)
5)Now when my S7 boot it showed no launcher, I simply held the home button down which opened the google search, in there I searched for the playstore app and installed Nova Launcher.
-Now reinstall SuperSU by double clicking the root.bat like before
6) Installed the following apps to help with lag; Lspeed, Greenify, Kernal Auditor, LeanDroid, Force Doze, and SSD Boost
-I used most of the settings found on Lag fix threads for the MM root
My S7 is smooth as butter after all of this, no lag spikes and random crashes like I was experiencing with just the ENG Root flashed.
EXTRA
1)I did have to to a reboot to get the camera to work properly
2) I had to download a Dialer/Contacts and Message app from the playstore because the stock ones were deleted in this process. But the store ones work just fine, I am recieving calls and messages like normal.
3) *Battery life is just a little worse than stock, might be worth waiting for Xposed to released for Nougat.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695) :good:

setup wizard keeps stopping...
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance

Bunrin said:
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Click to expand...
Click to collapse
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.

UPDATE
Went through the entire process once more and found that wiping but keeping SU image works the best, I chose "no wipe" but it caused random reboots. I then wiped my phone and did as stated in my original post and it is working smooth once again.

ikoyhn said:
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
Click to expand...
Click to collapse
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V

Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
The rom is for Verizon and T mobile devices. Your good to go.

Blade22222 said:
The rom is for Verizon and T mobile devices. Your good to go.
Click to expand...
Click to collapse
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
Yup it says G935 but it also works with the G930.

ikoyhn said:
Yup it says G935 but it also works with the G930.
Click to expand...
Click to collapse
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks

Bunrin said:
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Click to expand...
Click to collapse
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124

ikoyhn said:
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
Click to expand...
Click to collapse
Thanks for your support.

Is this for the Qualcomm processor?

Gon Rouge said:
Is this for the Qualcomm processor?
Click to expand...
Click to collapse
Yes the *US*S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.

ikoyhn said:
Yes the S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
Click to expand...
Click to collapse
Not all s7s are Qualcomm, we sometimes get international users in here.

Blade22222 said:
Not all s7s are Qualcomm, we sometimes get international users in here.
Click to expand...
Click to collapse
Whoops forgot about that, I fixed my reply. Thanks for pointing it out:good:

My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.

IDCM said:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
Click to expand...
Click to collapse
-After what step did it get stuck on the boot text?
-Did you start factory fresh?

ikoyhn said:
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
Click to expand...
Click to collapse
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:

IDCM said:
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
Click to expand...
Click to collapse
Glad you got it all sorted out:good:

I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?

fjgrf said:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
Click to expand...
Click to collapse
You cannot use any custom kernels on us snapdragon models. No magisk or anything. The only root option is engboot and root.bat plus the setups to smooth it out or no root at all