Related
just did the freegee unlock and phone will not power on
what happened?
i even got an popup congratulating me that i was unlocked
What version g pro you have?
Sent from my LG-E980 using Tapatalk 2
att version
e980
Clutchz said:
att version
e980
Click to expand...
Click to collapse
Try posting your issue in the actual thread in original android development
Sent from my LG-E980 using Tapatalk 2
Only your recovery and possibly boot partitions are touched, so worst case you can always get to download mode. However if the phone won't turn on at all its something not directly related. What happened before you rebooted into this state?
Sent from my LG-LS970 using xda app-developers app
i was doing the freegee thing and it had finished i went to home and hit reboot and nothing it stayed there
FreeGee has been updated and I unlocked my phone without any issues.
Clutchz said:
just did the freegee unlock and phone will not power on
what happened?
i even got an popup congratulating me that i was unlocked
Click to expand...
Click to collapse
Mine's doing it too man. Installed the app. Phone is rooted but stock recovery. Let it do its unlock thing and said yes to disable LGE security. Then tried to reboot using the volume and home keys to get to recovery and it gave a "Secure booting failed. Cause: Device Unlocked so boot success!!" message. Then LG logo again then AT&T animation and that's as far as it gets. No recovery menu, no normal boot. Just AT&T.
You get yours figured out yet? We gonna have to LGNPST back to stock?
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
wahida76 said:
FreeGee has been updated and I unlocked my phone without any issues.
Click to expand...
Click to collapse
SO how do you get to recovery then? I tried to 2 button into recovery and am now unable to boot the phone.
the computer detects something by this name: Qualcomm HS-USB QDLoader 9008 (COM17) and the screen stays black on the LG
lessthanzach said:
Mine's doing it too man. Installed the app. Phone is rooted but stock recovery. Let it do its unlock thing and said yes to disable LGE security. Then tried to reboot using the volume and home keys to get to recovery and it gave a "Secure booting failed. Cause: Device Unlocked so boot success!!" message. Then LG logo again then AT&T animation and that's as far as it gets. No recovery menu, no normal boot. Just AT&T.
You get yours figured out yet? We gonna have to LGNPST back to stock?
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
SO how do you get to recovery then? I tried to 2 button into recovery and am now unable to boot the phone.
Click to expand...
Click to collapse
I used a reboot app to boot recovery
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
Clutchz said:
the computer detects something by this name: Qualcomm HS-USB QDLoader 9008 (COM17) and the screen stays black on the LG
Click to expand...
Click to collapse
Your phone hard bricked and flashing might work
wahida76 said:
I used a reboot app to boot recovery
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
Your phone hard bricked and flashing might work
Click to expand...
Click to collapse
the flash tools dont detect the phone
Clutchz said:
the flash tools dont detect the phone
Click to expand...
Click to collapse
I am really sorry to say this but if that is the case then your hard brick can't be fixed your option is warranty.
oh well i'll go to att tomorrow thanks guys
Clutchz said:
oh well i'll go to att tomorrow thanks guys
Click to expand...
Click to collapse
If you bought the phone within the last 14 days then you can return it if not you can call at&t and speak to warranty and they will send you a warranty replacement your other option is to ask if they have a local warranty center they can try to flash it or exchange it.
Clutchz said:
oh well i'll go to att tomorrow thanks guys
Click to expand...
Click to collapse
Are you sure you were putting it into download mode? You take out the battery. Then put battery back in the phone. THen I believe you hold the volume down key and plug the phone into the computer. Then LGNPST should recognize the phone after you change the COM port to I believe 41 or 42
Edit: You hold BOTH volume keys while plugging the phone into the computer. It needs to be completely off when you do this.
Edit 2: Here's the guide : http://forum.xda-developers.com/showthread.php?t=2302660
Switch it under device manager to COM port 41. Now flash tools should recognize it.
I'm honestly bummed that I'm now going to have to re-setup everything again. I just had to flash my phone 2 weeks ago to get rid of 2nd Init recovery to install the value pack. Now I get to do it again, then run the update, then re-root, and put my 200+ apps back on, lol. FML. I guess this just isn't the phone the tinker with. Never had any of these issues on my S1, S2, S3, HTC One, One X, Note, etc. Oh well.
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Clutchz said:
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Click to expand...
Click to collapse
If you're on a windows 8 machine it will not detect your phone with them drivers, you need a win 7 os. I had same issue before
Sent from my LG-E980 using Tapatalk 2
turilo said:
If you're on a windows 8 machine it will not detect your phone with them drivers, you need a win 7 os. I had same issue before
Sent from my LG-E980 using Tapatalk 2
Click to expand...
Click to collapse
no dice tried it on both even xp i'm gonna give up on it i'll return it its easier
Clutchz said:
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Click to expand...
Click to collapse
Hey do you remember what version of freegee you installed? I think somehow you might have gotten version 1.0.6 instead of 1.1.0. Ive been through everything and the only thing that could have bricked you was using and older version of freegee. I didn't post on xda till Google showed the updated 1.1.0 version was live but maybe somehow you got an older on?
Sent from my LG-LS970 using xda app-developers app
Bootloader NOT UNLOCKED
I was wrong the bootloader is still Locked the developer of the App corrected his app info and this shows that.
http://forum.xda-developers.com/showpost.php?p=43813711&postcount=14
I have been up and down all the sites and recovery methods.
ISSUE:
In an attempt to root my Zenfone 2 (2.19.40.22 Lollipop) the tool I was using seemed to get stuck looking for my device. This was after installing a fastboot, or an attempt I believe. After a minute or so I noticed the phone screen was constantly showing the USB Logo.
I can turn on my phone and use it no problem. HOWEVER, I cannot POWER + VOL UP, to enter the bootloader. It just goes back to that USB Logo with the White Bar under it. And I have to power off and ON my phone again to get back to normal operation.
As you can imagine this makes it rather difficult to flash anything or use the ADB Tools whatsoever. Is there anything I can do to get that back, or am I doomed with a phone that can never be rooted?
[The tool that started this whole issue was the TWRPRecovery-Install]
Twrp tool only installs twrp recovery which you need an unlocked boot loader to install, so it should have never been used, can you use adb from the phone in normal operation? Can you get into recovery at all? Sometimes you can boot to recovery from adb shell when phone is in normal boot. Most of the solutions I can think of requires root but if you figure out how to get to recovery you can sideload a full update file to restore everything
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
And I am not sure if it will work now, but there is a one click root tool for this phone you could try it, but if you have an unusable bootloader it may not work, let me do some research for other options, may not find anything but we'll see
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:40 PM ----------
Start here
https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2
Sent from my ASUS_Z00AD using Tapatalk
Thanks for the info. I clearly followed the wrong guide. I did try the One Click Tool but again it goes straight to the USB logo. Its odd, if it was broken or deleted your imagine there would be a way to fix or reinstall it.
JetPKFR said:
Thanks for the info. I clearly followed the wrong guide. I did try the One Click Tool but again it goes straight to the USB logo. Its odd, if it was broken or deleted your imagine there would be a way to fix or reinstall it.
Click to expand...
Click to collapse
That is generally considered bricked... Only ASUS can fix for now....
So, I am a victim of the McAfee killswitch. I rooted my phone, then unlocked bootloader, but I made a mistake and had to flash kdz. For some reason, the kdz i downloaded was locked in mcaffee, so i really struggled but managed to install twrp, and of course root. The phone worked fine for a long time, but then I messed up and got a bootloop. The thing is, my killswitch is engaged now, so I can't just go into TWRP and wipe, or go into download mode. Both locked. And if i try to boot normally I just get the loop... So my questions are: Is there a way to get into TWRP directly (without having to confirm, phone could reboot to recovery just fine). Or just flash kdz, i don't know, anything. ADB shows device offline and sometimes unathorized, fastboot doesn't detect it. LG service said it will only fixed if i replace everything. Any help?
Sounds like you need togoba I to stock using lg flash tool
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
ToRt1sher said:
So, I am a victim of the McAfee killswitch. I rooted my phone, then unlocked bootloader, but I made a mistake and had to flash kdz. For some reason, the kdz i downloaded was locked in mcaffee, so i really struggled but managed to install twrp, and of course root. The phone worked fine for a long time, but then I messed up and got a bootloop. The thing is, my killswitch is engaged now, so I can't just go into TWRP and wipe, or go into download mode. Both locked. And if i try to boot normally I just get the loop... So my questions are: Is there a way to get into TWRP directly (without having to confirm, phone could reboot to recovery just fine). Or just flash kdz, i don't know, anything. ADB shows device offline and sometimes unathorized, fastboot doesn't detect it. LG service said it will only fixed if i replace everything. Any help?
Click to expand...
Click to collapse
Try flashing back to stock rom using lg flashtool
moswald1978 said:
Sounds like you need togoba I to stock using lg flash tool
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
Try flashing back to stock rom using lg flashtool
Click to expand...
Click to collapse
I can't access download mode, so I guess flashtool is not an option.
ToRt1sher said:
I can't access download mode, so I guess flashtool is not an option.
Click to expand...
Click to collapse
Try using the kHz method if your computer will reconize your phone. Use LG flashtool 2014 it will put your phone in download mode for you
---------- Post added at 06:06 PM ---------- Previous post was at 06:05 PM ----------
moswald1978 said:
Try using the kHz method if your computer will reconize your phone. Use LG flashtool 2014 it will put your phone in download mode for you
Click to expand...
Click to collapse
Kdz
How will it put my phone into download mode? If i click start, it says the phone is not connected to the computer. My computer can see the device as ADB device, but only offline or unauthorized.
When I used it my phone was stuck on the LG screen. Flashtool found my device and started the upgrade then it booted my phone into download mode
That does not work for me.. The program is stuck at 60% and telling me phone is not connected.
The only other option I can think of would be to a hard factory reset. Make sure your phone is off then hold down power and volume down together when the LG logo appears keep holding them. It should take you to that menu
I already said I can't go into recovery like that, because there is a killswitch activated on my phone.
ToRt1sher said:
So, I am a victim of the McAfee killswitch. I rooted my phone, then unlocked bootloader, but I made a mistake and had to flash kdz. For some reason, the kdz i downloaded was locked in mcaffee, so i really struggled but managed to install twrp, and of course root. The phone worked fine for a long time, but then I messed up and got a bootloop. The thing is, my killswitch is engaged now, so I can't just go into TWRP and wipe, or go into download mode. Both locked. And if i try to boot normally I just get the loop... So my questions are: Is there a way to get into TWRP directly (without having to confirm, phone could reboot to recovery just fine). Or just flash kdz, i don't know, anything. ADB shows device offline and sometimes unathorized, fastboot doesn't detect it. LG service said it will only fixed if i replace everything. Any help?
Click to expand...
Click to collapse
I guess it will be very hard to flash KDZ or TOT cause you need to put your phone to download mode or need to connect ADB. following the post.
ToRt1sher said:
I already said I can't go into recovery like that, because there is a killswitch activated on my phone.
Click to expand...
Click to collapse
did you ever find a solution ?
x000x said:
did you ever find a solution ?
Click to expand...
Click to collapse
No, that's why I asked for help here.
Any news guys? Did somebody find a solution to the killswitch problem?
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 try this follow step bye step works on most models
---------- Post added at 10:10 AM ---------- Previous post was at 10:04 AM ----------
This is a cure all for just about all bricks
---------- Post added at 10:50 AM ---------- Previous post was at 10:10 AM ----------
ToRt1sher said:
No, that's why I asked for help here.
Click to expand...
Click to collapse
It may seem hard but its really not
TheMadScientist420 said:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 try this follow step bye step works on most models
---------- Post added at 10:10 AM ---------- Previous post was at 10:04 AM ----------
This is a cure all for just about all bricks
---------- Post added at 10:50 AM ---------- Previous post was at 10:10 AM ----------
It may seem hard but its really not
Click to expand...
Click to collapse
You saved me, thanks a lot!!!
So i basically ended up delting boot partition or something.My Lg g3 wont turn on now.I was trying to fix Boot verfication but ended into more of a mess.It wont go to download mode ( pluging Usb cable and presing Up button).My phone is recognised by my pc when i connect it.Previously i had rooted it.Start of all this mess was while trying to install a custom recover Twrp.Any fixes now or i goota get a Jtag.
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
Read page entirely
Thanks TheMadScientist420 for reply but I did not understand a thing plus link to tool is also not working.
Lemme say it again phone won't turn on go to download mode or recovery.
You cannlook the tool up straight on google its out there im at work now so i not near my comp or i could walk u through further down the page it talks about disasambling the mother bord slightly kinda like jtag just not soldiering what ure doing is resetting the. Boot partitions to a factory blank state then ure using ure restore tot file and extraction stock partitions and pushing them to previously stated blank partitions on phone
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
It took me like 5 or 6 tries to short the pins out to do it
What exactly is the tools name btw? one i found requires me to pay to unzip it.
its on androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Bout half way down are the files u need
I got lg g3 D855 BTW thanks.
babapera said:
I got lg g3 D855 BTW thanks.
Click to expand...
Click to collapse
Could you fix your problem?
re
Sidz4u said:
Could you fix your problem?
Click to expand...
Click to collapse
I have yet to try it, iwill post my results don't know if it will work.I will have a tech guy help me with opening part.
babapera said:
I have yet to try it, iwill post my results don't know if it will work.I will have a tech guy help me with opening part.
Click to expand...
Click to collapse
i am having the same problem since this morning.
Phone is bootlooping again and again. Cant enter recovery/download mode.
but some how just now managed to get into download mode, flashed stock kdz, it installed completely (100%), but again when it rebooted after the flash, same boot loops have started and am not able to get through.
this problem is really weird.
Any clue on how to check if i have a Qualcom port or LG port?
You have to force it into the qualcom port with the pin shorting guide
---------- Post added at 01:10 PM ---------- Previous post was at 12:40 PM ----------
Again i stand corrected the g2 bad a ms dos script that pushed the partitions on the g3 wilzcracker aparntly pushes them so just follow the guide it works
Sidz4u said:
i am having the same problem since this morning.
Phone is bootlooping again and again. Cant enter recovery/download mode.
but some how just now managed to get into download mode, flashed stock kdz, it installed completely (100%), but again when it rebooted after the flash, same boot loops have started and am not able to get through.
this problem is really weird.
Any clue on how to check if i have a Qualcom port or LG port?
Click to expand...
Click to collapse
Not really
On your pc goto device manager youll see comms and ports thats wher youll see lg or qusb bulk 9008
my phones back online thanks mate. its working again
babapera said:
my phones back online thanks mate. its working again
Click to expand...
Click to collapse
what all did u do ??
just follow the guide
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
i followed the link but confused with their description on the pin shorting ..[.i cant find the specific pins to short.... please how did u short it......and which pins did u short
A small wire and you have to diasmble to get to the shorting point
TheMadScientist420 said:
A small wire and you have to diasmble to get to the shorting point
Click to expand...
Click to collapse
I am in India.. and we don't have .tot here. We use .kdz
Last I was on v21a.. fulmics rom.
Where should I get the tot files from ?
U can use kdz. http://forum.xda-developers.com/showthread.php?t=2785089
Hello everyone,
I have been seeing a lot of bricked phone help requests coming up lately across the forums here and I was able to fix my 16GB Model using the 32GB .TOT file located in this thread.
In that original thread posted by @bitdomo, he lists all the files necessary for download. The files he provides are working and I used his method to fix my phone with a variation in the repairing process. Specifically after you flash the 32GB .TOT file provided in the thread.
Download TOT file for your device
Download LG usb drivers
Download LGUP tool
Download 8994 dll for LGUP
Install LG usb drivers
Install LGUP tool
Install 8994 dll for LGUP
Turn off your phone
Press and hold the volume_up key while you connect the phone to the PC with usb cable.
Wait for Windows to install the new drivers
Start LGUP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Either select refurbish (will wipe userdata) or upgrade (wont wipe userdata)
Click on the line where it says BIN file to make the button with "..." appear and click on it then select the tot file.
Click on start
THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
After flashing the OTA, I cleared the cache and did a factory reset there in the bootloader menu and the phone is working perfectly.
P.S.: I used a USB 3.0 cable in a USB 2.0 slot on a Windows 10 PC. So, if I were you, I would do the same.
I am back to 7.0 rooted and this time won't be making the mistake of locking the bootloader before flashing stock images first.
PLEASE ASK QUESTIONS! I know this will be able to save a lot of people from buying new phones.
Also, this will require you to have some experience using terminal/CMD and have necessary SDK tools downloaded in order to ADB Sideload the given OTA for the 5X.
P.S.S.: Thanks for everyone who was involved in the original thread posted by @bitdomo. Specifically, @gee one, who initially provided the 32 GB .TOT files for the H790 and H791 variants.
Edit 1: thanks to @sfhub
If the post is being update it would be useful to add that people should *NOT* flash the TOT file if they are bootlooping because of EFS corruption due to TWRP 3.0.2-1 restore bug.
If they flash the TOT file, it will lock their bootloader but won't fix the EFS corrupt problem since the TOT file doesn't flash EFS.
With bootloader now locked, it becomes impossible to "zero" out the EFS partition to actually fix the problem because you cannot boot into TWRP since bootloader is locked and you only have stock recovery after flashing TOT file.
Click to expand...
Click to collapse
It is nice to post your specific info on how to fix the 32GB to 16GB userdata partition sizing issue that arises from flashing 32GB TOT file on 16GB phone.
However, perhaps it would be better to lobby for this info to be placed in the original thread rather than create a brand new one with 95% the same info?
The info is buried in that thread already but should be placed in the first post.
sfhub said:
It is nice to post your specific info on how to fix the 32GB to 16GB userdata partition sizing issue that arises from flashing 32GB TOT file on 16GB phone.
However, perhaps it would be better to lobby for this info to be placed in the original thread rather than create a brand new one with 95% the same info?
The info is buried in that thread already but should be placed in the first post.
Click to expand...
Click to collapse
First, if i need to provide more credit, please show me how. Also, I used most of his original post, because I could not have done it better myself. However, there needs to be some serious editing in the OP in order for people to be able to successfully unbrick their phones. It took me about 12 hours of researching with much trial and error to figure this whole thing out.
And yes, I usually would never just copy most of the steps. Furthermore, I think it should be sticked as a solution as well because the OT is titled as a request and is out-of-date in a lot of ways.
Apologies...
bardhi92 said:
First, if i need to provide more credit
Click to expand...
Click to collapse
It isn't about credit, you gave plenty of that. It is that most people would find the original post so IMO that is the best place to update instructions. In addition if the info is split, when instructions get updated, there will be inconsistent instructions if things aren't synced.
This is unrelated to your post but
If the post is being update it would be useful to add that people should *NOT* flash the TOT file if they are bootlooping because of EFS corruption due to TWRP 3.0.2-1 restore bug.
If they flash the TOT file, it will lock their bootloader but won't fix the EFS corrupt problem since the TOT file doesn't flash EFS.
With bootloader now locked, it becomes impossible to "zero" out the EFS partition to actually fix the problem because you cannot boot into TWRP since bootloader is locked and you only have stock recovery after flashing TOT file.
@briandresstoyota use this tutorial please. Once you have flashed the .TOT file and are inside the recovery where you can ADB sideload, please let me know. Like mentioned above, once flashed, use THIS OTA AND RENAME IT OTA.zip and sideload it.
Wide cache, factory reset and then reboot system.
bardhi92 said:
@briandresstoyota use this tutorial please. Once you have flashed the .TOT file and are inside the recovery where you can ADB sideload, please let me know. Like mentioned above, once flashed, use THIS OTA AND RENAME IT OTA.zip and sideload it.
Wide cache, factory reset and then reboot system.
Click to expand...
Click to collapse
Ok I will try this out. I will ping you when I get to the adb sideload phase. You wish me to use the exact OTA you linked yes?
@MajorSalvat to enter download mode, have the phone off with the USB cable plugged into the computer but not into the phone.
1. Hold Volume Up + Power Button while plugging the USB cable into the bottom of the phone.
2. Continue holding the Volume Up + Power Button until download mode starts up.
This sometimes takes a long while...
how do i tell which tot file?
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
uhm. my phone was dead. i was gonna boot to recovery to try to figure out what tot to download. Plugged in my phone and it charged and then booted and then went to the welcome screen and then rebooted. omg this phone is crazy.
---------- Post added at 09:03 PM ---------- Previous post was at 08:59 PM ----------
ok well now i have made it through welcome setup and to the home screen. annnnnnd now it just rebooted. I guess i really need to do this recovery.
briandresstoyota said:
how do i tell which tot file?
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
uhm. my phone was dead. i was gonna boot to recovery to try to figure out what tot to download. Plugged in my phone and it charged and then booted and then went to the welcome screen and then rebooted. omg this phone is crazy.
---------- Post added at 09:03 PM ---------- Previous post was at 08:59 PM ----------
ok well now i have made it through welcome setup and to the home screen. annnnnnd now it just rebooted. I guess i really need to do this recovery.
Click to expand...
Click to collapse
H790 U.S.
H791 International models
...usually
bardhi92 said:
@MajorSalvat to enter download mode, have the phone off with the USB cable plugged into the computer but not into the phone.
1. Hold Volume Up + Power Button while plugging the USB cable into the bottom of the phone.
2. Continue holding the Volume Up + Power Button until download mode starts up.
This sometimes takes a long while...
Click to expand...
Click to collapse
Still don't enter in Download mode. I try to do this many times but nothing. Just show the loading page and 2 seconds after restart
MajorSalvat said:
Still don't enter in Download mode. I try to do this many times but nothing. Just show the loading page and 2 seconds after restart
Click to expand...
Click to collapse
And this is with your USB plugged into the computer with the correct drivers and SDK files downloaded and properly installed? Is the USB slot a 2.0 or 3.0? Try to stick to 2.0 slots for this fix.
bardhi92 said:
And this is with your USB plugged into the computer with the correct drivers and SDK files downloaded and properly installed? Is the USB slot a 2.0 or 3.0? Try to stick to 2.0 slots for this fix.
Click to expand...
Click to collapse
Yes all drivers installed, my PC recognize the device in Fastboot. It's 2.0 to. I think it's the system not the PC
I held down Vol Up and then plugged in usb cable and phone turned on in Download Mode and then brings up the screen that says Firmware Update but when I start LGUP it says no device is connected.
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
@bardhi92 i noticed that when i entered download mode windows did not install any new drivers.
---------- Post added at 09:45 PM ---------- Previous post was at 09:38 PM ----------
dang lolol now windows is installing drivers three at a time lmao
---------- Post added at 09:49 PM ---------- Previous post was at 09:45 PM ----------
ok well LGUP says unknown model on COM4
---------- Post added at 09:51 PM ---------- Previous post was at 09:49 PM ----------
sometimes i can get to the DOwnload mode screen and it doesn not move on to the "Firmware Update Screen"
---------- Post added at 10:01 PM ---------- Previous post was at 09:51 PM ----------
ok trying on a different usb port (Not even sure how to see whcih is 2.0 or 3.0) now windows is trying to install drivers but it is taking forever and eventually my device turns off from firmware updat emode.
---------- Post added at 10:22 PM ---------- Previous post was at 10:01 PM ----------
ok i finally got it to connect and am currently going through the TOT process. when it is done i am going to boot into recovery and adb sideload the ota
---------- Post added at 10:40 PM ---------- Previous post was at 10:22 PM ----------
Foloowed your instructions exactly and now i get Google logo and then black screen.
---------- Post added at 10:53 PM ---------- Previous post was at 10:40 PM ----------
sideloading the original ota i had been trying to sideload before taking this advice. see if that helps
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
oh cool. got a * failed to read command: no error on the load at 89% and now im still in bootloops at the Google logo
If anyone is curious, I extracted the TOT file. It has the following:
PrimaryGPT
modem
boot
recovery
system
BackupGPT
It does NOT include
bootloader
vendor
efs
cache
userdata
If you have the EFS corruption problem due to TWRP 3.0.2-1 restore bug, TOT file will not fix it. It'll actually make things worse as it will lock your bootloader and you won't be able to unlock due to not being able to boot into Android due to EFS bug.
I am surprised this TOT file doesn't include vendor. Vendor and System need to be matched for things to work smoothly.
Has anyone else tried unbricking using this method with any success? Repeatability is important here.
bardhi92 said:
Has anyone else tried unbricking using this method with any success? Repeatability is important here.
Click to expand...
Click to collapse
IMO given what is included in the TOT file, this method no longer makes a lot of sense.
It originally came out because people were bricked but had their bootloader locked so they couldn't flash the factory image file.
Now that Google publishes FULL OTAs, these can be adb sideloaded using stock recovery and locked bootloader.
If it were me, I would first try the factory reset from recovery.
If that didn't work, I would suggest people try to recover from a bootloop with locked bootloader using the FULL OTA and adb sideload with stock recovery.
If you have unlocked bootloader, can also try flashing factory images from bootloader.
If that didn't work I would see if I have the EFS TWRP restore problem (and unlocked bootloader). If so try to get TWRP running and write zeros to EFS partition.
Only as last resort would I try the LGUP TOT file route.
That's just my opinion.
If this was an official TOT file that came from LG with all the partitions, then I would probably be recommending it more often. As it stands, with what is included in this TOT file, it has limited usage.
My last resort was this method. Was shocked it worked.
bardhi92 said:
My last resort was this method. Was shocked it worked.
Click to expand...
Click to collapse
I would just say that most bootloops today that don't get fixed with factory image or FULL OTA are actually hardware eMMC issues (either chip or solder joint), and this method wouldn't fix that.
I am not saying never try it, but I would really make it last resort rather than first resort.
---------- Post added at 05:34 PM ---------- Previous post was at 05:24 PM ----------
bardhi92 said:
THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
After flashing the OTA, I cleared the cache and did a factory reset there in the bootloader menu and the phone is working perfectly.
Click to expand...
Click to collapse
I think you meant to say you booted your phone into "recovery" not "bootloader"?
Also had you tried flashing the FULL OTA from recovery (adb sideload) prior to using LGUP and that didn't work?
sfhub said:
I would just say that most bootloops today that don't get fixed with factory image or FULL OTA are actually hardware eMMC issues (either chip or solder joint), and this method wouldn't fix that.
I am not saying never try it, but I would really make it last resort rather than first resort.
---------- Post added at 05:34 PM ---------- Previous post was at 05:24 PM ----------
I think you meant to say you booted your phone into "recovery" not "bootloader"?
Also had you tried flashing the FULL OTA from recovery (adb sideload) prior to using LGUP and that didn't work?
Click to expand...
Click to collapse
hey sfhub I am curious what you mean by full OTA. I tried the LGUP method and im stuck in a bootloop.
briandresstoyota said:
hey sfhub I am curious what you mean by full OTA. I tried the LGUP method and im stuck in a bootloop.
Click to expand...
Click to collapse
In the beginning we only got DIFFERENTIAL OTAs which were basically the monthly security patches. These are something 30-50MB and are only the *differences* from the previous version. They depend on you being on a specific version of software so the diffs can be applied. They are not FULL updates with every partition and all the contents to restore to a complete system.
A couple of months back, Google started letting us download FULL OTAs. These are much larger 700MB-1.2GB, basically almost the same size as factory image. They contain a FULL OS and can flash over anything, Nougat back to MM, MM to Nougat, bricked, etc.
https://developers.google.com/android/nexus/ota
The advantage of the FULL OTAs is they can be flashed on stock recovery with locked bootloader and they won't wipe your userdata partition.
If you needed to flash the factory images before, you needed to unlock your bootloader if it wasn't already unlocked, and unlocking would force a format of the userdata partition.
Also if you couldn't boot into Android and you didn't already have Allow OEM Unlocking set to true, then you were basically SOL because the factory image requires bootloader unlocking, but you couldn't do that until you booted into Android and set Allow OEM unlocking to true, but you can't boot into android because you have a bootloop problem.
Hence that is why this method with the TOT file and LGUP came out, so you could do a full image flash even without bootloader unlocked (in cases where you couldn't unlock the bootloader anymore)
At the time, I didn't even realize it didn't include the vendor partition. If you were on Nougat and just flashed this TOT file, your phone wouldn't boot because it would have the wrong vendor partition and it wouldn't be able to decrypt your userdata. By flashing a Nougat FULL OTA after the TOT file, you'll restore all the original partitions that you actually needed but were missing from the TOT file.
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
briandresstoyota said:
hey sfhub I am curious what you mean by full OTA. I tried the LGUP method and im stuck in a bootloop.
Click to expand...
Click to collapse
From what I read of your problem, I think you have hardware eMMC problem, either chip or solder.