So I have researched everywhere I can, watched videos, etc. and I cant figure this out. Wondering if I bricked my phone.
Originally my phone was stuck on the boot animation screen for Essential. For hours. So I factory reset it using the stock recovery. After that phone would boot and either get stuck on the essential Logo, or stuck on the boot animation. I reset the phone a bunch of times, and on 1 of them I was able to get to the phone set up screen which I quickly got through and made sure I was in developer mode, and had OEM unlocked turned on. While I was in the setup screen all kinds of services kept force closing, and about 30 seconds after setting up the developer stuff to unlock the bootloader the phone finally froze and went to the boot animation screen and just stayed there.
Next I unlocked the bootloader following the steps on here, then unlocked critical_processes or whatever it is called.
Next I tried to flash a stock essential rom from the roms dump page. When trying to wipe user date I get "error. Cannot generate image for userdata". I then flashed the stock rom, and restarted and experienced the same exact thing as before. Either stuck on logo screen, or stuck on boot animation....for hours.
Last I tried flashing to the stock rom recommended in the lineage OS thread, and then flashed TWRP again, and flashed Lineage, and once again I am stuck on the essential logo screen. If i go into recovery it now goes to the Lineage recovery so I am assuming the install worked.
I am completely stuck now and can not figure out what to do next, or if I am just stuck with a hard bricked phone. Any help would be appreciated.
Update: So after restarting the phone about 7-8 times I actually got Lineage OS to load up and was able to set the phone up. That lasted about 2-3 minutes before the phone froze, went back to the Lineage startup animation and then restarted. Now it won't go past the Essential logo screen.
I'm new to the PH-1. I went in circles because all I wanted was the AOSiP ROM. Then no touch, tried flashing the September "hyp" and "rpm" partitions. Didn't help... And on it went.
I finally dug out of my hole by sideloading the essential.com OTA in stock recovery.
That's what I would try if I were you. But then, I'm new to the phone [emoji23]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I'm new to the PH-1. I went in circles because all I wanted was the AOSiP ROM. Then no touch, tried flashing the September "hyp" and "rpm" partitions. Didn't help... And on it went.
I finally dug out of my hole by sideloading the essential.com OTA in stock recovery.
That's what I would try if I were you. But then, I'm new to the phone [emoji23]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Sideloading it using the factory recovery is the only thing I didn’t do. Everything I flashed through fastboot. Guess I’ll try sideloading it next.
minttoast said:
Sideloading it using the factory recovery is the only thing I didn’t do. Everything I flashed through fastboot. Guess I’ll try sideloading it next.
Click to expand...
Click to collapse
Did that work for you?
I was having these same kind of problems - all guides never said a thing about flashing unlock_critical - after I did that (and all other requirements to unlock and flash roms) then sideloaded I think it was .092 factory zip - I was able to start flashing things like old school android that I am used to. Still need to figure out why they are saying to use magisk on a boot.img and then flash manually but that may just be certain roms.
Related
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
MATTHEWLONG said:
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
Click to expand...
Click to collapse
This has been an ongoing thing with the 6P and 5X, there are multiple threads on this bootlopop issue some recoverable, some not. Check this out see if it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Thanks for the support, I will take a look.
I've read too many threads about 7.1 and the beta program causing boot loops and bricks....this is ridiculous!
Do you have a nandroid on hand? If so, try restoring it and see if that works.
I have only boot looped twice with this phone. Each time I went into TWRP and did a full wipe (everything except internal storage). I completed the full wipe three times consecutively. After the third wipe I boot into fastboot and flash the latest stock images from Google. Reboot.
Let the phone sit for 10-15 minutes then boot back into fastboot to flash custom recovery (TWRP). Then boot into recovery to flash SuperSU. Reboot. Let phone sit for another fifteen before continuing with setup.
I know wiping the device three times probably doesn't do anything extra than wiping once before flashing but it's what I've always done and what's always worked for me.
Over the past three or so days, I started getting random reboots and phone getting stuck at the Google Logo. I thought it might have something to do with Magisk or the DarkROM that I was using. So I decided to go back to stock.
- I have unlocked bootloader.
- I am able to get into TWRP
I fastboot flashed all the necessary files to get back to stock. However, phone still gets stuck at the GOogle Logo.
I flashed Aquarious custom ROM, - still stuck at Google logo.
Tried the modified 4 core version of the EX kernel in the bootloop fix thread - still stuck at Google Logo.
I am able to enter TWRP and bootloader. But can't get the phone to boot beyond the Google logo.
Anybody have any suggestions to help?
Check this: https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
ftarules said:
Over the past three or so days, I started getting random reboots and phone getting stuck at the Google Logo. I thought it might have something to do with Magisk or the DarkROM that I was using. So I decided to go back to stock. I am able to enter TWRP and bootloader. But can't get the phone to boot beyond the Google logo. Anybody have any suggestions to help?
Click to expand...
Click to collapse
Since you have access to recovery you may not have BLOD. Before applying the BLOD workaround, I would simply flash the latest (8.0) full image according to the instructions on the Google Factory Image website. That means using the included flash-all.bat. This is the way Google intended people to return to a fully stock device. Then you will know for sure if you are affected.
ftarules said:
Over the past three or so days, I started getting random reboots and phone getting stuck at the Google Logo. I thought it might have something to do with Magisk or the DarkROM that I was using. So I decided to go back to stock.
- I have unlocked bootloader.
- I am able to get into TWRP
I fastboot flashed all the necessary files to get back to stock. However, phone still gets stuck at the GOogle Logo.
I flashed Aquarious custom ROM, - still stuck at Google logo.
Tried the modified 4 core version of the EX kernel in the bootloop fix thread - still stuck at Google Logo.
I am able to enter TWRP and bootloader. But can't get the phone to boot beyond the Google
Click to expand...
Click to collapse
ummmm... this thread looks abandoned. i'm going through the same thing. i'm not sure what to do now.
please help!
thanks.
I received an update push from Motorolla that installed Nougat. After that, my phone would crash every 3-10 minutes. I did all the troubleshooting I could find online. I contacted support and they wanted me to spend $150 to get it "refurbished." Of course, it sure seems like a software problem, so that wouldn't help me anyways...
I turned to custom. After rooting, installing SuperSU and TWRP, I couldn't get several versions of AICP or Lineage to ever boot (stuck on loading screens). I also tried all the advice from this thread.
I went back and installed the stock Rom using f2fs , and the phone would get to the "hello moto" part of the boot up, then crash and reboot. I tried again using EXT4, and it worked, but just like before I ever begun, my phone was crashing every 3-10 minutes. However, the first crash wasn't until after I made a phone call, and my phone had been crash free for about 20 minutes before that call.
I'm a I.T. guy, but I'm not a "phone" guy. But it seems to me that there must be some other software that was modified during the update that is causing the problems that isn't part of ROMs. Something in the Kernal, or a driver folder or something?
Also, is there a way to get crash reports? So maybe if I at least go back to the default ROM and wait for it to crash, I have some info to work with?
Any help is greatly appreciated, thanks!
Flash full stock 6.0x for your model/region.
Important:
Without bootloader, gpt. Don't try locking BL.
Links you can find in my signature.
Try normal boot and after success any custom.
You cannot allow any ota update after it.
Some customs are only for Nougat modem/radio - don't flash it. @Kaivian
Ok, I got most of that, except I don't know what gpt refers to and am not getting any hits on search.
My signature - flashing stock - without bootloader & gpt.
So, I installed a 6.0 stock ROM and got tons of errors. I tried a 2nd time, still got tons of errors. Needless to say, stock 6.0 didn't boot. I decided, "The heck with it" and tried installing Lineage 7.1 again... and it worked! It finally booted up entirely. However, now I get a "Sim card missing" notification. Can I just reinstall part of something... like the modem? so I can keep this "working" lineage boot? Or am I starting over yet again?
Repeat
from
fastboot flash modem ...
to
...fsg.
dzidexx said:
Repeat
from
fastboot flash modem ...
to
...fsg.
Click to expand...
Click to collapse
This caused it to not boot.
I went back to 6.0 and turned off auto-updates. I'll try again sometime when I have time. I did like the custom rom a lot, just couldn't use it as a phone xD
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
jsm11482 said:
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
Click to expand...
Click to collapse
Mine does it aswell, but after like 20 min it boots up. I flash mine with the "Nexus Rool Toolkit" with the option "Flash Stock + Unroot", in your case i wull put the radio button on "Softbrick/Bootloop". Then follow the steps on the screen and then when it reboots the programm will tell you that you need to wait like 20 min. And then it should be up and running again