Database Users

Wife possibly soft bricked??

Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?

Zugshad said:
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Click to expand...
Click to collapse
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work

XxZombiePikachu said:
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
Click to expand...
Click to collapse
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:

Zugshad said:
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Click to expand...
Click to collapse
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code

XxZombiePikachu said:
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
Click to expand...
Click to collapse
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )

Zugshad said:
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Click to expand...
Click to collapse
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)

XxZombiePikachu said:
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
Click to expand...
Click to collapse
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
edit... ok that is the ota file.... thanks again )

Zugshad said:
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
Click to expand...
Click to collapse
yep that should be it; just delete and goodbye updates should stop working as a whole (if you want to get tibu to freeze you can always log in with your play account on her device and download the pro version)
edit: just noticed you solved it

[Q] How to unlock bootloader? (everything stock, only ROOT) (D802)

Hi! Just rooted my LG G2 d802 yesterday, but I dont know how to unlock bootloader D:
Everything is updated (Android 4.4.2,v20h)... Done root with ioroot, i really dont know how to unlock the bootloader D:
I want so much CloudyG3

0144walter said:
Hi! Just rooted my LG G2 d802 yesterday, but I dont know how to unlock bootloader D:
Everything is updated (Android 4.4.2,v20h)... Done root with ioroot, i really dont know how to unlock the bootloader D:
I want so much CloudyG3
Click to expand...
Click to collapse
Hello.
Congratulations on rooting your device. The LG G2's bootloader is locked. But that's not a problem. In order to get a custom recovery so you can start flashing, you just need to install an application called AutoRec and tap a button - it's that simple.
Check our this thread and follow the instructions. Make sure you download the right model for your device.
http://forum.xda-developers.com/showthread.php?t=2715496

vPro97 said:
Hello.
Congratulations on rooting your device. The LG G2's bootloader is locked. But that's not a problem. In order to get a custom recovery so you can start flashing, you just need to install an application called AutoRec and tap a button - it's that simple.
Check our this thread and follow the instructions. Make sure you download the right model for your device.
http://forum.xda-developers.com/showthread.php?t=2715496
Click to expand...
Click to collapse
IT WORKS! Thank you so much! Now that I've done anything, can I uninstall AutoRec app or I need to just leave it there? :laugh:

You can uninstall it. make sure you take a backup of your working rom.
Thanks for pressing the thanks button!

vPro97 said:
You can uninstall it. make sure you take a backup of your working rom.
Thanks for pressing the thanks button!
Click to expand...
Click to collapse
OK, everything works fine, but I made something that I *should* not to do... "Calibrate" the battery with Battery Calibration app... Since I've done it, my battery is just going crazy. It stays stock at 100% for an hour and then drops so much fast... What is the problem and how do I solve it? (When I restart without battery level at 100% it still reset the battery log :c)
P.S: It takes so much time to just show up expected battery time left!
Sent from my LG-D802 CloudyG3 ROM using XDA Free mobile app

A few questions for rooted Sprint users

I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!

williamvito said:
I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!
Click to expand...
Click to collapse
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method

me2151 said:
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method
Click to expand...
Click to collapse
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
Click to expand...
Click to collapse
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?

williamvito said:
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?
Click to expand...
Click to collapse
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.

me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
You're the man, thanks for the quick reply! I will give this another go tomorrow.

me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?

williamvito said:
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?
Click to expand...
Click to collapse
Once youve started the dirtysanta method it installs a new bootloader. you can access bootloader(fastboot) by holding VOL- and plugging iin the phone when powered off

Little help need for H910 (AT&T Update)

Hi guys,
I just recently bought LG V20 H910 and its stucked on December 1, 2016 update Now the simple thing i want is to remain on stock and update the software.
The thing that i learned is we need AT&T sim which is not possible for me and the second thing is Bootloader unlock.
Now guide that what should is do, i know dirty santa's FM problem i dont want that also the boot time is longer .
It would be helpful if anyone guide to simple update without further modifications or root.

If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian

runningnak3d said:
If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian
Click to expand...
Click to collapse
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?

runningnak3d said:
If you don't have an AT&T SIM, you can't update without rooting. However, if you don't want to stay rooted, you can flash a back to stock zip that will unroot you and keep you on the latest firmware.
However, if the only reason you don't want to stay rooted is the FM radio, that is now fixed.
-- Brian
Click to expand...
Click to collapse
If I have AT&T SIM but I am not in the US. Will I get the update?

Mastermind_hassan said:
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?
Click to expand...
Click to collapse
If you use the dirty santa root you'll still have the corrupt warning screen and slightly longer boot time, static on display can be eliminated by flashing a custom kernel

cnjax said:
If you use the dirty santa root you'll still have the corrupt warning screen and slightly longer boot time, static on display can be eliminated by flashing a custom kernel
Click to expand...
Click to collapse
What are other methods for H910 bootloader unlocking that dont have that corrupt warning screen and longer boot time

Mastermind_hassan said:
Thank you for quick reply. can u please give the link from where to start and also i heard that after bootloader unlock there is some kind of warning and delay booting time , is that fixed as well?
Click to expand...
Click to collapse
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
nirvikkhanal said:
If I have AT&T SIM but I am not in the US. Will I get the update?
Click to expand...
Click to collapse
I have no idea.
-- Brian

runningnak3d said:
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
I have no idea.
-- Brian
Click to expand...
Click to collapse
okay thank you please give me the link to get started

runningnak3d said:
The boot time is a little longer, but yes, the REALLY long boot time has been fixed. The warning will always be there if you have an unlocked bootloader. That comes from the bootloader itself. You could change the image if you felt like digging into raw_resources, but that is a major risk.
I have no idea.
-- Brian
Click to expand...
Click to collapse
Just one last question, i have completed everything now i just wanted ask like for example if i wanted to sale my phone what things should i do to make that fizzy bootloader screen gone? because when i sell it to seller he will think there is some kind of fault in the screen

Mastermind_hassan said:
Just one last question, i have completed everything now i just wanted ask like for example if i wanted to sale my phone what things should i do to make that fizzy bootloader screen gone? because when i sell it to seller he will think there is some kind of fault in the screen
Click to expand...
Click to collapse
The only way to get rid of the boot screen is to go back to completely stock and locked boot loader, search the v20 forums there are threads around on how to do it.

(LS997) - Cannot Boot Into Fastboot Mode

Pretty much what the title says. I've been trying to unlock the bootloader on my sprint v20 to install lineage 16, but I can't seem to get it to fastboot. I tried both using adb commands as well as holding volume down + plugging the cable in, but both ways simply boot the phone without doing anything. Can someone help?

i95swervin said:
Power off the phone, press & hold volume up
( if I'm not mistaken )
and plug in the power cord connected to a PC.
Good luck
Click to expand...
Click to collapse
Hey. Doing this sent my phone to a "download" screen with two icons for a few seconds, and then a firmware update screen. Is this what fastboot looks like? Because I hear people describing it as a menu with options.
Thanks.

Anwiday said:
Hey. Doing this sent my phone to a "download" screen with two icons for a few seconds, and then a firmware update screen. Is this what fastboot looks like? Because I hear people describing it as a menu with options.
Thanks.
Click to expand...
Click to collapse
Wrong volume key.
But you've got an ls997 mate. If you've taken an ota in about the last 18 months Sprint helpfully eliminated any chance of you unlocking the bootloader and rooting.
The last software version it was possible to revert futher back to an actually rootable version was ZV7, way back in the early-mid nougat versions.
Once updated past ZV7 Sprint helpfully physically burned fuses embedded in the CPU to keep you from going back and rooting. Hail overlord Sprint.

Phoenix591 said:
Wrong volume key.
But you've got an ls997 mate. If you've taken an ota in about the last 18 months Sprint helpfully eliminated any chance of you unlocking the bootloader and rooting.
The last software version it was possible to revert futher back to an actually rootable version was ZV7, way back in the early-mid nougat versions.
Once updated past ZV7 Sprint helpfully physically burned fuses embedded in the CPU to keep you from going back and rooting. Hail overlord Sprint.
Click to expand...
Click to collapse
Damn. So there's no way to install a custom ROM then?

Anwiday said:
Damn. So there's no way to install a custom ROM then?
Click to expand...
Click to collapse
Nope. Once it's past ZV7 it's never going back and you need to go back to root and install custom roms.