Through my searches I couldn't quite find a problem like mine.
Here goes.
My device will not reboot into fastboot mode, using adb reboot bootloader or restarting and entering recovery mode it just restarts the system.
If I instead enter adb reboot recovery it shows a black screen with the android droid laying on it's back with a yellow triangle with an exclamation mark. text on the screen reads waiting for command but fastboot commands do nothing.
any help would be appreciated.
is your v20 a VS995
LASERWOLF452 said:
is your v20 a VS995
Click to expand...
Click to collapse
No, it is an LS997 the sprint us model.
MadnessChi1d said:
No, it is an LS997 the sprint us model.
Click to expand...
Click to collapse
Hold volume down while plugging in the usb cable. With the other end of the cable plugged into your computer.
tymestopm said:
Hold volume down while plugging in the usb cable. With the other end of the cable plugged into your computer.
Click to expand...
Click to collapse
It just shows the lg screen then the charging screen.
I am having the same issue with the LG V10. There are very few mentions out on internet of the software version I have on my phone (21J). Maybe T-mobile is silently patching with and OTA to remove fastboot access?
I have the same issue. I'm on the December 2016 security patch.
Fastboot was pulled by the carriers (except TMobile, but even their fastboot is only good to unlock the bootloader).
-- Brian
runningnak3d said:
Fastboot was pulled by the carriers (except TMobile, but even their fastboot is only good to unlock the bootloader).
-- Brian
Click to expand...
Click to collapse
ls996 sprint i have the same problema ....there anyway to get fastboot please
I am having the same issue on my VS995, and I was wondering if there was anyone that has found a fix/work around? This post is literally the only mention on not having fastboot, or not being able to boot into fastboot. Any help is greatly appreciated.
LG V20 Fastboot
runningnak3d said:
Fastboot was pulled by the carriers (except TMobile, but even their fastboot is only good to unlock the bootloader).
-- Brian
Click to expand...
Click to collapse
Why on earth would they remove fastboot? Currently I am having an issue with texting, I can text everyone except my wife... I have cleared the cache, rebooted the device, removed the years of text message thread that we had on it.. Since I can text others and get no failure to send messages, (most of the time), and can make calls to my wife, (and everyone else for that matter), I believe it to be a software issue, resetting the phone to factory default I think would be a good troubleshooting step.. Also if I were to sell the phone I would love to be able to reset it to factory default, and clear all my data off the phone???
Fyrebaugh said:
Why on earth would they remove fastboot? Currently I am having an issue with texting, I can text everyone except my wife... I have cleared the cache, rebooted the device, removed the years of text message thread that we had on it.. Since I can text others and get no failure to send messages, (most of the time), and can make calls to my wife, (and everyone else for that matter), I believe it to be a software issue, resetting the phone to factory default I think would be a good troubleshooting step.. Also if I were to sell the phone I would love to be able to reset it to factory default, and clear all my data off the phone???
Click to expand...
Click to collapse
Because the carriers are wicked and want to control what you do with your phone
Sent from my LG-H910 using XDA Labs
Fyrebaugh said:
Why on earth would they remove fastboot? Currently I am having an issue with texting, I can text everyone except my wife... I have cleared the cache, rebooted the device, removed the years of text message thread that we had on it.. Since I can text others and get no failure to send messages, (most of the time), and can make calls to my wife, (and everyone else for that matter), I believe it to be a software issue, resetting the phone to factory default I think would be a good troubleshooting step.. Also if I were to sell the phone I would love to be able to reset it to factory default, and clear all my data off the phone???
Click to expand...
Click to collapse
You can do that in recovery. Hold volume down press power until the screen turns on then tap power repeatedly and itl prompt you to factory reset. It does this in stock recovery, if you're rooted itl boot into twrp (and youll have to manually enter the wipe menu and format data)
just got an "h910" from aliexpress (it says v10l), can't go into fastboot mode using the buttons or "adb reboot bootloader" ...
(but "adb reboot recovery" seems to go into recovery ...)
pierro78 said:
just got an "h910" from aliexpress (it says v10l), can't go into fastboot mode using the buttons or "adb reboot bootloader" ...
Click to expand...
Click to collapse
PS : I was fool enough to try DirtySanta for Newbies ( https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278 ) and it worked - at one step I had to go into fastboot with the buttons and this one time I was lucky enough and fastboot mode worked
pierro78 said:
just got an "h910" from aliexpress (it says v10l), can't go into fastboot mode using the buttons or "adb reboot bootloader" ...
(but "adb reboot recovery" seems to go into recovery ...)
Click to expand...
Click to collapse
Read the thread you just posted in. Post 8 in particular.
Dirty Santa replaced aboot (the part of the bootloader that provides (or not) fastboot) with an engineering one that does have fastboot with the ability to flash and also doesn't care if the bootloader is unlocked or not.
As much as this intrigues my curiosity, I'll take a pass for now........... I've rooted and TWRP'd phones in the past, but my past was a more simple time, with phones like the Droid, Droid-x, and those variants............ you just rooted it and it worked, simple. Nowadays, you have to jump through so many hoops, and if you miss just ONE, you probly brik'd yer phone. Nah................ will just wait some time, non rooted phones seem to do more these days
All I wanted to do was unlock bootloader and install twrp. what a bunch of bullcrap! Screw you Sprint for removing the bootloader and trying to control our phones. This phone is complete trash. I can't even install project treble for android 10.0 Q. I'm thinking about just getting an xs max and jailbreaking it. Forget android and all these fragmentation issues. At least iPhones receive updates past 2 years.
Having the same issues as everyone else. VS995. At first I thought it was only verizon... Just ordered a OnePlus 7 Pro. Hoping for something better than what the carriers can lock down.
Related
First off, I searched for someone with a similar problem and couldn't find anyone in the same situation.... Also, I'm very familiar with the root/flashy/etc. process coming from a GNex
So I rooted the G2, no problem at all (before OTA). Trouble came when I tried to flash recovery. I couldn't get it to do so, but I was following a guide that stated I needed to perform the OTA before flashing TWRP.
So I finally accepted the OTA and when I did, see first pic, it clearly asked if I wanted to perform a factory reset, I accepted. Then I get dumped into Fastboot, see second pic, and I cannot get out of Fastboot at all. In addition to that, when I plug it up via USB, it won't recognize the phone at all either.
Verizon of course said I was good to take the phone back and have it replaced, but thanks to the "tell tell" message on the Factory Reset option, check first pic - top left corner, they can clearly see it's rooted and will likely not replace it, and I'm out a ton of money.....
Are there any ideas out there as to how I can recover anything????
Thanks in advance!
You not the only one! I think the recovery partition may have got corrupted from a bad CWM flash file. I get the same black screen, fast boot bull****... phone still works at least lol.
You can always flash back to stock with the lg mobile suite, got me out of a bootloop. It should fix recovery partition I would hope
crielstar said:
You not the only one! I think the recovery partition may have got corrupted from a bad CWM flash file. I get the same black screen, fast boot bull****... phone still works at least lol.
You can always flash back to stock with the lg mobile suite, got me out of a bootloop. It should fix recovery partition I would hope
Click to expand...
Click to collapse
Where do I go to get that?
Or is there anyway I can actually make the phone connect to my computer via USB so that I can hopefully use the Verizon Upgrade Assistant?
I used the LG mobile support tool found here: http://forum.xda-developers.com/showthread.php?t=2432476
follow the steps, after the top right of that program will have drop down with "recovery update" or something to do a full restore.
I hope you can get into download mode for this, power +volume up
Good Luck!
crielstar said:
I used the LG mobile support tool found here: http://forum.xda-developers.com/showthread.php?t=2432476
follow the steps, after the top right of that program will have drop down with "recovery update" or something to do a full restore.
I hope you can get into download mode for this, power +volume up
Good Luck!
Click to expand...
Click to collapse
Many thanks! I'm downloading everything now, so we'll see....
blw1230 said:
Many thanks! I'm downloading everything now, so we'll see....
Click to expand...
Click to collapse
This helped me in the same problem, didn't have to go back to stock:
http://forum.xda-developers.com/showthread.php?p=45760203
VZW LG G2
jesssiii said:
This helped me in the same problem, didn't have to go back to stock:
http://forum.xda-developers.com/showthread.php?p=45760203
VZW LG G2
Click to expand...
Click to collapse
Thanks for the thought, however that thread is assuming you have ADB access which I cannot get my computer to recognize my phone while it's in fastboot through ADB....
Downer I have a day old phone and I may have to go ahead and make an insurance claim against because I'm not paying $549 for a new one...
Or is there a way I can completely bork this so it doesn't even get to the Factory Reset option, or at least so it won't show Rooted, so I can just take it back to VZW haha???
Hold the volume up and while holding, plug in USB. Should put it in download mode. If adb then can recognize, reinstall the recovery. If not, hold the power and volume down until it starts to reboot, when you see the LG logo, let go and immediately repress them and hold until it asks you to push the power button to reset phone. When you do reset, it will actually take you to the twrp recovery.
VZW LG G2
So if u can get into download mode use the lg moble softwear to restore it.adb is not required for that
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.
I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app
Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.
Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.
Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.
Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.
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.
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 ?
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.
Hey!
Thanks for your fast reply and your helpful tone.
However, when I choose Recovery mode it once again stucks in bootloop resulting in me never accessing recovery mode
npjohnson said:
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.
Click to expand...
Click to collapse
I am not sure my first reply was sent (having an unstable connection) so trying again:
When in bootloader and pressing recovery mode it goes straight back to bootloop. Hence, I cannot access recovery mode. Feels like a catch-22.
robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
maybe if you posted it in the correct forum, you would get an answer...
Moved to the correct board...
If you can't boot the phone and you can't boot to recovery and Android debugging and oem unlocking are not enabled, there isn't much (read anything) you can do. Maybe take it to a local repair shop and see if they can replace the motherboard for you.
robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Heating the phone temporarily boots the phone. (You can also check videos for saving data in bootlooped LG phones)