A co worker gave me this ATT unlocked LG Optimus G that he has royally screwed up.
When you turn on wifi it goes into a constant reboot (also does this in airplane mode)
When the sim card is installed an error keeps flashing something android process has stopped.
What i gathered from the conversation is that he rooted it and deleted stuff and then tried to do a factory reset.
He never put a custom rom on it.
I managed to get the get the apk for CRM and put it on the phone using the bluetooth .
NOw when you open the ap it wants to install the recovery manager.Problem is that there is no internet
any suggestions?
I am trying to get this phone in working order
Thanks
Does it still have IMEI?
---------- Post added at 02:19 AM ---------- Previous post was at 02:16 AM ----------
chrisskinner said:
A co worker gave me this ATT unlocked LG Optimus G that he has royally screwed up.
When you turn on wifi it goes into a constant reboot (also does this in airplane mode)
When the sim card is installed an error keeps flashing something android process has stopped.
What i gatered from the conversation is that he rooted it and deleted stuff and then tried to do a factory reset.
He never put a custom rom on it.
I managed to get the get the apk for CRM and put it on the phone using the bluetooth .
NOw when you open the ap it wants to install the recovery manager.Problem is that there is no internet
any suggestions?
I am trying to get this phone in working order
Thanks
Click to expand...
Click to collapse
Does it still have IMEI?
Yes it does
Try to reflash original KDZ for your phone
Is there a link you can point me to on how to do this without being able to boot into recovery?
chrisskinner said:
Is there a link you can point me to on how to do this without being able to boot into recovery?
Click to expand...
Click to collapse
Can you still boot to download mode?
Yes
http://youtu.be/3JVj6-K9ges
Follow the steps and the link in the description.
Just remember to use the LATEST KDZ for your LG G. Charge phone to 100% before doing the procedures. Good luck
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
chrisskinner said:
Yes
Click to expand...
Click to collapse
Hello ^
ClarkOwen said:
http://youtu.be/3JVj6-K9ges
Follow the steps and the link in the description.
Just remember to use the LATEST KDZ for your LG G. Charge phone to 100% before doing the procedures. Good luck
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
Hello ^
Click to expand...
Click to collapse
For E970 AT&T the procedure is different to E975, follow this Tutorial:
http://forum.xda-developers.com/showthread.php?p=50775936
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....
Dear folks, since yesterday i was not able to enter recovery mode. If i press vol up+ power then i can see a small USB icon with a white bar below that. After which nothing is happening. Powen button when pressed continously for 5sec will turn off my mobile and mobile starts again. Mobile is working perfectly. Only issue is unable to enter recovery mode. Can some one help please.....................
have you tried > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html ?
need to follow this exactly.. finger dance can be tricky but it will work...
I am aware of that bro.i tried many times.i was on custom rom earlier too. Now this us the first time i am seeing this USB icon with white bar below it. Phone is not entering recovery mode.
are u trying to restore ?
Pu$$nBooT$ said:
are u trying to restore ?
Click to expand...
Click to collapse
I am trying to reinstall the latest Global file using ADB
http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html
try this, ^^^
i followed this method to fix my issue
Try to flash the recovery again.
Pu$$nBooT$ said:
http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html
try this, ^^^
i followed this method to fix my issue
Click to expand...
Click to collapse
Bro you are not understanding. If the mobile is able to enter recovery mode then i can do all those things, mobile itself is not entering recovery mode. so there is no point in flashing usinng ADB
Using that link you can fix issues ... need to follow it to the letter.. called reading...
---------- Post added at 09:33 AM ---------- Previous post was at 09:30 AM ----------
Follow the guide like it says. You will fix the issues and dont plug the phone in a usb3 port, always use 2.0
Pu$$nBooT$ said:
Using that link you can fix issues ... need to follow it to the letter.. called reading...
---------- Post added at 09:33 AM ---------- Previous post was at 09:30 AM ----------
Follow the guide like it says. You will fix the issues and dont plug the phone in a usb3 port, always use 2.0
Click to expand...
Click to collapse
Downloaded UL-Z00A-WW-2.20.40.174-user.zip and renamed the file to UL-Z00A-WW-2.20.40.178-user.zip.
Copied the file and pasted into internal memory. System recognized the update file and asked me to update. Updated and mobile started normally. Now everything working fine, i was able enter recovery mode.
Hope this helps someone who encounters such type of issue,
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.
I was trying to flash Android 10 on my LG G7 Thin Q (LG-G710PM) with the LGUP cmd method, but I must have flashed an incompatible KDZ file or something because the process bricked my phone.
It won't boot no matter what I do, though my PC does recognize the device still (It recognizes it under other devices as QUSB_BULK_CID:0402_SN:333F0715)
I don't know what to do, and it would be a big shame if I truly just ended up killing my phone.
Update: I've downloaded Qualcom USB Drivers onto my computer and now the device is being recognized as Qualcomm HS-USB QDLoader 9008
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
Still download mode working?
Baijoosharma said:
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
Still download mode working?
Click to expand...
Click to collapse
No. Download mode does not work. The phone is unresponsive.
I've already tried the method in the link in your reply and it isn't working
Reyago said:
No. Download mode does not work. The phone is unresponsive.
I've already tried the method in the link in your reply and it isn't working
Click to expand...
Click to collapse
What is the problem with this method? Where you stuck? Any errors?