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
Related
I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.
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?
I want to make a clean Install of factory image (Android 8.0 Oct) on my Nexus 6P with TWRP.
Should wipe Dalvik, Data, System and Internal storage, then move the stock zip file (That I downloaded from google's web) from my computer to my phone and just install in TWRP? Will it work?
Device is unrooted, only has an open boot loader, I just want to make a clean install of Android 8.0
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
coremania said:
If you wipe your internal all your downloads and your factory image are gone.
Sure you can flash the unpacked *.img with twrp, but don't try to flash the bootloader or radio with twrp.
If you really want a clean start and wipe everything, then you should flash the factory image with fastboot. This will update your bootloader and radio too.
Click to expand...
Click to collapse
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
AndroMani said:
Hi coremania, I have a few questions towards this method.
1. If the stock image is stored in either external SD card OR USB OTG, even then will there be any problem installing the the stock rom back using TWRP?
2. If the boot loader is unlocked, should one has to re-lock it first before reinstalling the stock rom either thru' TWRP or thru' Fasboot commands?. and finally,
3. Is it not advisable to flash the stock rom from the full factory image using TWRP rather than Fastboot?
(As I think it is easier to flash thru TWRP than typing those ADB commands in Fastboot).
Thank you for your inputs.
Click to expand...
Click to collapse
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
sinjok said:
I hope someone here can help answer this question. I also want to flash factory image version 8.1.0 on my nexus 6P. But somehow my phone is not recognized by any computers I tried to plug it in. When I plug in the usb cable to the phone, it doesn't pop up the usb notification to choose MTP for file transfer. Then I try with Developer tab in Settings to choose it manually (USB debugging is enable) but it still doesn't work. My laptop has been updated with android usb drivers and other stuffs. I have a second phone (Oneplus 1) and it's recognized by my laptop the moment I plug it in. Please suggest any solutions to fix this. Thanks everyone.
Click to expand...
Click to collapse
Check your cable, or try a different with different port.
In the Dev options you can reset the debugging options, i guess a reboot is necessary afterwards.
coremania said:
If you decide to flash and test some stuff the bootloader should be always unlocked. If anything will went wrong and your bootloader is locked you're mostly f***ed. Never relock your bootloader until you want to sell your device.
I mostly use flashfire to flash stock and custom roms, TWRP is ok too, but it's easier to keep root and TWRP with flashfire by flashing stock images. Do not flash bootloader and radio with flashfire, never ever !!! There are TWRP flashable zips for bootloader and radio here on XDA, you only should use these with TWRP, but the safe way for bootloader and radio is fastboot for sure. Fastboot is the safest way for flashing stock,
but not absolutely necessary, you have to decide this for yourself.
Edit: to your first question, I never flashed with USB otg on the n6p, but I think yes it should be fine.
Click to expand...
Click to collapse
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
You don't need to ever relock your bootloader. If you want to try stock and use TWRP try SuperXe 8.1. It's just flaahable stock with some extras you can opt out of your not intereseted.
AndroMani said:
Thank you for the clarification. So, far I have not faced a situation to flash my custom recovery either thru' TWRP or thru Fastboot. Instead, I am using my Nandroid backups taken from TWRP and using it to restore my system after I try a custom rom OR upgrade my system with the latest Magisk version for a systemless root. So far there are no issues. But, I wanted to be aware of the methods to go back to stock (without any user installed apps/data) if need be. I read in some forums that we need to re-lock the unlocked bootloader if we want to go back to stock rom using fastboot. Otherwise, the system will not be installed alright and might cause a bootloop.
That's why I wanted to clarify.
Thanks again for your inputs.
Click to expand...
Click to collapse
I can't confirm the relock and unlock method to go back to stock. Senseless to me.
Hi guys,
I have an old Galaxy Note 4, and I completely forgot its password now.
I've noticed that some of guys use custom recovery like CWM to reset their Android password.
But maybe because I found it deep in the garage, the USB port didn't work.
Is there any way to install a custom recovery from stock recovery using only the SD card?
Or, is it not possible to make the custom recovery run automatically when the SD card is inserted and the recovery mode is turned on?
Please help.
This is not possible. If you're on stock firmware, the only way to install custom images is via a USB cable using Odin. The device will only load either the boot image or the recovery image; the stock recovery image only accepts firmware packages signed with Samsung's secret key. There is no way to modify anything on the device without first using Odin to flash TWRP to /recovery. This is a security feature of Android to prevent rogue apps or rootkits from installing unsigned packages.
V0latyle said:
This is not possible. If you're on stock firmware, the only way to install custom images is via a USB cable using Odin. The device will only load either the boot image or the recovery image; the stock recovery image only accepts firmware packages signed with Samsung's secret key. There is no way to modify anything on the device without first using Odin to flash TWRP to /recovery. This is a security feature of Android to prevent rogue apps or rootkits from installing unsigned packages.
Click to expand...
Click to collapse
Thank you for your reply.
I remember that this phone is not rooted and I have never had USB Debugging or Developer Mode turned on.
Is it possible to unlock the password by repairing only the USB port in the current situation?
There is a record of my conversation with my late father on this phone, and I really want to unlock it.
mas579ter said:
Thank you for your reply.
I remember that this phone is not rooted and I have never had USB Debugging or Developer Mode turned on.
Is it possible to unlock the password by repairing only the USB port in the current situation?
There is a record of my conversation with my late father on this phone, and I really want to unlock it.
Click to expand...
Click to collapse
Unfortunately, no.
To be able to run custom software such as TWRP, you would have to unlock your bootloader, which would wipe data.
Your best bet is to have the USB port repaired so you can at least charge your device, then do your best to remember your password.