Database Develop

Recovered from soft brick, after getting warranty replacement sent out, what to do???

okay, so long story short, I am one of the happy few that decided to attempt to downgrade before looking at the forums. to find out you can't after the lollipop update. So after soft bricking, i called up and got a warranty replacement sent out. shortly after, flashed a boot image from the 5.0 update, and got it to boot. then found the re-partition and flashed that, just to be safe. well after the fix, phone came up with the "security alert, restart device" warning. so maybe messed up a system file or something, not sure. but phone as it seems is running better than before i messed up. so here is the ultimate question, do i stick with what i have now, or take the refurbished device and send back this one? really seeing what you guys would do in this situation. oh and btw, can't take the new OTA update either. its like i'm back on kikkat lol. any and all opinions welcome. help me out guys.

Hard bricked??

I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.

waylo said:
I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.
Click to expand...
Click to collapse
Did u pull battery?
Sent from my LG-H811 using Tapatalk

MicroMod777 said:
Did u pull battery?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...

waylo said:
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...
Click to expand...
Click to collapse
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk

MicroMod777 said:
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.

waylo said:
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.
Click to expand...
Click to collapse
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk

MicroMod777 said:
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yeah, next time I will go the KDZ route to return to stock. Bummer!

Look up G2 unbrick.
Sent from my LG-H811 using Tapatalk

I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.

MrSteelX said:
I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.
Click to expand...
Click to collapse
Thank you all for the education.
10N hadn't been out for a day, so I was concerned this would raise some red flags at the store. Otherwise would have kept it on--a vast improvement over 10H.
I haven't been on LG at all previously, so all this info would have been nice to know beforehand. =/
Oh well, live and learn.
Of course it's similar with most phones (i.e. Samsung won't let you downgrade bootloaders/modem), but typically it will just not take, rather than brick. As I recall, what happened to me is an inherent danger with TWRP zip flashing.
Yeah, the KDZ failed 10h flash would have been a nicer way to let me know I am trying to do something very very bad.
I looked at some LG2 unbrick notes. Most of them talk about the connected computer showing several hard drives when connected. At this point, I can't even get the computer to show the qhsusb_bulk driver install attempt again. Any tips on how to get the phone to power on the right way to allow for this?

Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.

Biker1 said:
Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.
Click to expand...
Click to collapse
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.

waylo said:
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.
Click to expand...
Click to collapse
I hear ya.
I needed to make an updated 10h Nandroid anyway.

Don't hold me to it but from what i can tell we aren't being locked out of downgrading in future updates, just in 10n as it's main purpose was to patch stage fright which was a massive security flaw and they felt it unsafe to allow downgrade to an insecure state

so uh huge question here...i got my phone from tmobile aand it was 10h....so i flashed twrp and it worked...but now no matter what rom i run i get a hang until i reboot..then when i reboot the phone spazzes the **** out...help anyone thanks

Your problem is unrelated to this thread. Your phone is buggy but not bricked.

Last night I tried to root my phone. I pushed a rooted image. It completed and rebooted. Then I got a security error 11. I then pushed a factory image using the KDZ method. Now it's completely dead. Pulled battery a few times. Nothing. Held down power and volume down a few times. Nothing. Plugged it in to charge. No LED light, no battery charging animation, no security error. No nothing. I also connected it to my PC with a usb cable while holding in volume up. Nothing. A whole lot of nothing. I contacted LG and they sent me a fedex label. It's now in the mail.
Question: I have the naughty image on there, but as far as I know it never actually took so I never had root. Also, presumably the factory image is what is currently loaded. So will they be able to detect that the phone is rooted? If they find the naughty file will they consider that in the same way as if I had succeeded in rooting it?
I knew at the time that I was doing something that would void the warranty so I can't complain too much. So then in the process of finding that I was naughty will they unbrick it at least to the point where I can pray for a future fix? I can say "gosh darn just send it back as is" and hope that they helped me out while detecting my naughtiness. Or if I say, "ok you got me, what's it gonna cost for you to unbrick my phone?" will they fix it at a reasonable price? If not, can I run it over with my car and pay the $150 deductible on my insurance? Basically, where am I at?

this is lg we are talking about. They will do 1 of 2 things to fix it, 1. reflash the whole emmc chip call it done. 2. swap out the mother board and call it done.

So sorry, it was not a bad flash I did this exact thing tried to revert. You are hard bricked I just turned my phone in though because I did it on day 2 I had it and got a new one. Just warning people you upgrade and try to go back you will get a hard brick.

I did the same thing as smkyle, but I haven't turned mine in yet. Is there any hope for fixing it.
Edit: In device manager it showed "QHSUSB_BULK" and then stopped. I have a spare battery and charger so after swapping out the battery the computer read the phone again, but this time installed drives and now shows "Qualcomm HS-USB QDLoader 9008 (COM7)".

LG G3 LS990ZVG: LG One Click Root Doesn't Work (Lollipop 5.0.1)

Maybe a thread like this has been created before, I don't really know, but I kinda feel like my case is a little bit different.
I wanted to try to root my phone, considering Sprint is literally doing no updates for the LG G3, which stinks but that's another thread for another day. Anyhow...
I've followed the instructions of trying to root this phone, making myself a developer on said phone, USB Debugging is on, plug the bad boy into the PC. I have the LG Drivers as well as the "One Click" root system. First issue is the one click installer doesn't find the LG ports ever, so I have to hold the Volume Up button to put it manually into download mode. I've done this multiple times now and not much has changed. When I do go into download mode, down in the gray box it usually shows the the SuperSU command in the box, but the numbers have changed multiple times. First time it said SuperSU27 on COM4 (can't remember the exact verbiage it used for the file name) the next attempt was 25 on COM3, 21 on COM3 and last time it was 79 on COM3.
While all of that is going on, I get the message that it is rebooting my phone through one click, which it isn't, it's still trying to supposedly download SuperSU, which, always sat at 0% and never progressed.
I've noticed that many people haven't been using ZVG to root their LG G3's. I would attempt reseting my entire phone completely scratch, but I don't really dig the sketchy sites that LG Flash is on, so I've never downloaded anything from them for that. Then again, I would like to avoid totally resetting my phone like that, because I'm not very fluent in phones like that to trust myself to do something that could potentially mess it up.
Does anyone have a work around for my issue or know what could be going on.

did you figure this out? I'm in the exact same predicament..

tri0xinn said:
did you figure this out? I'm in the exact same predicament..
Click to expand...
Click to collapse
No I haven't. I have absolutely no experience at rooting phones, so it's basically something I can't figure out.
I've seen people completely reset their phones manually but I don't feel competent enough to try it.

I had an incident while flashing a ROM and had to use LG flash tool. I let the phone update to ZVG, but cannot get Root. Realistically, all I want is to be able to use wifi tether for now. I'm running into the same problem, the one click root is not noticing my device after i manually put it into Download Mode. Maybe it has to do with using Wimdows 10? Which operating system are you using? Have you figured it out?

ZVG is rooted!!
runningbandit said:
I had an incident while flashing a ROM and had to use LG flash tool. I let the phone update to ZVG, but cannot get Root. Realistically, all I want is to be able to use wifi tether for now. I'm running into the same problem, the one click root is not noticing my device after i manually put it into Download Mode. Maybe it has to do with using Wimdows 10? Which operating system are you using? Have you figured it out?
Click to expand...
Click to collapse
Well, I figured it out... Go Here if you're still looking... Do Method B, download the zip and go manually through it... Worked fantastic!
https://forum.xda-developers.com/sp...-zvb-rooted-stock-t3211878/page8#post70645157

thanks runningbandit!
now to get twrp

H811 unbrick help

Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.

Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?

freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.

Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.

freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!

If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!

Bricked NO bootloader mode or recovery..Black screen!

So I messed up...Was trying to root and got stuck in a bootloop after flashing MAGISK, so I tried to just reflash the stock image...
I flashed successfully and got out of the bootloop but my wifi stopped working, so I rebooted and tried to reflash with the Pie image instead of oreo. For some reason I was getting errors so I got this bright idea to run the commands one by one in the Flash-All.bat.
But I still kept getting errors so I thought id reboot the bootloader and try again...thats where everything went south..Screen went black cant get to fastboot mode cant get to recovey..Pc recogizes the phone as "Qualcomm HS-USB QDLoader 9008" Bashing my head finding old LG threads that cant work for the razer, I dont know what to do...Any suggestions? Or am i just completely screwed.

Bad news I'm afraid but that's a hard brick you've got there there's nothing you can do to fix that afaik.

Mate, try this link? I googled around for you and this came up. Worth a shot -- best case it fixes it, worst case you're back to square one.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868

w00tnezz said:
Mate, try this link? I googled around for you and this came up. Worth a shot -- best case it fixes it, worst case you're back to square one.
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868
Click to expand...
Click to collapse
I saw that link on my hunt but I can't use it because the files provided are specific to LG L70 devices, the Razer doesn't use TOT files for firmware they use I'm going file's and the software he provided (which I tried) can only flash tot files.
Thank you though!

Rox598 said:
Bad news I'm afraid but that's a hard brick you've got there there's nothing you can do to fix that afaik.
Click to expand...
Click to collapse
Yeah that's what I was afraid of. Well luckily I am able to get it replaced... maybe not the most honest way but I only had it for a day so I went to where I bought it and told them it stopped working and they are sending me a replacement. Since it doesn't actually turn on they can't see that I unlocked the bootloader.... however...I'm still gonna try to root it I'll be more careful but I need root! I've been rooted since way back in Evo4g and Galaxy S1 days I use allot of root features I just can't give up..it's why I dropped Samsungs and went to Razer since Samsung started locking bootloader's... anyway hope it goes better the second time around lol

majicmazo said:
Yeah that's what I was afraid of. Well luckily I am able to get it replaced... maybe not the most honest way but I only had it for a day so I went to where I bought it and told them it stopped working and they are sending me a replacement. Since it doesn't actually turn on they can't see that I unlocked the bootloader.... however...I'm still gonna try to root it I'll be more careful but I need root! I've been rooted since way back in Evo4g and Galaxy S1 days I use allot of root features I just can't give up..it's why I dropped Samsungs and went to Razer since Samsung started locking bootloader's... anyway hope it goes better the second time around lol
Click to expand...
Click to collapse
I'm glad you're getting it replaced! May I ask what factory image did you try to flash onto the device? Pie MR0 or MR1?

Rox598 said:
I'm glad you're getting it replaced! May I ask what factory image did you try to flash onto the device? Pie MR0 or MR1?
Click to expand...
Click to collapse
It was MR1 from March 2019 the 9.0 one.

Just an update got my replacement and rooted it! I didnt bother with the TWRP method I just patched my boot image with Magisk and BAM! anyway now im happy time to transfer over my old phone stuff and im good!

majicmazo said:
I use allot of root features I just can't give up
Click to expand...
Click to collapse
With the lack of Custom ROMs what root features are you looking for exactly?
I just ordered mine today and like you I've rooted all my past phones except my current LG G6 (which can't be hence my upgrade)
The only thing I usually really need root access for is the free tethering without AT&T knowing and I was able to do that to the G6 without root.
Not trying to be mean or anything I'm just curious.

Nitrous729 said:
With the lack of Custom ROMs what root features are you looking for exactly?
I just ordered mine today and like you I've rooted all my past phones except my current LG G6 (which can't be hence my upgrade)
The only thing I usually really need root access for is the free tethering without AT&T knowing and I was able to do that to the G6 without root.
Not trying to be mean or anything I'm just curious.
Click to expand...
Click to collapse
Block ads.
Overclock for speed
underclock for battery.
Remove bloatware
Change boot animations
Thats just some of many more...
A whole world of possibilities woth root beyond tetheting and roms.
Sorry for the months later answer i just saw this.
Btw i got this thing replaced and rooted the second time around just fine im very happy now