Hello, I am a new member and I'm having a hard time trying to fix my phone.
Currently, I can't go into any mode. I have neither fastboot or download mode.
I also can't get into my twrp through factory reset since it tries to reboot my phone.
However, whenever it tries to reboot, I get error: Boot certification verify and the screen goes dark.
I have tried to solve it by following this thread:
http://forum.xda-developers.com/showthread.php?t=2582142 but nothing has worked so far.
Can anyone please help me?
rawtomato said:
I also can't get into my twrp through factory reset since it tries to reboot my phone.
Click to expand...
Click to collapse
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
iowabowtech said:
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
Click to expand...
Click to collapse
I get there and selecting reset reboots the phone. However, an error about phone ceritication verify pops up
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
iowabowtech said:
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
Click to expand...
Click to collapse
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
rawtomato said:
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
Click to expand...
Click to collapse
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
iowabowtech said:
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
Click to expand...
Click to collapse
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Be very careful
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
iowabowtech said:
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Click to expand...
Click to collapse
It seems like i have messed my phone up really badly.. Thank you for the ideas but yes, I will continue to look for more options for now
Edit: I have never tried the first method you showed me before but I have tried the second and the third method and did not work. Would I be able to fix it if I take it to a shop?
virginwidow said:
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
Click to expand...
Click to collapse
Thanks for your reply but I absolutely have no idea how to get into the dd / phone part using linux. I'll continue to look for more threads close to my problem but I have no clue as of yet.
Related
Any help is appreciated! First some background:
Flashed device to stock using KK 4.4 version d80020c following steps found here http://forum.xda-developers.com/showthread.php?t=2432476. Successfully rooted using directions (and ioroot25) found here https://www.youtube.com/watch?v=HKuedInhdjU&noredirect=1.
Here's where I got into trouble...Downloaded TWRP 2.7 recovery img and flashed via Flashify. Since this step, my D800 has the exact same symptoms found on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
- No download mode (tried many times)
- No recovery (tried many times also)
- Secure booting error
- LG detected as qhsusb_bulk in device manager
- Device is recognized as 15 different drives, one of which contains a folder named image with 79 different files being .B0X files and Microsoft Access Add-in Data files
- Upon restarting, LG logo with secure booting error, then the screen goes black while your phone is still on
I've followed the steps in the thread that matches my G2's symptoms, run ubuntu 13.1 in VM, apply usb filters for my device which is then recognized as either LG Electonics Inc. QHUSB_BULK or Unknown Device 05C6:9006 when running in VM.
Upon running command ls /dev/sd* in VM Ubuntu Terminal, all that is returned is /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 which are the partitions for Ubuntu, no LG.
I've tried to download and update the Qualcomm drivers, device manager tells me that the drivers were recognized, but cannot be installed and do not pass the hash check (Note: PC is running Windows 8.1).
I've spent over 12 hours on this trying to fix this problem, researched and searched everywhere. If I could get ubuntu to recognize the device, I would be able to continue on with the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
Links for windows 8 qualcomm drivers, suggestions on how to get the device recognized in ubuntu vm, experiences from others in similar situation, or any with experience working with LG to get a repair done if I'm SOL (as in eMMC is fried) would be so helpful right now.
Thank you all!
After flashing recovery did you flash a patched kernel to boot stock kk?
Sent from my LG-D800 using Tapatalk
I had the same, also with a lot of drives etc.
Screen is black but low backlighted?
Then try with pluged USB Cabel in Phone, hold Power button until screen is realy off, then hold the Power Up Button and plug Cabel into PC.
So I got download mode after I tryed many times
I had problems a few weeks ago getting mine to go into Download mode... turned out that the cable I was using was great for charging, but sucked for everything else. Once I switched to a different cable things worked fine and I was able to load D80010c on the device.
I was running D80020c this morning (with the D80010c boot.img to have a custom recovery) and decided to do an update. Since you can't load D80020k if you have the older bootloader I went all the way back to D80010c, updated to D80010o, D80010q, D80020c and finally D80020k. I was able to root that using IOroot and have restored everything back onto my phone.
-Daryel
Thanks so much for the responses! I've tried endlessly to get the device into download mode, and tried a new cable to no avail. Any other suggestions?
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
d800 partitions are here
Still no luck
bender_007 said:
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
Click to expand...
Click to collapse
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Sneaky Elephant said:
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Click to expand...
Click to collapse
As soon as in the background of the white menu (factory reset) the secure boot appear plug it in. I'm not sure how much usb filter helps you(maybe it does) but try installing ubuntu over WUBI installer so your win remains. Or at least try ubuntu from usb stick. So you can know for sure if it's working.
Hi Sneaky E. I have the same issue you have. I'll be following your thread. If I figure anything out I'll let you know. I am also having an issue getting mine to charge now. Have you tried downgrading your TWRP?
VirtualBox Error
VirtualBox recognizes the device is plugged in, but won't allow me to push the device for use in linux. I keep getting this error message:
Failed to attach the USB device LG Electronics Inc. QHSUSB__BULK to the virtual machine Ubuntu.
USB device 'LG Electronics Inc. QHSUSB__BULK' with UUID {d8db3712-b86c-4257-a87b-275cef04e5a3} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Click to expand...
Click to collapse
I've tried all USB ports, 2.0 and 3.0. I feel like if I can get past this there should be no reason linux can't see the partitions in the phone. Please Help!!!
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
ambetdelarosa said:
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
Click to expand...
Click to collapse
What are the negatives to doing a JTAG fix?
Sneaky Elephant said:
What are the negatives to doing a JTAG fix?
Click to expand...
Click to collapse
Here is your fix.
follow exactly. LINK
ingoljosh said:
Here is your fix.
follow exactly. LINK
Click to expand...
Click to collapse
Followed steps already, still can't boot into recovery.
Sneaky Elephant said:
Followed steps already, still can't boot into recovery.
Click to expand...
Click to collapse
if your device is insured maybe report it lost and pay deductible and get a new one AND NEVER ROOT AGAIN
linux cant recognizy my lg g2 f320L
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
dr jam said:
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
Click to expand...
Click to collapse
The same with me - UP
install ur Ubuntu sing VMware....then partitions will appear.........
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
install ur Ubuntu using VMware......then ur mobile will be recognised and partitions will appear.....
Been running pac rom, tried installing a custom ROM that was almost stock kitkat for Verizon. Forgot to wipe i think, and now i have been screwed since. Stuck in boot loop. Factory reset can be reached, but screen goes black everytime and doesnt allow me to get into TWRP. Only thing accessiable is download mode. But device is not recongized in adb, only when its bootlooping. But it is recognized in devices and printers in bootloop. New computer also, no RSA authentication, while in bootloop ive tried to adb boot recovery commands, but no authorization. Im completly stuck and have been for days, ive read so many posts but everything i have found doesnt match all my problems. and most people dont read the entire post or problem before submitting a dumb answer, which is a duh i tried that kind of thing thanks for nothing. SO PLEASE HELP IF YOU CAN THINK OF ANYTHING ELSE. IM GOING CRAZY OVER HERE AND LOOSING MY MIND> WHO EVER CAN HELP ME, IS GOD AND SHOULD BE CONSIDERED TOP DOG GENIOUS>
When you get to the white Factory Reset screen, pressing the power button 3 or 4 times won't get you back into TWRP?
Well u press it once to give conform option, and the second time, turn it black
lg flash tool
that doesnt work because it thinks its got the latest version. I need some real help bad, its so hard not having my phone. This would be easy if my laptop didnt get stolen that had authorization to do cmd commands. Anyways, really need some brain power put togeaher on this on and \fast. Is anyone down with maybe skyping with me, to visually see whats going on and troubleshoot it as if you were remoting into a computer. Just tell me what to do!!!> Please you have no idea how much I would love someone if they did. Its been driving me balls for weeks now. I NEED SOMEONES HELP
seriously, no one can help?
millzdog said:
seriously, no one can help?
Click to expand...
Click to collapse
lg tool works.. can u go into download mode?? just need to tweak lg tool with offline script
33709
Croize said:
lg tool works.. can u go into download mode?? just need to tweak lg tool with offline script
Click to expand...
Click to collapse
Yes i can go into download mode, please show me how to tweak
millzdog said:
Yes i can go into download mode, please show me how to tweak
Click to expand...
Click to collapse
Use the official lg support tool to restore it if you can enter downloadmode!!!!
http://forum.xda-developers.com/showthread.php?t=2432476
vs98010b stock rooted
Hello,
I've done a lot of looking through these forums, so I can say that the following doesn't work:
* The solution where and adb command from the TWRP terminal (starting with if=dev/zero) does not work. It does not have the files/directories those commands look for.
* I will be currently trying the solution that boots into Linux and uses gdisk to manage partitions. I have hope in this one, but I am making a head start of looking for advice in case it doesn't.
Any .tot or .kdz methods are useless as my phone /cannot/ get into download mode. If there is a way of telling it to over a cable, like you can with fastboot, I would love to know.
How the problem happened:
Ironically when I finally settled with a rom and wasn't going to do any flashing in the near future, I decided to make a nandroid backup.
I watched its progress now and then and it was working regularly.
Once it finished, I slid to reboot, and walked away. When I came back, the phone was on the LG logo with pulsating blue/green LED.
I went to restore from the backup I had just made, and that's what really messed things up. Ever after, all directories are shown as empty, and if you tell TWRP to do any function like flashing or recovering, it starts, but then crashes and reboots.
To begin with, occasionally it /would/ show my directories populated as they had been... but the crash and reboot thing. Now it never shows anything in the directories.
Since then, I /did/ manage to get into Fastboot ONE TIME, but things didn't work out on the computer end for Flashtools because I was on my campus network.
I have held out for a similarly low odd since, but I have spent hours, and almost all the battery, holding the power up button different times and ways and plugging the USB cable in at different times and ways.
I had Xdabbeb's stock variant installed, XCeed kernel, latest TWRP (thank God for heat control or I would have a screwed screen by now!) and let me know if any other details would be helpful.
I'm about to boot into Linux, I'll see how far I can follow this solution:
http://forum.xda-developers.com/showthread.php?t=2582142
Has anyone been in this spot? What worked?
EDIT: Ubuntu solution no good - my device does not show up as qhsusb_bulk or in sda or sdb tables.
EDIT: I MIRACULOUSLY got into fastboot! Instead of selecting power off or just holding power etc. in TWRP I said to reboot as system - holding the VolUp, even with the cable already plugged in, got me into FastBoot!
Trying the .tot method.
EDIT: I could weep. .tot failed because of
[ 8:50: 3] LAF_READ_GPT_FAILED
[ 8:50: 3] LAF_READ_GPT_FAILED.
[ 8:50: 3] LAF retrieveGPT() failed.
So I thought I should reboot it into download mode (which it was already in...) and I'm back to it being impossible to attain. What worked from TWRP the other time was just lucky.
Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk
dgranillo said:
Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I greatly appreciate your reply.
I managed to get it into download mode one more time (the rate must have been 1 in 80 or fewer, but I had no choice!), and flashed a .tot file (an old one... Jellybean!)
Ever since then, I have been able get into download mode as easily as it should be. One or two things to note though.
Any further flashing of .tot files ends at 6% with the exact same errors as pre-"fix".
Even the successful flash didn't boot successfully at the end, but had a red-triangle android figure
Sometimes it boots successfully into the stock rom, but others it goes into LG logo and blue/green LED, as before.
After a successful boot, it will die/go back into a boot loop some time soon after.
This leads me to think that a significant part of this all happening (I mean, I only did a nandroid backup to start this all off...) is a hardware issue, maybe to do with the flash storage.
By huge luck, I am withing the last 2-3 days of the 30 day period after buying it refurbished from a seller who gives full refunds including postage. Convinced something's not quite right with the hardware, I will be sending it back. I simply can't waste any more time I could be spending with my wife, or out of a returnable period, seeing if there is a fix to it.
Like I said, it means a lot that you would respond to help. Maybe parts of this are useful to someone. Thank you!
Any advice on removing the "rooted" red writing from the download mode screen? Especially as I'm pretty sure it isn't any more.
That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk
dgranillo said:
That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I am sincerely thankful for the time and consideration that you have given my problem.
I will mark this as solved because I did get past the initial problem, and I am thinking the further problems might be hardware.
Thank you again.
EDIT: I can't see how to edit the topic title, perhaps a mod has to mark it as solved.
My ZTE Blade AF3 (T221) can't boot into fastboot nor normal mode (so I could use adb). I can only use recovery mode. I tried to flash the stock firmware through apply update option, but the latest available firmware online is 1.0.4 and the recovery is on 1.0.5 (DIS_RU_QB18D_P731A20V1.0.5). That wouldn't be a problem if the update-script didn't check for the version of the current firmware and abort the installation because it's newer. I tried to delete the checking code from the script, but then the file verification check fails. I didn't find an option to turn that check off and I can't flash a custom recovery due to the lack of fastboot mode.
There is also another mode to which it can go into if I just let it boot without pressing any buttons. The ZTE logo appears, then disappears and the white screen remains. In Device Manager it's identified as "Gadget Serial". I don't know if I could use it somehow.
Is there anything I could do to flash the stock ROM or another recovery to the device?
Thanks for help!
Edit: If someone knows a method to boot into fastboot other than holding down the volume - key and plugging in the USB cable the advice is more than welcome, I just think I tried every kind of button combinations (although I wouldn't have guessed myself the process to go into recovery mode, so there's always the chance).
You already solved it? Maybe i can help you!
codeblvnc said:
You already solved it? Maybe i can help you!
Click to expand...
Click to collapse
Nope, I abandoned it. I even wrote to ZTE support, but they said I should wait for the newer firmware to be uploaded to the site (which I kept checking for a while, but nothing happened, so I eventually stopped). I haven't used that phone since, it now lives in the bottom of a drawer somewhere .
If you have any tips, I can try to make it work, but it's not that important anymore, so don't bother if it's too much work.
geiszla said:
Nope, I abandoned it. I even wrote to ZTE support, but they said I should wait for the newer firmware to be uploaded to the site (which I kept checking for a while, but nothing happened, so I eventually stopped). I haven't used that phone since, it now lives in the bottom of a drawer somewhere .
If you have any tips, I can try to make it work, but it's not that important anymore, so don't bother if it's too much work.
Click to expand...
Click to collapse
I had this phone, i need to check but have some firmwares in my personal computer. I will try make a easy-understanding tutorial to you
tl;dr
Hey guys, The title says it all basically. So here's the actual issue. My US996 was running great. Then, a week or so ago it just randomly started getting super sluggish. Today, I turned it off and when i turned it back on, it went right into the "firmware update" screen. I pulled the battery, played it with then got it into the recovery screen. Only thing is, i was able to move up and down using the Vol down button and power button but, i couldnt actually go into anything. So i once again pulled the battery, and now it wont do anything but go back into the "firmware update" screen. after playing with it some i finally got into the Fast Boot screen. which allowed me to do nothing. I pulled the battery again and it wont do anything but go to that "firmware update" screen.
I have tried using Uppercut to flash it. But when the LGUP program does it's reboot it dumps me right back off on the same screen. Since Uppercut and the correct KDZ are not working. Is it a hardware or software issue?
Also please forgive me, I do not understand all of the Android terms. Like, I am not sure what ADB means. I am a bit tech savvy.
Try using LG Bridge. It will reset your phone to complete stock, but it should fix up your phone.
Obamaloominaty said:
Try using LG Bridge. It will reset your phone to complete stock, but it should fix up your phone.
Click to expand...
Click to collapse
I've tried that, Uppercut, pretty much everything. I think it's the dreaded bootloop issue. When I connect it to Bridge it tells me "no updates available" . Or, the update failed.
JethroFloyd said:
I've tried that, Uppercut, pretty much everything. I think it's the dreaded bootloop issue. When I connect it to Bridge it tells me "no updates available" . Or, the update failed.
Click to expand...
Click to collapse
Did you click "update error recovery"
Obamaloominaty said:
Did you click "update error recovery"
Click to expand...
Click to collapse
I did. It went through the update process on the phone. But, once again, when the phone restarted the it went right back to the "firmware update " screen. That tells me it's a hardware issue, right?
This doesn't make sense. If you had a bad NAND then the flash would fail because it wouldn't pass the hash check. If you had a bad CPU, it wouldn't be able to just load firmware update.
I am guessing that you have a corrupt misc, persist or persistent partition.
Use the patched LG UP to dump misc, persist and persistent. Then...
With the phone off, hold vol down and plug in the USB cable. That should that you to fastboot. If it does:
fastboot format misc
fastboot format persist
fastboot format persistent
Let me know what happens. If that fixes your phone, I can help you determine which partition is corrupt and help you fix it.
runningnak3d said:
This doesn't make sense. If you had a bad NAND then the flash would fail because it wouldn't pass the hash check. If you had a bad CPU, it wouldn't be able to just load firmware update.
I am guessing that you have a corrupt misc, persist or persistent partition.
Use the patched LG UP to dump misc, persist and persistent. Then...
With the phone off, hold vol down and plug in the USB cable. That should that you to fastboot. If it does:
fastboot format misc
fastboot format persist
fastboot format persistent
Let me know what happens. If that fixes your phone, I can help you determine which partition is corrupt and help you fix it.
Click to expand...
Click to collapse
I do appreciate your help. I attached a photo of what the ADB command prompt was telling me. but if for any reason you can't see it. It's telling me formatting isn't supported. Perhaps I'm using the wrong cmd
Weird.
Try erase instead of format.
runningnak3d said:
Weird.
Try erase instead of format.
Click to expand...
Click to collapse
Yeah. Everything about this situation is baffling. It just randomly started to happen.
Also, That command didnt work.
Did you unlock the bootloader with the bin file or using DirtySanta?
If it was with the bin file, you need to unlock it again. If you used DirtySanta, there is nothing that can be done. When you flashed the KDZ it replaced aboot, and now you can't fix the corrupt partition unless you can unlock it again.
I always tell people that if you have TWRP, don't ever flash the KDZ to try and fix your phone. There is nothing that it will do that you can't do if you have TWRP, and in your case you have an issue with a partition that isn't flashed by the KDZ ... and now no way to fix it.
Sorry, just reread your first post. I read recovery the first time and just assumed TWRP, but you meant the "vol down / press power" screen.
Is it possible an OTA got taken? Either way, I hate to be the bearer of bad news, but there is no fixing this except sending it to LG.
---------- Post added at 07:45 AM ---------- Previous post was at 07:38 AM ----------
Actually, send me a PM. I can send you a tool that can wipe those from download mode. You may be able to save your phone yet.
I didn't try to root the device. It did all this on its own. The device is still under warranty. I got in contact with LG about it. They sent me an RMA. All i tried to do was use Uppercut to try and fix it. Everything was stock on it when it did this. I purchased it brand new unlocked from B&H Photo. But, nonetheless thank you for your time and effort to help me.
I'm going to send out back to LG. But, i wouldn't mind getting that tool from you. I like LG devices. So i do plan on getting more.
I had the same issue. The phone was locked onto the firmware update and I could not override it. Pulling the battery and trying to re-flash the phone would not work. LG could not resolve it unless I sent the phone in for repair. ($42.00 + Shipping both ways)
This is what finally worked. Use the USB cord from your charger and connect the phone to a computer then power up the phone. This will override the firmware update and let the phone boot up normally.
Good Luck.
I gave up on this phone a while ago because of this issue. The only way i could start it up was if it was plugged in.. recently i started playing around with it again due to aosp second screen and started looking into the issue again. I forget where (it wasnt on xda) but i read that putting a little bit of water on the c type plug that goes into the phone fixes the issue. I dont know how or why someone discovered this and i first thought that it was someone joking or being malicious but i tried it and after 8 fricken months my phone can boot untehered!