Database Users

Bootloop Nexus 4 - Broken Stock Recovery - Bootloader won't unlock

I made sure the drivers are google drivers. I have done this before millions of times.
I swapped cables.
I tried everything.
I always get an OKAY, but no erases. I read that new Android Bootloaders need stock recovery to erase the data and other partitions after an oem unlock, in order to complete successfully.
Only issue is, stock recovery is broken with a red triangle and a dead android robot.
Bootloader version is MAKOZ30f.
'fastboot oem unlock' results in OKAY (as mentioned earlier) then I reboot boot loader and get it back on locked status again! Like NOTHING ever happened.
Is Debugging enabled? No. Because it was fully stock before this (friend's phone). Is that the issue? If so? How can I fix it when I can't get into recovery or even the system!
Hmm... What else?
That's mostly it.
I've tried NRT with no luck. It booted a modified boot.img and attempted to flash stock recovery 5.1.1 to no avail. The phone rebooted back into a bootloop, I shortly saw the unlocked white lock with the Google logo splash, but that was it then bootloooooop.
I have a fair bit of experience with android devices over the years. I am not a newbie, so I do have an intermediate level of knowledge with rooting, recoveries, Custom ROMs and the like.
Thank you guys in advance, I hope this is solvable! Because this is the first bootloop device that has actually gotten to me!
Tl;dr: Nexus 4 stuck in a bootloop. Recovery is broken (red triangle). Bootloader will not unlock (resets to 'locked' after bootloader reboot). Restarting after a bootloader unlock attempts just results in system bootloop again.
Help is gravely needed.

andezzat said:
I made sure the drivers are google drivers. I have done this before millions of times.
I swapped cables.
I tried everything.
I always get an OKAY, but no erases. I read that new Android Bootloaders need stock recovery to erase the data and other partitions after an oem unlock, in order to complete successfully.
Only issue is, stock recovery is broken with a red triangle and a dead android robot.
Bootloader version is MAKOZ30f.
'fastboot oem unlock' results in OKAY (as mentioned earlier) then I reboot boot loader and get it back on locked status again! Like NOTHING ever happened.
Is Debugging enabled? No. Because it was fully stock before this (friend's phone). Is that the issue? If so? How can I fix it when I can't get into recovery or even the system!
Hmm... What else?
That's mostly it.
I've tried NRT with no luck. It booted a modified boot.img and attempted to flash stock recovery 5.1.1 to no avail. The phone rebooted back into a bootloop, I shortly saw the unlocked white lock with the Google logo splash, but that was it then bootloooooop.
I have a fair bit of experience with android devices over the years. I am not a newbie, so I do have an intermediate level of knowledge with rooting, recoveries, Custom ROMs and the like.
Thank you guys in advance, I hope this is solvable! Because this is the first bootloop device that has actually gotten to me!
Tl;dr: Nexus 4 stuck in a bootloop. Recovery is broken (red triangle). Bootloader will not unlock (resets to 'locked' after bootloader reboot). Restarting after a bootloader unlock attempts just results in system bootloop again.
Help is gravely needed.
Click to expand...
Click to collapse
Stock recovery will give you the laying down Android with a red exclamation, once it times out press PWR+VOL UP to get to the recovery menu.
The bootloader probably won't unlock because it can't wipe (a requirement with the fastboot command), or it is locked in the Security settings of the latest stock image. Beginning with Lollipoop, if you are locked you have to tell Android it can be unlocked before doing it, it is a security measure.
You will need to reflash the full stock image, if NRT is failing do it manually, and do it from Linux if possible (no driver issues like Windows), you can get the images here: https://developers.google.com/android/nexus/images
And remember, first boot on Lollipop on the N4 can take 10-15 minutes or more well caches are being built and the OS is settings up (easily 5 times longer than a boot on KitKat), give it time, unless it restarts (a true bootloop) just let it sit. Patience is a real virtue here...
Note, you could have a corrupt or defective flash RAM chip, if that is the case, a full factory flash -MAY- fix it, but no guarantee... If the flash ram is bad, they you might be SOL.

Oh my god. Thank you so much. I am so stupid. I thought stock recovery is broken. But it's not. That's the normal way it should display. And you are right. Holding power then tapping vol up will show the menu
I am such a fool, I've always used custom recoveries, and forgot totally how stock recoveries work ^_^
I am now trying an adb sideload (the factory reset from recovery isn't working, lots of errors).
Gonna try a couple things.
And no I can't flash the images, cause I need to unlock the bootloader (if done through fastboot). Which is my main issue.
Hoping sideload really works!
BUT THANK YOU AGAIN SO MUCH ^_^

Okay. Now I am getting failure to mount /cache and stuff. Lots of problems with the cache partition.
I attempted 2 factory resets. I am now restarting and will report on how it goes. Gonna let the phone take its sweet sweet time booting.
If nothing else works, it really might be a hardware defect, and I really might be SOL @acejavelin
*sigh*
Oh well, all phones come to an end :/

Oh and great work Google on your 'extra precaution' with the whole bootloader unlock thing. Really? Nexuses/Nexii were MADE to be easily unlock-able. If this wasn't a problem... I might have actually been able to format the /cache/ partition, or try something with custom recovery that'd fix this phone quickly. *sigh*

andezzat said:
And no I can't flash the images, cause I need to unlock the bootloader (if done through fastboot). Which is my main issue.
Hoping sideload really works!
BUT THANK YOU AGAIN SO MUCH ^_^
Click to expand...
Click to collapse
When you do "fastboot oem unlock" are you getting a confirmation screen on the device and selecting Yes, or does that screen never pop-up?
Also, for the cache issue, in fastboot try "fastboot format cache" instead of the erase command.
And be aware that on first boot, I have had several Nexus/GPE Lollipop devices not show the setup screen or launcher (just a blank wallpaper) even after waiting 10-15 minutes, a simple reboot and more patience usually corrects this.

I did confirm, and it says unlocked on the phone. After restarting the bootloader it goes back to locked.
Cache: not supported in locked device.
I really cannot do a thing without unlocking the bootloader
Phone is still bootlooping. I gave it lots of time *sigh*

andezzat said:
I did confirm, and it says unlocked on the phone. After restarting the bootloader it goes back to locked.
Cache: not supported in locked device.
I really cannot do a thing without unlocking the bootloader
Phone is still bootlooping. I gave it lots of time *sigh*
Click to expand...
Click to collapse
I forget if unlocking the bootloader forces a reboot or not... If it doesn't, unlock and without rebooting try formatting cache or "fastboot boot recovery.img"" of latest twrp image.
Sent from my Nexus 4 using Tapatalk

That usually just says the device is locked, and that cannot be done on a locked device.
No it doesn't force a reboot!
I will try formatting cache partition again directly after unlocking bootloader (at least attempting). I'll report back if anything is successful.
I've tried flashing recovery as well, but just says cannot do while phone is locked. Will also try again.
Thank you for your help. I appreciate it.

acejavelin said:
I forget if unlocking the bootloader forces a reboot or not... If it doesn't, unlock and without rebooting try formatting cache or "fastboot boot recovery.img"" of latest twrp image.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

andezzat said:
Click to expand...
Click to collapse
After you unlock, do NOT try to FLASH recovery, try to boot it...
fastboot boot <path\recovery.img>
If the bootloader is unlocked, you should be able to push the recovery image over and boot it (not flash it), this will run a temporary copy that you can use to try to format the cache partitions, it doesn't write to the flash partitions to boot it, it all happens in RAM, so even if the flash is corrupt, you -MIGHT- be able to get TWRP loaded and format things to get them working again.
But to be honest, if you can't write recovery, or any other partition (or so it appears), this one might be done... but I don't stick a fork in it until there is nothing more to try.

I didn't notice the boot it part. Okay I am in TWRP now. I can't wipe cache. It is unable to mount cache, data usb-otg, and storage.
Where do I go to format not wipe?

Sideload gives me error: protocol fault (no status).

andezzat said:
I didn't notice the boot it part. Okay I am in TWRP now. I can't wipe cache. It is unable to mount cache, data usb-otg, and storage.
Where do I go to format not wipe?
Click to expand...
Click to collapse
Wipe in TWRP formats, except internal storage and data since internal storage is actually /data/media.
This is bad, if you can't mount cache or internal storage, your flash ram is likely bad.
andezzat said:
Sideload gives me error: protocol fault (no status).
Click to expand...
Click to collapse
Most likely you need a newer adb to use sideload in TWRP... There is a minimum revision of adb required, version 1.0.32 or higher.
Sent from my Nexus 4 using Tapatalk

That was useful! I got adb 1.0.32 but now instead, I get total xfer: 0.00x
Is that it? EOL for this phone? :'(

I don't know if this will help you, OP but here goes - try selecting the partition in TWRP, changing the partition type to something else and then changing it back to ext4. See if that works.
PS: I remember that my N4 refused to boot up to system after I flashed a factory image - it only booted up to recovery which I promptly restarted. Turns out you have to wait till the recovery reboots itself.

Nothing is working right now. I tried changing formats and everything. It's just unable to mount any of the partitions. And now they're all stuck on 0mb size.

I have an otg usb. It won't even detect or mount it at all. I can't even choose it instead of internal storage. This phone is beyond gone :/

I get constant ERROR=8 from e2fsck whenever I try to resize or repair. Probably has something to do with the phone not being REALLY unlocked.

I'm starting to wonder if this might be a corrupt image of your radio or the bootloader... Flashing it (if it's possible) might be risky in your situation but at this point in time I don't know if you can do much else than try.

Help help help with a hard bricked 6P

Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?

Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..

At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.

leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.

Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/

Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.

Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..

leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this

Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen

You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.

leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through

edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.

Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM

i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?

leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?

edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive

so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/

edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.

blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.

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

Do you know how recovery essential phone from the corrupt?

After several steps after installed twrp, now my essential phone is like these:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Chiminwon said:
After several steps after installed twrp, now my essential phone is like these:
Click to expand...
Click to collapse
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you

@mouraj2 have you done both commands:
Fastboot flashing unlock
Fastboot flashing unlock critical
---both are needed
Also, I'd recommend getting the current build for your ph-1 from here on xda or essential. Find the firmware you need/want and flash the BTS (back to stock) flash-all.bat. That flashes from fastboot lol. Don't download the OTA get the images file. Easier.
I don't know much about modding phones in general but i can work my way around a ph-1 for sure lol. PM me if u have any more questions

KingBeefy said:
@mouraj2 have you done both commands:
Fastboot flashing unlock
Fastboot flashing unlock critical
---both are needed
Also, I'd recommend getting the current build for your ph-1 from here on xda or essential. Find the firmware you need/want and flash the BTS (back to stock) flash-all.bat. That flashes from fastboot lol. Don't download the OTA get the images file. Easier.
I don't know much about modding phones in general but i can work my way around a ph-1 for sure lol. PM me if u have any more questions
Click to expand...
Click to collapse
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s

mouraj2 said:
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
You need to boot the phone and get into developer mode.
You will need to go into settings, about and tap the build 7 times.
Then go into developer settings and enable boot loader unlock.

tech_head said:
You need to boot the phone and get into developer mode.
You will need to go into settings, about and tap the build 7 times.
Then go into developer settings and enable boot loader unlock.
Click to expand...
Click to collapse
I can not phone stuck on the logo
It does not go into recovery also attached to the logo

mouraj2 said:
The bootloader does not open
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: -0.000s
Click to expand...
Click to collapse
Go to the essential website and download the latest windows drivers for the PH-1. It's not communicating with the phone. When you type the command "fastboot devices" it is probably not showing any connection to the device , right ?

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
mouraj2 said:
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you
Click to expand...
Click to collapse
The computer knows the phone in fastboot mode Shaper that the bootloader is closed and did not accept the opening and did not accept the update There is no way to cancel the update from the fastboot commands to complete the update

KingBeefy said:
Could you rephrase what your question is? I would like to help but can't figure out what you are explaining. I'm assuming you have unlocked the bootloader. I had some problems with this phone at first too. Most of the problems when compared to other phones is that Essential Phone has 2 partitions, like the Pixel. For simplicity, one is sort of the ACTIVE side and the other INACTIVE side. It has some learning. If you are just trying to get up and running try these steps...
1- Wipe data using fastboot command fastboot -w ---- locate the Stock ROM section in Essentials forum here on XDA and get the current STOCK build for your needs. Download it. And flash it in fastboot using the flash-all.bat file. Most will flash the files to both partitions, if it does not use the command in the next step to switch partitions and flash the other side too. This will set your phone back to stock and it should boot nicely. If you wish to root then proceed. BOOT INTO THE STOCK OS EVEN IF YOU ARE STILL GOING TO ROOT THE DEVICE. JUST BOOT UP, THEN REBOOT TO THE BOOTLOADER. DONT SIGN INTO YOUR GOOGLE AND DO NOT SET LOCK OR PASSWORD OR FINGERPRINT YET
2- Follow step one and then reboot into fastboot and use command fastboot set_active other --------- this will do two things. It will switch your partition and also tell you which one it switched to. There is an A side and a B sideFOR THIS EXAMPLE WE WILL PRETEND THAT AFTERYOU SWITCHED YOU ARE ON SIDE B
3- Stay in fastboot and flash twrp11mata using fastboot command fastboot flash boot exactTWRPfilename.img ------ this will boot you into TWRP on the B side
This next rule is very importantTWRP flashes a zip and a img file different. ZIP ROM FILES FLASH TO THE OPPOSITE PARTITION, IMG FILES flash to the partition that you are currently using. So, if you booted into TWRP on the "b" side and without switching flashed a new kernel or boot image it would install to the same "b" side you are on. If you did the same with a ROM it would install to the 'a" side. So, at some point you have to switch sides from within TWRP in the Reboot tab.
4- Copy your Roms/files to your phones internal memory and then flash using twrp. Flash the ROM not sideload. Flashing is for new roms, sideload is for updates to existing ROM. Back to our example, you booted into TWRP on side b, if you install new rom it will install on side A. Lets keep that idea going for the example. BE AWARE THAT IN THIS TYPE OF DEVICE, using our example where we flashed the rom to the A side (from TWRP on the B side), that side will not have TWRP. It will have stock recovery.
5- once the rom is flashed reboot system. (wipe cache / dont wipe cache.. I havent noticed a difference with either mindset) It will switch your partitions upon reboot if you don't do anything else in twrp.
So for our example this is what happened:
Wiped data from both partitions of the PH-1, side "a" and side "b"
Went BACK-TO-STOCK on BOTH sides
BOOTED INTO STOCK ROM ON THE SIDE WE WISH TO BE OUR ACTIVE SIDE***DID NOT SET UP GOOGLE OR PIN/FINGERPRINT/PASSCODE****
reboot into bootloader
Used Fastboot to switch partitions and installed TWRP to the INACTIVE side. Boot into twrp.
In TWRP, copied new files to phone storage the flashed new ROM Remember it will install it to the other side which is our ACTIVE side
reboot system.
If this helped at all and got you running great. Rooting is simple from here. This phone was the first device I ever rooted so I took my lumps so I hope I offered some tips that I didn't find or understand fully at first. Happy exploring. Ask away if I can help further.
Click to expand...
Click to collapse
Hi King,
I am hoping you can help. I never enabled USB debugging. I did wipe the phone but cannot run any ADB commands, only fastboot commands. The phone will not run recovery and I'm really hoping I can get some help to recover this phone. Essential won't help as the phone is off warranty. I was able to unlock the phone but cannot seem to load anything via Fastboot as the phone won't allow loading due to the USB debugging not being enabled. I was hoping for a way to enable it via Fastboot.
Thanks,
Grant

mouraj2 said:
Hello
I have an essential ph1 phone I bought new from a friend
I registered my google account and secured the phone with a fingerprint
While the update request protection orio8.1 agreed to download and update
Complete the phone Download the update The installation process then stuck a logo ,,
Now the phone is working on fastboot mode only
I can not log into recovery
bootloader lock
oem lock
usb debogen lock
I could not flash any picture ....
I hope anyone who can help me help me solve the problem and thank you
Click to expand...
Click to collapse
I have the same problem here,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cant flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you

You are both out of luck. I don't know what everyone is thinking by telling you to do all the normal instructions to fix your phones when you plainly say that you get a CORRUPT red warning a boot and at recovery, and you never OEM unlocked your phones to be able to unlock the boot-loader. So I am sorry to tell you this but your phones are garbage. I have the same red corrupt warning at boot and recovery just goes to boot-loader, but I DID unlock my boot-loader, so I am going to erase my critical partitions and flash them on both slots to see if that works. Funny thing, I finally figured out a way to boot into the OS... I just boot and when the red corrupt warning comes on I press the volume buttons randomly and hold them down randomly and at some odd point it just boots up. So weird, it is definitely a bad flash that didn't stick or the image was corrupt, or maybe the image was modded incorrectly. I flashed a patched boot image and that's when the red corrupt warning came up. I am not saying it was the patched boot file, I might have flashed it wrong, like over an already patched boot, which I read is a no no. But now I wonder....should I erase the critical partitions and flashall? And does that "erase" command wipe the partition's data or the partition as a whole??? Or, should I try formatting the critical partitions instead? Anyone know what the correct course of action is here? Or even just what is the BEST one is??? I was lucky to get into the OS because I lost USB debug when I flashed the latest security update trying to fix this. Also, I burned through a data cable somehow too. SMH. OK, Please advise me as to what I should do so that I don't Essentially end up using this phone as part of my chimney. TYIA!
---------- Post added at 03:40 PM ---------- Previous post was at 03:35 PM ----------
A.I.M said:
I have the same problem here,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cant flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
Click to expand...
Click to collapse
OEM locked is unchecked and you have no access to it? Thats a brick. Unless you can get an ADB connection while your phone bootloops.
SOMEtimes I could get in before my phone booted but highly unlikely.

Help Installing/Booting TWRP on Oreo

Using the 2017 Shield I am not able to fastboot boot twrp.img, when attempting to do so (using 3.0.2, 3.1.1, 3.2) it results in a momentary Nivida logo, then the display output stops, requiring a hard reboot.
I am able to fastboot flash recovery and boot into TWRP but once I've done this it causes a boot freeze, displaying the Nivida logo indefinitely.
I feel certain there is something I've missed, I've had this same experience on two Shield units so far.

w0rdie said:
Using the 2017 Shield I am not able to fastboot boot twrp.img, when attempting to do so (using 3.0.2, 3.1.1, 3.2) it results in a momentary Nivida logo, then the display output stops, requiring a hard reboot.
I am able to fastboot flash recovery and boot into TWRP but once I've done this it causes a boot freeze, displaying the Nivida logo indefinitely.
I feel certain there is something I've missed, I've had this same experience on two Shield units so far.
Click to expand...
Click to collapse
are you on a 4k tv, if so that is your problem twrp for the shield will not show on 4k

jionny said:
are you on a 4k tv, if so that is your problem twrp for the shield will not show on 4k
Click to expand...
Click to collapse

I had the same issues, tried different monitors (non 4K), gave up and used magisk for root. I use flashfire for backups and flashing zips. Installed xposed through magisk. I don't think i have a need for TWRP after all the bootloops and issues. I had to reflash the stock image everytime to get it to boot. I am running version 7.0.2.

Did you make sure to install the Nvidia Family Drivers for ADB. I had to uninstall ADB Composite Device and also delete driver files. I then rescanned after plugging back into PC, it was listed as ADB Composite under USB devices. Updated the driver with the Nvidia Family Driver. Haven't had an issue since.

Michajin said:
I had the same issues, tried different monitors (non 4K), gave up and used magisk for root. I use flashfire for backups and flashing zips. Installed xposed through magisk. I don't think i have a need for TWRP after all the bootloops and issues. I had to reflash the stock image everytime to get it to boot. I am running version 7.0.2.
Click to expand...
Click to collapse
I'll have to look into flashfire, as I've seen the same suggestion pop up elsewhere. Any tips on how to install Magisk on the Shield? I've attempted several times with as many methods I could find through several threads, and they've all failed in one way or another. Did you have to use a specific version of Magisk?
Also, I currently have TWRP flashed on my Shield. I've been reading that the new Oreo doesn't play nicely with TWRP and may be prone to bricking and bootloops. I eventually want to upgrade mostly to prevent the nag screen. Is there a way to install the stock bootloader without wiping the device and flashing the stock image?

thekwijibo said:
I'll have to look into flashfire, as I've seen the same suggestion pop up elsewhere. Any tips on how to install Magisk on the Shield? I've attempted several times with as many methods I could find through several threads, and they've all failed in one way or another. Did you have to use a specific version of Magisk?
Also, I currently have TWRP flashed on my Shield. I've been reading that the new Oreo doesn't play nicely with TWRP and may be prone to bricking and bootloops. I eventually want to upgrade mostly to prevent the nag screen. Is there a way to install the stock bootloader without wiping the device and flashing the stock image?
Click to expand...
Click to collapse
If i am understanding you, you are on Nougat and want to go on to Oreo? I have Magisk on Oreo.
I am on Oreo but i couldn't get TWRP to work. You could flash back to stock recovery; (download stock image from NVidia whatever version you are on)
fastboot flash recovery recovery.img
Use the recovery.img from the stock image that matches your current OS
I took the boot.img from the stock OS image put it in a location on my sheild i could access from file manager then patched it with magisk (latest version), then flashed it from fastboot
fastboot flash boot boot.img
"boot.img" being the one you patched with magisk.
None of this should wipe anything unless you unlock/lock the bootloader.

Michajin said:
If i am understanding you, you are on Nougat and want to go on to Oreo? I have Magisk on Oreo.
I am on Oreo but i couldn't get TWRP to work. You could flash back to stock recovery; (download stock image from NVidia whatever version you are on)
fastboot flash recovery recovery.img
Use the recovery.img from the stock image that matches your current OS
I took the boot.img from the stock OS image put it in a location on my sheild i could access from file manager then patched it with magisk (latest version), then flashed it from fastboot
fastboot flash boot boot.img
"boot.img" being the one you patched with magisk.
None of this should wipe anything unless you unlock/lock the bootloader.
Click to expand...
Click to collapse
Awesome. Thanks for the clarification. It worked, I flashed the recovery.img and I was able to install the OTA update.
I was able to use Magisk to patch the boot.img, however when I used fastboot to flash it to the shield, it didn't seem to do anything. I tried again with no improved results. I tried flashing the super.su zip that had worked for me before, and I ran into some bootloops, but was able to get things somewhat working again. I decided to scrap it, and try to flash the whole enchilada from the Nvidia image.
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and..... brick. oops.
I was able to pull the power, plug in a keyboard, hold down A&B and managed to get into fastboot. Yay!
I suspected I might have skipped a step in there or rebooted prematurely, so I tried the process again.
This time I got the yellow bootloader warning, followed by the red system corrupt warning. I thought I had screwed it up, but after a few moments it finished booting. So, it "works", but takes a bit longer to boot due to the additional red warning screen.
Any suggestions on where I should go from here? I feel like I'm walking on thin ice with this additional red warning screen on boot.

thekwijibo said:
Awesome. Thanks for the clarification. It worked, I flashed the recovery.img and I was able to install the OTA update.
I was able to use Magisk to patch the boot.img, however when I used fastboot to flash it to the shield, it didn't seem to do anything. I tried again with no improved results. I tried flashing the super.su zip that had worked for me before, and I ran into some bootloops, but was able to get things somewhat working again. I decided to scrap it, and try to flash the whole enchilada from the Nvidia image.
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and..... brick. oops.
I was able to pull the power, plug in a keyboard, hold down A&B and managed to get into fastboot. Yay!
I suspected I might have skipped a step in there or rebooted prematurely, so I tried the process again.
This time I got the yellow bootloader warning, followed by the red system corrupt warning. I thought I had screwed it up, but after a few moments it finished booting. So, it "works", but takes a bit longer to boot due to the additional red warning screen.
Any suggestions on where I should go from here? I feel like I'm walking on thin ice with this additional red warning screen on boot.
Click to expand...
Click to collapse
From magisk check root at that point, i didn't notice any difference until i open magisk and install the manager. I used the developer image from NVidia, flashed the 7.0.2 version then did the boot.img for magisk. The red warning screen? that the bootloader unlocked warning? If always used the flash-all.bat file so i didn't have to go line by line. I thought it would work either way, but maybe there is something more to the developers image i missed.

After I booted the magisk patched boot.img, the magisk application wouldn't load. It would just go to the splash screen with the logo image, and remain there indefinitely. I waited about 10 minutes, then FC it. Thereafter I couldn't even open the app until I rebooted, in which it would hang on the splash screen yet again. I tried to use apps that require root, and all apps indicated that I didn't have root. Oh well. I've had nothing but trouble with magisk on my shield, but it works flawlessly on all my other android devices. I'll have to keep futzing with it, because several people out there have successfully done so, and I must be totally missing some critical step along the way.
As for the warning screens, when I boot there's first the yellow bootloader unlocked warning, which I'm used to. After that goes away, just a black screen, then a few moments later a red warning screen pops up saying:
"Your device is corrupt. It can't be trusted and may not work properly".... yadda yadda yadda.
This stays on for a while, and at first I might have prematurely assumed I bricked my device, but it eventually boots. It takes about twice as long to boot now, but it eventually does.
I downloaded and flashed the developer's image from the Nvidia site as well, and followed the flashing instructions exactly as the attached documented steps indicated. Perhaps I ought to try the stock image next? If that doesn't work, I'm assuming I'll have to completely wipe and factory reset the device, then flash as stock image. The red warning corruption warning has me slightly worried, but mostly irritated that it takes my shield twice as long to boot now. (ok, maybe not twice as long, but at about 30 seconds longer)
I'm curious, where did you find the flash-all.bat? I'm wondering if there is some secret squirrel command that I neglected that wound me up in this situation. Or maybe the dual warning screens is "normal" for those using the developer image?