Related
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
ipsmaxes said:
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
Click to expand...
Click to collapse
First step: Don't panic!
Second step: Tell us which version of the G2 you have (carrier) and which update you had on before things went south, and also which version of TWRP you have.
Third step: Please explain what you mean by it not turning on but plugging it into the PC shows odd things.
Does that mean you CAN still get into recovery? Can you get to download mode? But either way, just stay calm. I just helped my buddy with the ATT version fix his phone from a similar issue a couple of days ago and I have also played with the Sprint version quite a bit and am familiar with LGs in general. Lemme know these things and I can help get you back on the right track.
Can you get into recovery mode?
If you can, try the factory reset and reboot your device.
Does your phone connect to adb?
If so i guess you could flash a fresh rom from there.
Correct me if i'm wrong, i am a new user with slight experience.
Same Thing Happened to Me
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
alferdjeffers said:
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
Click to expand...
Click to collapse
Probably would be best to start your own thread. However, what update were you on? I'm hoping that you do have the Verizon version of the G2? What error is on the screen? But generally speaking, you should be able to boot to the software update mode and re-install the stock OS with the kdz file, for most G2 things. I haven't worked on a VZW one though, only Sprint and T-Mobile ones and they're all a bit different.
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Ilikecheese said:
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Click to expand...
Click to collapse
you could try putting the sd in your pc to put the rom back on it, then back and try flashing. if that fails, sounds like its toast.
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Ilikecheese said:
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Click to expand...
Click to collapse
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Jewveeski said:
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Click to expand...
Click to collapse
thank you so much for the help (; ill let you know if i succeed
I think you will be okay, maybe try LG Flashtool and usb flash back to stock if those don't work.
I got it. Put the Rom in sd and it worked perfect. Whooo
Whew!..congrats.:good:
For some reason I can't flash from recovery menu..failed to mount sd/card, unknown error 150...
Maybe your SD is formatted in a file system twrp doesn't recognize? I had to reformat my 64gb to fat. I used twrp's built-in advanced wipe function to change external SD file system to fat, others have used a pc-based tool from ridgecomp.
You end up with the couple GB maximum individual file size limit, but I just copied my 11c 2.8gb system.img onto it without any trouble.
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
richsapf said:
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
Click to expand...
Click to collapse
You might be on the 11C update. Try downgrading (there's a thread in here somewhere) to 10b and you should be solid. I don't know if those numbers are correct, but check your build number.
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
B-Nice_88 said:
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And this check this for blocking an OTA: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
richsapf said:
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
Click to expand...
Click to collapse
Never ever take an OTA if you're rooted. In the future, just get rid of the notification, and then come here. Better yet - after you root, disable updates entirely.
Also, another reason to not take an OTA is because often times there are anti-rollback code in them, just like there is almost always a root patch. The regular "usb back to stock" and all the current root methods don't work on 11C for that very reason, and you have to use the KDZ method instead. If you jump on an OTA too early and find out there isn't a way to get back to the previous version... you're stuck. That happened to tons of people on one of the Galaxys I heard, and it so happened that the patch was a very good one. I've heard that the people who took that OTA are still stuck with it.
For 11C, there were early reports of those that rooted, but did not Bump or edit the system, got lucky and sometimes kept root after the OTA. Have you used a root checker to confirm you don't have root? None of the root methods are going to work on 11C, but you might still have it. If you don't, or something else is messed up, you'll need to get back to 10B to fix it.
Edit: Also, you're going to want THIS thread, not the other two I posted!
I did unroot before ota.. the only way I could at that time, via simple root. I just wanted to get the OTA out of the way(dont know why)
I used root checker, says no root.. If I go back to 10B I will try KDZ; or can I use the LG flashtool and try again with that using port 41, the 10B .dll, and 10B TOT?
For now I will follow your link and do as instructed..
Thank you laura
richsapf said:
I did unroot before ota.. the only way I could at that time.
Click to expand...
Click to collapse
Did you do anything else when you had root? Change anything in the system at all?
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
richsapf said:
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
Click to expand...
Click to collapse
Awesome! And yes, the sd card needs to be reformatted as fat32 for TWRP to see it.
Now that you're back on 10B, you can get the 11C update again if you want using this. The 11C OTA already has a rooted, deodexed flashable zip.
I do have that exact Rom/zip on both internal and ext card. Is there a program in particular to format, or just any, and should I format via pc(hook up usb with Windows 7), or is there a good .apk app.
Also, is 64gigs in any way too much.
Could I go up to 128gigs provided I use fat32.
Should the allocation just stay default? It looks like I can go up to around 4 mbs. Is that a cache type thing.
Sorry I am bombarding all these questions. I love learning this stuff. Need a break from studying for comptia 801/802.
Last, where is the thank u button?
I have the Verizon LG G3 with build 12b installed (Was updated by the store when I purchased phone). Is there anyway to unlock the boot loader and root the device as is, or roll the device back to a previous build that is easily unlockable/rootable?
You should have posted in the q&a forum area.
Anyhow - if you want to root, and install a custom recovery (twrp), use the kdz method to get back to 10b:
http://forum.xda-developers.com/showthread.php?p=56484240
Then from this forum area install the bump/twrp from autoprime, and make sure to either freeze system updates or rename the two LGDMSClient files in /system/app. The freeze or rename is so new ota don't get pushed onto your phone after you get the custom recovery (twrp). Otherwise you'll needed the solution in the "stuck in custom recovery" thread:
http://forum.xda-developers.com/showthread.php?p=56061720
(It is handy to download the "stuck" zip onto your phone as a just-in-case. If you do get an ota, and your phone keeps booting to recovery, tell twrp to Install the zip to clear the ota files )
HTH!
I am trying that method now (actually before you replied) but the kdz file is taking for ever to download. Been running for 30 minutes and still showing 7 hours remaining. I have a really fast internet connection but that one file doesn't wanna download!
markfm said:
You should have posted in the q&a forum area.
Anyhow - if you want to root, and install a custom recovery (twrp), use the kdz method to get back to 10b:
http://forum.xda-developers.com/showthread.php?p=56484240
Then from this forum area install the bump/twrp from autoprime, and make sure to either freeze system updates or rename the two LGDMSClient files in /system/app. The freeze or rename is so new ota don't get pushed onto your phone after you get the custom recovery (twrp). Otherwise you'll needed the solution in the "stuck in custom recovery" thread:
http://forum.xda-developers.com/showthread.php?p=56061720
(It is handy to download the "stuck" zip onto your phone as a just-in-case. If you do get an ota, and your phone keeps booting to recovery, tell twrp to Install the zip to clear the ota files )
HTH!
Click to expand...
Click to collapse
Check post 150 in that thread. annoyingduck posted a second link
markfm said:
Check post 150 in that thread. annoyingduck posted a second link
Click to expand...
Click to collapse
I think I am in love with you, JK.....seriously though thanks a bunch....downloading the Mega link now and it seems to be going MUCH faster.
Did it work for you? I tried to downgrade, when phone said 100% it rebooted. I had a dark screen.... Went to the Verizon store, was told it was hard bricked. Haven't tried rooting my replacement yet.
Early adopter, got my phone in July, used the original ioroot, never had to revert.
The kdz method has had quite a few people who succeeded, based on what I read, no idea why it went bad for you. If you are gun shy, understandable, post 2 of annoying duck's thread has a link for the tot approach, supposed to be a slightly more pita way but not too exotic. Key is to flash any existing g3 drivers on your PC, install the proper things used by the tot method.
martinez5241 said:
Did it work for you? I tried to downgrade, when phone said 100% it rebooted. I had a dark screen.... Went to the Verizon store, was told it was hard bricked. Haven't tried rooting my replacement yet.
Click to expand...
Click to collapse
Anyway to downgrade without this happening? I want to run stock lollipop on my G3 but so far am stuck at the VS98512b update too
_AI_ said:
Anyway to downgrade without this happening? I want to run stock lollipop on my G3 but so far am stuck at the VS98512b update too
Click to expand...
Click to collapse
I did the kdz method. Omg you run the program and it starts don't click on any notifications, just let it run. Sorry about the late response.
Hey folks. I'm in need of some help, but need to provide some background info as it seems there might be a few ways to correct this.
Background
I had a recent bad Nandroid mess up a restore process which somehow led to me losing root. I was on XDABBEB's 47A stock rooted ROM for months, then went to try the 3.1.1 ROM recently. I found that I wanted to go back, then BOOM! Bad restore from my data NANDROID. Then I:
Got stuck in a boot loop.
Rebooted into recovery
Saw the LG Recovery
(Stupidly?) chose to wipe cache
Continued to boot from LG Recovery
Went immediately to TWRP
Wiped Data and caches
Rebooted
At this point, I got back into 47A, but obviously without any data. I soon found that, though SuperSU was installed, it wasn't working:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-rot - consult the relevant forums for your device!
Click to expand...
Click to collapse
At this point, I checked Root Checker app and, surely enough, it says I wasn't rooted.
I checked ADB and tried to su from the prompt ($) and
Code:
su: notfound
However, adb reboot recovery brings me to TWRP
I tried TOT'ing on my Windows 10 (x64) machine, but it wasn't working:
PID: FAIL
IMEI: Unknown
[23:59: 0] CrossDL [Unknown] to [VS985].SW ***The text on this line continues, but I can't read it***
00000064
Error: [23:59: 0] CrossDL [Unknown] to [VS985].
Click to expand...
Click to collapse
I'm lucky in that my phone is currently working fine. I'm on 47a with everything working fine ... just not rooted, which I would really like to be.
So, my question is, what should I do next? I know some options that I have, I just don't know what options I should try or in what order I should try them...I understand some of the jargon and background info, but I don't understand the true inner workings of rooting and therefore don't feel comfortable making these choices on my own.
So, to all of you people that are way more intelligent at this than I am...
Should I try restoring my rooted 49A backup from TWRP?
Should I try to flash SU binaries in TWRP?
Should I TOT from my work machine that is Windows 7?
Should I KDZ on Windows 10?
Thanks in advance for your collective help.
This inquiring mind wants to know!
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone. In that case, you must flash back to 10B via the TOT method. That way, you can then root with Stump and then install TWRP, flash the correct boot images, and then reflash XDEBs ROM.
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method. It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
iBolski said:
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone
Click to expand...
Click to collapse
Correct. xdebbeb's stock 47A on a non-K model
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method.
Click to expand...
Click to collapse
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
Click to expand...
Click to collapse
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
my.ads0 said:
Correct. xdebbeb's stock 47A on a non-K model
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
Click to expand...
Click to collapse
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
iBolski said:
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
Click to expand...
Click to collapse
I just want to make sure that you're aware that I am NOT on pure stock 47A. I'm on xdabbeb_stock_vs98547a.zip from here.
When I flashed back from his 3.1.1 ROM, I flashed to my backup of the above ROM, which had Root. The SYSTEM flash from my nandroid back to his version of 47A worked without incident, but the DATA flash of my nandroid failed, left me in a bootloop, after which I performed the actions outlined in my original post. That squarely left where I am now, with no root, but on his version of 47A (I never had the stock 47A on my device before) with TWRP as my recovery.
In the end, I'm game for trying different things, but ideally, I'd like to try the least invasive method (trying to flash SuperSU in TWRP?; trying to flash my xdabebb 3.1.1 version?) ) before trying any other method or going to the extreme method (TOT'ing). I just am trying to avoid TOT'ing since my phone IS working AND the fact that I would have to do that at work. It would suck to go from a working phone to a broken phone without being able to fix it without knowing that I tried all of the least invasive methods first. I just need guidance from people like you as to what will or won't work in my situation.
The reason for this post is that I wasn't sure that you were aware I wasn't on pure stock 47A, but on xdabebb's version, which maybe you had overlooked and offered me more options? If you were aware of that and everything above is irrelevant, then I'm cool with that. Just tell me so. I just didn't want that fact overlooked.
Thanks again for entertaining my inquisitiveness, iBolski.
Well, trying to install the SuperSU binary zip from TWRP didn't work. That got me flashing blue & red lights. I tried restoring my XDABEBB 49A 3.1.1 install and that didn't help either. Both TOT & KDZ methods are failing on my PC (Windows 10) with both not able to read the phone properly (can't see imei). I will maybe try to uninstall the drivers or just wait until Monday to try my windows 7 machine at work.
Oops.
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
my.ads0 said:
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
Click to expand...
Click to collapse
Awesome. I saw your earlier post about being on XDEBB but that didn't matter. You were at a point that flashing back to 10b was your best option to get back to XDEB. That's why I kept saying you needed to flash back to 10B if you wanted to get back on XDEBB because where you were at that point was messed up, so it was just best to flash to 10b clean.
Glad you got it all worked out!
I tired a search and the only similar thread i found was someone who was able to boot into twrp. I am not able to do that. over a year ago i rooted my phone. but i haven't had any issues. out comes this stupid update and my phone tried to install it and failed. since then I've had issues so i figured i'd just reset the phone. I go to pull up adb and adb will force my phone to reboot but does not recognize it after its in bootloader mode. Okay weird also will show my phone in adb when i type adb devices, and will force it to reboot to firmware update, but never sees it. Figured I'd start back at square one Load up the patched version of LGUP, it recgnizes my phone when its NOT in bootloader mode, but the second i try it in bootloader it doesn't see my phone. I've tried deleting the adb Lgup the device drivers i've revoked debuggin authorization I just can't think of anyreson other than so messed up firmware that the phone would be doing this
Will doing the "button dance" get you into twrp?
What's the button dance?
deplorableone said:
What's the button dance?
Click to expand...
Click to collapse
Google LG V30 button dance.
Yeah all it does is restart my phone and when I get to the reset screen is just wipes my device
Yeah all it does is restart my phone and when I get to the reset screen is just wipes my device
deplorableone said:
Yeah all it does is restart my phone and when I get to the reset screen is just wipes my device
Click to expand...
Click to collapse
If you did it correctly, then that means you must not TWRP installed. If you had TWRP the button dance would boot to TWRP instead of wiping your phone. I hate doing the button dance as it takes specific timing to hit the buttons correctly.
In all my Guides there's only one scenario where I tell people they have no other choice than to use the button dance. In all others I stress other options.
I also tell people to never take an OTA update if you have TWRP installed.
ChazzMatt said:
If you did it correctly, then that means you must not TWRP installed. If you had TWRP the button dance would boot to TWRP instead of wiping your phone. I hate doing the button dance as it takes specific timing to hit the buttons correctly.
In all my Guides there's only one scenario where I tell people they have no other choice than to use the button dance. In all others I stress other options.
I also tell people to never take an OTA update if you have TWRP installed.
Click to expand...
Click to collapse
Yeah I woke up to the "update not installed" nag screen...I know i had twrp installed since it's how i installed magisk, and the VS99630c .zip. Those are still on my SD card. At least after wiping the phone it seems to be behaving properly, but magisk is now gone and being unable to boot into twrp means I can't put it back. It's all good though it's a 3+ year old phone figured if i can't fix it i'll just replace it. Didn't know if anyone had an experience like this with lgup and adb not recognizing the handset in download mode. Seemed like a strange quirk...
deplorableone said:
Didn't know if anyone had an experience like this with lgup and adb not recognizing the handset in download mode. Seemed like a strange quirk...
Click to expand...
Click to collapse
Yes, sometimes reinstalling drivers helps. Also trying a different computer.
Your bootloader is still unlocked, but because you are on Verizon firmware it's not giving you the scary warning. To reinstall TWRP and Magisk, using Dev Patched LGUP you would have to temporarily flash back to US998 firmware (Oreo would be best), then use go through Section 6 of the WTF Instructions to install TWRP, reformat internal memory, install Magisk. Then you could re-flash VS996 30C (until a TWRP flashable zip of 30d comes along). You would need to freeze the update files so this doesn't happen again.
ChazzMatt said:
Yes, sometimes reinstalling drivers helps. Also trying a different computer.
Your bootloader is still unlocked, but because you are on Verizon firmware it's not giving you the scary warning. To reinstall TWRP and Magisk, using Dev Patched LGUP you would have to temporarily flash back to US998 firmware (Oreo would be best), then use go through Section 6 of the WTF Instructions to install TWRP, reformat internal memory, install Magisk. Then you could re-flash VS996 30C (until a TWRP flashable zip of 30d comes along). You would need to freeze the update files so this doesn't happen again.
Click to expand...
Click to collapse
Yes i've been trying to just start back over at square one using the patched LGUP, but it doesn't recognize the phone. I've numerous cables and 2 different PC's and no luck yet. I am going to try and buy a new cable though since I just used the ones I've had around the house. Seems odd that the phone is recognized using the cables up until i place it into download mode though. Might try and clean out the ole charging port as well. Again i originally followed the instructions to a T and have had absolutely no issues but noticed i lost voice commands and my sms/mms were messed up, immediately after the failed update. the phone seems to be 100% now with no issues due to the wipe. SO it's not the end of the world if I can't figure it out, but more like a challenge of fixing it
If someone can capture and share that OTA update you received, you can flash it using LGUP in FOTA mode. This often restores a broken Download Mode, even if the system update itself fails due to the phone not being stock and/or lacking stock recovery.
LGUP FOTA mode works inside the OS (with the phone in File Transfer mode) and doesn't require working Download Mode.
Just a thought
Caveat: The purpose of this would ONLY be to fix your Download mode. However there is a risk it might actually mess up your OS (which is currently working). So if it doesn't fix your Download mode, you'll actually be worse off.
I have the exact same issue so you're not alone, I'm trying anything I can think of, lmk if you figure something out. It's weird it sees phone in desktop with phone booted then a glitch in download mode and it never pulls up. I'm due for a new phone anyway, the update slipped thru somehow, lost root and twrp, can't flash. I'll let you know if I figure it out as well. If Chazz don't know how to fix itwe might be out of luck.
cpete2112 said:
I have the exact same issue so you're not alone, I'm trying anything I can think of, lmk if you figure something out. It's weird it sees phone in desktop with phone booted then a glitch in download mode and it never pulls up. I'm due for a new phone anyway, the update slipped thru somehow, lost root and twrp, can't flash. I'll let you know if I figure it out as well. If Chazz don't know how to fix itwe might be out of luck.
Click to expand...
Click to collapse
Which model do you have, and which ROM are you on?
If you are "somewhat stock", on a model for which we have OTA files, you can force flash those using LGUP FOTA mode. This works inside the OS, doesn't require Download mode, and will often restore Download mode as the first thing -- even if the update itself fails because the phone isn't completely stock.
If you are on T-Mobile H932, we have a separate thread to help restore Download mode using OTA files and LGUP FOTA mode:
https://forum.xda-developers.com/lg-v30/help/h932-url-h932-pie-ota-file-t3991417/page7
And if you are on any model OTHER than
T-mobile H932, and you cannot find an OTA file, you can use the firehose and guidance in the thread linked below to re-flash the laf partition (Download mode).
https://forum.xda-developers.com/lg-v30/how-to/lg-v30-unbrick-guide-qualcomm-edl-9008-t4048661
I have a Verizon on 30c, I would like to make it to 30d, this phone started out as a ls998 sprint model, not that that matters idk. Yah I'm gonna try one of those mentioned routes to fix, I'm out of ideas.
cpete2112 said:
I have a Verizon on 30c, I would like to make it to 30d, this phone started out as a ls998 sprint model, not that that matters idk. Yah I'm gonna try one of those mentioned routes to fix, I'm out of ideas.
Click to expand...
Click to collapse
You're in luck then: If you're on Verizon 30c, it *should* offer you a 30d OTA update. And if you accept that, it *should* repair your Download mode as part of the update
The potential risk here is when you're not completely stock, the OTA probably won't complete. That's ok as long as it repairs your Download mode, since then you can re-flash with LGUP. But in case it *doesn't* repair your Download mode, you could theoretically be worse off. I haven't heard of cases where that happened, I'm just pointing out the potential risk.
Good luck to you :fingers-crossed:
Edit: No wait, if you started out as LS998, Verizon won't offer you the OTA. But I believe somebody captured the 30d OTA file and shared it in another thread (about the 30d). If so, you can force flash it with LGUP FOTA mode. Make sure the PC can see the phone as MTP (USB File mode) before attempting this.
TheDannemand said:
Which model do you have, and which ROM are you on?
If you are "somewhat stock", on a model for which we have OTA files, you can force flash those using LGUP FOTA mode. This works inside the OS, doesn't require Download mode, and will often restore Download mode as the first thing -- even if the update itself fails because the phone isn't completely stock.
If you are on T-Mobile H932, we have a separate thread to help restore Download mode using OTA files and LGUP FOTA mode:
https://forum.xda-developers.com/lg-v30/help/h932-url-h932-pie-ota-file-t3991417/page7
And if you are on any model OTHER than
T-mobile H932, and you cannot find an OTA file, you can use the firehose and guidance in the thread linked below to re-flash the laf partition (Download mode).
https://forum.xda-developers.com/lg-v30/how-to/lg-v30-unbrick-guide-qualcomm-edl-9008-t4048661
Click to expand...
Click to collapse
My friend was just looking for this information. Thanks
gimpy1 said:
Will doing the "button dance" get you into twrp?
Click to expand...
Click to collapse
Doin' the buttons in DL mode.