Bricked Your Newly Rooted Tungkick's H900 TOT? Fear not. ;) - LG V10 Q&A, Help & Troubleshooting

As we all know, Tungkick's Root Method by TOT instructions, are to be observed and followed step-by-step in order to achieve proper root on this device. One of the instructions is to leave the settings in LGUP, as "Refurbished".
Well, after accidentally flashing a zip file on my H900, my phone went through several boot loops and started giving me a headache from Hell. After considering the instructions by Tungkick, I thought, "What would Wesley do?" Think outside the box. Since I had not set my phone to MTP, I was not able to make any type of connection with the LG Bridge app, but once I crossed my fingers, ran LGUP and chose the "Ugrade" option, the phone rebooted like out of the box, and the good thing about this is that YOU DON'T LOSE YOUR DATA (pics, music, call logs, etc....) The recent lags my phone had been experimenting, went away and I was able to recover all my data using LG Bridge.
So, there. I hope this comes in handy for anyone experimenting issues and are Rooted.

Do you have a tutorial? Or links to this! I have the same issue please.
Nvm found the information tnx.
http://forum.xda-developers.com/att...g-h900-real-tot-make-tungkick-t3336317/page44

what zip did u flash? if u got bootloop with "fail *something*" on the top left, it's because u didnt unlock bootloader using fastboot (dev setting is not enough)

make123 said:
Do you have a tutorial? Or links to this! I have the same issue please.
Nvm found the information tnx.
http://forum.xda-developers.com/att...g-h900-real-tot-make-tungkick-t3336317/page44
Click to expand...
Click to collapse
Follow Tungkick's tutorial to "re-root" your phone, but instead of selecting "Refurbish", you'll select "Upgrade".
It's that simple.
If you have Xposed, you'll need to reflash it using Flashfire, and you'll have to re-install BusyBox. The rest of your apps keep the data, just as a computer would if you would to do an "upgrade" with the "without losing your files" option or something like that...sorry, it's been a long week.

Related

Fixing the unbrickable LG L9 [for the untechnical]

Let me just start by saying I am not technical and the persons who devised the methods will be credited properly as they helped me immensely and saved me an RMA to LG for stupid flashing error on my part.
If your phone is totally black and won't boot there's a chance that there's a problem with your bootloader assuming you didn't physically damage your phone and this is the result of improperly flashing the phone or some other software problem
Phone can be fixed in 4 easy steps and to save yourself time the next post will provide credit and links for the following 4 easy steps.
1.) Run the p769 boot loader script that _____ made this will get you into Software Recovery Mode after you run it with the USB cable attached to the phone (assumes you have the LG Unified Drivers installed) You can get into Software Recovery Mode by holding the Volume Up + button while you power on the device
2.) Flash the phone with the correct KDZ for the file and you can also root the device using the Lelus Cmahendra root method which involves swapping a bin file during flashing the phone (don't forget to follow their awesome tutorial on how to edit your hosts file, run the https appication, and don't forget you need to run Lelus' script which copies the superuser.apk file to the phone before you flash the phone *i skipped this step my first time and wasted time*
If your phone boots and everything is peachy - awesome! 3/4) If your touch screen is wacky like mine was then you will have to follow
Lelus' guide to using adb to replace the touchscreen firmware on your device
will edit post for clarity and to credit people and put in links (don't know how just yet) but knowing these steps in order like this is super time saving
flash v10g on v10g
Hi OP,
Sounds like you have been through a lot. I'm noob here and have searched for few hours couldn't find a solution.
I just hard-reset my P769. It is on v10g version. I was on a rooted v10g. I was trying to update to JB OTA. But after the download, the update process always fails (3 times) with the Android drop dead then the phone restart to v10g. Out of desperation, I did hard reset and hope to download JB update. Now I found my wifi stopped working besides root lost.
my wifi constantly on "obtaining IP address", I have reboot my router (WPA) several times no luck. I tried to connect the wifi at work (WEB), same "obtaining IP address" loop. the WiFi status icon on the top Status Bar is gone too. But I can still turn on and off the through Settings.
My question for you is have experienced this problem? any suggestions?
I'm about to flash v10g. just downloaded a clean version. Can I flash a new v10g on existing v10g? will this clean up all the system data/settings.
I'm suspecting the old DHCP binding information is cached in the phone. But I lost root have no way to clean up the cache data.
Thanks
brickedmyphone123 said:
Let me just start by saying I am not technical and the persons who devised the methods will be credited properly as they helped me immensely and saved me an RMA to LG for stupid flashing error on my part.
If your phone is totally black and won't boot there's a chance that there's a problem with your bootloader assuming you didn't physically damage your phone and this is the result of improperly flashing the phone or some other software problem
Phone can be fixed in 4 easy steps and to save yourself time the next post will provide credit and links for the following 4 easy steps.
1.) Run the p769 boot loader script that _____ made this will get you into Software Recovery Mode after you run it with the USB cable attached to the phone (assumes you have the LG Unified Drivers installed) You can get into Software Recovery Mode by holding the Volume Up + button while you power on the device
2.) Flash the phone with the correct KDZ for the file and you can also root the device using the Lelus Cmahendra root method which involves swapping a bin file during flashing the phone (don't forget to follow their awesome tutorial on how to edit your hosts file, run the https appication, and don't forget you need to run Lelus' script which copies the superuser.apk file to the phone before you flash the phone *i skipped this step my first time and wasted time*
If your phone boots and everything is peachy - awesome! 3/4) If your touch screen is wacky like mine was then you will have to follow
Lelus' guide to using adb to replace the touchscreen firmware on your device
will edit post for clarity and to credit people and put in links (don't know how just yet) but knowing these steps in order like this is super time saving
Click to expand...
Click to collapse
Flash 10g using offline method and reroot while you're at it. Should fix all your problems .
Sent from my LG-P769 using xda premium
Thanks for the reply.
Which offline method do you recommend?
I'm trying to use cmahendra's method but shttps.zip is found virus in it.
FLASH Any LG Factory ROM (kdz) WITH OFFLINE FIX METHOD
Tablechair said:
Flash 10g using offline method and reroot while you're at it. Should fix all your problems .
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
value99 said:
Thanks for the reply.
Which offline method do you recommend?
I'm trying to use cmahendra's method but shttps.zip is found virus in it.
FLASH Any LG Factory ROM (kdz) WITH OFFLINE FIX METHOD
Click to expand...
Click to collapse
I can vouch for that zip file. The small server is rerouting traffic so it behaves like malware in that sense. It's 100% clean though disable AV or add it as an exception. Or use this https://www.dropbox.com/s/9v1gne55cm5f04a/OfflineFlash.zip?m It uses apache to reroute the traffic from the LG software. Also you can just go thru the steps. 1. opens host file with admin permissions. 2. starts the server. 3 etc.
This is what I personally use works 100% of the time no matter what machine I'm using or the location of the folder its pretty nice.
Great! I disabled the AV then read cmahendra's instructions 3 times:http://forum.xda-developers.com/showthread.php?t=2085344
1st I flashed a new v10g, this is a t-mobil clean version. I tested the WiFi, no more "Obtaining IP address.." loop. "Obtaining IP address.." loop problem is totally fixed. WiFi connected to the AP instantly. I believe my first failed JB update messed up the WiFi system files so even the hard reset won't do anything. Writing this is to help some other people may experience the same problem and search for solutions. I had searched 3 days in row, almost every corner of the internet but couldn't find any viable solutions.
2nd, I cleared up couple of times of the Google Services Framework. then received the OTA v20d update.
I'm happy and dandy now on JB. I'll later root it when I have break.
Thanks OP for your help and guidance:good:. Learned a lot Android in the last few days. :laugh:
Tablechair said:
I can vouch for that zip file. The small server is rerouting traffic so it behaves like malware in that sense. It's 100% clean though disable AV or add it as an exception. Or use this https://www.dropbox.com/s/9v1gne55cm5f04a/OfflineFlash.zip?m It uses apache to reroute the traffic from the LG software. Also you can just go thru the steps. 1. opens host file with admin permissions. 2. starts the server. 3 etc.
This is what I personally use works 100% of the time no matter what machine I'm using or the location of the folder its pretty nice.
Click to expand...
Click to collapse
value99 said:
Thanks for the reply.
Which offline method do you recommend?
I'm trying to use cmahendra's method but shttps.zip is found virus in it.
FLASH Any LG Factory ROM (kdz) WITH OFFLINE FIX METHOD
Click to expand...
Click to collapse
@Tablechair
I dont want to be rude but may be this is what I have to tell when noobs MAKE NEW THREADS for no good reason and clutter the forum, simply because they dont read thread fully and carefully.
About false virus alarm, it is clearly mentioned in my OP, since day 1.
See He UNBRICKS phone with the help of my guide and group of files and no credit.
But does not forget to thanks OP with which the phone was actually bricked.
Sorry buddy I agree 100%.
Sent from my LG-P769 using xda premium
---------- Post added at 03:46 PM ---------- Previous post was at 03:39 PM ----------
If you used instructions and files from cmahendra make sure to thank him in his thread.
Sent from my LG-P769 using xda premium
brickedmyphone123 said:
Let me just start by saying I am not technical and the persons who devised the methods will be credited properly as they helped me immensely and saved me an RMA to LG for stupid flashing error on my part.
If your phone is totally black and won't boot there's a chance that there's a problem with your bootloader assuming you didn't physically damage your phone and this is the result of improperly flashing the phone or some other software problem
Phone can be fixed in 4 easy steps and to save yourself time the next post will provide credit and links for the following 4 easy steps.
1.) Run the p769 boot loader script that _____ made this will get you into Software Recovery Mode after you run it with the USB cable attached to the phone (assumes you have the LG Unified Drivers installed) You can get into Software Recovery Mode by holding the Volume Up + button while you power on the device
2.) Flash the phone with the correct KDZ for the file and you can also root the device using the Lelus Cmahendra root method which involves swapping a bin file during flashing the phone (don't forget to follow their awesome tutorial on how to edit your hosts file, run the https appication, and don't forget you need to run Lelus' script which copies the superuser.apk file to the phone before you flash the phone *i skipped this step my first time and wasted time*
If your phone boots and everything is peachy - awesome! 3/4) If your touch screen is wacky like mine was then you will have to follow
Lelus' guide to using adb to replace the touchscreen firmware on your device
will edit post for clarity and to credit people and put in links (don't know how just yet) but knowing these steps in order like this is super time saving
Click to expand...
Click to collapse
where can I find de bootloader???
HOLY UNNECESSARY BUMP BATMAN!!
Sent from my LG-P769 using XDA Premium 4 mobile app

lg l9 p769 - droid 4.0.4 - i'm lost, could use help, linux user

i have been seeing a lot of threads about rooting this phone, but, they all have windows scripts, even the thread that is said to have a runme.sh does not have it in any of the links that i unzipped - only a runme.bat, but yet, people keep mentioning a runme.sh in it... also, i really don't see any one lying out the steps for doing this with linux.
i'm a noob, and dont really know much about this stuff, but i've done this ONCE before with a galxy exhibit, but it was very easy, i just copied a file to the phone (stock rom?), rebooted into recovery, told it to recover from that file, and i was done.
i have no idea how to do it with my new phone, and so i'm wondering:
1: where can i find the files i need to do this with linux - i just want root, nothing special
2: where can i find the steps necessary to do it - in the easiest manner possible?
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
any help is appreciated.
sentientsystem said:
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
Click to expand...
Click to collapse
Your phone is running ICS 4.0, that is the version which it shipped with. Pretty much everyone on here has upgraded to JB either with software update on the phone or they have manually updated with the offline KDZ flash method.
I dont have any experience in linux so I cant help. I hope you can get your phone rooted!
Sent from my LG-P768 using xda app-developers app
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
sentientsystem said:
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
Click to expand...
Click to collapse
You would need wine and then set it up...
Sent From My Xperia Themed P769
well, i tried that "LGpwn" and it didn't work, as well as a fake lg-recovery app. i figured out that i've got a "10g" phone (P769 V10G ICS). i'm not sure what the next step is. some one mentioned downgrading to JB... is there some where you can point me to for that???
i've GOT to get this t-mobile junk off my damned phone... i've even TRIED to install cyenogenmod, but i can't figure out how to get my phone to go into recovery mode (NOT factory rest) - i've tried volup+power+home and volup+power, and neither seem to be working.
Setup a sandbox, windows xp. LG uses windows, no other way to root as of right now for the t-mobile version.
Sent from my LGMS769 using xda app-developers app
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrade to a samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
sentientsystem said:
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrad to an samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
Click to expand...
Click to collapse
Option #1
If you are rooted on stock T-Mobile 10e or 10g ROM and have the CWM installed from this thread:http://forum.xda-developers.com/showthread.php?t=2095825 follow my instructions.
Place one of these CWM ROM images on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2136204
Place this JB radio firmware from T-Mobile 20d ROM on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2256350
Power off the device.
After power on the back/menu capacitive buttons will flash repetedly. Press Volume down while the lights are flashing and the phone should go into recovery.
Flash the ROM first.
Flash the radio second.
Reboot.
***Notes***
1.) 20d is the latest T-Mobile, 21b is the latest Wind Mobile. Both work.
2.) 21b is lighter/faster but has no wifi-calling.
3.) 21b will require you to manually enter your APN settings for cellular data and MMS. Be sure to write down your APN settings before flashing this ROM.
4.) Some users say battery life sucks on JB. I notice that 21b is better on battery life than 20d.
Option #2.
In Linux install a Windows VM and follow the standard instructions here:
http://forum.xda-developers.com/showthread.php?t=2173465
Use KVM with a GUI or even easier use VirtualBox.
I'm a die hard linux geek too. I even run linux at work while all of our msp software was written for windows. You are better off just running an old copy of xp inside virtualbox trust me its just easier that way. You can use adb if you like (its the same thing the windows users use in their batch files and just rewrite the bash script, but you will save yourself lots of headaches just using virtualbox. -- my .02
Sent from my LG-P769 using xda premium
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
# what's the difference between unlocked boot loaders and being rooted?
# do you have to unlock the bootloader to get root access?
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
My bad. I should have read through your original question all the way before posting. I see that you are not rooted.
If you are on 10e ROM you can root in Linux:
http://forum.xda-developers.com/showthread.php?t=1990705
It will require rewriting the batch script as a Linux shell script. It is possible but nobody has done it yet.
If you are on 10g you will need Windows. I have also answered your questions below.
sentientsystem said:
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
It allows you to boot an un-signed kernel. You can boot custom ROMs basically.
# what's the difference between unlocked boot loaders and being rooted?
Root allows you to `su -` to the root user and own the whole system.
# do you have to unlock the bootloader to get root access?
No.
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
Click to expand...
Click to collapse
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
sentientsystem said:
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
Click to expand...
Click to collapse
Welcome!
I know that a long time ago when I ran VirtualBox in Ubuntu there was something I had to do to allow USB access to the VM.
Here are the current instructions directly from Ubuntu:
https://help.ubuntu.com/community/VirtualBox/USB
Good luck.
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
sentientsystem said:
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
Click to expand...
Click to collapse
Yes you can flash a pre-rooted image. They are available. Use the search?
I posted instructions on the first page showing how to boot recovery.
that's great news - that's all i really needed - i didn't see them before, at least, not conspicuously, but i'll search around again.
and, i must have some how missed your instructions, i'll look again.
thanks!
kevev said:
I posted instructions on the first page showing how to boot recovery.
Click to expand...
Click to collapse
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @everyone for your help.
sentientsystem said:
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
Click to expand...
Click to collapse
I've decided to help you out This page will give you some more info on the P769 and several kdz (roms) for the P769
The fastest way to root is to flash the V21B kdz (this is the Jelly Bean version for Canada) using this guide, http://forum.xda-developers.com/showthread.php?p=36351786
The reason why you want this rom is because it has a vulnerability that is easy to exploit with Jcase apk
Once your followed everything (and rooted), install Super Su and Busybox
Next install artas182x second init CWM (in case you can't find it on his page, the link is here )
Note: you will see blinking led lights when you see the LG logo (booting up) appear after a couple of seconds. To enter the CWM press the vol (-) when the lights start flashing.
After you installed Artas182x CWM you can recover from someones clockworkmod backup.
following info from Cmahendra's thread
Note: only restore CWM backups from P769 versions or MS769!!!!
Or check out the V10B (MetroPCS "JellyBean") CWM backup
Now the only 2 reasons to unlock the bootloader are:
1. Install a safer and better CWM
The reason why is because Artas182x CWM is a second init (bootstrap), so if you mess around with a busybox apk and something goes wrong or you remove a file that is required (for CWM), it will stop operating. You will have to reflash the kdz or fix what you changed to get it working again.) I've had this problem several times while messing around with different busybox apps and etc.
2. Custom roms
(which you stated you are not looking for) not worth talking about right now.
Answer to questions
The only pre rooted roms are clockworkmod backups, lol
The default recovery is useless to us (unless you feel like solving the problem)
Flashing back and forth (ice to jelly) comes with risk, the program used on Windows to flash is buggy at times. The best way (in my opinion) is to flash only when really required and mostly restore from clockwormod backups. The device is actually hard to hard brick, but it will require at lot more knowledge to get your device running again.
---------- Post added at 07:23 PM ---------- Previous post was at 07:16 PM ----------
sentientsystem said:
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @all for your help.
Click to expand...
Click to collapse
So what version are you on right now
Ice? Jelly?
i'm still on ICS for the moment. still trying to understand what i need to do next. re-reading your post for the 2nd time, and all the threads it references. making sure i don't screw any thing up. thinking about upgrading to JB, and trying this CWM. and looking into this "cyanogenmod" some more, to understand why i never see any one on this site mention it, and what all these "other roms" are about. lmao, like i said, i'm way new to this . it's a lot to take in, even for a web developer .
thanks \m/ (>_<) \m/

Data recovery HELP - Bricked phone

Sorry for the duplicated post. I just noticed the other one i posted is in the wrong section and this is the one for the AT&T phones so here it is again.
Hi Guys. Today i rooted my phone for the first time (LG Optimus G e970)
Everything went well, then i uninstalled the bloatware from AT&T and a few of the google apps that i do not use like books or music, and on the next reboot i got my phone bricked with the LG loop and "Security Error" message.
I found some great info on these forums on getting the phone in working condition with the help of this: http://forum.xda-developers.com/show....php?t=2388440
However, before i go ahead and restore the phone's original firmware, i would like to know if there is anyway to recover some of the files. I have some important notes i wish to recover, everything else is on google and the external SD card so im not all lost.
I am able to put the phone in download mode by holding the up and down volume keys and then powering on the phone with the usb cable connected to the PC, but it is not showing as an external disk on the computer. I do have the LG drivers installed tho, the same ones i used to root the phone.
Any ideas?. thanks a lot.
What recovery do you have ? You may be able to mount internal and sd card in recovery and access them on your computer ?
optimusv45 said:
What recovery do you have ? You may be able to mount internal and sd card in recovery and access them on your computer ?
Click to expand...
Click to collapse
Hi thank for the help.
I have no clue about what recovery i have. I never played with the phone before the rooting and removal of the apps, so i believe it should be the "stock" recovery if you wanna call it like that.
axopro said:
Hi thank for the help.
I have no clue about what recovery i have. I never played with the phone before the rooting and removal of the apps, so i believe it should be the "stock" recovery if you wanna call it like that.
Click to expand...
Click to collapse
I don't know what guide you followed to get the root. If you followed this
http://forum.xda-developers.com/showthread.php?t=2450258
You should have twrp. Stock recovery may not be able to mount storages for uses on PCs.
Also I haven't seen the post you included , maybe that's an older post. A lot of people use this to recover their "bricked" phones
http://forum.xda-developers.com/showthread.php?t=2230994
I personally have followed this too.
As long as you have download mode you don't have to worry. However you need to read carefully before processing with teenybins because its something that can actually brick your phone if used wrong.
optimusv45 said:
I don't know what guide you followed to get the root. If you followed this
http://forum.xda-developers.com/showthread.php?t=2450258
You should have twrp. Stock recovery may not be able to mount storages for uses on PCs.
Also I haven't seen the post you included , maybe that's an older post. A lot of people use this to recover their "bricked" phones
http://forum.xda-developers.com/showthread.php?t=2230994
I personally have followed this too.
As long as you have download mode you don't have to worry. However you need to read carefully before processing with teenybins because its something that can actually brick your phone if used wrong.
Click to expand...
Click to collapse
Ok so when i did the rooting i followed that same guide you linked to, but i only did it to the root part. Not the "UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-"
I just wanted the permissions to remove the apps.
So now with the TeenyBin guide.... will that erase the current settings and information on the phone or is it just an attempt to fix the firmware loop?
will the process attempt to restore the google apps missing?
axopro said:
Ok so when i did the rooting i followed that same guide you linked to, but i only did it to the root part. Not the "UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-"
I just wanted the permissions to remove the apps.
So now with the TeenyBin guide.... will that erase the current settings and information on the phone or is it just an attempt to fix the firmware loop?
will the process attempt to restore the google apps missing?
Click to expand...
Click to collapse
There are different kind of teenybins. They do different things, one giving you a working recovery and updating RPM/TZ, one restoring your phone to complete factory state. You will have to read it to know what I'm saying here. The one that give you twrp and update your partitions may let your data alone but you will most likely still have the existing bootloop. The gapps missing ? The ones you deleted ? If you use the bin that recovers phones to factory state then you will have all the stock apps again.
Quick update.
I was able to recover the phone and the data in it. :good:
I installed the new boot loader with the teenybin instructions and was able to backup the data partition to an SD card.
Anyway, after that i went for a recovery using the stock firmware and LGNPST and now i lost the boot loader with all the neat options, but got the phone working again, and to my surprise, everything was back there including data and applications,. i dont get it but oh well... im back alive.
Ill backup all the important stuff from now on, and then i will keep messing with the phone again LOL. i learned quite a few things today... ill read more from now on before doing more things.
Thanks for all the help.!!
Good nite

HowTo: Update To Stock Lollipop (23B - LG Official!) on the Verizon LG G3

*WARNING* - There have been at least two known hard bricks using this method. It has worked successfully for many people, including myself three times. However, with two hard bricks, this isn't something to go into without at least considering the possibility. The standard warning has always been in this thread (second paragraph), but consider yourself doubly warned. Now that we have root and TWRP on 5.0 stock, this method is all but obsolete. We're just waiting on the good devs to bring us superb Lollipop stock ROMs like SkyDragon by @HolyAngel and Jasmine by @hsbadr. Once those are out, this method should really only be used if you need "official" software on your phone. Or you can just wait for Verizon to push the actual OTA, which is probably technically safer than any custom flashing methods there are.
--------------------------------------------------------------------
**NOTE** - There are two stellar custom-stock ROMs here in the form of Jasmine v.5.0 and SkyDragon 3.0.0. There is no longer any need to use this method to upgrade to stock LP unless you just really need the software status to say "official". Download link & instructions at the following links:
SkyDragon G3 VS985 Edition Version 3.0.0
JasmineROM v5.0 Release [LP] [Stock] [Rooted] [Unmodified]
--------------------------------------------------------------------
Are you still here after reading that warning and looking at the great custom options? Read post # 148, then, if you really insist on being so daring as to try an obsolete method, I guess proceed on. Best of luck to you.
--------------------------------------------------------------------
For starters, this thread may be deemed unnecessary and/or redundant. If so, please accept my apologies and mods feel free to close the thread. This is an extension of this thread started by @annoyingduck. It's a start-to-finish way to flash 23A and keep all your apps. Rather than linking threads here, there and everywhere, I've compiled everything and put it all in one place, to try and keep down the number of questions in that thread (which is really supposed to be for devs to assist them in getting the info they need to make the wonderful stock ROMs we've all come to know and love). NONE of this information is original to me. I'm not that smart. All credit goes to the respective posters listed below.
Now, the usual disclaimer - I am not responsible if you brick your device by using any or all methods outlined below. They worked for me. They may or may not work for you. If you go down this path, you do so at your own risk and/or peril. Don't come crying to me in the unlikely event you can't figure it out or kill your phone!
Also, please take note right here right now, as this question will never be answered again by me in this thread. There is currently NO ROOT on 23A. Root will NOT be retained when you upgrade (in fact, it will be lost at the 12B KDZ step). Further, we do NOT know how to root stock Lollipop on Verizon at this point. So to answer your questions: NO, you will not have root on 23A at all, period, no matter what, until some smart dev is able to come up with a way to root it.
The good news is that you can downgrade back to 10B (the only root-able version) at any time and get back to rooted goodness and flashing rooted stock-KK or AOSP-Lollipop. I'm hopeful we'll get root eventually for stock Lollipop, but it's too soon for that.
First, you need to download several files. The first several have to do with KDZ'ing back to 10B, followed by 12B (you WILL LOSE DATA going back to 10B...back up everything!).
Things you will need:
Drivers from LG for the G3.
Two files from this download page - the 10B KDZ file (VS98510B_01.kdz) and the 23A update file (LG_VS985_12B-23A.dlpkgfile).
NEW 3/6/15 - The 23B (should be an OFFICIAL LP build) update is available here. Same as before, rename to .up and put it in the Software Update folder. Update from 12B stock.
The 12B KDZ file. (Alternate mirror.)
The LG Flash Tool 2014 (originally from this thread).
Now that you have those, we can move on to the directions. To KDZ back to 10B (followed by 12B after a few interim steps), you need to follow the procedure outlined here by annoyingduck. I'm quoting everything so it's all in one post, but linking back so those who made it get all the credit.
When flashing the 10B KDZ, you must use the "CSE Flash" option, because you're downgrading and getting rid of everything on your phone. You will lose ALL data, so copy your TiBu folder, your photos, files, etc. elsewhere first.
annoyingduck said:
-First remove any of the .tot flashing tools/programs that you may have already installed as they will conflict with the KDZ flashing tool.
-Download and install the latest LG drivers for your phone here (FYI I am linking the LG site directly instead of the file to ensure that you download the current up-to-date drivers): http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black
-Download the VS985 10b KDZ file from here: http://downloads.codefi.re/autoprime/LG/LG_G3/VS985 and thank @autoprime in whatever manner you deem fit.
-*New* Mirror for 10b.01 KDZ: https://mega.co.nz/#!7ERgXJbI!2KxATJt7q-HWvAPbTfVrT3wGuwPjWCw70N65MVlgfWg md5: d228ba692ef0c4704cba0b00fad8b8ce
-Download the LG Flash Tool 2014 from this thread here: http://forum.xda-developers.com/showthread.php?t=2797190 and be sure to thank @quangnhut123 for his efforts. Also read that thread a bit so you understand how to fully use the tool exactly, but I will outline the process below.
-Extract the .zip folder to wherever you wish to keep it (desktop, downloads, etc).
-Copy the 10b KDZ file (or whatever KDZ your flashing) into the LG Flash Tool folder
-Power off your phone completely, hold volume up, plug in the usb cable, wait for any drivers to load, and you should then be in Download Mode
-Run LGFlashTool2014.exe (you may need to run as administer as its not an installed program, rather an executed one from wherever you saved the folder).
-You may need to install Visual C++ Runtime Library. If so, refer to the LG Flash Tool thread for more info on obtaining that.
-Select CDMA as your type
-Select Diag as your phone mode
-Select your KDZ file that you copied or pasted into the folder
-Choose the option of CSE Flash (this is a full wipe, you will lose your data). Do not choose Normal Flash when performing a downgrade, nothing good will come from doing that!! Another screen will open, just leave everything the way it is.
-Click the Start button and yet another window will appear showing a language selection screen. Just leave everything the way it is as Korean and hit OK. Don't worry, the tool is already set to flash in English.
-Wait until the Flash is done 100% and unplug/reboot... and that's it
Click to expand...
Click to collapse
Ok, now that you're back to 10B, it's time to do some work there. You need to root your phone, install Titanium Backup and restore your backed up apps & their data. I prefer to use the IOroot method. So root, then install all your apps. After that, it's time to update to 12B. You're doing the same thing you did with 10B, except this time you are choosing "Normal Flash", not CSE flash, because you're upgrading. Once you've done that, you will be upgraded to 12B and will have lost root. Here is more from annoyingduck:
annoyingduck said:
-Restore apps, and select system data items you want restored (aka: call log, sms/mms messages, wifi access points, bluetooth pairings) via Titanium
-KDZ to 12b, but this time choose NORMAL flash. No bootloops because it's an upgrade
-Root is now lost, but atleast all your apps and data are already there
Click to expand...
Click to collapse
Now we're going to update to 23A using a method described here by justiz33.
justiz33 said:
Do not attempt unless you are sure of yourself and have a high percentage of battery left.
if you are on 12B and NONROOT, you can put the update on /storage/external_SD/SoftwareUpdate/23A.up (**hokie note - FYI, I had to put mine on the internal SD in a SoftwareUpdate folder for this to work; it wouldn't flash when on the external SD card. Don't forget to rename your update downloaded above to "23A.up")
then download and install Activity Launcher (**hokie note - Here's a play store link.)
then in Activity Launcher use the drop down to switch between ALL ACTIVITY.
scroll down to the bottom area and look for either 'Software Update' or com.lge.permission (**hokie note - Mine was titled a little differently, something like com.lge.fotaupdate.permission.)
click the dropdown and expand the list.
look for DmcEzUpdateStart and click it.
You should be on a black screen with FOTA UPDATE written, just sit on that screen and wait 3 min and it will then say 'Shutting Down'
It should reboot and start the update.
Click to expand...
Click to collapse
Now we'll let annoyingduck take us home.
annoyingduck said:
-Be prepared to wait a while while all that bloat and user apps optimize in ART!!
-Put your internal sd card data you pulled earlier back on your phone
-Cry now, because its a nice build and your stuck without root. No more saving your app data with Titanium or removing the load of ****e Verizon has put into it...... unless a root method is found.
-You can KDZ or TOT back to stock, re-root, bump recovery, flash 12b radio, and restore your backup if you can't live without root....which I will be doing again shortly because my OCD won't allow me to function with apps like NFL mobile embedded in my phone!! Just wanted to outline a method for you guys.
Click to expand...
Click to collapse
So there you have it, you're on Verizon official stock Lollipop (23A) for the G3! Now, there's a lot of bloat on there, which you can disable at will. This is a list of apps that are safe to disable, courtesy roirraW "edor" ehT and typed up by yours truly.
Can Be Uninstalled said:
Farmville
iHeartRadio
Click to expand...
Click to collapse
Can Be Disabled said:
Amazon
Amazon app suite
Amazon Kindle
Amazon MP3
Appstore
Audible
Cloud
DT Ignite
FamilyBase Companion
Favorite Contacts Widget
FIle Manager
Google Play Books
Google Play Games
Google Play Movies & TV
Google Play Music
Google Play Newsstand
Google+
LG TTS+
Message+
Music
Music
My InfoZone
My Verizon Mobile
NFL Mobile
SLacker
Support & Protection
Verizion Location Agent
VZ Navigator
Click to expand...
Click to collapse
After disabling most of that (I think I left one or two I use on, like G+, Google Books, etc), my G3 is happily up & running without issue. Some have discovered issues with their installs.
The only issue I've had is gmail not syncing on WiFi. I've tried everything I (and the community) can think of and am unable to fix the no-notifications-on-WiFi bug. Unfortunately I'm not alone, but it doesn't affect everyone. So, be forewarned, this is a semi-widespread bug. Everything else I experienced about this build is absolutely wonderful, save for that one bug.
Once you're done, you should be greeted by some notifications similar to these...and a software info screen that looks like this. With the bloat disabled, Antutu treated me well with a score over 41K. That's without any tweaking at all obviously since there is no root yet. I only miss two things about root - Titanium Backup and the ability to change DPI (to my preferred 600). Aside from that and the bloat (which is disabled), I'm quite happy as it is.
There you have it folks...if you want to be an early stock Lollipop adopter on the Verizon G3, this is how to do it! To answer the other inevitable question, yes you can downgrade back to 10B, root and install bumped TWRP without issue.
Special thanks to @annoyingduck for most everything how-to above, @justiz33 for the easy 12B-to-23A path, @roirraW "edor" ehT for the safe-to-disable list, Team Codefire for the files, @autoprime for IOroot & @quangnhut123 for the LG Flash Tool. If any one of you takes issue with how your posts are represented, please don't hesitate to PM me and I'll do what it takes to fix it.
Last, but not least, please do not quote this entire ginormous post in responses. It's unnecessary and insane. Thanks in advance. :fingers-crossed:
Do you have the MD5 for LG_VS985_12B-23A.dlpkgfile? (The update 12B to 23A MD5sum) i cant seem to find it but mine is
478a14b37b34e353722022e547fb2894
KShion619 said:
Do you have the MD5 for LG_VS985_12B-23A.dlpkgfile? (The update 12B to 23A MD5sum) i cant seem to find it but mine is
478a14b37b34e353722022e547fb2894
Click to expand...
Click to collapse
I just downloaded it again on my PC and checked the one on my phone. Both match: 85f01bfdefb4615328a29300a3625b64
Well this is new, and nifty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, fyi, disabling and re-enabling account sync did NOT fix my Wi-Fi gmail sync problem. Deleting and re-adding my Google account didn't either. Hate it, but I might have to try a factory reset. Perish the thought.
EDIT - Battery life is looking pretty darn good to me too.
I have the world's worst Windows machine and I'm having problems with the LG flash tool working. It just freezes every time I try and use it. I'm currently on the 11c build and with root and TWRP. Could I just restore the stock recovery, take the OTA to 12b, unroot within superuser, and then use the above method to get to lollipop?
jlvlawrence said:
I have the world's worst Windows machine and I'm having problems with the LG flash tool working. It just freezes every time I try and use it. I'm currently on the 11c build and with root and TWRP. Could I just restore the stock recovery, take the OTA to 12b, unroot within superuser, and then use the above method to get to lollipop?
Click to expand...
Click to collapse
If you're able to do that, I don't see why it wouldn't work; but I don't think it has been tried, at least that I've seen, so you'd be the guinea pig.
As far as flash tool, do you have any TOT flashing tools/programs installed? Are you sure the driver is properly installed? Try seeing if you can see your device with adb. It comes with the ioroot package linked in the OP. Enable USB debugging, plug it in and set it to internet/ethernet mode. Then launch a command prompt in the adb folder and see if you can see your device by typing "adb devices".
hokiealumnus said:
If you're able to do that, I don't see why it wouldn't work; but I don't think it has been tried, at least that I've seen, so you'd be the guinea pig.
As far as flash tool, do you have any TOT flashing tools/programs installed? Are you sure the driver is properly installed? Try seeing if you can see your device with adb. It comes with the ioroot package linked in the OP. Enable USB debugging, plug it in and set it to internet/ethernet mode. Then launch a command prompt in the adb folder and see if you can see your device by typing "adb devices".
Click to expand...
Click to collapse
Well, I wasn't able to OTA from 11c to 12b. I keep getting an error. My issue with the flash tool is it freezes before the flash process. It freezes at around 7 percent after plugging the phone in. Im pretty sure the drivers are correctly installed.
jlvlawrence said:
Well, I wasn't able to OTA from 11c to 12b. I keep getting an error. My issue with the flash tool is it freezes before the flash process. It freezes at around 7 percent after plugging the phone in. Im pretty sure the drivers are correctly installed.
Click to expand...
Click to collapse
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
hokiealumnus said:
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
Click to expand...
Click to collapse
I'll check when I get home and see if adb is working. Thanks for your help.
hokiealumnus said:
The only issue I've had is gmail not syncing on WiFi. I turned off, then re-enabled account syncing. I'll report back if that doesn't fix it when I'm back on WiFi.
Click to expand...
Click to collapse
A resolution has been had! Deleting my google account didn't work, nor did toggling sync. What worked was a kind suggestion by @Crsdr37 from the bug thread.
Crsdr37 said:
Use the built in LG backup app. Do a factory reset through settings and your sync issues should be resolved was for me anyways.
Click to expand...
Click to collapse
hokiealumnus said:
I'll give that a try, thanks! I honestly just ignored the built-in backup and didn't realize it would do downloaded apps. That's quite handy. Thanks for the tip, I'll report back whether it works. :fingers-crossed:
Click to expand...
Click to collapse
hokiealumnus said:
Wow, that worked incredibly well; pretty much equally as good as TiBu. Seems it fixed my gmail-on-wifi issue too. Thanks for the tip!
Click to expand...
Click to collapse
Like I said there, that thing is just as good as TiBu. Now the only real reason I miss root is the inability to change DPI. Sure, I'd rather have it de-bloated than have to disable a bunch of stuff, but disabled is nearly as good. I'm very pleased with this build.
Now @hsbadr & @HolyAngel are working diligently to try and get a custom stock ROM going for us, but in the mean time I'm happy to stick it out on unrooted stock. For now.
Thanks - this worked great. Software status says modified, is there a way to change that back since we're stock again?
hokiealumnus said:
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
Click to expand...
Click to collapse
So this is where I get stuck within the flash tool.
Ignite023 said:
Thanks - this worked great. Software status says modified, is there a way to change that back since we're stock again?
Click to expand...
Click to collapse
Huh...good question. Following the path above, mine says Official. Screenshot is here. You're not the first to report that though, so I'm not really sure what makes the difference, sorry.
hokiealumnus said:
Huh...good question. Following the path above, mine says Official. Screenshot is here. You're not the first to report that though, so I'm not really sure what makes the difference, sorry.
Click to expand...
Click to collapse
I don't know if this is the case here, but I think I've noticed even someone's rooted and they successfully unroot and restore stock everything, something is left behind and the status is modified, whereas if going straight from completely stock to 23A results in Official.
Sent from my VK810 4G
roirraW "edor" ehT said:
I don't know if this is the case here, but I think I've noticed even someone's rooted and they successfully unroot and restore stock everything, something is left behind and the status is modified, whereas if going straight from completely stock to 23A results in Official.
Sent from my VK810 4G
Click to expand...
Click to collapse
Very interesting. Using the method in the OP I was indeed rooted on 10B to install my apps with TiBu, then the upgrade to 12B took root away (leaving the apps). I wonder if it has to do with the method for root? Could stump root be different than ioroot maybe?
@jlvlawrence, what method did you use to root on 10B?
hokiealumnus said:
Very interesting. Using the method in the OP I was indeed rooted on 10B to install my apps with TiBu, then the upgrade to 12B took root away (leaving the apps). I wonder if it has to do with the method for root? Could stump root be different than ioroot maybe?
@jlvlawrence, what method did you use to root on 10B?
Click to expand...
Click to collapse
Mine's on official. I wasn't sure until I checked. I had my apps installed with Titanium Backup under 12B before I flashed the OTA. After trying it out I found my WIFI was constantly trying to turn on, so I did a factory reset and it was good after that.
I used Stump under 10B, for the record.
My phone overall seems snappier from the factory reset. It's probably a good idea for folks to so, period.
KDZ to 10B, root & restore apps, KDZ to 12B, initiate OTA to 23A, backup with LG utility, factory reset, login and restore from LG backup.
Sounds like a lot, but it is worth it, at least IMHO.
hokiealumnus said:
My phone overall seems snappier from the factory reset. It's probably a good idea for folks to so, period.
KDZ to 10B, root & restore apps, KDZ to 12B, initiate OTA to 23A, backup with LG utility, factory reset, login and restore from LG backup.
Sounds like a lot, but it is worth it, at least IMHO.
Click to expand...
Click to collapse
Doesn't 12B have the LG Backup too? Save restoring with TB if so. Might have to play with this.
Huh, not sure.
...and darnit, not getting notifications again. There must be something in the backup. I'll try it again and only back up my apps with nothing else and see if that fixes it.
I know it successfully got an email before restoring the backup. Hmm. Might have to just download the apps fresh the lollipop way. Hate to lose that data though.
hokiealumnus said:
Huh, not sure.
...and darnit, not getting notifications again. There must be something in the backup. I'll try it again and only back up my apps with nothing else and see if that fixes it.
I know it successfully got an email before restoring the backup. Hmm. Might have to just download the apps fresh the lollipop way. Hate to lose that data though.
Click to expand...
Click to collapse
Keep us posted if you make any progress on eliminating the quirks.

Verizon rooted/unlocked - deleted "My Verizon" system app now stuck on boot

Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
water- said:
Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
Click to expand...
Click to collapse
Early on with the verizon V30 roms I found that uninstalling some of the bloatware caused boot loops. From then on I just froze them; doesnt help your space situatuon though...
If no other suggestions, you could try a dirty flash of the ROM you were running (assuming you flashed TWRP zip).
I believe you'll need MyVerizon anyway, as this is what enables VOLTE and VOWIFI on Verizon (for me, at least). So I would not recommend removing it anyway.
Granted, you're past that. I would think that dirty-flashing the ROM should restore it, potentially? That could be one way to get back to running. Another way might be to reload the APK somehow. You might need to use TWRP to do that, unless there's another way to do it from a TiBu backup? If I can help in some way (I'm on VS996) I'm happy to try.
Unless you actually deleted the apps from System, it's almost certain that a Factory Reset will solve it. But I can understand your reluctance.
I'm not sure a dirty flash will help, since the problem is your data partition. You already tried deleting cache (I presume in TWRP).
And I agree that if you could somehow reload the apk, that might do it. Does ADB install work in TWRP, despite no OS? If so, that's worth trying. First pull the apks you removed from System to your computer, then run adb install apk-filename.
But FIRST make a full TWRP data backup of what you have now!
If you have to Factory Reset, you can use TiBu to restore your user apps from that backup. I haven't tried that in years, but I assume TiBu still has this feature.
Fingers crossed for you :fingers-crossed:
And for others who see this: Careful, selective debloating IS possible, but it always starts with a full backup: TWRP if rooted, otherwise LG Backup, (which saves app data and most OS settings).
Thanks all for responses, appreciated so much. In a bit of a pinch as I needed my phone for a backpacking trip last weekend, I just moved forward as best I could on Friday. Generally I tweak my phone enough to unlock/root then let it be. I guess I got greedy/complacent try trying to de-verizonify it and clear some space as much as possible.
Two things
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
I'm on 30c version of PIE and keep getting bugged to install a system update which I keep putting off because I'm leery of that..but I can't freeze the process without root.
Also because I flashed the stock OS, that means I lost the custom recovery, I don't have TWRP anymore (this seems so, but looking for confirmation), right?
2) retrospect, and a question for future reference
After all this I realized like an idiot I had a TWRP backup made in 2018 after I first unlocked and rooted it. Just hanging out on my SD card, which I could have accessed via TWRP before I flashed the KDZ. If I would have restored that it would have re-installed the OS and retained my data. Is that considered a dirty flash though, like it might not have worked or had subsequent problems?
And secondly on the SD card, I found all the 'dank memes' and other downloads I was worried I'd lost, so most of the data loss tragedy :silly: was averted (main pics backup to cloud, learned that lesson after lg g4 hardware bootloop pain).
water- said:
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
Click to expand...
Click to collapse
With unlocked bootloader on Pie, here's how you reinstall TWRP (IF you are on firmware with fastboot flash commands). Yes, I made a standalone post for this -- but if you read it it's basically just Section 6 of WTF Instructions. However, I had to make a standalone post because too many people kept thinking they had to downgrade back to Oreo, etc.
So, you can reinstall TWRP on Pie if you have unlocked bootloader. The problem is you need to fastboot flash commands to do that. VS996 firmware does not have that, which is why VS996 owners have to TEMPORARILY convert to US998 in the first place to unlock bootloader, install TWRP and root. Yes, your bootloader is already unlocked, but on VS996 you don't have the necessary fastboot flash commands to reinstall TWRP.
Thus, you will need to go back to US998 firmware (flashing KDZ via Dev Patched LGUP) to get fastboot flash commands. You can do it the hard way (US998 Pie KDZ) or you can do it the easy way (US998 Oreo KDZ). With already unlocked bootloader, you don't need to go back early Oreo, you can go to last Oreo. I don't recommend flashing US998 Pie for this, as there's too many people who have trouble with US998 Pie (stuck on LG logo, etc). You just need to temporarily get fastboot flash commands, and get TWRP reinstalled.
That post I have linked in the first sentence is for unlocked Bootloader with fastboot flash commands, on any stock firmware (Pie, Oreo, even Nougat if you wanted that for some reason).
Once you reinstall TWRP, then you can go back to VS996 Pie firmware via TWRP flashable zip.
Thanks for your response, now and two years ago.. super appreciated
I only need to get to the point to put the phone in debug mode (with access to fastboot) to get TWRP installed after flashing the recent oreo kdz. After TWRP installed follow your instructions (thanks!) to flash TWRP pie..
I'll probably give it a go this weekend or tomorrow evening, but do you have a recommended link to US998 Oreo kdz? https://androidfilehost.com/?fid=1395089523397933445 is fine?
Whereafter I'll follow your instructions for installing it (using LGUP patched) at: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
In the ROM section, go to ChazzMatt's US998 Pie KDZ thread. It also has instructions for rolling back to Oreo. Follow them to the t.
Make sure to use the Pie-compatible LGUP version in there when you roll back, and install it exactly as described in that thread.
His US998 Oreo thread will have a download link for Oreo 20h (the latest Oreo). Otherwise it's easy to find on lg-firmwares.com.
Good luck to you
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
2) maybe related to the above, maybe (probably not) not.. and I realize magisk and other avenues might cover it these days but I'm trying to debloat the TWRP flashed VS996 ROM with Titanium Backup.. stuff like NFL and slacker radio, google music.. like I did on Oreo. But Titanium keeps giving me an error about 'can't find the apk' -- Ti says I have root. I have read a bit that Android 10 really packages the apps in there so it's not like you can just remove the ones you want. is this the case for 9 too?
suggestions for alternative tool if Titanium is kind of a dinosaur in that regard?
Thanks
Well done!
1) It's best to use Format Data in TWRP to avoid that mounting error. Unless you are certain you have no mounting problems, I would recommend doing that before spending more time setting up the OS.
2) Before trying to freeze apps with TiBu, see if they can be Disabled in the regular Apps menu. Most of the "optional" bloatware can. Of course make a TWRP backup before freezing anything with TWRP!
Water-, there is already a debloated Verizon 99630c rom out there somewhere, if you would like to try it. I'm on it now.
Sorry, I can't link it. It was made by micromod777. So do a search for him.
I also use tibu, but there is another app (?) out there called migrate that backs everything up. You might look for it and try it. (I did use it a month or so ago myself just to try it - - worked for me).
water- said:
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
Click to expand...
Click to collapse
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
ChazzMatt said:
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
Click to expand...
Click to collapse
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
water- said:
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
Click to expand...
Click to collapse
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
ChazzMatt said:
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
Click to expand...
Click to collapse
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
water- said:
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
Click to expand...
Click to collapse
Do you have encryption on? TWRP will show a mount error upon start, and prior to the passcode being entered.

Categories

Resources