Hello,
I just installed Nougat version for my SPG712 (Europe version)
no method for root and twrp for SP712 (wifi) ?
Thanks you per advance for your help
steevou said:
Hello,
I just installed Nougat version for my SPG712 (Europe version)
no method for root and twrp for SP712 (wifi) ?
Thanks you per advance for your help
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71139256&postcount=601
Hello,
thanks for your return.
But does not work for me.
I installed :
Firmware 32.3.A.0.376 (Europe central version)
Kernel 42
twrp
but But after restart, I have a bootloop
for nougat you'll need v43
I know. But with kernel 43, twrp does not work with my SGP712 (Frozen screen on twrp)
steevou said:
I know. But with kernel 43, twrp does not work with my SGP712 (Frozen screen on twrp)
Click to expand...
Click to collapse
Flash 42v and twrp. Install there v43 + supersu.
Hello,
I always same problem (frozen screen under TWRP)
I use TWRP-3.0.2-0-20160604.img version
I installed :
Firmware 32.3.A.0.376 (Europe central version)
Kernel 42 and twrp
Kernel 43
I restart under twrp
frozen screen
read the changelog
steevou said:
Hello,
I always same problem (frozen screen under TWRP)
Click to expand...
Click to collapse
you "always" read the changelog?
-> known issue
workaround:
fastboot boot TWRP_earlier_working.img
do what you want to do
wait for fixed kernel-TWRP
EDIT:
I had the same touch issue in TWRP after installing Androplus' kernel v43.
So I installed v42. This of course bootloops on Nougat BUT: TWRP works
Then I fired up TWRP, flashed v43 and immediately (same TWRP-session) after that SuperSU
-> Nougat rooted
For a short version see post #6 in this thread.
Thanks you for your returns.
I'll wait for fixed kernel-TWRP
DHGE said:
you "always" read the changelog?
-> known issue
workaround:
fastboot boot TWRP_earlier_working.img
do what you want to do
wait for fixed kernel-TWRP
EDIT:
I had the same touch issue in TWRP after installing Androplus' kernel v43.
So I installed v42. This of course bootloops on Nougat BUT: TWRP works
Then I fired up TWRP, flashed v43 and immediately (same TWRP-session) after that SuperSU
-> Nougat rooted
For a short version see post #6 in this thread.
Click to expand...
Click to collapse
Perhaps you could clarify for me...
You install the Andro kernel in TWRP? I had always understood we were to extract boot.img and flash that in fastboot?
So understanding the steps post 376 install.
Install andro ver42 kernel
Install current TWRP and boot to TWRP
Flash ver43 in TWRP?
Flash supersu in TWRP
reboot
It doesn't seem correct to me so forgive me for asking.
Edit: Doesn't seem to matter what ver I go back to, 42, 40, etc touch on TWRP after doesn't seem to work...
Related
Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Mandeep Singh 07 said:
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Click to expand...
Click to collapse
Is ur bootloader updated to latest one ??
[email protected] said:
Is ur bootloader updated to latest one ??
Click to expand...
Click to collapse
yeah its latest one 3.0.3
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
actually when i root the phone , then it goes into bootloop, i didn`t backup my data so i lost my all data ,
after that i install paranoid then it stucks on boot logo , i tried it several times but none happens,
then i use adb push command ino twrp recovery(3.0.2) to copy cyanogenmod after that i flash it , it fails ,
then i flash cwm recovery then flash is succeded and currently running cm 13 ,
when i installed root checker it said your phone is partially rooted, when i enable root option in developer option then it said root verified.
But when i tried to flash other roms using twrp (3.0.3, 3.0.2) it stucks on boot logo.
Please help me
Exodusche said:
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Click to expand...
Click to collapse
lower bootloader can`t flash it fails every time....
Mandeep Singh 07 said:
lower bootloader can`t flash it fails every time....
Click to expand...
Click to collapse
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Exodusche said:
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Click to expand...
Click to collapse
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Mandeep Singh 07 said:
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Click to expand...
Click to collapse
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Exodusche said:
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Click to expand...
Click to collapse
thanks bro this works fine
As the title says global beta 7.2.9 is out. Anyone installed it?
What about twrp and root compatibility?
http://en.miui.com/download-299.html here is the link
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
mysa50 said:
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
Click to expand...
Click to collapse
Can you confirm the process please? Is it just:
1. Download the recovery version of the update to the phone.
2. Boot to recovery (TWRP).
3. Install the update zip file.
4. Re install TWRP.
5. Reinstall the SuperSU zip.
6. Reboot to system.
Do we need additional reboots between the steps? Do we need to unroot before installing the update? Does it matter if the existing global beta ROM is several versions old?
Sorry for asking so many questions. I have not updated the ROM since unlocking the bootloader and installing TWRP/SuperSU several months ago and am worried about bricking my phone.
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
mysa50 said:
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
Click to expand...
Click to collapse
That's good to know. Just to confirm, the update could be applied "dirty" without a need to reinstall all apps and data afterwards?
I am still on global beta 6.11.3 (which is MM) and twrp 3.0.2.0. Is 7.2.9 based on nougat which would require the update of twrp? I had thought that the nougat beta was on a separate thread open to a closed group only...
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Delete
Bhatyasirr said:
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Click to expand...
Click to collapse
Look in the mi5 developement thread There is twrp section and in the 3rd post the op uploaded a unofficial release of twrp 3.0.3 but stable enough to be considered as official.
mysa50 said:
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Click to expand...
Click to collapse
Thanks a lot. Shall try over the weekend.
Few screenshots
mysa50 said:
Few screenshots
Click to expand...
Click to collapse
This is on light use, with heavy use (games,messages,phone calls) battery last a day from 6.30 am to midnight and still 10-15% and ~5h30 sot
That's good
how to revert back to miui from LOS ?
it didnt boot up
harrez said:
how to revert back to miui from LOS ?
it didnt boot up
Click to expand...
Click to collapse
Did you try fastboot rom from xiaomi site? Give a look in the Q&A thread you should find how to revert back to miui
chan200606 said:
Thanks a lot. Shall try over the weekend.
Click to expand...
Click to collapse
Finally did it, but not without scare - my Mi5 was stuck at the boot logo with "Bootloader unlock" message screen after flashing the recovery version of 7.2.9 update and reflashing TWRP 3.0.3.0. Luckily managed to get the phone into fastboot mode to flash the fastboot version of 7.2.9 and get the phone back on again. Finally reinstalled TWRP and boot into TWRP before rebooting to system successfully.
The key step I had forgotten was the booting into TWRP after its installation over the 7.2.9 stock recovery, which had led to the bootloop.
So I now have updated to 7.2.9. I do notice that the boot process takes quite a bit longer than 6.11.3 (design of nougat?), but once up, the phone feels as responsive as before.
It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input
Hello everybody, i'm new in this forum! I'm really disappointed because i can't root my tablet after many procedures, downgrades, updates, flashing!
Actually, there isn't a kernel and a recovery for the latest nougat version, and with the latest twrp the touch doesn't work. Even if i have unlocked bootloader i can't do nothing... I really appreciate if everyone has a solution for this!
I've tried root kernel but with the latest kernel the os doesn't boot, it stops with the boot animation.
I've tried downgrading with lollipop and marshmallow too, installed respectively twrp 2.8.0 and twrp 3.0 and then flashed a prerooted nougat zip created with prf creator, but after flashing it stucks with sony logo.
Can't help with TWRP but you can patch up boot.img of newest kernel (32.4.A.1.54, right ?) https://forum.xda-developers.com/xp...ot-automatic-repack-stock-kernel-dm-t3301605
zacharias.maladroit said:
Can't help with TWRP but you can patch up boot.img of newest kernel (32.4.A.1.54, right ?) https://forum.xda-developers.com/xp...ot-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
Yes, i've tried this method. I can patch the boot.img of the newest kernel, but when i flash it to the tablet and then i boot in android, the touch doesn't work. it boots up, but i can't go over the lockscreen cause of the touch issue.