Related
If so, how? Thanks!
magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
worked for me perfectly
pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.
Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.
Google just posted the August images a few minutes ago, but they are listed as 9.0 Android P builds. PPR1.180610.009
I haven't been keeping up with the developer previews. Is this a new build or a preview?
MrDrift42 said:
Google just posted the August images a few minutes ago, but they are listed as 9.0 Android P builds. PPR1.180610.009
I haven't been keeping up with the developer previews. Is this a new build or a preview?
Click to expand...
Click to collapse
9.0 Pie is officially released 9.0.0 (PPR1.180610.009, Aug 2018)
Wow, just wasn't expecting it today, rumors were for the end of the month.
So would you be able to follow the below thread to go from Rooted 8.1.0 stock by just downloading the new image (9.0) and newer versions of magisk?
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
edit: and then i found this:
1. Boot into the bootloader and plug your phone into a PC with fastboot installed.
2. Flash the P factory image using the flash-all script.
3. Let the phone reboot back into the system and complete setup process.
4. Download everything needed for TWRP
SAILFISH FILES Twrp Image, Twrp installer
MARLIN FILES Twrp Image, Twrp installer
6.MAGISK
7. Boot your phone into the bootloader
8.
Code:
fastboot boot <twrp-image>
9. When TWRP boots, swipe to allow modifications
10. Flash the twrp ZIP
11. Reboot back into Android, then reboot back into TWRP
12. Flash the magisk zip
13. Reboot. If it freezes on the logo, hold the power button until it reboots.
Just installed on my stock OG Pixel XL and man is it smooth and fast. I believe it gave more life to this phone. I enabled the home key gesture but disabled after a few minutes. I will have to get used to it later. I'm on vacation and I don't want to have to learn new gestures yet. Hopefully battery life improves which is what I am reading it should do.
Sent from my Pixel XL using Tapatalk
Is magisk working with this? And is Safetynet passing?
KevinThaKid said:
Is magisk working with this? And is Safetynet passing?
Click to expand...
Click to collapse
Yes - rooted
No - safetynet pass
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
I did an OTA sideload, flashed TWRP, rooted with Magisk. No problems
Is there any advantage to flashing the full stock image instead of the OTA since this is an upgrade to 9.0?
I the ota came up on my phone today. I am currently on a unlocked loader and rooted. This is the first time Ive gotten an update notification. Is there any harm in taking the update. I really no longer have a use for root, or twrp.
OKAstro said:
Yes - rooted
No - safetynet pass
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
I did an OTA sideload, flashed TWRP, rooted with Magisk. No problems
Is there any advantage to flashing the full stock image instead of the OTA since this is an upgrade to 9.0?
Click to expand...
Click to collapse
Flash the full image, at least you'll know there won't be any left over stuff from Oreo, + fresh start. Side loaded the ota previews and then just flashed the official image with a full wipe, no problems yet.
---------- Post added at 09:47 PM ---------- Previous post was at 09:00 PM ----------
specd_out said:
I the ota came up on my phone today. I am currently on a unlocked loader and rooted. This is the first time Ive gotten an update notification. Is there any harm in taking the update. I really no longer have a use for root, or twrp.
Click to expand...
Click to collapse
Don't try taking an ota if your rooted, just sideload the ota.zip or flash the whole image with a full wipe (backup internal storage)
lordodin912 said:
Flash the full image, at least you'll know there won't be any left over stuff from Oreo, + fresh start. Side loaded the ota previews and then just flashed the official image with a full wipe, no problems yet.
---------- Post added at 09:47 PM ---------- Previous post was at 09:00 PM ----------
Don't try taking an ota if your rooted, just sideload the ota.zip or flash the whole image with a full wipe (backup internal storage)
Click to expand...
Click to collapse
So apparently my phone took the update, I do not recall accepting the update. But regardless I am on 9 and running ok.
specd_out said:
So apparently my phone took the update, I do not recall accepting the update. But regardless I am on 9 and running ok.
Click to expand...
Click to collapse
KevinThaKid said:
Is magisk working with this? And is Safetynet passing?
Click to expand...
Click to collapse
- Installed Factory marlin-ppr1.180610.009-factory-90a4fa8b.zip
- booted twrp 3.2.2.0
- installed Magisk-v16.7.zip
- Rooted = YES, Safety Net = YES
- Substratum does not have 9 for Android Version yet, tried 8.1 and it failed and no effect.
- All else is fine
jk8260 said:
- Installed Factory marlin-ppr1.180610.009-factory-90a4fa8b.zip
- booted twrp 3.2.2.0
- installed Magisk-v16.7.zip
- Rooted = YES, Safety Net = YES
- Substratum does not have 9 for Android Version yet, tried 8.1 and it failed and no effect.
- All else is fine
Click to expand...
Click to collapse
I wasn't able to get twrp to decrypt, no matter what password I set. Was able to install by turning off lock screen passwords entirely.
I honestly wasn't expecting to like P that much but I figured I'd give it a go. Honestly I quite like it. And the gestures. Now just to wait for custom roms and see what people can do.
jkennebeck said:
So would you be able to follow the below thread to go from Rooted 8.1.0 stock by just downloading the new image (9.0) and newer versions of magisk?
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
edit: and then i found this:
1. Boot into the bootloader and plug your phone into a PC with fastboot installed.
2. Flash the P factory image using the flash-all script.
3. Let the phone reboot back into the system and complete setup process.
4. Download everything needed for TWRP
SAILFISH FILES Twrp Image, Twrp installer
MARLIN FILES Twrp Image, Twrp installer
6.MAGISK
7. Boot your phone into the bootloader
8.
Code:
fastboot boot <twrp-image>
9. When TWRP boots, swipe to allow modifications
10. Flash the twrp ZIP
11. Reboot back into Android, then reboot back into TWRP
12. Flash the magisk zip
13. Reboot. If it freezes on the logo, hold the power button until it reboots.
Click to expand...
Click to collapse
Good stuff.
I am working on new guide: [Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch
Can anyone confirm if latest magisk Xposed is working on 9.0?
I am unable to change USB Options (e.g. file transfer) when plugging in a USB cable.. All choices are greyed out.
Any suggestions
Installed factory images on Pixel and Pixel XL from Oreo. Removed -w from flash-all, removed pin from phones, and everything worked fine. 16.7 Magisk after TWRP 3.2.2-0 .img only. I haven't installed TWRP and probably won't until a new version comes out that decrypts. Put PINs back on, then then the first time I ran SaftyNet on the XL, it came back invalid response, but then passed the next time I ran it (and has multiple times after that). PIxel passed 1st time and multiple times after. I had two apps come up with warning that they were created for an older version, but the message doesn't come back after hitting OK and relaunching. Both apps are working fine. The only thing I have noticed in Google Pay has an almost blank main screen (shows recent transactions only) but looks normal on other screens. I will try using it at a store today or tomorrow, but I suspect it will work since SafetyNet is passing and the app opened without an error.
twrp is up to 3.2.3-0 https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html
Pain-N-Panic said:
Can anyone confirm if latest magisk Xposed is working on 9.0?
Click to expand...
Click to collapse
Xposed is not compatible with 9 yet
I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Nothing will be lost from a regular OTA Just check around for any bugs or problems that other people are having if any? And update if you like.
rockerduck said:
I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Click to expand...
Click to collapse
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
rockerduck said:
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
Click to expand...
Click to collapse
You're welcome. I don't think it's needed the disable_dm-verity (but also i don't think that's a bad thing if you reflash it). If you want to thanks somebody in xda forum just press the thanks button (the ok button).
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
wheelnut said:
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
Click to expand...
Click to collapse
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
wheelnut said:
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
Click to expand...
Click to collapse
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
darhma said:
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
Click to expand...
Click to collapse
I'm using Windows and WinRAR. Will try after I download recovery rom (my dl speed is ****ty so it wont be soon)
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
thelastprime said:
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
Click to expand...
Click to collapse
Are you sure you downloaded the right rom? Error 7 is a mismatch of the firmware
Just come to say that everything went fine.
I didn't need to wait for unlock bootloader. I bought phone 2 weeks ago and using it normally and when I start unlock procedure it unlock without waiting time (I saw that someone must wait 720 hours!!).
I flash twrp and magisk (I had fingerprint lock so after flashing I did data erase) and now I have rooted phone
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
kaplanfa said:
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
Click to expand...
Click to collapse
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Is updating ota with full recovery rom via twrp erase internal data or installed app?
darhma said:
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Click to expand...
Click to collapse
Is installed app or data lost?
m.nav7854 said:
Is installed app or data lost?
Click to expand...
Click to collapse
If you do an update there should be no data loss however it is always recommended to have a backup of your data
Hey guys, how are you? So, let me explain my situation - I have a Redmi 7A (the 16 GB version) and I recently unlocked its bootloader to root, and uninstall some bloatwares ...... I managed to unlock the bootloader and install TWRP recovery, but I was unable to root, and i tried in a lot of ways, in a lot of times........... I'm on version 11.0.6 of MIUI, and I saw that some users here were having problems with this version too. Anyway, recently a MIUI update came out, and soon it will update to MIUI 12, but I'm not able to install the OTA update, after the phone restarts, it goes to TWRP recovery and shows an error message - so, I would like to go back to my original recovery and re-lock my bootloader, but for that I need the original recovery of the Redmi 7A, and I can't find it anywhere........
Someone here have this original recovery available to send or do upload? It would help me a lot! Thanks
eriksparks1 said:
Hey guys, how are you? So, let me explain my situation - I have a Redmi 7A (the 16 GB version) and I recently unlocked its bootloader to root, and uninstall some bloatwares ...... I managed to unlock the bootloader and install TWRP recovery, but I was unable to root, and i tried in a lot of ways, in a lot of times........... I'm on version 11.0.6 of MIUI, and I saw that some users here were having problems with this version too. Anyway, recently a MIUI update came out, and soon it will update to MIUI 12, but I'm not able to install the OTA update, after the phone restarts, it goes to TWRP recovery and shows an error message - so, I would like to go back to my original recovery and re-lock my bootloader, but for that I need the original recovery of the Redmi 7A, and I can't find it anywhere........
Someone here have this original recovery available to send or do upload? It would help me a lot! Thanks
Click to expand...
Click to collapse
I have detailed instructions - How to install TWRP + ROOT [Magisk] for redmi 7A HERE. Very easy. Please use google translate
sjcbank said:
I have detailed instructions - How to install TWRP + ROOT [Magisk] for redmi 7A HERE. Very easy. Please use google translate
Click to expand...
Click to collapse
Hi! I tried that way, but when i use the patched boot.img, it doesn't boot, and go straight to TWRP :/
eriksparks1 said:
Hi! I tried that way, but when i use the patched boot.img, it doesn't boot, and go straight to TWRP :/
Click to expand...
Click to collapse
If you can't do it, look down and read lesson #3, download ROM zip and txt files for flash via twrp. will definitely work 100%
eriksparks1 said:
Hi! I tried that way, but when i use the patched boot.img, it doesn't boot, and go straight to TWRP :/
Click to expand...
Click to collapse
Soo... I have problem too with root and I make temp root (unsafe method) . Patching boot img is idiot idea now , same as re-lock bootloader . I'm DEV and i'm know (look on my threads if you don't think). Better idea for you is download global rom or rom designed for your region . Actually i wipe my global rom and I install rom with android 10 . I have english only without polish support . All rom's is here : https://mirom.ezbox.idv.tw/en/phone/pine/ If you want to unbrick your device , download correct rom , and flash . For your bricked device is only fastboot rom for unbrick . In google you find how to install adb and fastboot drivers , disable check signatures of drivers in your windows , adb and fastboot exe file (if you have windows as me) etc. . Good luck . Disclaimer: After re-lock bootloader , your software and data be bricked , you must flash all with data too . Make copy of data to google or sd card
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-redmi-7a-all-miui-firmwares/
---------- Post added at 06:15 AM ---------- Previous post was at 06:04 AM ----------
https://xiaomifirmwareupdater.com/miui/pine/