11/21: Note from those working on root: "Do not update past ZV6 at this time, as we're working on a root method for ZV5 and ZV6"
[OLDER]
5/22: Sorry for not keeping this updated guys.
Promising developments on the Snapdragon 820-based S7/Edge HERE
G5 Root bounty thread HERE
All in all, it looks like root's on its way! Please keep posing any root/unlock related info you see and I'll keep this updated.
UPDATE: It appears that they've achieved root on the T-Mobile variant and a tool should be forthcoming.
No word yet on whether or not this applies to us, but here's hoping!
Video here: https://www.youtube.com/watch?v=Zlieyd9CP7Q
EDIT: It's confirmed, the bootloader on all of the snapdragon G5's is locked down tight.
It looks like there's not much we can do until someone figures out a way to crack the bootloader.
Sooo, it appears we've got the "Enable OEM unlock" option in our Developer Settings, but so far I've not been able to get the phone into Fastboot mode to actually perform the unlock.
I do have the following observations if they'll help anyone:
With the phone powered off, the following options are available:
Power+Volume Down - Boot to Recovery
Power+Volume Up+Volume Down - Displays Phone Identity (IMEI, etc.)
Volume Up+Connect to PC - Download Mode
Attempting to reboot to bootloader via adb command or from the stock recovery results in a normal system boot.
Hope somebody can use this.
yeah, I saw that. Hopefully that means root is possible. Great phone but I'd like it a whole lot more if I could get at the hosts file for ad blocking and a couple of other tweaks I'm used to.
Does the same method that the people over on the tmobil version work. They already have twrp posted.
Sent from my Nexus 6 using Tapatalk
bdsullivan said:
Does the same method that the people over on the tmobil version work. They already have twrp posted.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I looked at that thread again today. Looks like it was an April Fools...
The dev has TWRP builds that SHOULD work, but no way to flash them, as all variants appear locked.
bdsullivan said:
Does the same method that the people over on the tmobil version work. They already have twrp posted.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I edited the title to show "Not Working" for that version. I left the thread open however because they are discussing attempts to get through it.
Looks like it will be the g4 all over again. Its a shame.
Sent from my LGLS991 using Tapatalk
...but the g4 has been rooted
Give it some time.
sent from my g5
How long it took to get root on g4?
blarg said:
...but the g4 has been rooted
Click to expand...
Click to collapse
Not on marshmallow. Just lollipop.
Sent from my SM-G935P using Tapatalk
some progress has been made, apparently
https://www.youtube.com/watch?v=Zlieyd9CP7Q
blarg said:
some progress has been made, apparently
https://www.youtube.com/watch?v=Zlieyd9CP7Q
Click to expand...
Click to collapse
Awesome!
Sent from my SM-N920C using Tapatalk
Has anyone on sprint attempted this yet?
Sent from my Nexus 6 using Tapatalk
attempted what? its a work in progress. decryption is still not working, and the method hasn't been released or turned into an easy repeatable process yet. It's just a proof of concept and proof that it CAN be done right now.
Just a side note, tried adb reboot recovery and it wiped my phone, don't do that lol.
Warboy said:
Just a side note, tried adb reboot recovery and it wiped my phone, don't do that lol.
Click to expand...
Click to collapse
When you say it wiped your phone, did it completely wipe the system partition? or did it do a factory reset type wipe?
My phone got all weird during activation and it thinks it activated even though I get no service, when I did a factory reset from inside the OS, when the phone turned on, it assumed it was already configured on the network and actually asked me to manually put in date and time and didn't ask to sign into a google account or connect to wifi, I'm trying to do a full factory reset to try and get it to go through the activation process again.
Martin6040 said:
I'm trying to do a full factory reset to try and get it to go through the activation process again.
Click to expand...
Click to collapse
In the dialer do ##RTN# then reset and enter your MSL. If you don't have it you can use the guide to get it.
adb reboot recovery seemed to do a full reset, with user data partition completely erased since it was encrypted. Also it had to reactivate itself.
I now have the ls992 and the vs987. If I can contribute in any way, please let me know.
Sent from my LGLS992 using XDA-Developers mobile app
Warboy said:
adb reboot recovery seemed to do a full reset, with user data partition completely erased since it was encrypted. Also it had to reactivate itself.
Click to expand...
Click to collapse
That doesn't seem to happen anymore, as when I tried this it worked fine
Related
I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.
unlock bootloader
wcorey1974 said:
I was playing a game on my nexus 7, it froze then when rebooted it it just got stuck on google screen. Read a bunch of stuff, went into recovery and tried to recover, it would say erasing but never go any further, just sits there. got toolkit tried to restore factory with that, now when it boots I still just get google screen but I get the menu in corner for start/boot/recover/power off. still never boots, when I try to run recovery now it doesnt even go to erasing. Ive read everything I can find to restore it, got 2 toolkits, unfortunatly everything tells me to put it in debug mode, which is funny cause if I could boot up and go into settings to turn on bebug mode then I wouldnt be having these problems... Can someone please help, Im good with computers but dont know much of tablets. I did no messing with tablet besides downloading updates when they came out.
Click to expand...
Click to collapse
Also forgot to add, hen I try and run recovery from toolkit it tells me to unlock bootloader, when I try to unlock bootloadermy nexus asks me if I want to then when I hit yes, unlock it gives me neither usp nor cac partitions found.
Are you rooted?
Sent from my Nexus 7 using Tapatalk HD
Dark Jedi said:
Are you rooted?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.
How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD
Dark Jedi said:
How long you let it sit in recovery erasing before you rebooted it? Is there an option in boot loader or recovery for a factory reset? Beings you're not rooted I doubt those one click tool kits will work for you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It sat in erasing for 1 hour and didnt do anything. I was doing factory reset in recovery.
As long as the boot loader starts you can recover your Nexus. Check this guide: http://forum.xda-developers.com/showthread.php?t=1907796
If he can't unlock the bootloader then there's not a whole lot he can do. Run "fastboot getvar all" while in bootloader and tell us what it says please. If adb is seeing your phone in recovery, then run an adb shell and do "ls -l /dev/block/platform/sdhci-tegra.3/by-name/" please.
Sorry I can't help further but I just got this and don't know much. I am glad others came in to give you more help.
Sent from my Nexus 7 using Tapatalk HD
Damn... I didn't see he can't unlock the bootloader. This is going to be difficult.
wcorey1974 said:
My guess is no, I never messed with any of my system stuff. Everything was factory except for the updates it had me do as they came out.
Click to expand...
Click to collapse
Im exact in the same situation. No rooted phone, nexus wont boot anymore, cant dont anything in the bootloader section ...
I would be extremley thankfull for hints how to fix this issue.
Cheers
Papa
Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app
tnt0303 said:
Just sayin, I think you guys need to pull the back cover and disconnect the battery for at least one hour.
I am really new at this but it helped me save mine twice. I think?
After you plug the battery back in try fast boot.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
But this will void my warranty right ?
They have no way in knowing you pulled your back cover off. Just be careful so not to leave pry marks. Only way they will know is if you tell them you did it.
Sent from my Nexus 7 using Tapatalk HD
Hey guys
I thought I'd just let you all know that my ambition to get 4.3 and lack of knowledge, led to my phone getting bricked today. I'm so devastated. I was following efrant's guide and flashed everything correctly and then as usual I lost half my storage and I followed the other guide to restoring the lost storage, once again i followed everything but i didn't get the storage back, then i did some cmd commands like the guide did. Next thing you know I may have done something wrong and I was at the bootloader screen and I couldn't reboot or go to recovery. Read and read nothing helped, called Google and they couldn't help me. I am now getting a replacement. SO there you go guys, just the greed of getting 4.3 caused me to brick my phone as well as my lack of knowledge I guess. Can't complain. Thought I'd share this with you all.
Div
P.S Moderators if this isn't suitable you guys can delete it no harsh feelings
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fabrizziop said:
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
Click to expand...
Click to collapse
This. You're totally not bricked.
Please follow the instructions in this thread:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus⁴ using Tapatalk 4 Beta
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Fataldesain said:
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it's totally worth it
nqk said:
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Click to expand...
Click to collapse
Perhaps
Code:
# dd if=/dev/zero of=/dev/block/mmcblk0
Thats not greedy, your just too excited for 4.3
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Click to expand...
Click to collapse
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Dvash27 said:
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Click to expand...
Click to collapse
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
miniAndroidian said:
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Dvash27 said:
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Click to expand...
Click to collapse
Glad to know that it helped you mate
What about content on phone
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
TToivanen said:
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
---------- Post added at 10:45 AM ---------- Previous post was at 09:46 AM ----------
leiftorem said:
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
Click to expand...
Click to collapse
I can see my phone listet under "Advanced Utility, but I cannot seem to pull the files from my phone!
I am getting really frustrated here now!
Anyone??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Mr. Kostik said:
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Click to expand...
Click to collapse
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
leiftorem said:
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
Click to expand...
Click to collapse
Oh well you should look in one of those threads on how to root and so on, flashing a recovery using a toolkit should also work. Texts will be gone.
Or from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
But at some point you'd need a custom recovery anyway.
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
simon_lefisch said:
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
Click to expand...
Click to collapse
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
ericdabbs said:
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
Click to expand...
Click to collapse
ok. i was on stock. rooted with the IO method. wanted to flash a ROM (clean rom). downloaded ROM, wipe dalvik/cache/data. after reboot, phone booted into recovery mode. tried going into download mode to revert back to stock and LG FlashTool failed. said phone was the wrong model number (D802). the ROM i Downloaded said it was for VZW G2. obviously it wasnt. so i finally ended up using fastboot to push boot image and it booted, but in about phone, it says it D802 model (i just got it to boot, where as before i was stuck in fastboot mode). now i need to return to stock, but dont know how. any ideas?
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Gnarfsan said:
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Click to expand...
Click to collapse
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
simon_lefisch said:
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
Click to expand...
Click to collapse
Even following the steps posted in that thread?
Gnarfsan said:
Even following the steps posted in that thread?
Click to expand...
Click to collapse
yes. not sure why its doing that. is there any way that download mode can be deleted from the phone? also, how do you get into fastboot mode?
EDIT: nevermind. i finally got it into download mode!! (thank god!!) flashing right now. damn that was a pain in the ass. i was starting to freak out that i messed up my phone. this is my first LG phone so this process is a little new to me (been on moto for the last few years) thanks for trying to help me out. this was def a learning experience.
Phew, I'm glad to hear that. Some day I will be in the same situation
Sent from my LG-D802 using XDA Premium 4 mobile app
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
trickster2369 said:
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
I was thinking the same thing. It's best to stay out of those modes. Get a recovery installed ASAP and do everything that you need to do from there. I recommend TWRP Recovery.
Sent from my LG-D802 using XDA Premium 4 mobile app
Maybe because when flashing stock rom download mode is needed (atleast in my old sammy phone, maybe same in moto phones)
What's wrong with restoring the backup of the stock rom that should have been made before wiping and flashing a different rom? Not sure what I'm missing here.
Sent from my Nexus 10 using XDA Premium HD app
Download mode is useful to flash the entire phone back to stock using the OEM tools. It's not just for the stock ROM. It's everything. It's useful if you get a bit carried away in TWRP and wipe partitions you really shouldn't be touching. Or if you somehow manage to bork your recovery, or at least can't get into it. It's also good if you want your phone to be completely stock to sell it or to send it in on warranty. I'm sure someone could come up with other scenarios where it's useful.
But yes, it is a good idea to keep a backup of your stock ROM. And as always, know what you're flashing, make sure it's for your phone and check md5s. And be mindful of what you're doing in recovery. You should be able to avoid most issues. Download mode is indeed something you shouldn't be using often but as I said above there are situations where it is useful or necessary. It's actually something I suggest you know how to use. I say it's always a good idea to know how to get back to complete stock for warranty stuff, selling, or if something just goes majorly wrong.
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Semantics said:
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Click to expand...
Click to collapse
Hmm.....interesting. I may try that next time I have to flash to stock.
Sent from my VS980 4G using Tapatalk
Same Problem
simon_lefisch said:
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Can you fill me in on how you used fastboot to install twrp? I am in the same boat right now...
i'm stuck as well in Fastboot and can't figure it out
emmur0 said:
i'm stuck as well in Fastboot and can't figure it out
Click to expand...
Click to collapse
I sent you a pm
You can you adb side load which is the same for flashing rom, pushing, or pulling file from the phone which is the first thing to learn before flashing anything to the new device that you got and know nothing about.
Sent from my LG-LS980 using xda premium
So I set up my phone with all my apps, and turned it off and now it won't boot up. Any idea on how to get it to work?
Sent from my Nexus 6 using Tapatalk
When you say it won't boot, does it not turn on at all? Does it hang on boot? Bootloop?
Guessing you've checked the obvious like charging the battery, trying another plug, etc. The phone shipped with a USB type C charger with a C to C cable, as well as shorter USB A to USB C cable to use with a standard USB charger. I'd try both of them in different wall plugs and the USB A cable in multiple charging blocks.
Can you enter bootloader mode by holding POWER and VOLUME DOWN?
Sorry for not being detailed ?but yes it is stuck in a bootloop in the initial Google screen. It also let's me get into the bootloader by pressing power and vol down. I've tried the factory reset option and still the same thing.
Sent from my Nexus 6 using Tapatalk
MR_XXIV said:
Sorry for not being detailed but yes it is stuck in a bootloop in the initial Google screen. It also let's me get into the bootloader by pressing power and vol down. I've tried the factory reset option and still the same thing.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Did you try going into recovery and wiping cache and dalvik cache?
I would suggest flashing factory images, but I am not sure if you will be able to unlock the bootloader if you didn't enable it in developer options. I have read that trying to unlock the bootloader might not work if you didn't enable the option before attempting. Might also cause issues, but if you're already unable to boot, I don't know that it would necessarily be worse.
Google will likely suggest flashing the factory image before an RMA could be initiated. Hopefully someone more experienced than me can confirm if you must enable OEM unlocking before attempting. Unlocking bootloader does wipe data, but this shouldn't be an issue if you already tried a factory reset.
If your bootloader is already unlocked and you modified anything, I would bet a factory image flash would fix it.
fury683 said:
Did you try going into recovery and wiping cache and dalvik cache?
I would suggest flashing factory images, but I am not sure if you will be able to unlock the bootloader if you didn't enable it in developer options. I have read that trying to unlock the bootloader might not work if you didn't enable the option before attempting. Might also cause issues, but if you're already unable to boot, I don't know that it would necessarily be worse.
Google will likely suggest flashing the factory image before an RMA could be initiated. Hopefully someone more experienced than me can confirm if you must enable OEM unlocking before attempting. Unlocking bootloader does wipe data, but this shouldn't be an issue if you already tried a factory reset.
If your bootloader is already unlocked and you modified anything, I would bet a factory image flash would fix it.
Click to expand...
Click to collapse
The phone is actually not rooted so when I get in to the bootloader it doesn't give me the option to do any of that. This is really weird not sure what caused this to happen ?
Sent from my Nexus 6 using Tapatalk
MR_XXIV said:
Sorry for not being detailed but yes it is stuck in a bootloop in the initial Google screen. It also let's me get into the bootloader by pressing power and vol down. I've tried the factory reset option and still the same thing.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow step 9 to get your phone working again. That is if you are unlocked.
But don't relock your phone again, go back and read each step and follow it correctly.
Things that cause bootloops:
Not flashing the chainfire's modified boot.img
Using TWRP to install root when you exit it. If your phone is not rooted it will ask you to install root upon leaving TWRP and always say no. SuperSU and root are flashed with a file in TWRP, the file can be found linked in the tutorial I linked above.
Thank you all for the help, I got the phone up and running
Sent from my Nexus 6 using Tapatalk
MR_XXIV said:
Thank you all for the help, I got the phone up and running
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What ended up working? Could be beneficial for another user.
fury683 said:
What ended up working? Could be beneficial for another user.
Click to expand...
Click to collapse
The post above my previous comment just follow the link. It's real easy it gives you detaila step by step ???
http://forum.xda-developers.com/showthread.php?p=63772866
Sent from my Nexus 6 using Tapatalk
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Sent from my A0001 using Tapatalk
trsargent said:
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Click to expand...
Click to collapse
do you have an adb option in your recovery ?
nicoconepala said:
do you have an adb option in your recovery ?
Click to expand...
Click to collapse
Yes, I can get to an adb option in recovery
Sent from my A0001 using Tapatalk
trsargent said:
Yes, I can get to an adb option in recovery
Click to expand...
Click to collapse
ok then you should try to flash stock rom from essential
nicoconepala said:
ok then you should try to flash stock rom from essential
Click to expand...
Click to collapse
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Sent from my A0001 using Tapatalk
trsargent said:
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Click to expand...
Click to collapse
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Wrong section.
NaterTots said:
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Click to expand...
Click to collapse
Gave it a try, but it didn't resolve the issue. Got the your device is corrupt message. Any other ideas? Thanks!
Sent from my A0001 using Tapatalk
I'm searching for answers too! My essential is doing the dotted box to the dotted circle spin back & forth over & over ! I saw the dead robot with exclamation mark . The only thing on the essential website is to wipe phone ! Help. If the person that made this phone do this to people dies please let me know, so I can smile during this stressful time . If they r still alive I hope they are in agony over something thx!