Related
Alright like a idiot I downloaded a international rom and didn't pay attention...flashed in TWRP and went to reboot so it obviously doesn't work. Tried to use the Flashtool to revert back to the stock Verizon software and it throws the error of the Device Model is different. IMEI is right, BIN, DLL, SWV, SWOV all show the VS980 since I'm trying to flash that.
So have I killed it completely or is there a way to recover? Sure hope there is
I can get into the download mode still
Also appears that it boots into fastboot and can send fastboot commands via the command prompt
Wow this dropped quick...just putting this to the top so I can hopefully get it up and running quicker.
Please check the same thread about LG repair cost. It looks like you need to repair it. you have mismatch in model name in build.prop, so there is no solution as for now. http://forum.xda-developers.com/showthread.php?t=2506208
Ya I saw that after this morning...was hoping it wouldn't come to that. Mine says rooted on the download screen so hopefully that doesn't cause a issue when I send it in.
have you tried pushing a .img using fastboot, as you seem to be able to get to it?
aliaksei said:
have you tried pushing a .img using fastboot, as you seem to be able to get to it?
Click to expand...
Click to collapse
Nope as I'm not exactly sure which one I didn't want to attempt anything and break it further
If you could point me to the right one I would appreciate it
collins521 said:
Nope as I'm not exactly sure which one I didn't want to attempt anything and break it further
If you could point me to the right one I would appreciate it
Click to expand...
Click to collapse
Hey man are you able to access recovery at all by holding down Vol down+Power, releasing it when the LG splash screen appears for a sec, and then immediately pressing it again? I saw someone a day or two ago was able to put a ROM on a flash drive and install it from there in TWRP.
Mine actually seems to be booting into fastboot when I hold down the power button and it reboots. I can't get it to turn off completely, I can get into download mode if I hold down volume up and power if it's plugged into the computer. If I hold down the power button it will reboot and seems to be in some sort of fastboot when it tries to power on
collins521 said:
Nope as I'm not exactly sure which one I didn't want to attempt anything and break it further
If you could point me to the right one I would appreciate it
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1752270
aliaksei said:
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
Makes sense and should be easy enough except that thread makes it out that the boot.img really wouldn't change the device model. Unless it contains it in the img file
Which .img file would I be pushing? The boot.img?
I guess it would be more like which one? Would I be able to just used the one from say CleanRom?
Wohoo! Finally got it up and going...thought for sure it was toast.
I flashed the boot.img through fastboot and then was getting "secure boot unsuccessful" on the screen when it tried to boot. Kept trying to get it into the recovery and it finally did so when it went to the splash screen about pressing the power it put me into TWRP.
I tried to restore the backup that I had stored and it started to but then turned off, I'm not sure if it was because the battery was so low or if it was just the jacked up file structure but it wouldn't get any father than the LG splash screen. The LED would flash green then blue and it would just sit there.
That was when I thought for sure it was toast, let it sit and charge for awhile and still couldn't get back into the recovery but was able to get into download mode. Flashed the stock software via LG Tools and it finally booted.
Not sure if anyone else will run into this issue but now it's documented lol
help a bro
collins521 said:
Wohoo! Finally got it up and going...thought for sure it was toast.
I flashed the boot.img through fastboot and then was getting "secure boot unsuccessful" on the screen when it tried to boot. Kept trying to get it into the recovery and it finally did so when it went to the splash screen about pressing the power it put me into TWRP.
I tried to restore the backup that I had stored and it started to but then turned off, I'm not sure if it was because the battery was so low or if it was just the jacked up file structure but it wouldn't get any father than the LG splash screen. The LED would flash green then blue and it would just sit there.
That was when I thought for sure it was toast, let it sit and charge for awhile and still couldn't get back into the recovery but was able to get into download mode. Flashed the stock software via LG Tools and it finally booted.
Not sure if anyone else will run into this issue but now it's documented lol
Click to expand...
Click to collapse
i did the same thing as you i loaded a d802 rom on my vs980 can you tell me how to load the boot .img so i can do what you did i didnt buy a warranty cause i figured i didnt need it so i have no alternative way of fixing it
Had to push the boot.img through adb
collins521 said:
Had to push the boot.img through adb
Click to expand...
Click to collapse
What's the command input for the push
All I know is its the along the line of push/c:/(boot.img location)
It's more like "fastboot flash boot boot.img" you can't push it via adb, unless you're already in TWRP.
NRGZ28 said:
It's more like "fastboot flash boot boot.img" you can't push it via adb, unless you're already in TWRP.
Click to expand...
Click to collapse
I have twrp installed but I can't boot to it I get stuck on the [800] fastboot mode started screen can I do it from download mode
Was having issues with my Nexus 7(2013) this morning, rebooted the device and now it gets stuck at the "Google" loading screen.
I can get into the Fastboot loader. I was able to unlock the bootloader.. I have LOCK STATE - unlocked and the unlocked lock showing up on the "Google" boot screen.
I am UNABLE to get into Recovery mode.. either by selecting "Recovery mode" in Fastboot or holding the power and vol up buttons. It just sits on the "Google" boot screen.
I have downloaded and installed the SkipSoft Android Toolkit(mskip).. very nice toolkit BTW. But no matter what I do I'm unable to start the tablet up normally or get into a Recovery mode of any kind.
I have tried to flash TWRP. I have tried to flash the stock ROM. Nothing, still sits at the Google boot screen. Since flashing the stock ROM its been 30 min and still just says "Google".
I'm open to any ideas or anything that you can think of.
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Snuzzo said:
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Click to expand...
Click to collapse
No.. I do not get into recovery of any kind. Stock or TWRP after loading it.. just sits at the Google screen.
Quick question; what were your partition setups like? F2fs? Ext4?
Snuzzo said:
Quick question; what were your partition setups like? F2fs? Ext4?
Click to expand...
Click to collapse
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
FDokinawa said:
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
Click to expand...
Click to collapse
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Snuzzo said:
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Click to expand...
Click to collapse
Thanks for the help.. will give it a shot.
FDokinawa said:
Thanks for the help.. will give it a shot.
Click to expand...
Click to collapse
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Snuzzo said:
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Click to expand...
Click to collapse
Dont think I can use the warranty.. bought it used(1 hour old) from a friend for $100.. he got it and then decided he didnt like the aspect ratio. His loss, my gain. Until now.. lol
I'll keep hacking at it.. thanks again.
Anytime! You're welcome!
So the original issue I was having was that the screen was not responding to touches. Was unable to slide the unlock button on the screen.
I was able to "Boot to Custom/Stock Recovery without Permanently Flashing it" via SkipSoft Toolkit.. and had TWRP load up. But like before it was not responding to touches.
Starting to think this thing is totally borked.. =/
I'm able to get into TWRP now.. but sits on boot animation screen now. one step forward. Going to try and reload the stock ROM again and see if that helps.
That seemed to work.. at the Welcome screen.
So if anyone else runs into something like this..
Issues:
Flakey touch screen
Stuck on Google bootup screen
Eventually stuck boot loop animation
Get SkipSoft Android Toolkit, donate a couple bucks and keep flashing anything and everything you can. Sorry I can't give you a specific order that works. I would say try the 'ALLINONE'(#8) option first and then download and flash the stock ROM. I did several things in the toolkit a few times over and over. Hopefully I'm good now, if not I will update.
Have you tried reflashing recovery via fastboot?
Exact thing happend to my n4.
Sent from my N⁴ using Android Lollipop by @Sykopompus running Unleased kernel by @DeFcOni
================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
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,
My wife's 6P is stuck in a bootloop. Here's what I've tried so far:
adb devices -> no result
fastboot devices -> device info is displayed
Any other fastboot command -> "FAILED (command write failed(No error))"
I unlocked her bootloader when we got the phone, but I can't flash anything. I just keep getting that error.
Any ideas? Thanks in advance for your help.
Did you update ADB and fastboot ?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
coremania said:
Did you update ADB and fastboot ?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Click to expand...
Click to collapse
Yep, I'm able to see my 6P and N7 2012 via ADB, just my wife's 6P that I can't seem to get to work.
Not sure what happened, but I am now able to execute fastboot commands without getting that error. So now I'm waiting for the battery to die down enough to be able to boot recovery per this post. Hopefully this will fix it.
FlyOnTheWall43 said:
Yep, I'm able to see my 6P and N7 2012 via ADB, just my wife's 6P that I can't seem to get to work.
Click to expand...
Click to collapse
You're not able to boot to stock recovery ?
---------- Post added at 14:40 ---------- Previous post was at 14:21 ----------
What happens if you put a working twrp.img into your fastboot folder and try to boot it without flashing.
fastboot boot twrp.img
or
fastboot boot recovery twrp.img
coremania said:
You're not able to boot to stock recovery ?
---------- Post added at 14:40 ---------- Previous post was at 14:21 ----------
What happens if you put a working twrp.img into your fastboot folder and try to boot it without flashing.
fastboot boot twrp.img
or
fastboot boot recovery twrp.img
Click to expand...
Click to collapse
correct, I cannot boot to stock recovery, flash a custom recovery, or boot to a custom recovery directly (without flashing).
FlyOnTheWall43 said:
correct, I cannot boot to stock recovery, flash a custom recovery, or boot to a custom recovery directly (without flashing).
Click to expand...
Click to collapse
Just read the thread you linked, did you try the freezer, like the guy from the last post ???
coremania said:
Just read the thread you linked, did you try the freezer, like the guy from the last post ???
Click to expand...
Click to collapse
no, I just found that thread and I'm at work... going to try the freezer trick tonight.
coremania said:
Just read the thread you linked, did you try the freezer, like the guy from the last post ???
Click to expand...
Click to collapse
FlyOnTheWall43 said:
no, I just found that thread and I'm at work... going to try the freezer trick tonight.
Click to expand...
Click to collapse
Shoot, didn't help. Still continued to bootloop.
FlyOnTheWall43 said:
Shoot, didn't help. Still continued to bootloop.
Click to expand...
Click to collapse
Yes, actually the thing with the freezer i never heard that before, but if i remember right someone uses heat to make the phone bootable for a short time. May you carefully try this
with a hairdryer ??? And then try the 4 core modified boot.img
coremania said:
Yes, actually the thing with the freezer i never heard that before, but if i remember right someone uses heat to make the phone bootable for a short time. May you carefully try this
with a hairdryer ??? And then try the 4 core modified boot.img
Click to expand...
Click to collapse
ok, I can give this a try today after work and report back... thanks
The freezer trick did not work. But what helped me was to let the phones battery run out then plug it into the charger and let it boot loop for about 20 mins or so. The phone should boot at that point. I'm thinking the phone has to at least have a minimal charge to boot. Once the phone boots take it off the charger and make sure that "usb debugging" is on as well as allow "oem unlock" option. Once those settings are set go back to fast boot and attempt to flash the four core fix. It really works ????. If you leave the charger on it will go back to boot looping after it reaches 10 percent or so. Hope this helps.
pacoe said:
The freezer trick did not work. But what helped me was to let the phones battery run out then plug it into the charger and let it boot loop for about 20 mins or so. The phone should boot at that point. I'm thinking the phone has to at least have a minimal charge to boot. Once the phone boots take it off the charger and make sure that "usb debugging" is on as well as allow "oem unlock" option. Once those settings are set go back to fast boot and attempt to flash the four core fix. It really works . If you leave the charger on it will go back to boot looping after it reaches 10 percent or so. Hope this helps.
Click to expand...
Click to collapse
My bootloader is already unlocked, but I can't flash or boot the four core fix.
I know this question sounds redundant, but does your phone show your bootloader to be unlocked? Seems quite strange that it would not run the fastboot commands. What is the command that you are typing in to install the four core fix.
pacoe said:
I know this question sounds redundant, but does your phone show your bootloader to be unlocked? Seems quite strange that it would not run the fastboot commands. What is the command that you are typing in to install the four core fix.
Click to expand...
Click to collapse
no worries, I appreciate the attention/suggestions this thread is getting.... yeah, the bootloader is showing as unlocked. Also as of post #4, I am able to execute all fastboot commands now... I'm not 100% sure why it started working.
Always glad to help. Have you been able to fix the phone?
Sorry to disturb you, after I unlocked my device, I tried to flash both normal fix and 4 -core fix img > flash TWRP recovery, but I still cannot get into recovery mode, is my procedure wrong?
1) Flash 4 core fix boot img.
2) Flash TWRP recovery.
3) Boot to recovery.
4) Bootloop.
Thank you.
pacoe said:
Always glad to help. Have you been able to fix the phone?
Click to expand...
Click to collapse
No, but our Pixel 2's just showed up, so this isn't as urgent for me as it originally was. I'm hoping I can still get her old Nexus 6P and use it as our home phone with Google Voice. But, first I have to get this fix to work...
I'm able to flash the modified boot images without any errors, but I still can't get it to boot... I'm thinking it might be because my wife had to keep her phone 3-6 months behind the most current factory image (due to a poorly supported app she HAS to have for work) so I'm thinking the boot images on this thread won't work for her phone because he's on an older factory image. Am I correct in thinking this might be the problem?
I've requested that the OP of that thread either created modified boot images for the older versions of the factory images or explain how he made them so I can try to make them myself. Hopefully he's able to help me out.