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)".
Related
Well, the ZV6 should hit anytime now, Sprint & LG updated links. The changelog seems lacking though
LG Open Source LS991::
http://opensource.lge.com/osSch/list?types=ALL&search=ls991
Sprint Changelog LS991:
http://support.sprint.com/support/a...ServiceAdvisory_542_GKB86631-dvc8970002prd#!/
* If anyone receives the update and is rooted, please capture / copy the update file to your SDCARD and post for us to download
.
Agimax said:
Well, the ZV6 should hit anytime now, Sprint & LG updated links. The changelog seems lacking though
LG Open Source LS991::
http://opensource.lge.com/osSch/list?types=ALL&search=ls991
Sprint Changelog LS991:
http://support.sprint.com/support/a...ServiceAdvisory_542_GKB86631-dvc8970002prd#!/
* If anyone receives the update and is rooted, please capture / copy the update file to your SDCARD and post for us to download
.
Click to expand...
Click to collapse
Will the old root method still work?
SantinoInc said:
Will the old root method still work?
Click to expand...
Click to collapse
The factory reset protection has me curious. I think the better question is can then somehow block TOT flashing.
We won't know if the old root method will mess things up. I would just wait for a v6 image to be released. Someone did make a post as a how-to root the image yourself if you can get it off the phone. I would just wait.
someone needs to capture the OTA and get it to me so I can check it out.
I'd suggest holding off on actually applying the update until we know what's what.
Thx in advance.
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Much thanks to you guys! Work some magic for us!
mswlogo said:
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Click to expand...
Click to collapse
sent you a PM as well but I'll say it in here just in case you check here first. got it.. thanks again!
so.. after some poking around I can confirm...
ZV6 updates the anti-rollback version yet again, this time to "v2". If you flash this update or any part of the zv6 bootstack or zv6 modem it will update parts of your phone you will never be able to downgrade. This would also stop the ZV5 TOT from working... but to be specific.. ZV5 TOT will flash.. but your phone will be BRICKED after.
ZV6 does not seem to unlock the bootloader. I'm about 90% on this after initial code review. Perhaps some poor soul will take the OTA and be able to confirm this without a doubt... but it looks like the "Factory Reset Protection update" (related to oem unlock in development settings) has nothing to do with unlock status itself.
If a ZV6 TOT is somehow acquired in the future... the system and boot partitions could be extracted and used on the ZV5 bootstack... possibly ZV4 as well. Basically... boot.img and system.img would not blow any qfuses to permanently set a "version".
Bootloader/bootstack consists of aboot, sbl1, sec, rpm, tz, hyp, pmic, sdi... and then theres the modem. Flashing any ZV6 partition mentioned in the prior sentence will blow your fuse to "v2".
As for root... it's hard to tell without the device in hand to be honest... but I would assume it's still able to be rooted. So taking the OTA would not be the end of the world... you'd still have root. But you'd lose the ability to flash the ZV5 TOT without bricking... and it once again updates your bootloader version which may be blocking previous holes in a v0 or v1 bootloader we have not yet found.
I am not sure why LG and the US carriers have done this. I could understand the v1 update.. as that would separate USA from the rest of the world and make bootloader unlocking harder. To update it to v2 just doesn't add up... not yet anyway.
tl;dr
If you want to stay on a v0 (ZV4) or v1 (ZV5) bootloader version.. don't update.
If you couldnt care less about the bootloader and only want root... ZV6 should still allow that.. but the ZV5 TOT would no longer be able to be used.
mswlogo said:
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Click to expand...
Click to collapse
So I can install this in the stock recovery (I am not rooted) because there is an option?
(I am doing it now but it seems to be stuck on "patching system files", uh oh)
edit: I am fine now, it installed fine. Was a little un-patient
I notice now the icons at the top are more stock android like with the "!" point if there is no internet. Pictures
Also the phone "feels" faster, I hope we can uncover what is under this update.
I hope this doesn't fix my free hotspot trick.
So if the OTA pops up, I can download and install it and still have root? Or has that been undetermined to to this point?
autoprime said:
sent you a PM as well but I'll say it in here just in case you check here first. got it.. thanks again!
so.. after some poking around I can confirm...
ZV6 updates the anti-rollback version yet again, this time to "v2". If you flash this update or any part of the zv6 bootstack or zv6 modem it will update parts of your phone you will never be able to downgrade. This would also stop the ZV5 TOT from working... but to be specific.. ZV5 TOT will flash.. but your phone will be BRICKED after.
ZV6 does not seem to unlock the bootloader. I'm about 90% on this after initial code review. Perhaps some poor soul will take the OTA and be able to confirm this without a doubt... but it looks like the "Factory Reset Protection update" (related to oem unlock in development settings) has nothing to do with unlock status itself.
If a ZV6 TOT is somehow acquired in the future... the system and boot partitions could be extracted and used on the ZV5 bootstack... possibly ZV4 as well. Basically... boot.img and system.img would not blow any qfuses to permanently set a "version".
Bootloader/bootstack consists of aboot, sbl1, sec, rpm, tz, hyp, pmic, sdi... and then theres the modem. Flashing any ZV6 partition mentioned in the prior sentence will blow your fuse to "v2".
As for root... it's hard to tell without the device in hand to be honest... but I would assume it's still able to be rooted. So taking the OTA would not be the end of the world... you'd still have root. But you'd lose the ability to flash the ZV5 TOT without bricking... and it once again updates your bootloader version which may be blocking previous holes in a v0 or v1 bootloader we have not yet found.
I am not sure why LG and the US carriers have done this. I could understand the v1 update.. as that would separate USA from the rest of the world and make bootloader unlocking harder. To update it to v2 just doesn't add up... not yet anyway.
tl;dr
If you want to stay on a v0 (ZV4) or v1 (ZV5) bootloader version.. don't update.
If you couldnt care less about the bootloader and only want root... ZV6 should still allow that.. but the ZV5 TOT would no longer be able to be used.
Click to expand...
Click to collapse
Thanks for poking around and seeing what's what. If I were inclined to update my rooted ZV5 to ZV6 (understanding the current TOT restore would brick my phone) how exactly would I keep root?
SantinoInc said:
Thanks for poking around and seeing what's what. If I were inclined to update my rooted ZV5 to ZV6 (understanding the current TOT restore would brick my phone) how exactly would I keep root?
Click to expand...
Click to collapse
I dont think you'd be able to keep it. You'd most likely have to re-root with a ZV6 rooted system.img... same way you rooted ZV5.
How did you manually install the update? I've looked up guides online but they say you need to install the Android SDK and LGFlashTool and such, which I messed around with but I can't really grasp on how to install this. Putting my G4 into download mode and trying to detect it via CMD did nothing (USB Debugging is checked).
Sorry, maybe somebody can lead me in the right direction, as I really want to try out this update and I'm also very impatient lol
argh2000 said:
I est gues is that the game is not meant for VGA screen
Click to expand...
Click to collapse
How do you create a ZV6 rooted boot image?
KillerDisturbed said:
How did you manually install the update? I've looked up guides online but they say you need to install the Android SDK and LGFlashTool and such, which I messed around with but I can't really grasp on how to install this. Putting my G4 into download mode and trying to detect it via CMD did nothing (USB Debugging is checked).
Sorry, maybe you can lead me in the right direction, as I really want to try out this update and I'm also very impatient lol
I have Skype also if that's something that you could do, cause I'd really appreciate the help
Click to expand...
Click to collapse
It requires an sd card..copy the file to the root of the sd card then power off the phone. Hold down volume down then power till you see "recovery mode" then release. Once stock recovery loads use the volume down to the last option, something like install update and press power. This will bring up the directory from the sd card. Select your file with volume down and press power.
Sent from my LGLS991 using Tapatalk
Swetnes said:
It requires an sd card..copy the file to the root of the sd card then power off the phone. Hold down volume down then power till you see "recovery mode" then release. Once stock recovery loads use the volume down to the last option, something like install update and press power. This will bring up the directory from the sd card. Select your file with volume down and press power.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
SantinoInc said:
How do you create a ZV6 rooted boot image?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62369954
Sent from my LGLS991 using Tapatalk
---------- Post added at 11:36 PM ---------- Previous post was at 11:33 PM ----------
This update does include the Stagefright fix.
Sent from my LGLS991 using Tapatalk
KillerDisturbed said:
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
Click to expand...
Click to collapse
Can this be done even on rooted ZV5?
Probably. I installed the update and have noticed a few small touches in the UI, but notably a more responsive keyboard and overall faster phone. Knock code is also a bit more consistent and snappier for me as well, so I'll probably be using that from now on. Great update from the looks of it so far.
Sent from my LGLS991 using XDA Free mobile app
KillerDisturbed said:
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
Click to expand...
Click to collapse
Tried a few times to do this but it won't read my sd card..any ideas?
Sent from my LGLS991 using Tapatalk
stam27 said:
Tried a few times to do this but it won't read my sd card..any ideas?
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
You may need to pull the card out and put it on a computer and format it using SD CARD FORMATER. If you Google it you will find it. I know with other phones I've had that solved recovery being able to read it. You are copying to the "external" sd card?
Sent from my LGLS991 using Tapatalk
Overnight my nexus 6's USB port decided to die. Computers wont pick it up, it wont charge, AND my turbo charger makes a beeping sound while it is plugged in. tested w/ an old phone and it charges. i've tried different bricks and everything. still nothing. So i am trying to find out if there is some way i can unroot it, flash stock recovery and relock the bootloader without a computer because i cannot figure this out. i know i can do the super SU uninstall from supersu, but that will not fully unroot my phone correct? it will just remove root permissions. if i cant figure this out, i need to return the phone back to verizon and get another. but if i do so as is, i can say goodbye to my warranty... which i dont want to do. So if anyone can give me some help or steps in the right path, please do so. Thanks.
****Edit****
last night i went to bed and plugged it in and it charged just fine. i woke up in the middle of the night and heard a beeping. found out that my phone wasnt charging. and well. here i am now.
Cbabe101 said:
Overnight my nexus 6's USB port decided to die.
Computers wont pick it up, it wont charge, AND my turbo charger makes a beeping sound while it is plugged in. tested w/ an old phone and it charges. i've tried different bricks and everything. still nothing. So i am trying to find out if there is some way i can unroot it, flash stock recovery and relock the bootloader without a computer because i cannot figure this out. i know i can do the super SU uninstall from supersu, but that will not fully unroot my phone correct? it will just remove root permissions. if i cant figure this out, i need to return the phone back to verizon and get another. but if i do so as is, i can say goodbye to my warranty... which i dont want to do. So if anyone can give me some help or steps in the right path, please do so. Thanks.
****Edit****
last night i went to bed and plugged it in and it charged just fine. i woke up in the middle of the night and heard a beeping. found out that my phone wasnt charging. and well. here i am now.
Click to expand...
Click to collapse
1.
Don't panic.
2.
When your N6 is not charging with the M-charger you have 2 options:
- use another standard charger and/or cable.
- buy a cheap qi-pad and try wireless charging.
3a.
When the N6 can be charged with the help of 2. you can flash a factory image.
Don't forget to remove your accounts first.
3b.
When the N6 can't be charged, there will be a moment it can't switched on/start up.
Than send it back with the message: N6 can not be turned on since 'to day'.
NLBeev said:
1.
Don't panic.
2.
When your N6 is not charging with the M-charger you have 2 options:
- use another standard charger and/or cable.
- buy a cheap qi-pad and try wireless charging.
3a.
When the N6 can be charged with the help of 2. you can flash a factory image.
Don't forget to remove your accounts first.
3b.
When the N6 can't be charged, there will be a moment it can't switched on/start up.
Than send it back with the message: N6 can not be turned on since 'to day'.
Click to expand...
Click to collapse
Will doing 3a relock my bootloader and also flash stock recovery? i believe that is my main problem i see with if i need to return my phone. If i return this phoen (even if its dead) they could repair it and get it turned on. once they see the unlocked bootloader... thats my next concern. also, i dont see how i can flash a factory img w/o a computer. since it is not registering when i connect it to anything. i downloaded a factory image and tried from recovery, but it didnt show up in the place it downloaded
Cbabe101 said:
Will doing 3a relock my bootloader and also flash stock recovery? i believe that is my main problem i see with if i need to return my phone. If i return this phoen (even if its dead) they could repair it and get it turned on. once they see the unlocked bootloader... thats my next concern. also, i dont see how i can flash a factory img w/o a computer. since it is not registering when i connect it to anything. i downloaded a factory image and tried from recovery, but it didnt show up in the place it downloaded
Click to expand...
Click to collapse
Relocking is the last thing you should do.
First unroot and back to stock.
Then test again the charging.
When still charging issue and full stock and accounts removed......
NLBeev said:
1.
Don't panic.
2.
When your N6 is not charging with the M-charger you have 2 options:
- use another standard charger and/or cable.
- buy a cheap qi-pad and try wireless charging.
3a.
When the N6 can be charged with the help of 2. you can flash a factory image.
Don't forget to remove your accounts first.
3b.
When the N6 can't be charged, there will be a moment it can't switched on/start up.
Than send it back with the message: N6 can not be turned on since 'to day'.
Click to expand...
Click to collapse
NLBeev said:
Relocking is the last thing you should do.
First unroot and back to stock.
Then test again the charging.
When still charging issue and full stock and accounts removed......
Click to expand...
Click to collapse
How do i flash stock without my computer? i downloaded the factory image from google's dev site and i cant find the file in my downloads if i boot into recovery to try and flash from there
Cbabe101 said:
How do i flash stock without my computer? i downloaded the factory image from google's dev site and i cant find the file in my downloads if i boot into recovery to try and flash from there
Click to expand...
Click to collapse
Actually, the phone keeps telling me download failed. so that would be why i cant find it... anything i download it fails on.
Cbabe101 said:
How do i flash stock without my computer? i downloaded the factory image from google's dev site and i cant find the file in my downloads if i boot into recovery to try and flash from there
Click to expand...
Click to collapse
You can flash only images that are saved in the internal storage of the N6.
You need to boot in recovery and than flash the images with TWRP or CWM
You need also to flash the stock recovery.
That is your problem.
You could try if TWRP will flash the stock recovery image over itself. But I think that won;t work.
NLBeev said:
You can flash only images that are saved in the internal storage of the N6.
You need to boot in recovery and than flash the images with TWRP or CWM
You need also to flash the stock recovery.
That is your problem.
You could try if TWRP will flash the stock recovery image over itself. But I think that won;t work.
Click to expand...
Click to collapse
So is there anything i can really do then? From the sounds of it, i need to have the factory image, and stock recovery. but since my phone will not download the files i need, i'm pretty much out of luck since i cant hook it to a computer right?
Cbabe101 said:
So is there anything i can really do then? From the sounds of it, i need to have the factory image, and stock recovery. but since my phone will not download the files i need, i'm pretty much out of luck since i cant hook it to a computer right?
Click to expand...
Click to collapse
I had to install a different browser to download it. i was able to get firefox to download a factory image. Since it is the last thing to do, is there a way to relock the bootloader w/o a computer so i can return the phone to verizon? and you're right, i dont think TWRP will allow me to overwrite it with stock recovery just by flashing it through TWRP
Cbabe101 said:
So is there anything i can really do then? From the sounds of it, i need to have the factory image, and stock recovery. but since my phone will not download the files i need, i'm pretty much out of luck since i cant hook it to a computer right?
Click to expand...
Click to collapse
I am very sorry for you.
You need to have 'the extracted images' on your internal storage. Extract on a PC the images and than transfer to a cloud storage like Dropbox.
But still your problem will be how to 'reflash stock recovery' without a working usb-connection.
The only suggestion I have is discharging....
Send it back with the simple message 'charging not possible' and wait/hope.
NLBeev said:
I am very sorry for you.
The only suggestion I have is discharging....
Send it back with the simple message 'charging not possible' and wait/hope.
Click to expand...
Click to collapse
Thats kind of what i was thinking too... One last question though. Is there a particular wireless charger i need to have? or can i really use any wireless charger? my friend has a samsung one that my phone hates. but my other friend tried his N6 on it and it didnt charge his either.
Cbabe101 said:
Thats kind of what i was thinking too... One last question though. Is there a particular wireless charger i need to have? or can i really use any wireless charger? my friend has a samsung one that my phone hates. but my other friend tried his N6 on it and it didnt charge his either.
Click to expand...
Click to collapse
You need a QI-compatible charging pad.
After sales stuff for Samsung is mostly QI.
Big chance you can use the wireless charging of your friend.
Why are you so worried about getting it back to stock software-wise when what you have seems to be a hardware failure that can't be caused by software?
nhizzat said:
Why are you so worried about getting it back to stock software-wise when what you have seems to be a hardware failure that can't be caused by software?
Click to expand...
Click to collapse
Although it concerns a hardware failure unlocking bootloader and/or rooting etc. is a violation of the warranty rules.
Furthermore repair is mostly outsourced to several companies that declare the costs of repair/replacement. Often at fixed price conditions. So declaring costs at users could be more attractive.
Cbabe101 said:
, i dont think TWRP will allow me to overwrite it with stock recovery just by flashing it through TWRP
Click to expand...
Click to collapse
It needs hassle with a cloud storage. Maybe this may help you to restore stock.
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
Wow. That probably would have worked. I sucked it up and took it to a local repair shop though. Good as new. A co worker ofbnine advised that if I ever need a warranty replacement, I could always just destroy the phone... Although I could never just simply on purpose destroy my phone lol. Another friend said to just simply report as lost. They'll send me a new phone and I can do whatever with the old one. But as for now, I'm all set. If I need it fixed, I will definitely be going back to the place I went. They did excellent work.
Sent from my Nexus 6 using XDA Free mobile app
Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.
I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
EDIT:
Not sure what the exact issue was, but I downloaded the Droid Turbo OEM from HERE. Waited 8 hours to download (original links don't work anymore and the mirror is stupid and charges for a fast download), unzipped the file, then ran the VRZ_XT1254_SU4TL-44_44_CFC.bat and it booted right up and has been working fine. I then simply installed TWRP, flashed SuperSU, then edited the build.prop to get hotspot working.
flametail2518 said:
I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
Click to expand...
Click to collapse
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.
GreaterLesser said:
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.
Click to expand...
Click to collapse
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.
TheSt33v said:
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.
Click to expand...
Click to collapse
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.
GreaterLesser said:
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.
Click to expand...
Click to collapse
Honestly, I have no idea.
I agree yes try recalibrating the battery. Or do a clean flash. It should recalibrate the battery when you do this.
The calibration is simply a file based on battery reads.
TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.
flametail2518 said:
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.
Click to expand...
Click to collapse
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.
My phone likes to shut down around 1-8% without warning, but it does say Powering down as it does it. It's kind of annoying, but I'm sure that's not similar to what you're experiencing.
TheSt33v said:
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.
Click to expand...
Click to collapse
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.
flametail2518 said:
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.
Click to expand...
Click to collapse
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
See previous post. I got it fixed today.
Sent from my SHIELD Tablet using Tapatalk
TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.
flametail2518 said:
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.
Click to expand...
Click to collapse
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.
TheSt33v said:
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.
Click to expand...
Click to collapse
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk
flametail2518 said:
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.
TheSt33v said:
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.
Click to expand...
Click to collapse
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.
flametail2518 said:
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.
Click to expand...
Click to collapse
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!
TheSt33v said:
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!
Click to expand...
Click to collapse
The free option said they look for physical damage first then go on to the repair.
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!