Related
Hello all.,,
I checked and read many thread slowly and steadily ,but couldn't find a good solution to root this phone 3T.
I just bought this Beautiful Device runing so smooth but with Hands tied too hard unable to run many apps and many ads and Bloatwares..
Thought to Root this device ,but all are mostly either Oxygen 3 or Marshmallow or 7.0. Version of ANdroid..and DW Error,is also a major concern to look out..
So Please help me to root this device running O2 4.1.1 (I literally dont want to change the stock,as of now) and Android 7.1.1 ,some simple steps...
Thanks and Regards
Awaiting for replies!!
I'm about to get this phone so I've been doing a lot of research myself. It looks like you can follow the steps in this thread and you can flash supersu through TWRP once you've unlocked the bootloader.
Unlock bootloader.
Flash TWRP.
Flash your preferred root zip in TWRP (SuperSU or Magisk are two good choices, I prefer Magisk).
That's about it...
i too tried the above method,,But I got struck with Logo of TWRP and got enabled only after 6 Hours.. But to my fate,,i'm still running on Stock recovery.. Not on TWRP !!
Use the latest official TWRP (currently 3.1.0-1). Works just fine.
i can relate to your question.
however, i discovered how to root the 3t and flash the usual zips files the finally the freedom rom, on my own.
it was a thrill.
i advise you to just take the blue pill.
I installed Blusparks Version of TWRP ,,but still no use,,SuperSU or Magisk both says My phone is not rooted!!!!
I want to live the Stock ROM and just to root the device,,But the steps are not futile for me!
What I would do if i was you.
Unlock bootloader
Flash TWRP
Flash latest Magisk 13.2 zip
Hey,
Is this method still valid for rooting the 3T?
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Yes, that is still valid, more or less. Might be a more current version of blue_spark's TWRP (official TWRP is on 3.1.1.2) although the link only says 3.1.1-x, so I don't know what that means. But probably won't make a huge difference.
Can't see what version Magisk is linked (my office network is blocking the link). If you choose Magisk, flash latest version 13.3, especially if you want to hide root (from Snapchat, banking apps, etc.). Older versions of Magisk will fail to hide, due to recent changes Google made to SafetyNet.
And what if we want to flash this beta to a brand new device?
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_12/
Should we first unlock the device, then install the TWRP recovery, then flash this beta rom and then root?
I made the mistake of installing TWRP and Magisk before updating, and all I get is the "update unsucessful" screen, so now I'm stuck with 7.1.1 on my Android One Moto X4.
I found a factory image of Oreo on firmware.center (can't link it here because new user, but the filename was PAYTON_FI_8.0.0_OPW27.57-25-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) for my device, and would like to know if it's safe to use and how to install it (sites seem to give conflicting information). This thing is brand new, so I'm a bit nervous about messing it up.
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
sleeptab said:
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
Click to expand...
Click to collapse
One last thing, that guide mentions using mfastboot, where do I get it? Is it any different from the regular fastboot?
No it's just normal fastboot.
Flashed it, works great! Thank you! (However, Android File Host was having issues and it took multiple times before a successful download)
Anyone know a secure procedure and a custom recovery compatible?
marte66 said:
Anyone know a secure procedure and a custom recovery compatible?
Click to expand...
Click to collapse
We don't have TWRP yet, it's not officially out yet for any G7 models and I don't know when ours may be.
Root your G7 with Magisk
I noticed this method without using TWRP on the G7 XDA forum but haven't tried it, and you must unlock the bootloader first. Apparently it's working for a few G7 users so it should on G7+ too if the correct boot.img is used (for G7+/'lake' not G7/'river') according to your release channel. You still wouldn't have a custom recovery but could install Adaway, Magisk modules, and gain full access to the file system.
EDIT:
If anyone tries this method please report back, and don't forget to unlock the bootloader first and use the Lake/G7 Plus firmware from lolinet. No one has reported it not working but only a handful have used it afaik. I'm on RETLA w/Dec security patch so would rather wait until OTA updated and then I might try it because it would give me everything I need from root except nandroid backups and installing ROMs (of which there aren't any yet). I have my unlock code ready to go and have the needed boot.img from my channel-specific firmware but remain fully stock.
The instructions aren't that detailed but I found you can install Magisk Manager as an apk, open it and when you tap on Install Magisk 18.1 (which isn't installed yet) it also gives the option to "patch boot.img" (which I didn't select but assume it'll let you navigate to where you put the one from firmware & not alter the currently booted partition). When finished you put/copy that altered one on your pc (preferably in your Fastboot/ABD folder) and fastboot flash it, then reboot and you should be rooted in Magisk.
EDIT #2:
Tried it, it works!
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Having done it I can say that Magisk Manager does let you navigate to the stock boot.img file after offering to patch it, then it goes through the same familiar steps as when installing in TWRP, and at the end tells you it's in your Download folder with the name patched_boot.img. After transferring to my pc I renamed it to boot.img and just manually typed in the fastboot flash boot command.
I also want to repeat that although rooted there's still no custom recovery/TWRP so you can't do nandroid backups, and now when my channel's OTA comes along I'll have to disable Magisk & flash back to my original boot.img before taking it, which I hope works but it should. It's great being rooted though on G7+ with Adaway and Youtube vanced background play, also Root Explorer to change my boot animation or debloat or whatever.
Dahenjo said:
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Click to expand...
Click to collapse
Yeah, I thought so. Thanks anyway.
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
I see there is a PPW29.98-66 RETAIL channel firmware on lolinet:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETAIL/
I'm not sure what difference the boot.img would have between them if any, and the RETAIL channel is more a 'generic' type which might be a safer choice than others of the same build version. I know the G5+ debloated ROMs by NZedPred ended up with just one version (instead of by various channels as he did originally) after finding he didn't need to bother, though I believe he did make other changes. He'd be a good one to ask though if you want to PM him.
After I get updated (revert to full stock etc) I may try the RETAIL one to re-root to see if we can use it for this purpose regardless of channel. My 'international model' from Amazon is actually just the RETLA channel since it wasn't released in the US, so I'd almost rather be on the more generic channel if it works.
EDIT:
Did some experimenting, reverted to full stock then successfully tried it again with the boot.img from the RETAIL firmware (which for my version is still PPW29.98-28), so I believe RETAIL could be used for other channels too.
This process worked for me. Moto G7 Plus, International Unlocked version.
This worked for me, XT1965-2, AT&T mexican version. Also, managed to run Substratum, just needed to compile, reboot and activate each time I changed theme.
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7pluswas shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
shaDNfro said:
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7 was shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
Click to expand...
Click to collapse
I assume you have G7 Plus (not G7) with the build number you showed.
To answer your question:
I successfully fastboot flashed the full RETAIL channel PPW29.98-66 firmware a few days ago. I was on RETLA PPW29.98-28 with the December security patch and now have the January patch, and my channel is still shown as RETLA. I used the batch file posted in this thread which worked perfectly. Everything for my XT1965-2 RETLA model is working as it should on the newer RETAIL firmware, but I don't know if your RETEU2 has anything different that could cause issues.
Enforced Verity, Unlocked Bootloader, rooted Lake OPENMX Not working with Google Pay
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
vvarrior said:
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
Click to expand...
Click to collapse
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
shaDNfro said:
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
Click to expand...
Click to collapse
There's a bunch of Google apps that need verity to be enforced I think. I think we need the stock ROM with the stock boot. Maybe the phone has to be rooted to patch the stock boot.img with verity enforced? I'm not sure but I stepped up to the G7 Plus because it finally has NFC so I can use it to pay and it was an unlocked international version that works good with Google Fi (which also needs verity enforced).
Still looking for a solution and will probably just go back to my old phone until I can get Google Fi and Pay working.
Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.
I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*
Updating from an update fileI have been seeing a lot of posts about people not receiving the OTA on their phone, and got tired of linking my instructions, so I decided to make a separate post
Download the version that you need from the Asus Zenfone 8 Support page (Note that if you are not on the latest Android 11 firmware (30.12.112.72), you will not be able to Android 12. So you need to do these steps with the latest Android 11, and then re-do them for the Android 12 firmware)
Plug in your phone to your computer, make sure the computer is trusted and that you can transfer files from the PC to the phone.
Move the zip file of the update in the base directory of the phone (The same directory as Alarms, Downloads, etc).
Wait for the transfer to finish, then you can unplug your phone if you want.
Reboot the phone
After the reboot, the phone will take a few seconds/minutes and will notify you that an update file was found, select the option to update the phone
It will then extract the update and install it all by itself, the normal update procedure starts from there
not work for me :/
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
eVen123 said:
I've spent a couple of hours yesterday to get this thing working. Basically, the Android 12 update will only update from specific image. I will try to describe the whole process below.
You have to do this process to upgrade all the way up to 30.12.112.7. If you have anything else, it won't work.
First, I've reverted back to stock, using
WW-ZS590KS-31.0803.0403.54-user_20210831-release.zip
... which contains the full flash scripts.
In my case, I had to do these delta upgrades manually (so copying the zip to root of sdcard memory).
UL-I006D-ASUS-30.12.112.56-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.62-1.1.31-user.zip
UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip
UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip
Number 4 is actual android 12 update. Hope this helps anyone.
Click to expand...
Click to collapse
I think that what is needed is to update to the latest firmware, then Android 12. So if you are already on Android 11, but not latest firmware, install it with the instructions, then do the same to update to Android 12's latest version.
drum94 said:
not work for me :/
Click to expand...
Click to collapse
What part does not work? Please be more specific and also, you should re-read the steps more carefully, in case you missed something
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
drum94 said:
The android version I currently have is 30.12.112.72
I downloaded version 31.1004.0404.81 from the asus site to have android 12 on my zenfone 8.
I copied the folder without extracting it and put it in my phone's internal storage next to the other folders.
Once the copy was finished I restarted my phone so that it offered me the update but it did not offer it to me.
I do not understand why .
Click to expand...
Click to collapse
It also depends what prefix your installation has. See the first letters
UL-...
If you are from some other region, it could be that UL- is not a fitting upgrade option for you. As far as I can tell, it's not possible to tell which of the versions you have.
I give you the build number which is marked in the software information:
RKQ1.2021022.002.30.12.112.72
I have the right version or not suddenly?
Thank you for the quick tutorial. I was doing this via fastboot till now.
However: I upgraded to the latest firmware BEFORE Android 12. No issues.
Then I upgraded to the Android 12 firmware: stuck. Gave me some kind of ram dump, reboot returned me to the same error: bootloop. I was able to reboot and get to the bootloader. After selecting "recovery" it actually booted Android. And now for the weird part: it looks like I have a mix of Android 11 and Android 12 now! The phone is all but unusable for how slow it is. But the main UI looks like Android 11 still, but things like the reboot screen now look like Android 12. Bizarre...
I was at least able to enable ADB debug again, so I think I will be able to recover the phone. Still a weird issue though. Don't know if flashing with fastboot would have prevented it...
If anything fails, you can always try the Asus flash script it will solve most of the issues with your phone, just note that it installs Android 11 (30.11.51.115)
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
EDIT: nvm, I saw your other reply, you alreay tried that. Were you able to get it working again?
Going from WW-30.12.112.82 to WW-31.1004.0404.107 worked flawlessly, i did not lose settings or data on that upgrade (but I want to stress that a good backup is STILL a very good thing to have!) It then started downloading the 31.1010.0410.43 upgrade on its own. (shown in the ui as SKQ1.210821.001.31.1010.0410.43)
Why didn't I upgrade to the latest one myself? Simple: I goofed up and downloaded the older one.
change the name in UL-ASUS_I006D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Hi, has anyone tried to upgrade a firmware that has Magisk and TWRP installed? Today Android 13 has been released for the Zenfone 8, but I wouldn't really like to do something really dumb such as upgrading, rebooting to recovery to reinstall Magisk only to discover that TWRP has been replaced by the stock recovery and the phone completely erases any data it has stored.
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Rokcy98 said:
You can update by putting the fw in sdcard folder, while keeping magisk (you need to restore images before updating and reinstalling magisk in the inactive slot after updating, then reboot). Otherwise, you can just update through system or through twrp, and after that, boot/flash twrp and install magisk again. In both ways you won't lose any data
Click to expand...
Click to collapse
Thank you! As this is my first phone with A/B slots, I wasn't completely sure about how to proceed. I'll follow your instructions! The only thing I don't get is where is TWRP stored and why it won't be overwritten by the update.
EDIT: installed successfully, thanks!