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.
Related
I have been running Paranoid Android rom for for several months fine. However last week the calls stopped working (no audio) then constant crashing application. After some checking I found that the cache partition was corrupt. I reinstalled the factory image from google. The installed the Team Win recovery again. After serveral hours of use I started getting the same problem. Again the cache is corrupt. I tried again to to install the factory image using both the Nexus 4 toolkit and with my Ubuntu notebook. Bothe gave me can not write errors. The device shows up with adb and bootloader. I can boot into the TWRP recovery still but I can not write to memory at all now.
I need to wipe the recovery and if possible install stock recovery. I was oem unlocked but still have secureboot enable. Can not but the phone except recovery and bootloader.
Is there a way to wipe this completely using dd or anything? Obviously it is defective hardware. The phone would get very hot which I know is not that unusual but I think it is related to the failure.
Update: was able to erase recovery through bootloader.
Still ned to oem lock. bootloader oem lock first appears to work but when doing a reboot the phone still shows locked. Seems nothing can be written to flash on the phone.\
Any ideas of what to do before sending in for warranty?
Deleted-misread OP
Did you test a stock ROM to confirm it is not a bug with Paranoid rom?
johnciaccio said:
I have been running Paranoid Android rom for for several months fine. However last week the calls stopped working (no audio) then constant crashing application. After some checking I found that the cache partition was corrupt. I reinstalled the factory image from google. The installed the Team Win recovery again. After serveral hours of use I started getting the same problem. Again the cache is corrupt. I tried again to to install the factory image using both the Nexus 4 toolkit and with my Ubuntu notebook. Bothe gave me can not write errors. The device shows up with adb and bootloader. I can boot into the TWRP recovery still but I can not write to memory at all now.
I need to wipe the recovery and if possible install stock recovery. I was oem unlocked but still have secureboot enable. Can not but the phone except recovery and bootloader.
Is there a way to wipe this completely using dd or anything? Obviously it is defective hardware. The phone would get very hot which I know is not that unusual but I think it is related to the failure.
Update: was able to erase recovery through bootloader.
Still ned to oem lock. bootloader oem lock first appears to work but when doing a reboot the phone still shows locked. Seems nothing can be written to flash on the phone.\
Any ideas of what to do before sending in for warranty?
Click to expand...
Click to collapse
nwtspam said:
Did you test a stock ROM to confirm it is not a bug with Paranoid rom?
Click to expand...
Click to collapse
Yes. First time I had the problem I flashed stock rom. I started having the same problem on stock. After a short time I could no longer mount any partition through recovery. TWRP recovery showed error messages when trying to mount them. Also bootloader commands fail when trying to write anything to memory. Only erase command works.
At this poit I am mostly concerned with getting the phone to remain oem locked so I can return it to LG for warranty service.
try using the wugfresh toolkit. I've used to to return to stock and do an OEM lock.
Need some help.
I just sideloaded the 4.3 update to phone and now it's stuck on the 'X' loading screen.
My phone was rooted, but all stock (including the bootloader). I used the sideload ADB command and everything went fine, but the phone now won't boot.
How do I fix this?
did you data wipe(factory reset) before flashing?? if not, you have too.
I applied the OTA...didn't think I had to
Any idea on how I fix it now?
Really don't want to lose all my data
Install a custom recovery and wipe or apply factory image
favaroooo said:
Install a custom recovery and wipe or apply factory image
Click to expand...
Click to collapse
Is there a way I can fix it without wiping everything?
theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
I do not think because you have to change recovery you must unlock the bootloader and unlock bootloader wipe the phone
theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
no, its the data(and other stuff) causing it not to boot. same thing when flashing custom rom, you wipe when fkashing different roms. and going from android 4.2.2 to 4.3, theres many changes, enough to consider it a different rom.
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
theprodigy85 said:
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
Click to expand...
Click to collapse
are you flashing a zip or an img file??
simms22 said:
are you flashing a zip or an img file??
Click to expand...
Click to collapse
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Try to restore using the factory image
theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
yea, the zip youd want to wipe data/factory reset, then flash the rom. dirty flashing wont help since the changes are big enough.
theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
I bought my ole lady a Nexus 4 for Valentines day, anyway, today she got the OTA update and let it install the update. Now mind you she is 100% stock, adb debugging was not enabled, and her bootloader was still locked. (She would not let me touch her Nexus 4 lol) When the device rebooted it stuck on Android Upgrading finishing boot. So I said well let me see what I can do, this is what I did to fix it.
I use only Ubuntu so this may not work on windows i do not know. I Booted the device to the bootloader, connected it to my laptop via USB. I opened a terminal and typed in "sudo fastboot devices" and entered my password when promted and this gave me the device ID and fastboot letting me know fastboot was working. I then typed in "sudo fastboot reboot" and the device rebooted but was stuck on the bootanimation. I opened the internal storage up on my laptop in my file explorer and made a copy of her internal storage. Next I booted the device back into the bootloader then opened a terminal and typed in "sudo fastboot oem unlock" and the device gave me the unlock warning and the yes or no options. I selected yes so it would factory reset. After it did the factory reset the device reboot and booted to the setup welcome screen. Hope this helps others, also thanks to my good good friend Ljjehl for reminding me to use "sudo".
Edit: If you open the command promt with Administrative permissions in Windows this will work in Windows as well. Go to C:\Windows\System32\cmd.exe and right click on the cmd.exe file and select run as administrator. Then CD to the location with your fastboot.exe command. Thanks to another good friend TheBr0ken.
Thanks for the help...
I just ended up flashing each of the 4.3 components from the factory image. Just annoyed that I lost everything...
I'm stuck at the same screen. I received the OTA update, I didn't do anything special. My phone is unlocked and rooted (or WAS) but that was months ago, the rest is stock.
I think having encryption on my phone may have made it do this. I don't think Google anticipated doing the update properly for encrypted phones. Now I fear I've lost everything because even if I could connect, all data is encrypted...
similar problem
After starting to OTA update it was going smoothly, i was making breakfast, came back to find my screen at the "starting apps" screen frozen. The little circle that rotated wasnt doing anything so i left it there for awhile longer and still nothing. It would not move off that screen so i held power button down and restarted. now its stuck at the X screen also.
Yeah, I'm stuck there too. Already tried Factory Rest, didn't work. So what can I do?
I was on stock 4.2.2 and unrooted. I used the 'Google Services Framework' hack to force the 4.3 OTA update. The update downloaded successfully, phone restarted to apply the update and then restarted again. And now its stuck at the Google screen and keeps on restarting :crying:
I dont have the USB drivers installed on my PC too.
Same Problem
I have a nexus 4 (stock and unrooted),after 4.3 update,it is lagging during phone lock on/off (2 sec/5 sec).Hence I restarted my phone,and it stuck at "x" logo.Did clean data 3 times and then its working.
The problem is,in 2 days,I have experienced and done above thrice?
What could have gone wrong?
Hi guys,
I've just found how to correct this problem. All you have to do is to correctly wipe your phone before flashing factory image.
So :
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
I've just unbrick a n4 this way 15 minutes ago.
I have found the problem in recovery where you can see error log saying "cannot mount cache"
So formating correct the issue.
Hope it can help, fingers crossed.
Sent from my Galaxy Nexus using xda premium
My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?
AlfexOmega said:
My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?
Click to expand...
Click to collapse
I'm in the exact same boat...hopefully something can be done, but I'm afraid we're idiots for not having checked OEM Unlocking. I've tried adb sideloading the OTA image, but as you said, with a locked bootloader, we've got nothing. Anybody have any ideas?
You might be able to use ADB to modify the OEM Unlock setting while booting.
Also, if you ever plan to mess with your OS, especially alpha/beta versions, always have your bootloader unlocked to prevent issues like this.
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Live booting TWRP works on the 6P even with the bootloader is locked?
Sent from my Nexus 5X using Tapatalk
imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Can't boot twrp.img because the device is locked. Anything else I can do?
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
No luck for me, unfortunately. Keep in mind that I tried to sideload the OTA.zip with a locked bootloader before doing this, so that may have made this process not work. For those who haven't tried to "fix" their failed installation like I did, give the cache clear a try first.
Apparently some people can use the fastboot format command while their bootloader is locked. You can try booting into the bootloader and issuing these commands. (THIS WILL WIPE YOUR ENTIRE DEVICE INCLUDING SDCARD/INTERNAL STORAGE. Of course, your device is now bricked, so I'm sure this is fine for you.)
Code:
fastboot format cache
fastboot format userdata
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled
lightmastertech said:
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled
Click to expand...
Click to collapse
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip
Ame123 said:
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip
Click to expand...
Click to collapse
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing
silviuardelean said:
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing
Click to expand...
Click to collapse
Seems like it could be a driver issue. If you run adb devices does your device show up?
freezerbite said:
Seems like it could be a driver issue. If you run adb devices does your device show up?
Click to expand...
Click to collapse
Yes, the device was showing up in cmd but couldn't get over <waiting for devices>... I've tried to install TWRP and failed again. After trying to sideload the image a dozen times and clearing cache, formatting data, etc several times, it somehow worked in the end. Thank you very much!
It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging
GeorgeOSbeta said:
It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging
Click to expand...
Click to collapse
I was able to get mine to work without having it enabled you could try using Nexus Root Toolkit it guides you through how to do everything
https://www.youtube.com/watch?v=LfDSZsr6230
Locked bootloader 7.1.1 ota preview help!
I have the latest preview build directly installed ota from Google. The phone just started bootlooping the other day for no apparent reason. I didn't have the developer options on or oem unlock enabled.
I can get to bootloader mode and recovery mode. I have wiped and reset from recovery with no help. I can access adb and fastboot on the pc but it won't let me write any files because of the locked bootloader. Anything I try to sideload so far gives an error. Any further suggestions?
AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?
solefero69 said:
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?
Click to expand...
Click to collapse
You use recovery to sideload it via adb. If you are unsure how to do so you can download and use Nexus Root Toolkit it does everything for you, it's really useful This video will help
https://www.youtube.com/watch?v=LfDSZsr6230
I was running Pure Nexus. My camera won't focus at distance, so I was trying to revert the phone to stock before RMAing it.
I used #10 in this guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) and flashed all the pieces.
This is the zip I used for the images - https://dl.google.com/dl/android/aosp/angler-n4f26o-factory-c53f0a50.zip
Then I formatted userdata, relocked the bootloader, and tried to reboot. It's now stuck on the Google logo. It doesn't look like it's looping, it's just stuck.
I can boot into the stock recovery, but since it's a fresh install, USB debugging is not set so I don't think I can ADB anything. And since I locked the bootloader, I don't think I can fasboot flash anything either.
Am I out of luck?
Since I was going to send it back anyway, should I just blame the return on the fact that it won't boot?
Thanks
Edit: Huh, I think I got it to work. I had tried the guide to flash a full OTA as a fix, but when I got to "ADB devices", it wouldn't see my phone. But I tried it again, and it did see the phone and I was able to flash the OTA. It's rebooting now.
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