So, one of my family members was mucking around on their tablet. I was sure that I has locked down the appropriate areas, but as of right now, I think I'm looking at a hard-brick. I'm not sure what kind of fastboot capabilities I have, turning it off, and on again boots to what looks like fastboot, but I have a Google splash screen. Using the vol up/down/pwr button does boot into fastboot, but I'm not sure what I have at my disposal for flashing. Any suggestions? I've just never seen anything like this before.
If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5
Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.
Pirateghost said:
If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5
Click to expand...
Click to collapse
bsquare said:
Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.
Click to expand...
Click to collapse
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!
Verfassergeist said:
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!
Click to expand...
Click to collapse
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5
Pirateghost said:
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5
Click to expand...
Click to collapse
I....*facepalm*
Related
I updated TWRP today to 2.3.0.0 from within GooManager then rebooted into recovery and fixed my permission. It was done unusually fast and when I rebooted, it would get stuck on the booting screen. When I tried to boot into recovery by pressing power and both volume buttons, it would get stuck on the google logo.
Please advise.
Any other way I can fix this or somehow restore from a backup?
A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium
Gigabitex2 said:
A lot of users are having issues with cwm and twrp not booting with new boot loader. You can revert back to old version or some have had success by deleting "recovery-from-boot." file. You can look at http://forum.xda-developers.com/showthread.php?t=1779092 I'm going to wait patiently for a twrp update that should resolve the issue.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you very much!
I'm sorry but I'm not too much of an expert on Android. AFAIK Recovery mode is the only way I know to do some low system stuff. If I can't boot into recovery, how else can I do anything to fix this?
How can I revert back to old version?
I know you linked the other thread but there are 33 pages I was hoping you would have a short answer hehe thanks.
Is it constantly rebooting at the google screen or just stuck?
goofball2k said:
Is it constantly rebooting at the google screen or just stuck?
Click to expand...
Click to collapse
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
I see that you posted over on the twrp thread, hopefully those guys can help you. I am assuming that you have updated to 4.1.2? If you're really stuck maybe try a tool kit like wugs or n7 toolkit? Sorry but SDK isn't one of my strong points either
Sent from my Nexus 7 using xda premium
woshiweili said:
If I try to boot into system, it's stuck on boot animation.
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2
comminus said:
You can reflash recovery from fastboot. If you've updated to 4.1.2 you might be experiencing same issue as many of us - being unable to boot to recovery. If that is the case, flash bootloader 3.34 from the JRO03D factory image as well.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol
woshiweili said:
From what I understand, in order to reflash recovery from fastboot would require me to get the file to the device. However, right now I can't seem to get access at all as it never boots up whether into system or recovery. Are there any other ways to get files onto there?
---
OK this is weird. I tried rebooting into recovery again and it worked! I then rebooted into system and that worked too! This is so strange because I didn't do anything different. I guess it just took 20+ tries... I am not rebooting in a while... lol
Click to expand...
Click to collapse
Hey, glad to hear you're in. In an earlier post you described
woshiweili said:
If I try to boot into recovery manually (power + volume buttons then select recovery) it would get stuck on Google. It doesn't loop.
Click to expand...
Click to collapse
which sounds like you were able to get to fastboot mode (power + vol buttons) - your N7 should look like this. From there you can issue fastboot commands to the device to flash recovery. kerne, and bootloader to name a few.
Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.
woshiweili said:
Actually I spoke too soon.
I can boot into recovery TWRP 2.3 with USB plugged in, but still can't boot into system.
Is it possible for me to downgrade to TWRP 2.2 from within TWRP? I kind of doubt it but am pretty desperate at the moment lol.
Yes, I can get into fastboot, but I'm not sure how to do anything besides pressing volume up or down to start, recovery, fastboot or shut down.
Click to expand...
Click to collapse
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.
comminus said:
If you can get in to fastboot you are in good shape. :good:
You'll need the fastboot program (and the driver if on Windows) on your computer in order to issue commands. This guide can direct you on how to get that set up.
Click to expand...
Click to collapse
Thanks for all your help comminus!
Fortunately I was able to wipe everything while I was in recovery and restore from my most recent backup and now it's working fine. At the very least it's allowing me to boot into system
OK I'm really not rebooting for a while lol
I installed twrp a few weeks ago through GooManager and made a backup. When the 4.1.2 update came out, I downloaded it manually with the intent on flashing it via cu custom recovery, but low and behold twrp wasn't working at all. Even with my device plugged into my Win 7 pc... nothing but the exclamation point droid.
I was able to install an updated version of twrp and get everything sorted out, but now I don't have a lot of faith in it, and am booting into recovery at least once a day to make sure it's still working. I never had any problems with cwm.
Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium
I'm using twrp version 2.3.0.0, and have no plans on updating it because it's stable and working great now
Gigabitex2 said:
Twrp has been updated if you're still having issues.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Updated to 2.3.1.0 but still having booting issues
Yeeeeh Unlocked my nexus10, then i got a bootloop i tried to fix it :> now i cant boot to recovery or anything else, any ideas? ^^ the only i c is fastboot mode
I was in the same situation, go for the factory image of Google and flash it.
Normally this should solve your problems!
DJavireX said:
Yeeeeh Unlocked my nexus10, then i got a bootloop i tried to fix it :> now i cant boot to recovery or anything else, any ideas? ^^ the only i c is fastboot mode
Click to expand...
Click to collapse
Give this tool http://forum.xda-developers.com/showthread.php?t=2015467 a try. It should help restore your N10 back to stock.
DJavireX said:
Yeeeeh Unlocked my nexus10, then i got a bootloop i tried to fix it :> now i cant boot to recovery or anything else, any ideas? ^^ the only i c is fastboot mode
Click to expand...
Click to collapse
Ahaha, sorry, not laughing at you, but this is a pretty familiar situation.
Wug's toolkit is a great tool, but if you ever intend to work more with ROMs and rooting, I'd highly recommend you take the opportunity to learn to use fastboot (which you can download if you search around the forums). You can download the factory image from Google, and once you open that folder it's a simple matter of running:
fastboot flash system /path/to/system.img
fastboot flash recovery /path/to/recovery.img
and possibly fastboot flash boot /path/to/boot.img.
Be grateful you still have fastboot running though-- without that, what a disaster.
Rirere said:
Ahaha, sorry, not laughing at you, but this is a pretty familiar situation.
Wug's toolkit is a great tool, but if you ever intend to work more with ROMs and rooting, I'd highly recommend you take the opportunity to learn to use fastboot (which you can download if you search around the forums). You can download the factory image from Google, and once you open that folder it's a simple matter of running:
fastboot flash system /path/to/system.img
fastboot flash recovery /path/to/recovery.img
and possibly fastboot flash boot /path/to/boot.img.
Be grateful you still have fastboot running though-- without that, what a disaster.
Click to expand...
Click to collapse
Thx i tried fastboot also i fixed it... used another workstation... then it worked in about 10 mins... craaaap!
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
RohMish said:
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
Click to expand...
Click to collapse
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
flash installs the recovery but nothing works. i have to do a wipe and install the stock recovery to boot it. i wrote it on top
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
RohMish said:
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
Click to expand...
Click to collapse
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
RohMish said:
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
Click to expand...
Click to collapse
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
tried an older version of cwm, touch, everything. but all are having same issues
RohMish said:
tried an older version of cwm, touch, everything. but all are having same issues
Click to expand...
Click to collapse
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
UPDATE: Tried twrp via fastboot boot command. nothing. just a blank screen after the reboot from bootloader (and after google boot screen) for a few seconds, andd then shuts down.
RohMish said:
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
Click to expand...
Click to collapse
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
spaceman860 said:
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
Click to expand...
Click to collapse
not working. says 0 is a not a command. this is as | works as a batch separator in windows
Update: as i remembered modifier <"> will prevent | from kicking into next line, i tried that, and it works!
fastboot -c "lge.kcal=0|0|0|x" boot recoverycwm.img. but still no action. tried a backup, it starts to backup but files are corrupted. and nothing else work.
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
spaceman860 said:
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
Click to expand...
Click to collapse
i loads up but is kind of broken.
any way i can copy the files to my pc to do some analysis. currently the folder which used to save the files has nothing. adb pull /mnt/shell/emulated/clockworkmod/backup/ /android/adbbackupfiles/nexus4 is yielding nothing.
OK. so now i tried using the touch version, and this time there are some files(Still copying). but those are very different than what it was on my older phones and my initial backup. Sorry, I had got away with this due to studies. now the files are .a and.b and the orignal file which is 0KB
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
GuyWithBrokenPhone said:
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
Click to expand...
Click to collapse
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
GuyWithBrokenPhone said:
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
Click to expand...
Click to collapse
It definitely shouldn't have taken that long. Can you boot into the recovery?
Sent from my Nexus 7 (2013)
Just put your phone in fastboot mode and flash factory image.
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
That's normal for stock recovery, you won't be able to sort your phone from there, stay in fastboot mode. You can use a toolkit to flash back to stock from there if you need it more noob friendly. Otherwise you can use the flash-all.bat script in the factory images.
GuyWithBrokenPhone said:
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
Click to expand...
Click to collapse
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
audit13 said:
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
Click to expand...
Click to collapse
Oh god thank you.
Okay. I'm trying to reinstall Paranoid Android now. I did the sideboot via ADB.
I couldn't seem to get the stock version of android on it though. I made sure to open the tar file and tried to move the .zip "image-occam-jdq39.zip" onto the phone, but it wouldn't accept it. So I'm trying Paranoid android again.
Edit: I got it booted. But now wifi won't work. Neither the speakers.
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
DrFredPhD said:
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
Click to expand...
Click to collapse
Doing so now. If I had known about this tool before, I probably would have been done with this a lot sooner.
Currently flashing stock and unrooting.
The toolkit is most certainly the way to go. No mess, perfect every time for me.
Sent from my Nexus 4 using Tapatalk
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
avansledright said:
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
Click to expand...
Click to collapse
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Fe Mike said:
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Click to expand...
Click to collapse
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
avansledright said:
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
Click to expand...
Click to collapse
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Fe Mike said:
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Click to expand...
Click to collapse
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
avansledright said:
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
Click to expand...
Click to collapse
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Fe Mike said:
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
,
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Do you get the error on all that you try to flash? Maybe just try the recovery img only to see if you can at least get that. If that works you should be able to sideload ota through recovery. With having a locked bootloader you might be at a loss. But on the flip side, having everything locked and not rooted you should be ok for warranty replacement.
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Ahh, missed that in your first post. I'm not sure how you can get recovery going if it's bootlooping when you access it.
Sent from my Nexus 5X using Tapatalk
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Fe Mike said:
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Click to expand...
Click to collapse
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
avansledright said:
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
Click to expand...
Click to collapse
Good to hear about replacement! There are a few people in these forums that have a brick and can't get out of it. I thought you couldn't Hard brick these phones unless that was your goal. And most of these users who have bricks don't even know what causes it. Just a random reboot then loops. Kinda scary.