Related
Hey everyone,
I apologize if this has already been asked; did some searching but didn't really find much.
So I updated my samsung galaxy tab 8.9 wifi to ICS via Kies when the update was released sometime back, not thinking that it would prevent me from being able to root (I know, stupid of me). I always figured Samsung devices were developer friendly, and always had easy ways to root them.
I tried the root instructions posted in all the tutorial posts, and unfortunately they does not work for me (and I presume others). I get a "E:unknown volume for path [/sdcard]" error when trying to access "apply update from external storage" from recovery. I assume this is a change to the bootloader/recovery that Samsung made to prevent unauthorized access (aka, rooting), which is kind of a bummer if you ask me.
When googling for that I found a lot of stuff, but nothing that really told me the best course of action to take for this tablet. Should I hold out for someone to come up with a solution, or would it be best to revert back to 3.2 (if that is even possible), and then "install" the package I saw on the XDA developers front page that gets ICS on the tab with root access. Or is there something else I should do? I've found articles explaining some courses of action, but none explicitly related to the new ICS update that was just released (these were mostly articles referencing the prior 3.2 version).
I realize it was only recently since the update was provided, but any ideas/suggestions would be appreciated. I would like to have root again on ICS if possible!
Thanks.
Was answered several times, e.g. here
http://forum.xda-developers.com/showthread.php?p=31196953
zemoffm said:
Hey everyone,
I apologize if this has already been asked; did some searching but didn't really find much.
So I updated my samsung galaxy tab 8.9 wifi to ICS via Kies when the update was released sometime back, not thinking that it would prevent me from being able to root (I know, stupid of me). I always figured Samsung devices were developer friendly, and always had easy ways to root them.
I tried the root instructions posted in all the tutorial posts, and unfortunately they does not work for me (and I presume others). I get a "E:unknown volume for path [/sdcard]" error when trying to access "apply update from external storage" from recovery. I assume this is a change to the bootloader/recovery that Samsung made to prevent unauthorized access (aka, rooting), which is kind of a bummer if you ask me.
When googling for that I found a lot of stuff, but nothing that really told me the best course of action to take for this tablet. Should I hold out for someone to come up with a solution, or would it be best to revert back to 3.2 (if that is even possible), and then "install" the package I saw on the XDA developers front page that gets ICS on the tab with root access. Or is there something else I should do? I've found articles explaining some courses of action, but none explicitly related to the new ICS update that was just released (these were mostly articles referencing the prior 3.2 version).
I realize it was only recently since the update was provided, but any ideas/suggestions would be appreciated. I would like to have root again on ICS if possible!
Thanks.
Click to expand...
Click to collapse
Check this thread: http://forum.xda-developers.com/showthread.php?t=1406137
I just got mine rooted and I had the exact same issues as you. It's basically a broken root, as laid out in the OP of that thread I linked. See the How To section, subcategory Fixing Root.
Thanks,
I swear I did search, but apparently didn't know what key words to search for. I apologize for the duplicate post.
I have same issue and have thoroughly trawled the referenced threads. Can't access a root zip from recovery and can't flash a recovery from Odin. As a relative newb would really appreciate a step by step idiot's guide
alexbush said:
can't flash a recovery from Odin.
Click to expand...
Click to collapse
Why not? What goes wrong? What recovery file did you try this with?
Tried various versions of cwm. Odin simply freezes although it has a connection to com6. Stock recovery same issue.
I'm not sure where the appropriate place for this would be, and I apologize in advance if this isn't it, but I need some assistance.
For starters, I'm an absolute n00b when it comes to anything root and I don't understand the language and procedures to it, only how to do it by following instructions. Hence why I'm currently on a 4.4 untethered root.
I'm due for an upgrade this month and am torn between getting a later device with Lollipop or a newer device with Marshmallow. The deciding point is if there's any kind of walkthrough on rooting Marshmallow, preferably a dumbed-down version for nondevs like myself.
I know there's currently an experimental one provided by Chainfire, and I skimmed through it but couldn't really understand it.
So any assistance would be greatly appreciated.
@Chainfire If you could weigh in, that would be very helpful.
What are you on about untethered root this isn't IOS. Also it's just two simple steps:
Get a recovery for your device (TWRP preferably)
Use either the stable zip from this forum or beta zip thosent matter and transfer it to your device.
Flash it in the recovery done you're rooted
@Xmaster24 I appreciate the response. I was losing hope on getting an answer as I had already gone with the newer device for my upgrade.
In jcase's pie thread for the 2013 Motorola line, that's what the 4.4 root was referred to as. Wasn't confusing Android with iOS.
And I apologize for being so n00bish, but how would I go about getting TWRP recovery? I do know how to flash the zip from there as I used Safestrap on my current device (but I already needed root access for it to work).
Kodalades said:
@Xmaster24 I appreciate the response. I was losing hope on getting an answer as I had already gone with the newer device for my upgrade.
In jcases's pie thread for the 2013 Motorola line, that's what the 4.4 root was referred to as. Wasn't confusing Android with iOS.
And I apologize for being so n00bish, but how would I go about getting TWRP recovery? I do know how to flash the zip from there as I used Safestrap on my current device (but I already needed root access for it to work).
Click to expand...
Click to collapse
Depends on your device just tell me what it is and I can send you some info. Safestrap seems to be dead for at least a year thosent sound very safe lol.
Xmaster24 said:
Depends on your device just tell me what it is and I can send you some info. Safestrap seems to be dead for at least a year thosent sound very safe lol.
Click to expand...
Click to collapse
I'm getting the Samsung Galaxy S7 Edge. Considering it's not out in the US yet (I have it on preorder), I'm not sure if you'd be able to tell me anything at the moment.
Kodalades said:
I'm getting the Samsung Galaxy S7 Edge. Considering it's not out in the US yet (I have it on preorder), I'm not sure if you'd be able to tell me anything at the moment.
Click to expand...
Click to collapse
Oh dear yes it has just been released probably no rooting info available for quite some time considering samsungs stance on root and open software. Maybe check again in a few weeks or months
Xmaster24 said:
Oh dear yes it has just been released probably no rooting info available for quite some time considering samsungs stance on root and open software. Maybe check again in a few weeks or months
Click to expand...
Click to collapse
Bummer. Kinda expected something along those lines though so I'm not surprised.
Would getting TWRP or some other kind of recovery still be possible at the very least?
Kodalades said:
Bummer. Kinda expected something along those lines though so I'm not surprised.
Would getting TWRP or some other kind of recovery still be possible at the very least?
Click to expand...
Click to collapse
Flash fire could work but it requires root already. Doubt there are any easy exploits on a flagship just released phone
Xmaster24 said:
Flash fire could work but it requires root already. Doubt there are any easy exploits on a flagship just released phone
Click to expand...
Click to collapse
Makes sense. I really appreciate the help. If you happen to learn of anything more, please let me know.
Kodalades said:
Makes sense. I really appreciate the help. If you happen to learn of anything more, please let me know.
Click to expand...
Click to collapse
Guess not kingo root seems to be working :http://www.xda-developers.com/galaxy-s7-root/
Hello XDA,
I just purchased a new Acer Iconia One 8 B1-850 and was wondering if I could root it.
I see many posts on B1-810 and similar, but nothing for the B1-850.
CoreyGamingTV said:
Hello XDA,
I just purchased a new Acer Iconia One 8 B1-850 and was wondering if I could root it.
I see many posts on B1-810 and similar, but nothing for the B1-850.
Click to expand...
Click to collapse
same here
i want to root to enable the multi user option by updating the build.prop file, i've been able to connect with ADB but the device isn't visible in windows or mac (tried both) when you reboot into boot loader, in fact it doesn't appear to boot into boot loader it just seems to power off (when using ADB reboot command or choosing boot loader from the recovery menu) so i wonder if its locked out somehow??
Need it too. Did anyone find a way to root B1-850?
Thanks!
dtalas said:
Need it too. Did anyone find a way to root B1-850?
Thanks!
Click to expand...
Click to collapse
I too just purchased a B1-850 tablet, but I've figured out how to root it. Really quite simple. Just use Kingroot:
1.) Navigate to https://kingroot.net/ from your tablet
2.) Download the APK for android
3.) Install said APK (this requires you to have allowed installation from unkown sources in the "Security" panel of the settings menu)
4.) Load up the app and follow its instructions
5.) Reboot and try it out
For good measure, I would also unlock the "Developer Options" panel and allow USB debugging (adb access) and such; I did this before proceeding. You'll have to search for instructions on that yourself, its well documented.
This all worked for me this morning! Really looking forward to unlocking the potential of this cheapy tablet.
Kingroot worked first try, just swap their super user program with supersu. I am having trouble installing the xposed framework though if anyone has any tips.
I was able to root, now I need to install a custom recovery. CWM says this model is not in the supported list. Has anyone been able to install a recovery? I need NANDROID backup functionality.
I made a thread walking you through how to do it on this tablet in the guides area but just use flash fire for recovery and xposed install
Did the B1-850 hardware updated in anyway? I was able to root it in June 2016, but after a screen repair and factory reset and fresh rom from acer, king root and all others can't work. I'm stuck without any root options. Any idea?
Same here
Dylfaus said:
Did the B1-850 hardware updated in anyway? I was able to root it in June 2016, but after a screen repair and factory reset and fresh rom from acer, king root and all others can't work. I'm stuck without any root options. Any idea?
Click to expand...
Click to collapse
There was recently new firmware released for this tablet (08/24/16, Build #: AV0L0.RV09RC04.WW.GEN1), and a handful of updates (08/25/16, 08/26/16) from Acer. I have this same tablet, and I'm unable to root after flashing to the firmware released on the 24th, and latest firmware (Build #: AV0L0.RV0BRC02.WW.GEN1) as well. Hopefully someone can find a fix, as the few different methods I've attempted simply will not work with the latest firmware from Acer.
On KingRoot Please click submit search if enough people do they will find a root until then just hold tight.
jared407 said:
On KingRoot Please click submit search if enough people do they will find a root until then just hold tight.
Click to expand...
Click to collapse
I have done this a bunch, sadly still no love. It's annoying me not being able to root a relatively cheaper tablet, as these tend to get rooted first since they get in more people's hands faster. Oh well, just have to have patience.
Thanks, I was having problems, two different rooters failed and I wondered if it was the recent software update! The image version on my B1-850 is the same as you have quoted! Please post if you find a solution, some apps that need deleting are annoying.
---------- Post added at 06:23 PM ---------- Previous post was at 06:13 PM ----------
random4t4x14 said:
There was recently new firmware released for this tablet (08/24/16, Build #: AV0L0.RV09RC04.WW.GEN1), and a handful of updates (08/25/16, 08/26/16) from Acer. I have this same tablet, and I'm unable to root after flashing to the firmware released on the 24th, and latest firmware (Build #: AV0L0.RV0BRC02.WW.GEN1) as well. Hopefully someone can find a fix, as the few different methods I've attempted simply will not work with the latest firmware from Acer.
Click to expand...
Click to collapse
I was having a problem rooting my device and wondered if it was the recent software update, and my image version is as you have quoted! I f you manage to root your device please post!
knockout350 said:
I made a thread walking you through how to do it on this tablet in the guides area but just use flash fire for recovery and xposed install
Click to expand...
Click to collapse
Which recovery do you install with flash fire; I don't see a link to it in your other thread?
Success!
The latest release of KingRoot is able to root the latest firmware for this tablet. I saw there was a new release of KingRoot back on the 23rd, and it's working as it should. I grabbed the working version here -> http://forum.xda-developers.com/devdb/project/dl/?id=21707
hi guys. any idea how to recover b1-850 from bootloop?
I no its a little late but i rooted mine with the kingoroot one click root apk. Ive installed xposed framework and customized like crazy everything from fonts to boot animation. Cant find a custom recovery tho.
I cannot root it with any of the tools I have tried (Kingo ROOT, KingRoot, etc). Anyone know any method that works?
Acer B1-850. Is this device even rootable?
This device has made an idiot of me. If I can be of any assistance finding a root exploit for this device let me know. I will gladly write a detailed procedure of the process. I made the mistake of assuming since it was an entry level, inexpensive device, the path to root would be simple. Three months later none of the common "one-click" programs has found an exploit. I have a copy of stock rom for recovery so testing is not a problem for me. It's a matter of pride at this point. So much so I found one on sale for $60 and bought it just for this purpose. I have followed every link I can find associated with this device to a dead end. Any help will be appreciated.
pdnorman said:
This device has made an idiot of me. If I can be of any assistance finding a root exploit for this device let me know. I will gladly write a detailed procedure of the process. I made the mistake of assuming since it was an entry level, inexpensive device, the path to root would be simple. Three months later none of the common "one-click" programs has found an exploit. I have a copy of stock rom for recovery so testing is not a problem for me. It's a matter of pride at this point. So much so I found one on sale for $60 and bought it just for this purpose. I have followed every link I can find associated with this device to a dead end. Any help will be appreciated.
Click to expand...
Click to collapse
Same here, still no root for me. Usually these cheapo tablets are not as locked down.
Still waiting!?
I have given up getting assistance from xda on this device. Its as political here as anywhere else. I don't drive a Samsung so nobody wants to help with root. I've heard every excuse from locked bootloader (unlockable in dev options) to what one dev actually told me,"There's little interest in spending energy on an inexpensive device." I understand, but why misrepresent the site by implying all android devices are treated the same? Hell on the Iconia One 8 thread, it says that the B1-850 does not have a MTK SoC, but instead has an Intel Atom chip. Then they send you to another thread where, of course, there is no B1-850 listed! That's because it uses a MTK8163 SoC. In both tablets.
(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.