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

Working zip of Chinese stock rom for 6045I

First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system & efs as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : removed due to some problems occurred after flashing.
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
Caution : Does not works on 6045Y & 6045K.
Backup efs also in case u loose ur IMEI or having error of unknown baseband/ no network
If you like my work, dont forget to hit thanks......
Sorry for all the trouble caused.
Well I am also in the same boat as well.....

yash_rathore25 said:
First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : https://mega.nz/#!88t2jJjT!dFpCY6987LAyAO2CcuKr0wmi5EPB3kRu9v8YTrNBgHs
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
May also work on 6045Y and 6045K : just need some willing hands.
If you like my work, dont forget to hit thanks......
Click to expand...
Click to collapse
Woohoo. Gonna download this!!!

For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......

Quick question. Can this rom read/write ExFat? I'd rather have my sd card formatted to that so that i can store larger movie files.

Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:

brian117 said:
Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:
Click to expand...
Click to collapse
One enhancement I read about was that it did have newer camera software. Many of the packages included are newer version levels than the ones included on our phones because the i806 came out after our models.
---------- Post added at 08:58 PM ---------- Previous post was at 08:45 PM ----------
yash_rathore25 said:
For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......
Click to expand...
Click to collapse
You should consider removing the system update checker from your custom rom. The icon appears in your screenshots so I'm assuming it's still included. Since the build.prop says it's a 6045i but it has the i806 codebase patches will never apply since the checksum's won't match.....so depending on what "version" it thinks it's on vs the update version the update checker will either never show an update or always show an update.

OK. I think I have this working. The ROM seems to be functional for me. Downloading all my apps now and getting it set up how I like. Will try to run it through the day tomorrow and see what I like and don't like... not expecting much difference over stock, but we'll see.

Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.

famewolf said:
Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.
Click to expand...
Click to collapse
I might still have a PA micro gapps file somewhere. Just need to see if it's 5.0 or 5.1.
Edit: Here you go. Just pick up the zero gapps. It works perfectly.
http://forum.xda-developers.com/showthread.php?t=2792842
Another option is the Slimgapps official thread here. They do have a "zero gapps" package, and both 5.x I think.
Sent from my 6045Y using XDA Free mobile app

yash_rathore25 said:
May also work on 6045Y and 6045K : just need some willing hands.
Click to expand...
Click to collapse
You mean testers?
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
You mean testers?
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
Yupp bro.
Just edit build.prop with notepad++ and change it to 6045Y instead of 6045I and flash the rom.
Then check the log of TWRP specially before the error in executing updater binary.
It will say something about the check_cu.
If you will open updater script with notepad++ you will see first line of command saying "check_cu("6045I-2AALUS7");"
Just change this line ("6045I-2AALUS7") with the line shown in the TWRP similar to this ( something like 6045Y-XXXXXXX)
Then again flash the rom, gapps and hope it will work.
If it works, dont forget to hit thanks button :laugh:

Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
I rooted my phone the next day it came to me,
Eventually i am also not going to get warranty as I imported this device from US to India.
N I personally dont care about warranty as none of the android device gets bricked completely, there is always a way.
Like I got stucked in bootloops in try of porting cm12.1 from other device.Even my backups failed to boot. Then I followed the mobile updater app provided by Alcatel and it simply restored my device to factory rom which will get updates also.
N warranty will not work if the device got physically damaged.
Yes backup will work.
After flashing this rom I would suggest you to make TWRP backup of this rom also alongwith Stock one.
I am getting a lot of range in network selection as it contains all the radios available for this device.
Screenshots of network range:

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.

famewolf said:
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.
Click to expand...
Click to collapse
I agree with you bro......:good::good:

Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion no risk of losing imei no. and radio modems

yash_rathore25 said:
In my opinion no risk of losing imei no. and radio modems
Click to expand...
Click to collapse
I'm attaching a platform.xml file already modded to allow full read/write access to the external sd (just drop the .zip off the filename as that was just to get xda to allow me to upload it...it's a text file)....you might find it useful to replace this in yours.(/etc/permissions)..other options include pre-rooting...adding in init.d support....etc.

Ran this ROM overnight and through most of my day so far (about 3 hours off the charger). First impression is that it's about the same as stock, not that I was expecting any different. You get the TCL splash screen at boot but the overall UI is pretty much the same. Since I now have root I went ahead and used app quarantine to freeze the bloatware apps I didn't want. Kinda wishing I had installed minimal gapps, but I figure I'll be reflashing again soon since the floodgates are probably about to open with new ROMS anyway.
Conclusion: If you're curious, flash it, it doesn't hurt anything. It may be a hair smoother, and I haven't really tested the camera extensively enough before or after to be able to tell a difference.
Edit: Literally as soon as I submitted this message (from my PC) I went to turn wi-fi off and the phone decided to reboot. Really odd.

@nickalltogether:
Which version of the phone do you have?
Sent from my 6045Y using XDA Free mobile app

ILAPO (Infinite Loop Auto Power off) FIX - ROOT REQUIRED for 4 Cores

Dear gals and guys,
I have created a video tutorial how to fix ILAPO issue here:
If you follow the step-by-step tutorial properly, you will be able to recover all your important data and even keep using the device.
If you are willing to either keep using the phone or sell it with all 4 cores enabled, please follow second tutorial:
Edit: New revision v8.0 has been released. Enjoy full Marshmallow support

Hey, thanks for that. Maybe I missed something but... what have you done in the 1st video?
That could be useful, but the only thing I got is the phone wasn't booting and the you got that booting.
Thanks!
W.

@maddler - I have only flashed the ILAPO fix using the LGUP, so that all cores but one have been disabled and I was able to get to the home screen once again.

Great work! Thx!
You saved my phone!
The lg rejections the mainboard replace, because unlock bootloader.
Now working perfect L, Is it possible in the future M?
Thx again!

blueeyeblue said:
@maddler - I have only flashed the ILAPO fix using the LGUP, so that all cores but one have been disabled and I was able to get to the home screen once again.
Click to expand...
Click to collapse
If you could, please, add download links and (maybe) a step by step guide could be useful for lesser experienced users too.
Thanks by the way!
Edit: found this http://howtovideoz.xyz/play?m=6c624a5877506d62584663 (which appears to be your too, if I'm not wrong).

I run 4 cores since 4 months now, Im on a custom ROM and just enable them all 4 cores every boot in Device Control by changing frequency. I think I've mentioned that in my notice post but I can't remember. Its good though, that the app for it has been created, some people might know now how to use tools like Device Control. We also might want to think about why you cannot lock the device on AOSP/CM based ROMs with 4 cores enabled... BTW from Wed I'll be free of a bootlooped G4, my OnePlus 3 is comming!

@maddler - Yes, the video tutorial is in the first post.
@Adam Myczkowski - Please try the app and let me know whether or not it works for you.

blueeyeblue said:
@maddler - I have only flashed the ILAPO fix using the LGUP, so that all cores but one have been disabled and I was able to get to the home screen once again.
Click to expand...
Click to collapse
Ok, great job guy, but where is the link to download the fix?
Moreover, if my smartphone is bootloop how can I downgrade from MM to LL? Everyone knows that even by flashing a different ROM, or downgrading, the smartphone does not start again!

@casabato - From where do you got that info? I downgraded from MM to LL without any problem. Model H815.

blueeyeblue said:
@casabato - From where do you got that info? I downgraded from MM to LL without any problem. Model H815.
Click to expand...
Click to collapse
Good to know, thanks. I wanted to say this: my smartphone (H815 too) has MM, but if it is in bootloop how can I perform a downgrade to LL and be sure it was successful?
As far as I know anyone who has suffered a bootloop is unable to restart the smartphone even by flashing a different firmware.
So I should downgrade now that the smartphone works, and not when it is in bootloop (hopefully never!), To be ready to eventualities ..
However, my first question remains: where is the link to download the fix?

blueeyeblue said:
@maddler - Yes, the video tutorial is in the first post.
@Adam Myczkowski - Please try the app and let me know whether or not it works for you.
Click to expand...
Click to collapse
It does work on AOSP as well. Checked, confirmed.

@casabato - Everything is in the first video description.
@Adam Myczkowski - Okay, thank you for the reply.

dolasz said:
Great work! Thx!
You saved my phone!
The lg rejections the mainboard replace, because unlock bootloader.
Now working perfect L, Is it possible in the future M?
Thx again!
Click to expand...
Click to collapse
Really I sent my phone back to LG to fix the board and my bootloader was unlocked and they fixed it and sent it back.

I tried the 7 HD ROM and when I tried to go back to stock LGUP doesn't recognize my device because swversion is changed in 'cust / OPEN_COM /cust_OPEN_EU.prop'. How can I delete that file or edit. I lost the custom recovery and I have access only to fastboot.

@Chosen_on184 - You are the lucky one
@exilod - Did you extract only the system partition and flashed it using the send command utility? It works only for H815.

blueeyeblue said:
@Chosen_on184 - You are the lucky one
@exilod - Did you extract only the system partition and flashed it using the send command utility? It works only for H815.
Click to expand...
Click to collapse
I have the H815. Here is what I tried:
After I encountered the bootloop for the first time I flashed the .tot fix with LGUP(The application could recognize my phone).
Then I applyed the 4 core fix with your app. Then I tried the ROM you recomanded but after some time I wanted to go back to stock L. LGUP says 'Unknown device '(see image) and I can't apply the tot fix again. I think the cust partition where that 7 HD sw information resides is not deleted even after reflashing the kdz. I don't know to use the Send_Command.exe except for connecting to phone and apply command for entering in fastboot mode.
If it's possible to flash with send command I am very interested how.

exilod said:
I have the H815. Here is what I tried:
After I encountered the bootloop for the first time I flashed the .tot fix with LGUP(The application could recognize my phone).
Then I applyed the 4 core fix with your app. Then I tried the ROM you recomanded but after some time I wanted to go back to stock L. LGUP says 'Unknown device '(see image) and I can't apply the tot fix again. I think the cust partition where that 7 HD sw information resides is not deleted even after reflashing the kdz. I don't know to use the Send_Command.exe except for connecting to phone and apply command for entering in fastboot mode.
If it's possible to flash with send command I am very interested how.
Click to expand...
Click to collapse
Maybe you have bad drivers. I had no success doing it under Windows 10, thus I had to switch to Windows 8.1 and install the following drivers: https://www.androidfilehost.com/?fid=95916177934549194

blueeyeblue said:
Maybe you have bad drivers. I had no success doing it under Windows 10, thus I had to switch to Windows 8.1 and install the following drivers: https://www.androidfilehost.com/?fid=95916177934549194
Click to expand...
Click to collapse
I tried on two laptops with windows 10. same problem. I'll try with windows 8.1 but I still think the problem comes from the phone.

@exilod - If you can enter the download mode, then it should be easy to flash the kdz again.

blueeyeblue said:
@exilod - If you can enter the download mode, then it should be easy to flash the kdz again.
Click to expand...
Click to collapse
I can enter download mode, I can flash L kdz file with LG Tools 2014 but LGUP still doesn't recognize my phone.

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

Question Touchscreen not working

Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.

zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money

persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.

to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful

persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash

I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong

Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.

persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters

Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).

persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.

Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.

persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.

Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.

Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.

persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.

So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.

persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.

As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.