Database Users

my friend (soft?)bricked his nexus 4...help?

So he was following some random youtube video that was years old so it probably was outdated...
the phone state is currently unlocked, not unrooted yet..but with clockwork mod .
it responds to fastboot commands using the nexus toolkit by wugfresh but i can't get adb to work? all the guides i see say you have to have the phone booted normally before installing it and we can't do that
any help is appreciated

Your situation is a bit unclear, Is the phone boot looping? What you can do is flash a factory image while the phone is on the bootloader mode using Ncry toolkit or something similar. This way doesn't require the phone to be on or have any flash files already on the phone.

hey thanks for relying so fast, yes it is boot looping, ill try what you said now and update status, thanks again
edit: where would i get the factory image? does that toolkit download it for you?

colonelcack said:
hey thanks for relying so fast, yes it is boot looping, ill try what you said now and update status, thanks again
edit: where would i get the factory image? does that toolkit download it for you?
Click to expand...
Click to collapse
you didn't go into the stock recovery after unlocking bootloader
here is the factory images page - https://developers.google.com/android/nexus/images
you could probably just flash the recovery.img in the image-*.zip file to recovery, then go into recovery, wait for it to do it's thing then flash clockworkmod, philz or TWRP with the toolkit and do root etc.
you can also just flash the factory image, then do the stuff with the toolkit (easier)
sorry if I've confused you o.o

Easiest way to do this is to use Ncry (http://goo.gl/l0iuEn):
1. Put phone in bootloader an connect phone to pc with Ncry ON.
2. Click on the one click menu.
3. click SR mode.
The programme will automatically download the files and do the flashing, when finished the phone will auto boot.

MameTozhio said:
you didn't go into the stock recovery after unlocking bootloader
here is the factory images page - https://developers.google.com/android/nexus/images
you could probably just flash the recovery.img in the image-*.zip file to recovery, then go into recovery, wait for it to do it's thing then flash clockworkmod, philz or TWRP with the toolkit and do root etc.
you can also just flash the factory image, then do the stuff with the toolkit (easier)
sorry if I've confused you o.o
Click to expand...
Click to collapse
he needs to get it to be recognized as an adb device right? where would i get windows 8 x64 adb drivers?

colonelcack said:
he needs to get it to be recognized as an adb device right? where would i get windows 8 x64 adb drivers?
Click to expand...
Click to collapse
I Use: Wug's Nexus Root Toolkit v1.7.9
And Do the Universal Drivers, and its worked for me.

ok great thanks man it worked, really appreciate your time. only thing is that it wont show up on windws 8 pc but it does show up on windows 7 pc, you really helped my buddy out of a jam thanks again

Need help recovering my nexus 6p!

Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.

When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?

matteosaeed said:
When you go into your recovery and connect the phone to the computer, does it read on the computer MTP?
When you go into twrp, do you have something unmounted by default?
I don't know about the fastboot, but this is weird, Have you tried to access the bootloader from twrp?
Click to expand...
Click to collapse
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.

Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Asmodic said:
ok, so when in recovery and i connect the phone, the computer doesnt read.
when im in twrp it asks me for a password but i hit next and choose the option to enable changes to the file system. no drives seem to be unmounted but i dont see my downloads folder or any of the folders i used to see before.
and i am able to access the bootloader but not get into fastboot mode to use adb, also when in bootloader mode, my phone doesnt get recognized with my computer. And yes full sdk is installed with latest updated drivers.
thanks for your response.
Click to expand...
Click to collapse
Also check this out, it might help

matteosaeed said:
Well, this is good, if twrp is asking you for a password, it means that something is encrypted. Also, I had an issue with TWRP 3.0 before I updated to the latest version.
Check out this thread on reddit.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Also check this out, it might help
Click to expand...
Click to collapse
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!

Why don't you just go to Heisenberg's guide in the general section and flash the latest stock images from Google via Fastboot and start from there? This way you'll at least have a working phone to boot into. From there you can reflash custom recovery and even systemless root. This is what I have always done when the phone wouldn't boot, or I had a backup handy and flashed that. When in trouble just flash latest images.

Asmodic said:
Hi,
So I seemed to have messed up my nexus 6p. I was flashing a custom rom and it would boot so i decided to flash the vendor.img first and then re-flashed the rom as it stated in the instructions for the rom. Now i am stuck as the nexus wont boot up still. I am still able to boot into recovery - currently at TWRP 3.0.0.
I was trying to use fastboot to recover the nexus to stock but it seems like i am not able to boot into fastboot mode. i see the green android screen with the writing at the bottom which states that the bootloader is unlocked but i never get the Fastboot mode written on it on the top no matter how many times i reboot the device. I even tried toolkits but nothing seemed to work.
Also, in TWRP i am not able to see any files or my backups. its like everything just disappeared from my device. I am not able to connect the device to the computer when im in twrp either, so i cant put older roms that worked.
Any suggestions/help is much appreciated!
thanks
LA.
Click to expand...
Click to collapse
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Sounds like you need to update you drivers if your computer is not recognizing it

Asmodic said:
Ok so i looked at the reddit thread and its saying the phone is encrypted which is why its asking for a password but i dont remember encrypting the phone. i always used my fingerprint to unlock the device. any thoughts as to what the password could be? :S
thanks for all your help!
Click to expand...
Click to collapse
Any Luck?

it's because you don't have the NEWEST version of TWRP.
Even the simplest of searches would've come up with this answer.

If your phone stuck at bootloop just go to recovery and wipe cache it will work.

pankajste said:
If your phone stuck at bootloop just go to recovery and wipe cache it will work.
Click to expand...
Click to collapse
No it won't, not in this situation.

Heisenberg said:
Bootloader mode is fastboot mode, it never actually says fastboot mode on the screen, so if you're in the bootloader screen you're in fastboot mode and fastboot commands will work. Follow the instructions in my guide to return to stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!

Asmodic said:
Thanks so much it worked. I used the guide and was able to adb flash back to stock.
Cheers!!
Click to expand...
Click to collapse
So this should be marked "Solved?"

It should be marked as "when in trouble revert to Heisenberg's guide."

Bootlooping Nexus

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.

A little help please...

I have the US version of the ZTE Axon 7 running the B29 build.
I recently unlocked the bootloader successfully, When I flashed the TWRP recovery via fastboot soon after, it worked perfectly. Phone booted properly and worked normally. When I tried to install the TWRP app in the OS, I was told to download the latest TWRP version from the website and flash it (even though I had the latest version already flashed from fastboot). I did that. Now I have no recovery menu at all. I have access to the bootloader menu, and I can boot into the phone. When I try to boot into recovery, all I get is a black screen. I tried to reflash the TWRP recovery img from fastboot like I did originally with no success this time. Fastboot recognizes the phone when I type devices, but when I type the fastboot command to flash recovery twrp.img, it says it can't load the file. I then downloaded the ZTE stock recovery img and tried to flash that with the same result. I assume the recovery partition is locked somehow now? What can I do to recover the recovery? Am I stupidly forgetting something trivial.

hello, this happened to me once on a Nexus 7, I did a clear cache/wipe and restore I think, I got it to work.
Not sure if this will solve your issue but you can give it a shot...
good luck

I would never flash a recovery from an app unless there was no other option. Use tennear/tenfar tool to flash twrp.

lafester said:
I would never flash a recovery from an app unless there was no other option. Use tennear/tenfar tool to flash twrp.
Click to expand...
Click to collapse
yeah. live and learn. too late to help at this point. I'll try the tool you suggested

Bucci83 said:
hello, this happened to me once on a Nexus 7, I did a clear cache/wipe and restore I think, I got it to work.
Not sure if this will solve your issue but you can give it a shot...
good luck
Click to expand...
Click to collapse
Thanks for your suggestion. I cant wipe/flash/ recover/or even reset to factory because I have no recovery menu at all. Unless there's a way to do that outside of the recovery boot menu.
At least it's not bricked.

[email protected] said:
Thanks for your suggestion. I cant wipe/flash/ recover/or even reset to factory because I have no recovery menu at all. Unless there's a way to do that outside of the recovery boot menu.
At least it's not bricked.
Click to expand...
Click to collapse
I think he means go to fadtboot and do fastboot clear cache or something like that, Google fastboot cache clear command

sudden bootloop (can't get into recovery mode) n I didnt update to android 7,

so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help

jay0514 said:
so there I was in my car, my phone plugged in via aux cable and playing some music
suddenly I notice the music stops and my phone goes into a reboot,
I was using a pure nexus rom on marshmallow ( the latest marshmallow one i believe) and had xposed, and sometimes my phone would randomly reboot,
it was annoying but I could live with it
so i thought it was having another one of it's moment
but now it doesn't actually reboot,
my phone is stuck in a reboot loop and I can't even get into recovery mode, (I had TWRP installed and could boot into it numerous times before this)
anyone have any ideas?
I've installed twrp via fastboot
but I can't use the adb command to boot into recovery since device is not found,
when i try
adb devices
the list is empty,
and yes I've installed the latest google drivers via android studio
I've installed hi-suite
someome please help
Click to expand...
Click to collapse
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21

5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
ohhh i see
yeh I dones't let me get to the recovery mode in the options from bootloader
and what are the commands to format cache and data in fastboot??

5.1 said:
Hi... You can't use adb commands while in bootloader... Only fastboot commands. Use the volume rocker till you see recovery mode displayed and press power button. If it still bootloop, try formatting cache and data with fastboot in bootloader and reboot in recovery again. If it still bootloop. Finally try fastboot flash a stock Google image. If none of these steps work, your phone is probably dead and you'll have to try to RMA your N6P.
Check this thread for further infos: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page21
Click to expand...
Click to collapse
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'

jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...

5.1 said:
First try:
fastboot format cache
fastboot format userdata
If the above doesn't solve your issue it's probably dead...
Check this thread for factory image flashing tutorial: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page552
Good luck...
Click to expand...
Click to collapse
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S

jay0514 said:
followed the guide to install stock rom,
still in reboot loop
how can a fine phone just die suddenly? :S
Click to expand...
Click to collapse
Sorry... Known issue with the N6P... Have you checked the tread I linked you in my first answer?
Good luck...

jay0514 said:
and im trying to flash a stock google image
im following steps from the official android page
but how do I execute a .sh file?
the instruction is to go to the folder with files and execute 'flash-all.sh'
Click to expand...
Click to collapse
Fastboot flash-all.sh is for Mac computers so presumably you have a Mac. Flash-all.bat is for windows. You need to unzip the Google image and move everything into the same folder where you have the fastboot program. Just open a command prompt window inside that folder and type the command. That's how I do it in Windows. Presumably the process is similar with a Mac. You will still have a zipped archive after you unzip the Google image but you want to leave that one as is. So far flashing flash-all.bat has gotten me out of every boot loop I've gotten into on my 6P but my phone never spontaneously bootlooped. I was always doing something (updating a rom, trying to restore a nandroid backup) that resulted in a bootloop. The fact that your phone boot looped without warning is probably a bad sign. If you still have warranty I would try to flash stock and see if you can RMA phone. If that isn't possible you might want to try staying on stock or using a different rom and seeing if the random reboots still occur. Good luck.

Well that really sucks. Sorry for your loss but it is a long running phone failure problem. I'm on my second 6P because this. Even worse to me is the fact your were running almost the exact same setup I am now. I refrained from running 7.x.x to try and minimize my chances of another BLOD so now w4on knows what to do. Lol
Sent from my Nexus 6P using XDA-Developers Legacy app