this is mosty a copy and past cuz i didnt find this part of the forums when i had to remake my acc. if u watch the video u'll see what i did and what i should cuz the how-to for install magisk is broken to say the least
i have a sony xperia z3v and before u ask yes i did follow when was on the xda but NOTHING works as u see in this video here - https://www.youtube.com/watch?v=Jaga6MUcTdc&feature=youtu.be.
so first thing i need is a Custom Recovery. so i follow what that page here - https://www.xda-developers.com/how-to-flash-install-custom-recovery/ says...
first thing it is say i need Android SDK but never once talks about needing it ONE TIME.
2nd, both links given on that page for the custom recoverys 404! - https://imgur.com/bV9egdH
so what do i do next? i follow whats given and BOTH SITE R DEAD! also that page doesnt ONCE going into how to set up a custom recovery at all.
how is that u guys can help me out when it comes to flashing my sony xperia z3v back to stock after i F-ed up on a root and yet not have a set by set for geting Magisk to work install and work on your phone?
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Didgeridoohan said:
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
yes u do need a custom recovery as said on this page here - https://www.xda-developers.com/how-to-install-magisk/
"What You’ll Need:
A device running Android 4.2+
Custom Recovery (how to install)
We’ll be using TWRP in this guide"
i have the magisk manager already install as is my phone it rooted as u can see in this SS from the phone here - https://imgur.com/a/Kq1EChq but as u see magisk has a red X since its not installed so i go to install it but it give a .zip so i use that and it errors out EVERY ****ING TIME as see here - https://imgur.com/a/VyAslvt
if u toke a few mins of your day to watching the video instead of being a ass and commenting that knowning full well u could have watched the video to see i did everthing that the pages sad u wouldnt be most the comment u just did. u just make yours look like a ass. i want ppl the help me not say "u dont need a custom recovery" when the page on the how to install SAYS U ****ING NEED ONE.
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Didgeridoohan said:
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Click to expand...
Click to collapse
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
let me make it as simple to understand what im looking for. i want to use my Sony Xperia Z3v to game assets dumps for Uta-Macross so i can have pull the 3D models and cards (very nice photos) from the game. to do this i need to have my sony phone rooted and i need to have Magisk so i can hide the root from Uta-Macross so i launch into the game to download the assests to do a dumb. everthing up to this point i have YET to understand what do at all. that link u give - https://topjohnwu.github.io/Magisk/install.html says to this then go here then go here and do this over and over again never saying just do this, this, and this, and your done.
tankball said:
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
Click to expand...
Click to collapse
The instructions by @topjohnwu are pretty complete... They do assume that you are somewhat familiar with things like fastboot, but that is information that can easily be found by searching the big ol' interwebz.
Using a custom recovery is one of the ways of installing Magisk. If this is the route you really want to go I suggest you take a look in your device's forum here on XDA:
https://forum.xda-developers.com/z3
That's usually a good first step since you'll likely find others discussing the same device specific topics.
But if you take a look again in the linked docs, you'll find that you can also use something called boot image patching (which doesn't require a custom recovery at all):
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Rooting and tinkering with your device does require a certain level of knowledge about what you're doing. If you can't follow/understand the instructions available there's a good chance you might mess up your device. If you have your data backed up somewhere off the phone (which you should always have when playing with this stuff) you should be good since a complete and catastrophic failure is very unlikely. It's really annoying to have to set everything up from scratch though...
But if you take a look again in the linked docs said:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching[/url]
Click to expand...
Click to collapse
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
tankball said:
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
Click to expand...
Click to collapse
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Didgeridoohan said:
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Click to expand...
Click to collapse
i should also root the phone again also?
tankball said:
i should also root the phone again also?
Click to expand...
Click to collapse
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Didgeridoohan said:
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Click to expand...
Click to collapse
ok now im lost again. to do date dumps for Uta-Macross i need a rooted phone so i can pull the files without windows again tard and saying "unknow error" when i go to copy the files from my phone. but to play this game i need to hide the root from Uta-Macross so i need to use Magisk. is Masgisk a root itself? im really lost again
Magisk provides a way to do systemless modifications to your device, it is a root solution in itself, and it has the ability to hide itself and it's components from most apps and services that look for a rooted or modded device.
This is kind of the basics, so I reallly suggest you do more research before continuing. The best source for information is the Magisk GitHub page:
https://github.com/topjohnwu/Magisk
Start there, take a look at the readme and the documentation available and continue searching for whatever other information you might need.
I'm not going to be available for further assistance for the next 8 to 9 hours (I hope, but that's entierly up to my little one). G'night.
nothing i did worked. the .zip fail or the D6708_23.4.B.0.319_1288-1477_R30C.ftf file in the .zip witch in the rom from the phone, it will ALWAYS say failed, unsupported/unknow image format.
Morning. Like I posted previously, old (and new) Sony devices have been known to have issues installing Magisk. Search your device's forum for Magisk related posts and you'll likely find the info you need.
Good luck.
Related
Hi,
I made this guide after struggling to install TWRP using several guides on XDA and other forums which fail to mention few other steps needed.
I am using a verizon lg g2 on stock lollipop 5.0.2 , rooted using LG ONE CLICK ROOT. But i guess this guide goes for all g2 variants who cannot simply install twrp on their stock firmware using flashify or autorec.
ISSUE :
I have tried flashify but this app is only useful if you already have an older version of recovery installed since i failed to install any version of twrp and cwm while trying. After installing a twrp , you can flash upgrade recovery using this.
Autorec gives me unresponsive button when tapping on the FLASH TWRP icon.
Other solution requires manual installation such as THIS GUIDE which i haven't tried because i am not that advanced android user yet since i came from using iOS.
The easiest way to install TWRP is autorec but to fix the unresponsive button, follow below steps:
** Ofcourse you need root in order to install custom recovery
1. Install AUTOREC from HERE. There are different app for different g2 variant so install accordingly.
2. Go to SuperSU settings , uncheck " Enable Superuser" and then scroll bottom where you see " reinstall" under CLEANUP section. Tap on that and proceed. Wait few seconds and when done, reboot your device.
3. Go to THIS LINK and download supersu 2.46
4. After its downloaded, tap and install it. Update binary and reboot.
5. Go to autorec, give it superuser permission and tap on the "Flash TWRP" icon and you will see it working.
** note : in order to install latest twrp, you must first install the initial img version and then flash the latest version zip from within. Update link : TWRP 3.0.2-1
Feel free to post below if it worked for you or if you need further assistance.
Help with twrp & flashing rom on g2
I have a rooted G2, ATT W/stock KitKat. At one point when I bought it, it had Lollipop, and TWRP, but I bricked it trying to install Magisk as a workaround to play Pokemon. That began my unwanted journey into the world of rooting, custom recovery, flashing, and the whole bit. I've watched many videos and read many threads but I'm very much a "noob" , and something always goes wrong. I can, and do read instructions but, I have found that usually I don't understand all the slang techy terms, and/or important steps are left out of the tutorials. Most recently, I tried to install TWRP using AutoRec and a YouTube video, and got stuck in TWRP and "soft-bricked".
I started a thread on here asking for help, even offering to donate, and got like 2 short replies saying "flash a custom ROM". Like that explains anything to a newbie.... When I clearly state I'm new at this, that doesn't help. Then today I get notification my thread was moved. Anyway, for a third time, I had to (follow the only YouTube tutorial that has actually worked for me), which just unroots, and puts the device back to a damn factory reset state.
MY GOAL is that I'm bound and determined to at least get Lolliop back on the device. I prefer that over KitKat. I also would love to be able to play Pokemon again, since the a**holes at Niantic blocked rooted phones from playing. Even after I did the factory restore thing and unrooted, the game still wouldn't install, saying "device not compatible". Apparently the Magisk workaround works for some people...
I am getting so frustrated and should just leave well enough alone. Everytime I say I'm not going to mess with it anymore, I end up trying, against my better judgement, and end up bricking.
So one last try.... - If there is anyone out there in XDA land with the ability, or inclination to help, I would greatly appreciate it. I'm not a simpleton, but apparently there are so many things that have to be done precisely, or I get bricked.
If anyone can give simple, step-by-step instructions, leaving nothing out, accounting for anything that might go wrong, provide links that still exist, etc, etc. I will not only be a very happy guy, but my daughter will be happy that she can play Pokemon again, and I will be happy to have Lolliop, or even, dare I dream Marshmallow, and I would GLADLY donate a few bucks to whatever account...
If you've read this far, thanks for that, at least.
it works , thanks man ?
note : I used kingroot to rooting my device .
No dice on AutoRec... do I need a special version?
AutoRec doesn't seem to actually do anything and flashing the recovery through any of the normal programs just leads to an error message when trying to enter recovery. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Bill720 said:
AutoRec doesn't seem to actually do anything and flashing the recovery through any of the normal programs just leads to an error message when trying to enter recovery. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Click to expand...
Click to collapse
Can you please explain that in nubbie terms like step by step i would greatly appreciate it thank you in advance
Clarification
jboo01 said:
Can you please explain that in nubbie terms like step by step i would greatly appreciate it thank you in advance
Click to expand...
Click to collapse
To get the AutoRec app to work, you need to uncheck "tapjacking protection" inside of the SuperSu app (or its equivalent in whatever root manager you use).
not work in d805 lolipop ??????
Hi,
How do I just root my OnePlus 3T? I want to keep everything the same but just be able to have root to install adblock.
Model - A3000
Oxygen - 4.0.3
Android - 7.0
Rob94 said:
Hi,
How do I just root my OnePlus 3T? I want to keep everything the same but just be able to have root to install adblock.
Model - A3000
Oxygen - 4.0.3
Android - 7.0
Click to expand...
Click to collapse
Unlock your boot loader, flash twrp and install supersu to root. or you can also try dns66 to block ads, it works without root.
https://fossdroid.com/a/dns66.html
bonham1988 said:
Unlock your boot loader, flash twrp and install supersu to root. or you can also try dns66 to block ads, it works without root.
https://fossdroid.com/a/dns66.html
Click to expand...
Click to collapse
I'm new to android, switched from ios. I'm not familiar with the terms, how would you do these? "Unlock your boot loader, flash twrp and install supersu to root."
Rob94 said:
I'm new to android, switched from ios. I'm not familiar with the terms, how would you do these? "Unlock your boot loader, flash twrp and install supersu to root."
Click to expand...
Click to collapse
here a guide https://forum.xda-developers.com/oneplus-3t/how-to/guide-how-to-root-oneplus-3t-unlock-t3544391
but if you just want Adblock, I'd suggest you try dns66 instead of root.
bonham1988 said:
here a guide https://forum.xda-developers.com/oneplus-3t/how-to/guide-how-to-root-oneplus-3t-unlock-t3544391
but if you just want Adblock, I'd suggest you try dns66 instead of root.
Click to expand...
Click to collapse
I installed the adb program but where are the files? I'm stuck on this step 2:30 in the video.
Rob94 said:
I installed the adb program but where are the files? I'm stuck on this step 2:30 in the video.
Click to expand...
Click to collapse
What files?
Sent from my OnePlus3T using XDA Labs
bonham1988 said:
What files?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I got past that part but now im stuck. I'm trying to install supersu but my computer isn't finding the oneplus 3t in my computer so I can't drag supersu to my phone to install it.
Part 8:47
https://www.youtube.com/watch?v=wwd31NU7VC0&feature=youtu.be
Everytime I plug in my phone I see this in device manager. Even though I install the ADB.
site to upload photos
I got it to work, just had to manually install MTP driver.
Could you help me find a guide for adblock install and in-app purchases?
Rob94 said:
Could you help me find a guide for adblock install and in-app purchases?
Click to expand...
Click to collapse
Google "AdAway XDA". The first result is the thread for the AdAway app.
And what do you mean in-app purchases? You install an app from the Play Store, tap the in-app button, add your gift card and/or credit/debit card (if required), buy.
If you're talking about circumvention, you are NOT going to get help here, AT ALL. This is not one of those places for that mess.
Rob94 said:
Could you help me find a guide for adblock install and in-app purchases?
Click to expand...
Click to collapse
Ad block you don't need any guide. Just install the apk from f-droid. When you'll open the app it will prompt you to grant root access. Just click yes and you have to enable adblock from the app.
Sent from my OnePlus3T using XDA Labs
Rob94 said:
I'm new to android, switched from ios. I'm not familiar with the terms, how would you do these? "Unlock your boot loader, flash twrp and install supersu to root."
Click to expand...
Click to collapse
I know you are new here, and here is some friendly advice:
1) Search before you post! Most of the info you want, and probably ever want, is already on XDA. It's probably been asked and answered before, probably numerous times. There are a number of guides posted for basic things, like how to root. Just using the search function, or for that matter just browsing through the thread titles will often yield a lot of the info you are looking for. Also, there are resource threads like the Index at the top of the 3T "Guides, News & Discussion" section, which organizes a lot of the useful threads and other resources (with links). Be sure to take advantage of these threads "sticky" to the top of each section.
Only after you have done your due diligence, and can't find what you're looking for, should you make a new thread. If every person who was wondering "how to root" made a new thread asking that, this whole website would quickly become a cluttered, useless mess. The folks here are happy to provide help and try to answer your questions, but only after you've taken at least a little time to try to find the answer yourself.
2) You need to slow down and do some learning and reading. This is something you should have done before starting to do any of the steps toward root. Halfway down the phone modding rabbit hole is not the time to be asking questions like "how do I put the SuperSU zip on the phone".
I've been around here a long time, and modded/rooted a lot of devices. Even so, every time I get a new device, I spend at least an hour or two reading about the root methods (plus possible pitfalls, issues, etc.) for that specific device (as every one has it's own peculiarities and nuances). I simply can't fathom jumping into the root/mod process without this minimum due diligence.
3) Make sure you understand the meaning and implications of an unlocked bootloader, root, etc. There are benefits, and there are also risks. When someone comes on here asking the questions you are asking, what often comes to mind is that a person with that lack of knowledge has no business having root. This isn't to be mean, it's just a fact (at least as I see it).
Side note: I'm not a fan of YouTube guides. They have a place, in conjunction with (but not a replacement for) proper reading and understanding. Just following one of those videos, without doing any other learning, is going to get you in trouble. You'll only know enough to get yourself into a jam (which is inevitable if you play with these devices), without a clue of how to get out. Know (at a minimum) how to recover or get back to stock. Case in point, the linked video skipped what is to me, a critical step. You should always make a TWRP backup before flashing any mods like root or custom ROM. It's not technically a "requirement" but to me, its a must. This gives you an easy way out, if anything goes wrong (and it eventually will). Sure, there are other ways to recover. But the simple step of making a TWRP backup is one way, that doesn't require any additional downloads, tools, etc. It's simply a no-brainer to me, to do this.
(Note: I didn't make any of this software. I just found it all and brought it together. I apologize for not being able to add direct links to each post I got this all from, I didn't record the sites I got them from.)
This is for the people who were unlucky enough to own a VS980 LG G2, rather than the other models which are loved by developers, a phone that is incredibly finicky and niche...
I honestly wish somebody made a guide like this for us VS980 users (a phone which most ROMs don't work on, has a locked bootloader, etc...) before I had to experience this pain.
(Okay, rant over.)
However, I have done it anyway and installed 7.1.1 Nougat on the VS980
(If you don't know the pain I'm talking about, consider yourself lucky...)
I've also gathered all the necessary files to one place so you won't have to hunt like I did. Following this guide to a T should result in a "effortless" to a "dang, I had to do something" modding experience
"Basic" Steps:
Install ALL tools Necessary (Drivers, Programs, Etc...)
Downgrade to Kitkat
Root
Install TWRP and Kernel
Erase Phone
Install Bootstack
Install ROM (CM14.1)
Install Gapps
Reboot and Enjoy (Might take a while first boot.)
Additional Notes (So you guys don't do what I do)
The files are all downloadable here:
Mega: https://mega.nz/folder/nOQiSZhA#geOCtLtVnEqVABogOXhmvA
(The files are 3.3GB so it will take a while.)
Use MegaDownloader to bypass Mega's download restrictions:
https://megadownloader.en.softonic.com/
The folders are marked accordingly to the "Basic" steps listed above.
Follow each of them in order and Open the "READ ME" text file in each for instructions.
Good luck!
(Sorry for the Bland-looking Post and Files, I don't really have a knack for making colorful Guides.)
EXTRA:
If you'd like to try getting 8.1, Here's a link to a ROM (I tested) that works:
https://forum.xda-developers.com/lg-g2/development/rom-aospextended-rom-v5-6-t3802329
Just make sure you flash the bootstack. Files are found in Folder: "9.Things to Try"
Basically follow the same steps (Downgrading, TWRP, etc...)
-Use Magisk to Root (Better than Super SU because, installed properly, it will hide your root so you don't
have to use Root Cloak.) <=(Pokémon GO)
NOTICE: WHEN REBOOTING AFTER FLASHING, DO NOT PRESS INSTALL SUPER SU
Just press do not install. You can root later....
[ Installing Super SU can possibly brick your phone and you'll have to start over ]
(It's just that every time I press that button, it never works... but I'm not sure )
If you brick your phone (Black screen of death), you can use a USB jig to get it to download mode and use the .kdz flasher (Lg Flash Tool) to restart from the beginning with the stock software.
USB jigs are really cheap (like <2$. I just made one myself ) and are incredibly useful to get out of tight situations. If you plan on modding a lot in the future, you should consider getting one.
(If you don't know what I am talking about, try to keep it that way.)
ADDITIONAL RESOURCES:
I thought I should add this (You're welcome BTW)
Bootstacks:
https://forum.xda-developers.com/ve...resources-bootstacks-unofficial-t3050777/amp/
Stock Kdz and Tot Files:
https://lg-kdz-firmware.com/lg-g2-firmware/36.html
(If any download links don't work, I can update them)
Dude, you are the boss.. Been doing this forever, and it is always appreciated when I find someone who puts it all in one place.. MANY MANY thanks to you for putting all this in one place.. Also thanks to the coders who made it possible..
angael said:
Dude, you are the boss.. Been doing this forever, and it is always appreciated when I find someone who puts it all in one place.. MANY MANY thanks to you for putting all this in one place.. Also thanks to the coders who made it possible..
Click to expand...
Click to collapse
Glad I helped
Is anyone still out there?
All of the Mega linked folders are empty, am I doing something wrong?
As a side note, my objective is to upgrade the ROM to at least Marshmallow so I can install Android Auto and Screen2 Auto. There is one app I want to use but it isn't allowed by Android Auto. I'm then hoping to make the phone a dedicated Android Auto "server" and leave it connected to my car's USB port. Any guidance on the best way to do this would be appreciated.
My VS980 is currently on the stock Android 5.0.2 ROM.
Update: I managed to get CM14.1 installed following the "Basic" steps. It took some trial and error but I got there.
If anyone finds this thread and knows of a better ROM for my use I'd be interested in hearing about it.
RKCRLR said:
Is anyone still out there?
All of the Mega linked folders are empty, am I doing something wrong?
As a side note, my objective is to upgrade the ROM to at least Marshmallow so I can install Android Auto and Screen2 Auto. There is one app I want to use but it isn't allowed by Android Auto. I'm then hoping to make the phone a dedicated Android Auto "server" and leave it connected to my car's USB port. Any guidance on the best way to do this would be appreciated.
My VS980 is currently on the stock Android 5.0.2 ROM.
Update: I managed to get CM14.1 installed following the "Basic" steps. It took some trial and error but I got there.
If anyone finds this thread and knows of a better ROM for my use I'd be interested in hearing about it.
Click to expand...
Click to collapse
What happened? I do have LG G2 VS980 and works fine to me. I'm actually in Android 11 now. Links are down? How come?
Absolute Territory said:
What happened? I do have LG G2 VS980 and works fine to me. I'm actually in Android 11 now. Links are down? How come?
Click to expand...
Click to collapse
I think the files expired in Mega (or I'm doing something wrong to access them).
My phone seems to be working OK but I don't use it for making phone calls.
My main problem now is I can't figure out how to access fastboot. I get a "waiting for any device" response when I issue any fastboot command. I can get to the download screen where it is waiting for a firmware update but I can't get past that.
Re uploaded the MEGA link. Don't know why there weren't any files there anymore. It is probably because I didn't check it for a while.
Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
@camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.
I am super new to rooting I mainly use it for PokemonGo. I am following this video on YouTube.
Basically when I flashed via Odin, I then install Magisk. Then everything is working and rooted BUT when I restart my phone my Magisk is then magically unrooted (I dont know if this is the right term) it says 'Magisk is not installed' and underneath that is says 'Magisk Manager is up to date'
So why does it keep doing this? Everytime this happens I need to Flash again via Odin and do the whole procedure again. This only happens when I restart the phone. Why does it keep doing this and how do I fix this? I will pay someone who can fix this for me. Ive been trying to figure out for the past day and Im going insane. I have no knowledge about rooting etc like i said i just want to play Pokemongo location spoofing.
Appreciate everyones help.
What did that guide say on how to boot up your device? On devices like yours, that matters...
Here's what the official docs/instructions have on that:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Didgeridoohan said:
What did that guide say on how to boot up your device? On devices like yours, that matters...
Here's what the official docs/instructions have on that:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Click to expand...
Click to collapse
Hi it says bixy, power and volume up I believe.
littlepuppies said:
Hi it says bixy, power and volume up I believe.
Click to expand...
Click to collapse
You mean from the guide? Yes, as far as I understand that's the combo that you'd need on an s10 (I don't do Samsung). If you look at John's instructions he's covered that prety well.
Are you sure that you are doing the button combo properly? Because if you don't you'll just end up with Magisk not loading during boot and the system will seem to be unrooted.
But, as I wrote above I don't do Samsung so I'm not the best person to give advice about this... You might be better of asking for advice in your devices forum (because there you'll find people who knows the ins and outs):
https://forum.xda-developers.com/s10-plus
Thread closed as duplicate of https://forum.xda-developers.com/s10-plus/help/samsung-s10-plus-everytime-restart-t4099659