I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.
epr2175 said:
I apologize if this is in the wrong section this is my first time posting to xda
I tried rooting my tmobile LG V20 and cant seem to get into TWRP. Every time i boot up it goes to screen that says
"your device software cannot be checked for corruption. Lock the bootloader"
then it boots to a white screen that says Encryption Unsuccessful with a reset button at the bottom. I am unable to get into twrp with the power and volume down button.
Click to expand...
Click to collapse
There is another thread around here that answers your problem. I had the same issue. Something along the lines of plug in phone and open command prompt with command : and reboot bootloader and reboot phone. When you see twrp booting and installing files hit enter and you should boot into twrp again.
I tried it about 35-40 times and failed. It finally worked after many tries. Look for the thread around here somewhere though.
---------- Post added at 04:42 AM ---------- Previous post was at 04:38 AM ----------
Found it, its under questions and answers. The title is "hi guys my tmobile is stuck in bootloop"
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Also stuck at the same page with the reset button please help
Locking/Unlocking Bootloader Works!!
Thank You!!! You finally got my phone to work after trying for a few days! :laugh:
jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you for this tips, i Lock the bootloader and then Unlock it again as your command, and viola my phone back to life haha
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
still have issue, i can't install ane apps now.. how to solve it please ?
jjr3211 said:
Happed to me too. Turn off tne phone hold vol down plug in phone that will get you into bootloader lock it then unlock it again. Mine booted right up after that.
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
You saved the day my friend! Locking and unlocking via fastboot did the trick. Phone booted right up.
runningnak3d said:
The reason locking / unlocking your bootloader worked is because that formats data. If you would have formatted data in TWRP (NOT wipe -- FORMAT), then your problem would have been solved.
You got lucky, and OEM Unlock was still enabled in developer options. If it hadn't been, then you would have locked your bootloader and wouldn't have been able to unlock it.
-- Brian
Click to expand...
Click to collapse
Okay - I have this too now. I have a h910 that I just followed runningnak3d's dirty santa guide on. Been flashing all around the last 2 weeks - learning a lot along the way. But today I flashed back to stock 10r. I fomatted data in TWRP - typed yes etc and it just reboots to that. I went to TWRP and installed Alpha Omega Oreo - same error. Restored one of my backups of Lineage I get the same error. So what is the right way out of this problem?
KDZ back and follow your dirty santa guide to re/unlock the bootloader? (I sure hope Brian is still around reading these) Not to screw up the terminology - but if TWRP still boots as my recovery - doesn't that mean my bootloader is unlocked.?
Well - not sure what I was doing yesterday... But wiped all, format data and factory reset in TWRP this morning and flashed h910 10r and then Magisk v20.4 and it worked. Could it be as simple as forgetting to flash Magisk? Maybe that is all that was wrong?
Thanks for reading.
Well if you find yourself in this same sticky spot - check out this here
I flashed 2018-04-15 level and my restore worked without issue.
YMMV
Good Luck
I formatted data in twrp. No change
The correct answer is to downgrade twrp, at least only that fixed it for me.
Related
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.
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
same problem here and cant find solution ...
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Flash the latest su and your fine.
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
did that but my adb says no devices or emulators?
jo4mvp24 said:
did that but my adb says no devices or emulators?
Click to expand...
Click to collapse
Make sure your on charging mode and you have adb debug enabled
send the adb reboot recovery command as soon as the twrp connects to the computer. as soon as you hear it connect to the computer it should work if your drivers are working.
charlieb620 said:
Make sure your on charging mode and you have adb debug enabled
Click to expand...
Click to collapse
how do i do that when phone stuck on encryption unsuccessful screen?
exactly my issue
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
This method WORKS!!!! Same situation happened to me. THANK YOU 500x!! you saved my brick!
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
This works 100% thank you so much. Just have patience as it has to be at the right time....WORKS WORKS WORKS!!!!!
Help
Can someone explain the commands and how to do this please thanks in advance
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
epr2175 said:
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
Click to expand...
Click to collapse
What screen are you stuck in? Do you have adb up and running?
Same as before Encryption unsuccessful. I was able to do the trick, got into two and wiped data. Then rebooted to system and it went right back to that screen. I've tried 100 times or so to get back into twrp with no luck. I hear the computer recognize the device when it goes into twrp for 2 seconds after you click reset. Not sure if that means add is up and running or not.
jessiemougeot said:
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
Click to expand...
Click to collapse
Well it booted then got stuck on the lg boot screen again. Adb does not recognize my device, can only boot into Fastboot. Fastboot does see my device, tried lgup, lg bridge, and lg update none see my device, tried relocking bootloader after oem lock bootloader rebooted said my device was corrupted and shut itself off went back into Fastboot unlocked bootloader again and back to the same lg screen help?
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
---------- Post added at 02:06 PM ---------- Previous post was at 01:11 PM ----------
crazyc78 said:
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
Click to expand...
Click to collapse
Now I don't even have the encryption screen it just reboots back to TWRP very frustrating!!
fixed!
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole process step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
This option works!
SyHusky said:
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
jay_h_jacob said:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
Click to expand...
Click to collapse
No problem!! Also I forgot to add I only rooted afterward and didn't try to install a ROM or anything. I would think you risk danger with some ROMs without that decryption thing turned off. So maybe in the short future there will be better fixes.
As title states. I recently traded for this phone with a friend so I could use viper4android. He had already updated it. Is there anything I can do? Thanks internet.
You can still root on 12a. Download the .Kdz file
my_handle said:
You can still root on 12a. Download the .Kdz file
Click to expand...
Click to collapse
Thanks so much. I will try that again. I was just having issue with lg up.
If it's an issue with lgup not seeing the device try using the uppercut program like I did. https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Tzimmerman15243 said:
Thanks so much. I will try that again. I was just having issue with lg up.
Click to expand...
Click to collapse
my_handle said:
If it's an issue with lgup not seeing the device try using the uppercut program like I did. https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Click to expand...
Click to collapse
That worked great! Thanks so much! However, i am now having issues with Root/Twrp/Bootloader. I can make it through to installing twrp, but the device does not continue boot up past the Verizon logo and loading animation. I let it stay there vibrating for about 30 minutes. Haha
Tzimmerman15243 said:
That worked great! Thanks so much! However, i am now having issues with Root/Twrp/Bootloader. I can make it through to installing twrp, but the device does not continue boot up past the Verizon logo and loading animation. I let it stay there vibrating for about 30 minutes. Haha
Click to expand...
Click to collapse
What exactly have you done?
my_handle said:
What exactly have you done?
Click to expand...
Click to collapse
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Tzimmerman15243 said:
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Click to expand...
Click to collapse
If you're stuck where I think
*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
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
my_handle said:
If you're stuck where I think
*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
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Click to expand...
Click to collapse
So i did try the first part. I flashed boot2 and it got me to the Password screen. The second part says to fix that by booting recovery (Twrp) and erasing the things correctly. I cant get into twrp or any sort of recovery. Not by adb (cant boot phone past password screen or verizon screen) or by button holding on power up. (just continues with boot up. I can get into fastboot mode and download mode.
I would try step 2..bat again if you still can't get it try reaching out to @me2151. He's the mad genius that got this and he's pretty good with helping those who are stuck
my_handle said:
I would try step 2..bat again if you still can't get it try reaching out to @me2151. He's the mad genius that got this and he's pretty good with helping those who are stuck
Click to expand...
Click to collapse
Thanks so much! I'm very new to posting. Is there some way I thank you? Like officially? haha
Tzimmerman15243 said:
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Click to expand...
Click to collapse
If you get to the secure start up password and you cannot get any further, you did not decrypt the phone by formatting the data and such.
nahepler90 said:
If you get to the secure start up password and you cannot get any further, you did not decrypt the phone by formatting the data and such.
Click to expand...
Click to collapse
Is decrypting something I need to do before getting into Twrp? I can't get into recovery.
Also, and this might be nothing, but it seemed to work in my case, but when you're in that rebooting step, make sure you're unplugged. Mine did the same, sat there for 20+ minutes vibrating away. I redid the steps but without it plugged in, and it went through. I've also noticed that on rebooting my phone (different ROM now but still), if I'm plugged into my computer, it'll go into vibrating and act quirky during the reboot, whereas if I'm not plugged into the USB, then it restarts normally.
Totally might be all coincidental, but if you haven't tried it that way, worth a shot.
Tzimmerman15243 said:
Is decrypting something I need to do before getting into Twrp? I can't get into recovery.
Click to expand...
Click to collapse
No the decrypting is done in twrp. Did you successfully install twrp through adb/fastboot?
CharlzO_2000 said:
Also, and this might be nothing, but it seemed to work in my case, but when you're in that rebooting step, make sure you're unplugged. Mine did the same, sat there for 20+ minutes vibrating away. I redid the steps but without it plugged in, and it went through. I've also noticed that on rebooting my phone (different ROM now but still), if I'm plugged into my computer, it'll go into vibrating and act quirky during the reboot, whereas if I'm not plugged into the USB, then it restarts normally.
Totally might be all coincidental, but if you haven't tried it that way, worth a shot.
Click to expand...
Click to collapse
Thanks for the reply! I have tried all sorts of booting with both Boot1 and boot2 img. Both unplugged and plugged in to no avail.
nahepler90 said:
No the decrypting is done in twrp. Did you successfully install twrp through adb/fastboot?
Click to expand...
Click to collapse
I think its installed? Haha. It goes through in fastboot as in fastboot flash recovery twrp.....blah blah.img
But, i have not been able to boot to it in any form.
Solved! I messaged @me2151 himself and he straightened me out. It is always the simplest things. I was trying to boot into recovery the incorrect way by way of not only releasing the power button. Thanks for all the friendly internet help. When I posted here, I had no idea there were so many great people out here behind the text. Thanks again!
Tzimmerman15243 said:
Solved! I messaged @me2151 himself and he straightened me out. It is always the simplest things. I was trying to boot into recovery the incorrect way by way of not only releasing the power button. Thanks for all the friendly internet help. When I posted here, I had no idea there were so many great people out here behind the text. Thanks again!
Click to expand...
Click to collapse
Sorry o didnt get back to you sooner. Glad you got it worked out! @me2151 helped me out getting root on my phone as well. Hes a good help
Glad you got it figured out. And I told you he was good about helping
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)
Hi there,
I think I have screwed up my V20.
I have flashed a new rom, met the decryption unsuccessful, format data didn't work.
then I searched a thread, it said lock bootload and then unlock it could help.
then, brick.
I have not entered the new rom and tick on the oem unlock button. and now the phone didn't pass the security check and shutdown automatically.
any methods could help? 9008?
thanks a lot.
magicsword123 said:
Hi there,
I think I have screwed up my V20.
I have flashed a new rom, met the decryption unsuccessful, format data didn't work.
then I searched a thread, it said lock bootload and then unlock it could help.
then, brick.
I have not entered the new rom and tick on the oem unlock button. and now the phone didn't pass the security check and shutdown automatically.
any methods could help? 9008?
thanks a lot.
Click to expand...
Click to collapse
yeah... locking the bootloader has zero to do with encryption/decryption..
If it won't let you back into fastboot mode (volume down+usb connect) and reunlock it.
You might have Download mode/LG UP.... unless you put/left twrp on that. (volume up+usb connect from powered off).
If you don't have either of those and you have an H918 you're screwed.
If you don't have either of those and you have another variant (as long as its not an ARB 1 ls997) it may be possible to reflash using the leaked firehose (which is arb 0 and signed for the other variants besides H918) but I have no experience with
Phoenix591 said:
yeah... locking the bootloader has zero to do with encryption/decryption..
If it won't let you back into fastboot mode (volume down+usb connect) and reunlock it.
You might have Download mode/LG UP.... unless you put/left twrp on that. (volume up+usb connect from powered off).
If you don't have either of those and you have an H918 you're screwed.
If you don't have either of those and you have another variant (as long as its not an ARB 1 ls997) it may be possible to reflash using the leaked firehose (which is arb 0 and signed for the other variants besides H918) but I have no experience with
Click to expand...
Click to collapse
thanks for the reply mate.
i am afraid I have met the worst situation.
1. able to enter fastboot, but not allow wo unlock bootload. (cos I flashed the new rom and didn't even enter it, and tick the oem unlock button )
2. I have used LAF to change the download mode to be TWRP, so no hope here. the tricky thing is, once I lock the bootload, it could not even enter download mode or TWRP, showed not pass the safety check, will not boot. and then an endless boot loop.
3. my V20 is H918.
4. MY V20 is totally screwed........cry face.