Nexus 4 rooted and unlocked, TWRP 3.0.
Yesterday I updated with the CM13 nightly, which locked up the phone. No big deal, I thought I would just wipe and restore. Except I discovered my restore image wasn't there. Now I have no OS, but worse I can't connect to the phone via ADB/Fastboot.
The phone doesn't show up in the device manager at all on my pc after many driver uninstalls and installs. Then i installed ADB/Fastboot drivers on my macbook. Terminal commands for ADB/Fastboot work, but no device is found while in bootloader.
Any guidance is appreciated.
rickp1777 said:
Nexus 4 rooted and unlocked, TWRP 3.0.
Yesterday I updated with the CM13 nightly, which locked up the phone. No big deal, I thought I would just wipe and restore. Except I discovered my restore image wasn't there. Now I have no OS, but worse I can't connect to the phone via ADB/Fastboot.
The phone doesn't show up in the device manager at all on my pc after many driver uninstalls and installs. Then i installed ADB/Fastboot drivers on my macbook. Terminal commands for ADB/Fastboot work, but no device is found while in bootloader.
Any guidance is appreciated.
Click to expand...
Click to collapse
What happens when in the bootloader you choose recovery? What happens when you try to boot normally? Did you do anything special when you installed the nightly? What did you wipe?
Sent from my Nexus 4 using XDA Labs
rickp1777 said:
Nexus 4 rooted and unlocked, TWRP 3.0.
Yesterday I updated with the CM13 nightly, which locked up the phone. No big deal, I thought I would just wipe and restore. Except I discovered my restore image wasn't there. Now I have no OS, but worse I can't connect to the phone via ADB/Fastboot.
The phone doesn't show up in the device manager at all on my pc after many driver uninstalls and installs. Then i installed ADB/Fastboot drivers on my macbook. Terminal commands for ADB/Fastboot work, but no device is found while in bootloader.
Any guidance is appreciated.
Click to expand...
Click to collapse
Been there, does your phone show up as Qualcomm HUSB device in device manager ?
Sent from my Nexus 4 using XDA-Developers mobile app
Same happened here it originally booted up and just get stuck on cyan mod symbol boot loop so I restarted it and thought that would help but it didn't so I was told to factory reset it witch I did now it just gets stuck on Google so I tried re installing through recovery but nothing is there not even an os just recovery logs so I tried using a toolkit on my pc that didn't work because of the adb can't be turned on which now just insta ****s all solutions I have found so far I too am or rather was using nightly cm13
Related
When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?
SpectralFlames said:
When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?
Click to expand...
Click to collapse
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize
RubbleTea said:
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize
Click to expand...
Click to collapse
Could you give me instructinos on how I would do that?
I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that
CoryFNM said:
I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that
Click to expand...
Click to collapse
MATE you saved my day...thanks so much....got the stock image back working again with the help of the command in the thread you where mentioning.
thanks once more.
best.
upage
I just installed TWRP on my N4 and have never used it before. I always used CWM and I just wiped it through recovery. My issue is that I wiped EVERYTHING. It says "no OS detected" and won't boot past the Google logo. Can't install drivers when connected to the computer, and I can't for the life of me figure out how to flash a stock image, or fix it with the nexus root toolkit. Could someone PLEASE give me a walkthrough for a noob of how to go about fixing this? I don't understand a lot that deals with ADB and all that. Thank you.
Sent from my Z665C using xda app-developers app
Google tool adb fastboot drivers. Then Google nexus 4 factory image and download that. Use 7-zip to extract it. Flash the flash-all.bat while your phone is in fastboot mode and connected to your pc
Sent from my Nexus 5
Do I she the factory image it originally had which was 4.2.2 or do I use the image I updated to which was 4.3? Don't know if it matters, but I've never done this so I don't want to make anything worse.
Sent from my Z665C using xda app-developers app
If you don't understand, this time right now seems a good reason to learn about it right?
As to you problem, can you boot into recovery..the twrp? If yes, then it is easy. Just sideload a rom (preferably a 4.2.2 rom as it was the last rom on your device). Oh and yeah, sideload does use a bit of adb command (see how important it is for us, the nexus user?).
The other way is to simply use toolkits (which is a shortcut, not good as you will learn nothing of the whole process and it just takes all the fun away). Look in original android dev section for wugfresh toolkits (but I really, really, really hope that you learn ADB. After all, we need to learn to count before we start using a calculator right? ). Good luck. Don't sweat it so much.
p/s: That video there can be used for any android version and any rom of nexus 4.
Sounds easy enough. My only issue has been that I couldn't install any drivers. I can boot into twrp, but that's it. Any guide I've researched says to turn on USB debugging, which I can't figure out how to do since it won't boot past the Google logo, and the drivers won't install correctly when I connect the nexus to a computer.
Sent from my Z665C using xda app-developers app
Use wugfresh nexus root tool kit to flash a stock rom.
USB debugging is not required to flash a stock ROM via fastboot.
sinndissension said:
Sounds easy enough. My only issue has been that I couldn't install any drivers. I can boot into twrp, but that's it. Any guide I've researched says to turn on USB debugging, which I can't figure out how to do since it won't boot past the Google logo, and the drivers won't install correctly when I connect the nexus to a computer.
Sent from my Z665C using xda app-developers app
Click to expand...
Click to collapse
The easiest in my opinion would be sideloading a new rom, like cm11, paranoidandroid etc. Then you could easily install it on your n4
See here how to do it: http://teamw.in/ADBSideload , http://forum.xda-developers.com/showthread.php?t=2559200 , http://forum.xda-developers.com/showpost.php?p=45798359&postcount=825
Tried the toolkit yesterday. Didn't work because it couldn't install the drivers
Sent from my Z665C using xda app-developers app
Install drivers manually. Just Google "nexus 4 USB drivers" download and install. Then get toolkit and flash stock image.
Sent from my Nexus 4 using xda app-developers app
I'll try again. I was able to figure the drivers out. Tried flashing a stock image I downloaded, but I still wouldn't boot past the Google logo. I flashed it to the system partition, but I didn't know what partition to flash it to. Do I need to use the modified boot image it wants me to download, or am I supposed to flash it to a certain partition?
Sent from my Z665C using xda app-developers app
FIXED IT!!! thank you all for your help.
For anyone else with this problem, I downloaded "universal naked drivers" and installed them manually, use the Nexus Root Toolkit selected "soft brick, than flash stock/unroot, let it download RETORT and the modified boot image, flash it in fast-food, then when it booted up, re-rooted. (You lose root access when you do this).
I installed a custom rom, decided I wanted to go back to stock by restoring from TWRP, now in bootloop. I can boot into recovery and bootloader via the phone but my PC does not recognise that it is connected via bootloader. Is there a way I can rescue my device?
I have build B29M, and noticed there is a zip version of another build on this forum which I could have installed through TWRP, but would that make things worse?
Thanks for any advice..
Stupid question probably, as you've already installed a custom ROM, but you do have the fastboot drivers installed on your PC?
Yes it all worked before, I think it's because the phone must have defaulted back to not being in Debugging mode, and I can't access the OS to enable this mode.
leicablue said:
Yes it all worked before, I think it's because the phone must have defaulted back to not being in Debugging mode, and I can't access the OS to enable this mode.
Click to expand...
Click to collapse
Well, if you can reach recovery, flash another custom ROM to get the phone usable, then flash back to stock, looking at points 11 and 12.
I managed to fix it, for anyone who may encounter similar issue in the future...I tried restore again from TWRP but this time did not select Vendor Image, only Vendor.
I have this same problem, my PC doesn't see the phone when I go to bootloader and I can't fastboot at all. I can use my phone regularly copy files over. I already flashed to a new ROM from cataclysm to purenexus but still can't fastboot.
Sent from my Nexus 6P using Tapatalk
I've posted in a few places here on xda but no responses yet, please help! I've unlocked bootloader, rooted, installed twrp, tried to flash cm13 but had the wrong gapps, so it failed, I tried to wipe and restore a backup I made in twrp but it says my device is corrupt then halts at the Google logo. I think all I need is to push the correct gapps to the phone through adb but I can't get my stupid pc to recognize it anymore. I boot into twrp, plug it in to the pc, tried multiple tools and sdk adb route, but nothing works! I have all the drivers installed, and reinstalled, keep getting a Windows error "The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll"
I read somewhere that the ws2_32.dll is only available in Vista and up... I'm running xp, I wonder if that's my problem. Sorry for all the posts and long explanations, I'm just frustrated and need professional help
You could get that dll somewhere and add it to your windows. I never flashed under Win XP... Also, you could try to download the factory image (NRD90U) from google. Boot your phone on fastboot mode and flash all the .img one by one and should be back to stock... That should fix your problem hopefully!
How do I boot into fastboot mode? I can get to the ko'd android and select options and get into twrp, it says download mode disabled and connect usb data cable, which doesn't change when I plug it in but I see my serial under fastboot in the skipsoft tool kit. I mainly get that error message when using that tool kit too
wonton9224 said:
How do I boot into fastboot mode? I can get to the ko'd android and select options and get into twrp, it says download mode disabled and connect usb data cable, which doesn't change when I plug it in but I see my serial under fastboot in the skipsoft tool kit. I mainly get that error message when using that tool kit too
Click to expand...
Click to collapse
If you're running XP your pretty seriously out of date.
All of them say download mode disabled when you are in your bootloader. If you see the little droid on his back and the ascii device status in the bottom left corner of your screen you are in bootloader (which is fastboot 'mode' as you put it). Since it is returning your serial number it sounds like you're good.
I expect you may want to simply reflash the stock OS from your Skipsoft kit. Get it booted stock first, then install a custom ROM.
Ok thanks, got my bro here with his win 7 laptop, gonna try and see about pushing the correct gapps to the phone first, if I can't get adb to work when booted into twrp I guess I'll try the fastboot method to stock.
Is it safe to use the Skipsoft toolkit to flash stock Rom while I have twrp installed? And unlocked bootloader?
wonton9224 said:
Ok thanks, got my bro here with his win 7 laptop, gonna try and see about pushing the correct gapps to the phone first, if I can't get adb to work when booted into twrp I guess I'll try the fastboot method to stock.
Is it safe to use the Skipsoft toolkit to flash stock Rom while I have twrp installed? And unlocked bootloader?
Click to expand...
Click to collapse
If your device is currently borked, just start from scratch. If you flash the factory image partitions properly as per Heisenberg's guide then recovery is overwritten anyway. And, you can't flash anything unless your bootloader is unlocked. You would need to reflash TWRP and SuperSU after it first boots.
Sent from my Nexus 6P using Tapatalk
Thanks, I'm trying the skipsoft toolkit it's flashing the stock img now, I'll let ya know how it goes, fingers crossed!
wonton9224 said:
Thanks, I'm trying the skipsoft toolkit it's flashing the stock img now, I'll let ya know how it goes, fingers crossed!
Click to expand...
Click to collapse
I would suggest booting it up stock and letting it set up before flashing TWRP and then rooting. And if you do, when you flash TWRP via fastboot, boot right to recovery and flash SuperSU, otherwise TWRP will get overwritten by stock recovery. Rooting stops that.
Sent from my Nexus 6P using Tapatalk
I followed Heisenberg's guide with no problems the first time, it was all good before I was stupid and flashed a Rom with wrong gapps and tried to restore a backup, thanks tho, I really appreciate the help!
wonton9224 said:
I followed Heisenberg's guide with no problems the first time, it was all good before I was stupid and flashed a Rom with wrong gapps and tried to restore a backup, thanks tho, I really appreciate the help!
Click to expand...
Click to collapse
So you went through that and flashed the wrong Gapps pkg again? I may regret asking but what custom ROM are you flashing? There are really only debloated stock variants right now.
Sent from my Nexus 6P using Tapatalk
Not again, only flashed wrong gapps once, was trying to flash cm13 and got the gapps from opengapps.org. It's ask good now tho, I'm back to stock thanks to you guys and the skipsoft toolkit! Thanks again!
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
roelmmata said:
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
Click to expand...
Click to collapse
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
roelmmata said:
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
Click to expand...
Click to collapse
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Click to expand...
Click to collapse
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
roelmmata said:
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
Click to expand...
Click to collapse
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
Thanks I try it out!
ultyrunner said:
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Click to expand...
Click to collapse
Hey again
I used guide specifically to go back to stock, combined with a couple times of wiping in stock recovery I finally got the phone to boot up! However I've learned something new, the phone will only stay on if I'm plugged into charger, and as soon as it's unplugged it turns off. Any other suggestions?