Test Pin Location - LG V20 Questions & Answers

Hello, while removing dirty santa on my v20 h990n I bricked it... hard. I am in no rush I have a V30 but I would still like this functioning as a spare. I was wondering what the test pins are that need to be shorted in order to force it into download mode. I have done extensive searching and have seen it mentioned in v20 posts but never details given.
For the curious I followed the instructions on the dirty santa post but I was accidentally in USB mode when I did the DD command that copied the abootbackup file I created when I first installed root.
It will not boot or even power on the screen. It will only give the power on vibrate when you press the power button after the battery/cable have been disconnected.
not seen by device manager, ADB, or LG programs.
The only thing it will display on the screen is a blinking battery ! when the battery is removed and usb connected.
My first brick in about 10 years of rooting phones, hopefully I can get it back. I am hoping the test pin will force it into a download mode so I can use LGUP or ADB to get it working again.

r4736 said:
Yeah, it's fun. I wasn't paying attention and used did to restore the aboot backup while in USB mode. So it does practically nothing. Detectable by nothing, nothing on the screen. The only signs of life are it doing the power on vibrate, and the creek will only come on to blink a ! Battery warning if plugged in with battery removed. Thank goodness it's just a spare, v30 visits my daily.
I'm half thinking about taking it to a LG repair center here in Hong Kong. If it's not expensive if like to have it working.
Click to expand...
Click to collapse
I'm quoting you from the other thread here as it's best not to muddle up runningnak3d thread.
When I first responded to your question I did not consider such a scenario. Normally the V20 goes automatically into 9008. I do now after reading your case, remember another person who had the exact same symptoms. He too had failed during dirtysanta root procedure. I'm not familiar with that procedure myself. I had a H918 and I didn't use the engineering aboot.
So it would seem you have a blank 'aboot' partition? In any case that is very unusual brick.
I would try the lg repair like you said, or 3rd party service with "box" (you know like, infinity, octoplus etc).

askermk2000 said:
I'm quoting you from the other thread here as it's best not to muddle up runningnak3d thread.
Click to expand...
Click to collapse
I appreciate that.
I had assumed I was sol, but still had to check. And I didn't fail rooting it, I was actually returning it to stock. It seemed pretty simple but after running dd and powering off to go into download mode that was all she wrote.
Method 1b: (TWRP, with file from another source)
This is simply a tweak of the above resulting from recalling there is a backup of aboot already on the phone itself.
Boot into TWRP (DOWN + Power with a brief release during LG logo).
Run `adb shell` and type (or copy&paste) the following commands:
Code:
dd if=/dev/block/bootdevice/by-name/abootback of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
Get into Download mode. Power off phone from TWRP. Press and hold UP, then power phone on (no need to hold power).
Load the appropriate KDZ file onto your phone via LGUP.
Thanks again for responding and thinking about my problem.

r4736 said:
dd if=/dev/block/bootdevice/by-name/abootback of=/dev/block/bootdevice/by-name/aboot
Click to expand...
Click to collapse
That command is wrong. It's supposed to be "abootbak", without the c. But I'm not sure if that had anything to do with it. Though it's strange that the instructions seem to re-lock the bootloader while still having twrp on recovery partition.
BTW, did you try to enter fastboot mode? I believe there is a key combination for that but I don't remember it now. Though if aboot is erased that shouldn't work since that's where fastboot is.
Edit: Combination is: Press and hold VOL down + insert usb cable.

askermk2000 said:
BTW, did you try to enter fastboot mode? I believe there is a key combination for that but I don't remember it now. Though if aboot is erased that shouldn't work since that's where fastboot is.
Click to expand...
Click to collapse
I can't go into any mode. Nothing comes up on the screen. I've tried all the key combos but nada. Just does the power on vibration. Nothing shows up when connected to the computer in adb, device manager, or lgup.
It's the damnedest thing, never screwed up a phone that bad before.
Also I think it's named abootback because that's the name of the backup of that partition created when doing the root process.

r4736 said:
It's the damnedest thing, never screwed up a phone that bad before.
Also I think it's named abootback because that's the name of the backup of that partition created when doing the root process.
Click to expand...
Click to collapse
No, its abootbak. The command is not pointing to a backup. It's pointing to a partition, and there is no partition called "abootback", only abootbak, xblbak, recoverybak, lafbak and so on. These are part of the stock partition layout. I'm positive the dirtysanta root procedure does not include creating an additional partition on the device. That certainly would be hilariously risky and unnecessary.
Anyway, sorry I couldn't be of more help to you.

askermk2000 said:
Anyway, sorry I couldn't be of more help to you.
Click to expand...
Click to collapse
It's no problem, thanks for pondering my peculiar predicament.

Have you tried volume down and plugging in usb.....

stinka318 said:
Have you tried volume down and plugging in usb.....
Click to expand...
Click to collapse
I had the same issue . Literally nothing I could do. Only time screen turns on is when battery is out and you plug in a USB cable. Had to send it to Lg

Related

Bootloop / No Recovery / History Unknown

Good evening XDA,
I've got a Nexus 6p (obviously), and can't get it to boot. Unfortunately, I don't know the exact history as to how it's in this state.
I've tried everything I can think of and read every guide/steps/forums I can find that relates to my situation.
I can get to the bootloader and issue Fastboot commands. I've got adb/fastoot/drivers installed via the sdk/platform tools, and drivers are up to date as far as I can tell.
-I'm using the OEM cable attached to my computer (Surface Pro3, Windows 10)
-I can unlock/re-lock the bootloader as I wish.
-I've tried WugFresh toolkit, flash factory + unroot. All completes, but phones continues to loop even after leaving it for an hour+.
-I've tried Heisenbergs guide for manually flashing stock google images via fastboot to no avail. Tried several different google images. Everything completes, but it still just loops.
-I can get all fastboot commands to complete with no errors, but the phone just simply bootloops at the google logo, or if I leave bootloader unlocked it loops with the orange triangle & google logo. I have left it looping for at least an hour+, but it doesn't finish:crying:
-Stock recovery or a fastboot flashed trwp recovery simply won't boot, it just goes to the google logo and loops, I don't get the dead android w/triangle. "Recovery" in the bootloader selections is RED, if that means anything. Tried fastboot commands to boot recovery, but just sends it to the google logo and loops.
-Adb commands don't work, only fastboot commands.
-During flashing a google stock image with fastboot, the only thing that stands out is "max download of ####### reached", or something similar, but it still completes.....?
Seems to me that I've got a true brick (first ), and just need to send it in for repair.
Any help would be greatly appreciated. TIA.
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
TnT_ said:
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
Click to expand...
Click to collapse
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Dhickory said:
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Click to expand...
Click to collapse
Does all the data in the bootloader look fine? The storage size etc?
TnT_ said:
Does all the data in the bootloader look fine? The storage size etc?
Click to expand...
Click to collapse
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Dhickory said:
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Click to expand...
Click to collapse
Usually with board failure - that I saw in other threads - there are missing fields. My phone had a little glitchyness after I accidentally flashed the userdata.img - which caused my 128gb to become 32gb, which I found amusing - Other than that, I don't know. I'm sure others would reply.
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Dhickory said:
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Click to expand...
Click to collapse
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Jammol said:
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the link, and I've been reading the "Let's figure out this brick together" thread. The link you posted requires ADB commands to work to fix the EFS partition, but I can only run fastboot commands. ADB nor Recovery work on my device. Still reading...
Woohoo! Huawei replaced the phone, no questions asked. I think the saving grace was being able to flash stock images, and relock the bootloader. May be helpful to anyone else in this situation that can only run fastboot commands, and no recovery.

LG H918 V20 Hard Brick - Dirty Santa

Got a new V20, but it's been hard bricked after running step 3 of the Dirtysanta patch.
Before running Dirtysanta, I did unlock the bootloader by rebooting into fastboot and running
Code:
fastboot oem unlock
I verified it was unlocked through fastboot.
In order to install TWRP, I started Dirtysanta from the top. It seemed to be going successfully until I ran step3.bat to reboot the phone.
The screen only comes to life when taking out the battery completely and plugging it in. It brings up a no battery warning screen.
If the power button is pressed, the phone vibrates but the screen remains off. Same with pressing vol. down + power while trying to get into recovery mode.
Holding vol. up and plugging in the USB to get to download mode hasn't worked. I don't know what else to do.
edit: one other person in the dirtysanta thread has indicated he had the same problem. seems that dirtysanta completely bricks T-Mobile V20s. welp.
mocklee said:
Got a new V20, but it's been hard bricked after running step 3 of the Dirtysanta patch.
Before running Dirtysanta, I did unlock the bootloader by rebooting into fastboot and running
Code:
fastboot oem unlock
I verified it was unlocked through fastboot.
In order to install TWRP, I started Dirtysanta from the top. It seemed to be going successfully until I ran step3.bat to reboot the phone.
The screen only comes to life when taking out the battery completely and plugging it in. It brings up a no battery warning screen.
If the power button is pressed, the phone vibrates but the screen remains off. Same with pressing vol. down + power while trying to get into recovery mode.
Holding vol. up and plugging in the USB to get to download mode hasn't worked. I don't know what else to do.
edit: one other person in the dirtysanta thread has indicated he had the same problem. seems that dirtysanta completely bricks T-Mobile V20s. welp.
Click to expand...
Click to collapse
Yes dirtysanta completely bricks tmo devices. THATS WHY ITS NOT SUPPORTED There is no way to fix. take the insurance loss and get it replaced.
Then which is the best way to root for TMO?
suaverc118 said:
Then which is the best way to root for TMO?
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/development/lg-h918-t-mobile-one-click-recowvery-t3491969
suaverc118 said:
Then which is the best way to root for TMO?
Click to expand...
Click to collapse
As jerry has linked you. The one that specifically states its for tmo
Appreciate y'all fellas
me2151 said:
As jerry has linked you. The one that specifically states its for tmo
Click to expand...
Click to collapse
Is there anyway to revive a v20 tmo that is hard bricked ? I mean literally no power on. Even computer just makes a buzzer sound like I lost at a spelling bee sound when I connect the phone to it. I was attempting to flash older fw with cracked v20 lgup tool. Any advice? I think it's just a Frisbee now :crying:
LG-h918 bricked with old 9008 loader
I am trying to unbrick an LG-h918 using QFIL and I keep getting sahara fail. I am open to ANY options to unbrick this device!not just QFIL. Any help would be greatly appreciated
jevans85 said:
I am trying to unbrick an LG-h918 using QFIL and I keep getting sahara fail. I am open to ANY options to unbrick this device!not just QFIL. Any help would be greatly appreciated
Click to expand...
Click to collapse
There are 0, an h918 in 9008/EDL mode is DONE. The firehose that leaked for the other models of v20 won't work for it (can't remember if its an arb check, the differing firmware signature, or both,, its talked about somewhere in the firehose/9008 test point thread). If you don't at least have download mode or twrp there's nothing to be done for it without sending it LG and paying them (if they bother to dig out their copy of the firehose or just replace the board or just tell you sorry, idk, but they're the only ones who might be able to do anything)

DirtySanta Root Attempt on Verizon LGV20 - Stuck After Step 3 Sitting on Fastboot

Hi, I don't have enough posts to ask this in the actual DirtySanta thread.
I meticulously followed the steps in the DirtySanta thread making sure I had all the correct software, all the pre-requisites, all files in my ADB folder (except SuperSU zip, which is on the SD card on the phone). Suffice it to say that I did all the steps exactly as written in the guide. I was prompted when to run the next batch files each time, etc. Entered the proper commands in the terminal utility, and so on. Everything as written.
After clicking on step3.bat, the phone immediately rebooted to a Fastboot screen. In the meantime, the batch files disappeared off my desktop.
So, for the past 15 minutes or so the phone has been sitting on Fastboot and vibrating away.
Here's what I see in the small Fastboot screen:
Fastboot Mode (in red)
stuff like Product_name, Variant, HW_Version, etc. up until it says LOCK_STATE.
Ok, after all of that basic stuff, it says:
[1090]
[1140] Fastboot mode started
[1670] fastboot: processing commands
[17600] usb_read() transaction failed; txn_status= -1
[17650] usb_read: DONE: ERROR len=64
[1700] fastboot: oops!
[17750] fastboot: processing commands
And that's where it sits, doing seemingly nothing and vibrating away.
Can anyone assist?
Try a different usb port. then rerun step 3.
me2151 said:
Try a different usb port. then rerun step 3.
Click to expand...
Click to collapse
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Heyitsrick said:
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Click to expand...
Click to collapse
First off, a big thanks for helping me.
Update: OK, changing the USB port worked I re-ran Step3.bat. I have made it through getting to TWRP, and have done these steps:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
So, with that all complete, it's rebooted to a Verizon screen (horizontal progress dots) and a low buzzing.
I did try what you mentioned in the guide to get over the wait time by pulling the battery, reinserting with vol down key pressed and re-attaching the USB to flash boot2.img via fastboot, but it didn't get back to fastboot after the battery/voldown/usb. It went back to the same Verizon screen after the obligatory "Corrupt" screen came on.
Can I assume that I can wait this out for 20 minutes, or did I miss something in how to interrupt this waiting period for first setup? I do want to (and know I have to) flash boot2.img.
EDIT: wasn't holding vol key down long enough to get into fastboot. Doh. Just flashed boot2.img and rebooted.
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Heyitsrick said:
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Click to expand...
Click to collapse
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
NegativeX said:
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
Click to expand...
Click to collapse
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
The first time I tried this, it booted up fine, but it went right back to the Logo screen. Doh! I figured perhaps I wasn't waiting long enough with the Volume Down button so I tried it again. What happened the first time when it rebooted to the Logo screen is I released the Volume Down button the moment the phone started to turn on (you feel the vibration). That's when it booted back to the Logo. This second time, I removed the battery again while it was on that never-ending Logo screen to power it off and disconnected the USB cable again. I put the battery back in, then with the Volume Down button pressed down, I reconnected the USB cable. The difference this time is that I did not release the Volume Down button this time UNTIL I saw it was in the Fastboot screen and not the Verizon Logo.
So, at this point the phone was on the Fastboot screen and I saw it was it was ready to go, so I initiated the ADB command to flash boot2.img. It went through its paces and once it got back to the ADB command prompt, I did an ADB Fastboot Reboot command. It rebooted, first with the obligatory corrupt warning, then the Verizon Logo and progress dots, but then after a short while I got the "Hello" screen in red and I knew it was actually going to finish. Whew! Relief! At that point I was eventually at the phone's setup screen for a new user, and I finished setting up the phone, reinstalling apps, etc.
One caveat in this: I don't know why, but even though I had gone through all the steps in "4" section of the instructions, when I checked Root, I wasn't rooted! Huh?
In other words, I had already gone through this part:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
Click to expand...
Click to collapse
After setting up the phone and reinstalling my apps, I opened up the SuperSU app, and it said there was no executable installed. In other words, it didn't recognize that I had flashed it in step 4.1. Perhaps flashing boot2.img overwrote that? Not sure, but at this point, I set about to figure out how to boot into TWRP Recovery on the phone (not fastboot) to flash it from there (again).
It took me a while to find the instructions on how to boot into TWRP, lol, and it's a little unnerving that before it boots to TWRPyou are warned that all your data is going to be overwritten before you can boot to it, but it did get me back into TWRP. Once in TWRP, I re-flashed Supersu-blahblah.zip and rebooted via the system reboot. (did not wipe any caches again, though).
After reboot, I checked root again, and this time after a bit SuperSu brought up the permissions screen for the Root app that I had to allow, and it brought back a successful Root message.
I then set about to do what I really wanted to do with root - bypass the Verizon entitlement check for hotspot usage, and got that working fine.
All in all, I have to say this was the diciest rooting I've ever had to go through. I guess that's because of Nougat and that there can't be (at least not yet) a "one-click" root. But man, was I worried when I was at the point where I first posted in this thread. I bought this phone as a "new-resale" (never used) phone from Swappa.com for $450, so if I bricked it, I was out of luck. But it seems to be ok now.
Heyitsrick said:
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
​
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
Click to expand...
Click to collapse
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
NegativeX said:
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
Click to expand...
Click to collapse
Late response - sorry.
There must be something we each did differently, as we both have the same phones, same carrier, same software revision (13a). I was able to get to TWRP via the button method on the phone. Didn't use ADB for that. I was presented with an ominous white screen about all files will be wiped/deleted, but when accepting that (and hoping for the best, lol), it just went to TWRP. So, again...something or some step(s) must be done differently to get to that point on your end from what I did.
I'm guessing you're through with doing the flashing on this thing, so this is all moot now.
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
kratos380 said:
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
Click to expand...
Click to collapse
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
me2151 said:
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
Click to expand...
Click to collapse
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
kratos380 said:
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
Click to expand...
Click to collapse
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
me2151 said:
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
Click to expand...
Click to collapse
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
kratos380 said:
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Sorry for the constant posts but i followed the steps on that thread, deleted the misc/fota files and it stopped it going to twrp and booted to the lg logo with the black screen, i waited there for about 2-3 hours to no avail rebooted into bootloader tried the fastboot img 2 and the same thing happened it was just stuck at the lg logo now when it boots to the fastboot screen however adb doesnt recognize the device anymore but fastboot does. Is it time to kdz and start over ?

Bricked phone

Hey guys, i made a major mistake and bricked my phone. I need to get this working badly but think I am screwed. Here is where I am:
The phone had stock B32 and stock recovery. completely stock phone. From this thread: https://community.zteusa.com/discus...safe-method-unlock-bootloader-usa-axon-7-only
A2017UV1.0.0B29_MoveToSDCard.zip
I got some error message when I try to flash A2017UV1.0.0B20_MoveToSDCard.zip... so I rebooted the phone and it seemed fastboot was enabled finally so I figured I was good to go.
Then I used the Axon7toolkit to lock the bootloader but I think it flashed the FASTBOOT_UNLOCK_EDL_N , and thats what bricked my device. After it sucessfully flashed, i rebooted the device and
it seems to be stuck in FDU mode.
Currently:
Nothing ever shows up on the screen, no bootloader screen, ZTE logo, nothing. The red power light will flash on and off and in Windows it will only show up in DFU mode. I have tried to boot into EDL mode many times and have had no luck.
Seems like I am stuck, any way out?
thanks :crying:
4th brick category
yea thats what i thought...
spacemanvt said:
yea thats what i thought...
Click to expand...
Click to collapse
Ouch... Read all my comments on the dfu repair manual, they seem to have been useful for many people
Choose an username... said:
Ouch... Read all my comments on the dfu repair manual, they seem to have been useful for many people
Click to expand...
Click to collapse
Sorry i am bit a confused... is there anyway to do this without opening the phone?
spacemanvt said:
Sorry i am bit a confused... is there anyway to do this without opening the phone?
Click to expand...
Click to collapse
Yeah but i haven't been able to pull it off. What I was saying up there is that the 4th category brick repair manual was kinda badly explained, so when I had to follow it, I shared all that I had to figure out on my own so that others could do it faster (I had to pry the battery off, and try like 40 times until miflash decided to install stuff on my phone).
The theoretical way to fix your phone without opening it up is by entering FTM mode somehow. Some people were able to get there, they say they drained the battery completely first (no idea how, given that not even the display fires up) and then they held the key combination to enter FTM (vol down+power i think). It's unclear if you have to have the phone connected to the PC but I believe that's the case since the battery should be dead and you need to use adb after FTM appears on the screen.
If you manage to enter FTM mode (a box with 'FTM' should appear [or 'Factory test mode', i don't remember]), you have ADB. So you simply issue 'adb reboot edl' and voila, you are on EDL. Then you install a FULL_EDL package for your device through MiFlash and you're done
Choose an username... said:
Yeah but i haven't been able to pull it off. What I was saying up there is that the 4th category brick repair manual was kinda badly explained, so when I had to follow it, I shared all that I had to figure out on my own so that others could do it faster (I had to pry the battery off, and try like 40 times until miflash decided to install stuff on my phone).
The theoretical way to fix your phone without opening it up is by entering FTM mode somehow. Some people were able to get there, they say they drained the battery completely first (no idea how, given that not even the display fires up) and then they held the key combination to enter FTM (vol down+power i think). It's unclear if you have to have the phone connected to the PC but I believe that's the case since the battery should be dead and you need to use adb after FTM appears on the screen.
If you manage to enter FTM mode (a box with 'FTM' should appear [or 'Factory test mode', i don't remember]), you have ADB. So you simply issue 'adb reboot edl' and voila, you are on EDL. Then you install a FULL_EDL package for your device through MiFlash and you're done
Click to expand...
Click to collapse
Right, i read that post also... it was only one guy though... sounds like a weird lucky guess.
i think i will have to send it back to ZTE... hopefully they will not be mad and fix it

no OS, no TWRP, no fastboot..... no chance?

when reinstalling a ROM earlier today, I got an error 7 ... no problem. probably TWRP problems... so, i go to reboot phone to recovery to begin fresh, and now, TWRP boots, but the screen flashes blank every couple seconds, for a second, then the TWRP splash screen comes back up. blank screen, then TWRP splash screen again. never gets further than that. because I dont have an OS installed, i cannot access debugging for adb. because i deleted my OS, i cannot allow fastboot, to flash a new recovery and begin again. ..
I am broke, and cannot afford to pay for a new replacement thru insurance or to just go buy a junker phone and make do with that.
am i ****ed, or is this recoverable...? ive been searching the forums, but cannot seem to find the answer, and im starting to get nervous enough that its sorta beginning to compound my problems more than i can deal with.
edited to add again: .... battery removed + volume dn then insert battery will not enter fastboot. im about to paperweight this ****.
again edited - Sprint LS997 is phone model. no TOT'ing for me.
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
XblackdemonX said:
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
Click to expand...
Click to collapse
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
elijah420 said:
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
From fastboot you can reflash TWRP which from where you can reflash the OS which would unbrick the phone.
elijah420 said:
i have access to: LAF (download mode)
Click to expand...
Click to collapse
If you have access to download mode, can't you reflash your phone using the LGUP with the backup that did in the first place?(you did a backup of the original OS right?)
elijah420 said:
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
Sounds like empty or bad battery to me. When did your phone start acting up upon ya? Right after root or you had it working with root etc before u ended up into such situation.
Also, as XblackdemonX pointed out, you can still use LGUP to stock.
I'm pretty sure that happened to me. And I fixed my H990DS by flashing kdz file in download mode with LG BRIDGE.
There's a guide about how to unbrick any v20 around here.
@elijah420 What software version were you on before this started? Why does it matter? If you were on ZV7 or earlier, then you can flash a VS995 KDZ in download mode, root it, and then fix your phone. If you were on ZV8 or later, then you still might be able to salvage your phone, but you will have to run firmware from another model since you will not be able to root and flash back to Sprint firmware if you were ARB 1 or later. Better than having a totally busted phone though.
Last possibility is to use the debug firehose that I have, but that is an even bigger unknown than running firmware from another model.
-- Brian

Categories

Resources