Related
I tried to use Yemenroot to root my phone and ended up stuck in a Boot recovery and no matter what I try I cant get out of it. What suggestions could anyone give me? Ive tried the factory reset option and the clear cache. neither helped. Thanks in advance!
Not sure exactly what you mean by "stuck".
Are you saying that every time it reboots it boots into the recovery?
If so, then:
- Pull the battery
- Reinsert the battery*
- Boot the phone by holding down Vol-Down+Home+Power*
When it asks you if you want to go into Download Mode, select Cancel (Vol-Down iirc)
The phone should boot into the regular ROM, albeit completely unconfigured, as you have already performed a factory reset (which wasn't needed btw).
If the Stock ROM won't boot you will have to flash the Stock ROM in Odin
*don't have the phone plugged in to a PC at this point or it will spontaneously reboot.
bftb0 said:
Not sure exactly what you mean by "stuck".
Are you saying that every time it reboots it boots into the recovery?
If so, then:
- Pull the battery
- Reinsert the battery*
- Boot the phone by holding down Vol-Down+Home+Power*
When it asks you if you want to go into Download Mode, select Cancel (Vol-Down iirc)
The phone should boot into the regular ROM, albeit completely unconfigured, as you have already performed a factory reset (which wasn't needed btw).
If the Stock ROM won't boot you will have to flash the Stock ROM in Odin
*don't have the phone plugged in to a PC at this point or it will spontaneously reboot.
Click to expand...
Click to collapse
Thanks for responding! Yes you are correct that it boots in recovery. Home+Power+Vol Down brings me up to a Warning screen, says if i want to download a custom OS to hit vol up, if I want to cancel press Vol Down. I press vol down and it puts me back into recovery boot again.
If you are familiar with YemenRoot maybe I just screwed up doing that and can still continue with that to fix it? I ran the program, choose Tar.1 in Oden and hit start. Went back to the command prompt and "pressed any key" to continue. It went to 2). Rooting, but never went any farther. The phone automatically rebooted but into recovery mode. That was where I thought something went wrong and stopped.
EDIT: I went back again and pressed vol up to see where it would take me. It takes me back to the downloading screen like it showed in one of the steps for the root. I ran tar.1 and tar.2 and was able to get the phone usable again. No luck with the YemenRoot though Tried going through to do it a second time and came up with the same issues. It just sits on (2) Installing root forever and the phone eventually reboots into Recovery again. Im not sure how to get Yemen to work correctly, and no one seems to respond in the yemenroot post that I found on here.
trizzypballr said:
Home+Power+Vol Down brings me up to a Warning screen, says if i want to download a custom OS to hit vol up, if I want to cancel press Vol Down. I press vol down and it puts me back into recovery boot again.
Click to expand...
Click to collapse
Well that's a little odd & unexpected.
[Edit] - Oops, I didn't initially see the part about you getting it working [Edit]
I can't help you out with Yemenroot, I've never used it. (But I suspect the stock ROM needs to be booting in order for it to work, so you are going to have to do the Odin Flash no matter what)
I can suggest that if you are going to keep trying w/ yemenroot, I would only minimally configure the (factory reset) stock ROM in case you end up back in the same spot again.
PS if you know how to create Odin .tar.md5 files, you could create a "reduced" stock flash for Odin containing only boot.img & system.img. That way you could "dirty flash" those two in Odin if you got in the same situation again... without needing to do a factory reset.
good luck
I flashed using odin N900VVRUEOF1_N900VVZWEOF1_VZW. It took the flash but is now stuck on RED Verizon screen. Ity is like it is doing something but not fully recovered?? Any suggestions?
bftb0 said:
I can't help you out with Yemenroot, I've never used it.
Click to expand...
Click to collapse
Then how in the world did you root your phone? I thought those were the only ways to get your device rooted?
RaaidR said:
Then how in the world did you root your phone? I thought those were the only ways to get your device rooted?
Click to expand...
Click to collapse
I used Kingo root when my phone was on MJ7 and I never upgraded thereafter.
Even now my phone is only on the MJE bootloader (it can be rolled back to MJ7).
The version of TowelRoot that I have (v3?) currently seems to work on all stock versions from MI9-NC4, but it wasn't yet released when I rooted.
I'm not planning on upgrading my bootloader past NC2 until such a time as I am going to sell the phone, or there is a way to upgrade only the bootloader components while preserving root in the ROM.* My motivation for that is quite frankly to avoid using the yemen root tool.
*So that the bootloader unlock can be performed immediately thereafter, to regain bootability of a custom recovery. IMO this should be trivial so long as OB6/OF1 bootloader will boot a rooted-stock kernel+ROM from 4.4.x (NC4, NJ6, NK1). Frankly I believe that to be more likely than a 4.4.x bootloader booting a 4.3.x rooted-stock kernel+ROM (MI9/MJ7/MJE).
bftb0 said:
I used Kingo root when my phone was on MJ7 and I never upgraded thereafter.
Even now my phone is only on the MJE bootloader (it can be rolled back to MJ7).
The version of TowelRoot that I have (v3?) currently seems to work on all stock versions from MI9-NC4, but it wasn't yet released when I rooted.
I'm not planning on upgrading my bootloader past NC2 until such a time as I am going to sell the phone, or there is a way to upgrade only the bootloader components while preserving root in the ROM.* My motivation for that is quite frankly to avoid using the yemen root tool.
*So that the bootloader unlock can be performed immediately thereafter, to regain bootability of a custom recovery. IMO this should be trivial so long as OB6/OF1 bootloader will boot a rooted-stock kernel+ROM from 4.4.x (NC4, NJ6, NK1). Frankly I believe that to be more likely than a 4.4.x bootloader booting a 4.3.x rooted-stock kernel+ROM (MI9/MJ7/MJE).
Click to expand...
Click to collapse
Why do you not want to use the yemen tool? The one for Windows 10 worked flawlessly for me.
RaaidR said:
Why do you not want to use the yemen tool? The one for Windows 10 worked flawlessly for me.
Click to expand...
Click to collapse
The ends don't justify the means.
No disclosure of method.
No prior or subsequent author activity on XDA
Use of a PC
No Windows 10 box that I am willing to expose to random executables from unknown authors on the internet.
bftb0 said:
The ends don't justify the means.
No disclosure of method.
No prior or subsequent author activity on XDA
Use of a PC
No Windows 10 box that I am willing to expose to random executables from unknown authors on the internet.
Click to expand...
Click to collapse
I for sure understand not wanting to risk it. I really didn't either but didn't have another choice other than to stay unrooted.
DjRenigade said:
I flashed using odin N900VVRUEOF1_N900VVZWEOF1_VZW. It took the flash but is now stuck on RED Verizon screen. Ity is like it is doing something but not fully recovered?? Any suggestions?
Click to expand...
Click to collapse
Use Jasmine ROM 6.1, it is based on OF1 and works fine.
Sent from my SM-N900V using Tapatalk
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.
So it was only a matter of time before I managed to hard brick my phone. Wouldn't you know it, I'm with one of the only carriers to not have a KDZ available?! #%^&^!
I was trying to update TWRP, but after flashing the phone went to the red triangle screen, then LG screen, then turned off. When I rebooted it went into what looked like Fastboot, but I cannot get it to return to that state now. I pull the battery, do the factory reset process, then get the red triangle, LG screen, then off. I can get the download screen, but that does me absolutely no good without a usable TOT or KDZ. FML.
What options do I have? I'm on a leased device with no way to restore with LGUP (which in my opinion is utter horse $hit). Last I remember, there was some progress being made on a TOT file, but I can't find the thread anymore. @me2151, @Team DevDigitel, @SaintZ93 -- any help, guys???
:crying:
So assuming you can't get to TWRP, right?
I had something similar to this and just kept trying to reboot recovery. Once rebooted into recovery I was able to plug into a computer and force it into fastboot mode.
Wish I had more stuff to help with.
fogame said:
So assuming you can't get to TWRP, right?
I had something similar to this and just kept trying to reboot recovery. Once rebooted into recovery I was able to plug into a computer and force it into fastboot mode.
Wish I had more stuff to help with.
Click to expand...
Click to collapse
No TWRP, No fastboot...just red triangles, LG Screen, then darkness, lol. Using the Volume Down/Power method results in the same...red triangle, LG, darkness. If only Sprint would provide a dang KDZ.
No worries though, man. I contacted Sprint tech support and they are sending me a new phone. I just played like I didn't know why it wouldn't boot and they immediately processed an advanced exchange. I should be getting a replacement V20 either tomorrow (hopefully) or Monday at the latest.
I'll probably still hang out in the forums, in case files are needed. But yeah, no more root for this guy.
Try to completely re root again using dirty santa.
SaintZ93 said:
Try to completely re root again using dirty santa.
Click to expand...
Click to collapse
Even without fastboot or TWRP--will that work???
bgibson72 said:
Even without fastboot or TWRP--will that work???
Click to expand...
Click to collapse
Follow the directions from beginning to end again, may help you require fast boot and twrp again. If not Ill see if the dirty santa maker will have ideas.
SaintZ93 said:
Follow the directions from beginning to end again, may help you require fast boot and twrp again. If not Ill see if the dirty santa maker will have ideas.
Click to expand...
Click to collapse
It's ok. I've already got them processing an advanced exchange. It's probably for the best since I want to be able to update OTA again and didn't really see much benefit in rooting at this point. The ROMs I was using were pretty close to stock anyway.
bgibson72 said:
It's ok. I've already got them processing an advanced exchange. It's probably for the best since I want to be able to update OTA again and didn't really see much benefit in rooting at this point. The ROMs I was using were pretty close to stock anyway.
Click to expand...
Click to collapse
If you run the dirty Santa or should get you back up and running, im speaking from experience. A seeks of formats flashes and wipes through adb.
Goose0121 said:
If you run the dirty Santa or should get you back up and running, im speaking from experience. A seeks of formats flashes and wipes through adb.
Click to expand...
Click to collapse
That would be nice, but I can't get adb anymore. I've tried, but the device is not recognized by adb OR fastboot via the 'devices' command. The only thing I can get is the firmware update screen, but that's useless on Sprint.
Hello to all. can anyone explain how to downgrade my lg g6 from android 8.0 to android 7.0. thank you all
Ala1101 said:
Hello to all. can anyone explain how to downgrade my lg g6 from android 8.0 to android 7.0. thank you all
Click to expand...
Click to collapse
Unlock BL and flash TWRP then Flash 7.0 based custom ROM
Sent from my SM-G950F using Tapatalk
Lg up e uppercat e flash 7.0 kdz.
menonmanjesh said:
Unlock BL and flash TWRP then Flash 7.0 based custom ROM
Click to expand...
Click to collapse
What are you talking about...
siggey said:
Lg up e uppercat e flash 7.0 kdz.
Click to expand...
Click to collapse
Correct, just flashing 7.0 in Uppercut. But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base.
romcio47 said:
What are you talking about...
Correct, just flashing 7.0 in Uppercut. But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base.
Click to expand...
Click to collapse
What are the steps to downgrading? I just bought my g6 and loved it. then i upgraded to oreo 8.0 cause the notifications were annoying me. but i HATE it and now im sad any help?
amyelizabeth said:
What are the steps to downgrading? I just bought my g6 and loved it. then i upgraded to oreo 8.0 cause the notifications were annoying me. but i HATE it and now im sad any help?
Click to expand...
Click to collapse
You may want to look into anti-rollback numbers, because if you have one at a certain value, downgrading may brick your phone. I don't remember from the top of my head. Please be cautious and do this at your own risk.
Look for "LGUP 1.14" and "LG Uppercut" on Google and download them. The first search results should be what you're looking for.
Install LGUP first. Once that's done, put your phone in download mode by powering down and then turning it on while holding volume down and the lock button (the fingerprint sensor). Next, connect it to your computer.
Open Uppercut (after extracting it) with administrator privileges. It will open LGUP. Have your KDZ ready somewhere easy to find, like your desktop.
You should have four options that you can tick off, one of which is "REFURBISH". Select it.
At the bottom, you will see a list. Select the first thing on the list and click on the three dots on the right. Select the KDZ. Finally, press start. DO NOT TOUCH YOUR PHONE WHILE IT IS DOWNGRADING! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS!
Once that's done, and ONLY when it says "finished" on LGUP's interface, your phone should boot at the set up screen.
Incidentally, I was after the exact same thing as the OP, and incidentally, my search led me to do exactly as "fegitoli" suggests: Downloaded Uppercut, downloaded the last 7.0 KDZ (H87011i_00_OPEN_EU_OP_0108.kdz), but then I tried to downgrade using the "Upgrade" option (sounds stupid when written I know). Process seemed to be complete, but since the phone started I get an error saying "Settings crashed, reopen" followed by "Settings keep stopping, close app". On the top left corner it says: "Secure start-up" and the phone is an airplane mode with no control over the notification bar or anything else minus power and volume buttons, so stuck there.
Don't tell me that in 8 years of modding various Android devices this will be my first brick?
fegitoli said:
You may want to look into anti-rollback numbers, because if you have one at a certain value, downgrading may brick your phone. I don't remember from the top of my head. Please be cautious and do this at your own risk.
Look for "LGUP 1.14" and "LG Uppercut" on Google and download them. The first search results should be what you're looking for.
Install LGUP first. Once that's done, put your phone in download mode by powering down and then turning it on while holding volume down and the lock button (the fingerprint sensor). Next, connect it to your computer.
Open Uppercut (after extracting it) with administrator privileges. It will open LGUP. Have your KDZ ready somewhere easy to find, like your desktop.
You should have four options that you can tick off, one of which is "REFURBISH". Select it.
At the bottom, you will see a list. Select the first thing on the list and click on the three dots on the right. Select the KDZ. Finally, press start. DO NOT TOUCH YOUR PHONE WHILE IT IS DOWNGRADING! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS!
Once that's done, and ONLY when it says "finished" on LGUP's interface, your phone should boot at the set up screen.
Click to expand...
Click to collapse
Its work? I flahsed lg g6 h870ds indian nuogat to h870ds twn...
Now i think to downgrade to official firmware indian nougat
Sent from my LG-H870DS using XDA-Developers Legacy app
mclisme said:
Incidentally, I was after the exact same thing as the OP, and incidentally, my search led me to do exactly as "fegitoli" suggests: Downloaded Uppercut, downloaded the last 7.0 KDZ (H87011i_00_OPEN_EU_OP_0108.kdz), but then I tried to downgrade using the "Upgrade" option (sounds stupid when written I know). Process seemed to be complete, but since the phone started I get an error saying "Settings crashed, reopen" followed by "Settings keep stopping, close app". On the top left corner it says: "Secure start-up" and the phone is an airplane mode with no control over the notification bar or anything else minus power and volume buttons, so stuck there.
Don't tell me that in 8 years of modding various Android devices this will be my first brick?
Click to expand...
Click to collapse
Not much I can help you with there. I made the same mistake with my G4 which resulted in a brick similar to yours. Hence, why I specified you use the REFURBISH option.
I'm sure other people in the modding forum can help you out. If nothing works, I'd like to pay my respects for you and your wallet.
fegitoli said:
Not much I can help you with there. I made the same mistake with my G4 which resulted in a brick similar to yours. Hence, why I specified you use the REFURBISH option.
I'm sure other people in the modding forum can help you out. If nothing works, I'd like to pay my respects for you and your wallet.
Click to expand...
Click to collapse
Ha! It was close but still my "Brick counter" reads zero The answer lied a couple of posts above in @romcio47 's post: "But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base."
I entered in stock Recovery and did a Factory reset from there, then the phone became again accessible from LGUP so I re-flashed the 7.0 KDZ and this time it booted fine!
Can i downgrade LS993 from android 8 (ZVB) to Nougat?
From today i am a happy Nougat user again for my H870 EU model
I've followed the exact instructions from @fegitoli,and i fortunatelly had the perfect result.
Here i have to mention one detail that probably gave me the desired result..
As it is mentioned in the instructions,i selected the "Refurbish" option,but when i pressed the start button,i got an error notification in LG UP display,saying that my kdz file can not be used for refurbish,so i cancelled the whole process without disconnecting my phone from the pc,but i closed the LG UP and opened Uppercat again.
Probably the "refurbish" option is something like a hard(factory) reset mode for the existing ROM.
Then i choose the "Upgrade" option and started the process again until i got the notification "completed" in LG UP interface.
After the phone started rebooting,i disconnected it from pc,waiting to complete reboot.
When completed reboot,i got an error saying "settings are not complete" and "safe mode start",but giving me the option "reset phone"..
Then i pressed "reset phone" and a second reboot followed..after that,it opened the first set up screen and everything went fine.
BE CAREFUL WHAT YOU DO AT YOUR OWN RISK..
I AM NOT RESPONSIBLE FOR ANY DAMAGE ON YOUR PHONE!!
P.S: Many thanks @fegitoli for his valuable help with his post!
Sent from my LG G6 using XDA Labs
granazias said:
Many thanks @fegitoli for his valuable help with his post!
Click to expand...
Click to collapse
No problem! Glad my instructions helped, because if they didn't, I would have caused a lot of trouble. Hopefully everything is working fine for you!
fegitoli said:
No problem! Glad my instructions helped, because if they didn't, I would have caused a lot of trouble. Hopefully everything is working fine for you!
Click to expand...
Click to collapse
Be sure that if one on a million something was going wrong,i was not intented to blame you..
What is everybody doing with his phone,is on his own responsibility.
After a lot of reading here and in other forums,that a lot of people had problems with bricking their phones,i was prepared for the possibility to brick mine too,but i was decided to take the risk.
Oreo,and especially the last June update,had disappointed me with the battery times,so i didn't have other option than to try the downgrade,and i am really happy that everything went fine.
Maybe more people now can do the same and take the most from this wonderful G6.
Regards!
Sent from my LG G6 using XDA Labs
granazias said:
Be sure that if one on a million something was going wrong,i was not intented to blame you..
What is everybody doing with his phone,is on his own responsibility.
After a lot of reading here and in other forums,that a lot of people had problems with bricking their phones,i was prepared for the possibility to brick mine too,but i was decided to take the risk.
Oreo,and especially the last June update,had disappointed me with the battery times,so i didn't have other option than to try the downgrade,and i am really happy that everything went fine.
Maybe more people now can do the same and take the most from this wonderful G6.
Regards!
Click to expand...
Click to collapse
Very glad to hear that!
Here's a little disclaimer I'd like to add. This should go without saying: YOU are responsible for what YOU do to YOUR phone. If you bricked it because you missed a step, it's not the instructor's fault. If everything is okay but the screen shuts off randomly, it's not the instructor's fault. Please mod responsibly and be prepared for failure, because things don't always work as they should.
mclisme said:
Ha! It was close but still my "Brick counter" reads zero The answer lied a couple of posts above in @romcio47 's post: "But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base."
I entered in stock Recovery and did a Factory reset from there, then the phone became again accessible from LGUP so I re-flashed the 7.0 KDZ and this time it booted fine!
Click to expand...
Click to collapse
Please can you tell me how to return Nougat from oreo. I have LG UP and I have official Nougat H870DSU10f_00_OPEN_HK_DS_OP_0803.kdz firmware downloaded. How to avoid brick and factory reset? Can I just refubrish from LG UP or I will have to do factory reset of the phone and "brick" at first?
Ferovac said:
Please can you tell me how to return Nougat from oreo. I have LG UP and I have official Nougat H870DSU10f_00_OPEN_HK_DS_OP_0803.kdz firmware downloaded. How to avoid brick and factory reset? Can I just refubrish from LG UP or I will have to do factory reset of the phone and "brick" at first?
Click to expand...
Click to collapse
I did as described above. I was with Oreo 8.0. I downloaded LG UP with Uppercut, downloaded: H87011i_00_OPEN_EU_OP_0108.kdz, (Nougat factory image) then using Uppercut I selected "Upgrade" and pointed it to the downloaded KDZ. The flashing starting normally without any warnings, completed but then on first boot the phone kept crashing (I guess because Oreo data is not compatible with Nougat base as romcio47 says).
At that point I thought I had a brick because the phone could not complete any action other than crash continuously. Then followed the instructions for booting into Bootloader: (volume down + Power for 10", keep both buttons pressed, when you see the LG logo immediately release and re-tap again the Power while volume is always pressed). There it only gives you one option: "Factory reset", selected YES, rebooted and then phone started normally into the Nougat setup.
You can "upgrade" to 7.0 in lgup but after flash you must manually boot to recovery and do a factory reset. I've done it a lot on my H870
Sent from my Nexus 6P
ARB1 Problem
fegitoli said:
Very glad to hear that!
Here's a little disclaimer I'd like to add. This should go without saying: YOU are responsible for what YOU do to YOUR phone. If you bricked it because you missed a step, it's not the instructor's fault. If everything is okay but the screen shuts off randomly, it's not the instructor's fault. Please mod responsibly and be prepared for failure, because things don't always work as they should.
Click to expand...
Click to collapse
Just got my G6 a week ago and there is considerable scroll lag so I'm trying to get back to stock using LGUP. I am getting "0x81000402 fail tot header antirollback". I am on ARB01 and cannot for the life of me get around this. I've tried LG Flash tool with no luck either.
Any insights??
amyelizabeth said:
What are the steps to downgrading? I just bought my g6 and loved it. then i upgraded to oreo 8.0 cause the notifications were annoying me. but i HATE it and now im sad any help?
Click to expand...
Click to collapse
Simplest way is
Take backup if you want
STEP1: download .KDZ file from https://lg-firmwares.com/lg-h870ds-firmwares/firmwares/
STEP2: LG up from here https://www.filedropper.com/g4
SETP3: In dev option open Enable OEM unlock and USB debugging
STEP4: turn off the device and long press vol up + and connect data cable to PC
SETP5: Open LG up S/W it will show your device then select location of KDZ file go
you are done :good:
By the way why you want to downgrade
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Also I made a Reddit post about this before, if it helps: https://www.reddit.com/r/lgv20/comments/ac6apr/got_stuck_in_an_endless_twrp_bootloop_tried/
phamanhvu01 said:
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Click to expand...
Click to collapse
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
clsA said:
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
phamanhvu01 said:
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
Click to expand...
Click to collapse
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
txenglan said:
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
Click to expand...
Click to collapse
I have a potential solution for you. I'll PM you.
Have you guys tried to wipe data from recovery
Did this solution work? Can you share it?
txenglan said:
I have a potential solution for you. I'll PM you.
Click to expand...
Click to collapse
merrickville said:
Did this solution work? Can you share it?
Click to expand...
Click to collapse
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
txenglan said:
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
Click to expand...
Click to collapse
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
merrickville said:
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
Click to expand...
Click to collapse
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
txenglan said:
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
Click to expand...
Click to collapse
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
merrickville said:
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
Click to expand...
Click to collapse
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Edit: Here is the what I tried, not Reddit, but here. But, no LGUP_US996.dll. LGUP_common.dll, no, that does not work either.
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
merrickville said:
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Click to expand...
Click to collapse
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Click to expand...
Click to collapse
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Damn....getting the right dll was also part of what I did IIRC. It's too bad it was such a long time ago else I'd have a more clear recollection of the exact steps I took. All I can say for sure, is that if you don't give up, you'll eventually stumble on the right solution.
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
clsA said:
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Click to expand...
Click to collapse
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I have never seen the screen or error you described. Having a total of 4 v20 I thought I had seen everything.. guess not
Sent from my ONEPLUS A6010 using Tapatalk
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I wonder if this might work for you:
https://forum.xda-developers.com/v20/how-to/9008-test-t3855777/page13
It's an annoying process to have to go through but I revived mine when it was completely bricked (I couldn't even get as far as you because the phone wouldn't even turn on).
couple of thing that may help
No command screen is stock recovery being confused.
Try doing a factory reset using the volume - and power method (hold volume -, press power until the screen turns on, then tap power repeatedly until the menu appears)