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.
Related
I tried to go from my AOKP device to a stock rooted rom I downloaded from the Development Section here, but it seemed to go horribly wrong.
I got force closes all over the shop, so I did a Factory Reset and tried again, still got Force Closes.
I tried to restore my Backup, but it seems that 4.2 puts my SDCARD data in a folder called /0/, so TWRP couldn't find them.
I have ended up downloading the Factory Image for 4.2 from Google and have decided to start from scratch. (And deleted ALL MY DATA in the process!!)
So, is there anyway I can root this stock ROM? I have just re-installed TWRP, so I am set with a custom recovery!
http://forum.xda-developers.com/showthread.php?t=1750835
This worked for me.
It might cause a boot loop.. Don't worry about it, let it sit a few..then power off
And restart.(see the last page in the thread.)
taqulic said:
http://forum.xda-developers.com/showthread.php?t=1750835
This worked for me.
It might cause a boot loop.. Don't worry about it, let it sit a few..then power off
And restart.(see the last page in the thread.)
Click to expand...
Click to collapse
Yeah, just done it! Seems to work well!
All I need now is an Extended Power Menu!!
Hi guys,
I tried to update my Nexus 4 to 4.4 when Google pushed the update out for it yesterday, I forgot I had unlocked the phone (I don't have any custom ROMs on it, just SuperSU.)
Every time I try and power it on, the loading screen is endless, although I can hold power and volume down to enter recovery mode, nothing seems to be working.
I am a bit of a novice so any help or suggestions would be really appreciated!
Thanks.
The first few pages of the forum is littered with posts like this, i was in the same situation.
What i did was download the 4.3 rom from google, and flash /boot and /system onto the phone. I suspect the 4.4 rom would also work.
This got the phone booting without harming (most of) my data, but much of the UI was mangled and didnt work properly. I tried to backup my images over USB but it didnt work, you might have a better result. I also wanted to backup my SMS but they had all vanished.
I rebooted the phone to recovery (TWRP) and used adb to backup the sdcard (adb pull /sdcard sdcard) then did a full flash using the 4.4 rom downloaded from google and that got it working again. Then i reflashed the latest version of TWRP recovery and SuperSU.
Hope that helps.
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
GeorgeAmodio said:
That's really helpful, thanks! Is there ANY chance of a step-by-step? I'm a complete 'noob' probably a mistake to root in the first place :crying:
If you're busy don't worry, just don't want to **** things up more than I have haha.
Thanks, appreciate it.
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
Cheers guys, a lot more helpful than the bloke from Google. Will try it in the morning!
This will surely help
If somebody is facing boot loop after kitkat update on nexus 4 and no data backup can try to go to safe mode and backup their data. To goto safe mode on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
Hi,
It also happened to me, dont know if it is related to having ROOT or not, but i had to manually flash factory image (4.4) and it worked. I flashed everything except userimage.img but on first boot it took like 15 minutes to reboot and then all my personal data (photo, music...) was gone....
So just be cautious before upgrading!
gee2012 said:
Look here http://forum.xda-developers.com/showthread.php?t=2010312 for flashing a factory image guide.
Click to expand...
Click to collapse
Yeah that is pretty much what I did to fix mine except that I did not flash the userdata (step 10 in chapter D) so that I would't loose my data.
arffrhn said:
Got stuck in google screen, tried to flash factory images but my pc won't detect the phone anymore. Any advice?
Edit: Solved.
Click to expand...
Click to collapse
What did you end up doing for your PC to detect your phone?
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
I don't know what any of that means or how to do it...
iamj00 said:
I don't know what any of that means or how to do it...
Click to expand...
Click to collapse
This is sideload guide. And the is the rom I used to sideload before: Purity. After I had successfully booted into the system. I flashed 4.4 factory images using this awesome noob friendly guide for a clean kitkat update.
arffrhn said:
I had sideloaded a rom in recovery so that it will replace the lost system.img on my phone. Then, it booted up and I flashed back factory images the usual way. Everything is running smoothly again.
Click to expand...
Click to collapse
iamj00 said:
What did you end up doing for your PC to detect your phone?
Click to expand...
Click to collapse
Installing the driver. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1992345
Boot to bootloader and connect to your PC, usually Windows will find the driver automatically
Last night my phone wanted to update to 4.4.4 because it's been wanting to for a while, but I know it wouldn't work because my phone is rooted. It had tried this at least 3 times before and everything was fine; download update, tries to install, fails, boots right back up. I wanted to get rid of the Update notification in the top bar, so I just ran it again thinking it'd be okay. Well, this time it bricked my phone, leaving me at a neverending loop at the boot animation. I first tried to wipe the cache and dalvik cache, which did nothing. Then I tried a factory restore, which also did nothing. Then I reinstalled the stock 4.4.3 rom I had been using, which did nothing. Then I wiped the SD card completely and reinstalled a stock 4.4.4 rom through sideload, which has done nothing. My phone just sits at the boot animation and taunts me. Worse yet, I have a 16-hour drive tomorrow and my phone was going to be the majority of my sanity during that time.
What should I do?? Is there anything I can do? Normally I would just contact Google to get a replacement (I've done this before when the 4.2 update was causing a lot of bricks,I think it was 4.2 anyway, I forgot) but I'd like to have a working phone for my 16 hour trip..... if possible. Any help would be greatly appreciated! Thank you.
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
CCody said:
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
Click to expand...
Click to collapse
I had a Vanir 4.4.3 rom on my phone that I tried to flash as well, but for some reason it went right into "Optimizing Apps" after the first boot, something I hadn't seen before. Then it got stuck at "Starting Apps...", then after a restart, it too was stuck at the boot animation.
I can boot into recovery luckily, but that's all I can do. I have CWMR v6.0.3.5. I've tried just about everything I can think of. [edit] I was able to contact Google for some live chat support and am now #2 in the queue. Hopefully they can either help me or get a replacement going. Either way, I'd still love any help you guys can give me, I'd really like to get it fixed rather than waiting for a replacement.
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
CCody said:
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
Click to expand...
Click to collapse
I've done that already, Factory Reset + wipe cache + wipe dalvik cache + format system/data/cache/sdcard/data/media. The phone was completely bare and that's when I sideloaded the stock 4.4.4 rom (otherwise it's stuck at the Google boot screen). I'll try it again, though.
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
RawrNate said:
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
Click to expand...
Click to collapse
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
CCody said:
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
Click to expand...
Click to collapse
Yeah haha, it's really really strange. I appreciate you trying to help me, though! Lucky for me I'm getting a "One-time exception replacement" since my warranty is expired but they must be super stumped with the issue as well xD
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
CCody said:
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
Click to expand...
Click to collapse
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Wait, how do I flash the binaries since they're .tgz files?
RawrNate said:
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Click to expand...
Click to collapse
This is really strange man. Flashing stock ROM is the last resort but even that seems to be failing for you.
Have you tried downloading the stockRom again (just to make sure it isn't corrupted). Also, maybe you can try using TWRP instead of CWM this time.
Good luck.
RawrNate said:
Wait, how do I flash the binaries since they're .tgz files?
Click to expand...
Click to collapse
No need to flash them, since you are on a factory image, sry.
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
RawrNate said:
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
Click to expand...
Click to collapse
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
CCody said:
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
Click to expand...
Click to collapse
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
RawrNate said:
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
Click to expand...
Click to collapse
Jesus!
What about custom ROM? Cyanogenmod maybe? Make sure to downlaod the M7-Release.
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
RawrNate said:
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=tZbvuikfnks
CCody said:
https://www.youtube.com/watch?v=tZbvuikfnks
Click to expand...
Click to collapse
Oh good that was easier than I thought xD
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.
Earlier I was on Megapixel Rom running february vendor img. I flashed my PN ROM backup thru flashify then it boots up with my security lock pattern. It shows that my pattern is not correct. I am rebooting to y TWRP but still it doesn't show me any files and I cant flash a zip rom. Someone help me (((
Try using different decryption method...
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Gameplay_Ethan said:
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Click to expand...
Click to collapse
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
lesterinidad said:
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
Click to expand...
Click to collapse
factory reset?
v12xke said:
factory reset?
Click to expand...
Click to collapse
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
lesterinidad said:
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
Click to expand...
Click to collapse
See the sticky thread in General: https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
You might be better off flashing the full factory image to start over and then reflash whatever you want in terms of recovery and custom rom. I did that when I was in the same situation as you. But I have never successfully restored a nandroid backup on the 6P and I never had that problem with any other phone I have ever owned. Different versions of TWRP only give me different issues when I try to restore a backup. I've had bootloops. I've had TWRP ask for a password even though I removed security before making the back up as people advise. I've had backups that seemed to restore until I started getting error messages that there was something wrong with my device and I should contact the phone manufacturer. I've given up on Nandroid backups on this phone.