I have an unlocked bootloader. (Because I will probably want to root the phone in the future and want to be able to keep user data. However I don't want to root it right now because then my children will not be able to catch pokemons.) What I was not aware of is that unlocking has disqualified me from any official updates. So the question is: how can I get the latest stock version into my phone? Preferably with intact user data.
Sony seems to have pretty good support for unlocked devices. You'll just have to use an alternate route to update stock. This might help: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Edit: You could also try flashing the latest Magisk, 10.2, which provides systemless root. Delete your system su binaries and you can probably have root + PoGo. But there's another thread for that.
I was able to update with xperifirm + flashtool with intact user data.
Although the first attempt resulted in a soft brick. But I had better luck with the Linux version. Might be a driver issue I guess.
Bigfoot987 said:
I was able to update with xperifirm + flashtool with intact user data.
Although the first attempt resulted in a soft brick. But I had better luck with the Linux version. Might be a driver issue I guess.
Click to expand...
Click to collapse
Glad to hear it worked. If you look into the newest Magisk for your root solution, you should have no problems running Pokemon Go.
OK, I'm a newbie to Sony devices, so here is my question:
Let's say XC phone is on Nougat, BL unlocked, TWRP + custom Kernel installed, rooted as well. Now Sony releases a new February security update. Of course I can't install the OTA. So if I head to Xperifirm and Flashtool for a firmware upgrade, how do i proceed to preserve the custom recovery, custom kernel? I know how to keep the userdata, but i suppose root will be gone. I would like to upgrade the firmware with the least hassle, am I on the right track or is there a better/faster way?
On my z5c i flashed new firmware without any wipes, than flashed custom kernel. That's all.
Related
My phone is prompting me to update to B29, but when it reboots, it brings me to the TWRP recovery, and I can't seem to find an update.zip or anything. Is it not there, or am I just looking in the wrong places? Will it even successfully update with the bootloader unlock (not the official unlock) and TWRP installed, or do I need to restore the stock recovery?
My phone was originally on B20_boot, but I've since restored using Draken's TWRP files to get to B27 (I'm assuming still B20_boot).
You won't be able to OTA update with your system modifications. DrakenFX has flashable zips posted in another thread, but beware there seems to be quite a few bugs in b29 (I have no in-call audio personally).
You can use my updated post to B29 (bootstack and boot/system) flashable files are there.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
So why am I getting the notification, then? Will it just keep popping up, or is there a way to block it (even though I'm not rooted)?
As for the bugs, I've seen plenty who have upgraded to B29 without issues. How did you update? Could it be something with updating via TWRP?
Have you personally heard of anyone having problems with your update file? Will it wipe my phone (ie: will I have to reinstall everything)?
Bootloader unlocked, normal twrp flash as per DrakenFX's instructions. And yeah but a lot of people are in both boats so your milage may vary.
Thanks. Do you think I'll be able to keep my data partition intact? I really don't want to set everything else up again. It's getting old... lol.
I wiped everything, so I'm not sure. Maybe that's why my stuff is broken lol
You can't do system updates with custom bootloader's. You are getting the message because you still have the update program on your phone. Look for some sort of update.apk and disable or uninstall it.
I didn't think you could do that without root.
Oh well, I plan on putting root back on soon anyway.
That would be interesting, if true. You would think a "dirty flash" would cause more problems than a clean one.
What about the whole "can't root B29" thing. I've seen a comment where someone said they could not root B29 since they didn't root before the upgrade. I'm not rooted now, but I am bootloader unlocked with the latest TWRP. Should I be ok to flash without rooting first? I was hoping to root afterwards, and try to figure out a way to make Magisk work.
You can't root locked bootloader B29 afaik at the moment. You'd either have to unlock your bootloader or stay on B27 to get root.
I am bootloader unlocked.
I'm not rooted now, but I am bootloader unlocked with the latest TWRP.
Click to expand...
Click to collapse
I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?
Read the nougat thread in general.
lafester said:
Read the nougat thread in general.
Click to expand...
Click to collapse
I have seen this thread: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
But I was wondering there was a more simple or directly method which doesn't involve EDL mode?
Edit: Nevermind, I don't know why I was expecting a more simple method, nothing on the A7 is more straightforward than that. I'd still like to know if I should be expecting any issues and if a full wipe is needed. For that matter will my phone be wiped anyway if I install that ROM?
Cyrus D. said:
I'm currently sitting on the stock 6.0.1 B29 ROM for my 2017U A7, which is BL unlocked, rooted (SU 2.79-SR2), Xposed, with RootSwitch working, and TWRP.
What's the most simply way for me to upgrade to Nougat while maintaining those things listed above (aside from Xposed which I know doesn't support Nougat yet)?
Would I be forced to wipe my phone after installing Nougat in order to get everything working optimally?
Are there any issues or potential problems when upgrading that I should be aware of?
Click to expand...
Click to collapse
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.
bluestudy said:
I don't see any reason that you couldn't flash the universal bootstack and modem for the U variant from the Lineage thread, and then flash the stock Nougat ROM that's posted in the BadBoyz Magisk thread. Or just flash the bootstack and modem, then flash that ROM, being that it's stock and should still allow you to pass SafetyNet.
Click to expand...
Click to collapse
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go to prevent any possible mistakes.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.
Cyrus D. said:
I would assume that it'd overwrite TWRP and I'd have to reinstall that again, and considering all the steps overall, that's not really any faster than jcadduono's EDL mode method which installs the bootstack + ROM + TWRP from one package and can recover a brick.
Basically I was hoping there was a method that could just allow one package to be directly flashed and get it all done in one simple go so I don't have to do a song and dance every time I want to change my ROM. But I don't know if I can just do that with jcadduono's package because IIRC TWRP doesn't automatically install things to where they should be, you have to manually select it (recovery, etc) and that package needs to be installed to multiple locations. Or maybe I have no idea what I'm talking about it.
I said screw and installed the necessary program and drivers to flash the package with the Nougat bootloader + ROM + TWRP in EDL mode, it appears to detect properly, but I don't know if I want to go through with it until Xposed arrives. Between YouTube ads or grinding my face with a belt sander, I think the latter is less painful and horrific.
On the topic of SafetyNet, I currently pass it if I switch root off, yet Nintendo games won't install on my phone. They show as "incompatible with your device" the same as if they detect I have root. I have SUHide installed as well, but I have no idea how to check on that (where it is or how it functions for that matter). Installing the APKs from an alternate source just results in them crashing on start-up. Nintendo REALLY don't want root users playing any of their games.
Click to expand...
Click to collapse
Have been able to play Pokemon Go (my son, lol) and Fire Emblem on several Lineage based ROMs using Magisk. Can also get Android Pay to work (except for my bank currently not supporting it, but it doesn't show that I'm running any third party ROM or have my bootloader unlocked.) So, that might be the way for you to go, if you decide to try it out. As far as the EDL method, I've never tried it, but it does seem like an extremely useful tool.
Sorry went back and edited my post. It seems I was mistaken and I'd have to at least flash 2 packages by the EDL method, the TWRP package isn't the full ROM, just the bootloader and recovery. The only thing I can get working is Pokemon Go if I switch off root. Is Magisk working on the stock Nougat ROM as well?
Hey guys, so I'm still pretty new at this whole android modding stuff (but I do have some background knowledge). I managed to unlock the bootloader, install TWRP, and root B29. However, now I wanna upgrade up to Nougat and eventually to the newest firmware available (either B19 or B25, not sure which one yet because I've heard quite a bit about B25's lack of fastboot). Anyways, I have no idea how to get there while still retaining my custom recovery and root. I tried using Flashfire, however, since MiFavor auto-installs after it finishes downloading the OTA, I can't stop it fast enough to launch Flashfire and install it through that. Could anyone point me in the right direction (or show me a guide) that would help me get to the newest firmware? Thanks!
P.S: This is slightly unrelated, but I was wondering, would I have to flash a custom bootloader+modem if I choose to flash a stock update through TWRP? I heard that if you choose to upgrade to a newer generation of android (i.e: Marshmallow to Nougat) through a custom recovery, that you'd have to flash an updated version of the bootloader+modem as well, but the thing is I'm planning on staying on MiFavor, so I'm not sure if it'd be necessary.
HunterBlade said:
Hey guys, so I'm still pretty new at this whole android modding stuff (but I do have some background knowledge). I managed to unlock the bootloader, install TWRP, and root B29. However, now I wanna upgrade up to Nougat and eventually to the newest firmware available (either B19 or B25, not sure which one yet because I've heard quite a bit about B25's lack of fastboot). Anyways, I have no idea how to get there while still retaining my custom recovery and root. I tried using Flashfire, however, since MiFavor auto-installs after it finishes downloading the OTA, I can't stop it fast enough to launch Flashfire and install it through that. Could anyone point me in the right direction (or show me a guide) that would help me get to the newest firmware? Thanks!
P.S: This is slightly unrelated, but I was wondering, would I have to flash a custom bootloader+modem if I choose to flash a stock update through TWRP? I heard that if you choose to upgrade to a newer generation of android (i.e: Marshmallow to Nougat) through a custom recovery, that you'd have to flash an updated version of the bootloader+modem as well, but the thing is I'm planning on staying on MiFavor, so I'm not sure if it'd be necessary.
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Is there a working root method for the Moto G4 (Running Android 7.0) yet?
And I'm not talking about the G4 plus...
I desperately want to break my phone free.
There must be one by now.
TheTechnoToast said:
Is there a working root method for the Moto G4 (Running Android 7.0) yet?
And I'm not talking about the G4 plus...
I desperately want to break my phone free.
There must be one by now.
Click to expand...
Click to collapse
G4 and G4 plus use the same method, flash TWRP then elemental x kernel and then you can root it With super su or magisk.
Enviado desde mi Moto G⁴ #StayUnbeaten
syverman said:
G4 and G4 plus use the same method, flash TWRP then elemental x kernel and then you can root it With super su or magisk.
Enviado desde mi Moto G⁴ #StayUnbeaten
Click to expand...
Click to collapse
Thanks for the reply! Is there a guide to do this?
TheTechnoToast said:
Thanks for the reply! Is there a guide to do this?
Click to expand...
Click to collapse
I wanted to try it but I have a problem with the bootloader that I can not unlock because my computer is the amazon version that no one could remove said ads in the latest security update NPJ25.93.14.5, if anyone knows of any solution I will be grateful .
TheTechnoToast said:
Thanks for the reply! Is there a guide to do this?
Click to expand...
Click to collapse
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting
echo92 said:
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting
Click to expand...
Click to collapse
Thanks for this. Yes, I'm okay with all of this (I've rooted my previous phones), I'm aware of the risks and stuff. I'll give this a try ?
flako72 said:
I wanted to try it but I have a problem with the bootloader that I can not unlock because my computer is the amazon version that no one could remove said ads in the latest security update NPJ25.93.14.5, if anyone knows of any solution I will be grateful .
Click to expand...
Click to collapse
Um... Could you ask questions in your own forum please? This forum is for rooting help for the Moto G4.
TheTechnoToast said:
Um... Could you ask questions in your own forum please? This forum is for rooting help for the Moto G4.
Click to expand...
Click to collapse
I think he is asking about the Moto G4 Amazon version. So he is in the right forum.
Caxref said:
I think he is asking about the Moto G4 Amazon version. So he is in the right forum.
Click to expand...
Click to collapse
Oh, okay. But even still - I think he should be asking the question individually. Not only would he get more help from people but it wouldn't detract from my post.
echo92 said:
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting
Click to expand...
Click to collapse
Thanks so much! Worked perfectly on the Moto G4.
Consider the question closed
I am on OOS 4.5.13 "stock", i used the engineering mode exploit to get magisk root while my bootloader is still locked, now i want to upgrade to latest OOS oreo but i am afraid that this exploit might end up bricking the device. My bootloader is still locked and i have stock recovery (sorry if stating the obvious) and i have no problem losing my data to upgrade to oreo, but i would like to get magisk on oreo when i upgrade, any tips/precautions or a link to a guide would be very helpful. I don't need to root right away as i might like getting OTA updates but i don't wan't to wipe the device another time for some special procedure.
Should i unlock bootloader then upgrade or reverse the order? I keep getting these prompts to upgrade with a disclaimer that full system needs to be downloaded, should i just do it OTA?
PS: i have titanium backup working and can backup the apps i need.
yohouse2 said:
I am on OOS 4.5.13 "stock", i used the engineering mode exploit to get magisk root while my bootloader is still locked, now i want to upgrade to latest OOS oreo but i am afraid that this exploit might end up bricking the device. My bootloader is still locked and i have stock recovery (sorry if stating the obvious) and i have no problem losing my data to upgrade to oreo, but i would like to get magisk on oreo when i upgrade, any tips/precautions or a link to a guide would be very helpful. I don't need to root right away as i might like getting OTA updates but i don't wan't to wipe the device another time for some special procedure.
Should i unlock bootloader then upgrade or reverse the order? I keep getting these prompts to upgrade with a disclaimer that full system needs to be downloaded, should i just do it OTA?
PS: i have titanium backup working and can backup the apps i need.
Click to expand...
Click to collapse
if you are ok with loosing data then i suggest you to unlock the bootloader then flash the latest oos build from the official website ( that makes it easy for you to switch roms easily in the future )
if you need your data then just accept the ota ( obviously you will lose root access and magisk features )
but imo no harm can be done accepting the ota as oneplus itself know that most of users are rooted so they send you the ota as a full build that replace the firmware parts previously modified
the choice is yours
Sent from my OnePlus 5 using XDA Labs