Related
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
GedBlake said:
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hi guys, I actually encountered this problem a minute ago when I attempt to flash a new version of TWRP recovery on my grouper. Whenever I go to the recovery, it just shows 'No command' with a red alert of Android on it (I started to panic when I found that there's an unusual error that prevents me from entering the recovery and this is the first time that I saw this error on my flashaholic experience *btw my previous recovery was CWM) I'm currently on stock 4.4.2 with an unlocked bootloader. I have no idea what problem is causing to display that issue when attempting to enter recovery but then I left it for like 5-10mins while it's displaying that error and after that the device reboots then it just quickly enter TWRP recovery normally as is :silly: sick of that haha, silly ol grouper jesus -_-
EDIT
After entering recovery, I got stuck forever on bootloader and recovery! whenever I reboot, I always get directly enter to the recovery and it forces me to not to enter the ROM oh my god at least I can still configure the recovery so I can backup and flash another ROM :|
Hi everyone,
I recently got the 4.4.2 OTA update from google and as soon as it restarts, it gets stuck in recovery with an error saying "No Command". I can successfully reboot into 4.4 without issues but it downloads it again and I get the same error.
Im running Stock 4.4 without ROOT or any mods,
Thanks for the help!
I would recomend all wipes available in recovery, but you will loose all data. APS will restore if you store aps data in google
tapped from ace
If you are fully 100% stock and not rooted, download the latest stock image here: https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
The site: https://developers.google.com/android/nexus/images#mantaraykot49h
the links are messed up but use the above as it works.
Then extract and apply via fastboot:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
This should NOT cause you to lose any data and see if that fixes your issues.
good luck
planet_x69 said:
If you are fully 100% stock and not rooted, download the latest stock image here: https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
The site: https://developers.google.com/android/nexus/images#mantaraykot49h
the links are messed up but use the above as it works.
Then extract and apply via fastboot:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
This should NOT cause you to lose any data and see if that fixes your issues.
good luck
Click to expand...
Click to collapse
After running"fastboot oem unlock" and restart the bootloader, it returns to locked all by itself...
Not sure whats wrong.
Not sure why you needed to unlock to begin with. If you are fully stock and run the unlock command it will do a factory wipe if it completes successfully.
Unlocking and updating are different things and not really related so I'm a bit lost with your response.
planet_x69 said:
Not sure why you needed to unlock to begin with. If you are fully stock and run the unlock command it will do a factory wipe if it completes successfully.
Unlocking and updating are different things and not really related so I'm a bit lost with your response.
Click to expand...
Click to collapse
I did try to update and it says its successful but after i restart the n10, im still on 4.4 with my data intact. I tried to unlock the bootloader to use the flash-all.bat command.
Its very weird, any pictures i delete or apps i remove, after a restart, they come back. It also freezes a lot randomly to a point where it becomes unusable.
I guess my tablet is dying but it sucks because its only been a week since my warranty expired...
I don't think you need to unlock to apply the factory image. It will wipe and replace all if you run it from your PC. The whole point of it is to completely wipe your tablet and replace it with a clean base OS.
I'd be surprised if its a hardware issue. At this point you should just extract the 4.4.2 factory image and run the batch file with no unlock commands before or after. This will wipe all data everywhere and should successfully restore your tablet to operation.
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
sl2222 said:
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
Click to expand...
Click to collapse
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
IT Rider said:
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
Click to expand...
Click to collapse
Hi, I have exactly the same problem after installing Android 5.0 OTA. Please post a solution here if you find it. Thanks!
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
sl2222 said:
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
Click to expand...
Click to collapse
But I cannot flash any rom as none of ADB commands can be run (device is not connected, though I connected it with OEM cable). I tried factory reset but it didn't help.
Just wanted to share what worked for me after the OTA update failed and flashing stock images didn't work. Put the tablet in fastboot. Installed stock image, tablet wouldn't boot. Restarted went into recovery got the android on its back with the red x coming out of it (did not say bad command at thia point). I presses volume up and power at the same time on this screen. Cleared cache and rebooted then the tablet booted up.
I cannot believe companies still get away with this inadequate device "killing" type of software. Did no-one at the company do any testing before release?????
Rant over, onto solution - for me anyway.
The issue I had was that I could not get ADB to be of any use so switched to fastboot. Should have used fastboot from the getgo. Hohum.
So, into recovery with android on it's back with red triangle and reboot into fastboot.
Connect N10 to PC with USB cable.
Downloaded "Minimal ADB and Fastboot"(MAF)
Downloaded Lollipop for Nexus 10 - image-mantaray-lrx21p.zip and saved to c: drive (this saves loads of typing at command prompt)
File path for update is c:\image-mantaray-lrx21p.zip
Open MAF and ensure folder path points to your MAF install folder..
At command prompt type fastboot update c:\image-mantaray-lrx21p.zip
If you want to wipe device prior to update then type fastboot -w update c:\image-mantaray-lrx21p.zip
This may take a while so go make a drink - or something.
If all goes well, mine did, you should eventually be presented with the lollipop opening screen and a working device.
Just finally got it working!
ROM updates from ADB Sideload or Fastboot failed every time for different reasons.
What I had to do is to flash custom recovery (latest TWRP) with "fastboot flash recovery <recovery.img>" command.
From TWRP flashing the official ROMs also failed. But flashing Lollipopalooza as sl2222 suggested finally succeeded.
Thanks for all the help!
Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
mfastboot.exe flash recovery twrp-2.8.6.0-ghost.img
sending 'recovery' (9488 KB)...
OKAY [ 0.849s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.819s
Click to expand...
Click to collapse
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.
And you are booting straight to recovery after flashing via volume down and then volume up to select not the power button?
_litz said:
Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.
Click to expand...
Click to collapse
After you flash TWRP, at the command prompt type:
fastboot reboot-bootloader
I can't remember where I read it but some people said they had to do that to get the custom recovery to stick.
THEN unplug your device from your computer and reboot into recovery by scrolling down with the volume down button to highlight recovery and then hitting the volume up button to select recovery.
Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP ... to develop this process)
So ... the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.
_litz said:
Ok, figured this out ...
Click to expand...
Click to collapse
I think all that needs to happen is after you flash TWRP - you don't boot into recovery. Instead, reboot into bootloader mode. This has been a problem from the beginning for some people with their MX13's and not a new thing. I don't think it has anything to do with the update. Some people have to reboot into bootloader after flashing TWRP in order to get it to stick for some reason.
@_litz Please understand that @JulesJam is correct... the proper way to flash a recovery is as follows...
Start the phone to the Fastboot AP/Bootoader menu
using moto's fastboot (aka mfastboot) exectue the following...
mfastboot flash recovery RecoveryYouWishToFlash.img
mfastboot reboot-bootloader
Then use the volume/power keys to enter recovery.
Once in the recovery, it is safe to Reboot the phone normally.
that mfastboot reboot-bootloader step has been crucial for getting the newly flashed recovery (3rd party OR Stock!) to "stick" on the phone.
Flashing with RSDLite is over kill.
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.
_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
That is because you are pressing the power button when you should be pressing the volume up button.
Yep ... ain't my first rodeo ....
It flat out refused to take recovery.
I had to back it back down to the old 4.4.4 version, reflash TWRP, then I simply applied the whole RSD package (sans recovery) to re-upgrade it to the new 4.4.4.
Worked like a charm.
(Plus it gave me a chance to extract the fxz from the moto manager app)
Travisdroidx2 said:
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.
Click to expand...
Click to collapse
yes, that is what is happening.
See above ... this isn't my first time at this. Was not working as described.
_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
Was not trying to insult your knowledge. That is a very common problem that many do. So I had to ask.
_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
You needed to reboot into bootloader by typing fastboot reboot-bootloader after your flashed TWRP. THEN disconnect your phone from your computer and boot into recovery by using the volume down to highlight recovery and volume up to select recovery.
If you follow those instructions, you will flash TWRP fine. No need to go through that long drawn out process you came up with.
Probably should rename or delete this thread, since its fairly misleading.
Check in the /system partition for a file named recovery-from-boot.p or something similar. If that file is there it will reflash the stock recovery when you reboot, and I've seen it reflash when booting into recovery.
I just used the TWRP manager app from the Play store after reverting to stock recovery and installing the OTA. It worked perfectly the first time.
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
I'm curious as to what is different.. because the other day after flashing stock recovery back on my phone, taking the update to 212.166.3 KXA21.12-L1.26-3 which Verizon just pushed, I used those EXACT STEPS to put TWRP back on my phone and had no problems.
Beats me ... for me, it didn't work ...
So after I got things back onto the old 4.4.4 version, I put together the FXZ with the modified xml file, and simply re-updated, applying both the update, and TWRP, all in one go.
anyone else on old 4.4.4 can do the same thing if they wish, which was why I posted the links and the instructions.
not to bump this thread, but I had zero issues going from stock with 212.55.26 ota update installed and flashing twrp. it just worked like normal.
i would agree with @superkeest seems like this thread should get renamed.
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
StarShoot97 said:
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
theesotericone said:
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
Click to expand...
Click to collapse
I said it looks like this, I did not say the button is the reason
When I access fastboot it stays there until I manually select an option
ultyrunner said:
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
StarShoot97 said:
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
Click to expand...
Click to collapse
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
When stock recovery is installed, I am from time to time able to access it (most of the times it just ends in a bootloop)
If I flash TWRP I can't access it, no matter how often I try
I have factory reset my phone, the stuff on the internal is still there and I want to reach this, as I have my chats, SMS, university stuff and so on backed up on the internal storage
I am trying everything - all the regular adb methods, toolkits, every driver, nothing is working
Sorry if you don't understand my situation, but I am in a pinch right now
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery and cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Edit2: wrong, see my latest reply
RoyJ said:
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery. Perform a factory reset again like you already mentioned you did as well as a cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Click to expand...
Click to collapse
I did this already exactly like you wrote, did it again now, and I am still stuck in the reboot loop (boots up to Google Logo, then shuts itself down; repeat)
Can't reach recovery mode either
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Fastboot twrp 3.0.0-0 then try to access it
RoyJ said:
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Click to expand...
Click to collapse
Yes, I think so too. I flashed the phone with the full Stock image, the bootloop is still there.
Looks like my precious is dead
At least I have my most important data like phonenumbers, pictures and SMS saved to the cloud
Gonna RMA it tomorrow
Goodybe my precious, I hope you'll be fine :crying:
Got my device back today, the mainboard was damaged, so I had no chance to get my data from the phone
Hey, at least my warranty has been renewed 'till 2018
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
Try flashing TWRP 3.0.2-3 or boot into twrp through fastboot. Using
fastboot boot recovery <twrp filename>.img
I think booting to twrp using this command will work.
And here's the link to Twrp 3.0.2-3 , as its not available on Official Twrp page.
https://idlekernel.com/twrp/nexus/twrp-3.0.2-3-angler.img
I had the same problem with my 5X, nothing worked I tried every possible solution described above and more. Nothing. I figured out that there was nothing to loose and followed directions from YouTube videos (links below) and it worked. Used heat gun at max temp for about 2 mins from each side. It's been about 12 hours since then, phone works flawlessly. Here are the links:
https://www.youtube.com/watch?v=SD25mdrgAys
https://www.youtube.com/watch?v=Cqh2x-TGnCY
Be careful handling the motherboard after you heat the first side, let it cool first before you start working on the second side. The same with the second side do not pick it up until it's cool.
5X, Pure Nexus Rom 7.1.2 June 5th security update, Elemental X Kernel,
has anyone found solution to this?????