Right guys I'm relatively new to the G2 scene.. 2 quick questions i've read somewhere that you can't do an over the air update on your g2 otherwise you go into a boot loop via di cyanogenmod updater and i was just curious to see if this is true as i've been getting really bad battery drain recently and i want to update to the latest nightly.
Question 2 if this doesn't happen to fix my recent battery drain problems how easy would it be to return to stock firmware i've read up on it and it seems quite confusing and i was wondering if there is an easier method or if it's just a simple as plugging it into your pc on updating via lg software.
Thank you for taking your time for reading this and i hope you guys have some answers for me
ferteen said:
Right guys I'm relatively new to the G2 scene.. 2 quick questions i've read somewhere that you can't do an over the air update on your g2 otherwise you go into a boot loop via di cyanogenmod updater and i was just curious to see if this is true as i've been getting really bad battery drain recently and i want to update to the latest nightly.
Click to expand...
Click to collapse
Official Over the Air updates (the ones released from Google) are bad if you have a Custom Recovery installed such as TWRP or CWM. You never want to take an Official OTA if you have either of those installed. But if you're just talking about updating your CyanogenMod build, that should be fine. For more information about updating CyanogenMod visit http://wiki.cyanogenmod.org/w/Updating. You can always manually update instead of using the inbuilt updater. Just download the new NIGHTLY and flash it via recovery, see #Updating_Manually.
ferteen said:
Question 2 if this doesn't happen to fix my recent battery drain problems how easy would it be to return to stock firmware i've read up on it and it seems quite confusing and i was wondering if there is an easier method or if it's just a simple as plugging it into your pc on updating via lg software..
Click to expand...
Click to collapse
Returning to stock is one of the most easiest things to do. Follow the Return to Stock guide. Basically you download your .KDZ file for your specific phone model. Boot into Download Mode, Open the LG Flash Tool, Point it to your .KDZ and hit Flash :good:.
NOTE: Make sure you flash a .KDZ that is made for your phone model! Do not flash any other models .KDZ onto your phone.
To make sure you download the correct .KDZ for your device visit LG Firmware ROM and enter your IMEI. It will direct you to your appropriate .KDZ.
Hello all,
Today I read a lot of posts here about rooting my phone because I was done with the stock UI.
I went for it and now I think I made a mistake, I would like your help. I read some similair posts, but I cant find a true solution for my problem.
My goal is to run CM 11, I have a stock LG 802 config with 4.2.2.
My steps were as followed:
- I used towelroot v3 wich was succesful
- I installed and ran D802 autorec (wich i guess was a bad idea). I got to recovery mode and I wanted to back up first.
- I made a back up of boot and system
- After the back up, I had to reboot
- NOW its stuck in a boot sequence to nothing. Just a light green and blue. I get the logo and I can get in the stock recovery it seems. Should I reset to factory settings?? Is that data still present?
I hope I can go from there, but after my major fail Im afraid to try it.
Thanks a lot in advance!
Update
I can get into download mode and LG Support Tool finds a phone, but the specs do not match and the update states that there is not any update available, wich there is.
When I get into recovery mode I can get into TWRP and I should be able to continu the process with flashing and wiping. The CM mod and Gapps are already on the internal memory. But I am really afraid.
For the record I did not flash or wipe anything yet, except for running Autorec and rebooting after prompt.
The real question for me is (I guess), is Autorec really unsupported with 4.2.2?
I would like to go on with the process, but I also would like to go back stock if needed in the future (hence the recovery back up I made with TWRP before the bootloop.)
Thanks again for any help what so ever
Hi everyone...
I have an awkward issue here with my Nexus 4...
It is in an eternal loop in bootlogo 5.1.1
I already did anything I found in Google search
Flashed ALL firmwares stock, tried some Cyanogenmod and nothing!
I already used simple .bat/.sh in stock folder, used Nexus Toolkit with bricked/bootloop ticked, SkipSoft Tookit and even a tutorial saying to use LGNPST to flash a developer version... this last one worked... but like said in tutorial, the rom is encrypted and the user can do nothing! After that, flashed stock rom and still got stucked in logo!
I did not say, but yes.. I always run ALL wipes
I do not know what else I can do! The phone seems to work normally. I can entry,
download mode, fastboot, recovery but system..
Any ideas?
Thanks for now and sorry about english!
Are you flashing the userdata.img file?
yes and no!
The same result... =/
After flashing userdata.img in fastboot, are you going into recovery using the power and volume buttons to perform a factory wipe?
yes... I already did that too!
Today in the morning, I installed a developer version 4.2 through LGNPST... The phone worked, but it is a old version, I want the last one 5.1.1 and I got the problem that internal memory shows 8GB instead of 16GB...
And I could not resolv this, even reading tutorials from xda forum
If anyone could give me a BIN file of 5.1.1 to use in LGNPST...
no one???
I'm facing the exact same issue, here my post
http://forum.xda-developers.com/nexus-4/help/nexus-4-stuck-animation-android-t3419997
Did u solved it?
No man...
unfortunately I ditched the device!
I've installed Android 4.2.2 and block OTA updates rooting the device, the problem is internally in the device, maybe is a hardware problem, I already made a test of the sensors and none works, for know I'm gonna use it just for phone calls and wapp...
thanks for answer....
Hello
Im just recently bought this device from a friend so i could ditch my broken Galaxy S2. I just need a good looking phone that does the job without lag and is unrestricted in terms of access which means, i want to be able to install custom roms. Oh and screen size is also important to me.
I however am NOT new to the android modding community and ive created a couple of things myself, but for every new phone im forced to relearn almost everything. Aaand boy did this phone land me in a very awkward situation that 6 hours of pure googling, experimenting with different firmwares etc, couldn't fix.
I learned the hard way that i have a JDI display and that its less common than the other one. I followed some simple guide where i was on 4.4.2 already and basically rooted it with ioroot. Now the only method ive found so far to install a recovery on a stock 4.4.2 lg g2 (d802) 32gb edition is by using a certain application called autorec.
I did try it. It seemed to work. No error. However, to my suprise i found out i had a screen that was completely covered in white/green/blue lines. By how the procedure was supposed to go, the app was supposed to boot me to twrp recovery after the install. And im guessing it did because i could feel the vibrations of the different buttons as i tapped the screen on different places. But i couldnt see what i was doing.
I researched into it and found out about the whole jdi thing. Found a Europe Open D80230b.kdz firmware and flashed it but just blindly booting the phone into download mode tho it was still covered in lines and couldnt see a thing. Once it was done, the phone booted and the LG logo was visible and the lines started to decay and slowly dissapeared. after about an hour, they were totally gone.
Now to the main issue im having and the question i have for you if can help me.
How do i go about installing a recovery that works (that i can actually see) so that i may access the menu in order to install this ldi kernel zip? Ive tried installing a recovery with the one click root + recovery script by somboons.
It gets stuck on this part "author : blog.lvu.kr
SPECIAL COMMAND : ENTER,LEAVE
#"
I basically CANT install a recovery on 5.0.2 with the one click script because it gets stuck. Cant root it either with SRKTools. I CANT install recovery on 4.4.2 with Autorec because my phone gets covered in white lines and i cant see what im doing. I tried installing a certain jellybean firmware to go from there. Using the open europe d802 jellybean firmware wasnt possible because the flash tool kept giving me disconnection errors. So i tried installing a open polish d802 firmware. got white lines so that is a no go too. One thing that i suprisingly can do. I can root it using the LG one click root method 1.3. The 1.2 script cmd version doesnt work. It gets stuck on the special command # part, however the graphical interface version roots without any problems.
ive found the recovery im gonna use which is supposedly nicer to jdi screen that, according to the creator, is supposed to generate less heat on the jdi screen. however i dont know how im supposed to install it. For now im gonna use the 5.0.2 open europe d80230b firmware til i find a solution. All im trying to accomplish here is to successfully install CloudyG2 3.3. And open the doors for a potential cm13 install.
Finally reached recovery by using this app.
https://play.google.com/store/apps/details?id=wli.areclp802
Read description on whats required if you intend to try it yourself. It requires root and some SuperSU option unchecked. Worked perfectly on my LG G2(D802) with JDI display that ran 5.0.2 lollipop stock firmware 30d. It will flash recovery successfully but then i had to manually press the button inside the app for it to boot me to the recovery. its the newest twrp 3.0 recovery. Now im happily running CloudyG2 3.3
This question thread can be closed now!
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.