Database Users

TWRP 2.1 | fff 1.4a problem

Rom: Stock
Rooted with KFU 0.9.5
TWRP 2.1
fff 1.4a
The problem I'm having is that when I boot my KF up it goes to fff. I get 3 options to boot from (this is whenever I power down the KF). When I choose to boot to recovery, the power light turns orange for two secs and then it boots; but back to the fff screen. I did this about four times in a row and it still boots back to the ffa screen.
If I choose ~normal boot~, It boots up fine. When I try to use KFU to boot to recovery or fast boot, it says that it is waiting for device. I tried this several times but no luck.
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
I'm not very advanced in this stuff. Please be patient with me. Thank you for all your help.

what command are you using to install recovery?
ok
download twrp 2.1.1.img onto pc
turn off kindle (20 second hold) with the usb cable unplugged from the kindle
open terminal where you have fastboot located.
type the following:
fastboot flash recovery </enter/path/to/recovery.img/here>
press enter
you should see waiting for device
then plug in your usb to kindle
this should power up the kindle and fastboot flash a new recovery.
then type
fastboot reboot
note:
(there is a space between recovery & /
i also find it easier to put a space after "recovery" then drag & drop recovery.img into terminal)

ok...
I did everything you said and the cmd console was still <waiting for device> after I plugged in the KF.
I checked in device manager and that's ok for the adb (it says: android composite adb interface).
Still looking to get into twrp recovery.

IndianaBond said:
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
Click to expand...
Click to collapse
There's probably something wrong in KFU's process. Could you at least show us its log or a screenshot?

reflash twrp using smirkit. than try to get into recovery again
Sent from my Galaxy Nexus using xda premium

if its waiting for device your pc is issuing fastboot command. so as you say its your kindle.
one of the above methods should work.
imho smikis's smirkit is nice to use
edit: can you copy and paste your commands after you try to flash new recovery

[GUIDE] Nvflash-ICS Restore

Nvflash-ICS Restore!
This guide will not provide information to install Nvflash-ICS as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
The second method to restore has been removed until further study can be done!
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
I have finished installing Nvflash but where are my files?
/sdcard/AndroidRoot/ - this is your internal sdcard
Click to expand...
Click to collapse
What files should I have?
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
Click to expand...
Click to collapse
Nvflash recovery and going back to ICS for a fresh start.
Use blobunpack to unpack a stock ICS blob. The blob is found by unzipping the stock ICS firmware twice.
You can find the ICS firmware at this link (9.4.3.30) (post #3).
[INDEX][18 April 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
Please give philos64 a thanks while there, without him you would have a very hard time finding these downloads if at all.
these files have to be in the folder with Nvflash
wheelie -r --blob blob.bin -created with Nvflash install
nvflash --resume --download 4 blob.EBT -created with blobunpack
nvflash --resume --download 10 blob.APP – created with blobunpack
nvflash --resume --download 6 blob.LNX – created with blobunpack
nvflash --resume --download 5 recovery.img-ICS twrp recovery image name
nvflash --resume --go
then press volume down to enter twrp, flash root, flash rom or whatever you wish
Click to expand...
Click to collapse
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
What is blobunpack?
Here are some links to download and explain use.
https://github.com/AndroidRoot/BlobTools
windows compiled blobtools - http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
There were no dates for the following information.
The current AndroidRoot.mobi bootloader versions are
Transformer Prime: 9.4.2.28r01
Transformer TF300: 9.4.3.30r01
Transformer TF700:9.4.5.30r01
ChangeLog:-
Patch: Enable ‘fastboot boot’ command (removes ‘fastboot continue’, use ‘fastboot reboot’ instead).
Patch: Force unlocked state (protect your unlock status no matter what happens to your token).
Patch: Remove blob requirement from ‘fastboot flash’ (Flash the raw images (example: ICS_recovery.img) and not blob files).
Click to expand...
Click to collapse
When failing to get into APX mode you can try the following suggestions.
Special thanks to wha2do and daws for their input!
Also wha2do has posted a guide to enter APX that provides detail not found here! Please see his guide and give proper thanks if you find it helpful!
http://forum.xda-developers.com/show...3#post36159253
1.To enter APX mode you either have to boot, choose reboot (if available) and hold volume up pressed until it reboots and then the screen should remain black. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume up pressed while pressing power on and keep it pressed until screen is blank.
or
2.fastboot -i 0x0B05 reboot (hold volume up)
or
3. adb reboot (hold volume up)
or
4. with unit powered on hold volume up and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -hold volume up.
This is done using a terminal; Android terminal is free from the play store. You must be rooted for this to work.
or
6. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.You should now be in APX mode.
Thanks for the help daws.
or
Only if there is no other resort!
7. remove cover from unit, disconnect battery, press and hold volume up, reconnect battery!
Click to expand...
Click to collapse
Good Luck!
Click to expand...
Click to collapse

Due to my dock smoking my motherboard I have purchased a new motherboard and luckily it came as 4.0.3 ICS.
I now have installed and use Nvflash on my tablet.
In case anyone is interested this is the unit I purchased.
The box shows - Manufacturer's Reconditioned Parts - 90 Day Limited Warranty.

Usefull guide
Good work and helpfull guide for xda members :good:
Nice stuff

philos64 said:
Good work and helpfull guide for xda members :good:
Nice stuff
Click to expand...
Click to collapse
Thank you for your kind words.

can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.

chanhny said:
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
Click to expand...
Click to collapse
No.
The files contain device-specific keys and cannot be used for other devices.
See the original thread for details:
[DEV][TOOL][BRICKPROOF]TF300 NVFlash release!

There's something I've not been quite clear about with NVFlash.
So I do my backup and keep my files.
Afterwards I upgrade to Jelly Bean (because I need the JB bootloader for ROM's right?), put TWRP recovery on, and flash a new ROM that uses the bootloader version I have.
So now I have the JB bootloader, can I still enter APX mode and do a restore, or do I have to remain on ICS bootloader to do a restore?
Is NVFlash truly unbrickable? A glance at this forum shows loads of bricks, would this have sorted their problem if they backed-up first?
Thanks!

tobdaryl said:
This guide will not provide information to install Nvflash as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
I have finished installing Nvflash but where are my files?
What files should I have?
Nvflash recovery and going back to ICS for a fresh start.
What is blobunpack?
Caution
Caution
There were no dates for the following information.
When failing to get into APX mode you can try the following suggestions.
Caution
Full brick recovery
Caution
Good Luck!
Click to expand...
Click to collapse
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?

graphdarnell said:
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
Click to expand...
Click to collapse
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.

tobdaryl said:
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
Click to expand...
Click to collapse
Not really. I didn't touch it. I'll do it again today to see. Thanks for the reply.

No recovery
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike

waynestatemac said:
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
Click to expand...
Click to collapse
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.

tobdaryl said:
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
Click to expand...
Click to collapse
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike

waynestatemac said:
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
Click to expand...
Click to collapse
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.

tobdaryl said:
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
Click to expand...
Click to collapse
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike

waynestatemac said:
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
Click to expand...
Click to collapse
The first thing you flash in this guide is the bootloader. nvflash --resume --download 4 blob.EBT
With nvflash you can flash only what is needed for your situation. If you feel the problem is the bootloader you can flash just that and try again.
What you describe sounds like stock recovery is still working on your tablet. If flashing the bootloader does not help I would use stock 9.4.3.30, unzip once and place the remaining zip on your internal sdcard. You may get an update notification. Accept it and let your tablet do the work. If you don't get the notification reboot your tablet and you should see it then. Doing this will write stock bootloader, recovery, etc.
Stock recovery is the blob.SOS when you blobunpack. Just use the stock 9.4.3.30 blob and use the resulting SOS (recovery.img).

TF300T Bricked accessible using APX Mode.
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany

NaderALDirany said:
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
Click to expand...
Click to collapse
I have read your previous posts in addition to this one.
There are four vehicles to restore your tablet. (some things can be done within android but you have no access)
1. recovery - stock or twrp
2. fastboot
3. adb
4. nvflash
I notice you also posted in my guide for accessing adb, fastboot, and apx. You were unable to access fastboot, adb, or recovery with those methods.
I don't know of any way to recover through apx without nvflash previously installed and you have no access to the other three methods.

Needs Stickied ... thanks man you helped save my butt :good:

Trigger911 said:
Needs Stickied ... thanks man you helped save my butt :good:
Click to expand...
Click to collapse
Thanks! *I'm glad you found the info useful.

[Help] I cannot get my zenfone 2 into recovery mode.

I've tried everything I could find with a google search but I haven't found anybody with a similar problem. I cannot boot into recovery mode as every time I select recovery mode I get sent back to the fastboot screen. I can use normal boot and my phone starts up fine but choosing recovery mode just brings me through an endless loop of going to the fastboot screen. Anybody know a way around this?

turdcannon said:
I've tried everything I could find with a google search but I haven't found anybody with a similar problem. I cannot boot into recovery mode as every time I select recovery mode I get sent back to the fastboot screen. I can use normal boot and my phone starts up fine but choosing recovery mode just brings me through an endless loop of going to the fastboot screen. Anybody know a way around this?
Click to expand...
Click to collapse
Tried adb?
Please press the thanks button if I helped you.
Sent from my C2305 using Tapatalk

turdcannon said:
I've tried everything I could find with a google search but I haven't found anybody with a similar problem. I cannot boot into recovery mode as every time I select recovery mode I get sent back to the fastboot screen. I can use normal boot and my phone starts up fine but choosing recovery mode just brings me through an endless loop of going to the fastboot screen. Anybody know a way around this?
Click to expand...
Click to collapse
It usually occurs simply because it cannot boot into recovery. This may be due to accidentally wiping the recovery partition, thus having no recovery to boot to at all, or that you flashed an incompatible recovery onto your device.
Fret not, just a few simple commands should get your phone back alive and kicking.
First, download the recovery.img (ZE550KL) at https://drive.google.com/open?id=0B6QXDUz9wzc9bUZaOHJsTzBhcVk
Then, boot your device into recovery mode.
Once done, type the command, in order,
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Do take note that you would need to have ADB tools installed, a reliable connection to your computer, ASUS drivers in order for your device to be detected, and some knowledge on where to place the recovery.img in order for the commands above to work. If you need any help, please feel free to ask. Also, since you did not state the variant of your device, I had put the ZE550KL recovery.img instead. If your device is of another variant, please inform me immediately and I will get the recovery.img up for you.

Rizzed said:
It usually occurs simply because it cannot boot into recovery. This may be due to accidentally wiping the recovery partition, thus having no recovery to boot to at all, or that you flashed an incompatible recovery onto your device.
Fret not, just a few simple commands should get your phone back alive and kicking.
First, download the recovery.img (ZE550KL) at
Then, boot your device into recovery mode.
Once done, type the command, in order,
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Do take note that you would need to have ADB tools installed, a reliable connection to your computer, ASUS drivers in order for your device to be detected, and some knowledge on where to place the recovery.img in order for the commands above to work. If you need any help, please feel free to ask. Also, since you did not state the variant of your device, I had put the ZE550KL recovery.img instead. If your device is of another variant, please inform me immediately and I will get the recovery.img up for you.
Click to expand...
Click to collapse
Thanks so much, this worked. I have a ze551ML but I had a stock recovery already on my drive. I've been trying to install the twrp recovery for the last two days but have been completely unable. Although the "fastboot oem reboot-recovery" failed as adb didn't recognize the OEM remote. Any idea why the most up to date twrp recovery has not worked in the least?

turdcannon said:
Thanks so much, this worked. I have a ze551ML but I had a stock recovery already on my drive. I've been trying to install the twrp recovery for the last two days but have been completely unable. Although the "fastboot oem reboot-recovery" failed as adb didn't recognize the OEM remote. Any idea why the most up to date twrp recovery has not worked in the least?
Click to expand...
Click to collapse
You need to unlock the bootloader first. There are plenty of guides online about how to do this, unofficial and officially. Also, there's a dedicated forum for your device variant, named "ASUS ZenFone 2"
This forum here is for the Laser variants.
Sent from my ASUS_Z00LD using XDA-Developers mobile app

Reboot loop, can't access Recovery

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?????

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?

forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?

videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.

WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work

sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?

zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.

Stuck twrp says no os installed . But i did learn how to push files.

just trying to get back to stock now 

videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .

Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.

thanks everyone.

videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.

I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help

This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much

avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical

videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks

avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.

Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks

avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.