Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk
so...i'm in 8.1 and these is the conclusion in that state after few tests.
I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.
I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.
the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..
Related
I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
MM modified DM removed removed force/encryption and custom sepolicy to allow system root.
DOWNLOADS FOR 7.0 OFFICIAL
NRD90M(Decrypted)(System_root hopefully coming soon)
https://drive.google.com/file/d/0B4yuQy7Zn1WSYm5sTXNhZmsxcVk/view?usp=sharing
DOWNLOADS FOR MM
MTC20F(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSeVc1bjdDOGFETDA/view?usp=drivesdk
MTC19V(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSY3FZaVNXMjhEN2c/view?usp=drivesdk
MTC19T(System_Root)
https://drive.google.com/file/d/0B4yuQy7Zn1WSWXMyRHF1bGQ2YUU/view?usp=sharing
MCH19q
https://drive.google.com/file/d/0B4yuQy7Zn1WSclZ6dGhCNXNUUEk/view?usp=drivesdk
DOWNLOADS FOR ANDROID N Preview builds
NPD90G
https://www.androidfilehost.com/?fid=24572369242689017
NPD56N
https://drive.google.com/file/d/0B4yuQy7Zn1WSM3FORTl4ejlUV2M/view?usp=sharing
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSTklfZW1McXZxQUk/view?usp=drivesdk
NPC91k
https://drive.google.com/file/d/0B4yuQy7Zn1WSSG5WTGNBMHVvZXc/view?usp=sharing
DIRECTIONS
fastboot flash boot boot.img
Good to see your work here as well. :good:
Would love to see more.
F.A.Q - Frequent Answers and Questions
Bringing the love to 5x!!!
To users:
Don't question just follow his directions and profit
Sent from my Nexus 5x using XDA-Developers mobile app
Tigerstown said:
I own a nexus 6P and i have a few threads over there. one is for modified boot.imgs i have been getting a lot of PM asking if i could make one for the 5x so i did and it has been tested by @RTNDO128
So this is a decrypted and DM checks have been removed. flastboot this boot.img when flashing N preview factory imgs. Also i will be posting a MM modified boot.img the has DM removed removed force/encryption and custom sepolicy to allow system root. but for now here is the N boot.img
DIRECTIONS
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
To my knowledge you need to decrypt phone then flash N and before boot flash decrypt boot img then boot twrp then flash super su 2.71. To be decrypted rooted N.
Now to begin that process you need a decrypted phone which is why i am waiting for m decrypt boot begore i proceed.
Tigerstown can correct me if i am wrong.
Sent from my Nexus 5X using XDA-Developers mobile app
m.daziale said:
Hy guys, if i have the April N Preview on my n5X can i use this method to decrypt it? do i have to use only the code "fastboot flash boot boot.img" in fastboot (after have put my n5X in fastboot mode)? or do i have to compute some "erasing" in order to avoid bootloop?
i ask you that 'cause i want avoid to do the installation of N preview again
thnks Guys
Click to expand...
Click to collapse
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution
m.daziale said:
thanks a lot buddy i will try to do that, hoping in a not-bootloop solution
Click to expand...
Click to collapse
No bootloop guarantee, until you do something different than this. :victory:
DJBhardwaj said:
Yes, you can use this method to decrypt your 5X.
To begin, make sure that you have backed up everything on your internal storage, since everything will be removed. It will basically be like a fresh start.
Boot your 5X into bootloader mode and connect it to the PC.
Flash the modified boot.img (The one you have downloaded from above):
Code:
fastboot flash boot boot.img
After that is done, decrypt your 5X:
Code:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This is exactly what I was just going to reply. If your on N flash boot.IMG and decrypt using fastboot like said above.
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
Yes, perfectly alright. Avoid the recovery image, in case you have TWRP installed.
zipredictive said:
Awesome Im running android m with force encryption removed (fed patcher).
I want to upgrade it to N without loosing data : I think I have to flash THIS boot, recovery, Bootloader, vendor, cache, and system image files. I'm not flashing Userdata instead.
Is it right for having android N devrypted?
Click to expand...
Click to collapse
that is How I do it on my 6P. After flashing I boot to twrp and do factory reset myself. You don't need to flash the N recovery.
Sent from my Huawei Nexus 6P using XDA Labs
Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.
exploreresp said:
Many thanks @Tigerstown !!
This DP2 is actually really nice. I tried it with encryption, had a couple of bugs, but now unencrpyted, everything runs pretty smoothly and no bugs so far.
Love the new ergonomy improvements... no root needed anymore.
Click to expand...
Click to collapse
Hey no problem just glad to be helping out.
Sent from my Huawei Nexus 6P using XDA Labs
Op has been updated added MM MCH19q support. Still have to work on sepolicy for system root on 5x like I have it for 6P. Once I get it right I'll update with that.
Sent from my Huawei Nexus 6P using XDA Labs
aaaaand thanks again for the MM boot.img ! Glad to have both actually
Thanks for this, waiting for rootable version.
Hey thanks you for this
But if i flash only the modified boot on android n and i don't make a userdata wipe ?
What happen ?
khanjui said:
Thanks for this, waiting for rootable version.
Click to expand...
Click to collapse
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs
Tigerstown said:
Should have time tomorrow after work to get that done. Should is the key word ????. You feel like testing for me when I do? I have no 5X or I would of course do it myself. Lol
Sent from my Huawei Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I can test it.
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.
messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.
superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk
So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app
GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?
I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t
Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...
maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image
maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.
maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...
maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...
We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.
5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful
so i'm going thru the same thing as OP.
I need help.
So i wanted to try RR, but can't get it too install for some reason. I've been able to flash LineageOS, but every time I try RR I get an error message in TWRP.
Wondering what steps anyone with success has used. I followed the same steps as if I were installing LineageOS.
Thanks~
When I installed RR on my LG G2 a long time ago, it let me reduce the haptic vibration. Wonder if it would do this on the PH-1 too.
mpetruzz said:
So i wanted to try RR, but can't get it too install for some reason. I've been able to flash LineageOS, but every time I try RR I get an error message in TWRP.
Wondering what steps anyone with success has used. I followed the same steps as if I were installing LineageOS.
Thanks~
Click to expand...
Click to collapse
Wipe phone completely then flash twrp-7 and flash RR.
shooterlgk said:
Wipe phone completely then flash twrp-7 and flash RR.
Click to expand...
Click to collapse
Ok. I was using twrp 6 if that makes a difference. Thanks
mpetruzz said:
Ok. I was using twrp 6 if that makes a difference. Thanks
Click to expand...
Click to collapse
I unlocked the bootloader today, I was trying to install RR with twrp 6 and the other one that is on the root guide section. They won't install it. I tried with the 7 one and bingo. The only issue I'm facing I can't get twrp to stick, is either twrp or wifi gets broken.
Sent from my PH-1 using Tapatalk
Yeah I just tried with twrp 7 and it worked!!!
If you're gonna flash Magisk, use Invisiblek's hacked version. Thanks to The_Automator for pointing this out to me. https://forum.xda-developers.com/showthread.php?p=74701054
Sent from my PH-1 using Tapatalk
mpetruzz said:
Yeah I just tried with twrp 7 and it worked!!!
Click to expand...
Click to collapse
Were you able to keep twrp and wifi?
Sent from my PH-1 using Tapatalk
Nochis said:
Were you able to keep twrp and wifi?
Click to expand...
Click to collapse
I have WiFi but I haven't gotten as far as rooting so don't know about twrp
mpetruzz said:
I have WiFi but I haven't gotten as far as rooting so don't know about twrp
Click to expand...
Click to collapse
Ok thanks. Let me know if you try it.
Sent from my PH-1 using Tapatalk
Here is what you do.
From your ADB folder
Reboot to bootloader (adb reboot bootloader)
fastboot -w (completely wipes the device)
fastboot flash boot twrp.img (flashes TWRP, I renamed mata7 to twrp to make it easier)
Reboot into TWRP
adb shell twrp sideload (this starts sideload in TWRP)
adb sideload lineage-14.1-20171130_060947-UNOFFICIAL-mata.zip (this flashes the latest RR)
adb sideload magisk_14.3_invisiblekhax.zip (this is magisk that is tweaked properly)
Then reboot. Do no reflash TWRP as you have no reason to, and it breaks stuff.
This will work everytime, I've jumped from RR to Lineage to XenonHD without any issues at all.
Nochis said:
Ok thanks. Let me know if you try it.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Just flashed Magisk 14.3 and can confirm Wifi is broken, won't turn on.
Is there a trick to get it working or is it not on RR?
mpetruzz said:
Just flashed Magisk 14.3 and can confirm Wifi is broken, won't turn on.
Is there a trick to get it working or is it not on RR?
Click to expand...
Click to collapse
You have to flash the ROM again and magisk the one invisiblek provided. WiFi gets broken because you flashed twrp.
Sent from my Pixel 2 XL using Tapatalk
Nochis said:
You have to flash the ROM again and magisk the one invisiblek provided. WiFi gets broken because you flashed twrp.
Click to expand...
Click to collapse
I reflashed everything from scratch and it's all good now!!
Does work great but one problem is that i can't use TWRP for backups.
Turbojugend said:
Here is what you do.
From your ADB folder
Reboot to bootloader (adb reboot bootloader)
fastboot -w (completely wipes the device)
fastboot flash boot twrp.img (flashes TWRP, I renamed mata7 to twrp to make it easier)
Reboot into TWRP
adb shell twrp sideload (this starts sideload in TWRP)
adb sideload lineage-14.1-20171130_060947-UNOFFICIAL-mata.zip (this flashes the latest RR)
adb sideload magisk_14.3_invisiblekhax.zip (this is magisk that is tweaked properly)
Then reboot. Do no reflash TWRP as you have no reason to, and it breaks stuff.
This will work everytime, I've jumped from RR to Lineage to XenonHD without any issues at all.
Click to expand...
Click to collapse
There's gotta be a way to do it w/o having to wipe internal storage! I have 100gb of stuff I don't want to erase and then move back all the time.
Kochoa940 said:
There's gotta be a way to do it w/o having to wipe internal storage! I have 100gb of stuff I don't want to erase and then move back all the time.
Click to expand...
Click to collapse
Just wipe with TWRP. U don't need to do the adb -w.
Sent from my PH-1 using Tapatalk
Airwolf79 said:
Just wipe with TWRP. U don't need to do the adb -w.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Do you mean I don't have to do the fastboot -w?
Kochoa940 said:
Do you mean I don't have to do the fastboot -w?
Click to expand...
Click to collapse
Yes. The steps that Turbojugend posted are just one way of doing it. You can also just download the ROM to ur phone, then wipe, and flash it in TWRP. The only adb step u need is to flash TWRP, if u haven't done that already. If u want root, just make sure u flash Invisiblek's hacked Magisk version, which saves u from having to flash Magisk to the other partition, and keeps the boot.img intact.
Sent from my PH-1 using Tapatalk
Airwolf79 said:
Yes. The steps that Turbojugend posted are just one way of doing it. You can also just download the ROM to ur phone, then wipe, and flash it in TWRP. The only adb step u need is to flash TWRP, if u haven't done that already. If u want root, just make sure u flash Invisiblek's hacked Magisk version, which saves u from having to flash Magisk to the other partition, and keeps the boot.img intact.
Click to expand...
Click to collapse
So all this can be done from slot A?
Hi there XDA, I've recently been having issues with custom roms and random reboots, so I decided to go back to stock. Going back to stock I used fastboot to flash the system and boot images. After some setup I wanted to get root. Instead of there being twrp I ended up with the stock recovery somehow. TWRP 3.1.1 seemed to stick, then I decided to upgrade to the most recent version. And it no longer sticks(TWRP recovery).
I just don't know what to do or what the cause for this to happen may be. My only thought is that I'll have to fastboot flash recovery every time I want to modify something.
Any way you guys would be willing to shed some light on what's going on for me???
Sent from my SM-N7507 using Tapatalk
probably since you are not rooted
@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.
wizardwiz said:
probably since you are not rooted
Click to expand...
Click to collapse
Nah, I'm rooted through magisk
Exodusche said:
@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.
Click to expand...
Click to collapse
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.
double post
dirtyreturn said:
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.
Click to expand...
Click to collapse
So your flashing twrp after first boot, rooting and still won't stick?
Exodusche said:
So your flashing twrp after first boot, rooting and still won't stick?
Click to expand...
Click to collapse
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
Who knows maybe google changed something. Do it my way and you will be fine.
dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
When you flash system and boot images, root is removed. On Oreo, TWRP does not persist without root being maintained. I believe on Nougat or Marshmallow, this was not the case. When you booted into the stock rom, this restored the stock recovery.
Flash TWRP then boot directly into TWRP and flash Magisk. When installing new security patches, boot directly into TWRP and reinstall root.
Sent from my Nexus 5X using Tapatalk
any help ?