I recently messed up my V30 H933 badly and it'll only boot to TWRP now (not even Download Mode is working), so I'm looking for someone using LG official FW and who'd be willing to run the following command on TWRP on either Nougat or Oreo:
Code:
ls -l /dev/block/bootdevice/by-name
I'm hoping that, with said command output, I'll be able to manually flash some stuff around on my phone that'll get the system booting again. Should I be successful, I'll write down a guide to help people who run into the same problem as well.
Thanks in advance.
From my experience with past snapdragon devices (LG G Pro and OP2) that had that problem: misc partition was corrupted
Flash a kdz (should reset that flag there), or (didnt try this on a V30, but works on a G6, so... i dont guarantee anything, could even brick your device) via terminal (adb or twrp built in):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Safer method should be to flash a kdz though...
SGCMarkus said:
From my experience with past snapdragon devices (LG G Pro and OP2) that had that problem: misc partition was corrupted
Flash a kdz (should reset that flag there), or (didnt try this on a V30, but works on a G6, so... i dont guarantee anything, could even brick your device) via terminal (adb or twrp built in):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Safer method should be to flash a kdz though...
Click to expand...
Click to collapse
I can't flash a KDZ because the phone won't go to Download Mode, it will only reboot to TWRP.
And I tried that command, it did nothing for me except stopping the phone from booting up when I connected it to USB.
GryphonBR said:
I can't flash a KDZ because the phone won't go to Download Mode, it will only reboot to TWRP.
And I tried that command, it did nothing for me except stopping the phone from booting up when I connected it to USB.
Click to expand...
Click to collapse
If you reboot to TWRP, what happens if you flash a US998 ROM?
Have you tried Master Reset to wipe everything?
ChazzMatt said:
If you reboot to TWRP, what happens if you flash a US998 ROM?
Have you tried Master Reset to wipe everything?
Click to expand...
Click to collapse
How can I flash a US998 ROM (I'm assuming the KDZ) when I can't access Download Mode? And yeah, I tried doing a full wipe and then flashing a couple of different ROMs I found here (Lineage, WETA and Boombox), none worked, I could see under /system that information had been populated, but trouble is that it would seem as though I need to repartition the whole memory and reinstall the system from scratch before it works again.
So, breaking news: found a flashable ZIP that fixed my phone from the ground up. Managed to, luckily, get it back to working.
GryphonBR said:
So, breaking news: found a flashable ZIP that fixed my phone from the ground up. Managed to, luckily, get it back to working.
Click to expand...
Click to collapse
Good!
GryphonBR said:
So, breaking news: found a flashable ZIP that fixed my phone from the ground up. Managed to, luckily, get it back to working.
Click to expand...
Click to collapse
mind sharing where you found the zip? or the zip itself?
Just incase someone in the future has a similar problem
SGCMarkus said:
mind sharing where you found the zip? or the zip itself?
Just incase someone in the future has a similar problem
Click to expand...
Click to collapse
Absolutely! I used the ZIP I found on this thread to reflash the phone to stock ROM; I'm currently trying to get ahold of the guys who created the ZIP in the first place to try and figure out a way to do the same thing for my variant (H933), so I can reflash my phone with TWRP embedded since, apparently, lglaf can't be made to work with the V30 implementation.
Related
LG G3 Stuck in Recovery Fix
Background
This thread is to help those who get stuck in custom recovery every time they try to boot into the rom.. usually after trying to take an OTA. Now that we're all rooted and unlocked this might be needed soon. Inspired by IOMonster's [FIX] Installed TWRP and now you're stuck after OTA? thread for the LG G2. Sometimes wiping FOTA was not enough and wiping the misc partition was also needed. But wiping the entire partition isn't the best idea. I've made a flashable zip to automate this process to properly fix being stuck in TWRP/CWM due to "stuck fota" or "stuck misc"
This should work on the G2, G Flex, G Pro 2, G3... and possible other LG devices that use the MISC and also have a custom recovery.Fix
Flash LG_G3_Flash2FixStuckRecovery.zip to backup the current stuck fota/misc partitions and then fix them to allow proper booting.
Flashing LG_G3_Flash2FixStuckRecovery.zip creates a backup of your FOTA and Misc partitions in the /sdcard/FOTAnMisc_Backup/ folder.
1. Download the LG_G3_Flash2FixStuckRecovery.zip and place it on your phone.
You can use TWRP's MTP feature to copy it from computer to phone, use OTG w/connected storage containing zip or use adb push to get the file onto your phone...
Code:
adb push LG_G3_Flash2FixStuckRecovery.zip /sdcard/
DOWNLOAD FROM CODEFIRE HERE
2. Flash LG_G3_Flash2FixStuckRecovery.zip in recovery
or use adb commands below to fix boot issues..
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
[SIZE="1"]dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=256 count=1 conv=notrunc[/SIZE]
reboot
3. Finished
If you are still booting into TWRP/CWM then you may have accidentally flashed the custom recovery img to the boot partition slot instead of the recovery partition slot. Reflash the rom in TWRP/CWM which should fix the boot.img... or download the required boot.img, place on root of internal storage ( /sdcard/ ) and flash the boot.img in TWRP/CWM...
Code:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
reboot
Click to expand...
Click to collapse
word
I had this problem yesterday, spent hours trying to fix the situation. Had to flash stock firmware and all to solve the issue. NOW you bring this fix when i already fixed my phone lol
all good thanks for this, i will prob need this in the future
autoprime said:
LG G3 Stuck in Recovery Fix
Background
This thread is to help those who get stuck in custom recovery every time they try to boot into the rom.. usually after trying to take an OTA. Now that we're all rooted and unlocked this might be needed soon. Inspired by IOMonster's [FIX] Installed TWRP and now you're stuck after OTA? thread for the LG G2. Sometimes wiping FOTA was not enough and wiping the misc partition was also needed. But wiping the entire partition isn't the best idea. I've made a flashable zip to automate this process to properly fix being stuck in TWRP/CWM due to "stuck fota" or "stuck misc"Fix
Flash LG_G3_Flash2FixStuckRecovery.zip to backup the current stuck fota/misc partitions and then fix them to allow proper booting.
Flashing LG_G3_Flash2FixStuckRecovery.zip creates a backup of your FOTA and Misc partitions in the /sdcard/FOTAnMisc_Backup/ folder.
1. Download the LG_G3_Flash2FixStuckRecovery.zip and place it on your phone. You can use TWRP's MTP feature to copy it from computer to phone, use OTG w/connected storage containing zip or use adb push to get the file onto your phone...
Code:
adb push LG_G3_Flash2FixStuckRecovery.zip /sdcard/
DOWNLOAD FROM CODEFIRE HERE
2. Flash LG_G3_Flash2FixStuckRecovery.zip in recovery or use adb commands below to fix boot issues..
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=256 count=1 conv=notrunc
reboot
If you are still booting into TWRP/CWM then you may have accidentally flashed the custom recovery img to the boot partition slot instead of the recovery partition slot. Reflash the rom in TWRP/CWM which should fix the boot.img... or download the required boot.img, place on root of internal storage ( /sdcard/ ) and flash the boot.img in TWRP/CWM...
Code:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
reboot
Click to expand...
Click to collapse
I wish i saw this post yesertday............
I had this problem accidentally installing 10L wish I had this then. Had to run a fix in lg pc suite and start all over again. Great job tho. I know where to come next time I have this problem.
Help !
I have this very problem and I try to flash your file. Now I don't have any recovery any more (I had twrp 2.8.0.0) and the phone has black screen with only "fastboot mode started" on the top left corner. I'm lost, if anyone could help, I have lg g3 d855 with stock v10h installed.
Edit : problem solved, I managed to boot in download mode and flash a kzd rom using flashtool.
your the best! worked like charm!
Also wish i wouldve seen this, had to reflash stock software, lost 80%of my pics.... Thanks for posting, hopefully this will help others not repeat my mistake.....
Thanks!
Worked like a charm, accidentally took the OTA and this fixed things!
---------- Post added at 11:26 AM ---------- Previous post was at 11:18 AM ----------
Is this fix specific to the G3? I have a friend that is having the same issue on an unlock Moto X. Took an OTA update by accident and phone is stuck in a recovery boot loop.
Thoughts?
thanks bro your work is much appreciated
Will this method also work to restore download mode? (Can't connect to fastboot, windows can't recognize my phone).
received OTA file and prevently flashed LG_G3_Flash2FixStuckRecovery.zip
I just received a new OTA file from LG and prevently flashed LG_G3_Flash2FixStuckRecovery.zip.
This created 2 files named stuckfota.img and stuckmisc.img in /sdcard/FOTAnMisc_Backup/ folder.
But when I lanched OTA installation, I get stuck in TWRP. What did I miss ?
How can I have OTA installation finished ? Thanks
So I've been at it for quite a while. The zip.file is on the internal sdcard. went to instal in twrp, selected the file and flashed. got a Zip signature verification failure: 1 Error flashing zip ' /sdcard/LG_G3_Flash2FixStuckRecovery.zip'
Any suggestions are much appreciated. Meanwhile still searching
Thanks
After trying different things I found this and it worked.
http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
This worked to allow me to boot
What caused the issue? I didn't accept the OTA and even blocked it in the phone menu
nest75068 said:
This worked to allow me to boot
What caused the issue? I didn't accept the OTA and even blocked it in the phone menu
Click to expand...
Click to collapse
Same thing happened to me. I disabled it in the phone menu as well and when I got up today it was on TWRP.
Luckily I found this.
Yep
Mine did the same BS. Blocked the OTA as well as the notification. Woke up this morning to this crap.... Thank you for the fix!!! WOOT!
MizSxxyBych said:
Mine did the same BS. Blocked the OTA as well as the notification. Woke up this morning to this crap.... Thank you for the fix!!! WOOT!
Click to expand...
Click to collapse
Same thing happened to me this morning... Is there a way to for sure block this update and this happening again?
same thing to me also. drove to work listened to pandora all the way. clocked in and all i see is team win screen. this fix worked great. hope i can do a nandroid backup now.
nest75068 said:
What caused the issue? I didn't accept the OTA and even blocked it in the phone menu
Click to expand...
Click to collapse
From what I understand, AT&T forced an update lastnight, causing the issue for many of us. (of course, i'm only speaking for AT&T users)
I guess I'm SOL since my partition is encrypted?
Thanks for this. Wish I did a better search before I restored back to stock then re-rooted. Lost all that temporarily important personal data. Glad I know this is here now so I can use it if I foolishly click "Update now" again.
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
ezugaru said:
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
Click to expand...
Click to collapse
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
Hi, this is what i used to downgrade : http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Hope it helps, i'm at the office now, so when i get home I'll check where i got the resources to downgrade since i used my personal computer to do it.
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
ezugaru said:
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
Click to expand...
Click to collapse
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
gypsydanger said:
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
Click to expand...
Click to collapse
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
ezugaru said:
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
Click to expand...
Click to collapse
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
gypsydanger said:
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
Click to expand...
Click to collapse
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
ezugaru said:
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
Click to expand...
Click to collapse
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
gypsydanger said:
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
Click to expand...
Click to collapse
Did you give terminal root permissions by issuing the SU command and then granting the permissions on the phone?
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
gypsydanger said:
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
Click to expand...
Click to collapse
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
roirraW "edor" ehT said:
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
Click to expand...
Click to collapse
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
gypsydanger said:
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
Click to expand...
Click to collapse
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
bweN diorD said:
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
Click to expand...
Click to collapse
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
is there a specific version of twrp I need for that nightly?
gypsydanger said:
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
I'm attempting to wipe recovery again and try CWM to see if that will work.
Click to expand...
Click to collapse
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
bweN diorD said:
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
Click to expand...
Click to collapse
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
gypsydanger said:
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
Click to expand...
Click to collapse
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
gypsydanger said:
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
Click to expand...
Click to collapse
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
roirraW "edor" ehT said:
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
Click to expand...
Click to collapse
it says update failed due to an error and you have to hit retry or it does nothing...unless I need to just do nothing.
edit: IT WORKS YAY...all I did was retry and retry (definition of insanity) and the /sdcard just appeared then the dd command worked and I'm in recovery now yayayayayay
edit: edit: I did take out my eternal SD card so I am going to guess and say that that was the problem from the get go...anybody have any thoughts on that??
I am trying to flash TWRP on 10B (was running 23C and did KDZ flash back to 10B). Rooted via Stump, installed BusyBox, TWRP Mananger and Official TWRP App. Since TWRP didn't appear to install TWRP I did some more research I read people had success with 'Partitions Backup' to backup stock recovery partition and then use 'Flashify' to install TWRP. So I downloaded the twrp-3.0.2-0-vs985.img and installed that to recovery after backing up stock. Next reboot takes me into TWRP. If I then boot normally and then shutdown and enter recovery again I'm back in stock recovery. So it's like the flash is temporary.
Anybody care to educate me about what I am doing wrong. I'm sure this was easier in the days of the 'all-in-one' root/TWRP installer but can't download that anymore and I'm tired of the updates and poor performance so want to try custom ROM's.
Any help would be appreciated. I am thinking maybe I need to install recovery again when booted into TWRP? Not sure.
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
skay said:
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
Click to expand...
Click to collapse
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
iBolski said:
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
Click to expand...
Click to collapse
Thanks for the reply iB. I only tried flashing with the VS985 img files. But I didn't start with one that specifically had the "bump" or "bumped" designation in the filename. I am wondering if the later version that I used doesn't actually install bump to recovery but it intended to be installed as an updated version of TWRP on a previously "bumped" recovery image? Sorry for getting into the weeds here but I actually just stayed rooted on 23C for quite a while until I couldn't take it anymore. I looked at moving up to G4, G5, V10 and V20 but it seems like the G3 is the best value LG phone for custom ROMs and hardware is still not bad overall.
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
skay said:
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
Click to expand...
Click to collapse
It's been a long time (over a year) since I last used TWRP on my G3 (which is now in the cell phone cemetery as it died last December), but I believe if you boot normally, hook your phone to your PC and use adb reboot-recovery, it SHOULD go straight into TWRP, but I could be wrong. Otherwise, factory reset is the only way to get to it. The normal "recovery" screen shows up first, from what I remember and you have to go that route to get to TWRP. You should always, always back up your phone whenever doing things like this anyways. I don't know if there is a way to "verify" that it is installed, so once again, backup everything first. Just in case.
Thanks for the help and the confirmation that the standard recovery is expected once it's installed. Based on videos I expected something different. But I tried it after backing up and it works fine. Now time to flash!!
My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.
Hey there,
it seems like it's a very bad day for me. After some problems with my psyche, which is nothing new, i decided to flash a new ROM. This is what always makes me happy, try out new features and just messing arround with the system. Turns out, today i messed to much but i think it shouldn't... Here's what i did and happend (coming from RR 7.0):
-downloaded Superior OS from https://forum.xda-developers.com/lg-v30/development/post-t3909765
-downloaded the GAPPS package (first time with AROMA)
-moved both files to the SD-Card
-backed up my data, wiped system, dalvik, cache, data, internal storage
-installed the Superior OS zip
-installed the GAPPS zip
This is where it all got messy. The zip didn't finished, it stopped after 2 seconds and the H930 rebooted directly to recovery. There was no screen with the LG standard boot screen, it went straight to recovery. I rewiped everything and i got an error message which said: can't wipe data partition because device or resource is busy. I tried to repair it via wipe > advanced > selecting data > change or repair filesystem and tried to resize, repair and change file system. it always returns the error that it can't mount the partition. After the script, TWRP returns script succeeded, but fails to mount /data.
If i try to install RR 7.0, the script returns E3004: This package is for device : v30,joan,h930; this device is .
After all, i can't restore the backup i had from AOSP extended. I tried to flash the following two files TWRP-JOAN_H930_OPEN_EU-21w.zip and H93020R(TWRP).zip which started with the error E: Legacy property environment did not initialize succesfully. Properties may not be detected.
TWRP Version: 3.2.3-7
I would appreciate any help on this topic, even if i'm one of the xda profits who don't really gives a thank to the threads an just tries out until my devices work as i want them to do (i'm just honest). It's not because i don't appreciate the work of the dev's, they do really nice work which deffinetly is too much for myself to do. I'm just a messy person when it comes to interpersonal relationships. I'm sorry for my kind of awkward english, that's how i am...
I don't have a lot of knowledge about programming itself but i know how to use adb and fastboot, since i had some issues with my HTC one M7 on which i wasn't able to restore the IMEI due to too much messing arround. I think i started a thread about it, but i got it replaced even with a custom rom installed for free which will be my driver for the next couple days.
Kind regards
mrstupidus
I'm still new to this phone but, can you use LGUP to reinstall stock. Then just start over.
Sent from my LG-US998 using Tapatalk
Thanks for the reply,
i would if I could access download mode (forgot to mention it), seems like i'm not able to since the device only boots to recovery, the LG V30 bootscreen never shows up.
It seems like my device data is corrupted or lost, since different scripts in TWRP report that I have no device number. Also if I shut down the device trough TWRP, it boots to TWRP again and makes no attempt to shut down. I haven't tried to access download mode, I had to go to bed for work today. I still have to go tomorrow but one night without sleep will be worth it.
As far as I remember I have a backup of my EFS lying around, I will try to flash it this evening. I'll keep you guys updated if I find a way to get my v30 working, since it could help others too.
Regards
mrstupidus
mrstupidus said:
Thanks for the reply,
i would if I could access download mode (forgot to mention it), seems like i'm not able to since the device only boots to recovery, the LG V30 bootscreen never shows up.
It seems like my device data is corrupted or lost, since different scripts in TWRP report that I have no device number. Also if I shut down the device trough TWRP, it boots to TWRP again and makes no attempt to shut down. I haven't tried to access download mode, I had to go to bed for work today. I still have to go tomorrow but one night without sleep will be worth it.
As far as I remember I have a backup of my EFS lying around, I will try to flash it this evening. I'll keep you guys updated if I find a way to get my v30 working, since it could help others too.
Regards
mrstupidus
Click to expand...
Click to collapse
Have you tried going into download mode manually with the hardware buttons?
Press and hold the Volume Up key on your LG V30.
While still holding this button connect your phone to the USB cord on your computer.
The download mode should now be displayed on your device.
You can release the Volume Up key and resume the update / downgrade operation.
Click to expand...
Click to collapse
You are going to have to have to flash boot and system via fastboot:
* Download the ROM you want to flash and extract it. It will have boot.img or boot.image ... boot.something (depends on the ROM), and system.SOMETHING.
* Open an elevated command prompt in the directory you extracted the ROM in.
* From TWRP choose reboot / bootloader. If it wants to be a PITA and reboot back to TWRP, then you will have to wait till the phone dies and then use the vol down + plug in the USB cable method
* In the command prompt type:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot boot boot.img
Obviously replace boot.img and system.img with the names of the boot and system files.
To solve your /data issue (and you might want to do this first actually):
While in TWRP
Code:
adb shell
umount /data
umount /sdcard
mkfs.ext2 /dev/block/bootdevice/by-name/userdata
Repeat those two umount, and that is umount NOT unmount, until you get an error. If it isn't unmounted, when you try to format it, mkfs.ext2 will throw an error.
-- Brian
runningnak3d said:
You are going to have to have to flash boot and system via fastboot:
* Download the ROM you want to flash and extract it. It will have boot.img or boot.image ... boot.something (depends on the ROM), and system.SOMETHING.
* Open an elevated command prompt in the directory you extracted the ROM in.
* From TWRP choose reboot / bootloader. If it wants to be a PITA and reboot back to TWRP, then you will have to wait till the phone dies and then use the vol down + plug in the USB cable method
* In the command prompt type:
Code:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot boot boot.img
Obviously replace boot.img and system.img with the names of the boot and system files.
To solve your /data issue (and you might want to do this first actually):
While in TWRP
Code:
Code:
adb shell
umount /data
umount /sdcard
mkfs.ext2 /dev/block/bootdevice/by-name/userdata
Repeat those two umount, and that is umount NOT unmount, until you get an error. If it isn't unmounted, when you try to format it, mkfs.ext2 will throw an error.
-- Brian
Click to expand...
Click to collapse
Thank's a lot for you're efforts, it turned out that i didn't needed to flash the system.img and boot.img
ChazzMatt said:
Have you tried going into download mode manually with the hardware buttons?
Click to expand...
Click to collapse
Thanks a lot too for you're effort's, this really helped me out in a unecpected way
So here's what the issue was: a corrupted Gapps package. It failed to install and was still active in the recovery while the recovery "rebooted" (it just flashed off and started again with no normal boot between, kind of awkward to explain). The Phone itself never really rebooted into recovery, i have no idea how that happened. The /data partition was still in use from the Gapps script, but the script wasn't visible anymore and i was able to use the recovery as normal. So i ended up with an error everytime i tried to install a zip, restore a backup or wiping the /data partition.
Something i forgot yesterday in the spiral my mind was, forcing the phone to shut down via holding the power and volume down button. I then booted to recovery and i was able to wipe the /data partition. I then tried to install RR and the script suceeded with no error, then the Gapps package with AROMA and i was at the same point as yesterday. So forcing the phone to shut down and back to installing RR now without Gapps. I'm now going to install a .KDZ to start from the original firmware, so i can update the whole firmware and then moving on to unlock the bootloader and install TWRP and a rom with the working Gapps package i have
Thank's a lot for the help
Regards Simon
PS: I hope i will be more focused the next time i encounter issues with my phone and myself, this thread probably put's me in the place i deserve :silly:
That's crazy, I made the exact same mistake you did just now and I was just about stumped on what to do.
Thanks for saving me from a small panic attack, the Power + Vol (-) did the trick.
i tried to convert my sprint v30 to h930 and worked but since i didnt get signal decided to convert to us998 but know it dosent relock the bootloader and when i reflash our restore it gets to setup menú and reboot… i can enter download,fastboot and recovery but dont seem to stop it from rebooting..i dindt want to start a new thread.help please
dami00976 said:
i tried to convert my sprint v30 to h930 and worked but since i didnt get signal decided to convert to us998 but know it dosent relock the bootloader and when i reflash our restore it gets to setup menú and reboot… i can enter download,fastboot and recovery but dont seem to stop it from rebooting..i dindt want to start a new thread.help please
Click to expand...
Click to collapse
It'd be better if you provided the roms and versions you were using.
In between tho, try flashing the last US998 rom you used again but in refurbish mode instead of DL. I had an almost similar bootlooping issue last night and 2nd refurb flash got it to stop.
dami00976 said:
i tried to convert my sprint v30 to h930 and worked but since i didnt get signal decided to convert to us998 but know it dosent relock the bootloader and when i reflash our restore it gets to setup menú and reboot… i can enter download,fastboot and recovery but dont seem to stop it from rebooting..i dindt want to start a new thread.help please
Click to expand...
Click to collapse
Why would you try to convert LS998 to H930? North America variant should only be cross flashed to other North America variants, when using LGUP. Through LGUP, you can't completely Frankenstein a North American phone to a non-North American phone and at the worst you will have a brick.
You need to read the Frankenstein instructions on how to convert LS998 to US998. You either didn't flash US998 Nougat first or you didn't do the Master Reset step in between Nougat and Oreo:
ChazzMatt said:
FRANKENSTEIN - CONVERTING ANY NORTH AMERICA V30/V30+ (except T-mobile H932) TO US998 OREO
SHORT VERSION:
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) THEN open patched LGUP and flash NOUGAT US998 to DL PARTITION. In the pop up box "Select All". Use the attached patched LGUP in this post.
3) Master Reset (post 101)
4) Flash Oreo US998 in LGUP UPGRADE MODE. (Make SURE you are choosing Oreo US998 and not accidentally re-flashing Nougat US998 again!)
(For bootloader unlock purposes, use the US998 KDZ versions with pre-July 2018 security patch: 20a or 20b. You can always update to newer US998 firmware later, AFTER bootloader is unlocked.)
5) DONE.
NOTE: For Canadian H933 to convert to US998, @cre4per says you have to use DL Partition for both stages (Nougat and Oreo KDZ)
Click to expand...
Click to collapse
Those instructions work for all North American variants -- except T-mobile H932 -- but were written specifically with screenshots while me personally doing Sprint LS998.
________
neocyke said:
In between tho, try flashing the last US998 rom you used again but in refurbish mode instead of DL. I had an almost similar bootlooping issue last night and 2nd refurb flash got it to stop.
Click to expand...
Click to collapse
Refurbish has its uses. But to be honest I think you just didn't follow the Frankenstein directions. Master Reset stabilizes the bootlooping when flashing US998 Nougat before then flashing US998 Oreo. Has worked for everyone for over a year.
Unless the phone you got which you said was already Chinese Frankensteined was messed up due to whatever they did to it.
ChazzMatt said:
Refurbish has its uses. But to be honest I think you just didn't follow the Frankenstein directions. Master Reset stabilizes the bootlooping when flashing US998 Nougat before then flashing US998 Oreo. Has worked for everyone for over a year.
Unless the phone you got which you said was already Chinese Frankensteined was messed up due to whatever they did to it.
Click to expand...
Click to collapse
Honestly, i gots no idea how they did it and didn't really care at that point. Just needed to get the phone working again.
I actually did the master reset. Several times in fact. Never worked once. Longest it'd hold is for me to input wifi pw. It was the only other thing i could get to other than download mode.. I got the refurb step from either this or the WTF thread. Someone else had the same problem and refurb was their fix. Just so happens same for mine.. So, yeah..
I figured it out,but bricked that one lucky I have a spare and I didn't brick that one....but it wasn't de lg up our software. Through the process of reverting electricity went off in the process of flash and now is on black screen oh well
Is there a way to fix the bricked LG v30?