Related
[EDIT Oct. 25] Here's what I did--cleaned up and corrected for bootloaders--to install the official 5.2.2 update (build date September, 2015) on myrooted tablet running Developers Preview, build date July, 2015.This is only for those who rooted and installed the dev preview before the upgrade/downgrade troubles. It let's you keep all your stuff.
Few important things:
If you don't reset/wipe in TWRP you can keep most of your stuff, including homescreen layout, play store and all apps. However . . .
Google framework, account manager, contact sync and calendar sync get deleted with the update.
I didn't flash Gapps and got bogus insufficient space error [130 Mb free] when I tried later. Restoring framework fixed everything, but it may be best to flash new Gapps (although that can cause problems when update doesn't completely wipe /system, like this one). Up to you.
Oct 26 Update: Based on reported "insufficient space" flashing Gapps--plus testing and researching contacts and calendar--I suggest not flashing Gapps but simply backing up Google services framework before you upgrade and restoring it after. The other google system apps that get deleted don't seem to be needed; if you want to sync Google contacts & calendar on the Fire you can add your google account(s) in Settings, same as on any Android. If you don't want Amazon's stock calendar or contacts, get another from the Play Store. I've updated the instructions to reflect this.
.
HDXposed module is no longer needed for working Play Store.
Xposed Framework: The update doesn't support the version we used with the July dev preview. You must either flash the latest version or flash the uninstaller if you don't want Xposed anymore.
Stock launcher now = com.amazon.firelauncher
Home key now defaults to stock launcher until you pm disable it. (No prompt anymore)
Backup Google Services Framework.
Turn off wifi (airplane mode) and plug in.
Download the zips:
* September 5.2.2 update (thanks @Hariiiii !) and rename extension from bin to zip.
update-kindle-full_ariel-20.5.2.2_user_522053520.bin: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
* Latest Xposed Installer or Uninstaller from here: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Installer = Xposed-v74-sdk22-arm-by-romracer-20150911.zip
Uninstaller = xposed-uninstaller-20150911-arm64.zip
* Gapps (if using)
tk_gapps-modular-pico-5.1.1-20150920-signed.zip: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
* 5.2.0_stock_recovery_only.zip
Attached to bibikalka's lollipop post: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Get latest SuperSU apk (?) Don't know if it's required, but I installed it.
- SuperSU 2.52 Beta: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
Follow Step 1 of @bibikalka's guide to temporarily install TWRP and while in TWRP:
a. Flash the update
b. Flash Xposed (installer or uninstaller)
c. Flash 5.2.0_stock_recovery_only.zip
d. Choose boot to recovery and install SuperSU when TWRP prompts you.
Confirm you're in recovery, then boot to system and press Exit at "Welcome to Fire OS 5!"
In OS, see if SuperSU is still managing root access. If it's not or you want to update, install the new SuperSU apk and update binaries.
(Wait to reboot unless you can't get su access at next step.)
Block OTA:
a. Disable dcp or otaverifier (whichever you prefer)
b. Rename system/priv-app/devicesoftwareota/devicesoftwareota.apk extension to apk_
Restore Google Services Framework and reboot.
Turn on wifi and sign in to playstore.
Thanks for the guide!
deleted
putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
As far as I understand from my experience of going from unrooted september 5.2.2 to rooted 4.5.3 to rooted september 5.2.2, it should work fine if you go via that route.
putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
This is only for rooted tablets. Follow the steps Hariiiii describes here. There are guides for what he did.
[How To] Upgrade Rooted Developers Preview to Official 5.2.2 Release
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
I order a replacement. What i have to do to have fire os 5 final with root, play store and other launcher?
Thanks
You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.
Could we possibly get a video tutorial on how to do this?
(May be easier for some.)
Ooh, I don't do video and doubt anyone will for this, but that would be kind. You can pm me with questions.
I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.
Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
bibikalka said:
Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Hdxposed is not necessary
cm11noob10 said:
I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.
Click to expand...
Click to collapse
Think we have some confusion. I'll need to make this clearer: This guide is only for people who already have the rooted developer preview--people who did the downgrade/upgrade using the July build. There is no longer a way to use the developer preview to gain root; the latest version (September) ends up causing bricks, as you learned the hard way. Fortunately, it looks like the official 5.2.2 update that Amazon is now OTA distributing can be successfully used in the downgrade/upgrade operation. I'm sure guides for that will be out soon.
Then I'll look for a guide on that and go from there.
Thx for the replies.
bibikalka said:
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Good feedback, thanks. HDXposed is indeed not needed, which of course means Xposed isn't required. If you don't install the new Xposed, though, I suspect the old, non-working one will stay on system even with factory reset. Your thoughts?
(Edit: NVM. Yes, they'll still have old Xposed, so will need new.)
Yeah, Gapps <sigh> It's such a personal thing. (Thinking about how to handle.)
DoLooper said:
You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.
Click to expand...
Click to collapse
But my first time i update and i didn't flash 5.2.0 recovery and work perfectly and i haved root. This mean that it isn't necessary flash 5.2.0 recovery?
Enviado desde mi SM-N910F mediante Tapatalk
davigar said:
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
Click to expand...
Click to collapse
I'm looking into this again. When you flashed "5.2.0 recovery" which zip did you use, 5.2.0_stock_recovery_only.zip or 5.2.0_stock_recovery_uboot.zip? Thanks.
I flashed 5.2.0_stock_recovery_uboot.zip
davigar, you got the developer preview in order to downgrade to OS 4.5.3 and root, is that right? If not, what OS were you on and how did you install it?
EDIT: @davigar Wait a minute--did you not root? Did you just use this tutorial to install the update and that's when you forgot recovery? This will make a difference. Thanks.
I upgrade my kindle to developer preview then i downgrade to 4.5.3, root and upgrade it to 5.2.2 developer with gapps. I followed the newbie friendly tutorial when i bought it. Sorry for my english [emoji16]
Enviado desde mi SM-N910F mediante Tapatalk
Hello,
I am really confused about whatever Moto E4 supports Xposed Framework after all.
I have Mediatek variant. XT1762 (Dual Sim one).
I've successfully unlocked the bootloader, installed TWRP recovery, along with dmverify and rooted the phone (by Magisk). I can edit system partition and the phone boots perfectly.
about systemless xposed:
when I try to install a Magisk module, whenever in recovery or application mode, I get /data/magisk_merge.img mount failed error. I uninstalled Magisk 14.0 complately and then tested with Magisk 14.3. But no luck. I gave up installing Magisk modules because I think the stock kernel have some problems with loop module (altought, I am not sure about that).
_______________
Then, I tried to flash them: API 25 / ARM
(offical one) https://forum.xda-developers.com/showthread.php?t=3034811
(unoffical, seems for Moto E4) https://forum.xda-developers.com/moto-e4/how-to/info-xposed-framework-nougat-t3687263
both give bootloop and USB debugging is getting turned off everytime I reboot the phone therefore I do not have any valueable / debug information. The only way me to get the phone booted again is to flash the uninstaller from the recovery!
_______________
How do you guys install this XPosed framework on this phone? I am so confused!
buraktamturk said:
Hello,
I am really confused about whatever Moto E4 supports Xposed Framework after all.
I have Mediatek variant. XT1762 (Dual Sim one).
I've successfully unlocked the bootloader, installed TWRP recovery, along with dmverify and rooted the phone (by Magisk). I can edit system partition and the phone boots perfectly.
about systemless xposed:
when I try to install a Magisk module, whenever in recovery or application mode, I get /data/magisk_merge.img mount failed error. I uninstalled Magisk 14.0 complately and then tested with Magisk 14.3. But no luck. I gave up installing Magisk modules because I think the stock kernel have some problems with loop module (altought, I am not sure about that).
_______________
Then, I tried to flash them: API 25 / ARM
(offical one) https://forum.xda-developers.com/showthread.php?t=3034811
(unoffical, seems for Moto E4) https://forum.xda-developers.com/moto-e4/how-to/info-xposed-framework-nougat-t3687263
both give bootloop and USB debugging is getting turned off everytime I reboot the phone therefore I do not have any valueable / debug information. The only way me to get the phone booted again is to flash the uninstaller from the recovery!
_______________
How do you guys install this XPosed framework on this phone? I am so confused!
Click to expand...
Click to collapse
The only xposed that worked for me was the official but NOT SYSTEMLESS .zip . I flashed it via recovery . I was using magisk 14.3 . I got the same error in magisk with systemless version . If you get a bootloop try going back to recovery and flashing magisk 14.3 ..reboot to recovery ...flash xposed ..reboot to RECOVERY ..flash no dm-verity ...clear cache & dalvik ..reboot RECOVERY ...reboot system ......
In nougat xposed maaany xposed modules has bugs so just flash a custom rom bro
the modified xposed is not really necessary as the normal version of xposed works too.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
Before doing this install xposed installar apk BUT THE LATEST ..give it root access in magisk ..go to settings ..disable verify apps via USB ..enable install from unknown sources ...enable USB debug ...all of this in developers settings
Then boot to recovery and do the above and see what happens ..I don't understand how or why your USB debug is being turned off on reboot because it should survive boot and stay in USB debug mode
If you have substratum installed remove it before doing xposed
Oh yes make sure you are using SDK 25 XPOSED ARM none of the others .
KevMetal said:
The only xposed that worked for me was the official but NOT SYSTEMLESS .zip . I flashed it via recovery . I was using magisk 14.3 . I got the same error in magisk with systemless version . If you get a bootloop try going back to recovery and flashing magisk 14.3 ..reboot to recovery ...flash xposed ..reboot to RECOVERY ..flash no dm-verity ...clear cache & dalvik ..reboot RECOVERY ...reboot system ......
In nougat xposed maaany xposed modules has bugs so just flash a custom rom bro
the modified xposed is not really necessary as the normal version of xposed works too.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
Before doing this install xposed installar apk BUT THE LATEST ..give it root access in magisk ..go to settings ..disable verify apps via USB ..enable install from unknown sources ...enable USB debug ...all of this in developers settings
Then boot to recovery and do the above and see what happens ..I don't understand how or why your USB debug is being turned off on reboot because it should survive boot and stay in USB debug mode
If you have substratum installed remove it before doing xposed
Click to expand...
Click to collapse
Thanks for verification! thought I were late for the additional one, I uninstalled everything and recovered from boot.img backup, installed no dm verify. Booted into the system. Installed xposed installer, rebooted into recovery and flashed xposed, and I am waiting for the result. (no Magisk installed for this time)
but I don't think it is going to work cuz I have tried all of these combinations before :'(
what was your variant? Qualcomm or Mediatek?
buraktamturk said:
Thanks for verification! thought I were late for the additional one, I uninstalled everything and recovered from boot.img backup, installed no dm verify. Booted into the system. Installed xposed installer, rebooted into recovery and flashed xposed, and I am waiting for the result. (no Magisk installed for this time)
but I don't think it is going to work cuz I have tried all of these combinations before :'(
what was your variant? Qualcomm or Mediatek?
Click to expand...
Click to collapse
I have mediatek xt1762 ...make sure you are using XPOSED SDK 25 ARM classic NOT systemless .
KevMetal said:
I have mediatek xt1762 ...make sure you are using XPOSED SDK 25 ARM classic NOT systemless .
Click to expand...
Click to collapse
You're crazy! It worked! I have removed everthing, just TWRP, no dm verify and 88.2 offical arm not systemless zip did the trick!
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
Hello,
I have a Moto E4 XT1762 with the ROM STOCK MOTOROLA_E_NMA26.42-75_ROW (France) and two Xposed module, one: xposed-v89-sdk25-arm64.zip and a: xposed-v89-sdk25-arm.zip much lighter. Alas I remain stuck on the home screen very long at least 1/2 hour before the smarpthone starts. Once in Xposed, I have a message in yellow that tells me that Xposed does not work and you have to go see in the log, but the log is empty.
I have these two files + the uninstall file available if it interests someone. These files come from the site: https://repo.xposed.info/
If anyone can help me make Xposed work, it would be nice. Thank you
Darkmo said:
Hello,
I have a Moto E4 XT1762 with the ROM STOCK MOTOROLA_E_NMA26.42-75_ROW (France) and two Xposed module, one: xposed-v89-sdk25-arm64.zip and a: xposed-v89-sdk25-arm.zip much lighter. Alas I remain stuck on the home screen very long at least 1/2 hour before the smarpthone starts. Once in Xposed, I have a message in yellow that tells me that Xposed does not work and you have to go see in the log, but the log is empty.
I have these two files + the uninstall file available if it interests someone. These files come from the site: https://repo.xposed.info/
If anyone can help me make Xposed work, it would be nice. Thank you
Click to expand...
Click to collapse
Just install the systemless module from inside magisk + systemless xposed apk from link inside module explanation imside magisk & reboot
Or
REMOVE MAGISK & install custom rom and use
"SYSTEM" Supersu version
____in both cases you should be formatting data to EXT4 first
__DOWNLOAD THE CORRECT VERSION OF XPOSED ..your device is NOT 64bit
__download ARM ...
But honestly you could have figured this out if you just read 20% of what is in the moto e4 mtk xt1762 forum and posts
There is one thing I do not understand, I thought the Moto E4 (MT6737) was 64 bits according to a technical sheet that I read ?
Darkmo said:
There is one thing I do not understand, I thought the Moto E4 (MT6737) was 64 bits according to a technical sheet that I read ?
Click to expand...
Click to collapse
Nope. It's chip is capable of 64 bit. But it has no 64 bit software whatsoever.
OK but then for Xposed, you have to take it in ARM64 or not?
Darkmo said:
OK but then for Xposed, you have to take it in ARM64 or not?
Click to expand...
Click to collapse
No. Arm. It has no arm 64 software at all. No drivers, blobs, nothing. Do not consider arm 64 at all for anything on this device.
OK thank you
This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really
Requirements:
- Unlocked bootloader
- Windows PC
- fastboot (present in the miunlock app folder)
- Latest TWRP (download here)
- Latest Magisk (download here)
Steps:
- Install latest Magisk app
- Put latest Magisk zip on your device storage (SD)
- Shut down device
- put latest twrp.img in miunlock folder
- Connect phone to PC
- Press volume down and power button to boot to fastboot mode
- Open "Command Prompt" on your PC
- Type: (without quotes)
----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)
----- "fastboot devices"
----- "fastboot boot twrp.img"
- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.
- In TWRP, flash the Magisk zip
Enjoy root
Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
kn1g said:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
Click to expand...
Click to collapse
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?
This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.
The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.
Ok, but is Xposed etc. possible?
kn1g said:
Ok, but is Xposed etc. possible?
Click to expand...
Click to collapse
I haven’t tried but should work.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
It is really works! Thank you!
gonna check this cause i wanna root the phone but keep enjoying updates
I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial
I bump this because it worked. Quite easy, clean and fast. Thanx!
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
masri.razak said:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
Click to expand...
Click to collapse
Wrong...u need to boot twrp not to install. Read the OP for steps.
Dadovvv said:
Wrong...u need to boot twrp not to install. Read the OP for steps.
Click to expand...
Click to collapse
Well... That's I mean, boot TWRP using adb
After have TWRP, how can i get update via OTA?
it successfully worked for Redmi Note 4 global beta/stable MIUI9.2
even installed camera api 2 using magisk module
Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?
**[EDIT]**
Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.
Installed successfully on miui 9.2.1.0 stable
Now when a new update for magisk is released, how should i update it??
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.
Giacomo_ITA said:
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
Click to expand...
Click to collapse
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Baxeisindi said:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Click to expand...
Click to collapse
Do you mean this?
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse
Giacomo_ITA said:
Do you mean this?
Click to expand...
Click to collapse
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.
I'M NOT RESPONSIBLE IF YOUR DEVICE BRICKS, SD CARD DAMAGES OR NUCLEAR WAR STARTS.
Rooting method described below will work on Oreo-running devices ONLY (confirmed on build OPN27.76-12-22 and on OPNS27.76-12-22-9).
Please follow all steps very carefully and make sure you downloaded correct versions of all .zip files mentioned in my instruction!
ROOT (SafetyNet test will PASS!)
1. Download all files listed below:
- twrp-3.2.3-0-addison.img (CLICK)
- Magisk-v17.1.zip or newer if availabe (CLICK)
- f2fsfix-2018.9.2.zip (CLICK)
2. Flash TWRP using Fastboot:
Code:
fastboot flash recovery twrp-3.2.3-0-addison.img
3. Flash Magisk-v17.1.zip (or newer if available).
4. Go to TWRP/Settings and open Terminal.
5. Run both of following commands:
Code:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
6. Flash f2fsfix-2018.9.2.zip
7. Reboot (it is crucial in case of installing Xposed afterwards).
8. Optional but recommended: update your Magisk Manager to the latest version (CLICK).
9. Open Magisk -> Modules and update f2fs-loopback-bug-workaround module to the newest version (can be done only via Magisk Manager only if new version of f2fs-loopback-bug-workaround module is available).
10. Enjoy rooted Oreo.
UPDATE 03.10.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 17.1.zip AGAIN (yes.).
3. Flash f2fsfix-2018.9.2.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me).
UPDATE 03.10.2018
XPOSED (be careful: Xposed for Oreo is still in BETA distribution and flashing it will break your SafetyNet!)
1. Open Magisk Manager -> Downloads.
2. Download Xposed Installer (the one from the screen below):
https://image.ibb.co/byLUuK/Xposed_Framework.png
3. Let Magisk install it.
4. Reboot.
5. Open Xposed Installer (you will see orange exclamation mark, don't worry).
6. Reboot once again.
7. Voila.
Hit THANKS if I helped!
Credits:
- @topjohnwu
- @rovo89
- @Artim_96
- @VR25
@rafikowy ah, so basically the problem was with dm-verity and forced encryption? That makes sense. So it would basically also work if you'd not extract the boot.img from the OTA zip and mod it with Magisk manager with both enabled and flash that (might be easier than flashing normal Magisk and then make the changes), so you'd basically just flash the img and the module zip in TWRP.
Well, if no bigger bugs appear I might try the Oreo OTA and root tomorrow. Don't think it will be here on its own till then, even if it's already the official rollout (Indian and brasilian users seem to get it officially)
First magisk manager did not want to open, but a reboot solved. thanks
So, Lenovorola is still "undecided" in regards to patching F2FS.
I wonder why...
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Only a Soak test is available, the link is in the thread in the ROM section. And yes, it doesn't seem to update your bootloader, it was already successfully testet to go back to 7.1.1
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
Look at
https://forum.xda-developers.com/mo...se-attempt-t3812530/post76991120#post76991120
not work - moto z play - oreo soak
Unfortunately it does not work. : (TWRP prompts for a PIN to decrypt data.) How to select cancel and install Magisk on installation f2fs-loopback-bug-workaround-2018.1.31.zip displays an error that does not detect magisk or is incompatible. How do I format the date everything is installed but the phone does not turn on... Any idea?
Sorry but, if verity is enabled, that means you are unable to modify /system files?
Necrodaemon said:
Where can I find the firmware or OTA to update Oreo on my 1635-02 with Android 7.1.1 Patch December? Is possible back to Stock Oreo or Nougat?
Click to expand...
Click to collapse
You can go back, problem is you will lose IMEI by going back to Nougat.
huma_dawii said:
You can go back, problem is you will lose IMEI by going back to Nougat.
Click to expand...
Click to collapse
I gone back to 7.1.1 Nov patch and everything is OK with my IMEI. Just flash 7.1.1 Plus ROM with TWRP. One issue what I have - In can't mount OEM partition in TWRP.
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Camarda said:
Could someone provide a TWRP backup of the 8.0 Soak? I've modified the system partition and this method stoped working. All the 8.1 roms have a so bugged camera, I don't wanna go back to them
Click to expand...
Click to collapse
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
St.Noigel said:
Here are system and boot from 8.0 soak test. Just unrar it adn put to TWRP folder with your backups.
Click to expand...
Click to collapse
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Camarda said:
I've restored the backup, but I'm still unable to boot with magisk. Don't know what is wrong now
Click to expand...
Click to collapse
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Can i go back to 7.1.1 and relock bootloader ??
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
LovinVEVO said:
Hi,
Can anyone help me, i have updated to Oreo (Soak Update) and now i wanna go back to Nougat 7.1.1 NPNS26.118-22-2-12 and re-lock bootloader, is it possible ?? if yes guide me
thanks in advance
Click to expand...
Click to collapse
Nope. It's impossible for now. You can`t go back to full stock, because you'll lose your IMEI with flashing full 7.1.1 FW with RSD or fastboot.
St.Noigel said:
1. Restore backup
2. Flash Magisk 15.3
3. Flash this https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
4. Flash this https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
5. Go to the terminal in TWRP and run two commands:
- mm
- f
Reboot.
That's all. You don't need to run commands from OP.
IF I help you - you can buy me a beer )))))
Click to expand...
Click to collapse
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Camarda said:
Did everything, but still stuck at bootanimation. Only boots if I unninstall magisk.
Click to expand...
Click to collapse
If you have bootanimation - just wait few minutes
St.Noigel said:
If you have bootanimation - just wait few minutes
Click to expand...
Click to collapse
Just waited for 30 minutes. It wont boot
after uptade magisk my phone stuck in fastboot . i cant go to recovery . what i can do ?
phone is over or i can fix it ?
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
zgfg said:
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
Click to expand...
Click to collapse
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Add me on discord for live support :
SneezeOnYou2#8507
AC420 said:
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Click to expand...
Click to collapse
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
zgfg said:
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
Click to expand...
Click to collapse
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
AC420 said:
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
Click to expand...
Click to collapse
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
zgfg said:
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
Click to expand...
Click to collapse
Its not that i didnt look up on youtube about flashing in revovery mode. When i did search for more information i get those videos of people in india talking their own language. Np if you dont have time and on other topic someone said that they wint use discord because it wont be public for someone else with the same problem but i was gonna make photos with the steps i did for fixing it. The thing is i cant find the uninstall. File or the older version of twrp. Skip i wont takr your time good luck with your private life
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
AC420 said:
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
Click to expand...
Click to collapse
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
zgfg said:
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
Click to expand...
Click to collapse
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
AC420 said:
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
Click to expand...
Click to collapse
I've had this ****, i just used abd to flash a new twrp img and dirty flashed the ROM after it flashed magisk back on again, only problem I got was safety new which idk how I solved but I think was using lsposed