I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Wallstud44 said:
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Click to expand...
Click to collapse
What happened to this? I have the same damn issue. Although I managed to get fastboot and adb functionality with great difficulty. But the device doesn't seem to be able to boot into anything. I've tried every single thing software by the book, and by the forums too. I suspect it might be hardware.
Any luck?
Related
Hello,
I just got my Hero this weekend and I was interested in partitioning the SD Card. I have been following a guide and when I boot into recovery(Screen that shows phone with triangle and exclamation point) the computer does not seem to see the Hero anymore.
When I plug the phone in while it is running Android the computer picks it up fine in Device manager. Once I type adb shell reboot recovery it boots into the screen the computer no longer picks it up. I have tried unplugging and replugging the USB cable while in the recovery screen but still get nothing. If I type adb devices before I run the recovery command I am able to get the serial number, once it boots into the recovery screen it no longer shows me the serial number when I type in adb devices. But this is due to it no longer being picked up once in the recovery screen.
I'm not really sure what I am doing wrong here. Can anyone help me get this issue sorted out?
I have tried it on Windows 7 and read that a lot of people had issues with the syncing so I just finished attempting it on an Windows XP machine and still get the same issue.
One more thing, when in the recovery screen the phone does not respond to the power button anymore. It seems almost like it locks up or something. The only way I can get back out of the screen is by taking the battery out and putting it back in. Is this normal?
Any help would be really appreciated!
Thank you,
Mizex
You need to root the phone and install the recovery partition first.
Mizex said:
when I boot into recovery(Screen that shows phone with triangle and exclamation point)
Click to expand...
Click to collapse
jonnythan said:
You need to root the phone and install the recovery partition first.
Click to expand...
Click to collapse
Exactly what jonnythan said. If your recovery screen shows the triangle then you haven't installed a modified recovery image yet. Follow any of the guides on this site for rooting.
Oh wow I feel dumb the guide I was following said nothing about the phone needing to be rooted. I attempted to follow a 1 click root and while attempting to do the backup step I get a message saying that it can't complete the command. According to the guide if I get this error then it means I have a patched firmware and need to downgrade to a cupcake firmware.
Anyone know of a good guide for doing the downgrade? Or can perhaps share a bit of knowledge on the error?
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
EverAngelOn said:
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
Click to expand...
Click to collapse
Can you get into the bootloader still?
I can't
b3ltazar said:
Can you get into the bootloader still?
Click to expand...
Click to collapse
No, I can't. The screen is completely black.
Have you tried any of the suggestions in the thread you linked in the OP?
EverAngelOn said:
No, I can't. The screen is completely black.
Click to expand...
Click to collapse
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Wugs tool kit
First when you plug it in hold all three power buttons
Second
I also have used the tool kit it gets stuck all the time on the flashing system. I think its a time out error because of the complexity of extracting the image and flahing the image with out a retry or check command. Here is a fix that i have figured out. When in Wugs tool kit download the Os Version you want on your device locate the folder with the downloaded image and extract it using 7 zip. once extracted flash the remaing .img files seperatly under andvance setting menu select flash system then user data it should boot right up. if you forgot what version you flashed previously flash all img files boot bootloader system user etc. if you still have problems let me know. i can give you my email.
Click thanks if i helped
b3ltazar said:
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures
Click to expand...
Click to collapse
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
EverAngelOn said:
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
Click to expand...
Click to collapse
Unfortunately it sounds like you erased your bootloader and nvflash can do nothing for you unless you used the unbrickable mod before u f'ed up your tablet. Try sending it to asus for Warranty tell em you installed the ota update and it wouldn't boot up afterwards. I have read many threads about this issue with nobody being able to recover there tablet. Asus does have global warranty
Hello,
I had installed the Franco Kernel on my N4 some months back. I recently got the 5.0 Lollipop OTA update but i could not install it. I read somewhere that i needed to install the stock kernel to get Lollipop installed. So i got the factory image of 5.0 for N4 from google and manually tried to flash with some Kernel flasher app i dont recall the name. THAT WAS THE WORST DECISION I EVER TOOK.
Now my phone is stuck in fastboot mode. I can go to recovery and all. Whwn i try to start up my phone i can only see a black screen.. i downloaded adb but the problem is I HAD NOT TURNED ON USB DEBUGGING. I searched the net for a week,asked my friends who all said that i should throw away my old( i dont consider it old) phone and get a new one. I have come here with a lot of hope. I bought the N4 so as to use it for atleast another year .
Adb doesnt recognize my phone. Pc says "Android Device". Please help me. Im saving for getting my sister a laptop and i just cant afford another decent reliable phone.
You do not need USB debugging for fastboot mode. when cionnected is should say android device and some serial number.
USB debug mode is when the android OS is running not fastboot mode
if it does not when connected at the prompt type fastboot devices
follow the install instructions here and it should get you device back. (in the commands remember to replace the file names with the lollipop names)
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
I have brought back at least 10 devices from my own doing and from people that screw up their phone and not know what they are doing.
Good luck
Ok i will follow it. I currently have the 4.2.2 image file. Yes in fastboot mode PC recognizes it as Android Device. Lets hope i can do it I dont need USB debugging right ?:silly:
I dont know how i should thank you and this forum. I love you guys, you helped me when i had lost all hopes of getting my phone back i love you guys <333333333333333333333333333333333333333333333333333333333333333333
Glad it worked. Just spread the love on the forums.
I learned by reading here and glad to help others.
Hi!
First of all, yes I've browsed and tried the different solutions in the forum but none of them worked for me.
My Nexus 4 fell from my car (a long story) and the screen is completely destroyed, and yes I mean DESTROYED. The phone works cause the screen lights up and some colours still work, but I can't see anything, and the touchscreen of course does not work.
Problem is: I had a lock pattern so I can't access the data in my computer. I've tried Droidbrowser and the unified Android Toolkit, the last one always gets stuck on "waiting for adb mode" or something like that. I'm pretty sure I had USB debugging activated and all that, but except that, phone is factory, no root, no ROM, no unlocked bootloader.
I've been struggling with this for a while now, would appreciate some help!
Thanks in advance
dari1495 said:
Hi!
First of all, yes I've browsed and tried the different solutions in the forum but none of them worked for me.
My Nexus 4 fell from my car (a long story) and the screen is completely destroyed, and yes I mean DESTROYED. The phone works cause the screen lights up and some colours still work, but I can't see anything, and the touchscreen of course does not work.
Problem is: I had a lock pattern so I can't access the data in my computer. I've tried Droidbrowser and the unified Android Toolkit, the last one always gets stuck on "waiting for adb mode" or something like that. I'm pretty sure I had USB debugging activated and all that, but except that, phone is factory, no root, no ROM, no unlocked bootloader.
I've been struggling with this for a while now, would appreciate some help!
Thanks in advance
Click to expand...
Click to collapse
With out an unlocked bootloader or a custom recovery I'm afraid you're sol. Otherwise you'd need to boot into the os which you can't do with a lock pattern to use adb.
Sent from my Nexus 9 using XDA Free mobile app
>Install vysor on Windows.. Then connect to your phone..
semdoc said:
>Install vysor on Windows.. Then connect to your phone..
Click to expand...
Click to collapse
Well, vysor doesn't look like detecting my phone...
Data* not days for title...
Rooted and unlocked, I used my Nexus 6P for a few month after the infamous boot loop of death running 4 cores. Today seems to have been there final moments of my phone. I tried reinstalling the patch, I've tried waiting for four hours for it to turn on. However, it goes to the Google logo and dies. No Nexus logo at all. Google, die, Google, die. When I try to go into my recovery, Google logo, dies. I tried reinstalling the recovery, same thing happened.
Fastboot is working and I am rooted but for some reason when I type "adb devices" it says no emulator or device found and it refuses to see my Nexus 6P. When I type fast boot devices it shows the serial number of my phone.
I was going to use ADB to pull all my internal storage to my computer but ADB is refusing to see it. I made sure the driver was updated and I have the newest platform tools on my PC.
Is my internal storage pretty much gone at this point? ADB is refusing to recognize it and it will not turn on. There's no other way?
I have a broken 6P too for parts.. any way to salvage the snapdragon and put it in my phone? Lol.
snappycg1996 said:
Data* not days for title...
Rooted and unlocked, I used my Nexus 6P for a few month after the infamous boot loop of death running 4 cores. Today seems to have been there final moments of my phone. I tried reinstalling the patch, I've tried waiting for four hours for it to turn on. However, it goes to the Google logo and dies. No Nexus logo at all. Google, die, Google, die. When I try to go into my recovery, Google logo, dies. I tried reinstalling the recovery, same thing happened.
Fastboot is working and I am rooted but for some reason when I type "adb devices" it says no emulator or device found and it refuses to see my Nexus 6P. When I type fast boot devices it shows the serial number of my phone.
I was going to use ADB to pull all my internal storage to my computer but ADB is refusing to see it. I made sure the driver was updated and I have the newest platform tools on my PC.
Is my internal storage pretty much gone at this point? ADB is refusing to recognize it and it will not turn on. There's no other way?
I have a broken 6P too for parts.. any way to salvage the snapdragon and put it in my phone? Lol.
Click to expand...
Click to collapse
Same issue here was running latest Lineage everything updated can still get into TWRP but only can flash things like vendor & such via fastboot, but when I try to sideload new OS & gapps it'll take bout 50-75% of it then it'll reboot to bootloop & I get remote permission denied & adb doesn't list my device. Took it to a computer shop they said Nexus made weak logic board & I need a new one. I did find a video on utube saying the solder joints are weak & shows taking board out subjecting to heat & afterwards it runs fine and help appreciated
snappycg1996 said:
Data* not days for title...
Rooted and unlocked, I used my Nexus 6P for a few month after the infamous boot loop of death running 4 cores. Today seems to have been there final moments of my phone. I tried reinstalling the patch, I've tried waiting for four hours for it to turn on. However, it goes to the Google logo and dies. No Nexus logo at all. Google, die, Google, die. When I try to go into my recovery, Google logo, dies. I tried reinstalling the recovery, same thing happened.
Fastboot is working and I am rooted but for some reason when I type "adb devices" it says no emulator or device found and it refuses to see my Nexus 6P. When I type fast boot devices it shows the serial number of my phone.
I was going to use ADB to pull all my internal storage to my computer but ADB is refusing to see it. I made sure the driver was updated and I have the newest platform tools on my PC.
Is my internal storage pretty much gone at this point? ADB is refusing to recognize it and it will not turn on. There's no other way?
I have a broken 6P too for parts.. any way to salvage the snapdragon and put it in my phone? Lol.
Click to expand...
Click to collapse
The ADB commands do not work in fastboot mode. You are in fastboot mode as per fastboot devices command. Unless you can get recovery up and going you're pretty much left to luck. Sorry, not much help.
Aimless Rambler said:
The ADB commands do not work in fastboot mode. You are in fastboot mode as per fastboot devices command. Unless you can get recovery up and going you're pretty much left to luck. Sorry, not much help.
Click to expand...
Click to collapse
Do you know any way or if it would be possible to swap in another snapdragon processor to fix said bootloop? I can't find anything online about it really. I have another 6P with a broken screen but good processor.
snappycg1996 said:
Do you know any way or if it would be possible to swap in another snapdragon processor to fix said bootloop? I can't find anything online about it really. I have another 6P with a broken screen but good processor.
Click to expand...
Click to collapse
Seems like it would be easier to swap screens/LCD unit than trying to swap chips out. Google a few YouTube videos on Nexus 6P teardown and read the ifixit writeup. Between all the available online sources you get one good tutorial.
Aimless Rambler said:
Seems like it would be easier to swap screens/LCD unit than trying to swap chips out. Google a few YouTube videos on Nexus 6P teardown and read the ifixit writeup. Between all the available online sources you get one good tutorial.
Click to expand...
Click to collapse
I want to get off the data on the phone much as my pictures and music primarily which is why I'm not concerned with swapping those things.
snappycg1996 said:
I want to get off the data on the phone much as my pictures and music primarily which is why I'm not concerned with swapping those things.
Click to expand...
Click to collapse
Tough spot without recovery. Have you tried any of the "heat up the back" tricks? I've never had to try it but I've read by heating the back, with heat gun or blow drier, just above fingerprint sensor (approximate location of chip) it will trick the phone into throttling off cores long enough to get into recovery. May be worth a shot.
Aimless Rambler said:
Tough spot without recovery. Have you tried any of the "heat up the back" tricks? I've never had to try it but I've read by heating the back, with heat gun or blow drier, just above fingerprint sensor (approximate location of chip) it will trick the phone into throttling off cores long enough to get into recovery. May be worth a shot.
Click to expand...
Click to collapse
That was when it first boot looped. All this is after the four core patch lol. It's probably just done for.
snappycg1996 said:
Data* not days for title...
Rooted and unlocked, I used my Nexus 6P for a few month after the infamous boot loop of death running 4 cores. Today seems to have been there final moments of my phone. I tried reinstalling the patch, I've tried waiting for four hours for it to turn on. However, it goes to the Google logo and dies. No Nexus logo at all. Google, die, Google, die. When I try to go into my recovery, Google logo, dies. I tried reinstalling the recovery, same thing happened.
Fastboot is working and I am rooted but for some reason when I type "adb devices" it says no emulator or device found and it refuses to see my Nexus 6P. When I type fast boot devices it shows the serial number of my phone.
I was going to use ADB to pull all my internal storage to my computer but ADB is refusing to see it. I made sure the driver was updated and I have the newest platform tools on my PC.
Is my internal storage pretty much gone at this point? ADB is refusing to recognize it and it will not turn on. There's no other way?
I have a broken 6P too for parts.. any way to salvage the snapdragon and put it in my phone? Lol.
Click to expand...
Click to collapse
Did you try to boot twrp through fastboot?
"fastboot boot twrp.img"
If this is successful you should have access to your data.