Related
Hey. I had rooted 5.1.1 Moto X Style and did a return to stock 5.1.1. eu version (relocked bootloader). After booted up, I received update to Marshmallow, I installed it. It worked. Later I wanted to root it, so I unlocked bootloader again and also did flash custom recovery - TWRP (twrp-2.8.7.1-clark). Later I restarted device and its was stuck on logo of Motorola. Nothing boots up.
Cant find solution for this. Thanks.
UPDATE:
Solved my issue here.
UPDATE2:
If there is problems upgrading your device to Marshmallow, I would suggest install custom ROM TruPureXMM with custom KERNEL Frankenclark. I am using this combo for long period of time and now I can suggest to others too!
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
dgato said:
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
Click to expand...
Click to collapse
You need to reflash the LP radio from the restore all file ( NON-HLOS.bin ). That should do it.
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
JayShams said:
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
Click to expand...
Click to collapse
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
ChadMan097 said:
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
Click to expand...
Click to collapse
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
JayShams said:
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
Click to expand...
Click to collapse
Nop, could find solution, so I did full wipe, and restored my backup file with 5.1.1. Also flashed stock logo, boot and modem, so it can boot my old 5.1.1. Moto.
Will wait for some kind of european ROM with Marshmallow, or TWRP update. Maybe later will try again to go fully stock and upgrade to Marshmallow, maybe will find something that will work, right now I just need my "phone" back so I can use it as daily driver.
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
JayShams said:
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
Click to expand...
Click to collapse
For wifi you should flash modem from his thread: https://www.androidfilehost.com/?fid=24269982087017262
Its Pure modem with band 12 fix.
I was using his Rom for some hours and didnt like it, my personal opinion:
Good: easy to install; twrp, supersu, xposed is working.
Bad: modified kernel (had more problems with it, it was draining battery so fast - 4 little cores was always online for ~900-1440MHz, and 1 big core always online for same frequancy as little cores, only one big core was going idle), so I didnt like all this modifications to stock kernel, also I didnt like that mine EU version now is listed as US version XT1575, and last that I noticed after some hours of usage is that on secret menu, mine 3G network was listed as WCDMA, but on EU of mine Style same 3G is using GSM auto method. I suppose that there can be some difficulties in EU countries - after changing settings to 4G, I loosed signal, and only after restart I got it back.
Thats the main reasons why I want european rom, or to modifie stock eu MM with xposed.
patt2k said:
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
Click to expand...
Click to collapse
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
ChadMan097 said:
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
Click to expand...
Click to collapse
Either do systemless or 2.52 had same issue til I flashed 2.52
Sent from my XT1575 using Tapatalk
Solved my issue here.
BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
donebrasko said:
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Click to expand...
Click to collapse
For this you need adb files on your PC.
You should read this thread, for how to get this files on your PC.
Then:
Basically, open terminal within adb driver folder, connect phone via USB to PC with USB Debugging ON, and you are ready to go - boot your phone into fastboot mode (shut down phone first, and then power+volume down) and now your are ready to use this command: fastboot flash modem NON-HLOS.bin, but remember to put this "NON-HLOS.bin" file into folder where you opened terminal from.
But if you experience problems, I suggest just install TruPureXMM ROM. It whould be much easier!
Good luck!
Kennyeni said:
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
Click to expand...
Click to collapse
Hello!
Have you read my other thread?
I have explained all my steps there, my device is Moto X Style (XT1572).
But I can suggest also use TruPureXMM ROM. Right now I am using this rom for about month, you could try it!
Good luck!
No luck with reflashing NON-HLOS.bin
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
[email protected]@lker said:
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
Click to expand...
Click to collapse
Lets start from beginning.
What is your device codename (region)?
I had installed cm 13 and tried installing a new kernel but i guess since i was on a old version it didn't work out. So i proceeded with putting the old kernel back *sandy kernel* however now when the phone opens up i put my pass code it shows the background for a split second with a system ui crashed error and back to lock screen. hence i tried installing a recovery again (twrp hybrid) since the latest roms use that and I wanted a new rom anyway. But i thought id back my stuff up but alas the system ui error doesn't allow me to do so. Finally i ended up by using fastboot to flash the new recovery but even after it said OK ! my phone won't boot into recovery.
So now i am stuck with a OP2 that boots into cm13 but cant get past the lockscreen, a recovery that won't load and a fastboot mode that is the only working thing.
God I really shouldve backed it up i know. But is there a way I can resolve this without losing my data?
I have an exam and the notes are in them.
Help is appreciated !
rogermax said:
I had installed cm 13 and tried installing a new kernel but i guess since i was on a old version it didn't work out. So i proceeded with putting the old kernel back *sandy kernel* however now when the phone opens up i put my pass code it shows the background for a split second with a system ui crashed error and back to lock screen. hence i tried installing a recovery again (twrp hybrid) since the latest roms use that and I wanted a new rom anyway. But i thought id back my stuff up but alas the system ui error doesn't allow me to do so. Finally i ended up by using fastboot to flash the new recovery but even after it said OK ! my phone won't boot into recovery.
So now i am stuck with a OP2 that boots into cm13 but cant get past the lockscreen, a recovery that won't load and a fastboot mode that is the only working thing.
God I really shouldve backed it up i know. But is there a way I can resolve this without losing my data?
I have an exam and the notes are in them.
Help is appreciated !
Click to expand...
Click to collapse
Please use the following Guide. Method 1 should be your answer. https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
toxicore said:
Please use the following Guide. Method 1 should be your answer. https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
sir thats a 1gb file and im on data net right now. I'll download it but are you sure it will resolve my issue ?
Just download latest oxygen or cyanogenmod recovery and flash in fastboot it will sure boot to recovery
paradise220 said:
Just download latest oxygen or cyanogenmod recovery and flash in fastboot it will sure boot to recovery
Click to expand...
Click to collapse
thank you for your help sir, even though i tried flashing all kinds of recoveries via fastboot, it says the flash was successful but it still doesn't boot into recovery. Any other suggestions ?
rogermax said:
thank you for your help sir, even though i tried flashing all kinds of recoveries via fastboot, it says the flash was successful but it still doesn't boot into recovery. Any other suggestions ?
Click to expand...
Click to collapse
As I said. the method i showed you is most certainly the solution. But you need a Computer and yes, 1gb is propably too much for mobile data
Maybe, just maybe if you flash OOS-Firmware it might help. But i dont know for sure.
So i finally managed to get into twrp 2.8.7 (lollipop)by this http://forum.xda-developers.com/devdb/project/dl/?id=16684
thanks a lot for all your hard work guys ! (cant boot into os still but twrp will help atleast)
so i was on RR official rom and i wanted to try AEX so i flashed it as usual but i wanted to revert back to RR so i wiped everything and flashed the Oreo firmware zip and then restored the RR backup and rebooted the phone.....
but i was stuck on the boot logo so i clean flashed the rom zip file but no use
i also tried LOS15.1 zip file but still i was stuck on the boot logo
i tried to flash the 7.12.7 nougat fastboot rom through Mi flash the rom booted but started to reboot at the time of selecting network during setup
i did some research and found out many users had this issue and they flashed persist.img
i tried the same using the TWRP method but still no use
i even flashed the Oreo beta through the Jamflux tool but even that kept rebooting at the time of setup
plz help me out
TY in advance
clean all and lock option could be helpful !
leo_pard2331 said:
so i was on RR official rom and i wanted to try AEX so i flashed it as usual but i wanted to revert back to RR so i wiped everything and flashed the Oreo firmware zip and then restored the RR backup and rebooted the phone.....
but i was stuck on the boot logo so i clean flashed the rom zip file but no use
i also tried LOS15.1 zip file but still i was stuck on the boot logo
i tried to flash the 7.12.7 nougat fastboot rom through Mi flash the rom booted but started to reboot at the time of selecting network during setup
i did some research and found out many users had this issue and they flashed persist.img
i tried the same using the TWRP method but still no use
i even flashed the Oreo beta through the Jamflux tool but even that kept rebooting at the time of setup
plz help me out
TY in advance
Click to expand...
Click to collapse
Flash command fastboot userdata.img of rom stock oreo
laugeek57 said:
Flash command fastboot userdata.img of rom stock oreo
Click to expand...
Click to collapse
i extracted and flashed the userdata.img from the stock oreo rom but still the phone is rebooting i m on the latest stock rom
Custom rom 243 said:
clean all and lock option could be helpful !
Click to expand...
Click to collapse
i already have tried that but no use
leo_pard2331 said:
i already have tried that but no use
Click to expand...
Click to collapse
Have you tried with a stock rom getting installed in fastboot mode?
laugeek57 said:
Have you tried with a stock rom getting installed in fastboot mode?
Click to expand...
Click to collapse
yes i tried to install the stock Oreo 7.12.29 rom using mi flash tool
actually i am currently on the latest Oreo rom and my phone is restarting
laugeek57 said:
Have you tried with a stock rom getting installed in fastboot mode?
Click to expand...
Click to collapse
i flashed the firmware zip from this link:https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
but i wasnt on 7.12.29 at that moment i was on the OPR1.170623.026.8.1.10-beta build flashed by Jamflux's tool do you think that might have caused the problem?
leo_pard2331 said:
i flashed the firmware zip from this link:https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
but i wasnt on 7.12.29 at that moment i was on the OPR1.170623.026.8.1.10-beta build flashed by Jamflux's tool do you think that might have caused the problem?
Click to expand...
Click to collapse
I don't know Buddy i use last oreo stock 9.5.9 stable dev
Be careful when you flash a 8.1 I tested the Pixel Experience rom I flash userdata.img from oreo for my phone to restart ... otherwise bootloop
laugeek57 said:
I don't know Buddy i use last oreo stock 9.5.9 stable dev
Be careful when you flash a 8.1 I tested the Pixel Experience rom I flash userdata.img from oreo for my phone to restart ... otherwise bootloop
Click to expand...
Click to collapse
so basically this is my condition right now...
if i flash stock rom i get frequent reboots
and if i flash custom roms i get bootloop :crying:
can i claim my warranty if i flashed the stock rom and locked the bootloader?
leo_pard2331 said:
so basically this is my condition right now...
if i flash stock rom i get frequent reboots
and if i flash custom roms i get bootloop :crying:
can i claim my warranty if i flashed the stock rom and locked the bootloader?
Click to expand...
Click to collapse
Attempt to re-install through a newer Oreo image in either fastboot
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
laugeek57 said:
Attempt to re-install through a newer Oreo image in either fastboot
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Click to expand...
Click to collapse
nevermind i was able to fix the issue by flashing the persist.img :laugh:
anyway thank you very much for your help
leo_pard2331 said:
nevermind i was able to fix the issue by flashing the persist.img :laugh:
anyway thank you very much for your help
Click to expand...
Click to collapse
Well done
Hey guys, VERY new to the phone customization game. I gave rooting my ph-1 a shot and it crashed and burned. I tried flashing Magisk with no luck and now my WiFi will not turn on. It is stuck I the off position. This is incredibly frustrating. I tried restoring the phone and nothing seems to be working. Anyone out there able to help?
Silver1212 said:
Hey guys, VERY new to the phone customization game. I gave rooting my ph-1 a shot and it crashed and burned. I tried flashing Magisk with no luck and now my WiFi will not turn on. It is stuck I the off position. This is incredibly frustrating. I tried restoring the phone and nothing seems to be working. Anyone out there able to help?
Click to expand...
Click to collapse
Flash Back to stock zip from Development Section.
You should be good to start experimenting again..
:laugh:
indian84 said:
Flash Back to stock zip from Development Section.
You should be good to start experimenting again..
:laugh:
Click to expand...
Click to collapse
I tried flashing OPM1.180104.166 AFH from @invisiblek (that's the latest 8.1 Oreo) the problem is still there. WiFi Won't toggle on. Should I flash the earliest build? NM181C?
Silver1212 said:
I tried flashing OPM1.180104.166 AFH from @invisiblek (that's the latest 8.1 Oreo) the problem is still there. WiFi Won't toggle on. Should I flash the earliest build? NM181C?
Click to expand...
Click to collapse
Did you do critical flashing unlock?
If you have messed up with the modem, without critical flashing unlock, it would not flash modem partitions
indian84 said:
Did you do critical flashing unlock?
If you have messed up with the modem, without critical flashing unlock, it would not flash modem partitions
Click to expand...
Click to collapse
Are you referring to unlocking the bootloader? If so then yes I did that.
Silver1212 said:
Are you referring to unlocking the bootloader? If so then yes I did that.
Click to expand...
Click to collapse
Nope. Not only bootloader. You have to unlock critical.
Read below.
http://mata.readthedocs.io/en/latest/
Silver1212 said:
Hey guys, VERY new to the phone customization game. I gave rooting my ph-1 a shot and it crashed and burned. I tried flashing Magisk with no luck and now my WiFi will not turn on. It is stuck I the off position. This is incredibly frustrating. I tried restoring the phone and nothing seems to be working. Anyone out there able to help?
Click to expand...
Click to collapse
You have a firmware mismatch...
Because I don't think you can boot the device into the OS with the TWRP kernel anymore...
Which I'm pretty sure means you missed unlock critical...
And didn't read the output from the terminal window after running the flashall
rignfool said:
You have a firmware mismatch...
Because I don't think you can boot the device into the OS with the TWRP kernel anymore...
Which I'm pretty sure means you missed unlock critical...
And didn't read the output from the terminal window after running the flashall
Click to expand...
Click to collapse
Is there a way to bring this thing back to original bare bones stock? Are there tutorials around for that?
Silver1212 said:
Is there a way to bring this thing back to original bare bones stock? Are there tutorials around for that?
Click to expand...
Click to collapse
Just like you unlocked the bootloader, you now need unlock_critical.
Then go through the flash procedure.
Silver1212 said:
Is there a way to bring this thing back to original bare bones stock? Are there tutorials around for that?
Click to expand...
Click to collapse
1) boot to bootloader
2) fastboot flashing unlock
3) fastboot flashing unlock_critical
4) get the latest rom 9OPM1.180104.166 AFH from @invisiblek) and use flash all.
I had this same issue when flashing the wrong version boot image. Downloaded correct boot image, flashed and then flashed Magisk and fixed her right up.
xorwin said:
1) boot to bootloader
2) fastboot flashing unlock
3) fastboot flashing unlock_critical
4) get the latest rom 9OPM1.180104.166 AFH from @invisiblek) and use flash all.
Click to expand...
Click to collapse
Okay so this is the current situation:
I typed in:
1) fastboot flashing unlock - everything looked as it should.
2) fastboot flashing unlock_critical - the script ran and then said: FAILED (remote : device already : unlocked!)
3) I went forward with the flash-all-WIPE and the issue is still not corrected. I honestly don't know what else to do here.
I wholeheartedly appreciate all the help so far! Id like to figure this out!
GOT IT! WOOOO! Thanks guys!
Silver1212 said:
GOT IT! WOOOO! Thanks guys!
Click to expand...
Click to collapse
Hi Silver1212, Please can you advice how did you fix this issue? I did the following as you did too:
1) flashboot flashing unlock
2) flashboot flashing unlock_critical
3) bash flashall.sh
It completed with no errors, but wifi still won't turn on
What did you have to do to fix this problem?
zenga_82 said:
Hi Silver1212, Please can you advice how did you fix this issue? I did the following as you did too:
1) flashboot flashing unlock
2) flashboot flashing unlock_critical
3) bash flashall.sh
It completed with no errors, but wifi still won't turn on
What did you have to do to fix this problem?
Click to expand...
Click to collapse
Use the flashall wipe
zenga_82 said:
Hi Silver1212, Please can you advice how did you fix this issue? I did the following as you did too:
1) flashboot flashing unlock
2) flashboot flashing unlock_critical
3) bash flashall.sh
It completed with no errors, but wifi still won't turn on
What did you have to do to fix this problem?
Click to expand...
Click to collapse
Do a reset of all your network settings. It fixed it for me some time back earlier this year
my nexus 6p just recently crashed while using it, and began to boot loop.
the only thing i can do is boot to fastboot. no splash screen, no recovery.
rom installed was StatixOS android pie, Recovery was TWRP 3.2.3-0, and rooted with Magisk 17.
i had everything except for magisk for a week or so, before eventually flashing magisk, and used it for about another week until now.
i know statixOS rom informed of flashing a BLOD fix if i was on 4 cores, which i did not do since, to my knowledge, i was still using all 8. i am aware of the 6p having bootlooping issues and have tried flashing the fix from here: https://www.xda-developers.com/nexus-6p-bootloop-fix/
i have also tried the modified recovery.img from the statixOS post with no results.
any help would be apreciated.
Okay, something similar happened to me today. The only difference being that I just flashed Magisk and it started happening immediately. I am able to flash a system image and get it to boot once. But Once booted though it loses the recovery. So I tried flashing the twrp before that first boot which asks for a password to decrypt the device and it was not encrypted in the first place. Any password I tell it just erases is the phone next time it boots. If I leave the system image I can get one good boot. So this boot is good I can load my info to the phone but it has so little battery that it dies before I can do much else. Once dead if I try to boot it, it loops. So I flash another system image and the cycle repeats. So I also tried flashing a stock image then adb sideloading a custom ROM and although the progress bar on the phone fills up, the percentage that my dos window shows only gets to about 46%. The phone states that it loaded successfully but the ROM won't boot. I think this is because its encrypted? That's just a guess, as I am no dev of any kind.
I don't think your issue is caused by the same problem.
Yours might be caused by magic, and I've read v17 has had issues in the past.
I can't get into recovery at all, regardless of what I flash.
Even the nodded versions of tarp to use 4 cores.
RTyper56 said:
my nexus 6p just recently crashed while using it, and began to boot loop.
the only thing i can do is boot to fastboot. no splash screen, no recovery.
rom installed was StatixOS android pie, Recovery was TWRP 3.2.3-0, and rooted with Magisk 17.
i had everything except for magisk for a week or so, before eventually flashing magisk, and used it for about another week until now.
i know statixOS rom informed of flashing a BLOD fix if i was on 4 cores, which i did not do since, to my knowledge, i was still using all 8. i am aware of the 6p having bootlooping issues and have tried flashing the fix from here: https://www.xda-developers.com/nexus-6p-bootloop-fix/
i have also tried the modified recovery.img from the statixOS post with no results.
any help would be apreciated.
Click to expand...
Click to collapse
well i think this same thing happened to me while trying to flash the same rom, the only other issue is that my vol down doesnt work so i have no way of booting into fastboot that i am aware of. my phone is useless now.
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
i think there is something wrong with that modded recovery and rom. this is kinda strange.
My 6p also crashed after flashing the latest statix os and magisk. It crashed in the middle of the night. Now it goes into indefinite bootloop showing the google logo and warning screen. I tried flashing stock firmware several times and also the 4 core patch but still no signs of life. Please update if anyone has a fix. Tried the 4 core twrp too. but cant get even to the recovery.
Sterben Pistole said:
well i think this same thing happened to me while trying to flash the same rom, the only other issue is that my vol down doesnt work so i have no way of booting into fastboot that i am aware of. my phone is useless now.
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
i think there is something wrong with that modded recovery and rom. this is kinda strange.
Click to expand...
Click to collapse
You need to open the phone, I know it sucks.
Anyhow, I just managed to help one member from the StatiXOS community by let him flash this recovery.
Try to flash it via fastboot and try to boot up into recovery.
imjuz4you said:
My 6p also crashed after flashing the latest statix os and magisk. It crashed in the middle of the night. Now it goes into indefinite bootloop showing the google logo and warning screen. I tried flashing stock firmware several times and also the 4 core patch but still no signs of life. Please update if anyone has a fix. Tried the 4 core twrp too. but cant get even to the recovery.
Click to expand...
Click to collapse
Did you wipe the internal storage after you flashed StatiXOS? This step is necessary.
oshithedead said:
Did you wipe the internal storage after you flashed StatiXOS? This step is necessary.
Click to expand...
Click to collapse
I was running Statix rom for a day before it crashed on me. I installed magisk and the EX kernel on top of the statix build. My phone crashed in the middle of the night while i was sleeping.
I found my phone low on battery next morning and when i put the phone on charging I found it bootlooping endlessly.
I tried entering recovery through bootloader but phone was not going into recovery. No matter what option i click on the bootloader i.e. factory reset or recovery, it shows the warning screen and then the google logo and restarts to do the same. I tried flashing stock rom and it flashes without any errors. But still the same result, BOOTLOOP. I cannot get my phone into recovery be it stock or twrp.
I even tried flashing the 4 core recovery in the OP, but 6p is still adamant on the bootloop cycle.
RTyper56 said:
my nexus 6p just recently crashed while using it, and began to boot loop.
the only thing i can do is boot to fastboot. no splash screen, no recovery.
rom installed was StatixOS android pie, Recovery was TWRP 3.2.3-0, and rooted with Magisk 17.
i had everything except for magisk for a week or so, before eventually flashing magisk, and used it for about another week until now.
i know statixOS rom informed of flashing a BLOD fix if i was on 4 cores, which i did not do since, to my knowledge, i was still using all 8. i am aware of the 6p having bootlooping issues and have tried flashing the fix from here: https://www.xda-developers.com/nexus-6p-bootloop-fix/
i have also tried the modified recovery.img from the statixOS post with no results.
any help would be apreciated.
Click to expand...
Click to collapse
typical thing happened to my phone yesterday guess the phone is dead for good cause i did everything that possible same as your procedures with no luck whatsoever
imjuz4you said:
I was running Statix rom for a day before it crashed on me. I installed magisk and the EX kernel on top of the statix build. My phone crashed in the middle of the night while i was sleeping.
I found my phone low on battery next morning and when i put the phone on charging I found it bootlooping endlessly.
I tried entering recovery through bootloader but phone was not going into recovery. No matter what option i click on the bootloader i.e. factory reset or recovery, it shows the warning screen and then the google logo and restarts to do the same. I tried flashing stock rom and it flashes without any errors. But still the same result, BOOTLOOP. I cannot get my phone into recovery be it stock or twrp.
I even tried flashing the 4 core recovery in the OP, but 6p is still adamant on the bootloop cycle.
Click to expand...
Click to collapse
there's your problem. Don't install any custom kernels, especially since EX hasn't been updated for Pie. Also, you may have a dud battery. Have you re-flashed TWRP?
oshithedead said:
there's your problem. Don't install any custom kernels, especially since EX hasn't been updated for Pie. Also, you may have a dud battery. Have you re-flashed TWRP?
Click to expand...
Click to collapse
My current situation is that no matter what i flash through my bootloader, let it be twrp, stock rom, 4 core recovery or each individual file from the stock image through fastboot commands, it restarts to bootloop.
My battery was replaced few months back and was giving me solid standby time, so cant blame it. All i am trying is to get to boot my phone to recovery which it refuses. Cant understand whether its the file system that is damaged, but my flashes returns me no error, and also i formatted through fastboot whichever partition i could. Still cant see any life.
I am having the same issue. I was running Statix with no custom kernel or magisk for about a week. My device just randomly went into boot loop. I tried to flash back to stock file by file... still bootloop. I flashed that 4 core patch and the twrp... still bootloop. I can get into recovery, but I don’t know what to do from there because no matter what I flash, it always ends up in bootloop. Any ideas?
Jertlok said:
You need to open the phone, I know it sucks.
Anyhow, I just managed to help one member from the StatiXOS community by let him flash this recovery.
Try to flash it via fastboot and try to boot up into recovery.
Click to expand...
Click to collapse
Do you have any other suggestion than this? It doesn't seem to work.:crying:
imjuz4you said:
Do you have any other suggestion than this? It doesn't seem to work.:crying:
Click to expand...
Click to collapse
did you ever get this figured out had the exact same thing just happen to me.