Database Users

Not booting past Google logo

So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?

shredder47 said:
So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?
Click to expand...
Click to collapse
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?

simms22 said:
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?
Click to expand...
Click to collapse
I wiped data, and I don't have a previous ROM or nandroid to go back to, because I (stupidly) wiped EVERYTHING last night, and I've been working on fixing it since then .... I'm currently booted to recovery though, and I may just push a new ROM to it and try again
says my SD card is read only? trying to remount it as rw

I ended up having to reflash all the stock images...

could be worse.
keep a copy of your latest running rom/kernel/gapps in your storage, for just in case. thats my normal procedure, if you dont want to keep a nandroid backup in your storage, because of its size. but a nandroid backup would be ideal

Having the same issue. Tried installing new Carbon nightly (with factory reset) and didn't boot past Google logo. After that I restored my nandroid, which lasted for about a day or two. Today I started getting force closes and phone won't boot. Now I'm backing up everything (ADB rules ) and will try stock image.

Dont feel bad. When twrp updated I didn't notice wipe internal as I usually wipe all but USB in bottom but it was too late. I had swiped my finger and lost everything. Worse? My computer crashed. So RMA backordered so I bought new s2 for backup. I have to fix before sending back. But its not broken. All asurion does is push files and make sure it boots. They wipe everything. So I did most of the job for them lol. I feel stupid as I've never had a problem in four years. Bam I got too far comfy and forgot the twrp updated and had no idea what was added. I will just find a computer and fix or they will get a wiped device with twrp lol not that I think they will do anything as I've heard far worse but I did it so I'll pay if they mention.
Sent from my Nexus 4 using xda premium

[Q] Freezing, rebooting, and can't flash stock rom (reverts to previous state)

Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?

Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM

Same problem here....

Flash factory image

USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.

Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok

Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!

Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash

USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.

violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader

USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?

violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer

Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.

violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary

USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?

violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem

USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.

violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it

USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064

violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.

Nexus 6p weird bootlooping.

Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.

Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:

Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.

Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?

Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked

Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.

Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.

XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart

Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982

Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same

Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:

Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.

I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.

Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!

Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:

I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.

Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk

Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.

Soft-bricked Nexus 4, no guide will work

My Nexus 4 had been running Cyanogenmod (cm-12.1-20151007-SNAPSHOT-YOG4PAO334-mako) correctly for months. Two days ago, the screen failed to auto-rotate when I tilted the phone so I decided to reboot and see if that worked. Not only did it not work, the device went into a bootloop. It would boot, ask for my encryption password, accept the password but the OS would never start (I waited over 2 hours).
I'm able to use adb, fastboot, and access TWRP.
I tried reflashing CM12 to no avail. I've also tried going back to stock by reformatting all partitions in fastboot and flashing stock bootloader, radio, and system image (also in fastboot). That's where I'm at right now. I have everything stock except for the recovery partition where I have TWRP.
Here's the TWRP log: http://pastebin.com/MCKD73G0
Here's the dmesg log: http://pastebin.com/BdVjV2vz
Here's the last kernel message log: http://pastebin.com/DBQQBFQv
Any ideas?

I have a very strong hunch that this problem has got something to do with the sensors.
I flashed Android 4.2.2 and, to my surprise, the phone booted correctly into Android. No other ROM (stock or otherwise) would boot correctly. As I mentioned in the OP, screen auto-rotation isn't working so I downloaded an app to test other sensors. The proximity sensor, pressure sensor, light sensor, and the gyroscope don't work. I strongly doubt this is a software issue but I'm not ruling it out yet. I will try to open the phone case later tonight and move the sensor around, it might be stuck.

Just had a pro take a look at my phone. He said there's nothing wrong with the sensors so it must be a software problem. I've been trying to fix this for days now.
Any ideas would be greatly appreciated.

I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?

Feareilo said:
I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?
Click to expand...
Click to collapse
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
Voilà! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!

bart.found said:
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
Voilà! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!
Click to expand...
Click to collapse
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.

Feareilo said:
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.
Click to expand...
Click to collapse
Sad to hear that... did you already factory reset from the stock recovery?

bart.found said:
Sad to hear that... did you already factory reset from the stock recovery?
Click to expand...
Click to collapse
Yeah

6P still bootlooping after flashing stock.

So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?

I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.

318sugarhill said:
I had the same issue upon installing N with complete stock. My bootloader was unlocked. I had to boot into recovery, wipe everything (I did it multiple times to be sure) and then in recovery I powered off the device. With N still installed I setup the phone WITHOUT restoring ANYTHING from Google. Upon the initial setup menu I started like it was a brand new phone and I had no Google account. Set that all up later. That ended my bootloop problem.
Unfortunately Wi-Fi password backup was huge for me and now it's gone. Everything else while a hassle was manageable, I'm hoping when the factory image is released I can start over and sign into my account and have that data restored.
Click to expand...
Click to collapse
what did you use to update to N?

I was on the beta. I never flashed anything else. Like a dummy I had my adb commands backwards (was using adb instead of fastboot). Otherwise I would have reflashed MM.

Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/

same here.... guess this is the first brickable nexus device... the only thing that gets me to boot is if I flash N then flash the MM F vendor image, but it does not detect the sim card and camera don't work.

Mgrev said:
Some other person had the exact same issue when going from 7.0 to 6.0.1
I will have to get a replacement. :/
Click to expand...
Click to collapse
Look in the other post about botched nougat install , some of us got phone working

yeah some but like most people say they got no backup available so it doesnt help @rbouza1

minidude2012 said:
yeah some but like most people say they got no backup available so it doesnt help @rbouza1
Click to expand...
Click to collapse
I have a twrp backup, but it doesn't help at all.

Mgrev said:
I have a twrp backup, but it doesn't help at all.
Click to expand...
Click to collapse
From that thread, my solution.
FragmentsOfLife said:
Okay, this is the method I used to fix my phone. The issue was the phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the lock.
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Click to expand...
Click to collapse

Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
Hoping to find the answer for you!

Mgrev said:
So i was going to downgrade from android 7.0 (DigitalHigh6P rom). I flashed the newest 6.0.1 factory images, but no matter what i do, it still bootloops. I have tried sideloading an ota file, wiped everything several times. My bootloader is unlocked (of course).
I never get to the android boot animation.
what do?
Click to expand...
Click to collapse
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel

anidaniel said:
Ur getting bootloops bcuz u didn't had cleared the dalvik and sys cache. try doing a sys format (along cleaning those ) and then do a fresh flash of android 6.0.1 then it'll definitely work. (Y)
-anidaniel
Click to expand...
Click to collapse
I have already done that, and it does not work.
I have already contacted my retailer about getting a replacement.