Is it possible to re-flash the stock bootloader? I believe mine is corrupt somehow.
It's a bit hard to explain how it's acting without actually seeing it, but it acts sporadic and barely works half the time. For example I can't reboot into the bootloader via adb, trying to power off the phone via bootloader doesn't work, and 9/10 times I try to turn my phone on it goes right to the bootloader.
Not to mention it takes ~15 seconds of holding the power button to get the phone to boot.
Installing Lineage was pretty much a brute force trial and error until it wanted to work.
Any suggestions?
Edit: Realized this is probably in the wrong forum, mod feel free to move it accordingly.
jAm-0 said:
Is it possible to re-flash the stock bootloader? I believe mine is corrupt somehow.
It's a bit hard to explain how it's acting without actually seeing it, but it acts sporadic and barely works half the time. For example I can't reboot into the bootloader via adb, trying to power off the phone via bootloader doesn't work, and 9/10 times I try to turn my phone on it goes right to the bootloader.
Not to mention it takes ~15 seconds of holding the power button to get the phone to boot.
Installing Lineage was pretty much a brute force trial and error until it wanted to work.
Any suggestions?
Edit: Realized this is probably in the wrong forum, mod feel free to move it accordingly.
Click to expand...
Click to collapse
To answer your question, yes, you can reflash the stock bootloader. To do so, in addition to unlocking your bootloader via:
Code:
fastboot flashing unlock
You also need to run the following:
Code:
fastboot flashing unlock_critical
This will allow the bootloader to be overwritten (reinstalled) when you reflash the factory images from Essential's website. The downside here is that just like conventionally unlocking your bootloader this will also wipe your data, it's unavoidable. I believe it would also require you to go back to stock before reinstalling Lineage properly, I'm not 100% sure about that one. It's possible that you may be able to get away with flashing one of the stock firmware dumps from this forum on top of Lineage (8.0B3 preferably, it you intend to return to Lineage), I'm just not sure if they contain the bootloader image, you'd have to check and see. Whatever you flash, you want to make sure it includes a file named abl.
return.of.octobot said:
To answer your question, yes, you can reflash the stock bootloader. To do so, in addition to unlocking your bootloader via:
Code:
fastboot flashing unlock
You also need to run the following:
Code:
fastboot flashing unlock_critical
This will allow the bootloader to be overwritten (reinstalled) when you reflash the factory images from Essential's website. The downside here is that just like conventionally unlocking your bootloader this will also wipe your data, it's unavoidable. I believe it would also require you to go back to stock before reinstalling Lineage properly, I'm not 100% sure about that one. It's possible that you may be able to get away with flashing one of the stock firmware dumps from this forum on top of Lineage (8.0B3 preferably, it you intend to return to Lineage), I'm just not sure if they contain the bootloader image, you'd have to check and see. Whatever you flash, you want to make sure it includes a file named abl.
Click to expand...
Click to collapse
I've fallen victim to way too many bootloops in my quest to get magisk, so I've flashed the factory images probably 10 times. I might just have a defective device.
Welp here's to not giving up and getting Magisk on lineage!!:good:
return.of.octobot said:
To answer your question, yes, you can reflash the stock bootloader. To do so, in addition to unlocking your bootloader via:
Code:
fastboot flashing unlock
You also need to run the following:
Code:
fastboot flashing unlock_critical
This will allow the bootloader to be overwritten (reinstalled) when you reflash the factory images from Essential's website. The downside here is that just like conventionally unlocking your bootloader this will also wipe your data, it's unavoidable. I believe it would also require you to go back to stock before reinstalling Lineage properly, I'm not 100% sure about that one. It's possible that you may be able to get away with flashing one of the stock firmware dumps from this forum on top of Lineage (8.0B3 preferably, it you intend to return to Lineage), I'm just not sure if they contain the bootloader image, you'd have to check and see. Whatever you flash, you want to make sure it includes a file named abl.
Click to expand...
Click to collapse
Does reinstalling the factory image from Essential reinstall the bootloader or should I still run the unlocks (even if Im already unlocked)?
jAm-0 said:
Does reinstalling the factory image from Essential reinstall the bootloader or should I still run the unlocks (even if Im already unlocked)?
Click to expand...
Click to collapse
You have to do the flashing unlock critical if you have not to flash things like bootloader, boot, and modem.
jAm-0 said:
Is it possible to re-flash the stock bootloader? I believe mine is corrupt somehow.
It's a bit hard to explain how it's acting without actually seeing it, but it acts sporadic and barely works half the time. For example I can't reboot into the bootloader via adb, trying to power off the phone via bootloader doesn't work, and 9/10 times I try to turn my phone on it goes right to the bootloader.
Not to mention it takes ~15 seconds of holding the power button to get the phone to boot.
Installing Lineage was pretty much a brute force trial and error until it wanted to work.
Any suggestions?
Edit: Realized this is probably in the wrong forum, mod feel free to move it accordingly.
Click to expand...
Click to collapse
jAm-0 said:
Does reinstalling the factory image from Essential reinstall the bootloader or should I still run the unlocks (even if Im already unlocked)?
Click to expand...
Click to collapse
If you've already unlocked your bootloader you do not need to run fastboot flashing unlock again, however you do need to run fastboot flashing unlock_critical as it is required in order to overwrite the bootloader.
return.of.octobot said:
If you've already unlocked your bootloader you do not need to run fastboot flashing unlock again, however you do need to run fastboot flashing unlock_critical as it is required in order to overwrite the bootloader.
Click to expand...
Click to collapse
Great to know, thanks for the info. Too bad my phone is hardbricked now.
Wont power on
Wont connect to pc
No fastboot
No recovery
Beautiful paper weight
Related
I am a noob at android--just putting that out there. But trying...
I just received my new nexus 7 2013. I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it, and then the plan was to root it. Something happened in the process--can't say for certain what, but at some point the tool brought up TWRP on the nexus and a file that the tool said was supposed to be there, wasn't. The end result now is that my nexus is stuck on the bootloader. None of the buttons seem to work, other than restart bootloader. Turn off DOES turn off the nexus, but then when pressed again, goes right back to the bootloader. The recovery one flashes the screen quickly, then goes back to the bootloader. The Start option makes it so the screen shows the "Google" icon indefinitely with the unlocked lock icon. I need to note that the option to get into the bootloader (power + vol up and vol down) did not work for me—the only way I was able to go into the bootloader was the power and vol down. Currently though, pressing the power button makes the nexus go directly into the bootloader.
When plugged into computer via the usb cord, windows xp currently doesn't recognize anything is plugged in, although I do have the latest USB drivers installed.
I downloaded and ran SDK and went through the various fastboot commands from within a cmd window. The fastboot devices command does bring up a device number, so it is recognized by fastboot.
Here's where others will start to shake their heads in bewilderment...in my haste to try and get this up and working and out of the endless bootloader menu, I *could* have flashed it with the nexus 7 2012 recovery image, because when using fastboot to do so, at end says something about grouper and my device says flo (although nothing changed with the nexus—as in there are no obvious changes as still in bootloader). I am aware that the official flo factory image is not yet available, although at this point, I don’t have much confidence in that doing anything.
If I open up Wugfresh’s Toolkit, I can’t do anything with it, as it says that ADB doesn’t work or something and to enable USB debugging, which I can’t do because I’m stuck on the bootloader.
I don't know where to go from here--I don't know if the device is salvageable or if it is completely toast and I should just return it and get another one...I see that in the day since I downloaded Wugfresh’s Toolkit, he has released two more versions—not sure if the new version can do anything—haven’t tried yet. Can anyone with more knowledge than myself give me a hand or some advice? Thanks in advance.
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Username invalid said:
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Click to expand...
Click to collapse
it is unlocked. I am able to use the fastboot commands to unlock and lock. it currently is unlocked.
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Username invalid said:
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Click to expand...
Click to collapse
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
busdonic said:
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
Click to expand...
Click to collapse
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Username invalid said:
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Click to expand...
Click to collapse
Yeah, I see that....not sure why I did it myself actually, cuz now that you mentioned it, does seem pretty stupid--I guess that explains why I'm here asking for advice
I'm assuming that the one click restore will work. If it doesn't, I think I found a non-official flo factory image. I think (?) if I flash that to the tablet in fastboot, that will restore it, or at least get it past either the bootloader menu or past the Google icon shown at startup.
Geodude074 said:
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
Click to expand...
Click to collapse
this worked--thanks much. Am much relieved to be up and running again....
My 6p is stuck in a bootloop. nbd90x build my bootloader is locked is there anyway to unlock from adb. I have already tried sideloading ndb90x through adb wipping chache and user data and still no luck. Help me Xda youre my only hope..
So you previously enabled USB debugging, how about OEM unlocking? If so, use 'fastboot flashing unlock' to unlock the bootloader. Note that internal storage will be completely wiped. Everything. Though with USB debugging enabled, you should be able to adb pull the contents of you SD card first. If you can unlock the bootloader you can try flashing factory images with fastboot. Otherwise, not much else besides RMA it with Google. There's been a few reports of stock N6Ps bootlooping. Haven't seen anyone post that Google denied the claim.
no bootloader is locked so cant flash using flashboot but debugging is enabled so I am able to use adb .
I know. What I'm asking is if you enabled allow OEM unlocking in developer settings? That doesn't unlock your bootloader in itself. You still need to use fastboot to do it. However if that setting IS enabled what you can do is... Use ADB to pull your internal storage to PC. Then use fastboot to unlock the bootloader and flash factory images. If the setting is not enabled, and wiping data and flashing an OTA don't work, I'm not sure what else can be done.
You can try downloading the 7.1 dev preview OTA and seeing if it updates whatever is causing it to fail. Other than those, RMA would be your best bet.
https://developer.android.com/preview/download.html#device-preview
After sideloading a ton of times between 7.0 and 7.1, one time i got it to boot up then i immediately enabled oem unlock then it crashed again... so now I am able to flash through fastboot although I havent been able to get it to boot again. Is it normal for bootloops to not get fixed by flashing?
Hijacking your post to report what is happening to me. I posted the same thing on the Android Beta program community on G+.
Have been using the latest beta since it came out on completely stock 6P (locked bootloader, unrooted). Everything working normally when yesterday around 10 or 11AM, phone starts to bootloop OUT OF NOWHERE, it was just sitting there on the table while I was working. I could still get to bootloader/recovery, so that was a bit of a relief. First thing I tried: clear cache, nothing. Then proceed to wipe/factory reset the device, to no avail. Immediately downloaded the latest factory image from Google's page, tried flashing it but couldn't since the bootloader was locked (OEM unlock option also disabled). Then downloaded the beta OTA and sideloaded it, process went through OK but device still bootloops. Tried sideloading the latest stable OTA but didn't work since it was from a previous build. Ran out of ideas. So there I was creating a thread on XDA for help while the device was still on its bootloop rush, about to hit the Submit button when again OUT OF THE BLUE SKY the device decides to boot itself back up. First thing I did was unlock the bootloader. Phone worked normally for 6 or 7 hours, when I'm doing something on it and then again, screen froze and bootloop starts again. This time I only reset the device and left the it bootlooping, after about 30 minutes it boots up again. I unenrolled from the beta and installed the latest 7.0 build. Everything working fine for the last 12 hours. Anyone have any idea on what can cause the device to bootloop like that? Never seen anything like it.
Yea I signed up for the beta program too do you have the link to unenroll? So you just reset and let it sit?
Here you go
google.com/android/beta
do you remember what you did to get it to boot?
noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
Well, that's the thing. Everything I tried didn't seem to work. I couldn't flash the factory image since the bootloader was locked. I was able to sideload the beta OTA but the device still bootlooped after that. So I just left it bootlooping and after around 20 or 30 minutes the device booted normally. I have no idea what caused it and what I did to make it work again.
P.S: device restarted 2 times while I was typing this.
noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
If your boot loader is locked you are screwed, sorry to say, I would RMA it. Unbelievable an update can mess a phone up...that's why I always unlock the bootloader first thing and never lock it. I need complete control of my phone.
Edit: Only thing I can think of is delete the partitions with fastboot or adb and reflash factory image.
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
noetre said:
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
Click to expand...
Click to collapse
As a last resort, flash all of the images manually with fastboot. This will wipe all userdata and completely format the SDcard. Nothing will be left. Extract the bootloader and radio images from the factory images zip. Flash them in fastboot. Reboot to fastboot again. Extract the next zip in the same folder as BL & radio images and flash the vendor, system, boot, recovery & userdata image files. Just for good measure, boot to recovery (stock Android recovery) and perform a factory reset & cache wipe. If the phone still fails to boot, your only option would be to RMA it at this point.
Note: As per Heisenberg's sticky thread, do NOT flash userdata.img if you have anything besides the 32gb model as you will only have the ~32gb storage available. If you're using a model with more storage, just use fastboot to format userdata but don't flash the image.
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
noetre said:
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
Click to expand...
Click to collapse
Not on a Nexus, no.
Added: I had to RMA mine after the phone got its first update. I unlocked the bootloader and stayed stock for a long time (until N came out). I took the OTA in About Phone and it applied with no problems but the phone would not boot. Factory images also couldn't get it running. Stock recovery and all. RMA'd without issues. I didn't tell them, just sent it in. If they tried to boot it they would've seen the unlock symbol. There's also a thread somewhere buried in the general section where someone called Google and asked and they confirmed to them that unlocking does not void warranty. I'll try to find it for you.
Found it: http://forum.xda-developers.com/nexus-6p/general/unlocking-bootloader-warranty-google-t3229804/page1
I also returned 4 faulty Nexus 5's (mostly screen artifacts) all unlocked with no problems.
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
RoyJ said:
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
Click to expand...
Click to collapse
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
anokmik said:
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
Click to expand...
Click to collapse
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
fapste said:
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
Click to expand...
Click to collapse
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Alsen Lea said:
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Click to expand...
Click to collapse
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
Click to expand...
Click to collapse
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Steps that I have done from stock recovery:
1. Wipe cache
2. Wipe data/ factory reset
3. Sideload 7.0 (angler-ota-nbd91k-32c2eac8) and the result is successful "script succeded: result was [1.000000]"
4. Wipe cache
5. Wipe data/ factory reset
6. Power off
7. Power on
Unfortunately boot loop persists and if I go back to recovery there is the same build version MTC20F (6.0.1).
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
Click to expand...
Click to collapse
For "fastboot oem unlock" command prompt returns "failed: remote: unknown command". I think this is because Google has changed such command to "fastboot flashing unlock", which gives me "failed: remote: oem unlock is not allowed". This because OEM unlocking hasn't been allowed from Developer Options by previous owner and now I cannot get there because of boot loop. Also have tried "flash-all.bat" from 7.0 latest factory image and on each step it returns error "failed: remote: device is locked. cannot flash images" and this is because of locked bootloader.
Possible solution?
In Stock recovery I have "Mount /system" option. Maybe someone can clarify what does it mean and could it potentially fix boot loop in some way? I have tried google for it, but unfortunately have no luck in finding information about this option.
Thanks in advance for any information!
anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
---------- Post added at 11:39 AM ---------- Previous post was at 11:29 AM ----------
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
fapste said:
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
Click to expand...
Click to collapse
Issue has star from me now. Thanks for the link!
jhs39 said:
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
anokmik said:
Issue has star from me now. Thanks for the link!
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
Click to expand...
Click to collapse
Are you running the latest versions of ADB and Fastboot?
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
jhs39 said:
Are you running the latest versions of ADB and Fastboot?
Click to expand...
Click to collapse
These are the outputs from command prompt:
adb:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
fastboot:
fastboot version 0e9850346394-android
I think that they are the latest, because I'm an Android dev and I'm updating SDK with tools as soon as new version come in.
jhs39 said:
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
Click to expand...
Click to collapse
Yep, I have known that device has boot loop issue and it was selling as-is for repair. Also I have known that this issue could be fixed, so it was hit or miss. Now I think that this was a miss.
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
jhs39 said:
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
Click to expand...
Click to collapse
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
anokmik said:
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
Click to expand...
Click to collapse
I don't think the warranty is transferable but it won't cost you anything to contact Huawei and see if they will help you out.
http://consumer.huawei.com/in/support/warranty-query/index.htm
You can go to this site to check if the device is still under warranty. I have read about them allowing RMA on 6Ps that were out of warranty so it's worth a try at least.
http://consumer.huawei.com/us/support/warranty-query/index.htm
Sorry this is the site to check if phone is in warranty within the US. Other site was for India.
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 am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Choose an username... said:
I'm not even sure if you can lock the bootloader in stock+ Oreo, but it should be possible. What you can do is go back to MM (MM B10 should be fine), then use a fastboot package for MiFlash (such as A2017U_FASTBOOT_UNLOCK_EDL, it works even though you have a G) or maybe check if EDL Tool has an option to install fastboot, i don't remember.
The other way around it is not locking it and just using a modified bootloader to conceal the 5 second screen. Good enough for sending the phone with warranty. If you'll sell it you might be able to sell it for more if the bootloader is unlocked
Click to expand...
Click to collapse
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Spooderman46 said:
Thanks I checked the Axon 7 Toolkit and turns out it does have fastboot unlock as part of the process of unlocking the bootloader. Though it techinically doesn't support Oreo I chose the nougat one and it still did the trick albeit with another hardbrick, once locking the bootloader I had to wait for the battery to drain again before I could get into EDL and flash back to Oreo. Very painful proccess, would not recommend, should have just used your method of going back to marshmallow locking then updating again. Thanks anyway mate, the help was much appreciated.
Click to expand...
Click to collapse
I never mentioned the axon7toolkit. That one is finicky, I don't recommend it. I was talking about EDL Tool (you might even find it if you google it), it's here in the ROMs, kernels, development section.
Spooderman46 said:
I am attempting to return my Axon 7 A2017G to complete stock so that I can use the warranty. I used the EDL tool to return to latest stock oreo, but it seems that there is no way to access fastboot/bootloader on this update. I've found many guides for other models or older versions on how to get fastboot but none of them seem to be specific to my model and I am not than keen on bricking my device again. Could anyone help me out on what process I should go through to be able to lock my bootloader?
This is the EDL package I flashed: A2017G_B03_OREO_FULL_EDL
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Predatorhaze said:
you need to flash original stock rom for your device trough edl. (rom your device came from factory,you need B11 marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Click to expand...
Click to collapse
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
SaintZ93 said:
Repeatedly posting the exact same thing in every thread will only get you banned again, you sure you want that?
Click to expand...
Click to collapse
Sorry