Hello, I don't post much as I read and find my answers but this one is sort of a doozy and don't want to waste time if it is unfixable.
So I tried to update my CynogenMod on my phone. I wanted to start off fresh install. I backed everything I wanted with Titanium. Anyways I seem to have rebooted my phone after being formated. It gave the warning that the root has been removed so I pressed the back button but I guess that means go ahead.
Now the phone won't boot into recovery mode. I see the Blue text show up but it just reboots again and then it just sits at the Samsung logo.
I found forum.xda-developers.com/showthread.php?t=2621279 but not sure if this just works with AT&T or every carrier. I am currently downloading my stock firmware but taking forever as it is huge. I do have a backup of my phone before I installed CynogenMod but not sure if I can use those with odin or even which file goes where.
Model is SGH-I337m
Any help will be greatly appreciated.
Thank You!
So after working on this late into the night I got it back up and running. forum.xda-developers.com/showthread.php?t=2621279 worked like a charm. All I had to do was download a stock rom for my carrier I found online. Rstored it to stock form then just started over again. Glad I made backups of all the apps still got Flappy Bird :good:
Finally got CM 11 with PGAPPS working.
Sallad said:
So after working on this late into the night I got it back up and running. forum.xda-developers.com/showthread.php?t=2621279 worked like a charm. All I had to do was download a stock rom for my carrier I found online. Rstored it to stock form then just started over again. Glad I made backups of all the apps still got Flappy Bird :good:
Finally got CM 11 with PGAPPS working.
Click to expand...
Click to collapse
Yeah, just be careful. The guide you followed is for the i337, our canadian variants are i377m. Completely different, glad it worked out for you though. And yes, flashing stock fw with odin will fix any boot issue/soft brick provided the device turns on, any lights at all and can always recover. There is also an unbrick creator script for fixing hard bricks on our devices as well.
azuziel said:
Yeah, just be careful. The guide you followed is for the i337, our canadian variants are i377m. Completely different, glad it worked out for you though. And yes, flashing stock fw with odin will fix any boot issue/soft brick provided the device turns on, any lights at all and can always recover. There is also an unbrick creator script for fixing hard bricks on our devices as well.
Click to expand...
Click to collapse
Thanks for the information. I was pretty desperate last night I even tried adb sideband.
Hi there
I just received this lg (sprints ls980) from my friend a few days ago and I promptly rooted and it all went well. I had a hard time figuring out how install a custom recovery but i eventually figured it out and got twrp on. (an older version then 2.8.6.0 and 2.8.6.1)
But now it's stuck on a boot loop? I figured, who cares I'll just factory reset and install vanir. No dice. I flashed philz and still nothing any help?
I can boot into recovery and adb push so i'm not in a terrible spot haha
Ok *now* i am in a terrible spot I've tried following the restore to stock guide but none of my computers detect it in download more. Really sucks. I did restore the stock recovery so I can only use adb sideload which i don't know what the heck is good for. Please help i've been up way too long. I'm also getting the lg logo with "security error"
Bump.
Actually I have developments haha. So I'm on the same spot and after a lot of messing around with adb sideload I've gotten nowhere. And I'm pretty sure it's a dead end; short of some serious hacking. I've looked at a lot of this phones forum and I'm certain my USB is broken. Which makes sense.
I'll be buying a replacement USB and go from there.
The good part of this whole mess is that I'm learning a lot about this phone at least. So I'll be able to help out like I have for my older device
first i wanna say that this is my first time trying this and after a lot of research i thought i knew what i was getting into but now i feel completely lost. earlier today I rooted my phone using one click root then installed twrp using auto rec. auto rec seemed to work fine and i clicked open in recovery just to see if it worked. twrp opened no problem but when i went to boot the system back up i started getting security error messages under the LG logo. i tried getting it to boot again after formatting and now its just stuck on the LG logo and not doing anything at all. im almost positive i have a d800 version and pretty sure that i used the right autorec file. i was running 5.0.2 instead of kit kat so not sure if that had something to do with it. please help me out anyway you can, i really need to get my phone working again for work and not sure what to do. i tried searching for an answer but had trouble figuring out what to do.
Yes definetely it has something to do with it. Because autorec uses kitkat kernel. You just have to flash lollipop kernel and you're good to go.
Cr0wbaar said:
first i wanna say that this is my first time trying this and after a lot of research i thought i knew what i was getting into but now i feel completely lost. earlier today I rooted my phone using one click root then installed twrp using auto rec. auto rec seemed to work fine and i clicked open in recovery just to see if it worked. twrp opened no problem but when i went to boot the system back up i started getting security error messages under the LG logo. i tried getting it to boot again after formatting and now its just stuck on the LG logo and not doing anything at all. im almost positive i have a d800 version and pretty sure that i used the right autorec file. i was running 5.0.2 instead of kit kat so not sure if that had something to do with it. please help me out anyway you can, i really need to get my phone working again for work and not sure what to do. i tried searching for an answer but had trouble figuring out what to do.
Click to expand...
Click to collapse
Flash stock firmware with KDZ (Lg Flash Tool) there are a lot of tutorials here on xda.
Good luck.
I'm in the middle of the TOT method right now to get it back to stock firmware, seems to be working. so now if i want to start over and root/get twrp on my phone any suggestions on the best method? i've read a lot of different ways to do it and not quite sure what would be best. sorry if this seems like an easy find, i just dont want to run into this mess again ha.
Lg g2 wont turn on after installing autorec
I have tried to install auto rec on my g2(4.4.2). And now the wont boot and not even going to download mode. When i connected the phone to the computer phone is not getting detected. In the device manager it is shown as android phone=> android bootloader interface. when i try to turnon the phone, the screen just displays some vertical and horizontal lines on left side of the screen. Please help !!!
Good Day everyone
I am in desperate need for some help please, i managed to brick my LG G2, and need help unbricking it
I have the D802 International model.
The story so far, it had Cloudy G2 2.1 Rom on, wanted to update it to, Cloudy G2 3.3 , followed the guide on Blogspot, when, you search for "kevin with tech cloudy G2 3.3" on Google
Wiped the partitions via TWRP 2.7, as stated in the video (everything except internal storage), and then installed the KK-D802 bootloader.
After i rebooted, my G2 did not come boot again, it will go on with the boot logo and the words: "Boot certification verify" Secure booting error. will appear for about 2 seconds then just goes black.
Whenever i try to plug in via USB cable, it will detect multiple new drives in windows and accept me to "Do you want to format". in the device manager i can see device being detected as "QHSUSB_BULK"
My phone is rooted as well.
Some sites recommend using a linux way, but i have been through countless forums, and not sure which way is the right
Please please i need some help unbricking it, and willing to donate to the successful user advice / tutorial of unbricking it.
Thanks for reading and in advance.
Download mode
Hi everyone
I managed to get into download mode
Serenath said:
Hi everyone
I managed to get into download mode
Click to expand...
Click to collapse
then flash stock firmware using tot method.... [email protected] com
Serenath said:
Good Day everyone
I am in desperate need for some help please, i managed to brick my LG G2, and need help unbricking it
I have the D802 International model.
The story so far, it had Cloudy G2 2.1 Rom on, wanted to update it to, Cloudy G2 3.3 , followed the guide on Blogspot, when, you search for "kevin with tech cloudy G2 3.3" on Google
Wiped the partitions via TWRP 2.7, as stated in the video (everything except internal storage), and then installed the KK-D802 bootloader.
After i rebooted, my G2 did not come boot again, it will go on with the boot logo and the words: "Boot certification verify" Secure booting error. will appear for about 2 seconds then just goes black.
Whenever i try to plug in via USB cable, it will detect multiple new drives in windows and accept me to "Do you want to format". in the device manager i can see device being detected as "QHSUSB_BULK"
My phone is rooted as well.
Some sites recommend using a linux way, but i have been through countless forums, and not sure which way is the right
Please please i need some help unbricking it, and willing to donate to the successful user advice / tutorial of unbricking it.
Thanks for reading and in advance.
Click to expand...
Click to collapse
Had the exact same issue, I believe it's caused by corrupting the internal memory (multiple causes for this).
Don't freak just follow http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 (there's a video guide at the bottom, but it's pretty straight forward).
After that follow http://forum.xda-developers.com/showthread.php?t=2432476 to get it back to stock and work from there.
Good Day everyone
Thanks for all the advice and help, wanted to update the thread to solved, but things went a bit hectic at work during the week.
Anyways managed to get my phone working again, and restored to original state(thank God).
Basically followed a guide i found on Youtube, used the LG Flash Tool 2014 to flash back to Kit Kat stock, and then from there i rooted and used Auto_rec.
Found a guide on Reddit for Cloudy 2.2 install, flashed correct KK-Bootloader, and restored my Nandroid backup (which strangely at first did not work when restored via TWRP on stock Kit Kat, got the same Secure boot error)
Restored only data and system (everything except the boot) and my phone was back to it's original state.
Hope this helps anyone in the same situation.
PS: I was stuck in some boot loops, so had to format my internal memory as well.
Peace
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.