Database Info

Rooted, Bricked, now fixed, w/no recovery mode. download mode issues.

Hello everyone and thanks for taking the time to read this and help me out.
I had rooted my LG G2 D801 using a method which I can no longer seem to find. Let alone remember what it even was.
After attempting to revert from Lollipop to Kit Kat in order to flash a custom ROM(after countless hours of trying to figure out a way) , I hard Bricked my phone.
Then(after countless more hours of trying to figure out how to fix), I somehow managed to bring my G2 back to life.
Now, I'm unable to boot into any recovery whatsoever. Download mode works, however my computer states that no Serial Port Service is running on the phone. I happened to stumble across Auto-Rec Lollipop which states that it is currently installed. Although I can't seem to find it. Not sure if that's relevant or not but there you have it.
I'm not sure what's wrong, just looking for some guidance so I can maybe attempt rooting and /or flashing a custom ROM again.
Any help would be appreciated.​

[Completed] Soft-bricked my ZenFone 6, proceeded to screw up the recovery too. Requesting help.

Hello. First of all, let me just say I'm glad I was pointed to this place by a friend, and, while I know asking for help with your first post is simply bad form, I think you guys are my last hope for fixing this phone, so I'll just go ahead an explain.
Alright.
So, yesterday I decided to root my ZenFone 6 (A600CG) for the first time after about 9 months of use. Up until then, I didn't really have any interest in rooting or even unlocking the bootloader, or any knowledge of how to do anything with it at all.
So, I did a quick google search, and found this:
w w w.asus-zenfone.com/2015/05/one-click-root-for-zenfone-series.html
The whole thing felt a bit dodgy, what with the all the bat files and stuff, but I decided to go ahead anyway. And it worked just fine, my phone was rooted. Hooray. Time to go and install stuff I couldn't before, right?
That's when this came in:
w w w.asus-zenfone.com/2015/10/how-to-add-zenmotion-to-your-zenfone.html
So, I did that. What I didn't realize, however, was that my bootloader was still locked. And so I followed the instructions detailed on that tutorial and all, seemed to work. Except when my phone rebooted, all that showed up on the display was a USB symbol. It wouldn't boot. I swear, I nearly shat my pants at that moment. So, I set out to fix that.
I couldn't really find ANY decent tutorial on how to undo the soft-brick for the ZenFone 6 specifically, so what I did first was trying to sideload each and every single rom that ASUS has for the ZenFone 6 on their support page. None of them worked, all of them showed the "failed to verify whole-file signature" error when I tried to have them sideloaded with ADB. So, I followed these:
zenfone-blog.blogspot.com.br/2015/06/guide-how-to-unbrick-asus-zenfone-4-5-6.html
w w w.windroidica.in/2015/07/how-to-revert-back-to-stock.html
First the former, didn't work because the rom wouldn't sideload, then the latter. Now, I'm aware the latter tutorial deals with the ZenFone 5 (for some reason, everything out there regarding these devices is either for the ZenFone 2 or 5, almost nothing can be found regarding the 6), but I figured the two are similar enough that a ZenFone 5 firmware would most likely work on the ZenFone 6, since they're basically the same thing, except for the camera and display size. Well, I was wrong. It kinda worked, though, it was stuck on a bootloop at that point.
So, with my phone stuck on bootloop, instead of coming here for help before, this dumbass here tried to flash the recovery for a custom one (TWRP, in this case). Except the bootloader was locked. So, I tried flashing dnx and ifwi with a bootloader toolkit I found here on XDA-Dev. I don't even know what went wrong, but the bootloader is still apparently locked, fastboot won't flash TWRP on top of the current default recovery, and now the phone is soft-bricked again, with that USB logo appearing whenever it turn the phone on.
Is there any chance at all I can solve this, or should I just throw this in the trash and buy a new one? I'd rather solve it, as I quite like this device, even if ASUS is terrible with their updates.
PS: Sorry about the links, but I feel as though they're necessary to better explain the situation.
EDIT: Seems like the bootloop is back now.
EDIT 2: Finally found a working firmware (2.20.40.11)! Sideloaded it, but I got a message about installing the latest 4.3 version first. I'm assuming it refers to the Android version, and now I'm really not sure whether it worked or not, as the phone still seems to be on a bootloop. Confusing as hell.
EDIT 3: It wasn't even a bootloop, just a longer than normal boot! My phone is running again! Lost all my data, contacts, everything. It's as if I had bought it today. I'm happy, though. Feel free to lock this thread, the issue has been resolved!

Issue resolved, thread closed.

Installing TWRP per instructions and now phone DOA...

Hi all,
I've been ROM'ing since 2013 on multiple devices so I am somewhat familiar with adb/fastboot flashing and commands, what to do, what not to do, etc.... I just picked up a used pixel and first thing I did was unlock the bootloader - no problem. Next I go to root, so I began following this tutorial https://android.gadgethacks.com/how-to/root-your-google-pixel-pixel-xl-0174670/ , as instructed I DL the required drivers, image files, patch file etc...and follow this tutorial for installing TWRP https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ , I get to step 8 and instruct via the command window to fastboot boot twrp.img, just as instructed. Everything appeared to be going the way it should as it started to boot to TWRP but almost as quickly the phone just died. I mean dead as a door nail. It won't do a thing. It won't even charge now. I have never had a phone just die like this. I fear I have met my first true full on brick.
I mean, yeah, I have soft bricked phones many a times but always had a backup to restore or was able to dig my way out one way or another but that was explainable by messing with questionable ROM's or something similar. Here I was just booting to the phone specific most recent version of TWRP by a solid well known tutorial with solid links, no indication that these could be the wrong images or zip's at all....but I'll be damned if this phone is dead as hell. I'm hoping someone can shed some light as to what happened or even miraculously tell me that it can be fixed.
Guys, is this a worst case scenario full on brick with no hope or getting it back to life? If so, why? Where did I go wrong? If this is going to be what I fear it is I hope to at least understand how it happened so I can avoid it in the future. This was a very expensive F-up on my part. I am beside myself with grief and disbelief that I could have done this with as many times as I have unlocked bootloaders, rooted, installed TWRP, flashed ROM's, etc.. I mean I 'm not the best but I am not a noob by any means. I feel like such a dumb ass right now!
Appreciate any help or explanation anyone can offer. Thanks.

We don't flash avb or any other patches anymore and haven't for like an android version and a half. For future reference look for more current information when modding a phone and for simple things like root guides go to xda don't just ask Google.

@kerryh420,
Those are some pretty old tutorials!
After plugging in the charger and wait for say 10seconds, can you boot into bootloader with button combo?
(Power + volume down or power + volume up for recovery as alternative)
Cheers
Sent from my Galaxy Tab S2 8.0 using XDA Labs

No offense, if you've been ROM'ing since 2013 you'd know not to go to other websites for tutorials! XDA is your best friend to follow instructions on Rooting, Flashing a recovery, and etc! Sorry that happened to ya. If it's literally dead you're probably out of luck and I know that's not what you want to hear. My best advice is to not follow tutorials on other websites. Good luck on your next device!

My (un)pleasant experience rooting the Samsung Galaxy S8 G950U

All links to articles that I tried to follow are at the bottom of this post. Attempt this root at your own risk!
Let me start out by saying I have successfully rooted Android phones before (Motorola Droid from 2009 and LG G3 Vigor from but this phone was not wanting to cooperate from the very start. My intention was to root my Galaxy S8 so that I can install a custom ROM and get rid of unneeded software (i.e. Google, Sprint software, etc...). As it turns out, this is easier said then done. After A LOT of searching on this site and DuckDuckGo, I came across a few articles that seemed like they were legit and would get the job done. So, I prepared by downloading all the necessary files (the new firmware, Odin, adb, etc...) and factory resetting my device. I then tried to follow along with the first tutorial. Everything looked good. I was able to get everything set up just fine. My problem started when I was in the Download mode on the device (the light blue screen that says "Downloading..." in the center).
Before even connecting the device, I had PrinceComsy Odin fired up and ready to go being sure to follow the tutorial steps completely and accurately. Then, I connected my device and hit start.
...It's looking good!...
...Added!...
After a few other very promising log outputs .... nothing happened. I thought to myself, "Okay, no big deal. It said I may have to retry a couple times to get it to work." So, I reset everything back up and rebooted the phone back into Download mode. This time I tried the regular Odin version instead. However, I was presented with an error after hitting start: "SHA256 Invalid". After some searching, I found out that if you get that error in the regular Odin you should try the PrinceComsy Odin. Wow, okay, so I went back to PrinceComsy Odin and tried again to no avail. Still didn't work.
This is when I started to become concerned that I wouldn't be able to root this phone. Note: At this point, the phone still booted back into the OS with no problems. i.e. It was not bricked...yet!
I wasn't even past the Odin part of the root and already I was having problems. What was going on? I did some more searching around the web and these forums and found something interesting. Supposedly having your device plugged into the USB3.0 ports on your computer can sometimes mess Odin up. I tried plugging the phone into the normal USB2.0 ports on the back of my computer and restarted the whole process again.
Now, I was getting some weird errors. Stuff like "odin fail complete(write) operation" and "fail (no pit partition)". I started to sweat a little bit. I can't screw this phone up! I rebooted the phone just to make sure everything was still fine on the device. It booted into OS perfectly fine, again.
Okay, so one more try, and then I'll stop. I did everything again (booted phone into download mode, fired up PrinceComsy Odin, added firmware to appropriate slots, connected the device, and hit start). Once again, everything looked fine until I got another error, "Error SW REV CHECK FAIL : [aboot] Fused 4 > Binary 2". It was at this point I looked more closely at the text on the top left of the Download mode.
My bootloader was locked and for some reason that had something to do with all this failing. After all, I wasn't trying to change the bootloader at all; just trying to gain access to root permissions. Most of the tutorials I looked at said to enable the "OEM Unlocking" option in settings. However, I didn't have this option at all. I didn't think it would matter that much but boy was I wrong. I decided to give up, boot back into the OS, and call it a day.
I rebooted the phone and it took longer than normal. Like way longer. It was stuck at the Samsung splash screen for about an hour before I realized that the device was probably bricked. "Great," I thought. So, I managed to find the stock firmware on Sam Mobile. Once again, I used Odin and tried flashing the stock firmware. This time however, Odin actually completed! I thought I had done it. I successfully restored my phone, right? Nope, turns out the firmware I installed wasn't actually Sprint's original stock firmware. I'm not sure exactly what it was but everything looked fine until I entered the setup device screen. Some settings were greyed out and I was getting some weird error messages (I don't remember what they were). Then, after completing the setup, I noticed that I was no longer on the Sprint network. I also had some of Cricket's and MetroPCS apps installed by default. It was like the phone was in a so called "carrier limbo" and unable to connect to any one carrier. The weird thing is I was still able to send and receive phone calls and receive text messages. It was at this point, I realized I royally screwed up my phone I tried to factory reset (through the Recovery mode) hoping that would fix some issues but nope. Didn't seem to fix anything.
The next day, I took the phone back to the Sprint store to see if they could do anything. Of course, I knew they were just going to try factory resetting it as well. The tech came back and said they could ship it off to Samsung and have them repair it or replace it. I am really crossing my fingers and hoping that they just replace the phone. That would fix all of my issues (including the cracked screen ). Now, I have to wait 5-7 business days before I know if I'm going to be stuck without a Galaxy phone or if I'm going to get a new phone straight from the factory. Who knows? As of now, I am using my old LG G3 Vigor temporarily while Samsung looks at my phone.
TL;DR: If you are on the Sprint network, have a Samsung Galaxy S8, model sm-g950u, US variant, ATTEMPT ROOTING AT YOUR OWN RISK! Sprint apparently has some pretty intense software locks on their phones which is rather unfortunate seeing as I believe Android to be an open-source and modifiable OS. Basically, we have to use the phone as it is from Sprint or we can't use it all. This is unacceptable.
I will update this post with any new information as it becomes available.
Links
LG G3 Vigor: https://support.sprint.com/support/device/LG/LG_G3_Vigortrade-dvc8360002prd
Motorola Droid: https://www.cnet.com/products/motorola-droid-verizon-wireless/review/
1st Root Method: http://www.stechguide.com/root-galaxy-s8-and-s8-plus-snapdragon-variants/
2nd Root Method: https://forum.xda-developers.com/ga...on-sampwnd-t3658911/post73455543#post73455543
3rd Root Method: https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
Restoring Stock Firmware: http://rootmygalaxy.net/stock-firmware-on-galaxy-s8-and-galaxy-s8-plus/

Before rooting, flash it with the unbranded "U1" firmware which is much cleaner (bloat free), and also works on all carriers as long as the sim lock is unlocked.

I just use the regular Odin and flash TWRP for the correct Samsung device then find a nice custom ROM you can install using TWRP I wrote several guides for it using Samsung phones, A3(2017, A5(2017, A7(2017, A5(2014, J8(2018 other than the button sequence for DL/recovery it is pretty much works the same, installing a stock ROM I did with Odin but finding a good stock ROM that you can download at a decent pace is harder. The OEM unlock is under Dev option in your phone though combined with USB debugging so you would need to do that before using Odin. But I get where you are coming from most guides are confusing as hell.

Upgrading a G3 For Dummies

I've been getting help in the Newbie thread, but it's time I start a new topic, since it's getting harder and harder to find replies.
All I'm trying to do is upgrade an old LG from Android 5.0 to 6.0. That's it.
I've got the drivers installed. I've downloaded three different versions of Flash Tool. The only one I got to do anything was "Flash Tool 2014".
The first time I ran it (following the directions on the web page where I found it), I picked "CDMA", "DIAG", and "CSE Flash". I was able to pick "Other Country" and "English" and got the phone to start installing. However, it only got as far as 4% and gave me an error. Now, when I run it, I pick "Other Country" and can't even pick a language. They're all blank. If I continue, all the messages consist of Question Marks, however, it still gets as far as 4% before stopping.
The phone is bricked in Download Mode. I have tried two different USB cables, two different computers, one of which has Windows 7 & 8.1 installed. I've tried all different USB ports to make sure I'm on USB 2.0 and not 3.0. I've tried running in Administrator Mode.
I see many posts about the 4% Error. The solution involves downloading a "wx.dll" file and putting it in the C:\system32\LGMOBILEAX\PHONE folder, but that didn't work. I also so one that said when you get the error, take the battery out of the phone, unplug it, put it all back together, and then Continue. That didn't work either.
What else can I possibly do? Thanks.

Hey, I have been trying to find a rom for 6.0 and I can't find anything. The only way to get to 6.0 is through ota. If you have 5.0 then your lucky. Ota can only be used if you still have a sim card that's active in the phone. There isn't roms for stock android 6. I would try and help but I can't.
If anyone finds away to get stock 6.0 please let me know.
Talking about your issue of your phone being bricked, there is many unbrick methods. I personally used https://forum.xda-developers.com/t/...n-qualcomm-hs-usb-qdloader-9008-mode.2933853/ it helped and fixed my issue. I still had my device info wiped off my phone somehow but at least it works. Your at a issue with a flash tool, fresh reflash with that method I sent if you can use it and start over. I can guide you through it if needed.
You might be stuck at a stand still, tell me what your phone says in device manager. You probably flashed a bad firmware. In that case I used the method above.