Related
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
GedBlake said:
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hi guys, I actually encountered this problem a minute ago when I attempt to flash a new version of TWRP recovery on my grouper. Whenever I go to the recovery, it just shows 'No command' with a red alert of Android on it (I started to panic when I found that there's an unusual error that prevents me from entering the recovery and this is the first time that I saw this error on my flashaholic experience *btw my previous recovery was CWM) I'm currently on stock 4.4.2 with an unlocked bootloader. I have no idea what problem is causing to display that issue when attempting to enter recovery but then I left it for like 5-10mins while it's displaying that error and after that the device reboots then it just quickly enter TWRP recovery normally as is :silly: sick of that haha, silly ol grouper jesus -_-
EDIT
After entering recovery, I got stuck forever on bootloader and recovery! whenever I reboot, I always get directly enter to the recovery and it forces me to not to enter the ROM oh my god at least I can still configure the recovery so I can backup and flash another ROM :|
Hi guys...
So my OnePlus 2 was having some issues yesterday, and I flashed the stock ROM. This was completely fine and dandy, but I also wanted to put the stock recovery on it. I made sure OEM unlocking was on, went into fastboot, and typed in "fastboot oem unlock" like normal. It finished in like a tenth of a second which I thought was a little strange. The phone rebooted and I put it back into fastboot. I tried to flash the recovery and it said (remote device is locked. Cannot flash images). So at this point I was frustrated. I went into TWRP and installed the SuperSU binary. Then, I went to the Play Store, downloaded Flashify, and flashed the recovery onto my phone. I restarted my phone.... and bam. Recovery wouldn't work anymore. And then when I tried to boot into normal Android it still wouldn't work, just stuck on the OnePlus and Android screen, as if there was no /system/ partition. I can still get it into Fastboot, and I put it in EDL mode and installed the Qualcomm 9008 driver, and flashed OxygenOS 3.0.2 through the MSM downloader from https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ and the MSM downloader just gave me an error that, in garbage text, said something about Sahara and Firehouse or something like that. I did get it to go successfully by downloading a different recovery package (I believe it was Color OS 2.0) but I have a ONE A2005 and I belive that was meant for ONE A2001 and it caused my phone to constantly flash rapidly at the Oneplus and Android screen (it would start to boot then immediately shut off). Fastboot still works but it still says the bootloader is locked so I can't really do anything. Any help would be much appreciated!
Jack
Update: I finally got Recovery to work. However, it still gets stuck on the OnePlus & Android screen, even after sideloading a stock ROM and installing it via the stock recovery. I fear my boot.img is corrupted. Does anyone happen to know where I can find a stock ROM that comes with recovery.img, boot.img, system.img, et cetera?
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
superblox02 said:
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
Click to expand...
Click to collapse
You should be able to unlock it in fastboot or adb
OEM unlock or something like that
Check this thread https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.
I would really appreciate some help recovering my device without resorting to MSM and having to wipe everything.
I accidentally ran "fastboot flash boot twrp.img" instead of flash recovery...yeah.
Now I've lost access to the bootloader, to the recovery and to my (stock) rom. I've held volup+power and it reboots but it cannot ever pass the "boot loader is unlocked blahblah integrity" page.
I've tried volup+voldown+power to no avail.
I can't seem to even shut the device off, it's always stuck on on that bootloader warning page.
Normally I would just boot into fastboot and flash the correct boot.img but since I can't even access fastboot now, I'm a little stuck.
Any help would be massively appreciated, thank you.
EDIT: It miraculously booted into fastboot on its own, from there I flashed the latest boot.img, used fastboot to boot into the latest twrp, flashed magisk zip and booted back into the system as normal.
try this tool to flash stock boot img.
Apcoolboy said:
try this tool to flash stock boot img.
Click to expand...
Click to collapse
Thanks for the reponse but this tool does not/cannot work because I cannot access the bootloader, as I mentioned. I can't access any aspect of the device whatsoever aside from the "bootloader is unlocked.." warning page.
it seems your soft brick phone can only revive after flashing stock boot. And as you mentioned you cant get into bootloader then only option is MSM. Also you mentioned that your phone can't switch off, try draining battery to zero and then volume down-power on it. Check this guy's phone boot to twrp after draining phone battery.
Apcoolboy said:
it seems your soft brick phone can only revive after flashing stock boot. And as you mentioned you cant get into bootloader then only option is MSM. Also you mentioned that your phone can't switch off, try draining battery to zero and then volume down-power on it. Check this guy's phone boot to twrp after draining phone battery.
Click to expand...
Click to collapse
I'll try draining the battery and report back afterwards. Thank you very much for your help so far.
EDIT: It miraculously booted into fastboot on its own, from there I flashed the latest boot.img, used fastboot to boot into the latest twrp, flashed magisk zip and booted back into the system as normal.
3dawg said:
I'll try draining the battery and report back afterwards. Thank you very much for your help so far.
EDIT: It miraculously booted into fastboot on its own, from there I flashed the latest boot.img, used fastboot to boot into the latest twrp, flashed magisk zip and booted back into the system as normal.
Click to expand...
Click to collapse
So is it after draining whole battery or just randomly booted into fastboot?. Glad your phone data survived.
my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
You tried stock images. Does that include factory images? That erases and reflashes quite literally everything (bootloader, recovery, system, etc.)
Find them here for 6P: https://developers.google.com/android/images#angler
Santhosh Jangamgari said:
my nexus 6p is not booting into rom, recovery (stock and custom).
i have a unlocked bootloader, flashed custom recovery(twrp) by fastboot but can't get in to twrp as i wanted to flash blod patch to use 4cores to work.
i tried flashing stock images of MM, Nougat, Oreo using platform tools by google but getting an error like see in the attachment:crying:.
i tried it with fastboot by manually entering commands it will flash but not use still bootlooping.
i tried toolkits like NRT & all in one toolkit by XDA member this toolkits can flash stock rom successfully but cant get boot into system, stock recovery.
help me with your answers. my status is "unlocked bootloader, fastboot working, can access bootloader but can't get into recovery from it".
getting couldn't parse partition size 0x when booting boot img through platform tools.
tell me if i did any mistake. Thank you.
Click to expand...
Click to collapse
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Lughnasadh said:
You didn't mention which custom recovery you flashed. Did you try the one in this thread? https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/
If you did and you still can't get into it, your device is likely dead from the BLOD. But to make sure you have the BLOD, flash the latest factory image first (Dec. 2018) with the latest platform tools to see if it boots... https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Santhosh Jangamgari said:
firstly i already cant boot into stock recovery from my bootloader i'm on stock os 8.1.
and now i've flashed twrp for angler from twrp website but cant boot into custom recovery too.
now i've flashed twrp image of 4cores but still can't get into recovery.
so what's the problem of this phone if my mobile cant get even into twrp i can't do blod patch if we think my device is suffering from blod issue.
do you think it may be the problem of hardware like ram,emmc, or the SD 810?
Click to expand...
Click to collapse
As I said in my previous post, if you can't boot into the 4core custom recovery, your device is likely dead because of the BLOD, unfortunately. If you are on stock with nothing else on your phone that might be preventing you from booting (e.g. mods, Substratum overlays, etc.) there's not much else you can do.
Is your device recognized in fastboot?
marianodelfino said:
Is your device recognized in fastboot?
Click to expand...
Click to collapse
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
DaKoin said:
Hi, I am havin same problem as the user above....I am on stock 7.1.2 right now. Unable to boot into TWRP, i flashed twrp-3.2.1-0-fbe-4core-angler.img and then entered recovery from bootloader screen. nothing! i also tried to do a temporary boot to my recovery via fastboot command. didn't work! I dont think my phone is that dead...but I don't see why it isnt booting into twrp...i did the flash all of stock firmware from the Google website. Any assistance? Currently I have a Pixel 2 thats not working, so i thought I would try to revive the 6P, but no luck so far.
Click to expand...
Click to collapse
thanks but no assistance required as i have sold it to another nexus 6p user for using it's spare parts.