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.
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
can you at least get the phone to fastboot mode?
microMXL said:
can you at least get the phone to fastboot mode?
Click to expand...
Click to collapse
No I cannot, The screen is completely black and nothing comes on at all if I hold down the power button.
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
microMXL said:
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
Click to expand...
Click to collapse
I have already looked through that thread, and i have done everything up to the flashing process, and then I get a STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) Error. I looked it up but the only option I haven't tried to solve the issue is to remove the battery, which i cannot do currently because to remove the battery you need a heat gun to remove the screen to get to the rest of the phone. I think I've given up all hope on fixing this phone and may just begin saving for a new one.
Sgt.Collywobbles said:
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
Click to expand...
Click to collapse
Help, pls I got the exact same problem... Pls any solution to it... I have been at it for a month now no solution, help
same problem. after twrp flash x626 not boot
Started off by unlocking the bootloader on the December update (just got device the other day)
Used @munchy guide to install twrp and root the device
everything looked great
backed up stock
flashed everything but internal storage
installed lastest version of AOSiP
crashed during install so I thought ok, bad download. did a restore and got an error that system wasn't mounted. unchecked the box under mount, and restored. I reboot and all hell has broken loose. Fore close left and right. I go back to try and get to TWRP, and it's stock Recovery.
Follow guide again and get back into TWRP. I see that all my stuff is still there. So I do some reading and saw some folks having similar problems with TWRP not sticking, so I find some instructions in the TWRP thread that I need to flash the TWRP image to both slots, run the install patcher and should be all set. I do that...wipe again, restore and now I am in a continuous bootloop. I tried to switch slots, do a restore on the other slot....bootloop.
I feel really stupid and really bummed out that even with all my years and experience, I somehow found myself in this noob trap. Is anyone able to help me at least get back to just stock? All I really want at this point is to be back on stock with root so I can run an ad blocker. Thanks everyone
Mods - could you please close? I know have a hardware issue (lol), a rubber ring on the inside of USB port has come out and wedged inside the port, rendering the device defective. Thank you
I have this device and I used to use it a lot but then I got a new device. Recently I wanted to start rooting so used this device as a dummy. Instead of flashing Malik’s I flashed the update package or something like that for magisk and bricked device. Got that fixed by wiping stuff in twrp but when over board and wipes the os. Now when I boot j to recovery it does not happen and I’m stuck as boot logo. I don’t need any of the information on the old phone so I am wondering if anyone can help?
Ps I was running team win on it and it’s the Samsung s4 stat model.
ex4722 said:
I have this device and I used to use it a lot but then I got a new device. Recently I wanted to start rooting so used this device as a dummy. Instead of flashing Malik’s I flashed the update package or something like that for magisk and bricked device. Got that fixed by wiping stuff in twrp but when over board and wipes the os. Now when I boot j to recovery it does not happen and I’m stuck as boot logo. I don’t need any of the information on the old phone so I am wondering if anyone can help?
Ps I was running team win on it and it’s the Samsung s4 stat model.
Click to expand...
Click to collapse
Boot into download mode and check what firmware you were on. Depending which bootloader you're on, you can download it and use ODIN to flash back to 100% stock. However, if you're on later firmware the firmware package may not be available here in the forums.
Hi guys, a few weeks ago I revived my old 2012 N7 and have been getting some decent use out of it, however after trying to flash one of the Nexus factory images I think I may have bricked the device. I'll get straight to the point and explain more further down.
1. The bootloader is unlocked
2. The tablet boots into this screen - https://i.imgur.com/nzYaXLt.jpg
3. Whenever I boot into the bootloader the screen turns off (I believe the bootloader is the main cause of this issue)
4. Booting to recovery does nothing
5. Fastboot works(at least detects the device - https://i.imgur.com/yUGTVjh.jpg
6. When i try to flash a nexus factory image I get this error, then the tablet boots into the bootloader with a black screen - https://i.imgur.com/Kc9adlJ.jpg
7. Attempting to flash TWRP recovery results in this error - https://i.imgur.com/SHuQZWK.jpg
8. A video of what happens when I try different things: https://youtu.be/JBBT__nGJS8
I'm pretty sure the issues happened because there was some sort of failure halfway through a factory image flash(I flashed quite a few of the factory images but was trying to find the one I liked the most), so I unplugged the tablet( I know:/ ) as the flashing wasn't progressing at all after the error.
If anyone can help it'll be massively appreciated, I hope I've made it clear on what's going on with the device, and I'll be able to further explain things if needed
Sorry to tell you, but it looks to me as if the emmc memory is broken ... bootloader cannot be flashed / updated. If you had done a backup of your binary blobs before as described here there would have been the chance to reformat and to recover from scratch. Otherwise I suppose there is nothing you can do now. Our devices are becoming ancient ...
AndDiSa said:
Sorry to tell you, but it looks to me as if the emmc memory is broken ... bootloader cannot be flashed / updated. If you had done a backup of your binary blobs before as described here there would have been the chance to reformat and to recover from scratch. Otherwise I suppose there is nothing you can do now. Our devices are becoming ancient ...
Click to expand...
Click to collapse
Cheers for the reply It does make sense that the memory is broken as the tablet often fully freezed/switched off randomly during the last 4/5 days of its life. Just a shame because it was actually working surpisingly well before the memory issues! And also, thank you for the 7.1.2 AOSP ROM, definitely the best working ROM I tried as it never seemed to have any issues with it
TheGrade said:
Hi guys, a few weeks ago I revived my old 2012 N7 and have been getting some decent use out of it, however after trying to flash one of the Nexus factory images I think I may have bricked the device. I'll get straight to the point and explain more further down.
1. The bootloader is unlocked
2. The tablet boots into this screen - https://i.imgur.com/nzYaXLt.jpg
3. Whenever I boot into the bootloader the screen turns off (I believe the bootloader is the main cause of this issue)
4. Booting to recovery does nothing
5. Fastboot works(at least detects the device - https://i.imgur.com/yUGTVjh.jpg
6. When i try to flash a nexus factory image I get this error, then the tablet boots into the bootloader with a black screen - https://i.imgur.com/Kc9adlJ.jpg
7. Attempting to flash TWRP recovery results in this error - https://i.imgur.com/SHuQZWK.jpg
8. A video of what happens when I try different things: https://youtu.be/JBBT__nGJS8
I'm pretty sure the issues happened because there was some sort of failure halfway through a factory image flash(I flashed quite a few of the factory images but was trying to find the one I liked the most), so I unplugged the tablet( I know:/ ) as the flashing wasn't progressing at all after the error.
If anyone can help it'll be massively appreciated, I hope I've made it clear on what's going on with the device, and I'll be able to further explain things if needed
Click to expand...
Click to collapse
You still might be able to recover your Nexus with my guide. Go check it out.