For those who have problems trying to update their devices to Android Nougat, here you can download the recovery and fastboot images of the latest upgrade TOS089A.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
OTA UPGRADE ZIP (UNOFFICIAL LINK by /u/WhyLeeFox)https://drive.google.com/file/d/0B0Lwu25d1bgoNU5vZTlMcnBWN1k/view (from 7aa1c7975e to decf3a575d)
Have fun, and don't forget to debloat your system
linuxct said:
For those who have problems trying to update their devices to Android Nougat, here you can download the recovery and fastboot images of the latest upgrade TOS089A.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
OTA UPGRADE ZIP (UNOFFICIAL LINK by /u/WhyLeeFox)https://drive.google.com/file/d/0B0Lwu25d1bgoNU5vZTlMcnBWN1k/view (from 7aa1c7975e to decf3a575d)
Have fun, and don't forget to debloat your system
Click to expand...
Click to collapse
Does this work for the swift 2 x?
seannorri said:
Does this work for the swift 2 x?
Click to expand...
Click to collapse
Indeed, it's compatible with all marmite devices (Swift 2, 2 Plus and 2X).
When i flash the recovery or the fastboot image, is then all my data and everything lost or not??
I had a Nexus 5 that i have flash several times and nothing was lost. I hope it can als on a wileyfox.
RiesVLD said:
When i flash the recovery or the fastboot image, is then all my data and everything lost or not??
I had a Nexus 5 that i have flash several times and nothing was lost. I hope it can als on a wileyfox.
Click to expand...
Click to collapse
For the recovery image, it doesn't delete the user data partition. However, I think there's a userdata image in the fastboot images zip, so, if you flash everything except that one I think it should work and won't delete your data.
linuxct said:
For the recovery image, it doesn't delete the user data partition. However, I think there's a userdata image in the fastboot images zip, so, if you flash everything except that one I think it should work and won't delete your data.
Click to expand...
Click to collapse
Thanks for your answer, but none of the opties works for me. i stay stuck on the logo. When i get into recovery i see there's nothing on internal storage. I have riple flasht Recovery Image, triple Fastboot image (Without the userdata.img) en at last triple the ota image.
Matbe i must do a clean install en set everything back, it takes a lot of time, but these options also.
RiesVLD said:
Thanks for your answer, but none of the opties works for me. i stay stuck on the logo. When i get into recovery i see there's nothing on internal storage. I have riple flasht Recovery Image, triple Fastboot image (Without the userdata.img) en at last triple the ota image.
Matbe i must do a clean install en set everything back, it takes a lot of time, but these options also.
Click to expand...
Click to collapse
I think the problem is that DM-verity is active, preventing you to boot up the phone. Try flashing Magisk after flashing the recovery image again, for example.
linuxct said:
I think the problem is that DM-verity is active, preventing you to boot up the phone. Try flashing Magisk after flashing the recovery image again, for example.
Click to expand...
Click to collapse
I have flashing Magisk, but it's not working. The DM is working and i can not turn it off. Is flashing Magisk enough to keep the DM away??
RiesVLD said:
I have flashing Magisk, but it's not working. The DM is working and i can not turn it off. Is flashing Magisk enough to keep the DM away??
Click to expand...
Click to collapse
If the phone boots up (like, it's not bootlooping), but the warning appears, it's absolutely fine.
seannorri said:
Does this work for the swift 2 x?
Click to expand...
Click to collapse
unfortunately the link is down
RayfG said:
unfortunately the link is down
Click to expand...
Click to collapse
None of them is.
duplicated post... turns out a rc can't delete a post so yup. This is staying here.
linuxct said:
None of them is.
Click to expand...
Click to collapse
Yes, sure everything works fine,
Was a prob due to my internet.
Greetz
Related
Hey I'm trying to install TWRP on the latest Android N preview and whenever I reboot from boot loader into recovery TWRP loading screen just hangs.
I read online that you need to decrypt but how would I do that?
same problem here :/
Had the same problem, flashed this http://rootjunkysdl.com/getdownload.php?file=Nexus%206P%20Angler/Android%20N%20Preview/Angler%20npc56p%20Remove%20Encryption.zip with fastboot and it worked.
Techno Peter said:
Had the same problem, flashed this http://rootjunkysdl.com/getdownload.php?file=Nexus%206P%20Angler/Android%20N%20Preview/Angler%20npc56p%20Remove%20Encryption.zip with fastboot and it worked.
Click to expand...
Click to collapse
You will first need to disable forced encryption, and then decrypt the 6P running Android N Dev Preview: http://www.droidorigin.com/decrypt-nexus-6p/
DJBhardwaj said:
You will first need to disable forced encryption, and then decrypt the 6P running Android N Dev Preview: http://www.droidorigin.com/decrypt-nexus-6p/
Click to expand...
Click to collapse
I love Droid Origin! Thanks I'll take a look
Techno Peter said:
Had the same problem, flashed this http://rootjunkysdl.com/getdownload...N Preview/Angler npc56p Remove Encryption.zip with fastboot and it worked.
Click to expand...
Click to collapse
What is the proper command to flash this in fastboot?
poor2rican1 said:
What is the proper command to flash this in fastboot?
Click to expand...
Click to collapse
I renamed the image in the folder to boot.img and flashed it with "fastboot flash boot boot.img"
ZacksBuilds said:
Hey I'm trying to install TWRP on the latest Android N preview and whenever I reboot from boot loader into recovery TWRP loading screen just hangs.
I read online that you need to decrypt but how would I do that?
Click to expand...
Click to collapse
Dont know if you fixed the issue but i posted on another thread my experience and found that reverting back to twrp 3.0 was my fix. Flashed in fastboot. To decrypt I flashed the midified boot.img and than twrp and than formatted data to decrypt. Hope it helps.
Is there a way to root NCP91K version of N
I believe we need a special image or boot loader file. Please point me in the right direction.
pospower said:
Is there a way to root NCP91K version of N
I believe we need a special image or boot loader file. Please point me in the right direction.
Click to expand...
Click to collapse
Hello pospower,
I hope you are new to the community, so first of all, welcome to the Nexus 6P section.
I advise you to read the sticky threads here at the section. First in the list would be: http://forum.xda-developers.com/nexus-6p/general/questions-section-t3214020
Over to your query now. Bootloader has no relation to rooting, except one, that it should be unlocked. Unlocking the bootloader will enable you to flash TWRP recovery, which in turn would be used to flash SuperSU v2.71 flash-able zip.
For detailed instructions, please refer to section #1, #2, and #6 in the following thread: [GUIDE] Unlock/Root/Flash for Nexus 6P
I hope this helps. Best regards.
DJBhardwaj
boot.img my bad i was refering to this below
Download the latest TWRP Recovery. Please note: if you're on MHC19I or above you must use TWRP 3.0.0-1 or above, otherwise TWRP won't be able to decrypt. Also, if you want to use TWRP with the Android N Developer Preview you must use TWRP 3.0.0-1 or above, and you must also flash the modified boot.img found here.
ok got twrp installed 3.0.2.0
flashed the boot.img from above post
flashed twrp.img
rebooted bootloader
rebooted into recocery but freezws on teamwin screen
pospower said:
ok got twrp installed 3.0.2.0
flashed the boot.img from above post
flashed twrp.img
rebooted bootloader
rebooted into recocery but freezws on teamwin screen
Click to expand...
Click to collapse
TWRP is having issues with encrypted filesystems right now. You can either flash TWRP v3.0.0 or decrypt your 6P.
The decryption process should be carried out just after you flash the modified boot.img.
To decrypt, you will need to connect your device in bootloader mode and enter the following command:
Code:
fastboot format userdata
(Please note that this will wipe your complete internal storage).
OK got twrp working 3.0.0
Now it's asking for a password to get to decrypted files.
Any suggestions?
pospower said:
OK got twrp working 3.0.0
Now it's asking for a password to get to decrypted files.
Any suggestions?
Click to expand...
Click to collapse
Did you decrypt your device? Check under Settings > Security > Encrypt phone. Is it showing "encrypted"?
DJBhardwaj said:
Did you decrypt your device? Check under Settings > Security > Encrypt phone. Is it showing "encrypted"?
Click to expand...
Click to collapse
I must have
pospower said:
I must have
Click to expand...
Click to collapse
Please confirm.
And by decryption, i mean that you first flashed the modified boot.img and then formatted the userdata.
DJBhardwaj said:
Please confirm.
And by decryption, i mean that you first flashed the modified boot.img and then formatted the userdata.
Click to expand...
Click to collapse
Yes this is what I did. Followed the steps exactly.
pospower said:
Yes this is what I did. Followed the steps exactly.
Click to expand...
Click to collapse
Give a try to v3.0.0-1, and let me know.
DJBhardwaj said:
Give a try to v3.0.0-1, and let me know.
Click to expand...
Click to collapse
tried 3.0.0-1 woudnt start froze on twrp screen
do i need to decryp data again?
pospower said:
tried 3.0.0-1 woudnt start froze on twrp screen
do i need to decryp data again?
Click to expand...
Click to collapse
If you don't mind doing it, I would say Yes!
reflshed boot.img
decrpted
rebooted
copied su to download folder
reflashe boot then twrp 3.0.0 rebooted boot then to recovery againg asking for password to decriped data
ugggg
pospower said:
reflshed boot.img
decrpted
rebooted
copied su to download folder
reflashe boot then twrp 3.0.0 rebooted boot then to recovery againg asking for password to decriped data
ugggg
Click to expand...
Click to collapse
That is weird. I have done the same thing like twice or thrice since the last two days, and it has worked like a charm.
If you're decrypted, TWRP v3.0.0-1 should work fine.
Are you sure you wiped complete storage using fastboot format userdata command?
Yes
pospower said:
Yes
Click to expand...
Click to collapse
Try switching to a different version of TWRP, and see if any one of them works for you.
v3.0.0-1, v3.0.1-0, or v3.0.2-0.
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.
d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).
nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.
nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
As far as i remember there were 2 files. dm-verity and forced encryption. I never needed them but if you stay on stock you will have to flash those so that twrp doesn't get replaced by stock recovery everytime you reboot. Check the how to root forum you should find more information there about this.
Or you can just root it and twrp won't erase with stock recover.
naikxda18 said:
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Click to expand...
Click to collapse
Do this:
[email protected] said:
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
Click to expand...
Click to collapse
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
Thanks but i flashed RR pie soon after flashing twrp now its working fine
[email protected] said:
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Click to expand...
Click to collapse
I didn't either, as you wrote if you boot into TWRP before going to system it should stick or also if you flash magisk before booting the OS.
But there are some devices/ROMs that need the no verity flag to be disabled so flashing this file might help if TWRP won't stick (even when DM verity looks for a tampered system partition in the first case). There are also some terminal commands to do that but I forgot them at the moment.
I mainly used the zip to keep my /data partition decrypted after reformating it. When flashing Nougat magisk did the job for me but when I upgraded to Oreo /data was reencrypted again after flashing magisk and booting into system.
The above zip prevents /data from being encrypted again and may make sure that TWRP sticks.
ahhh, ok I see. Thanks for the explanation.
I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?
Nikos2k said:
I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?
Click to expand...
Click to collapse
Try to re flash 21.4
Nameless Foe said:
Try to re flash 21.4
Click to expand...
Click to collapse
yes, but how?
Nikos2k said:
yes, but how?
Click to expand...
Click to collapse
Are you able to boot into fastboot mode?
Nameless Foe said:
Are you able to boot into fastboot mode?
Click to expand...
Click to collapse
Yes
Nikos2k said:
Yes
Click to expand...
Click to collapse
Are you able to flash the older version magisk through fast boot?
Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
Don't know how
Magisk 21.4 is a .zip file: Magisk 21.4
Is it possible to flash it through fastboot ?
Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
You might have to reset your phone via fastboot then flash the stock firmware
Nameless Foe said:
You might have to reset your phone via fastboot then flash the stock firmware
Click to expand...
Click to collapse
How can i reset it from fastboot?
And will I lose all my data?
Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.
Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.
Nikos2k said:
How can i reset it from fastboot?
And will I lose all my data?
Click to expand...
Click to collapse
Just use the MSM tool,, easier and risk free
wgs1028 said:
Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.
Click to expand...
Click to collapse
I didn't manage to restore it by just flashing boot.img
I then flashed all the image files from the output of payload dumper, but it didn't work either
Then wiped userdata (by using -w switch of fastboot), still no luck
Then changed active slot and flashed all the image files to that slot, and it booted successfully
dladz said:
Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.
Click to expand...
Click to collapse
i didn't manage to successfully boot it with the stock boot.img ...
Nikos2k said:
i didn't manage to successfully boot it with the stock boot.img ...
Click to expand...
Click to collapse
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required
dladz said:
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required
Click to expand...
Click to collapse
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Then did you try safe mode
Add bookmark
#45
For the Oneplus 8 pro with 11.0.4.4.IN11AA I had to get a boot.img (for 11.0.4.4IN11AA) and flashed it with adb via fastboot (from PC), then my phone started up without root but still unlocked (and none of my data was lost). I reinstalled Magisk 22.0 (apk) and then put the boot.img on my sdcard and used Magisk to patch my boot.img and then i booted into fastboot and and flashed the patched boot.img via adb fastboot(from my PC). I never orginally had Magisk hidden so not sure why my phone lost root after the Magisk 22.0 update. Hopefully this helps someone onto the right path.
Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK
dladz said:
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK
Click to expand...
Click to collapse
No no, i installed them to their respective partitions
Like a total firmware reset